I have bought 2 XBee Pro S2B modules with wire antenna, which I want to make communicate with each other in API mode (I want the extra functionality of API). So I first tested them in AT mode, everything working fine, and then loaded the API firmware into them (one coordinator, one end device).
And now we have the problem: X-CTU constantly loses connection with the end device, terminal operations are not working, and most of the time XCTU doesn't even find the module.
After a lot of searching (2 cables, two USB connection modules, swap firmware between modules, ...) I found out that the cause is the Sleep Mode setting, which is defaulted to "4" (cyclic sleep) in API end devices. If I set this to "1", everything works fine.
So, my questions:
1) Am I the first one having this? Loading new firmware into an XBee modules makes it unresponsive to XCTU because of the default settings --> this doesn't seem like intentional behavior to me.
2) I was lucky to be able to change the parameter, but you have to be quick. Can I avoid this in the future?
3) The end device will be battery operated, so can I test the modules with the end device in sleep mode, using XCTU? Or can I even configure the end device to cyclic sleep using XCTU? As soon as I do this it will constantly lose connection and I will quickly come into a situation where I need to recover the module (already had to do this tens of times).
Davy Van Rossem
P.S: I use the newest XCTU version and this connection module: