{TekCrack}

Sometimes technology can make you really want to bang your head against the proverbial brick wall. I’m definitely feeling that today as I spent quite a bit of time attempting to get two Xbee modules to communicate. Here is my setup. I have one Xbee controller plugged into my Make Controller and another plugged into a breadboard. The Make Controller is currently powering both Xbee modules at 3.3V. I am attempting to get these two modules to communicate but have had no such luck.

Here is a picture of my current setup.

In the above picture the standalone Xbee is using the Make Controller’s Xbee power to operate. The potentiometer in this picture is currently disconnected from the transmitting Xbee. The other Xbee breakout board is also pictured.

1) I programmed both Xbee modules with the xctu.bin and X-CTU application via the Make Controller and Maxstream’s software. I ensured the following:
    a) The channel was set to ‘C’ or 12.
    b) The PANID was set to 550.
    c) All other settings were unchanged and the same.
    d) The firmware used was 10A5.
2) I programmed one Xbee module to read a potentiometer. This Xbee module is on a breakout board connected to a breadboard. The potentiometer is connected to AD0. I also have two LEDs connected to the ON pin and Assoc pin. The ON LED lights up solid and the Assoc blinks every second or so.
3) Vcc and GND on the breadboarded Xbee are borrowing power form the Make Controller’s Xbee
4) The Make Controller has the Xbee board from MakingThings.com plugged into the Serial connection on the Make Controller board. I have also connected an LED from the Assoc pin to ground and this LED also blinks every second or so.
5) The standalone Xbee has been configured to send data from the potentiometer according to this link.
6) The Xbee module connected to the Make Controller board has been programmed to receive data via the same link.
7) The only command that will respond from the Make Controller’s Xbee is the /xbeeconfig/active command. The Xbee on the Make Controller will not report its Address, PanID, Channel, or the status of the potentiometer at AD0.
8 ) The only thing that does not work properly in the X-CTU application is the range test. It reports "Timeout waiting for data". I believe this is due to the Xbee modules not connecting/syncing up.

So as mentioned, I am banging my head against the brick wall at this point trying to get these to work. More details of what might be wrong can be found at the MakingThings forum here.

Hopefully I can get this issue resolved quickly as they are needed for my current project.

Trackback URI | Comments RSS