This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

zigbee association

Other Parts Discussed in Thread: Z-STACK

hai,
during the formation of association the device sends request to the coordinator, then association may be formed..fine; I want to know on what factor(deciding factor) the Coordinator may/may not form the association..[i.e it accepts or rejects the request] ?

thank u

  • Several factors can prevent a device (Router or End Device) from associating with the Coordinator ...

    1) Devices are operating on a different frequency than the Coordinator

    2) Devices are programmed with a incompatible PAN ID

    3) Device IEEE address is on Coordinator black list (security enabled)

    4) Device IEEEaddress is not on Corrdinator white list (security enabled)

    5) The Coordinator has exhausted its connection allocation (this is dependent on which Z-stack version is being used). Device would associate with another Router.

    6) There are limitations on compatibility between the Z-stack versions, which might cause the Router device joining to join as an End Device.

     

    This is all that I can think of off the top of my head.

     

    Scott

  • Hi...

    I have a similar problem with the association... Can anybody help me please?

    Here there is the post.

     

     

    Regards

  • Hi,

    How can I fix the problem of connection allocation exhausted?

    My problem is that my coordinator exhausted its connection allocation. If my routers reset they are not able to connect with the coordinator anymore.

    Even when I reset the coordinator, it is not able to give the association to the routers (the coordinator answers the beacon request with the flag association permit = 0 [NO]). I am using the flag NV_RESTORE before restarting my coordinator.

  • hi

    Can  you explain what is black list or white list?

    thanks

  • Black and white list mean that you can have such a list on your coordinator. For example, the node on white list is allowed to join network. To implement this capability, you need to construct your own white list of devices' IEEE address on coordinator. When a ZED joins ZC, you can check if it is on white list. If not, ask the device to leave.