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! :)
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.
I have MinimOSD Extra Copter 2.2.hex installed. Running from telem1 port I have a 3dradio in telm2 When mission planner connected i can see voltage and amp from my pixhawk. Looking at osd it reports 0 for both along with some of the other onscreen info has 0 for the value.
I've loaded R800 and it works fine. I had trouble getting RSSI to work on other software releases. 2 questions/comments. I have RSSI configured and it works but I get 2 percent (%%) signs after the number. Doesn't matter what the number is. The 2nd item is saved OSD config files. I can save them but get a read error if I try load them back in. Any ideas?
The hardware I'm using is a Pixhawk with EZuhf Rx.
Thanks for the great work you've done.
Ok, I need help. Yesterday, my minimosd worked perfectly fine. I decided to learn how to change stuff with extra using the osd configure. After hours and hours of trying all different firmware (original worked just fine as it was) I absolutely can not get the osd to read properly. I have stuff scrambled all over, weird characters, etc. I uploaded the R800 firmware and uploaded the characters included in this download. Here is a screen shot of what I have programmed into the osd configurator, and also a link to my DVR recording of whats actually on my video feed. What is wrong here??
Hi Itzik.....Have you managed to get your Minim to work properly yet?
I have a clone which had the same 'failed to talk to bootloader' message.
I found that if the 'video in' and 'video out' pins are disconnected from the board, I can configure the thing fine. If connected, I get the message.
I couldn't get the thing to work at all with the analogue and digital sides seperately powered, so I soldered the pads and power the board with a dedicated 5v Ubec. Only the Rx lead is connected from the APM telemetry port to the Minim OSD. The quality of all the connections seems to be very important, especially on the video side, so I have soldered those to the board.
Works perfectly now. Thanks to all those clever people who put this together!
I know you have very little time, so it'll be short.
I have been watching this project for a while. It is a very nice idea, it works, almost everyone with APM who's FPVing needs it, and lots of people are interested.
There are problems though:
- this page contains both updates about bug fixes and new releases and troubleshooting efforts involving users and the developer, all mixed together. There is no efficient way to search through this.
- The google code project still serves old versions of the firmware. New versions circulate in forums, and are commited to the project, but there is no indication between stable and semi-stable and bleeding-edge.
- In order to install a different charset, one has to dig in a few places, gather the appropriate files (answering questions like: which charset works with which firmware, and which other firmware needs to be uploaded first (in the plane version) to upload the charset?) and complete the process.
So, now that Google Code is closing down, I suggest that you/we use this opportunity to rebuild the organizational part of the project. Our target should be to make it:
- easier for users to find what they need and get it working
- easier for developers to collaborate and commit code
- more efficient (and easier) to help people. If the instructions are continuously improved (in a wiki page), less questions will come in from users in dispair.
I am more than willing to help you achieve this! We can start a github project, transfer all the code, setup branches (e.g. for smaller charsets, plane vs copter etc) and copy over the wiki, page by page.
Please please please give this project another chance! I won't ask for much of your time.
Let me know what you think! We're on the same timezone after all :P
Wow this is great! they already did the wiki and all...
Thanks for the link, I'll keep tracking the project there then :)
EDIT: actually, I see that they still commit in the google code repo, but there a already newly reported issues in the new repo :P. I guess it will be all fixed when g code closes down in January..