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.

CC1352P: ZNP Coordinator Not Permitting Join

Part Number: CC1352P
Other Parts Discussed in Thread: CC2652RB

We are developing a Zigbee system and finding that (sometimes) nodes can't join the network. Our current hardware is composed of the following:

  • "Light" node, a CC2652RB running the "zr_light" demo firmware.
  • "Switch" node, a CC2652RB running the "zr_sw" demo firmware.
  • ZNP node, a CC1352P1 connected to a BeagleBone Black running the Zigbee 3.0 Linux Gateway software 

After bringing the system up and running the Linux gateway software ("zigbeeHAgw" and the console-based "TI GATEWAY DEMO APP v2.01"), I can type "P" (to permit joining) and can usually get the "Light" and "Switch" nodes to join without problems. Further Zigbee interaction (such as creating and using bindings) works as expected. Powering down the system and restarting the Linux gateway software usually shows the previously-joined "Light" and "Switch" connected.

But if the "Light" and "Switch" nodes are removed from the network-- by either Issuing the "Reset to FN" command on the nodes or typing "R" on the Linux demo app-- then trying to get "Light" and "Switch" to join the network again fails, maybe 90% of the time. I am able to get "Light" and "Switch" to join the network again by power-cycling everything. Once everything is back up, the nodes (usually) join without problems.

I recently have found that I am having trouble getting "Light" and "Switch" to rejoin the network, I can stop the Linux gateway software, press the restart button next to the USB connector on the ZNP, and restart the Linux gateway software. This seems to allow joining again, which suggests (to me) that the issue I'm describing could be caused by the ZNP and/or its interaction with the Linux gateway software. 

If there is diagnostic information that would be useful from the system to help debug why nodes can have problems joining the network, please let me know what to look for.

  • I would suggest you to use sniffer to check what happens over the air exactly.

  • Hi John,

    The gateway application user_interface.c example uses how comm_send_permit_join -> nwk_set_permit_join_req__pack (commissioning_engine.c) to enable permit join.  Along with YK's request, it would be good to have a gateway log to further understand communication between the gateway and ZNP.  If you are able to use Z-Tool, does using ZDO_MGMT_PERMIT_JOIN_REQ  on this interface allow the devices to join?  If so then this may be used to compare the differences by monitoring the UART lines, debugging the ZNP MT_ZdoMgmtPermitJoinRequest parameters, and sniffing Mgmt Permit Joining Req broadcast packets.

    The issue could also be an inconsistency in secured device lists/tables between the gateway and ZNP.  Are other devices which have never communicated with this network before able to join when these "Reset to FN"/removed devices cannot? Also, have you tried the behavior of ZEDs and what SDK version are you referencing?  I was recently reminded of a Linux gateway issue and recommended workaround that I recommend you implement as it could affect removing secure devices from the network.

    Regards,
    Ryan