CC2530: Device Leaving with Remove/Leave command from Coordinator or Device

Ajit_Wadekar

Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK, , CC2538, CC2652R

Hello,

I am using Z-Stack HA 3.0.1 with Z-Stack Linux Gateway. Here I am facing a problem where when I try to add new device(complete new/fresh ieee address) to the coordinator using Z-Stack Linux Gateway, my device joins the network and than after few seconds it automatically sends Leave command over the network even if the device is not removed from the network through gateway nor is there any leave send from device though application.

Though if I use some old device(with old ieee address) that sometime back have joined that coordinator but currently is not part of that network and has fresh code in it, the device works perfectly fine i.e. it does not leave the network.

I have attached sniffer data for both the cases, could anyone help me figure out the problem here.

New Device Leave without Remove.zip

Old Device Does not Leave.zip

over 7 years ago

0 Ryan Brown1 over 7 years ago

TI__Guru**** 219997 points

Hello Ajit,

There is no Z-Stack HA 3.0.1, only Z-Stack 3.0.1 or HA 1.2.2a. The only current Linux gateway solution is 1.2.2a pending a 3.0 release coming quite soon. If the gateway is 1.2.2a and the joining device is 3.0 then it will leave the network after a few seconds because it will not receive a TCLK update. If the device is already authenticated on and known to the network then this is a rejoin situation hence no TCLK update is required. Your sniffer logs do not seem to come with the proper NWK key because all packets are encrypted on my end.

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

Dear Ryan,

Yes you are right I am using Z-Stack 3.0.1. By when can we expect the Linux gateway solution 3.0 to available?

Also I checked further, I tried using the same setup i.e ZNP of 3.0 and Linux Gatweway of 1.2.2a, I can add the device to the network but same thing does not happen with my other coordinator. It has the problem I have mentioned earlier. What is the solution for this?

Also my key for now is default as set in

0 Ryan Brown1 over 7 years ago in reply to Ajit_Wadekar

TI__Guru**** 219997 points

You cannot use a 3.0 ZNP with a 1.2.2a Linux Gateway, you need to use the pre-built ZNP firmware that came in the gateway package. Waiting for the web team to publish the new release. What version of Ubiqua are you using? I am still having trouble viewing your sniffer log, you may try starting over and uploading a new one.

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

Dear Ryan,

Its not Ubiqua, it is wireshark file.

Also I am already using 3.0 ZNP with 1.2.2a Linux Gateway and it is working fine.
But I have faced above issue after adding many different devices with different ieee addressess.

Is there any tentative date for New Linux Gateway release?

0 Ryan Brown1 over 7 years ago in reply to Ajit_Wadekar

TI__Guru**** 219997 points

How many devices are in your network? If you have more than NWK_MAX_DEVICE_LIST already joined then your ZNP will start requesting that new devices leave. 3.0 ZNPs are even more limited on the number of devices allowed in the network due to RAM limitations and the additional table requirements for TCLKs and child management per 3.0 specifications. The NWK_MAX_DEVICE_LIST default is 20 for a 3.0 ZNP

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

Dear Ryan,

Currently we have 11 active devices in the network.

But we have been using this network for testing, so we have been adding and removing devices through linux gateway. Can this cause the problem or is there any memory leakage here?

Just to inform we have not modifed the ZNP code.

0 Ryan Brown1 over 7 years ago in reply to Ajit_Wadekar

TI__Guru**** 219997 points

Hi Ajit,

I suppose memory leakage is possible, have you reviewed the following Wiki page? processors.wiki.ti.com/.../Zigbee_Known_Issues_and_Proposed_Fixes

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

Dear Ryan,

On Further testing I think the problem is http://processors.wiki.ti.com/index.php/Zigbee_Known_Issues_and_Proposed_Fixes#ZC_sends_ZEDs_Leave_Reqs_after_MAC_Association

Because the device sends leave command after it requests for the transport key and the key is not sent by the coordinator. The same thing does not happen with old device because that key must be already buffered by the Coordinator.

I have attached the sniffer log for validation.

Device Leave Without Remove.zip

Will this problem be resolved in new Linux Gateway or is it the problem with ZNP on CC2530?

0 Ryan Brown1 over 7 years ago in reply to Ajit_Wadekar

TI__Guru**** 219997 points

Hi Ajit,

I'm glad the Wiki page was able to help, this problem is related to the CC2530 ZNP and will not be addressed in the Linux gateway update.

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

So basically the problem is related to the memory, right?

Also can you give me some suggesion how can I tackle this problem? Which controller/processor should we use in order to solve our memory problem?

0 Ryan Brown1 over 7 years ago in reply to Ajit_Wadekar

TI__Guru**** 219997 points

A lack of space in the network layer data buffers to be exact. The proposed fix has already been provided. You can optimize your flash/RAM usage or upgrade to a CC2538/CC2652R. processors.wiki.ti.com/.../Optimizing_Flash_and_RAM_Usage_of_Z-Stack_for_CC2530

Regards,
Ryan

0 Ajit_Wadekar over 7 years ago in reply to Ryan Brown1

Mastermind 7620 points

Dear Ryan,

Thank you very much for the help. I will look into you suggestion.

Zigbee & Thread

Zigbee & Thread forum

CC2530: Device Leaving with Remove/Leave command from Coordinator or Device