• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 475 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: Implementability analysis，A coordinator, device that requires routing mode.

whong zhao
Genius 4180 points
Part Number: CC2652P7
Other Parts Discussed in Thread: CC2674P10, CC2652P, CC2530, Z-STACK

Tool/software:

Hello​

Feasibility Analysis: 500 Powered Devices in a 3m×5m Room Using Zigbee Communication to Transmit Status Within 20 Seconds​

​Configuration:​​

  • ​Single Coordinator:​​ CC2652P7
  • ​500 Devices:​​ CC2652P2 (all configured as ​router mode, forming a ​mesh network

Thank you 

  • 0
    Genius 4180 points

    Add to that all data is live, and 500 devices do not interact and are only sent to the coordinator. The time-lapse requirement is to send all device statuses one after another in about 20 seconds.

  • 0
    TI__Guru**** 219527 points

    Hello whong,

    The following statements seem to be contradictory (i.e. 500 ZEDs in a star network could be advantageous):

    whong zhao said:
    all configured as ​router mode, forming a ​mesh network
    whong zhao said:
    500 devices do not interact and are only sent to the coordinator

    Such a large network has not been tested by TI internally.  The CC2652P7 may have enough RAM and flash to store 500 separate device entries, but if not then the CC2674P10 would certainly be suitable.  Most of the issues involve physical limitations of Zigbee protocol.  Even if perfectly staggered then messages are being sent to the ZC every 40 ms (20 seconds divided by 500) which have to be MAC ACKed and hopefully not APS ACKed. This does not yet consider the occasional Link Status packets broadcast to the network (default intervals of 15 seconds) which each ZC/ZR uses.  Additionally, Zigbee throughput is limited to 250 kbps.  There are packet interval and network configuration changes necessary to accommodate such a large network.  In some cases, having multiple Zigbee networks using ZC gateways which report to the same IoT service is able to solve large network and device reporting concerns.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 4180 points

    Hello  Ryan

    I just mentioned mesh. Is there any problem with the following method corresponding to zigbee communication? The coordinator uses CC2652P+STM32, 2652 to perform serial port transit transmission, and then the terminal device only sends data to the coordinator. The same structure uses stm32+cc2530. Now 500 devices are divided into 100 groups, each with 5 units. Each 5 units send data to the coordinator at the same time, each group is assigned a 50ms window, the interval between groups is 0ms (continuous sending, maximizing efficiency), 100 groups × 50ms = 5000ms, how is this feasibility.

       Thank you

  • +1 in reply to whong zhao
    TI__Guru**** 219527 points

    If the coordinator is now tasked with processing 5 radio packets every 50 ms (i.e. 10 ms per packet) then this is even faster than originally proposed.  It appears that data packets must also be transferred serially at the same rate.  Then there are other routing maintenance tasks (Route Requests, Link Status, and other processing) which must be performed by the ZC.  It should be possible for you to run a quick test with 5 devices connected to the ZC which are sending radio packets every 50 ms, and by adhering to your application requirements as much as possible you will determine whether the ZC can at least keep up with the packet frequency.  Once again, 500 devices in a Zigbee network is feasible in theory but includes more difficulty when practically implementing. 

    Regards,
    Ryan

  • +1 in reply to Ryan Brown1
    Genius 4180 points

    Thank you. I'll need to consult in more detail later. Since there are no other routing devices available, is it possible to disable certain protocols?

  • 0 in reply to whong zhao
    TI__Guru**** 219527 points
    whong zhao said:
    is it possible to disable certain protocols

    The SimpleLink F2 SDK Z-Stack solution is highly configurable, however it does adhere to the Zigbee R22 Specification with backwards compatibility for older Specifications.  The answer would depend on what specifically you are seeking to disable.

    Regards,
    Ryan