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.1
We are sharing it to see videos you make using it! :)
Does not work again. I use RFD900 modems, if this make a difference.
Any ideas about this issue?
Normally video RSSI is only available at the ground station, unless you uplink it to the aircraft, which would be insane. Adding an OSD board to your the composite video line on your GCS monitor would make more sense. If I was doing that, I'd probably modify KV-OSD code, because it's already setup to make use of the spare analog inputs. If I had to buy a second minim board for this, I'd probably get the new one from rtfquads; it has those spare analog inputs broken out to pins.
Like Miguel mentioned, all the info may be more distraction than help. Also consider that as your VRx loses touch, sound starts to hiss before you see any static, and even then light "flyable static" will warn you before your video falls off the cliff.
I built some video RSSI dot bar displays using LM3914 chips a while ago. The color coded LEDs were quite obvious taped to the inside of my monitor shade, but I still found it of little use. For example when I fly 5.8 around the corner of a building, video might drop instantly with no RSSI, static, or audio warning. In that case only pilot instinct or a solid RTL will save it. Flying farther out in the open, my audio always hisses just before I start to see video static. Everytime I heard the hiss, video RSSI would be at the point where the red <30% LED's would light up... for me that's time to turn back home. So I ditched the VRSSI display and go off of audio hiss instead.
In the end, you just have to get used to the feel of video piloting, know where trouble lurks, and how to get out of it. On screen info rarely saves a crash. Besides, you'll be surprised at just how dodgy those RSSI numbers can be anyways. If a number randomly jumps from 100-0 all the time with no apparent effect on the pilot, the pilot will start to ignore the info, and then it becomes a distraction. Honestly in my years of flying FPV, I have learned that RSSI is far less important than maintaining situational awareness. Not saying this will be the case for you... just giving friendly advise. :)
Wouldn't telemetry/video RSSI be redundant? RX RSSI is important because a weak signal will cause loss of control. You should do some field tests to determine at what point (RSSI) the signal becomes too weak to control the aircraft; then always stay within range as indicated by the RSSI.
A weak telemetry/video signal will fade and start to break up. You will be able to see there is a weak telemetry/video signal by the degradation of the video! Therefore an RSSI on the video/telemetry is redundant with the ability to determine signal strength by video quality.
Telemetry rssi and video rssi are two different signals.
I agree with you regarding video rssi redundancy.
Regarding telemetry I think it could be usefull.
For example one may have GPS coordinates panel disabled in osd to have a less populated screen and get that info from ground station.
When you see on osd that telemetry rssi goes low you know that your ground station is beginning to lose info about your model location. Side not: Telemetry link may be completly broken but you still have osd live data as APM keeps sending data via that link.
Oh that's right! I forgot some people are using a separete telemetry link over 433mhz(EU) or 900mhz. I don't use a separate telemetry link, since the OSD carries all the real-time telemetry data I need for FPV, and logging contains all the data I need for post flight analysis. In addition, for setup and testing (within 15ft of my PC), I do use the telemetry over Bluetooth with MissionPlanner.
That's it Thomas, telemetry link over 433Mhz in my quadcopter :)
Gábor uses the same bluetooth method as you, and my goal is to follow your approach in my FPV plane build.
Great FPV flights! And videos if possible ;)
I am now using for my project http://diydrones.com/forum/topics/osd-for-frsky-smart-port-telemetr... svn r780 and CT pre-release r727 with MinimOSD_18.104.22.168.mcm.
The chars 0,1,2,3 are very blurry, also some letters. Can somebody tell me what version shoud I use, what CT and mcm ?
Never mind. While updating, I pluged in 12v and it updated the font.
Gabor, if you find another 180bytes or so on that chip, would it be possible to add estimated range? It would be great to know what the estimated range would be at the current Amp draw & speed, almost like a car. Of course wind need to be factored in by the pilot. Just a suggestion.
You may want to have a look at the Efficiency panel Hein, it's pretty awesome:
Maybe not exactly what you were after, but a pretty powerful panel once you memorize it.
Thanks Josh, I'm aware of that panel, maybe I should use it more!