Hi,Running APM 2.1 and the latest build of APM planner (according to update facilty in Planner).Xbees are 868s.Mavlink works great over USB but I get no end of exceptions over Xbees.The Xbees are working fine (they definately are connected and working and have flown many times on APM 1.x with a GCS). When I try to PID config or load a mission over the Xbee Mavlink I get 'expected 0 got 92' type errors (I can upload screenshots).Xbees have been the same on 9600 and 38400 baud.Any help appreciated. I would have thought Mavlink would have been very robust against less than perfect connection due to its intended purpose, but this seems not to be the case.CheersD
You need to be a member of diydrones to add comments!
The RF data rate is limited to 10% in Europe which effectively gives a 24Kbs throughput rate. I can only suggest you try them at a serial rate of 19200 (change the config and Xbee serial settings).
I have been running 900Mhz at 56k and 2.4Ghz at 34k xbees with APM2.X without significant problem.
"Expected 0 got 92" sounds like a strange error message. I do occasionally (<20%) get a failure on the parameter download, which is about the most stressful event for the APM/Mavlink/GCS system, but the error message is typically something like "expected 92 got 90". Which GCS are you using?
Replies
The RF data rate is limited to 10% in Europe which effectively gives a 24Kbs throughput rate. I can only suggest you try them at a serial rate of 19200 (change the config and Xbee serial settings).
The 2.4GHz Xbees do not have this limitation.
Peter
Davey,
I have been running 900Mhz at 56k and 2.4Ghz at 34k xbees with APM2.X without significant problem.
"Expected 0 got 92" sounds like a strange error message. I do occasionally (<20%) get a failure on the parameter download, which is about the most stressful event for the APM/Mavlink/GCS system, but the error message is typically something like "expected 92 got 90". Which GCS are you using?