please i need help ,i have this error (unable to communicate with modem ) when i press test \query
MostafaHamdy:
please i need help ,i have this error (unable to communicate with modem ) when i press test \query
This may be due to various issues such as:
The COM port is in use.
Wrong serial settings (baud rate/parity etc), this also may be incorrect/not matching in the COM port settings in the device manager.
Serial connection is faulty.
xBee module/shield is faulty.
Not possible to instantly see your problem as you have not stated how it is all connected.
If you are running through an Arduino shield ensure that the Arduino is in bypass/reset mode (ground the reset pin), this will ensure that all serial communication goes directly to the xBee module.
I personally avoid programming the modules through an Arduino for many reasons. I would recommend purchasing a xBee developer interface board or other board which is specifically for programming xBee modules.
Confirm that all the serial settings are correct (device manager settings, X-CTU settings and xBee module baud rate settings), if that wasn't the problem ensure the computer is communicating with the xBee module. If that doesn't work then one or more of your products are faulty.
Goodluck.
- Luke
Does it act like it communicates at all? I had my brand new module bricked up like this the other day. I had tried to upgrade the firmware and that was the end of communications. I had to resort to hot-plugging the module into the explorer board that I have because it doesn't have a reset button. This got me thru a flash cycle mostly and it would respond to WRITE requests after that, but it would still complain after the flash about not being able to do AT commands and it also wouldn't query the chip on the first tab.
I then learned that I needed to do the "Show Defaults" button to load the default settings for the firmware before doing an upload. It still didn't work right, erroring out on doing AT commands. When I finally turned on the API Enable option in the firmware settings by pure chance, it uploaded and then it successfully responded to all the things like it should. I could then turn off the API Enable option and do another Write and it would continue to work. This didn't really make sense, but it did unbrick my module completely.
I had no luck tinkering with the Enable API checkbox on the first tab. It also didn't help to check the no baud change box on that same tab. The only thing that finally fixed it was to Show Defaults and then turn on the Enable API option in the firmware settings list followed by an Write.
the same sheild work in another computer but the O.S. windows 7 & when i try it in windows 8 not work and give this error