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

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

          • Yep, I know that, but that did the trick for me I start thinking that the 5v from my ftdi adapter were not enough, or not enough amps were supplied.
            Edit: or should I say miliamps. Also check if your ftdi is 5v or the 3.3v version....
            • My ftdi is 3,3V.....

              http://store.3drobotics.com/products/ftdi-cable-3-3v

              • you need 5v FTDI, also make sure it is pure 5v as most of the double voltage 3.3v/5v will have selectable Vcc but the logic part is just 3.3v and for minimOSD you need those 5v.

                another thing I read on the forums is that some PC motherboards will not supply adequate voltage/current so maybe try a different PC?  

                • Eureka ....thanks Artem my ftdi is 3,3 v i have replace with 5v and all is all right 

                  Many thanks !

                  • no prob, glad to help! 

  • I have been able to sort out every MultiWii, OpenTx and OpenLRSng issue I have run into but I am completely stumped by an APM problem that should be no problem at all.

    My APM is flashed and configured, my MinimOSD is flashed and configured, both with the latest stable APM:Plane and MimimOSD Extra (for APM:Plane). No matter what I do I can't get the APM to talk to the OSD. I always get "No Mav Data".

    I have googled everything anywhere near this subject and tried it. Posted on RCG (they suggested all the stuff I had already found on Google).

    The only clue I have is the "Enable Telemetry" Button in advanced setup is grayed out and I can't click it.

    I have tried every wiring combo with the TX and RX wires.

    I know that there will be no Mav Data sent with the USB hooked up.  I have tried various startup and restart methods.

    In updated the SR1 parameters with a list of known good SR3 parameters.

    I have cleared both eeproms and started from scratch

    No matter what I do I keep getting "No Mav Data" on my monitor.

    Any Ideas?

    • It will be to do with you setting your APM to 19200 baud for OpenLRSng (I'm guessing) for your mavlink backhaul over your openlrs.

      The compiled hex's on the minimosd-extra site have the 57600 baud set, this is what minimosd expects.

      You will need to compile your own minimosd and set the baud to 19200 before you compile. 

      OR

      use this guys: http://84ace.com/?p=11

      This is for copter only - your Flight Modes will be broken (on your OSD screen) if you are trying to use a plane. I am currently figuring out how to compile minimosd to make a plane hex with 19200 baud

  • Is there any clue when the release will become available which solves the issue with the RSSI low/high values? Thanks!

    • Interestingly enough, currently the CT is locking the max high at 1790pwm, but my radio outputs 1793-1794.  Any attempt to plug a higher value in just seems to get overwritten. Will be excited to see that fixed when the guys get a chance.

      • Hi when i switch on armed minimosd freeze....

        config:

        tricopter fortis airframe

        minimosd copter firmware 2,2

        pixhwak 

        can you help me please?

This reply was deleted.

Activity