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.

CC2650EMK: End Device connect to a Coordinator with a different PANID

Part Number: CC2650EMK
Other Parts Discussed in Thread: CC2538, CC2650


I've  Zigbee end devices ( CC2650) developed  based on Z Stack 1.2.2HA  which communicate with coordinator CC2538 .
I have issues that the End device connect to a Coordinator with a different PANID

Do you know anything about this issue?
Any help would be appreciated .

Attached below is a document that summarizes the packet logs and the behavior at the time the problem occurred.

Best regards,

  • Hi Yuya,

    It's entirely possible for a coordinator to change its PANID due to conflict resolution, which the ZED may not be aware of while sleeping.  Thus the NLME_ReJoinReq checks the extended PANID, not the PANID, when rejoining so that it may rejoin the same ZC device as before.  Since the sniffer log shows that the two PANID networks are formed by the same ZC device which maintains the extended PANID as its extended IEEE address, the ZED rejoins even though the PANID has changed.  This is all expected behavior and allowed by the Zigbee Specification.  If you want to perform a separate action then after rejoinStatus is ZSuccess inside MODE_REJOIN of ZDApp_ProcessOSALMsg, you can read the _NIB.nwkPanId (it will change during NLME_ReJoinReq in the above instance) and determine the correct action to take from there.


  • Hi Ryan,

    Thank you for your reply.
    I will change the setting of the extended PAN ID of the ZCD.

    Best regards,