unable to rejoin end device

kumar A

Other Parts Discussed in Thread: CC2530, Z-STACK

Hi,

I'm working on CC2530 SEP profile.

Device is able to pair with meter successfully and working fine for some time and device is kept at 30 feet away from meter.

On long run, device got disconnected and unable to rejoin properly. Device will always show device state as end device. And, unable to bind end point with coordinator.

ZDApp_ProcessOSALMsg() is called by zstack library every time, while rejoining with coordinator.

Always rejoining process end up at AF_DATA_CONFIRM_CMD, after three tries. Usually, ZDO_CB_MSG and AF_INCOMING_MSG_CMD should be called, after sending device announce request to the coordinator in the rejoining process.

But, I'm unable to receive announce response, after sending announce request.

I tried to enable join flag on the coordinator side. Even after that, device is unable to pair with coordinator.

But, if I do reset to default. Device is able to pair with coordinator on join flag enable.

Is there any information stored in NV memory, that is creating problem?

Because If I reset, device is able to pair with coordinator. As I know, On reset device NV will be cleared.

Please help me in sorting out this problem. It is very urgent.

Thanks & Regards,

Kumar

over 10 years ago

0 YiKai Chen over 10 years ago

Guru 735685 points

If you can provide full sniffer log for this issue, it should be helpful to verify it.

0 TheDarkSide over 10 years ago in reply to YiKai Chen

TI__Genius 16570 points

Hi,
please attach a comprehensive log which includes the 'disconnect' event as well as the attempt to rejoin.
On device reset, the NV is cleared only if you issued a factory reset, or if you didn't enable NV at all (NV_INIT and NV_RESTORE compilation flags are not defined).

Thanks,
TheDarkSide

0 kumar A over 10 years ago in reply to YiKai Chen

Prodigy 80 points

Hi YK Chen,

As I see the logs, device is sending orphan packet to the ZC. But, ZC is responding with Coordinator realignment packet.

After that, device is unable to get valid short address. Please suggest me, what to be done for fetching valid short address.

Find sniffer logs along with this post.

Thanks & Regards,

Kumar.

Sniffer_logs.psd

0 kumar A over 10 years ago in reply to TheDarkSide

Prodigy 80 points

Hi Yikai,

Please find the above post for logs.

Thanks & Regards,
Kumar

0 kumar A over 10 years ago in reply to TheDarkSide

Prodigy 80 points

Hi,

I have already enabled NV related flag as you mentioned in the post. Still same problem persist.

Please check logs along with this post.

Thanks & Regards,

Kumar.

6153.Sniffer_logs.psd

0 YiKai Chen over 10 years ago in reply to kumar A

Guru 735685 points

Can you also include the process when device joins ZC in your sniffer log?

0 kumar A over 10 years ago in reply to YiKai Chen

Prodigy 80 points

I'm sharing sniffer logs of joining process for another device with same firmware image. Because, I don't want to do reset the device having re-joining problem.

It is very hard to reproduce it. This rejoin problem will occur, when device is receiving low RSSI value.

Usually device will send Beacon request and Association request to ZC in rejoin or join process. But in case of my device, while rejoining device is not sending beacon request to the ZC.

As I debug the code, ZDO_JoinConfirmCB is called immediately after sending orphan packet and setting nwkStatus == Success. So depending on the nwkStatus variable value, beacon will be sent from ZDApp_ProcessNetworkJoin() method.

Please find the logs along with this post.

Thanks & Regards,

Kumar.Join_process_sniffer_logs.psd

0 kumar A over 10 years ago in reply to kumar A

Prodigy 80 points

Hi,

Please check sniffer data in the previous post. And, let me know your opinion on that.

Thanks & Regards,

Kumar

0 YiKai Chen over 10 years ago in reply to kumar A

Guru 735685 points

I cannot find clue on your log. I tried to invite some TI guys to help.

0 kumar A over 10 years ago in reply to TheDarkSide

Prodigy 80 points

Hi,

Can you please help me in sorting out the issue. I'm waiting from long time to fix this.

Thanks & Regards,

Aravind

0 YiKai Chen over 10 years ago in reply to kumar A

Guru 735685 points

As I know, TI is verifying this issue. They told me that they will update it when they finish.

0 kumar A over 10 years ago in reply to YiKai Chen

Prodigy 80 points

Thanks for replying back.

I'm waiting for so long. TI support team hasn't come back on this issue.

It is very urgent for us to fix this problem. And, same problem is seen on some more devices in our testing.

Please help me in fixing this.

Thanks & Regards,

Kumar

0 YiKai Chen over 10 years ago in reply to kumar A

Guru 735685 points

I had tried to contact TI for this and they told me they were still working on it. I think this might be really a difficult issue for them. I would keep asking them and hope them would reply soon.

0 YiKai Chen over 10 years ago in reply to YiKai Chen

Guru 735685 points

Hello TI,
Do you have update about this issue?

0 YiKai Chen over 10 years ago in reply to YiKai Chen

Guru 735685 points

Hello TheDarkSide,
Have you figure out this problem on Z-Stack?

Zigbee & Thread

Zigbee & Thread forum

unable to rejoin end device