Programming instructions

Atmel AT02597: ZigBee PRO Packet Analysis with Sniffer [APPLICATION NOTE]
32210A−WIRELESS−09/2013
28
5. Analyzing Data Traffic in ZigBee PRO Public Profile Networks
Networks based on ZigBee PRO Public Profiles such as ZigBee Smart Energy, Home Automation, Light Link employ
specific join, security and data exchange schemes. The implementation details of the reference applications can be
found in [5].
This chapter provides sniffer
data analysis of example sniffer logs taken using [5]. The sniffer logs are provided in
a zip
package with this application note and this chapter references packet numbers from these logs. The logs are in *.dcf
format and can be viewed in BitCatcher.
5.1 ZigBee Home Automation
The Home Automation (HA) reference application in BitCloud Profile Suite implements six HA device types. The sniffer
log, HA_TC_DL_DS.dcf, demonstrates data exchange between a Trust Center, Dimmable Light and Dimmer switch
device.
5.1.1 Service Discovery
The Dimmable Light device joins the network created by the Trust Center from packet #3 and the Dimmer switch from
#17. This network employs standard network security with application link keys.
#32 shows a Match Descriptor Request broadcast by the dimmer switch to all devices with macRxOnWhenIdle = TRUE
(nwkHeader->dstShortAddr = 0xFFFD).
The Match Descriptor Data field consists of the number of clusters and the cluster ID .The request should be issued
individually for each server and client cluster. Hence, in #37, the in/client cluster count is 0x01 and cluster ID is the
ONOFF_CLUSTER_ID.In #178, the in cluster count is 0x00, the out/server cluster count is 0x01 and the cluster ID is
the ONOFF_SWITCH_CONFIGURATION_CLUSTER_ID.
The profile ID is PROFILE_ID_HOME_AUTOMATION defined in zcl.h and the cluster related defines in clusters.h found
in \ZCL\include directory in the BitCloud SDK.
The Trust Center does not support the clusters in this request and so simply re-broadcasts the packet (#33 shows this,
the apsHeader->counter and nwkHeader sequence number stay same, whereas the nwkHeader->radius is
decremented by one on re-broadcast).
The Match descriptor response gives sufficient information about the responder (short address, endpoint and cluster
information) for the requester device to do a device discovery (IEEE address determination) and binding.
Every cluster binding creates an entry in the requester’s binding table.
Table 5-1. Relevant Config. Server Parameters.
Network information Config. server parameter
Binding Table CS_APS_BINDING_TABLE_SIZE
IEEE and short Address pair CS_ADDRESS_MAP_TABLE_SIZE
5.1.2 Attribute Reporting
The HA reference application sets up automatic reporting of attributes with application configured report period.
In #113, dimmable light reports value of attribute ID, ZCL_ONOFF_CLUSTER_ONOFF_SERVER_ATTRIBUTE_ID
(attributeStatusList) of the ONOFF_CLUSTER_ID (apsHeader -> clusterId).
The ZCL header specifies that the direction of this frame (server to client) and this being a common ZCL specified
frame, the manufSpec is set to zero.