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! :)
How is the brand name of you's video tx..??? Minim osd use 57000 to connect to a apm...but you use other pins for generate the 1800bps for the audio modem...omly need to solder a wire in the atmega pin..or redesign the mininosd...maybe atmega2560 or a new pcb board to pads available to solder a wire...I think mega328 is limited...
How you plain to use video telemetry?? Maybe lm1881 video sync???
Hey guys I thought I was mentioned something I came across today. When I was at the boundary of my radio limit on a mission, my APM went into failsafe mode. When this happened my OSD disappeared. When I came back into range my OSD appeared again and so on and so forth each time i went into failsafe due to loss of radio communication (i don't yet have RSSI setup on this rig). I thought there may have been a problem with the firmware because I had just gotten screen switching configured and working but later in the day it dawned on me that it might be the limits on the channel that I configured for screen switching. Sure enough, this was the case. I actually configured my screen switching to one of my potentiometer dials and when I go above 1200 the OSD is supposed to turn off. When I originally configured failsafe I had that potentiometer set above this mark so after a quick reset of failsafe on my receiver with the dial in the correct position everything works perfectly now. Just thought i would share as it was a bit nerve racking to see that happen in flight when i was at the limit of my radio gear. :)
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).
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! :)
Good catch Paul. I was going to give that advice when I got a couple sentences in but as I read further I obviously discovered you figured it out. I've had this happen as well and also have on the checklist now for every time I set up a new bird to make sure I put the switch to go to the panel that has GPS coordinates on it, so that if I do lose the aircraft due to failsafe and it doesn't make it home, and I am recording the FPV signal I can just check the video, plug those coords in to my phone and start heading that way.
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
OSD menu feature isn't there anymore :(
We had to sacrifice it in order to include other features.
We should update the wiki.
My Tx s
A new processor with more code space would be great.
Regarding video telemetry, yes I already have 2 LM1881 an arduino uno and some resistors, capacitors and a diode to do the tests.
You're absolutly right. Failsafes are one of the most important things to set when you have flight controllers.
Including throttle failsafe value (most important) and osd failsafe channel (unless you turn panel switching off :) )
Thanks for sharing.
"I like the if throttle > 15% continue timer else pause"
I already made that feature :) I'm just including some a tricky feature in fw before releasing it.
off-topic:I live in Almada. If you pass by let me know ;) I'll do the same if I go to Algarve.
I think those libraries in code google are faulty.
I'll post here the right ones.
It seems I'll never get my MinimOSD working :-(
I was out testing today and realised that I'm losing the overlay too. I've turned off all switching in the CT tool so it's not that, I simply lose the overlay but the video remains on screen. It seems it's related to telemetry and the only way I can get it to work again is to unplug the telemetry radio. I don't suppose anyone can help me resolve this, I've been trying various things all day and cannot get it to stay on the screen.
The odd thing is, if I test it inside with no GPS fix, theOSD remains on screen, if I take it outside not long after a fix the OSD disappears... Can anyone help?