• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 56 subscribers
  • Views 306 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.

CC2652P7: How to configure CC2652P7 ZC and CC2652P ZR to support 256-node Zigbee network?

user4166295
Prodigy 40 points
Part Number: CC2652P7
Other Parts Discussed in Thread: Z-STACK, , CC2652P

Tool/software:

Hello TI Support Team,

I am building a Zigbee network using Z-Stack with the following setup:

  • Coordinator (ZC): CC2652P7

  • Routers (ZR): CC2652P

  • Zigbee SDK: simplelink_cc13xx_cc26xx_sdk_8_30_01_01

Network Design:

I want to support a total of 256 devices, arranged in a hierarchical router topology:

  • The ZC will directly manage 32 first-level routers (ZR level 1).

  • Each first-level router will manage up to 32 second-level routers (ZR level 2).

  • All devices are routers (no end devices).

  • No binding or group messaging is required.

Questions

  1. Does CC2652P7 have enough RAM to handle 32 routers directly and indirectly route 256 nodes?

  2. How should the ZC and ZR be configured to support a 256-node hierarchical Zigbee network, where the ZC manages 32 first-level routers and each router manages up to 32 second-level routers??

Thank you for your support!

  • 0
    TI__Guru**** 218207 points

    Hello,

    Please see this relevant E2E thread.

    1. TI has not tested a similar large network with this device, and the answer will depend greatly on Zigbee network configurations (i.e. MTO routing option, routing table sizes, etc.) although it appears that your requirements are minimal.  If you find the CC2652P7 to be insufficient then the CC2674P10 will be a pin and software compatible option with more Flash and RAM.
    2. You can refer to the Z-Stack API for software-level configuration options.  Organizationally you can use Zstackapi_ZdoMgmtPermitJoinReq() and zstackmsg_CmdIDs_DEV_PERMIT_JOIN_IND to influence which routers join through another routing or the coordinator device by only allowing for joining on one routing device at any given time.  The greater concern may be that the source Z-Stack library implements self-healing on the mesh topology and may be subject to change if routers become insufficient or fall off the network.  This, combined with issues spawned from large network reporting and broadcast across several nodes and hops, is why "having multiple Zigbee networks using ZC gateways which report to the same IoT service" may be a more feasible approach.

    Have you considered non-sleepy ZED which only report to one parent ZR but can still receive network broadcast messages and unicast messages without first sending a data request?  

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 40 points

    I have configured the ZC and ZC as per the AN123 guide – AN123 – Breaking the 400-Node ZigBee® Network Barrier With TI’s ZigBee SoC and Z-Stack Software. The number of connections in the network is limited to a maximum of 74 routers, but according to the documentation, the network can support more than 400 nodes. Do I need to configure any additional parameters, such as the size of the table or any other settings that need to be adjusted? The parameters I have currently configured are as follows:

    ZC Config

    • MTO_RREQ_LIMIT_TIME = 5000

    • MAX_DEVICE_TABLE_ENTRIES = 128

    • NWK_LINK_STATUS_PERIOD = 30

    • ZDNWKMGR_MIN_TRANSMISSIONS = 0

    • ROUTE_DISCOVERY_TIME = 13

    • DEFAULT_ROUTE_REQUEST_RADIUS = 8

    • DEF_NWK_RADIUS = 15

    • BCAST_DELIVERY_TIME = 100

    • NWK_ROUTE_AGE_LIMIT = 30

    • LINK_DOWN_TRIGGER = 12

    • CONCENTRATOR_ROUTE_CACHE = true

    • CONCENTRATOR_ENABLE = 1

    • SRC_RTG_EXPIRY_TIME = 2

    • CONCENTRATOR_DISCOVERY_TIME = 120

    • MAX_RTG_SRC_ENTRIES = 320

    ZR Config

    • MAX_DEVICE_TABLE_ENTRIES = 128

    • CONCENTRATOR_ENABLE = 0

    • NWK_LINK_STATUS_PERIOD = 30

    • ZDNWKMGR_MIN_TRANSMISSIONS = 0

    • ROUTE_DISCOVERY_TIME = 13

    • DEFAULT_ROUTE_REQUEST_RADIUS = 8

    • DEF_NWK_RADIUS = 15

    • BCAST_DELIVERY_TIME = 100

    • NWK_ROUTE_AGE_LIMIT = 30

    • LINK_DOWN_TRIGGER = 12

    • MAX_NEIGHBOR_ENTRIES = 48

    Thanks,

  • 0 in reply to user4166295
    TI__Guru**** 218207 points

    AN123 was developed using Legacy CC25XX products using an archived and customized Z-Stack HA 1.2 stack specification in 2014.  There are changes within the SimpleLink F2 SDK solution and Z-Stack 3.0 specification which will not directly apply.  A more recent Zigbee Large Network Application Report is SWRA650 and even here there will be changes to the definition names and locations.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 40 points

    1. I have configured the parameters for the ZC (CC2652P7) and ZR (CC2652P) according to SWRA650, but the network can only connect up to 47 nodes.

    2. My application controls street lights, which are arranged in a straight line with 35 meters between each. Therefore, I plan to configure 1 ZC and all the nodes as ZR. With a requirement of 256 ZR nodes, what parameters do I need to adjust for a network consisting of 1 ZC and 256 ZRs?

    3. I have a question: according to SWRA650, both ZC and ZR are configured with NWK_MAX_DEVICE_LIST = 6. As I understand it, a ZR can manage 6 ZEDs. So does that mean a ZC can manage 6 ZEDs or 6 ZRs?

    Thanks,

  • 0 in reply to user4166295
    TI__Guru**** 218207 points

    Your network will need to modify stack configurations so that it meets the needs of your network topology requirements.  Here are several E2E threads which further explain NV data, maximum device allocations, etc.

     CC2652RSIP: Increase NWK_MAX_DEVICE_LIST in zc_thermostat_sink_LP_CC2652RSIP_tirtos_ccs example 
     CC2652P: How many child devices can the coordinator allow to join the network? 
     CC2652P7: Maximum number of nodes information in NV 
     CC2652P: Maximum number of hops in a straight line of routers 
    LP-CC2652R7: Zigbee: Limiting maximum number of nodes in ZC network. 

    Regards,
    Ryan 

  • 0
    Genius 4180 points

    Does a CC2652P7 coordinator control 256 CC2530s? It should be OK. Is it not possible to poll and send data?You are so complicated, remove the route and use only one coordinator

  • 0 in reply to whong zhao
    TI__Guru**** 218207 points
    whong zhao said:
    Does a CC2652P7 coordinator control 256 CC2530s

    As it concerns memory allocation, the CC2652P7 can host a Zigbee network of 256 nodes, whether they are CC253X, CC26X2, CC26X4, CC23XX, or CC27XX.  However there will be physical limitations (i.e. broadcast storms, channel noise, etc.) which makes maintaining such a network more difficult.

    whong zhao said:
    Is it not possible to poll and send data

    It is, however packet throughput (i.e. multiple devices reporting to the same node simultaneously) can create issues given NWK data buffer allocations.

    whong zhao said:
    You are so complicated

    256 nodes is a fitting requirement for which to provide both advisories and cautions.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 4180 points

    Thank you

     I prepare to use a ZC with 100 ZEDS