• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 56 subscribers
  • Views 540 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2530: ZED proper join procedure, and rejoin.

Arkadiusz Gibes61
Prodigy 150 points
Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

Hi


I made a application based on TIs example codes and it works somehow, but it seams to have some instability issues. My stack is: Zigbee2mqtt + ZC based on cc2530+ ZED based on cc2530 Currently my end device uses IAS Cluseter to provide main functionality. Device is working, i had to play a bit to get enrollement working but it works. However there is an issue when my end device losse its parent device ie. coordinator goes down for some reason. When ZED  change parent to some router device that is near it's no more accessible when coordinator device brings back. It looks like some routing problem. As i know zigbee2mqtt has its joined device database, so i guesse it should be able to discover route to the joined devices in some magic way. I have simple logic to schedule event that triggers joining after ZED boots up. To join the network im calling  bdb_StartCommissioning(BDB_COMMISSIONING_MODE_NWK_STEERING) function, the question is, is this a correct way to proceed with joining of the end device ? If there is someone who could explain me a bit how the proper procedure/scenario for automatic join + rejoin should looks like i would be grateful.

Best regards

Arkadiusz

  • 0
    Guru 735625 points

    Basically, Z-Stack 3.0.2 end device would do rejoin automatically every 10 seconds when it loses network connection. You don’t have to do anything in your application unless you want to change the rejoin period.

  • 0 in reply to YiKai Chen
    Prodigy 150 points

    how about joining the network ? Is it correct to call bdb_StartCommissioning(BDB_COMMISSIONING_MODE_NWK_STEERING) to join network after boot up of the end device to get auto join functionality ?

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    Yes, it is correct.

  • 0 in reply to YiKai Chen
    Prodigy 150 points

    and how about the newtwork in case where coordinator will die ie. cause of power loss ? Will it work properly after coordinator comes back to life ? From my observation i can say that it doesn't work. My end devices are no longer avilable after ZC boots up again. Any hints to this ?

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    As I replied, end device should join automatically when ZC is back. If it doesn’t happen in your case, I suggest you to use sniffer to check what happens over the air.

  • 0 in reply to YiKai Chen
    Prodigy 150 points

    This is what happens when my end device loss its parent. It starts to send data requests to 0xfffe. The ZC seams to respond on that with some broadcasts, any hints what i should look for ?

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    Those are MAC layer retries. What are you actually looking for?

  • 0 in reply to YiKai Chen
    Prodigy 150 points

    The problem is, that after parent loss i can't communicate to the end device anymore. It looks like it can't change the parent ? Im looking for any hint where i could start debugging to solve this problem.

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    After power cycling your Zigbee2mqtt + ZC based on cc2530, would it keep previous network and don’t start new one?

  • 0 in reply to YiKai Chen
    Prodigy 150 points

    I think it does I have fixed PAN ID on both of the devices, ZC and ZED. I saw yesterday that sometimes my coordinator works after it comes back. In this scenario when I would unplug the router device which is parent of my ZED after ZC is available again, my ZED is no longer available in the network. I presume that as the coordinator is alive again, my end node should change its parent back to ZC right?

    So the sequencs of lifecycle of the devices are:

    ZED , ZC up

    ZED joins the network using coordinator as a parent

    Router up

    ZC - power down

    ZED - switch its parent to coordinator

    ZC - power up

    ZED - is working because it switch its parent to some router device

    Now router goes down.

    ZED is no longer avilable in the network. On the screenshot from yesterday you can see the place where it happens.

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    Yes, ZED should rejoin ZC as its new parent node when ZR is turned off.

  • 0 in reply to YiKai Chen
    TI__Guru**** 212077 points

    Make sure that the ZC shows the same PAN ID when it comes back online.  Does the ZC respond to the ZED's Beacon Request (after entering an orphan state) and Network Rejoin (if one is provided)?  Please provide the full sniffer log if possible.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 150 points

    Hi.

    Here is my full sniffer log. In text file, and on the screenshots. I can see that i got some Beacon response from the ZC but this is all. I also tried to use ext pan id but it didn't change anything.

    sniff_output.txt

  • 0 in reply to Arkadiusz Gibes61
    Guru 735625 points

    Can you attach sniffer log in pcapng format?

  • 0 in reply to Arkadiusz Gibes61
    TI__Guru**** 212077 points

    Hi Arkadiusz,

    Thanks for providing what we asked for.  Based on the sniffer log, this appears to be an issue with the ZED as it does not send a Rejoin Request after getting a Beacon Response from the ZC.  Are you using a TI-provided example (clarify which) and what modifications have been made?  It appears that a ZR is not required to replicate the issue but this is not expected behavior from typical Z-Stack 3.0.2 operation.  If you can debug the ZED please try to determine if bdb_rejoinNwk is entered inside ZDApp.c and why ZSuccess is not returned.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 150 points

    Thanks Ryan! It works. That was what i was looking for. I didn't know where to start debugg...  The problem was that i modified part of logic that was responible for the buttons/interrupts and There is a code that restores network parameters. It was triggered all the time. Now everything works perfect. Thanks!