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! :)
There shouldn't be any verification process that I am aware of, but space is very tight so I am wondering if the hex file is simply too big to be uploaded.
I tried many times to upload via the CT tools app, and finally gave up and successfully uploaded via Arduino.
I rebooted and tested another time and CT tools magically uploaded again.
However, the character set was messed up. Uploading the characterset resulted in errors time after time. I've put it to rest for today.
However, MinimOSD still displayed data with a number of formatting and character problems. I couldnt see where the battery2 voltage displayed, but I won't strain too hard until I know the characterset is fixed.
Buried in here somewhere is a disclaimer that with the latest version of Plane code you cannot update the charset due to size restrictions. I think Miguel said he had to rip that logic out entirely to fit something else in.
What you'll need to do is downgrade the Plane firmware, upload the charset, and then reupload your custom firmware. All your settings will be retained. I just did this on Sunday as a matter of fact for a friend.
Ah I've noticed the same over the weekend. I could only upload the char set if I downgrade first. Wow we need new hardware...!!
I am completely lost when it comes to SVN and how to download source code - well I can download code but its hard for me to find the location of the latest minimOSD-extra COPTER code
Can someone provide me a link to the latest SVN or a link inside this thread where I can download the latest Copter soucre?
Help is greatly appreciated
unfortunately I cant compile the code as well.
I got lots of errors in the MAX7456 code. Libraries are include - still no success.
If you found a solution please write me some tips so I can "upgrade" my MinimOSD as well ;)
Hey can you guys plz make downloads on your repo: code.google.com available. Inside the repo there are many branches, its confusing to know which is working, which is not quite ready and so on.
Here is a tutorial video I made for the EZUHF RSSI / Link Quality on the MinimOSD for APM 2.6 or Pixhawk
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:
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).
can anyone give me a link to the lastest plane release? The link in the first post is not working.