I have started to add functions to MinimOsd code.
At first i did it for myself only. Added many functions i thought i need. Then opened this thread.
after a while, Pedro and later Miguel came, and things started to happen fast. :D
They have optimised the code and added even more things to it.
They have worked hard on CT, and it became a great tool!
Thank you Bough! :)
By now MinimOSD-Extra got a pretty advanced OSD.
Here it is in action:
- Changeable unit measurement (US, metric)
- Home alt
- Battery Percent
- Battery used mah
- Current Draw
- Time From Startup (cleared at takeoff to show exact flight time)
- OSD Menu
- Wind horizontal speed and direction, and also the average wind speed of the last few minutes.
- OSD on/off
- Switchable secound screen
- WP distance
- WP heading
- Crosstrack error
- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI
- Efficiency, glide distance & thermic notifier. 3 in one panel
- OSD Brightness
- HAM Call Sign
- After flight summary
- Trip distance
- Smoothened horizon
- Real heading
- Vertical speed
This functions can be turned on and off, and placed on different screens now, by the Config. tool.
Also RSSI, switching mode and channel and unit measurement, Stall speed warning, Overspeed warning, Battery warning volt, Battery percent warning, RSSI warning, can be set in new Config Tool.
We built in a new way of setting video standards. Now OSD does not guessing anymore :). You can set it fixed from CT. It is in "Video Mode" menu.
Here is how it looks: (This video is a bit outdated, sorry. I will make a new one soon.)
The MinimOSD-Extra project is here: Link
This project is the developing version of the official Arducam OSD located here: Link
The latest stable version is: 2.2
The latest version can be downloaded from here: MinimOSD-Extra R800
CT is included. (The FW for Plane, Copter, Character upload and the character file is in the "FW & Char" directory inside CT directory)
We are sharing it to see videos you make using it! :)
Could you please add more info:
What "latest" firmware are you using (version #, quad, plane, ...)?
Which CT Tool version?
OSD data doesn't appear in video at all or it stays "freezed"?
I use miniOSD v1.1 downloaded the version 2 frimware with the characters set as well it updated well fom Arducam-OSD (zip and hex file)
I get the screen 1 and 2 whic i reconfigured to suit my liking
I see some characters but no data at all
can yu give me a list of the setting of what Ihave to tick
in config OSD Toggle channel must be ?
whar RSSI mi and Max I used default
must channel raw be on ??
RSSI is ticked
the miniOSD is v 1.1
I use Fatshark goggles used to work before I flashed
do you know were to find the original firmware for v1.1 ????
the data send by APM using 3DR telemetry works fine.....
the video is ok
a bit of character garbage on the goggles screen but no data what so ever
I tried reflahing
Toggle channel... are you using a switch on your Tx to switch screens, or are you changing screens with the flight mode switch? Select the correct channel and uncheck Rotation, or select Mode and check Rotation depending on what you are doing with it.
RSSI must be calibrated... read the wiki procedure on that... it involves first writing down your calibrated numbers by checking "Raw" and powering the Tx on/off. Then you uncheck RAW, and enter those numbers in the min/max boxes.
By character garbage, do you mean just unecessary icons, or garbled/staticy icons? Unecessary icons is one thing (edit code to taste), garbled display is another (that means you have overlapping red squares somewhere in the CT).
I was going to suggest checking SR0/SR3 parameters against this list, but if it worked before you updated the OSD and telemetry works, then I guess those parameters are OK. MP does have a new OSD check box, which I guess will set those parameters for you.
Is this for a copter, or plane? The firmware that comes with minimOSD is I believe arducamOSD... way out of date and AFAIK it does not work with the latest arducopter release. Not sure about arduplane. With that in mind, here's the original firmware: http://code.google.com/p/arducam-osd/downloads/list
I fly an hexcopter with OWSD and Fatshark this saved my hex twice
did you ever see this osd phaenomenon that suddenly all fields are flashed in?
I just installed the latest MinimOSD Copter Pre-Release BETA firmware in my new MinimOSD. I'm using CT 220.127.116.11 for the adjustments. I've pretty got most of it set up the way I like. I'm having an issue with the Altitude reading though. It's displaying my Above Sea Level reading. I'm wanting to have it display Above Ground Level. Is this a bug in the pre-release version or am I not doing something right? I appreciate any help in resolving this. Thanks in advance.
edit: Never mind. Someone straightened me out. I had selected 'Altitude' for my display. I should of selected 'Home Altitude'. Dooh....I think I'm good to go now.
Impressive results! Thanks for sharing.
A few questions:
The distances you refer in bottom left corner: Does it mean distance between minimOSD and APM? (4 inches seems far enough)
Did you use copper foil all around minimOSD, or just as a barrier between OSD and APM?
Are you grounding the foil?
Could you post a picture?
Does this seems like an interrogatory? :)
Didn't mounted yet my minimOSD in my quad rebuild but I'm certain I'll consider your approach. Maybe I'll be using aluminium foil instead of copper.
Distance to the APM has no effect on the apm - it's the distance between the mosd and the receiver that matters the two have to be separated as far as possible. The issue a lot of UHF users were running into was that their UHF control was dropping dramatically like getting cut by 50%...and all kinds of things were being done to isolate the circuits from the receiver lines which helped but didn't solve it altogether. It's just like everything else - every little bit you do helps overall.
The rise in noise floor likely explains my near field failsafes - I was gettign control lockouts even on 2.4ghz at 800m LoS. I'll have to redo the distance runs once I get a box to put this mosd in.
Yes, ground the foil, simply solder a wire anywhere to foil and connect to the ground connection on your battery if that's accessible. That will bleed any energy it picks up from transmission sources...the effect is negligible as far as I can tell, but it's good practice anyway.
For this photo - all I did was put put a strip of foil between the 2 components. So I imagine when I encase it in a box lined with copper foil - the results will be much more dramatic.
I tried aluminum and it doesn't have the same reflective capability as copper. You need about 6 or 7 sheets to start seeing an effect - I stopped at that point because it was getting too thick to be useful, and I had copper tape handy.
I'll do some scans for you so we can figure out how many sheets it takes.
anyone maybe an idea why are two panels switching?
Great. Looking forward to see image of it placed and boxed
Thank you for your explanation.
Back to work ;)