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'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..
I am no expert here but is it possible that Trip Distance is not present in the version that you are using and what you are seeing on the screen is a remnant from some other firmware? I use the R800 version linked in this thread and it works just fine for me Trip Distance is there and works great.
I just installed R800 and started playing with minimOSD extra. Love it so far, but I found a couple of puzzling things. I'm using an NTSC camera/monitor and settings in minimOSD
I have an extra "dash" on the screen, not sure where it's coming from. See the red arrow pointing to it in this screen
If you also look at the 3 yellow arrows, you cam see that those three text boxes are not aligned consistently with the tool UI, below (that's the OSD file I used for the video capture above)
And here's the OSD file I saved...
I don't expect perfect WYSIWYG, but this seems like a bug that should be addressed. I can easily work around it (just move things by one box left or right), but it's confusing nonetheless and takes extra time to get things right