CC2538: Unable to remove device using ZDO_MGMT_LEAVE_REQ on ZNP-HOST-FRAMEWORK Application.

Hi,

1. The gateway application uses the APS remove device command, which is different from the ZDO mgmt leave request.

2. Generally, the leave request should be sufficient. What do you mean by "the device will not getting reaseted of getting the beacon mode, it stays as it is in its last state (On / Off)"?

While screenshots of sniffer logs are good, please also provide the sniffer logs themselves.

Regards,
Toby

Toby Can you elaborate which API in Z-Stack we can send APS remove device command?

Hello Toby Pan,

What do you mean by "the device will not getting reaseted of getting the beacon mode, it stays as it is in its last state (On / Off)"?

Ans :

If I am removing the device using the using the ZDO_MGMT_LEAVE_REQ command sent from the znp host framework application,
I am able to found that device will be removed form the NV of the ZNP Device.
Also command will be transfer OTA to a device & get a successfull response in feed back.

But I think the device which has to be removed will not change/vanish its network configurations.
so if we try to do some actuations over it, the device will resopnse to it. 

Regards,

Shiv Patil.

Since you ask the device to leave, the device will forget its network status and you cannot communicate with it anymore.

Hello Toby Pan & YiKai Chen,

But its not happening in my case..

I am also providing the Z-Boss sniffer logs & the host framework application commandline logs, will help you to understand the probolem.

znp_host_framwork_logs.rar

Regard's
Shiv Patil.

That's because you set rejoin flash to true. You have to set rejoin flag as false.

Hello YK,

I have tried it by setting the network rejoin condition as false...

Still getting same results.

regards,

Shiv Patil.

What Z-Stack version and example do you run on your device that you are testing to take leaveng request?

@Toby, Can you elaborate which API in Z-Stack we can send APS remove device command?

Hello Toby Pan & YiKai Chen,

I am using the Z-stack 3.0.2 version SDK (compatile with the Zigbee 3.0) with the CC2538 Zigbee module.
I have tried it with the sample switch application with out doing any modifications.

Still I am getting the same responses as i have mentioned above,

while sending the  ZDO_MGMT_LEAVE_REQ  using the znp host frame work application.

Regard's,
Shiv Patil.

It might take device a while to do restart and erase previous network information from your device. If you wait 10 seconds, do you still see the device can be controlled from your coordinator?

Hello YK,

Yes, I have already waited for a minut..

if you the time stamp in screen shot you will be able to know that.

Is there somthing missing while doing the device remove process?..

have you tried it on your side?

I am still confuse why TI has implemented differnt commands for those applications for removing the device from the network.

Regard's,
Shiv Patil

YK, elaborating on Z-Stack API to remove device: from Zstackapi_* perspective, please see Zstackapi_secApsLinkKeyRemoveReq.

Shiv, please debug and see if the switch enters bdb_setFN in ZDO_ProcessMgmtLeaveReq .

yes, the application code enters in to the void ZDO_ProcessMgmtLeaveReq( zdoIncomingMsg_t *inMsg ) function & it will send response as a command successful.

but still im getting same results when I am trying to do some actuation over it.

I am sending you some screen shot will help you to understand it.

When it hits switch ZDO_ProcessMgmtLeaveReq, does it enters bdb_setFN?

No,

it does not enters bdb_setFN;

if(req.extAddr == NULL) this condition will get fail & then it leave the ZDO_ProcessMgmtLeaveReq function.

Will you please help why it is not entering to the bdb_setFN?

It looks there is something wrong in your extended address of leave command. If you have a look at your sniffer log, it looks incorrect and I suppose that causes the problem.

Hello YK,

I have debug the code & found that, initial zero ( 0x00) digit of  IEEE ID I am was sent by me so that the device will not getting in to the bdb_setFN
after removing that i able to enter int to bdb_setFN fnction. 

the device will response request success status in feed back.

but after that if I am trying to do actuation over it, it still response to that command.

Do you have new sniffer log after you fix extended address on leave command and test again?

Any updates?

Please let us know if you require further support.