I have one XBee setup as a coord and another as an endpoint. Coord is setup with CE=1, both on the same ID and CH and AP=2 . The coord is connected via shield to an Arduino Mega on serial1 using the XBee API library.
On power up communication works perfectly, I can send data from the coord to endpoint and receive. The problem occurs approximately after one minute with no data being sent either way, sending a command to the endpoint results in a 0x04 no response status from the coord. I've tried a few different XBees as endpoint, same result. Different XBees as coord, same result. Reseting the endpoint, still no response. The only way I can reestablish comms is by sending an ND (Network Discovery) command to the coord, to which the endpoint replies and then I can communicate with the endpoint again. But if there is no comms for a minute, comms is lost again. I've posted this in the XBee forum as well but I'm thinking it might be the XBee API library causing the problem and I wanted to know if anybody else had experienced this?
I have one XBee setup as a coord and another as an endpoint.
This doesn't make sense for point to point modules, which is what the Series 1 modules are.
both on the same ID
Hi. I'm Bob, and this is my brother Bob.
What ID are you talking about? PAN ID (which isn't ID)? MY? DH/DL? SH/SL?
Thanks for the reply, I was talking about the PAN ID.
I finally fixed the problem though. The XBees had version 10CD loaded which is a few revisions old. Once I upgraded, the timeout disappeared.