SWRA625B August 2018 – February 2020 CC1352P , CC1352R , CC2652P , CC2652R , CC2652R7 , CC2652RSIP
This section describes the software application setup for the measurements (obtained with the measurement setup shown in Figure 2) and how to reproduce it.
The applications programmed on the LAUNCHXL-CC1352P/CC26X2R1 LaunchPads are the Z-Stack 3.3.1 sample applications ZC Light Sink, ZED Switch, and GPD Switch using the Zigbee 3.0 stack. All are included in the Z-Stack examples of the SimpleLink CC13X2/26X2 SDK [5] as described in [6]. Further details about the usage of Z-Stack 3.3.1 and new features can be found in [7].
The idea of this setup is to commission the switch device (ZED) to the light device (ZC) as explained in Section 4.2.5. Typically, commissioning into the network is a one-time operation in the lifetime of the device operation; join the network, then find and store the information about the device it needs to communicate with. Finally after device authentication into the network, the ZED begins polling its parent, in our case the ZC, periodically to determine whether there are pending messages for it. The standby state will be referred to as Operation1, when the device is in sleep mode, or standby mode. The next scenario will be referred to as Operation2, where the ZED polls its parent when there is no data pending on the parent. Finally, the last scenario, referred to as Operation3, describes the situation where the ZED sends an On/Off Toggle command, polls its parent where a message (On/Off Toggle ACK) is pending, received, processed, and acknowledged by the switch application.
NOTE
In the described setup above, the ZED is running the switch application, and the ZC is running the light application, performing a realistic use case with the switch being a battery-powered ZED running Z-Stack, which is polling its parent, sending commands, and receiving acknowledgments.