SWRA625B August 2018 – February 2020 CC1352P , CC1352R , CC2652P , CC2652R , CC2652R7 , CC2652RSIP
Open the workspace file gpd_sw_cc26x2lp.projectspec with the correct version of CCS. The project file is found in the following folder after installing the SimpleLink CC13X2/CC26X2 SDK 3.1.00 [5]:
C:\ti\simplelink_cc13x2_26x2_sdk_2_40_00_81\examples\rtos\CC26X2R1_LAUNCHXL\zstack\gpd_switch\tirtos\ccs
A GPD device is different from the three logical Zigbee devices defined in Zigbee PRO: Coordinator, Router, and End Device. They have a strict energy budget and can only be commissioned into a Zigbee network through a Green Power Sink (GPS) or a Green Power Proxy (GPP). Similarly to a ZED, the GPD does not have some power saving features enabled by default, as it would hinder debugging during the development phase. To enable these features, we must set the correct predefined symbols as well as add several lines of code in the application files described below. As a GPD has very limited power, it uses a stripped down version of Z-Stack compared to a ZED. For detailed information on GPDs, see the Green Power Device Application Overview section in the Z-Stack User's Guide[6].
GPD devices send specific types of data packets, called Green Power Data Frames (GPDF), which are converted by a GPP into Green Power Notifications. As the GPD does not receive ACKs, duplicate GPDFs are typically sent out, where the number of duplicates to send is configured by the predefine symbol GPDF_FRAME_DUPLICATES. The default is 3 duplicates, however, the more duplicates sent out, the more power is consumed. Power measurements taken in Section 5 test both sending 3 duplicates as well as testing with no duplicates sent out.
For modifying the predefined symbols on the device for the GPD projects, see Section 4.2.3. The only additional predefine symbol that needs to be modified is the GPDF_FRAME_DUPLICATES, to the desired number of duplicate GPDFs to be sent.
As the GPD is not part of the Zigbee network the same way as a regular ZED is, no polling is done and does not require any polling configuration.
The next change is changing the TX power level when sending a GPDF. For a GPD project, the TX power level is changed in a different way compared to a ZED. Inside the file Application/gpd_sw.c, near the top, is the CONFIG_TRANSMIT_POWER define. This can be modified to any supported TX power level in dBm, as shown in Figure 8.