You need ONE coordinator, but only ONE!
The rest can be routers or enddevices. Routers as the name says can route to others.
The special of enddevices is, that they can't route but they are able to sleep.
With my module you will be able to communicate with all types (Coordinator/Router/Enddevices)
I think RSSI values or link signal quality can be read out by AT commands. Should be possible with all types of devices.
You need a PC to flash the right firmeware to the xbee's first.
Use the latest xBee firmeware in the API variant.
All the other settings can be done on the PC too or by AT commands from the espruino.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Hi Alex,
You need some basic understanding about xBee. The following book may help:
http://shop.oreilly.com/product/9780596807740.do
I try to answer your questions.
You need ONE coordinator, but only ONE!
The rest can be routers or enddevices. Routers as the name says can route to others.
The special of enddevices is, that they can't route but they are able to sleep.
With my module you will be able to communicate with all types (Coordinator/Router/Enddevices)
I think RSSI values or link signal quality can be read out by AT commands. Should be possible with all types of devices.
You need a PC to flash the right firmeware to the xbee's first.
Use the latest xBee firmeware in the API variant.
All the other settings can be done on the PC too or by AT commands from the espruino.
Sacha