I’m capturing temperature with the sensor and it does transmit to the hub station where my arduino code strips the API frame and decodes the temperature.
The goal is to then transmit something to the alarm station and trigger noise. I can’t figure out what type of network to assign to the Alarm station and if it needs to be AT or API. To prototype the design, I tried both AT and API firmwares on the Alarm. With the DH/DL configured properly, in the X-CTU terminal I type to communicate between HUB and ALARM with no success. Once when I had AT on the Alarm the ALARM spoke to the HUB (which is the opposite direction I want).
Any help is appreciated. Again, the fundamental goal is to send anything whatsoever from the HUB to the ALARM. I see the Tx LEDs going off but never the Rx.
I prefer to use peer to peer networking, since I don’t often need meshing.
With this, you disable the coordinator function. All nodes are 802.15.4 mode, and each node talks to whatever other node it chooses by setting the destination MAC address (DH:DL in Digi XBees) then send a packet. Enable MAC layer ACKs. RF permitting, any node can talk to any node, or broadcast to all.
Are you suggesting using the 802.15.4 firmware instead of a Router/Coordinator, API/AT firmware? If so, my units are Series 2 XB24-B, which doesn’t have a 802.15.4 firmware.
Its silly that I can’t get the HUB to pass information to the ALARM. I specified DH and DL properly and the PAN IDs match, so I assume they joined the same network.
