hey!!well all three XBEEs are working fine now!!!Are you using libelium shield with arduino for writing a program using XCTU??
if so,you will encounter many problems.I got a USB adapter from http://www.parallax.com/tabid/768/Produ … fault.aspx .i used this USB adapeter, magically 2 xbees worked fine.i encountered some problems with another XBEE but i used the following 12 troubleshoot methods:
Here are a few ideas that people have in the past found helpful.
1.Are you using the latest version of X-CTU? If not, download and install the latest version from the Digi site.
2.Check that the version of X-CTU you’re running really is the version you think it is (use the About… menu option). There has been one report that after uninstalling an old version it was necessary to delete the program folder and reboot before installing the new version. Without the folder deletion and the reboot the new version was installed, but the old one was still there and was the one that ran.
3.My thanks to Javier Gonzalez for pointing me to this one: On YouTube at http://www.youtube.com/watch?v=fxOqQZD-oaM, Digi have a video demonstration of how to recover an XBee. The video title is How to Recover an XBee from a Failed Firmware Upgrade. My transcription of the steps goes as follows:
a.Connect the affected module to your interface board and the PC, leaving the interface board disconnected from its power. The video shows a serial board, but it doesn’t say you can’t use USB.
b.Launch the X-CTU software.
c.On the PC Settings tab, make sure you have the correct COM port, baud rate and parity settings selected.
d.On the Modem Configuration tab, select the correct modem type, function set and firmware version.
e.Click on Show Defaults, and Write.
f.When the Action Required box comes up, hold the reset button in, then apply power to the interface board, then release the reset button. The Action Required box will then close out.
g.The firmware load will take place, and when completed your module will be functioning properly.
4.In X-CTU go to PC Settings and make sure it’s set for 9600 8N1 with hardware flow control. Also make sure that the Enable API box is NOT checked.
5.(Note: this one is a lightly edited quote from Digi Support.) Look at the bottom of the RF module and see which model you have. Then in X-CTU select the correct modem model and click show defaults. You should click on Download New Versions so you have the latest firmware version for your RF modem, and also make sure you have Update Firmware checked.
6.If you can communicate with the module from X-CTU or from a terminal program, try issuing the ATRE command to reset all parameters to their default values. Then if you’re using a terminal or the X-CTU terminal window, issue ATWR to save the default values to non-volatile memory. Then try again with the reprogramming.
7.If you get an error message from X-CTU when you click the Write button, then hold down the Reset switch on the development board while you click the Write button again. Keep the Reset switch down for another second, then release it.
8.If that doesn’t do the trick, try the Write command again and press the Reset switch when one of the LEDs on the development board goes solid.
9.Still no luck? Try this suggestion from Digi:
a.Download and install latest X-CTU from the downloads section.
b.Power off your module.
c.Put reset to ground, or activate reset switch in your test board.
d.While powered off (yes!) start the update on X-CTU and wait until it complains that a reset is needed.
e.Power on your board, and after a few seconds, release reset.
f.Update should start.
10.And here’s a recipe that was posted in the Zigbee Pro forum by NATP who says it has worked for him:
a.Using the USB board (XBIB-U-Dev rev 3), X-CTU 5.2.5.0 with Windows XP, SP3
b.Close X-CTU, disconnect the board
c.Power on the board
d.Open X-CTU
e.On the PC-Settings tab:
1.Set Baud Rate to 38400
2.Select “No baud Change”
f.Click Test/Query - this will fail with the “action required” dialog… - close it when it comes up (do not follow the instructions on the dialog)
g.Click “OK” to the “cannot find modem” dialog
h.On the PC-Settings tab:
1.Set Baud Rate to 9600
2.Un-select “No baud Change”
i.Click Test/Query - Success!
j.On Modem Configuration Tab – click “read” – Success!
11.Still need more? Here’s one posted by shahrj1988 in response to a request for help. The original poster replied that it had worked.
a.Make sure the XBee module is NOT plugged into the interface board.
b.Connect the interface board to the computer via appropriate cable (USB or Serial) (If using Serial, connect power as well).
c.Open the X-CTU program and select the proper COM port.
d.The first screen you see contains the PC Settings tab. On this tab please change the baud rate to 38400 and put a check in the `No Baud Change’ check box.
e.Navigate to the Modem Configuration tab.
f.Select the proper modem type, function set and firmware version from the 3 drop down menus located about 1/3 of the way from the top of the window.
h.Click on the Show Defaults button and put a check in the `Always update firmware’ check box.
i.Click on Write. (Yes, the module is NOT plugged in) An Action Required box will appear. This is good. When this happens, hold in the config/reset switch on the interface board and CAREFULLY plug in the module and then release the config/reset button.
j.You should now see that box disappear and a progress bar will appear along the bottom of the window. You will see the bar progress and then the box will appear again. This is good. Just hold in the reset switch on the interface board for about 1-2 seconds and then release. The box will disappear and the status at the bottom of the window will show that the write was complete.
k.Go back to the PC Settings tab and change the baud rate back to 9600 and uncheck the `No baud change’ check box.
l.Click the `Test/Query’ button. You should get a clean bill of health.
12.If none of the above worked, you can either post the problem to the forum or send a support request to Digi. When you do find a method that works for you, it would be a kindness if you would post it to the forum for the benefit of others.
13.Open an X-CTU Terminal Window
Change the baud rate to 115200
Assert/check DTR, De-assert/uncheck RTS, Assert/check Break
Hit the /RESET button on the XBee development board (example: XBIB)
De-assert/uncheck Break
Click on the Terminal Window tab, then Type a #B# and hit Enter or Carriage Return (the B must be upper case)
Check #Always Update Firmware# & select firmware you wish to load
Click Write
i have tried all methods and shuddenly it started working!!!my suggestion is to implement 6,13,10 points of the above mentioned troubleshoot methods more often.
After every trial try to write the default parameters.It will work!!
inform me if your problem gets solved. 