Green Power Attribute Reporting

• Introduction
• Software Prerequisites
• Functional Description
  • Software Overview
    • Application Files
• Configuration With SysConfig
• Example Usage
  • Buttons
  • Commissioning the Device Into the Network

Introduction

This document discusses how to use the Green Power Attribute Reporting Application and the different parts that compose it. Green Power Attribute Reporting Application is an example which exercises different features of TI Zigbee for a green power device implementation. The device can operate as battery powered device or batteryless device while using unidirectional or bidirectional commissioning.

Some of the features exercised include:

• Green Power application ID configuration for source ID or IEEE.
• Security level configuration.
• Commissioning data frame.
• Sequence number capabilities.
• Attribute Reporting data frame.

Software Prerequisites

• Code Composer Studio™ (CCS) v12.5 or newer

• SimpleLink™ LOWPOWER SDK

Functional Description

Software Overview

This section describes the software components and the corresponding source files.

Application Files

The application can behave as a batteryless device by defining the BATTERYLESS_DEVICE; with this, the application will read the keys pressed at the initialization of the device (start debug session or power cycle) and will transmit a command based on the keys pressed, after which the application will reach its end of execution. If BATTERYLESS_DEVICE is not defined, the device will behave as a battery operated device, being in deep sleep until a key is pressed.

The application can behave as a unidirectional device by defining UNIDIR_DEVICE; with this, the application will change its commissioning behavior to only support unidirectional communication. If UNIDIR_DEVICE is not defined, the device will use bidirectional commissioning.

By default, the application is configured to not have BATTERYLESS_DEVICE or UNIDIR_DEVICE defined. Meaning, the application will act as a bidirectional battery device.

• gpd_attr_reporting.c: Contains the application's event loop, device initialization function calls, and all Commissioning/Attribute Reporting command specific logic.

Configuration With SysConfig

SysConfig is a GUI configuration tool that allows for TI driver and stack configurations.

To configure using SysConfig, import the SysConfig-enabled project into CCS. Double click the *.syscfg file from the CCS project explorer, where * is the name of the example project. The SysConfig GUI window will appear, where Zigbee stack and TI driver configurations can be adjusted. These settings will be reflected in the generated files.

The example project comes with working default settings for SysConfig. For the purposes of this README, it is not recommended to change the default driver settings, as any changes may impact the functionality of the example. The Zigbee stack settings may be changed as required for your use case.

Note that some Zigbee settings are stored in non-volatile storage, and Zigbee prioritizes stored settings over SysConfig settings. To guarantee SysConfig settings are applied, perform a factory reset of the device to clear non-volatile storage.

Example Usage

This section describes how to use this sample application.

Buttons

• BTN-1: Starts the commissioning process.
• BTN-2: Sends Attribute Reporting command.

Commissioning the device Into the network

Green Power Devices can be commissioned to a Zigbee network by sending a commissioning GPDF, a GPDF with auto-commissioning or a commissioning tool. A Zigbee device with green power proxy capabilities can create an entry for a Green Power Device with the commissioning data. The proxy device will translate the GPDF commands to ZCL notifcations for the Zigbee network.