I bought a pair of XBee 2.5 modules (one wire antenna, one chip antenna), an XBee Explorer, and an XBee breakout board. Using X-CTU from my Windows box to talk to the XBee Explorer with the wire-antenna module physically connected, I configured it with the Coordinator firmware (1020). I then swapped back to my Mac, which will actually be doing the control in practice. Minicom (built through macports) works, but doesn’t display CRs properly (so, for instance the ATND command spits out one line, typing over previous lines’ output). I’m using realterm through WINE right now, which works better. X-CTU runs in WINE and I can get it to talk to the USB explorer to the point that the activity LEDs flash, but it won’t recognize the XBee’s firmware with the test commands.
Anyway, from within realterm, I issue the following commands
+++
OK
ATND
[snip, output; first line is MY of BA4B].
ATDNBA4B
ERROR
that should set the destination node for the controller to BA4B, which is the address the other node (which is being powered by a 3v regulator on a breadboard with no other devices attached right now) is reporting when the network detect scan happens. I’ve verified that BA4B is the correct address by plugging that XBee into the Explorer and issuing the ATMY command. So, to the best of my knowledge I’m setting the destination address correctly. Why is this an error? Do I need to join the remote module to the network first?