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! :)
A character firmware (older one) is actually included in r800, its in the FW & Char folder called Character_Updater_FW.hex. No need to search for older one to use. Can be diffucult to know how old it has to be to be working too.
I think it was size dependent, Miguel or Gabor sure know the right size. But for newcomers it can be a trial and error thing.
So just load the Character_Updater_FW.hex, update charset, and then update to plane or copter firmware thats in the same folder.
I remember there was an old firmware that was made to take care of the streaks across the screen behind the text. Was this bit of code included in r800? If so what am i doing wrong as i have the streaks across my screen. My osd brightness is set to low.
Are there any plans to add support for functions in Minimosd with KVTeam mod, would like to monitor my second battery I use for my gimbal.
Please try the attached FW.
I did a very fast addition to normal battery voltage panel, just to see if it works.
After you have tested it we can step forwrd.
Great, I'll try do do a test tomorrow after work. Thanks .-)
any further progress on this?
Once this is tested will you be writing a "code" for Bat2 for the copter version?
I imagine a Bat2 addition to the R800 which is working flawlessly.
I know we are pretty close to the memory limits of the MinimOSD and thus the charset upload code was removed but perhaps after perfecting the Bat2 we can we add HDOP which is so needed to establish what kind of GPS signal we are getting on a particular day.....as we all know, number of satellites alone doesn't cut it!
Thanks for all your work and all the other developers....after all these years of hard work I believe we are pretty close to perfection of the MinimOSD.
He mentioned earlier but HDOP is indicated by the flashing satellite. Anything over 2.0 causes the GPS icon to blink so it's already included.
Yes, I am aware of that, however there is a lot more information that can be ascertained by knowing the HDOP.
Also, for the satellite icon to stop blinking on the OSD; the number is not necessarily 2.0
It is whatever you have set in the parameter list, the default happens to be 2.0 I have mine set at 2.3 for a few reasons but mainly because the performance with my GPS units are great to hold a position at 2.1 or 2.2. (with these numbers, though, I keep the copter close until it drops some) and I don’t want to wait the extra time it takes to go below 2 when at days, it lingers at about 2.2, 2.3 for a while before it drops. This is assuming I want to take off in position hold mode….or any other “navigational” mode.
Also, I would not do a long distance mission on a day where the HDOP stays around 1.8 -2.0 on an average and atmospherically speaking, there are days like this. This is asking for a GPS glitch.
There are many other determinations that can be concluded by knowing the differential between HDOP and the number of satellites. You can have a high number of Sat count but an unusually high HDOP which tells you one thing. And you can have a lower number of Sat but a low HDOP which tells you something else.
Besides, this you can compare the performance of different GPS units analyzing the differential between sat and hdop.
Yes, I know I can see all this in the mission planner, but if I don’t want to bring a computer or tablet to the field it would be extremely beneficial the see the HDOP on the OSD.
Need some help! I received 2x RCTimer v2.0 MinimOSD modules and proceeded to follow the instructions Bjoern posted below. "... just load the Character_Updater_FW.hex, update charset, and then update to plane or copter firmware thats in the same folder." My current problem is that I get "No Mav Data" showing on my display no matter what I flash.
I even swapped ports from Telem2 to Telem1 and cables but no improvement. What am I doing wrong?