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 understand... and I know what you mean, sudden drops will not register etc.
But having the reading fluctuate 0.5V, even when the vehicle is on the ground, makes it very difficult (at least for me) to use it. I'd gladly give up the responsiveness to get a useful reading. I don't like doing math (gathering samples and averaging) while flying... I think most people would just want an easy, clear reading.
I explained it in the issue too:
It is very important (at least for me) to get a readable, easy to understand value when flying, without having to average out values in my mind. I believe this improvement will give a more "professional feel" to the OSD and consequently APM, as the stable readings give a feeling of reliability and dependability, at least for me.
What do you think? Are sudden voltage drops so much of an issue?
What do others think?
I agree, however when you are flying for example fairly quickly you want to be able to see your battery level at a glance you dont really want to be taking more than a fraction of a second to look at it or it becomes distracting i find. However on the flip side if its the low voltage you are worried about then the warnings tab does this just fine :)
Steven G, .5V will always make a difference. What do you consider a safe voltage to stop flying a 3S at? 11V? Ok, then you have to make a rule for yourself to stop flying when the voltage shows 11.5. Ok.
But the reading being inconsistent, it may show 11.5 but the real voltage be 11.8. Isn't it a pitty to lose all that flight time?
Robert, the warning tab is based on that reading, right? So when battery dips to 11.5 for a second, when it's really 11.8 or 12, the warning will go off.
I guess I just can't see a situation where sudden voltage drops will help you diagnose something and get out of trouble in time. I can imagine scenarios but they are all very highly unprobable to happen.
Yes, RSSI is radio-related, and that changes very rapidly. But still, it's only for a few percentage points, like 5%. Battery voltage has a much narrower range (9 to 12.6 V for a 3S, extreme values) so a fluctuation of 0.5V is about 13.9%. If you only use 10.5 to 12.6V like I do on 3S it's 23.8%!
But really, how much does your voltage reading fluctuate?
is there a chance that this project will move to GitHub?
I think its a great place for bug reporting and develop diskussions
Keep up the great work
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