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)

- 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


- 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 developing version of copter is here: Link to Copter FW

And the latest Plane is here: Link to Plane FW

In bough version, the CT is included. (The FW and the character file is in the root directory)

We are sharing it to see videos you make using it! :)


Views: 154607

Reply to This

Replies to This Discussion

I am writing a custom efficiency function for MinimOSD-extra to give percent efficiencies for horizontal flight and climb. Doing so requires the units in the math to work. Can someone verify that I am understanding the units correctly? It is not obvious in the code, and I fear that I cannot assume that the units are all in MKS (so as to maximize the resolution in the MavLink message).

All the ints or floats are in OSD_Panels:

  • osd_alt_to_home: [meters].
  • osd_climb: [meters/second].
  • osd_airspeed: *not* meters/second - uses a 3.6 conversion for MKS units. Not sure what to make of this.
  • osd_curr_A: [cA] (centi-Ampres!). The display in Amps uses osd_curr_A*0.01.
  • osd_vbat_A: [Volts]

My approach is to calculate the energy of the plane (potential + kinetic), estimate the time rate of change of the total energy, divide by the power in, and then smooth the result. Thus, the units are important.

Any help would be appreciated!

Yes you have units correct, and they are all MKS except i. The 3.6 conversion factor is for m/s to kmh. ;)

Centi-ampers is kinda weird... maybe there wasn't time/room for a float?

Please keep us posted... I think a zero excess power meter would be cool! That should be useful for holding an efficient profile as you climb/dive.



Thanks for the reply. Yes, ceni-amps is weird. The header declaration for osd_curr_A has a comment that says osd_curr_A is in units of mA. However, OSD_Panels prints osd_curr_A*0.01. Odd.

Yes. I'm trying to have a concise method to compare power in vs cruise/climb power out. It isn't easy because I am trying to not use aerodynamic relationships (and have something more first-principle), and there isn't a lot of wiggle room to add lots of functionality (I'd like to conserve as much of the existing MinimOSD-extra as possible).


© 2014   Created by Chris Anderson.

Badges  |  Report an Issue  |  Terms of Service