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.

CC2538: znp 3.0.1 ZDSECMGR_TC_DEVICE_MAX issue

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK

Hello,

starting from the original znp project for the CC2538 from the z-stack 3.0.1, i tried to increase the ZDSECMGR_TC_DEVICE_MAX define in order to allow more devices to join the network. I noticed that setting this value to 150 caused the firmware to become unstable. To be more specific, every time i reset the coordinator the network PAN ID changes, losing all connection to the previous connected nodes. Trying with a different value of ZDSECMGR_TC_DEVICE_MAX caused also the coordinator to emit all beacons with "no router capacity" and "no end device capacity" attributes, even though no device was connected.

Was the cc2538 znp project ever tested with these kind of values for the define ZDSECMGR_TC_DEVICE_MAX? Can the znp support more than 100 zigbee 3.0 devices?

Best Regards,

Daniele Coati

  • Daniele,

    I recommend you look at this page to help out with your parameters. dev.ti.com/.../network_configuration.html

    EDIT: To answer the question, the ZNP should most certainly support more than 100 zigbee 3.0 devices, as we have run tests with the ZNP with much more than 100 devices.


    Best,
    Sean

  • Sean,

    thanks for the feedback. I am familiar with the network parameters available for the z-stack, but do you have any feedback on the issues i am encountering while increasing the ZDSECMGR_TC_DEVICE_MAX define? Because i can maybe connect more than 100 devices, but when i turn off and on the coordinator the pan id changes by itself (even though it should restore the network) and the connection with the other nodes is lost.

    Considering you made some tests, can you maybe share more information on the other network parameters that i need to change (or other changes in the original zstack 3.0.1 znp build) in order to allow such number of devices?

    Best regards,

    Daniele Coati

  • You can try to follow these settings:

    (For ZC only)
    ZDSECMGR_TC_DEVICE_MAX=100 (or to number of Zigbee 3.0 devices you wish to allow onto the Zigbee network)
    NWK_MAX_DEVICE_LIST=10 to save RAM, this is number of childrencoordinator allows
    CONCENTRATOR_ENABLE=1
    CONCENTRATOR_DISCOVERY_TIME=120 (establish a route request every 120 seconds)
    MAX_ROUTING_SRC_ENTRIES=120 (should equal the max number of nodes in the the network)
    SRC_ROUTING_EXPIRY_TIME=2 (time which the route is valid in src routing table)
    CONCENTRATOR_ROUTE_CACHE=1 (set to TRUE)
    MTO_RREQ_LIMIT_TIME=5000 (Limits route request storm)

    (For ZC & ZR)
    LINK_DOWN_TRIGGER=12
    NWK_ROUTE_AGE_LIMIT=30
    BCAST_DELIVERY_TIME=100
    DEF_NWK_RADIUS=15
    NWK_ROUTE_AGE_LIMIT=30
    DEFAULT_ROUTE_REQUEST_RADIUS=8
    ROUTE_DISCOVERY_TIME=13
    ZDNWKMGR_MIN_TRANSMISSIONS=0
    NWK_LINK_STATUS_PERIOD=15

    (For ZR Only)
    MAX_NEIGHBOR_ENTRIES=48

     


    EDIT: Daniele,

    Apologies in advance for telling you all these settings to try. I just attempted to try the same thing on my end with a CC2538 on Z-Stack 3.0.1, by both changing ZDSECMGR_TC_DEVICE_MAX to 150 as well as keeping it at the default. However, both times I saw that the pan ID was different as you had seen, as well as the network frame counter on the ZC was ~1000 more than what it was when the device reset, probably pointing to corruption somewhere. I am looking more into this now.




  • This issue is related to the issue in Known Issues & Proposed Fixes (processors.wiki.ti.com/.../Zigbee_Known_Issues_and_Proposed_Fixes) and using the suggested fix, I can confirm it does fix the issue of the Pan ID now properly setting correctly.

    Best,
    Sean

    EDIT: Fixed link

  • Sean,
    thank you for taking the time to reproduce the problem on your end, but i didn't get the specific known issue you are referring to. Can you point me to the one that solves the problem?

    Best Regards,
    Daniele Coati
  • Oops! Looks like it included a parenthesis in the link when it shouldn't have. I've modified the link in the post above :)

    However, the issue is titled 'IEEE_Address_of_CC2538ZNP_is_reported_incorrectly'.
  • Hi Sean,
    i flagged your answer as resolved by mistake, but even by applying the fix I still have the same problem. I noticed that now the IEEE address is reported correctly over the air, but the coordinator still changes its PAN ID when i reset it.

    Looking forward to your feedback.
    Best Regards,
    Daniele Coati
  • If you're using the ZNP example from the SDK and applied the fix you should see that both the IEEE address and Pan ID are the same after resetting the device and after you restore the network (After a System Reset, you must send another APP_CNF_START_COMMISSIONING request with CommissioningMode 0x00. You will see:

    <RX>08:16:45.4 COM42 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x0D (Network Restored) (0xD)
    Commissioning Mode: 0x00 (Initialization) (0x0)
    Commissioning Mode: 0 (0x0)

    For my device, the PAN_ID was 0x2280, so after I restored the network, I sent a ZB_GET_DEVICE_INFO to see the PAN_ID, and was able to see that the PAN_ID is set properly.

    <TX>08:17:05.82 COM42 ZB_GET_DEVICE_INFO (0x2606)
    Param: PAN_ID (0x6)

    <RX>08:17:05.83 COM42 ZB_GET_DEVICE_INFO_RSP (0x6606)
    Param: 0x06
    Value: ."...... (0x80, 0x22, 0x01, 0x08, 0x00, 0xFF, 0xFD, 0xD1)

    Best,

    Sean