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:
Added:
- Changeable unit measurement (US, metric)
- Airspeed
- Home alt
- Battery Percent
- Battery used mah
- Current Draw
- Time From Startup (cleared at takeoff to show exact flight time)
- OSD Menu
- Variometer
- 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
- Temperature
- Smoothened horizon
- Real heading
- RSSI
- 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
Username: MinimOSD_Extra
Password: Top_Secret
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! :)
Enjoy
Replies
Hi Carsten,
The only problem creating custom flight modes in the main fw is that we're out of code space. So when we find some code improvements (which we still have to do) we prefer to include new features.
Also making a unique fw with custom flight modes for each flight controller will lead to a lot of entropy in code.
Your edited tip is a good one, thanks!
However we cannot make mode_str = osd_mode directly because are different types of variables.
The best implementation I tried for this will use 72 bytes of code space.
To have an idea, we are struggling to try to save around 100 bytes of code space improving existing code. So 72 bytes are "a lot" :S
Miguel
What warning voltage value do you usually specify use for 3S battery? It looks like my batteries lower the voltage on throttle or on full throttle, causing low voltage warnings start even after fresh start.
Hi Pavel,
It depends greatly on batteries performance.
An old / poor quality / low C rate, battery will lower voltage whenever there is current peak.
IMHO a good practice (my own :) ) is to use first a lipo alarm to learn how battery behaves.
I would start to set the alarm to 3.6V per cell. If you have a power module, after flight check how many mAh have been drawn from the battery. If you have more than, say 10% remaining battery capacity then lower the alarm setting by 0.1V so next fly it will trigger whenever a cell achieves 3.5V. Continue if needed (I believe not).
If you achieve a good point at say 3.5V per cell, then just set the osd alarm to the total voltage alarm of 3 x 3.5 = 10.5V (for a 3S lipo).
You always should keep in mind that a fast change in throttle may trigger the alarm.
Miguel
Hi Miguel,
I looked to the settings and it looks like I have there 10,1V alarm with 10% remain warn. level. Even when batteries are fully charged and during take off, I get voltage alarm triggered. That is interesting. Even the alarm is triggered and there is low voltage. Not sure if it is precise voltage measurement though. I use some cheapest PCB I found on eBay. It probably could measure fine if there is not load. I calibrated it with Voltmeter and Ampermeter. But the measurement is different if in load I think. So even the warning is triggered, then I can fly around 15 minutes or to fly about 10 Km up to 13 Km distance. Looks like I will need to do something with voltage measurement under load or to replace power and voltage measurement PCB with something more precise. Regards, Pavel
Hi Pavel,
In APM dataflash logs you may also check the voltage so you may decide which will be the best setting for you ;)
Miguel
any news about a new minimosd hardware (V2) or 32 bit so the developers can continue with programing new functions without messing around with the low resources?
Hi Peter,
AFAIK no news :(
We'll keep fighting against space I guess :S :)
Miguel
Sorry might be off topic, but a friend of mine says he has this cable : http://www.readymaderc.com/store/index.php?main_page=product_info&a...
Is that the same as a FTDI cable to program minimOSD?
Many thanks
I downloaded the latest version from the GIT yesterday and tried to verify a compile before I tinkered with a couple changes I wanted to make. On the verify/compile, I'm getting this error:
'apm_mav_system' was not declared in this scope
Any ideas?
Hi Miguel!
Before this gets lost just a bump up from my answer that i gave you.
Do you think you could implement this in the firmware?
BTW i'm also from Portugal(Algarve).
Obrigado! :)
I like the if throttle > 15% continue timer else pause.
That sounds like i winner!
The reset button works fine but you have to be near the quad. I would like to just go up in the air and the timer would start so that can give us an extra support to know more or less when to land.
Thanks for the great support and lovely firmware! :)
-
107
-
108
-
109
-
110
-
111
of 163 Next