End device rejoin issue

LAKSHMANAN KUMAR RANGARAJ

Expert 1795 points

Other Parts Discussed in Thread: PMP, Z-STACK

Hi TI,

I found issue on end device rejoin to coordinator.

I am switch on the Coordinator and end device.

After some time Switch OFF the coordinator let say for 2 minutes.( using the same PANID)

Then switch ON the Coordinator(same PANID) the end device wont rejoin at all.

it always send beacon request.

and coordinator responds with superframe structure.

How to solve this issue? kindly advise

Thanks and Regards

Lakshman,PMP,PMI-RMP

over 14 years ago

0 LAKSHMANAN KUMAR RANGARAJ over 14 years ago

Expert 1795 points

Hi TI

Any support ?

Thanks and Regards

Lakshman,PMP,PMI-RMP

0 Felix Bruckmüller over 14 years ago in reply to LAKSHMANAN KUMAR RANGARAJ

Intellectual 835 points

Hi,

I have the same problem with some of my devices, did you find a solution?

Thanks

Felix

0 YiKai Chen over 14 years ago in reply to Felix Bruckmüller

Guru 735705 points

Me too. Suffer the same problem. Can any TI Employee try to find a solution?

0 jie liao over 12 years ago in reply to YiKai Chen

Intellectual 295 points

me too TI help me ~~~

0 felix shih over 11 years ago in reply to YiKai Chen

Prodigy 100 points

Hi, YK Chen,

Do you find the solution for this problem?

My ZED just send "Beacon Request", and does not send "Rejoin Request" in normal condition.

I use Z-Stack HA 1.1.0.

According to ZDApp.c, in case ZDO_NWK_DISC_CNF:

Should it call NLME_ReJoinRequest() in this condition?

            // Perform Secure or Unsecure Rejoin depending on available configuration
            if ( ZG_SECURE_ENABLED && ( ZDApp_RestoreNwkKey() == TRUE ) )
            {
              rejoinStatus = NLME_ReJoinRequest( ZDO_UseExtendedPANID, pChosenNwk->logicalChannel);
            }
            else
            {
              rejoinStatus = NLME_ReJoinRequestUnsecure( ZDO_UseExtendedPANID, pChosenNwk->logicalChannel);
            }

0 YiKai Chen over 11 years ago in reply to felix shih

Guru 735705 points

You can try to use Z-Stack HA 1.2.1 and enable CHILD_AGING.

0 Cetri over 11 years ago in reply to felix shih

TI__Genius 9325 points

Hi felix,

Is compiler option NV_RESTORE defined on the ZC? What about Association Permit bit in the Beacon from the ZC after it restarts?

Sharing the sniffer capture here will be helpful for other community members to figure out the issue more precisely.

- Cetri

0 felix shih over 11 years ago in reply to Cetri

Prodigy 100 points

Hi Cetri,

According to your suggestion, I add NV_RESTORE option to ZC. For now, ZED sends “Rejoin Request”, but it rejoin ZC sometimes success and sometimes fail.

My test scenario is ZC always power on, just take ZED out of RF coverage to make it orphan, and then take ZED closer to ZC to make it rejoin. I do not know why I need to set NV_RESTORE to ZC, ZC is never power off.

The attach is sniffer log and Association Permit bit is NO, because ZC permitJoin is set to disable now.

Can you give me some advice?

2678.ZED_rejoin_fail.zip

0 YiKai Chen over 11 years ago in reply to felix shih

Guru 735705 points

Hi felix,

When you do the test, do you revise anything on Z-Stack?

0 Mark V over 11 years ago in reply to YiKai Chen

Prodigy 90 points

Hi,

We can reproduced an issue with ZStack Home 1.2.0 where an end device secure rejoin when the coordinator parent's PermitJoin is false will cause the child to be deleted from the parent's Association List. This leaves the end device data requesting the parent, but breaks comms from the parent to the child - when you try to send a message to the child the parent will do a route request.

I'm not sure if it is fixed in Home 1.2.1, or if it occurs with router parents.

It's been reported with logs to TI but i dont have an issue number.

Good luck!

Mark

0 YiKai Chen over 11 years ago in reply to Mark V

Guru 735705 points

Hi Mark,

Same question, When you do the test, do you revise anything on Z-Stack?

0 Mark V over 11 years ago in reply to YiKai Chen

Prodigy 90 points

Hi YiKai,

We are confident it is not something we introduced (although do have a lot of proprietary patches), but i have not had the time to reproduce the issue with a sample application based on a clean stack. We have provided clear steps to reproduce, proposed a patch and are moving on.

Mark

0 YiKai Chen over 11 years ago in reply to Mark V

Guru 735705 points

Hi Mark,

Thanks for the clarification. Do you mean you propose a patch to fix this? If so, can you share with us?

0 Cetri over 11 years ago in reply to felix shih

TI__Genius 9325 points

Felix,

You are right. If you don't power cycle the ZC, NV_RESTORE will not make any difference.

In your sniffer log, there is no MAC Ack in response to Rejoin Req. That means the ZC didn't hear the messages or didn't have enough memory to accept the Rejoin Req command. I would focus more on memory issue than on radio issue(TX power / RX sensitivity) because the ZC responded to Beacon Req. Can you check if there is any possibility of memory leak or temporary out-of-memory situation in your code?

By the way, I think what you want is to make ZED retry again and again until it successfully rejoins. Can you please add some lines(marked '+' in the beginning of each line) in ZDApp_NetworkInit() and test?

void ZDApp_NetworkInit( uint16 delay )
{
+  if ( devStartMode == MODE_REJOIN )
+  {
+    _tmpRejoinState = true;
+  }
  
  if ( delay )
  {
    // Wait awhile before starting the device
    osal_start_timerEx( ZDAppTaskID, ZDO_NETWORK_INIT, delay );
  }
  else
  {
    osal_set_event( ZDAppTaskID, ZDO_NETWORK_INIT );
  }
}

- Cetri

0 felix shih over 11 years ago in reply to Cetri

Prodigy 100 points

Hi, Cetri,

Your solution is right, ZED rejoin success now every time.

ZED : modify ZDApp_NetworkInit() as your suggestion.

ZC : unchanged.

Thanks for your help.

0 shekhar shakti78 over 11 years ago in reply to felix shih

Intellectual 595 points

When I restart the ZED It is not able to rejoin the ZC with which it was connected earlier.

I need some idea to do that.

Regards

0 YiKai Chen over 11 years ago in reply to shekhar shakti78

Guru 735705 points

Hi SS,

Do you enable NV_RESTORE?

0 The Seven over 10 years ago in reply to Cetri

Guru 11440 points

Hi Cetri ！
i am using the Zstack HA1.2.2a ， i always encountered ZED could not rejoin the network。
and i have not saw above code was add in the new version of zstack。

could you please tell me is this patch update in Zstack HA1.2.2a

BR!

0 The Seven over 10 years ago in reply to Cetri

Guru 11440 points

Hi Cetri
this patch does not work in HA1.2.2a.
it doesn't slove the issue of ZED rejoin failed !!!

BR!

Zigbee & Thread

Zigbee & Thread forum

End device rejoin issue