When I try to connect using mission planner versions 1.1.51 & 1.1.52 I get a "No Heartbeat Packets Received" box after the time out.
I don't have this problem with 1.1.50, have I missed something.
I am using Windows Xp if that makes a difference.
Tags:

That did it for me Michael. APM1 1280, APC220. I also use your patch for "parameter spacing" (except % 2 works for me) over at http://www.diydrones.com/forum/topics/apm-mission-planner-with-apc2...
in gcs_mavlink.pde
// send out queued params/ waypointsif (NULL != _queued_parameter) {
static uint16_t count = 0;
if (count % 3 == 0) {
send_message(MSG_NEXT_PARAM);
}
count++;
}
Permalink Reply by Tom Evans on March 29, 2012 at 4:35pm I've been having the exact same problems with any MP above v1.50. I ran several tests with my apm v1.4 and ArduCopter-2.5.3 installed. always connecting via usb. See
http://www.diydrones.com/forum/topics/apm1-and-comms-issues-with-mp....
I've been working through my Hexa setup using 1.1.50 with no problems. But really don't want of be shut out of future MP updates.
BTW just say the post re: MP v1.1.56 which I will try for sure.......
Permalink Reply by estebanflyer on July 23, 2012 at 12:13pm Hi Michael, I have tried both options, but the mavlink connection through xbee doesn't work.
Mission Planner 1.1.99
Mavlink 1.0
APM 1
Firmware 2.6
It does connect through USB.
eteban: forgive me if you've already checked these things:
--Confirm that you've selected the right port for the Xbees and set baud rate to 57k in the MP
--Check that the Xbees are talking to each other, either through the X-CTU loopback or the Xbee test code here.
--Tried powering your APM board with an ESC instead of or in addition to the USB.
Permalink Reply by estebanflyer on July 23, 2012 at 12:39pm COM 4 is for USB (works)
COM 5 for xbee (doesn't work)
Baud speed set at 57600 for xbee in MP.
I am powering up the APM through an ESC.
Tom, the MP is now at 1.1.58. It should be updating automatically when you load. Is that not working?
Permalink Reply by Tom Evans on March 29, 2012 at 6:39pm Hi Chris
It's working OK -- I'm just gun shy of updating because I basically haven't had anything since 1.1.50 work for me. I will try 1.1.58 tomorrow for sure.
Permalink Reply by Roelof Versteeg on July 19, 2012 at 2:34am We have a 1.4 board, and have the same issue with mission planner 1.92 not working (ie not connecting and giving a No Heartbeat Packets received after the connection timeout). I downloaded and used mission planner 1.50, and this seems to be doing fine (but I just barely got this going). I am wondering if there are any patches/solutions which I can use so I can use 1.92 and future upgrades
Thanks in advance - my son and I really appreciate the mission planner code and all the work put in to this
Roelof
try checking/unchecking the reset apm on connect option in the planner options.
Permalink Reply by estebanflyer on July 24, 2012 at 10:17am When I use a 3 cell battery at my work bench, the Xbee mounted with the quad works fine. While at the park I use a 4 cell battery, the Xbee bricked itself again. Do you think there is a voltage peak problem? Maybe by delaying the start-up time of the Xbee we can prevent a voltage peak? I'm just thinking here... I don't handle coding at all.
What I do now is, for fully charged batteries, I disconnect the Xbee from the APM, power up the APM and only then I connect the Xbee.
Hope this helps!
Permalink Reply by estebanflyer on July 23, 2012 at 9:45pm I finally got it to work. One of the Xbee's was bricked. I'm not sure which one, I just follow these instructions to fix them.
Once you unbrick one of the xbee's, you are gonna have to set the baud rate to 57600 and an ID to BOTH xbee's. Have in mind you can use the same adapter board for both xbee's, so you wont have to unmount the xbee pair in your quad, just unmount the top board. Remember to disconnect your USB and power down your quad before unmounting anything.

I've successessfully used a FTDI cable[1] to install Simulation Quad HIL to APM 1.4. But when I try to connect, I'm also getting "No Heartbeat Packet Received".
Now when I use a IMU + mini USB cable to connect to the same APM 1.4 it works fine.
Would this be a result of a bad FTDI cable? I'm puzzled since same FTDI cable installs firmware without an issue.
Thanks,
Ruwan.
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.51 members
682 members
184 members
8 members
130 members
© 2013 Created by Chris Anderson.
Powered by
