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 agree. DIYDrones' "forum" is ridiculus. shows 5 posts per page, you can't search in a "thread" etc etc...
IMHO we shouldn't average battery voltage for a couple of reasons:
1 - Hides sudden drops as refered by Gábor
2 - More code space spent on a almost full program memory platform
3 - We have other "averaged" battery indicators:
Battery percentage is a "fuel gauge" indicator. If it is set correctly setting in MP the mAh that effectively battery charger charged the battery it will give a very reliable indicator. Obviously we should also be sure that all the current and voltage MP parameters are set correctly.
The low voltage warning is also a voltage averaging indicator since it may be triggered by a sudden drop (low probability) but then the warning disappears.
For a FPV flight I believe we should keep the eyes on the "primary six" indicators (as real aviation does):
Airspeed (critical for planes)
Attitude indicator (horizon panel)
Course deviation indicator (Real heading panel) mostly for coordinated turns
Heading (or maybe Home Arrow panel for FPV)
Climb rate (vertical speed panel)
This is why I think that battery level indicators are important but as warnings.
Nice to read all the input :)
Yes we're moving to github.
Gábor is working with 3DR guys on that move to 3DR gihub repo
The move is taking some time as we have been very busy in our professional / personal lives :S
I hear you!
Thanks all for your replies. I'll start using percentage/capacity used more then. :)
We all have our desirements. That said, the current hardware is limited in capacity.
For me, if I had to pick a bare minimum, they would be; Speed, Altitude, Bank Indicator (turn coordination indicator is fine but not essential for me) and lastly, our "gas gauge" mAh used/remaining.
One day, someone will come out with a color, hi res, very customizable minimOSD but for now, our $10-14 little guy brings me happiness.
I'm using the charset and firmware from 2012.
The problem is that I can see all characters in my goggles, on the monitor I'm losing the edges.
I try to upgrade the miniOSD, I've upgrade the config tool to 184.108.40.206.
I use it to upgrade the firmware and charset (MinimOSD_Extra_Plane_R800).
It didn’t work for me. Instead of the horizon line I got lot of GPS look symbol, and the other is only a mess.
Is there 1 solution to both problems?
How do I upgrade the OSD?
There is a smaller glyphs charset?
There I a Beta version to check?
Yes there is a solution as this is exactly what happened with me, a couple of pages back is my solution. What is happening to you is that even though the CT is saying that the Character Set has updated correctly it has not. Once you correctly update the Character Set all will be fine. R800 works great for me on a clone Minimosd.
No, my problem looks to be different:
As I say, I've upgrade the firmware to MinimOSD_Extra_Plane_R800
When trying to upgrade the charset from the "FW & Char" directory: MinimOSD_220.127.116.11.mcm
I'm getting the message "Error entering font mode – no data"
That is normal.
You have to go back to the stable/old firmware(see downloads), load the new character set, then upgrade the firmware again to R800.