Unwanted "Leave" command from coordinator

Hello, I developed for my customer, a ZigBee coordinator in last 2019, using nRF5 SDK for Thread and Zigbee v3.2.0.
Now my customer has this issue:
- End Node connected via router, if router deads, the coordinator rejoin it but after few time send "leave" command to end node
Here attached WireShark log file of ZigBee radio communication
Some details:
- end node has NW address E3DF
- router has NW address D01B
- at line 14631 and following, the router deads
- at line 14680 starting end node routing search
- at line 14747 and followings rejon procedure
- at line 14850 Coordinator sends LEAVE command to end node E3DF

What is happened? Why Coordinator sends "Leave" command?
How can we avoid this unwanted behaviour?

Many thanks for your help!

Abele

Parents Reply Children
  • Sorry, it's summer vacation here also, it's very unlikely someone can look at this until after summer. I strongly recommend updating to test for this issue.

    Kenneth

  • Kennet,

    My customer is very worried, his coordinators is on field form over one year and in last months it have are several cases of this "unwanted leave"
    If this could help, seems that this issue is more frequent when one router dies and the coordinator try to rejon the end node, but really it happens sometime also for other reasons.
    In any case, could you help me to to update to SDK 4.2?
    What and how I have to do?
    How many hard could be?
    Could you suggest some step to do?
    Please note that to develop coordinator I started from CLI example ... there are someone in Nordic that can see my project to suggest best way to upgrade it?

    Many thanks for your patience

    Regards

  • I believe both the nRF5 SDK and T&Z releases should have some migration information in the release notes or as a separate document. Though you may first need to look at the first major release update (e.g. 4.0 or 16.0), since that kind of information is typically there.

    Kenneth

  • Kennet, 
    as you know, the guide is only a brief summary how to migrate standard examples, but in my use case I used CLI example on SDK 3.2 as base for my project, to which I have done a lot changes.
    Then, sure I will read guide, but perphaps I will need technical support by Nordic to best understand and to solve possible difficulties and issues.
    Surely the developer teams has some suggests and indications how to make migration more easily.
    Could I have these helps?
    Thanks

    PS there are chances to migrate only the ZBOSS stack v3.1.0 to ZBOSS stack v3.3.0, and not all SDK?

    Abele

  • ... I taked a look to new SDK 4.2 ... it hasn't IAR EWARM project!!!
    My actual project is under IAR EWARM 8.30

Related