Waiting for Mavlink Heartbeats...

I seem to have a problem with my MinimOSD setup.

When I connect my MinimOSD to the APM2 board I get the following message: "Waiting for Mavlink Heartbeats". The message never goes away as far as I can tell.

 

My setup is as follows:

APM2 board bought new from the store here

MinimOSD board bought new from the store here

CMOS camera bought new from the store here

EagleTree Eagle Eyes ground station that I've used for about a year.

 

Everything seems to work flawlessly meaning that I can hook up the APM2 to the camera and an external power supply and receive video on my FatShark goggles connected to the Eagle Eyes. 

I am using 900MHz for my video feed and I am not using any of the XBee components.

 

I've searched the forums here and this is what I have done so far:

-I've downloaded the ARDUCam OSD configuration utility and through that I have updated the firmware and the character set.

-I've updated the APM2 board to the newest firmware (ARDUPlane 2.33) and I am using Mission Planner version 1.1.67 which is current as of this morning.

-I've gotten into the MP and downloaded the logs and then reset the board.

-I've followed this post on here and reset my values on SR3 to the ones shown: http://diydrones.com/profiles/blog/show?id=705844%3ABlogPost%3A752128&commentId=705844%3AComment%3A815747&xg_source=activity

-I've replaced the connecting cables in case I had a bad one.

 

So far nothing has worked other than I'm getting a really nice picture using this setup! :-)  No interference that I can see.  I'll even go as far as ordering a new MinimOSD but they're sold out right now so that's not an option.

 

Thanks for looking!  If it helps I'll send a candy bar to whoever comes up with a winning suggestion. :-)

 

-Mike

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

Join diydrones

Email me when people reply –

Replies

  • Ok, the basics are that the OSD boards (doesn't matter which "brand"), plugs into the same serial port from the ardupilot as your telemetry modem (Xbee, the new ones or any wireless bridge setup). The OSD board really only needs to receive, where the modem will both transmit and receive. The bottom line is that you screwed up the wiring. Whatever you connected is either shorting that serial out, and/or you did not connect the modem solution correctly.

    Both boards (OSD and Modem) more or less get connected in parallel with each other to the serial port. (Think like a y splitter). The OSD receives the exact same packets as mavlink thus you might not be getting any data on either one.

     

    See this thread http://diydrones.com/forum/topics/getting-params-sys-id-compid-id-e...

     Better thread: http://diydrones.com/profiles/blog/show?id=705844%3ABlogPost%3A5272... 

This reply was deleted.

Activity