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! :)
one more detail, when the telemetry link goes down (in Mission Planner), the video image and OSD overlay image are continue to be good.
Where did you get an 800MHz telemetry radio? Or do you mean 900 (read 915)?
On the original OSD there are soldier jumpers to power OSD from APM.
I am having troubles with a new MinimOSD card : when the copter sits on ground everything is working great but as soon as I take off, the OSD overlay start to blink badly and randomly. Camera picture on the backgroud remains stable. Does anyone have already had similar problem ?
I am thinking of a dry joint solder somewhere but I don't know where to look.
Any help would be highly appreciated !
I gotta say thanks for posting that Peter. I'm about to move my dragonlink a lot closer to my OSD for CG purposes. Did you notice a difference in with noise before and after doing the mod?
I used to own a dragonlink and the OSD's switching regulator kills the range. You can see this for yourself by performing the micro power range test; one with the OSD on, and the other with the OSD off - you will see immediately.
Definitely do the 5v mod if you plan to use an UHF system.
I am using next module below which can be programmed to different 6 frequencies.
It was working very well for telemetry before rc7. I do not want to go back to previous FW, but to find why now those modules are affected by OSD.
My issues is that when I connect OSD, the telemetry link quality start to decrease progressivelly. When OSD is disconnected, then signal is 99%
On previous AC version (rc2) I was using telemetry with those devices at >500m without any issue.
I have a 3DR minimOSD and I did not see those jumpers.
I power the OSD from 2 different locations, as in diagram above.
Could you provide more details?
I have been having some character jumble issues after applying the recent copter update (R719) to a 3dr version 1.1 board and found a post on RCGroups stating that this version of the board has to have 12v (actually they stated that even 5v would work) applied to the video side of the board in order for the update to apply correctly. I have been using a 3dr V .1 version of the board and this version of the board does not need 12V applied to correctly apply the character update. I have the solder blobs connected on both versions of the board as I want to power the Minimosd in flight off of the APM.
My question is: Will having the solder blobs connected on the V 1.1 board cause a problem if I apply 12v to the video side to perform the update?
Steve, on a v1.1 with solder blobs installed, you should NOT hook up 12V. You should be able to update it with just the 5V attached. Just beware that this will require a decent amount of power from your USB; weaker USB ports/hubs may have problems with the update. If this happens, you can temporarily remove the blobs and attach 12V just for the update; then you can remove the 12V and reinstall 5V blobs before you fly.
Thanks Kevin... I thought this would be the case... I have updated this board many times before with the USB solder/blob technique but for some reason on this try I am getting a bunch of jumbled chars.