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! :)
I doubt it had to do with space honestly, it should just be a matter of the CT emulating telem from the autopilot. The minimOSD shouldn't be aware that its not really in the air..
I was afraid that was going to be your answer, because while I was writing my comments above, I thought I may have remembered trying it again at one point and being unsuccessful, but wasn't sure that it was my setup or something else.
Well crap, sorry man. There is definitely value in doing that for sure but it sounds like it won't work for a while.
Out of curiosity, why do you want to play it back on the MinimOSD? Is there something that's keeping you from doing it in Mission Planner or do you prefer the layout you created on the OSD? Maybe you're playing it back along with the video you recorded?
The MP HUD has most of the data, granted in a fixed layout. I'm trying to get a sense of why you want to do it with the OSD.
Okay, makes sense.
I'm not holding my breath for help. The past number of months tell me I'm on my own for this task. At least I took my head out of my a$$ and clued in of course the Tx isnt used on the MinimOSD/APM connection so I can use it for debug.
Maybe so, but the vector OSD wont display APM mavlink data - which doesnt help me.
Tlog send feature fixed.
All the feedback appreciated as always :)
Regarding charset update there are some options:
1. Boards that have separate powering:
They need 5V at telemetry connector and máx 12V at video middle pin connector
2. Boards that have shared powering (when connecting ftdi cable both leds (digital and analog) light on):
This boards don't need and shouldn't have video middle pins connected (with power) because that would mean two power sources powering the same circuit.
In this case if you have a 3dr ftdi cable you shouldn't have problems uploading charset as it has 5V power enough for both chips.
If you have a 3.3V ftdi cable (as a friend of mine) you should separate analog and digital powering so you can power video chip MAX7456 via the video middle pin (máx 12V). I'm not sure if it will burn osd by powering both sides without separating the digital and analog powering but it's not a best practice for sure.
Hope this help to clarify charset updating,
I just found out after two days head banging that with my Sparkfun 3.3 volt FTDI it was not enough to update the chararcter set even with the analogue side powered with 12v. 3.3 volts was enough to be able to read and send the config and panels to the Minimosd but was not enough to do the character set update. I had to lift the vcc pin from the connector and power it with an external 5 volts before it would work successfully.
Thanks for the feedback :)
I think this should really go to a troubleshoot page.
If you could, please post some videos of your osd working. Me and Gabor love to see it working and is a great way to catch some possible fw bugs.
I certainly will Miguel once I finish this build and our weather begins to get better I will upload any new video's to my Youtube site here:-
Am looking forward to flying with the APM and Minimosd.