Replies to This Discussion

Permalink Reply by Drone Savant on May 11, 2013 at 5:33pm

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/FlightBatt, http://code.google.com/p/minoposd/wiki/PacketRxOk

• ▶ Reply

Permalink Reply by Kevin B on May 11, 2013 at 6:47pm

Agreed & done. Apologies for taking my discussion OT.

• ▶ Reply

Permalink Reply by Wayne Holt on May 12, 2013 at 2:36pm

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

• ▶ Reply

Permalink Reply by Jerry on May 14, 2013 at 6:56am

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

• ▶ Reply

Permalink Reply by penpen on Saturday

is it possible to monitor a secondary voltage input ?

• ▶ Reply

Permalink Reply by iskess on Saturday

Unfortunately the APM doesn't allow for it.

• ▶ Reply

Permalink Reply by penpen on Sunday

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

• ▶ Reply

Permalink Reply by Dmitry Eliuseev on Sunday

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 

• ▶ Reply

Permalink Reply by iskess on Monday

It's been pretty quiet here lately. I'm about to prep the X8 for it first photogrammetry missions, and I was wondering where we are with the OSD firmware. What is the timeframe for a new stable release date for Arduplane? What bugs or features are still being worked on? Do you need more videos on the latest release candidate posted in the Downloads section?
Thanks for any update.
Keep up the great work.

• ▶ Reply

Permalink Reply by Miguel Pereira yesterday

Hi iskess,

Me and Gábor we're stuck on work this days :S

Also, I would like to make same minor changes in copter version before a stable release.

I may also implement some code savings in plane version (which are already in copter version) depending on Gábor's thoughts about that :)

However I had a crash a week ago which burned my APM 2.0 (PPM encoder dead) and my minimOSD.

I think it was a voltage peak, so I won't trust again in ESC's BEC and will use a UBEC instead.

Also a broken boom and a bent motor mount :(

Here is the video:

This is what happens when we want to test things fast and take risks (regarding wind speed in this case).

That said I have some work to do to put the quad flying again (and some investment to be done...). It's the painfull part of the hobby I guess :S

To all you guys that follow the development of minimOSD extra: Thank you very much for your thoughts and  feedback!

I will try to keep you posted about improvements. I think that in a week or two I will manage to fix that little issues I would like to fix.

Regards,

Miguel

• ▶ Reply

• ‹ Previous
• 1
• …
• 166
• 167
• 168
• Next ›
• Page