Just to say that I had a similar issue. I am sending data from a Waspmote to an Arduino via ZigBee.

My original application was powering up the ZigBee from deep sleep, then immediately entering a loop to check if the ZigBee was associated with the network, then sending the data. Though the ZigBee always associated after about 15 seconds, and the data was sent with no transmission errors, not all frames were being received by the ZigBee on the Arduino.

After reading the above post, I changed the application to power up the ZigBee, then delay 25 seconds (during which time I do not interact with the ZigBee at all), then check for association (which only takes one check in the loop as by that time the ZigBee is associated, then send the data. So far it works, as every data frame is received OK.

Thanks for this hint about the delay as it's really helped.

I'm having the same delay problem. I'm using ZigBee sleeping en devices and after wake up, if I don´t wait a few seconds (10s is working) the messages will not be sent to the coordinator. This is a big period consuming power and doing nothing, I would like to solve this issue. Any idea?



Thanks :)

One thing I am doing with the "spare" time is using it as time to "warm up" sensors on the Waspmote gas sensor board. Doesn't really solve anything with the ZigBee delay, but I'm trying to think of ways to use that "spare" time to do something useful. :)

Yes, but to "warm up" sensors you don't need to turn on the XBee module. You use the spare time but there's always waste of power... I really don't understand why is needed so much time before sending messages, simply doesn't make sense to me.

Samy and alanholding,

As far as we know, this necessary delay is required by the Zigbee protocol of Digi Xbee modules and is not required by Waspmote API.

We will do some research about trying to optimize it.

Thanks for sharing your comments.


Regards