Thought the problem was a potentially faulty APM 2.6 so unwrapped my PixHawk. Same problem.
In MP, it connects and downloads the firmware. Pixhawk then gives the successful happy song. Select connect via Mavlink:
- starts 30 second countdown
- red connect changes to green disconnect
- timer goes to 0
- continues trying or doing something for another 1 1/2 minutes while countdown stays at 0
- then get No Heatbeat error.
In Windows 8, Device Manager, Com 5 is set to 115200, 8 bits, no parity, 1 stop bit, no flow control, FIFO buffers.
In MP, Com 5 PX4 FMU v1.6 (COM5) is selected.
- restarting the computer
- connecting via a different computer (windows 7 and an older version of MP)
- four different USB cables plugging into different USB connections (getting desperate)
- different com settings
I'm beginning to think i'm in a no heatbeat black hole. will see if i can setup the radio (but can i do that without mp?)
I believe mission planner needs to be set at 57600 on the port. Try this out because thats how i have mine connected.
57600 is just for the radio connection. A direct USB connection should 115200.
Forrest, the baud setting in the Windows Device Manager doesn't matter. What matters it the baud rate in MP. Are you sure that's set to 115200?
got it, thanks for the claity on that.
I agree with you. There should be no need to go into the Device Manager and manipulate the COM port settings. I have never had to do so to get a good MavLink connection with my Pixhawks.
TCIII ArduRover2 Developer
Hey Chris -
Turned out my problem was a bad mag in the GPS/Mag unit. It would connect until the mag wire was connected to the Pixhawk. Had a spare GPS/Mag, which worked fine.
Good detective work! Glad you got it sorted out.
Just as an update, I had this same problem on a friend's iris last week. I found this thread very helpful and I was able to resolve the issue without the need for a new GPS/Mag unit so I thought I'd share for anyone else who may experience this.
No heartbeat, couldn't connect, tried alternative 433 Mavlinks, still no joy. GCS Mavlink flashing green, iris mavlink solid green flashing red.
iris mavlink id 68 (on sticker - not connecting properly to Mission Planner...may have been my fault!)), GCS mavlink id 28 (on sticker). Confirmed GCS Mavlink id of 28, changed to 68...still no connection.
Checked Mavlinks, found that the one attached to the iris was in a constant bootloader state (solid red led) when directly connected via micro usb to pc - tried to restore to default which partially worked but wouldn't confirm finished on the mavlink itself by changing from red to green LED.
Removed GPS/Mag from Pixhawk to check if this made a difference, it did. iris mavlink after restore to default confirmed reset by changing to a green led. Net id25. Restored the GCS Mavlink to default, again net id25. Powered iris with a battery and connected to mission planner and confirmed mavlinks were working/talking...all OK.
refitted GPS/Mag connection on Pixhawk. Powered iris with battery and connected with mission planner. All working.
Seemed to do the trick and the iris has had a few flights, connected to mission planner with no probs...
Well, just to add to the mystery, our first attempt at disconnecting the GPS from Pixhawk and trying the Mavlink failed. My friend had disconnected from the GPS end and left the cable attached to the Pixhawk.
After removing the cable completely from the Pixhawk and also removing the i/o cable from the GPS, we were able to restore the Mavlink. Seemed it needed everything removed from the GPS connection on the Pixhawk. As to why, I'm clueless?!
If (big if) removing the cable completely had anything to do with it besides coincidence, then the reason is most likely a loose connection on the board that gets tweaked when messing with the connection terminal or a cable with an intermittent short.
That was my initial thought too and why I asked my friend to remove the cable from the Pixhawk, although there were no signs of issue wit the cable. In my head I was thinking something had shorted/tricked the mavlink into bootloader mode.
Whatever it was, I was just very pleased to be able to get the issue resolved without needing replacement parts and to get my friend flying his new toy.. and this thread was my only source of info for doing that.
I posted yesterday about this problem. I am glad I found this thread. I failed to mention in my problem that the Multi=color LED had never lit up but was hoping that happened after calibration... ANYWAY,
I disconnected the GPS uBlox Mag and the UBec power cord to the PIXhawk and well I'll be ! Success!
Looks like the GPS prevents connection with MAvlink at this stage of the set-up. I have not done any calibrations yet.
On to the next problem... heheh loving it though.