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: Zstack

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

Tool/software:

Issue: A  Client (CC2531 Dongle device)  auto disconnect to Coordinator (CC2530F256 device) after connected for a while
Would you please tell me how to fix the auto disconnect issue

1. CC2530F256 device : 

        - use TI Z-Stack 3.0.1 software,

         - configure  a Device  as  a Coordinator

2. CC2531 Dongle device:

         - run Simulator software

         - configure a device as a Client

After starting Simulator, it connects successful to a Coordinator

A Client connects for a while then  a Client (CC2531 Dongle device)  disconnects by itself

Thanks

  • Hi oanh,

    We would need a sniffer log of the over-the-air packets and information about the Z-Stack 3.0.1 firmware configuration to know more about what occurred.  Does the dongle device disconnect occasionally or always, and does it always occur around the same time after joining?  How long does it take to disconnect?  Are there any other devices in the network, and if so then how many?

    If the dongle device is using a legacy Zigbee Specification (ex. HA 1.2) then you will need to make sure that BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE is set to FALSE as the TCLK exchange is only a Zigbee 3.0 feature.

    Regards,
    Ryan 

  • Device always disconnects after connecting for a while (couple minutes), It takes random time (minutes) to disconnect after connects. in the logs I see there are other devices (2 devices).
    would you please let me know how to verify the dongle device is using a legacy Zigbee Specification (ex. HA 1.2) ?
    thanks

  • It looks like the ZC is sending a leave and disconnecting in less than 10 seconds from the dongle device attempting to join (value of BDBC_TC_LINK_KEY_EXANGE_TIMEOUT by default is 5000 ms).  

    You're going to know it's a HA 1.2 device by it not initiating a TCLK exchange procedure(there should be APS packets representing this immediately after the ZC sends the network key upon association).

    You really should be using Packet Sniffer 2 and Wireshark to sniff Zigbee 3.0 packets.

    Regards,
    Ryan

  • Thank you so much for your help
    I update code to
    #define BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE                FALSE

    Verify the change with sniffer, Still have the auto Disconnect issue

    attached is sniffer log
    Coord-disconnect4-TC_REQUIRE_KEY_EXCHANGE-False-.psd



    Would you please tell me where can I get Packed Sniffer 2?

    Thanks

  • Sorry, It is working now.
    Thank you so much for your help