- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I have a problem with my zstack, I would very much appreciate some help. I use zstack version 2.4.0 with the ZIGBEE-PRO feature.
I have a network with one coordinator(with router functionality) that also is the trust center. I also have one router and a number of end devices.
This is what happens:
1. I power up the coordinator with a clean empty network, the association table i empty.
2. I power up the router and wait for it to join the coordinator, I get one entry in the association table on the coordinator and one on the router.
3. I add the end devices one by one. First, they fill up all slots in the routers associationTable. When the router is full, the cooordinator start to fill its association table.
4. After a few devices everything stopps(the assiciation table is NOT full) and the coordinator sends beacon indications saying it no longer has join or router capabilities. I start to examine the association table and find that there are many entrys left. So that is not the problem. I then examined the AddrMgr entrys. And the function AddrMgrIsFull returned TRUE!! I listed all the AddrMgr entrys and it was apparently so that the AddrMgr list on the coordinator contained nwkaddr-extaddr entrys from end-devices that had joines the router as well as the coordinator. Since the size of the AddrMgr table is the same as the association table + 1, this problem will ofcourse occur.
So, why is the AddrMgr table filling upp with all end-devices, even those that joined the router? What if I want to have a large network with hundreds of devices, that would never work.
Ideas anyone?
Regards
Andreas
