Transmission, addressing, and routing ZDO transmissions
Digi XBee® 3 Zigbee® RF Module
116
Bits 1, 2, and 3 of the AO command dictate the routing of incoming ZDO messages. When these bits
are cleared, the XBee 3 Zigbee RF Module will handle and respond to ZDO commands. When these bits
are set, then Supported ZDO, Unsupported ZDO, and/or Bind Requests are passed through the UART
and the XBee device will not respond.
Bit 4 of the AO command will allow any supported ZDO commands that the XBee application handles
to be echoed out of the serial port. This is useful as a diagnostic tool to identify when the XBee 3
Zigbee RF Module is responding to ZDO commands and what types.
Setting bit 5 of AO will suppress all ZDO output and disable pass through. Setting bit 5 will behave as if
bits 1, 2, and 3 are 0 (XBee device handles incoming requests). This is useful if you want to use the
0x91 receive frame, but only emit Digi-specific messages out of the serial port. The following figure
shows AO set to a non-zero value.
When a ZDO message is received on endpoint 0 and profile ID 0, the cluster ID indicates the type of
ZDO message received. The first byte of payload is generally a sequence number that corresponds to
a sequence number of a request. The remaining bytes are set as defined by the ZDO. Similar to a ZDO
request, all multi-byte values in the response are in little endian byte order.
Example 1: Send a ZDO LQI request to read the neighbor table contents of a
remote
Looking at the Zigbee specification, the cluster ID for an LQI Request is 0x0031, and the payload only
requires a single byte (start index). This example sends an LQI request to a remote device with a 64-
bit address of 0x0013A200 40401234. The start index is set to 0, and the transaction sequence
number is set to 0x76.
API Frame
7E 0016 11 01 0013A200 40401234 FFFE 00 00 0031 0000 00 00 76 00 CE