Did I just brick my XBee?

Wireless & IoT
1

Hi,

I just purchased two XBee 2.5 radios and one Sparkfun XBee Explorer USB.

I wired one radio to my Arduino board and connected the other one to my Mac computer. I wasn’t able to configure the two devices to talk… I tried many different configurations with AT commands and all of a sudden the radio connected to the computer stopped working.

It’s no longer responding to the +++ command… I assume that I corrupted the firmware somehow.

Since I only have a Mac I haven’t tried out the “windows only” software from digi yet… hopefully I can try it out at work tomorrow.

Any ideas… ? Can I save it?

Thanks!

/Jonathan

2

I managed to get the CTU software running in Windows XP under WM Ware Fusion on my Mac.

There was a handy restore function that did the trick :slight_smile:

So now I’m back at config mayhem!

/J

3

Hi,

I met similar problem of xbee.

It doesn’t communicate each other. I think reset is needed.

But now I have only two xbee802.15.4. I did not buy program board.

Do you have any methods?

And would you like to tell me how to reset xbee?

What’s handy reset?

Your reply is appreciated.

Regards,

Xing

4

So, Looks like some of you have had the same problem as I have… Downloading software and getting “bricked boards”. After I receive my development board (RS232), how do I restore factory settings ?

Thanks.

5

There is a documented non-obvious combination of buttons to push. I’ll try to remember where it is among Digi’s user manuals

6

Buttons? I seem to have a distinct lack of anything resembling a button on my Series 2 radios…

I had it responding fine in AT command mode. I wrote a PAN to it using the Digi app, and then … Nothing. Error from the Digi app (X-CTU) and now it’s not responding to AT commands anymore.

I don’t have an explorer board - I’m just talking to it from a Sparkfun level converter and a serial port under Windows - but it worked fine before. Are there some pins that some button shorts or … ? I’d really like to have not bricked a radio. I’m up against a design deadline…

[edit] Ok - I put a pushbutton to ground on the RST pin. X-CTU was able to detect my hitting the reset switch on a restore. I’m downloading new software - but I’m not sure what profile it should even be… Sigh.

[edit] I put my good matching XBee on and did a read from it. XB24-B Zigbee Router/End Device AT Version 1220.

So I put the bricked one back on

Restore

Unable to communicate with modem

Pull RST low for a couple seconds, and the Info window disappears just like it says it will.

I see data go to and from the device a few times (RX/TX lights on level matcher flash) X-CTU reports “Resetting AT Commands…”

Comes back a bit later and says “Unable to find configuration file for modem (firmware version õ). Use 'Download new versions” button to check the web for newer versions

Gobbledy-gook for a version number can’t be good. I’m at a loss…

[edit] Tried a “always update firmware” and it got stuck in an “update summary” loop. I finally got tired of clicking “ok” after the 341 time, and killed it, and rebooted. No data was going to or from the modem…

TIA for any advice!

— Jodie

7

I switched X-CTU to API mode under PC Settings and was able to write the AT mode software to the device, reset and there I was.

Now I just need to figure out how to re-insert all the hair I pulled-out…

8

I experienced a similar problem. I got an Xbee module with firmware 1084 but it wasn’t in my firmware list so I decided to flash the latest. I succeeded flashing but I still couldn’t read the firmware (it still told me it was an unknown firmware), so I tried the 1083 version which also was in my list. The flash went fine but after that it stopped responding completely. I was able to test/query by checking the Enable API box, and got a dialog box with some jibberish in it. The green LED on my USB board was blinking rapidly as well.

I also got the dialog box which tells me to press reset and then the dialog should close within 10 seconds, but that didn’t do any good. However, by selecting the latest firmware, holding the reset button down while pressing Write and not releasing the reset button on the board until the status bar progress changed I got to the point where the firmware was flashed without problems.

Maybe that trick can help someone else too :slight_smile:

9

I don’t think you can “brick” an XBee series 1 (don’t know about series 2).

I’ve abused them a lot and using Digi/Maxstream’s procedures with XCTU and their dev kit motherboard, always been able to reinstall firmware.

10

I got the same problem. I’ve tried resetting, etc but it still doesn’t respond to +++ AT code. I’ve tried different baud rate and even check and unchecked the API button. I’m at a lost. I posted the same subject few days ago.

11

if you are stumped, send me the XBee module and I’ll try to reset it.

PM

12

Sad day. Same problem here. My 3 XBees were responsive (they’d send a period back if I sent them +++), but now I get nothing either through the comm port directly or with X-CTU.

13

I have 3 XBeePro modules with the same problem. I was trying to configure them for API operation and somehow got them into a state in which XCTU can’t communicate with them at any baud rate or handshake mode. Is there a known fix yet?

14

I got my 2 XBee Pro modules restored to its factory settings (thanks Steve!). Both could respond to AT commands but still not able to transmit the actual data. I would send a “counting” number (ex: 1, 2, 3, 4…) but it would display garbage data at the terminal. Both modules appear to be communicating very fast but the problem of garbage data remains. Anybody solved this problem yet?

15

tell us the specifics on your configuration - what firmware, AT settings, etc.

And if you can get one of Digi’s demos to run.

16

This worked for me when the reset trick refused to.

It is possible when using the USB board. You just have to go about it in a different manner.

  1. Take the module out of the interface board.

  2. Connect the interface board to the computer.

  3. Open X-CTU

  4. Go to “Modem Configuration”

  5. Put a check in the “Always update firmware” box

  6. Select proper modem from drop down menu,

  7. Select proper function set and firmware version

from drop down menus.

  1. 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.

  1. You may get the info box again a short while after,

just use the reset button on the interface board.

This should get you back up and running.

It can take a couple of tries but it worked for me.

17

If you just have a breakout board make sure you hook up the Xbee like this:

http://www.faludi.com/itp_coursework/me … grade.html

It won’t work with just just Dout and Din connected. Otherwise follow the instructions above.

18

There is a similar thread on the digi forums:

http://www.digi.com/support/forum/threa … eadID=6583

19

Guys,

The fix above didn’t work for me, I have a XBee 2.5 module and I am trying to program it via a sparkfun USB board. The following did though.

  1. Select “Always update firmware”

  2. Under modem select “XBP24-B”

  3. Under function set select “ZNET 2.5 COORDINATOR AT”

  4. Put XBee module into USB board and plug into computer

  5. Press write button

  6. When dialog button pops up, reset the XBee module. I did this by turning over the XBee module and sticking an unraveled paper clip through the two holes marked “GND” and “RST”.

  7. The firmware should start to load.

Hope this helps.

Jim

20

You guys all do know the differences in feature/function set’s right?

In API mode ‘+++’ won’t work, in fact ‘nothing’ will work unless the messages you send it are in API format, so for the most part select the firmware with AT in it (unless you know what you’re doing :P).

Also the EndPoint/Serial Router or Coordinator mode defines the role of the XBee. The default function set for the 2.5 XBee is “EndPoint/Router AT”, which means the XBee works as an EndPoint device in Endpoint/Coordinator setups, or Serial ↔ Serial devices when you have just two XBee’s (what goes in comes out the other end).

The Coordinator function allows the XBee’s to be used in a mesh network, with this XBee as the Coordinator (can have and coordinate multiple XBee’s connected to this one).

Coordinator in AT mode is difficult as you have to enter command mode and set the “to” address every time you want to write to a different XBee.

API mode requires specific messages to be sent to it, to send your data messages, including the to address, network address, option bytes and a calculated checksum.

Slightly off-topic, but it helps to know what all the different function set’s do, and which one you require.

Remember too that when programming from one to the other (AT to API, or changing the baud rate), X-CTU will not find the XBee after programming it (to reload the AT commands) until you go back and select “API mode” or modify the baud rate and reconnect.