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 came, and things started to happen fast. :D
He optimised the code and added even more things to it.
He worked hard on CT, and it became a great tool!
Thank you Pedro! :)
Also Burt & Eddie came.
They also worked on it and added many smart things to our firmware.
By now MinimOSD-Extra got a pretty advanced OSD.
Here it is in action:
- Changeable unit measurement (US, metric)
- Home alt
- Battery Percent
- Current Draw
- Time From Startup (Will be cleared at takeoff to show exact flight time in the next release)
- OSD Menu
- Wind horizontal speed and direction, and also vertical wind speed (Vertical wind speed will be in next release)
- OSD on/off
- Switchable secound screen
- WP distance
- WP heading
- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI
- Efficiency, glide distance & thermic notifier. 3 in one panel (Will be in next release)
- OSD Brightness (Will be in next release)
- HAM Call Sign (Will be in next release)
- After flight summary (Will be in next release)
- Trip distance (Will be in next release)
- Temperature (Will be in next release)
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.)
About the menu:
I made a menu inside OSD. You can enter this menu only after boot, the same way as screen switching works.
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.1
We are sharing it to see videos you make using it! :)
Thanks TC... I have removed my comments that have nothing to do with the thread. Perhaps Kevin can do the same. Like you I am simply on THIS thread for informative help re: minimOSD
After glancing at the code it does not seem to far fetched to think one could use a patch on panWarn() so that when the warn_next_timer is triggered we check for a *custom* warning message that is supplied as a character string. It appears that it would only need its own warning type and a way to populate the string.
I guess the other way would be to modify writePanels() and make a new panel type that was only visible IF custom input existed (kinda like the GPS data is handled).
I went back historically and a few people have asked for a way to do this in the past. I figured I would ask here before I tried to tackle it on my own. The problem right now is I am not sure what the best way to populate the string is. It would be nice if there was an extra pin on the microcontroller for a SoftSerial interface (or similar API).
My brain is already accustomed to borrowing spare pins because the way some of the minopOSD features work with this hardware. http://code.google.com/p/minoposd/wiki/FlightBatt, http://code.google.com/p/minoposd/wiki/PacketRxOk
Agreed & done. Apologies for taking my discussion OT.
OK all...I'm sure this has probably been addressed previously but I haven't found it. I'm having issues with the MinimOSD (latest firmware and all) and a GoPro Hero 3 camera (latest firmware as well). Here's the situation:
So there's my situation. I've come to the end of ideas on where to go from here. Any help or guidance would be greatly appreciated.
I'm sorry if this has been asked before, couldn't find it in the search.
The temperature is internal in the board right? Is there a way to add an external sensor besides the one 3DR sells? I have a few micro temp sensors from eagle tree I would really like to use. If anyone could help me out with some base code to work off of that would be tremendous!
is it possible to monitor a secondary voltage input ?
is it an hardware/conception limitation or can i modifiy the loop code in APM to read a free analog input with adc (or take one which i don't use) create and generate a new mavlink command (or take one already existing that i dont use in minimosd) and modifiy in minimosd code for custom draw/units ?
(i understand those stuff won't be editable from MissionPlanner)
or, as the rushduino impl for minimosd and multiwii or mniOPOSD impl, modifiying the minimosd hard and code to read an extra analog input
Thanks to MinimOSD Extra developers. Based on this code, I made version for YS-X4/X6
Details on rcgroups thread http://www.rcgroups.com/forums/showthread.php?t=1893795
Me and Gábor we're stuck on work this days :S
Also, I would like to make same minor changes in copter version before a stable release.
I may also implement some code savings in plane version (which are already in copter version) depending on Gábor's thoughts about that :)
However I had a crash a week ago which burned my APM 2.0 (PPM encoder dead) and my minimOSD.
I think it was a voltage peak, so I won't trust again in ESC's BEC and will use a UBEC instead.
Also a broken boom and a bent motor mount :(
Here is the video:
This is what happens when we want to test things fast and take risks (regarding wind speed in this case).
That said I have some work to do to put the quad flying again (and some investment to be done...). It's the painfull part of the hobby I guess :S
To all you guys that follow the development of minimOSD extra: Thank you very much for your thoughts and feedback!
I will try to keep you posted about improvements. I think that in a week or two I will manage to fix that little issues I would like to fix.