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! :)
It is opensource ;)
I referenced the old link as an example of why I and I'm sure others are frustrated with MinimOSD. Someone needs to either take down that link or update it to redirect them to the correct site location.
I tested version 2.2 and although it was stable, it was out of date with flight mode changes in Arducopter for me. So I was excited to try the MinimOSD-Extra but ran into a snag. After flashing character set and Firmware many different ways, I noted the outcome never changed for the better. The issue is that some of the functions were not updating or showing data received from my Pixhawk. At this time, I cannot list which one they are as I pulled them a couple months ago and refuse to try anymore until something is fixed or a better product is found. Don't get me wrong, I love the idea of having heads up data while flying FPV, but what's the point if the data is wrong or not updating?
There is no issue with it.
It is that you are having some kind of issue with your hardware. (Computer, Cable, OSD, noisy uBEC, bad connection, wrong wiring, etc...)
Might be your FTDI. I don't know. I would really have to see and try to be able to tell.
R800 really is a well tested stable version now.
You are having problems that have nothing to do with the FW.
For the hardware you use, we are not responsible for.
How could we? (Even if there was a specific brand, but all the different clones, cables, etc...)
Not even for the FW. I mean we are. This is something we worked on and handed over. But still, "responsible" is not a good word to use here, when you do something for others as a favour and for fun. Sure we want it to work well! ;)
We even help if someone asks for it. Sometimes people are even calling me on phone.
We did all this for fun and for our FPV friends here. Not for money.
We are like you. We are not getting paid for this.
We just simply made a better FW than shared it with others.
It is the same as; You have a good idea, you make a totally new code than sharing it with this community.
I also have my job, my family.
When i have time, i am here. Reading posts and helping people as much as i can.
This is what i really do here. Really sorry if it is not enough.
Also sorry that you gave it up. I think you should not have. Opensource hardwares are just like this sometimes. (Tere are many systems in the market "ready to fly")
I respect your decision. As you have already decided, i can't help.
I wish you good landings,
I'm willing to give the MinimOSD another try. Any recommendations on Hardware? Ie 3DR version, Hobby King's, something better?
I could also send you all my modules as I'm not sure if they work anymore or that I'm have a heck of time with them. Either way, I would like to get my FPV outfitted but just don't feel like throwing more and more money at what I feel is a moody hardware product.
The classic $10 witespy board is what I have and both worked just fine.
Hi all with the help of Gabor (Big Thank You) I solved my issue with not being able to update the character set on my Minimosd. All the time the problem was at my end and hardware related. My FTDI is a 3.3 volt unit and while this is fine for making changes in the screen panels it was not enough to power the board for a character set flash. So I applied 5 volts to the digital side of the minim and 12 volts to the analogue side and it flashed the latest character set correctly first time. The R800 firmware is working fine after a long bench test here this afternoon and displaying all the new modes that I needed. Once again thanks to Gabor and the other guys for their dedication to this project.
I did this once before and it was straight forward, but it was several versions ago so perhaps something has fallen off.. Nonetheless, here is how I accomplished it:
Leaving the OSD board hooked up to the video equipment, I hooked up the digital side to the ftdi cable as normal. In the Config Tool, under "Options" is a "Send TLog" menu item. What that does is replay the tlog through the digital side (which then gets overlaid on to the video) at 1x speed. It doesn't update anything in the CT panels, it only operates on the chip itself.
Again, I don't know if this is still working, buts its how I did it a while back. Curious if you try this (if you haven't already!) and hearing if it works or doesn't work.. Good luck either way!
The no mavlink message was fixed for me when i updated the parameters in the mission planner.