Can not communicate with the xbee pro modem

XBee & XBee Gateway XBee - Zigbee
1

when I using the x-ctu test/query ,i get the following info.
communication with modem is OK
modem type=name unknow(ID=4294967248722130)
modem firmware version=

when I write the firmware XBP24-B version 1241 to the module,I get the following info
Getting modem type…OK
Programming modem…Flash checksum error failed
Write Parameters…Failed
Could anybody tell me how to solve this problem?
thanks !!!

2

If the checksum is failing, you might want to try downloading the current ZNet 2.5 firmware (1x47) from our Support website and try updating with that instead (assuming file corruption or something):

http://www.digi.com/support/productdetl.jsp?pid=3261&osvid=0&s=269&tp=2

Also it should be noted, when updating firmware from a zip file (like the one linked above), you update WITHOUT unzipping the file first. X-CTU auto-pulls what it needs from the zip in other words.

3

Hi…

I am also having same problem.
But only I am having XPB24 module.

Can any one solve this problem?

4

I have a couple comments.

Quoting the first post in the thread:

“when I using the x-ctu test/query ,i get the following info.
communication with modem is OK
modem type=name unknow(ID=4294967248722130)
modem firmware version=”

You would get this output even if there was no X-BIB board connected to your PC, and the “Enable API” box was checked. If you tried burning new firmware on a radio with the “Enable API” firmware box on the PC Settings tab checked, unless there was currently API-enabled firmware on the radio, I can see why this would fail.

Regarding:

“Programming modem…Flash checksum error failed
Write Parameters…Failed”

If getting the output seen in the first part of this reply, I can understand why programming new firmware into the modem would fail as well.

What that “checksum” error means is that the firmware file that was not able to upload to the processor properly. This could happen for a number of reasons, be it bad cable connection between X-BIB and PC, corrupted firmware file, or “Enable API” box checked when trying to write to a non-API enabled firmware build.