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

Normally video RSSI is only available at the ground station, unless you uplink it to the aircraft, which would be insane. Adding an OSD board to your the composite video line on your GCS monitor would make more sense. If I was doing that, I'd probably modify KV-OSD code, because it's already setup to make use of the spare analog inputs. If I had to buy a second minim board for this, I'd probably get the new one from rtfquads; it has those spare analog inputs broken out to pins.

Like Miguel mentioned, all the info may be more distraction than help. Also consider that as your VRx loses touch, sound starts to hiss before you see any static, and even then light "flyable static" will warn you before your video falls off the cliff.

I built some video RSSI dot bar displays using LM3914 chips a while ago. The color coded LEDs were quite obvious taped to the inside of my monitor shade, but I still found it of little use. For example when I fly 5.8 around the corner of a building, video might drop instantly with no RSSI, static, or audio warning. In that case only pilot instinct or a solid RTL will save it. Flying farther out in the open, my audio always hisses just before I start to see video static. Everytime I heard the hiss, video RSSI would be at the point where the red <30% LED's would light up... for me that's time to turn back home. So I ditched the VRSSI display and go off of audio hiss instead.

In the end, you just have to get used to the feel of video piloting, know where trouble lurks, and how to get out of it. On screen info rarely saves a crash. Besides, you'll be surprised at just how dodgy those RSSI numbers can be anyways. If a number randomly jumps from 100-0 all the time with no apparent effect on the pilot, the pilot will start to ignore the info, and then it becomes a distraction. Honestly in my years of flying FPV, I have learned that RSSI is far less important than maintaining situational awareness. Not saying this will be the case for you... just giving friendly advise. :)

Replies

- Gábor Zoltán > Hein du Plessis April 14, 2014 at 1:13pm
  
  Hi,
  
  I have tought of this. Like if you have just enough battery to get home level, than it would display 1.
  
  If you have twice as much than 2, etc.
  
  Atm. if i have free time i buildd my new plane. But after i will do this i think. :)
  
  Gábor
  - Miguel Pereira > Gábor Zoltán April 15, 2014 at 3:46am
    
    Hi Gábor,
    
    I recall well talking about this. In copter would also be cool, however needing another estimation algorithm.
    
    Should I finish my FPV plane and help with this one? (some many features ... so little time ...) :S :)
    
    Miguel
    - Gábor Zoltán > Miguel Pereira April 16, 2014 at 2:08pm
      
      :)
      
      Well for me now, the first is to finish my plane. It turned out much more work than i have expected.
      
      Than will make a mavlink based smart switch for my camera, and GPS tracker, than will be back working on OSD again. :)
      
      1-2 weeks i think.
      
      Gábor
- Josh Welsh > Hein du Plessis April 11, 2014 at 4:15pm
  
  You may want to have a look at the Efficiency panel Hein, it's pretty awesome:
  
  https://code.google.com/p/minimosd-extra/wiki/Pan_efficiency
  
  Maybe not exactly what you were after, but a pretty powerful panel once you memorize it.
  - 100KM
    
    Hein du Plessis > Josh Welsh April 11, 2014 at 10:34pm
    
    Thanks Josh, I'm aware of that panel, maybe I should use it more!
RazvanS April 11, 2014 at 10:09am

Hello,

I am now using for my project http://diydrones.com/forum/topics/osd-for-frsky-smart-port-telemetr... svn r780 and CT pre-release r727 with MinimOSD_2.4.0.0.mcm.

The chars 0,1,2,3 are very blurry, also some letters. Can somebody tell me what version shoud I use, what CT and mcm ?

Thank you.
- RazvanS > RazvanS April 11, 2014 at 11:05am
  
  Never mind. While updating, I pluged in 12v and it updated the font.
Anton April 10, 2014 at 11:38pm

Hi.
Can anyone tell me is there a feature to display the RSSI of the APM telemetry and maybe some other RSSI. In my case I use three RF systems - one for servos, one is APM telemetry and video. It would be comfortable to see all three RSSI of each RF system. And in present I can set the RX RSSI only.
- Kevin B > Anton April 11, 2014 at 10:23am
  
  Normally video RSSI is only available at the ground station, unless you uplink it to the aircraft, which would be insane. Adding an OSD board to your the composite video line on your GCS monitor would make more sense. If I was doing that, I'd probably modify KV-OSD code, because it's already setup to make use of the spare analog inputs. If I had to buy a second minim board for this, I'd probably get the new one from rtfquads; it has those spare analog inputs broken out to pins.
  
  Like Miguel mentioned, all the info may be more distraction than help. Also consider that as your VRx loses touch, sound starts to hiss before you see any static, and even then light "flyable static" will warn you before your video falls off the cliff.
  
  I built some video RSSI dot bar displays using LM3914 chips a while ago. The color coded LEDs were quite obvious taped to the inside of my monitor shade, but I still found it of little use. For example when I fly 5.8 around the corner of a building, video might drop instantly with no RSSI, static, or audio warning. In that case only pilot instinct or a solid RTL will save it. Flying farther out in the open, my audio always hisses just before I start to see video static. Everytime I heard the hiss, video RSSI would be at the point where the red <30% LED's would light up... for me that's time to turn back home. So I ditched the VRSSI display and go off of audio hiss instead.
  
  In the end, you just have to get used to the feel of video piloting, know where trouble lurks, and how to get out of it. On screen info rarely saves a crash. Besides, you'll be surprised at just how dodgy those RSSI numbers can be anyways. If a number randomly jumps from 100-0 all the time with no apparent effect on the pilot, the pilot will start to ignore the info, and then it becomes a distraction. Honestly in my years of flying FPV, I have learned that RSSI is far less important than maintaining situational awareness. Not saying this will be the case for you... just giving friendly advise. :)
- Miguel Pereira > Anton April 11, 2014 at 1:57am
  
  Hi Anton,
  
  There is even another RSSI on your system: telemetry remote rssi.
  Will you be able to process all that info while flying? :)
  I'm not planning to implement this because of space.
  However here is what I would do to implement what you're asking:
  
  If you have either radio rx rssi or video rx in pwm mode connect it in APM channel 8.
  The other rssi goes to the APM RSSI input pin.
  
  Changes in code:
  
  File OSD_Vars.h
  Add this variables
  
  uint8_t telem_rssi;
  uint8_t telem_rem_rssi;
  
  File MAVLink.ino
  Method read_mavlink()
  Add this in case block
  
  case MAVLINK_MSG_ID_RADIO:
  {
  telem_rssi = mavlink_msg_radio_get_rssi(&msg);
  telem_rem_rssi = mavlink_msg_radio_get_rssi(&msg);
  }
  break;
  
  File
  OSD_Panels.ino
  You'll need to show the 4 rssi values: chan8_raw, osd_rssi, telem_rssi and telem_rem_rssi
  The simplest approach will be to show them all via panRSSI method
  This way it's location will keep beeing settable via CT Tool
  
  Let me know if you need help implementing this.
  
  I'm not sure how much space will it require, but I guess you'll need to remove one or more other panels that you don't use.
  
  Miguel

of 163

This reply was deleted.

Discussions

Adding extra functions to MinimOSD

Replies

Activity