Other Parts Discussed in Thread: Z-STACK
hello:
I am suffered a question for z-stack 2.4, my scenario describes as follows:
1. One coordinator with NWK_MAX_DEVICE_LIST=32, with NV_INIT NV_RESTORE enabling.
2. 32 end devices which send packet to coordinator every 1 minute, with NV_INIT NV_RESTORE enabling.
When all devices power on, the all network works fine, but when I turn off coordinator and wait more than 1 minute and turn on coordinator again, all end device try to send a "orphan notification" to coordinator, maybe the RF environment is too dirty, so coordinator may not receive all orphan notify and can't send coordinator realigment back.
So, some end devices try to send beacon request to coordinator, but at this time, the coordinator's beacon associate permit bit is FALSE, so the end device can't join back to coordinator again, I think it may because coordinator only can accept the 32 end devices which use orphan join way, all devices use other way to join is not allowed, is that true?
If yes, can I increase orphan notification retry times?
Or can anyone recommend another good method to let the end deivce can join this coordinator?
Best Regards
Joseph Wei
