[CC2630/zstack 1.2.2a] Leave network without reset

if i understand correctly, the issue in that topic was to directly rejoin the PAN the device just left instead of resetting. I did try to use it (as that code seems to be part of 1.2.2a now) and after leaving the device rejoined the network.

However, i want to do the following (sorry, i think i have been a bit unclear):

-initiate network discovery when device is not part of a network.

-device joins a random network

-it is not the network i want it to join -> handshake is unsuccessful

-device leaves the network (maybe blacklists the PAN it just left)

-device does not reset but continues network discovery

The line in bold letters is what i still have to figure out, everything else is in place.

haven't been able to work on this for quite a while, because of more urgent tasks.

I've observed, that my device does send out beacon requests and they are answered by my coordinator (observed this in TI SmartRF Packet Sniffer). However, my EndDevice does not join another network. It just keeps sending beacon requests

Sure. I have attached it to this reply. I stopped capture after 5 Beacon requests after the device left the network.SmartRfPacketSnifferLog_continue_join_after_leave.psd

Hello Jose,

thank you very much for your reply. We have thought about filtering devices before joining as well (however, until now I wasn't sure were to implement such filtering). Currently, after zigbee joining we have put a kind of handshake mechanism in place:

The coordinator knows the IEEE of the End Device that is supposed to join, but we have no way to give the End Device any information about the Coordinator. Therefore, after joining any network, the End Device sends an AF_DATA_REQUEST to the Coordinator and the Coordinator will look at the IEEE of the End Device. If it is the desired IEEE, the Coordinator will answer with a defined message and the handshake will be complete. If it isn't the desired IEEE the Coordinator won't answer and the End Device will leave the network eventually (and reset).

This mechanism has been implemented for an older product generation (with different hardware) and we are now developing a newer Device Generation with the CC2630 and compatibility is required.

All this is already implemented. The only annoyance is, that the device resets after leaving.

However, if we could do this by filtering as you propose, this would be a way better approach. Do you have advice on what i could filter? Is it possible to modify beacon replys to contain additional data?

Also, on a related matter, with your proposed way, do you think it is possible to filter out router devices?

YiKai,

the leave request is sent by the end device to itself by use of Zstackapi_ZdoMgmtLeaveReq. I do

      // Wipe out the network state in NV
    NLME_InitNV();
    NLME_SetDefaultNV();
    // clear NWK key values
    ZDSecMgrClearNVKeyValues();

as you proposed to clear NV. However, if i only clear NV, network information will still be in RAM of my End Device, will it not?

I just thought, maybe this screenshot helps visualize the situation:

End Device sends Beacon request and receives multiple responses. The device i want it to associate with is the marked one.

I do

   // Wipe out the network state in NV

   NLME_InitNV();

   NLME_SetDefaultNV();

   // clear NWK key values

   ZDSecMgrClearNVKeyValues();

as you proposed to clear NV. However, if i only clear NV, network information will still be in RAM of my End Device, will it not?

Hello Luis,

unfortunately i can't do any filtering based on the ext pan id, because i can't know the IEEE of the coordinator beforehand. We have thousands of handheld (coordinator) devices and every end device has to work with any of these coordinators. But i managed put a filter into place that sorts out any router devices.

Thank you for your ideas and code on the blacklist issue. Looks like this is the route we have to take.

Unless maybe someone from TI could point me the way on how to continue discovery after leaving a network without resetting