• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 2981 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

The associated device list not appear in z stack 3.0

adrian humanes
Prodigy 230 points
Other Parts Discussed in Thread: Z-STACK

Hi,

I´m using the CC2538DK and I have got an issue with the associated device list (AssocDevList). I'm running the sample switch of z-stack 3.0 and I have configured my application as coordinator. I'm working with z-tool to send MT command. My problem is after joinning a device to my coordinador, when I send a Util Get Device Info command to known the short addrees of ED, associated previously, the AssocDevList is empty. I have checked my device is joined the network becasuse It responds to me when I send it a command to toggle a led. In addition I have set the variable bdb_default_tc_require_key_exchange to True to be able to join my devices.

How could I known the child list of a device?

  • 0
    Guru 735695 points
    Do you have router in your Zigbee network when you add this ZED to network?
  • 0
    Expert 1620 points

    Hi Adrian

    Just to clarify, bdb_default_tc_require_key_exchange is not to allow any device to join the network, it is for mandate the TCLK exchange procedure in which the default key is updated to an unique key.

    If your joining ED is not Z3.0 it will not perform this procedure and will be kicked by the coordinator if bdb_default_tc_require_key_exchange is set to TRUE, if bdb_default_tc_require_key_exchange is set to FALSE, then the device will be allowed to stay.

    Regarding your issue, can you provide a capture log to see what is happening between these devices?

    Hope this helps!

  • 0 in reply to Luis Luna
    Prodigy 230 points
    Hi Luis,

    Thanks for your answer. The first of all, sorry because I wanted to write I had set the bdb_default_tc_require_key_exchange to False to associate my ED which is not 3.0. I wrote it wrong.

    King regards.
  • 0 in reply to YiKai Chen
    Prodigy 230 points
    Hi Yekai,

    Thanks for answering. I have just realized the device, which I was testing ,was a ZR. This device is associated succesfully but not is shown in the AssocDevicesList. Now I have tested with a ED and this whether appear in the AssocDevicesList.

    Why the ZR appear and the ED not?

    King regards.
  • 0 in reply to adrian humanes
    Guru 735695 points
    According to my understanding to implementation of Z-Stack 3.0, it only put ZED to association list.
  • 0 in reply to YiKai Chen
    Expert 1620 points
    Hi guys,

    Just a clafirication, child devices are registered in association list (ZR and ED). One optimization for association list done in Z3.0 is that router devices now expire from the association list as it would do from the neighbor table (by aging), subsequently it would be added to neighbor table if it is discovered again.

    Do you still have a question?
  • 0 in reply to Luis Luna
    Prodigy 50 points
    Hi Luis,

    Can i have more question?
    If ZC is defined NWK_MAX_DEVICE_LIST=10 in Z3.0 environment.
    We have 10 ZEDs to join the network at first, then 5 ZRs will join the network.
    Are all of them can join these network ?

    Thanks a lot!
  • 0 in reply to SamC
    Expert 1620 points

    Hi SamC,

    No, that would not work as the association table would be full, and these entries are used by ZC to allow joining directly to it. If you have those 10 entries already used by ZED and you open the network, you would see the permit joining bit set to TRUE in the beacon, but the device capacity set to FALSE, which means that other router devices in the network can allow new devices to join it, but if there is no other routers that can take those new devices, then the network cannot grow, unless that one of the ZED is expired from the coordinator and then releases an entry in the assoc table.

    Let me know if this address your question.

  • 0 in reply to Luis Luna
    Prodigy 50 points
    Hi, Luis,

    Thanks for the detail description. Now I have more clearly to know what Z3.0 is.
    So if I want to know which one are connected to ZC.
    1. I must check associated table for ZED, then check neighbor table for ZR.
    " associated table + neighbor table = NWK_MAX_DEVICE_LIST." Is it right?
    2. What is suitable MT CMD for query neighbor table ? ( ZDO_MGMT_LQI_REQ? or ...)

    Thanks.
  • 0 in reply to SamC
    Genius 3415 points
    Hi SamC,

    That's correct, ZDO_MGMT_LQI_REQ retrieves the information of the neighbor table.

    Regards