I recently purchased an XBee Pro module (WRL-08690) and XBee Explorer USB (WRL-08687), but I am having problems trying to use them. After plugging the Explorer in and installing the USB-serial drivers, I am able to (apparently) send data to the XBee; I can run Hyperterminal and open the Explorer’s COM port with 9600 8N1, and whenever I type the middle LED at the bottom of the Explorer flashes (marked TX on the newer models). This leads me to believe I have selected the correct COM port and the signal is getting to the Explorer.
However, the module does not respond to anything I try in Hyperterminal (including +++ and a few misc AT commands), and X-CTU 5.1.4.1 says it is unable to communicate with the modem when I select the correct COM port (and every other COM port…and yes, Hyperterminal was closed). I have tried a second module in the same Explorer with the same results. I observed static precautions while handling the modules. Using a breakout board, I powered on one of the modules and measured a few of the outputs with an oscilloscope: ON (pin 13) stayed at a constant 3.3 V, AD5 (pin 15) oscillated between 0 V and 3.3 V with a frequency of about 2 Hz, and PWM0 (pin 6) remained at 0 V. GND (pin 10) and VCC (pin 1) were of course 0 V and 3.3 V respectively.
It seems like there must be something simple that I’m doing wrong because I’m really not doing much. Shouldn’t I just be able to plug an XBee Pro module into the XBee Explorer USB and have the X-CTU program talk to the module?
Yes, XCTU should automatically set the default baud rate. You choose the COM port according to what COM number the FTDI device driver chose at installation. I’ve found that you must use the same physical USB port on the PC each time, else the COM number will change.
No doubt you are using a USB port on the PC which has good 5V power rather than a non-powered hub, though that should work.
You could try removing the XBee and jumpering the pins Tx/RX data to create a loopback. Then use the terminal mode in XCTU to verify loop-back.
steve, yes, I’ve found the same behavior with the USB->RS232 adapters I’ve used. I plug and unplug the Explorer at the cable-Explorer interface rather than the cable-computer interface, so the cable always stays plugged into the same USB port.
I am using a desktop which definitely has good 5V power, but I don’t remember if I plugged the Explorer into a hub before the computer or not; I’ll check tonight.
Good idea about removing the XBee and jumpering the TX/RX pins; I can definitely test that from Hyperterminal and I’ll see about doing it from X-CTU also. I’ll also see if I can get the TX LED to blink from X-CTU’s terminal mode like I can from Hyperterminal.