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 am not a programmer. Sorry if I gave that impression.
I have seen that radar feature on the MinNaza project for the DJI NAZA so it can be done just has not been done for the APM/PixHawk. Maybe the developers can help you.
Nice picture of the Vector OSD. I wish the MinimOSD looked that good :-)
No I had not heard of witespy micro minimOSD or that it had more memory. No idea if that information is correct either.
I have not seen that problem Paul. I use FatShark Dominator goggles and have not see that problem but then again I am not running the R800 firmware or character set. Maybe some else has heard it. What goggles are you using, btw?
I am using Boscam GS 920 AIO goggles, but imho I don't think that is the issue.
The goggles only reproduce what they get delivered, or am I wrong?
I hope someone can help me, because I like the small characters in the R800 version ;-)
I download last F/W and now I have to press the reset every time I start the pixhawk
connect only Tx to the OSD
This is what i did
iskess thanks for your reply,at the moment the OSD connected direct to the monitor w/o the camera. but now I tried to upload the firmware 24R719 with CT Tool 2.4.0.01 but it stuck in 94%
A friend and I have been struggling setting up an RCTimer OSD with minimosd-extra and a fatshark TX. We were getting a lot of bleeding of the characters to the point of it not really being usable due to the obstruction of the video feed. However today we solved it. It took changing the source code to do it. We had to disable the automatic OSD black level control (register 6C) and then it was perfect. It might be useful to add an option to the config program to be able to enable and disable the automatic black level control.
The "stuck problem" solved by replacing the FTDI and upload the minimosd extra_800. the "reset problem" solved by change parameter BRD_SER2_RTSCTS=0
I've tried the 150ohm resistor - it removes the flickering but makes the image very dark, so I can't recommend this to anyone else.
I can't believe there's no fix for this!
Just wondering if anyone here can potentially help me, i have a quad running APM2.5 with Arducopter 3.2.1, i have a minimOSD flashed with R800 and 3DR radio telemetry module, these are connected with a Y cable (RX only on the OSD).
My APM is powered by a power module and the MinimOSD has the solder tabs joined so is running 5v across the board.
If plugged in direct to the APM with both Tx & Rx connected the OSD functions completely normally...
If attached to the Y cable along with the telemetry radio the OSD boots up fine but it shows nothing but zero's for data, this stays the same if connected to Mission Planner (1.3.25) or not...
If attached to the Y cable but with the telemetry radio unplugged I receive 'No mav data!'
I have 'enabled Telemetry' within MP and also made adjustments to the settings of SR0 and SR1 and these seem to have made no difference.
Any ideas? I have tried searching without much luck?