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 came, and things started to happen fast. :D

He optimised the code and added even more things to it.

He worked hard on CT, and it became a great tool!

Thank you Pedro! :)

Also Burt & Eddie came.

They also worked on it and added many smart things to our firmware.

Thank you!

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

- Current Draw

- Time From Startup (Will be cleared at takeoff to show exact flight time in the next release)

- OSD Menu

- Variometer

- Wind horizontal speed and direction, and also vertical wind speed (Vertical wind speed will be in next release)

- OSD on/off

- Switchable secound screen

- WP distance

- WP heading

- Warning messages for Lost GPS fix, Stall, Overspeed, battery volt, battery Percent, RSSI

- Efficiency, glide distance & thermic notifier. 3 in one panel (Will be in next release)

- OSD Brightness (Will be in next release)

- HAM Call Sign (Will be in next release)

- After flight summary  (Will be in next release)

- Trip distance (Will be in next release)

- Temperature (Will be in next release)

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.)

About the menu:

I made a menu inside OSD. You can enter this menu only after boot, the same way as screen switching works.

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.1

We are sharing it to see videos you make using it! :)

Enjoy

Views: 51815

Reply to This

Replies to This Discussion

Gabor I have a question. Would it be easy to add code that allows for the warning interface to be used to display a few lines of text that are fed from one of the extra / available pins (or via the serial interface) some how? 

I use the minoposd variant that extends upon your code - http://code.google.com/p/minoposd/ with my OpenPilot gear. My question should be universally beneficial to any project based on the extras functionality. 

What I had hoped to do is interface with some code that I have running on a small linux box that is capturing ADS-B packets from both a GNS 5890 http://www.gns-gmbh.com/index.php?id=238&L=1 and a MicroADSB stick http://www.microadsb.com

The code puts both devices into their proper modes and begins querying them for ADSB frames: 

ruby ADSB_USB.rb /dev/tty.usbmodem1d1341
We got the proper response from the device. Assuming either SPRUT or GNS based firmware
GNS 5890 ADS-B Receiver
adsbPIC Version: 128
*58A05ED17C17E9;
*58A05ED17C17EA;
*5DA4DAB6F3FA22;
*5DA4DAB6F3FA25;
*5DA4DAB6F3FA21;
*02E19498FD1CD7;
*5DA4DAB6F3FA22;
*5DA4DAB6F3FA22;
*02E19498FD1CD7;

I simply pipe the packets to a slightly modified dump1090 that runs in net mode (and archives them to an sqlite db among other things)

$ ./dump1090 --net-only --aggressive
Net-only mode, no RTL device or file open.

decodeModesMessage()
msgtype: 11
decodeModesMessage()
msgtype: 11
*5da4dab6f3fa21;
CRC: f3fa21 (ok)
Single bit error fixed, bit 53
DF 11: All Call Reply.
Capability : Level 2+3+4 (DF0,4,5,11,20,21,24,code7 - is on airborne)
ICAO Address: a4dab6

decodeModesMessage()
msgtype: 11
*5da4dab6f3fa21;
CRC: f3fa21 (ok)
DF 11: All Call Reply.
Capability : Level 2+3+4 (DF0,4,5,11,20,21,24,code7 - is on airborne)
ICAO Address: a4dab6

decodeModesMessage()
msgtype: 0
bruteforceAP()
*02e19498fd1cd7;
CRC: fd1cd7 (ok)
DF 0: Short Air-Air Surveillance.
Altitude : 32000 feet
ICAO Address : a4dab6

decodeModesMessage()
msgtype: 11
decodeModesMessage()
msgtype: 11
decodeModesMessage()
msgtype: 0
bruteforceAP()
*02e19498fd1cd7;
CRC: fd1cd7 (ok)
DF 0: Short Air-Air Surveillance.
Altitude : 32000 feet
ICAO Address : a4dab6

I'd like to start pumping ICAO address, altitude and distance of any nearby aircraft in relation to my current GPS location out onto my minimOSD. 

I was pleased to see this stuff pop up http://diydrones.com/profiles/blogs/ads-b-decoding-on-an-ar-drone as I have been on this in parallel for quite some time. We just need to get this data piped onto our OSD's !

Hi All,

This has been a good, informative thread and I do not want to have to close it because of politics. As DS has said, start a new thread to address the political aspect of drone safety and the media. Please lets continue to just address the MinimOSD in this thread.

Regards,

TCIII Admin

Thanks TC... I have removed my comments that have nothing to do with the thread. Perhaps Kevin can do the same. Like you I am simply on THIS thread for informative help re: minimOSD

After glancing at the code it does not seem to far fetched to think one could use a patch on panWarn() so that when the warn_next_timer is triggered we check for a *custom* warning message that is supplied as a character string. It appears that it would only need its own warning type and a way to populate the string. 

I guess the other way would be to modify writePanels() and make a new panel type that was only visible IF custom input existed (kinda like the GPS data is handled). 

I went back historically and a few people have asked for a way to do this in the past. I figured I would ask here before I tried to tackle it on my own. The problem right now is I am not sure what the best way to populate the string is. It would be nice if there was an extra pin on the microcontroller for a SoftSerial interface (or similar API). 

My brain is already accustomed to borrowing spare pins because the way some of the minopOSD features work with this hardware. http://code.google.com/p/minoposd/wiki/FlightBatthttp://code.google.com/p/minoposd/wiki/PacketRxOk

Agreed & done. Apologies for taking my discussion OT.

OK all...I'm sure this has probably been addressed previously but I haven't found it.  I'm having issues with the MinimOSD (latest firmware and all) and a GoPro Hero 3 camera (latest firmware as well).  Here's the situation:

  • Had OSD working properly with Hobby King camera prior to buying the GoPro
  • I've now installed the GoPro but I get no video from it.  I can see the OSD information but no video from the GoPro.
  • I am using a proper USB to composite cable for the Hero 3 (i.e. the 10-pin mini USB)
  • I can get video out of the GoPro if I go directly from camera to a video display device such as a computer (in other words...I've verified that the USB cable works properly)
  • I've updated the OSD firmware and character set a couple times now...no change.
  • I'm powering the OSD and transmitter from a dedicated power supply at exactly 12 volts
  • I'm not sending power to the GoPro but I am sharing the ground with the OSD and transmitter
  • I've tried bypassing the transmitter and sending OSD and video directly to the display device via hardwire connection...no change.
  • I've turned on the Hero 3's wifi while connected to the OSD just to see if I can get video from the camera that way.  Video feed over wifi is successful.
  • Here's the most interesting symptom...If I slowly decrease the voltage I provide the OSD from 12 volts down to ~9.5 volts, I can get the camera video to sporadically appear.  Sometimes it takes the place of the OSD overlay and sometimes it is combined with the OSD overlay...just depends on the voltage I send the OSD.  So....it's acting like the OSD is just plain overpowering the video signal from the camera.
  • The OSD and the camera are both set to NTSC video standard

So there's my situation.  I've come to the end of ideas on where to go from here.  Any help or guidance would be greatly appreciated.

Cheers,

Wayne

I'm sorry if this has been asked before, couldn't find it in the search.

The temperature is internal in the board right? Is there a way to add an external sensor besides the one 3DR sells? I have a few micro temp sensors from eagle tree I would really like to use. If anyone could help me out with some base code to work off of that would be tremendous!

Thanks!

John

Hi Jerry,

The temperature is the one sensed by the barometric sensor in APM. It's warmer than outside temperature because of all the electronics around it.

I see at least three possible ways to achieve that:

1 - Make a custom APM code, reading one of the auxiliary ports available in APM, and then send temp sensor data via the mavlink frame (overwriting actual one).

2 - Hardware hack! Get an available pin input in the minimOSD (not sure if there is one). Personally I don't like this one.

3 - Use a external processor between APM and minimOSD (maybe an arduino pro mini?), so you can read the sensors data, capture the mavlink, overwrite the temperature parameter in mavlink message and send it to the minimOSD.

That will be time consuming developing that, but I think it is doable.

Regards,

Miguel

is it possible to monitor a secondary voltage input ?

Unfortunately the APM doesn't allow for it.

is it an hardware/conception limitation or can i modifiy the loop code in APM to read a free analog input with adc (or take one which i don't use) create and generate a new mavlink command (or take one already existing that i dont use in minimosd) and modifiy in minimosd code for custom draw/units ?

(i understand those stuff won't be editable from MissionPlanner)

or, as the rushduino impl for minimosd and multiwii or mniOPOSD impl, modifiying the minimosd hard and code to read an extra analog input

Hi all.

Thanks to MinimOSD Extra developers. Based on this code, I made version for YS-X4/X6

http://www.youtube.com/watch?v=gmqjYyZUFG8

Details on rcgroups thread http://www.rcgroups.com/forums/showthread.php?t=1893795 

Hi Dmitry,

Thank you very much for your video feedback.

Regards,

Miguel

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service