CC2652R: End Device dropping from network

Can you elaborate your issue with your sniffer log?

Thanks for the quick reply,

Below is the screen shot of the logs already attached, On transaction ID 9261, the End device with MAC id 0x6138 sends the last data requeset and after that there are no messages for/from this end device.

 And when we check the devices status, it is showing as "PL NotOnNetwork".

Thanks

Is it possible that your device 0x6138 resets after packet ID #9261? What's the device 0x6138? Is it based on Z-Stack example? If yes, which Z-Stack version and which example exactly?

No the device did not reset.

Device 0x6138 is CC2652R based End device running zed_doorlock_cc26x2lp example code from SimpleLink CC26x2 SDK - version 2.20.00.36 and simplelink_zigbee_sdk_plugin_2_20_00_06

Do you do any modification on zed_doorlock_cc26x2lp example? Do you test this with LAUNCHXL-CC26X2R1?

Yes, modified the zc_doorlockcontroller_cc26x2lp code to send "zclClosures_SendDoorLockGetRFIDCode" command and zed_doorlock_cc26x2lp to respond for this request with 32 bytes of data. Also defined ZCL_DOORLOCK_EXT in both the projects to support this command.

I have tested this with 2 LAUNCHXL-CC26X2R1, one as ZC and other as ZED and don't see any issues. But when i add more the 3 end devices to the network, initially all the end devices will be responding. But after some time i see some of the end devices drop from the network. While the other devices which are still in network will be responding just fine.

For testing, I am initiating the command send to one of the end device through the APP screen from UART, after receiving the response, command will be sent to next end device. This will continue in loop.

How do you know your device doesn’t reset by itself due to any unknown reason?

I am testing this with UART interface of the app and i don't see the screen going back to default screen, which is the case if reset happens.

When this issue happens, does UART still work?

Yes, i am able move back to <COMMISSION> screen and see the status as "PL NotOnNwk". Event if try commissioning manually by pressing "E", the device will not join the network. For some time the status will be "Please wait... " and after some time it will be "-- NotOnNwk".

If you power cycle the device when you see this issue, can the device join back after power cycle?

No, the device is not able join the network, <COMMISSION> screen status is "-- NotOnNwk".

It looks like the network information is lost so I suggest you to debug in this direction. By the way, if you test with Z-Stack without modification, do you still see the same issue?

I just tried with Z-stack without any modifications and i see only 1 end device rejoins the network and all others fail to join.

Ryan Brown1 Do you have any idea?

Nazirahmed Tolagi 

I have tried reproducing this issue with using the sample application ZC_doorlockcontroller_cc26x2lp and ZED_doorlock_cc26x2lp, using 4 ZEDs and 1 ZC in the network. They have been running for over an hour and a half now four and a half hours now without fail, being no leave commands. There were 2 instances where a ZED might have been dropped and in the sniffer log attached you are able to see that they were successfully able to rejoin without fail.

I would recommend following my comments above to see if this fixes your issue.

Best,

Sean

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/ZC_5F00_DoorLockController_5F00_ZED_5F00_DoorLock_5F00_2_5F00_20_5F00_NoLeaveCmds.cubx