Texas Instruments™ CC13x2 and CC26x2 devices are part of the SimpleLink™ microcontroller (MCU) platform. Zigbee based applications can be developed on these devices using the TI Z-Stack included with the SimpleLink™ CC13x2 and CC26x2 software development kit (SDK). This SDK includes everything needed to develop Zigbee certifiable solution including tools, application examples, documentation and source code. It uses Zigbee 3.0, the latest specification from the Zigbee Alliance which unifies former application segments under a common certification process. The following sections intend to give users an overview of all of the new features introduced in the Zigbee 3.0 specification.
At the core of Zigbee 3.0 is the Zigbee PRO 2017 (R22). Note that previously Zigbee Pro 2015 (R21) was required for Zigbee 3.0, which has now been replaced with the newer Zigbee Pro 2017 (R22) specification. Older implementation based on the R21 specification are still compatible with the new R22 specification.
The Zigbee PRO Specification adds child device management, improved security features, and new network topology options to Zigbee networks. Commissioning devices into networks has also been improved and made more consistent through Base Device Behavior (BDB). Zigbee 3.0 furthermore requires Green Power Basic Proxy v1.1.1 functionality in all devices to further support Green Power capabilities and compiles all profile clusters into a single specification, Zigbee Cluster Library (ZCL) v7. Finally, it formalizes common Zigbee device application architecture nomenclature, expands on the Zigbee Lighting & Occupancy Device Specification, and comments towards Zigbee 3.0 certification. The following sections address each of these attributes.
Zigbee PRO (2015/2017) includes the formal set of rules that all software solutions must adhere in order to become a ZCP through the Zigbee Alliance, a highly sought-after certification that ensures interoperability between devices. The following are new features that have been added to the Zigbee 2015/2017 specification that developers should be aware of. Full details can be acquired through the Zigbee PRO specification documentation and also through the Zigbee Alliance website.
Child management is a procedure for which parent devices must now age out neighbor table entries for unresponsive end device children by a pre-configured default timeout. This aging timeout can be changed per end device upon request from that end device using the End Device Timeout Request command. MAC data polls are sent from a child end device to reset the parent's aging counter. But once the timeout value is exceeded and the child is aged out, the parent will send the device a Leave Request with the rejoin attribute set so that the device may be allowed to rejoin the network through a new parent device.