SWRA650B April   2019  – February 2020 CC1352P , CC1352P7 , CC1352R , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP

 

  1.   Z-Stack Large Mesh Network Performance Using the SimpleLink Wireless MCU Family
    1.     Trademarks
    2. 1 Introduction
    3. 2 Network Topology
    4. 3 Stack Configurations
    5. 4 Test Procedure and Results
    6. 5 Summary
    7. 6 References
  2.   Revision History

4 Test Procedure and Results

The test was run for one days (24 hours or 1440 minutes) on channel 22 with each ZR and ZED sending application frames 68 bytes in length to the ZC every 4 minutes (720 packets per device over the entire test period). Before starting, each device was flashed with its corresponding firmware. The ZC then began by creating the network. ZR devices were joined in the zone for which they were designated, with a black list implementation from the ZC used to enforce proper assignments. After the link status of every ZR was checked to ensure the correct zone topology, the ZEDs were joined by proximity to the zone for which they were intended. After the network was fully situated, each device was enabled to start sending application data to the ZC.

The ZC kept a full log of the source and contents of each report that it received. PER and latency results were then produced from the information and are provided in Table 2.

Table 2. Z-Stack 3.5.0 Large Mesh Network Test Results

Number of Hops From ZC Final Number of ZEDs Average Packet Error Rate (%) Average Latency (ms)
1 23 0.00 40
2 10 0.00 60
3 9 0.00 82
4 9 0.00 104
5 11 0.00 160

The results presented were obtained with all devices within close proximity (less than one and half meters) from a clean radio lab environment in Dallas, Texas. Network performances can vary depending on a wide number of interference sources, both physical and electrical, as well as the range between nodes. Evaluation of 2.4 GHz frequency channels should be performed to further understand the communication traffic sustained by other existing sources. Similar or comparable results cannot be expected if subjected to factors which could easily influence network operation.

Packet Error Rates were calculated based on reception of an APS acknowledgement from the destination device. The device from which the packet originated will wait the full APSC_ACK_WAIT_DURATION_POLLED (default 6 seconds) before re-attempting to send the application packet up to APSC_MAX_FRAME_RETRIES (default 2). If no APS ACK is returned then the Stack will report a ZApsNoAck status on the sending device, which in this test is the Zigbee Coordinator. For more information, see the the End-to-End Acknowledgements section of the Z-Stack User's Guide[3].