
Network commissioning and diagnostics
Group Table API
XBee/XBee-PRO® S2C ZigBee® RF Module
124
The packet in raw hex byte form:
7e001711010013a2004047b55cfffee6e70006c105000001ee0417
The response in raw hex byte form, consisting of two packets:
7e0016910013a2004047b55cfffee7e68006c1050009ee04007c
7e00078b01fffe00000076
The command response in decoded form:
ZigBee Explicit Rx Indicator
API 0x91 64DestAddr 0x0013A2004047B55C 16DestAddr 0xFFFE
SrcEP 0xE7
DestEP
0xE6
ClusterID 0x8006 ProfileID 0xC105
Options 0x00
RF_Data 0x09ee0400
The response in terms of Preamble, ZCL Header, and ZCL payload.
Preamble = “910013a2004047b55cfffee7e68006c10500”
The packet has its endpoints values reversed from the request, and the clusterID is 0x8006 indicating
a Group cluster response.
ZCL_header = “09 ee 04"
The first field is a frame control field which specifies a Cluster Specific command (0x01) using a Server-
>Client direction (0x08). The second field is a transaction sequence number which is used to associate
the response with the command request. The third field is the command identifier “Remove All
Groups” (0x04)
1
.
ZCL_payload = “00”
The first byte is a status byte (SUCCESS=0x00)[4].
And here is the decoded second message, which is a Tx Status for the original command request. If
the FrameID value in the original command request had been zero, or if no space was available in the
transmit UART buffer, then no Tx Status message would occur.
ZigBee Tx Status
API 0x8B
FrameID 0x01
16DestAddr 0xFFFE
Transmit Retries 0x00 Delivery Status 0x00 Discovery Status 0x00 Success
Default responses
Many errors are returned as a default response. For example, an RFData payload of a response
containing 08010b788b would be decoded as:
ZCL_header = “08 01 03" - general command/server-to-client, transseqnum=1,
default_response_command(0x03)
ZCL_payload = “78 8b” - original cmdID, status code (0x8b)
EMBER_ZCL_STATUS_NOT_FOUND
, document 075123r02: Remove Group Response, section 3.6.2.4.4.