Adding extra functions to MinimOSD

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

I found a couple bugs.

When the Waypoint arrow points to the left, it gets replaced with the wrong characters.

Also, the altitude and airspeed error on the Tuning panel is backward from what is intuitive to the pilot. The numbers should be negative if the plane is too low/slow, and positive if too fast/high. In the image above it appears that the plane it 74ft and 8 mph below the targets. In the next image (below) you can see that is not the case. The plane is on the ground 199ft below its target takeoff altitude. This should be a negative number.

I would like to reiterate my request to have the Tuning panel broken out into two separate panels for Altitude and Airspeed. I would like to move the Alt error to be near my other altitude data, same for speed. Actually I wouldn't even use speed error since my target speed stays fairly constant on my flight plans, whereas my target altitude is constantly changing.

Gabor, where have you been? We miss you.

Replies

- Terry > iskess November 24, 2014 at 11:08am
  
  Yes, it's too bad. There hasn't been an official "stable" version for a long tine or even good documentation on what has been done. This had lots of potential but in has fizzled out probably because most of us are too busy to pursue it.
iskess November 13, 2014 at 12:13pm

I found a couple bugs.

When the Waypoint arrow points to the left, it gets replaced with the wrong characters.

Also, the altitude and airspeed error on the Tuning panel is backward from what is intuitive to the pilot. The numbers should be negative if the plane is too low/slow, and positive if too fast/high. In the image above it appears that the plane it 74ft and 8 mph below the targets. In the next image (below) you can see that is not the case. The plane is on the ground 199ft below its target takeoff altitude. This should be a negative number.

I would like to reiterate my request to have the Tuning panel broken out into two separate panels for Altitude and Airspeed. I would like to move the Alt error to be near my other altitude data, same for speed. Actually I wouldn't even use speed error since my target speed stays fairly constant on my flight plans, whereas my target altitude is constantly changing.

Gabor, where have you been? We miss you.
Merlin November 11, 2014 at 2:31pm

Hello,

can anyone give me a link to the lastest plane release? The link in the first post is not working.
- 100KM
  
  Hein du Plessis > Merlin November 11, 2014 at 9:28pm
  
  See 3 pages back, Bjorn has given a link to my same question: http://diydrones.com/forum/attachment/download?id=705844%3AUploaded....
  
  John, I don't think the SVN contains binaries?
  - John Hutchison > Hein du Plessis November 12, 2014 at 9:30am
    
    Only binaries it has are the config tool and updater. Would have to compile the firmware.
- John Hutchison > Merlin November 11, 2014 at 5:12pm
  
  I would try again. The svn and latest plane links work for me right now.
Lockhart October 23, 2014 at 8:36pm
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!
- Kevin B > Lockhart October 27, 2014 at 10:26am
  
  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.
  
  Kev
  - Lockhart > Kevin B October 27, 2014 at 11:30am
    
    @Kevin:
    
    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).
David m October 22, 2014 at 6:37am

Here is a tutorial video I made for the EZUHF RSSI / Link Quality on the MinimOSD for APM 2.6 or Pixhawk

https://www.youtube.com/watch?v=rh7-D96FIK0

of 163

This reply was deleted.

Discussions

Adding extra functions to MinimOSD

Replies

Activity