Telemetry Xbee Communication Error With MissionPlanner
I have a problem communicating to the ground station using Xbee modules. After clicking on connect, it tries to communicate then waits 30 seconds and finishes with an error message:
-----------------------------------------------------
Your serial links is not fast enough.
-----------------------------------------------------
both Xbee modules are set correctly and work perfectly (see attachment)
I changed the baud rate (in both Xbee's, firmware and MissionPlanner) to 38400 but still the same problem. Still not sure if it is a hardware or a software problem. I thought it could be a circuit noise so i disconnect all sensors from the board keeping only the xbee but that still not changing any thing. this disappointed me the who day. If anybody have the same problem please let me know.
I am using the flowing hardware/software:
Xbee modules: 2.4GHz XBee XBP24-AWI-001: http://www.sparkfun.com/products/8742
Xbee explorer on laptop side: http://www.sparkfun.com/products/8687
Xbee explorer on ArduCopter side: http://www.sparkfun.com/products/9132
ArduCopter firmware: ArduCopter-2.5.5
Mission Planner 1.1.92
- Attachments:
Replies to This Discussion
-
Permalink Reply by Airfoto.se on -
The baudrate should be 57600
-
Permalink Reply by Alex.CCCP on -
the baudrate is not so critical.
The problem is in your explorer board If your XBEE doesn't have pullup resistor on DIN. I experienced the same problem with my modules. Solved it by replacing the DIN diode with a 1k resistor. But to tell the truth the more perfect deal is to solder about 10k resistor between DIN on the XBee side of the diode and the 3v3 out - this will make external pullup. But DO NOT try to simply shorten the diode, it may burn your XBEE putting 5v on DIN.
-
Permalink Reply by Alex.CCCP on
-
i'm talking about your -Xbee explorer on ArduCopter side: http://www.sparkfun.com/products/9132
-
Permalink Reply by Abusus on
-
Thanks Alex.CCC, I will try your solution and hope it works. In fact i faced this problem only with firmware version 2.4 and above. When i use an older firmware version then XBee communication works perfectly, therefore i thought that it could be i code bug.
-
Permalink Reply by Alex.CCCP on
-
maybe for your module there is a possibility to enable internal pullup via XCTU ? if it has it?
-
Permalink Reply by Abusus on
-
I tried your solutions but still not able to communicate using xbee modules. That is really frustrating. Now whenever i want to tun parameters or load way-points i have to land, communicate with the cable and fly again. I read a lot throwout the forum and tried many things. I was sometimes able to communicate for one or two times and then not able to communicate like always.
Social Networking
Top Content
Contests
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.A list of all T3 contests is here.
Groups
-
Queensland
4 members
-
ArduPlane User Group
682 members
-
Documentation Editors
51 members
-
Moderators
24 members
-
ArduRover User Group
184 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
