Programming instructions

Atmel AT02597: ZigBee PRO Packet Analysis with Sniffer [APPLICATION NOTE]
32210AWIRELESS09/2013
29
This sub-field shall be set to TRUE for all manufacturer-specific extensions to ZCL specification (addition of new
attributes, commands to existing clusters and addition of new clusters).
5.1.3 Commands
The HA reference application demonstrates usage of ZCL specified commands.
In #189, an addGroup command is sent from the Dimmer switch to the Light for the Group ID, defined in the application.
On receiving this command, the dimmable Light adds the Group ID and Group Name to its Group Table (maintained by
the application).
It shall then generate an appropriate Add Group Response command indicating success or failure.
It is useful to group devices to send messages to the group as broadcast data.
In #333, an On command is sent from the Dimmer switch to the Light with the noDefaultResp sub-field in the ZCL
header set to zero. This causes a default Response packet to be sent out from the light with the statusCode
0x00(SUCCESS).
Default Response is sent out under the following conditions:
1.
The Disable default response bit of its Frame control field is set to 0(as discussed above).
2.
No response command exists for the received command.
3.
For an unsupported command received.
5.1.4 Security
By default, network layer encryption with the network key is used for cluster commands.
Table 5-2. Relevant Config. Server Parameters.
Config. server parameter
Knowledge of security keys on device CS_ZDO_SECURITY_STATUS
Active Network Key CS_NETWORK_KEY
5.2
ZigBee Light Link
The ZLL Demo in the BitCloud Profile Suite for ZLL package implements standard device types: color scene controller,
color light and bridge. The sniffer log referenced in this section is ZLL_CL_CSR.wrk which shall be viewed with
Perytons Network Analyzer.
5.2.1 Touchlinking
The ZigBee Light Link network is not created by a coordinator. Instead, network parameters are transferred from an in-
network device to a factory-new device (device that is to join the network). This process of transferring network
information occurs as Inter-PAN data exchange and is called touchlinking or commissioning.
In the sniffer log, packets #3 to #20 cover the touch-link procedure. All frames in this sequence follow the inter-PAN
command format specified by [6].
Table 5-3. Fields of Interest – Inter-PAN Command Frame Format.
Frame field Value
MAC header -> Frame Control panIDComp or Intra-PAN set to zero
NWK/APS header-> Frame Control Frame Type set to reserved type
Inter-PAN Transaction Identifier 32-bit unique value valid throughout Touchlink process