Discussions

Xbee pro could not connect any more pls help

Posted by Duy Pham on February 4, 2012 at 11:24pm

Hi All,

I am using APM1 with Xbee pro 900 stock.

When I am updating params for Arducopter, I got failure and then it could not connect any more.

The Mission Planner is 1.1.31.

Is there any way to test this Xbee and detect what module is wrong? Both them still have power on.

Thanks,

Duy

Ps: This is the screenshot of this error from Mission Planner3690912573?profile=original

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Brent February 6, 2012 at 8:08pm

    One of the modules is probably bricked, follow these instructions from the wik http://code.google.com/p/arducopter/wiki/APM1telemetry

     

    Unbricking an Xbee

    IMPORTANT NOTE: Sometimes Xbee modules get corrupted due to spurious signals. If you're finding that yours stops working (green LED on Adafruit adapter doesn't come on), instructions to reload the firmware follow:

    Using the USB adapter board:

    1. Take the module out of the interface board.
    2. Connect the interface board to the computer.
    3. Open X-CTU make sure Baud Rate is set to 9600
    4. Go to "Modem Configuration"
    5. Put a check in the "Always update firmware" box
    6. Select proper modem from drop down menu (for the 900Mhz ones recommended above select "XBP09-DP"; for 2.4GHZ Xeebee Pro 2 select "XBP24-B")
    7. Click on the "Write" button. After a few seconds of trying to read the modem, you will get an Info box that says Action Needed. At this point, CAREFULLY insert the module into the interface board. After a few seconds, this should trigger a reloading of the firmware.
    8. You may get the info box again a short while after; if so just repeat the previous step a few times and it should work.
    9. This will put the module back to 9600 baud. Set your X-CTU PC settings to that and test it. It should report back that it's recognized.
    10. Once you've confirmed that it's working again, make you sure you reset its baud rate (typically 57k for APM) and VID number to match your other module.
    11. If X-CTU flashes a new revision of the firmware when you do the un-bricking procedure, and the second half of the Xbee still has the old firmware, they will not be able to connect. You must update both to a matching firmware revision.
    12. If you get a message "Could not open output file. System Error: Access is denied." it could be because you are operating in Windows XP with a non-administrator account. Run X-CTU as admin.

    (Thanks to Doug Barnett for these tips)

This reply was deleted.

Activity