Differences between API frame 0x10 and 0x11

Sending API frames

If your serial device sends a payload using API frame 0x10 (Transmit Request), then these defaults are assumed:

• The endpoints are 0xE8 and 0xE8
• The cluster id is 0x0011
• The profile id is 0xC105

Sending the API frame 0x11 (Explicit Addressing Command Frame) allows your device to override these defaults. If you do not wish to override them, then there is *NO* advantage to using API frame 0x11 over 0x10. The same information moves over the RF channel regardless.

The Digi gateways always sends API frames as 0x11.

Receiving API frames

Although the API documentation might lead you to believe your device receives API frames 0x90 when the peer uses 0x10, and 0x91 when the peer uses 0x11, this is not true. What your device receives is defined by the AT Command "AO" (API Output).

• Setting AO=0 means your device receives API frames 0x90 (Receive Packet) regardless of whether the peer sent the frame to its local Xbee via API frame 0x10 or 0x11.
• Setting AO=1 means your device receives API frames 0x91 (Explicit Rx Indicator) regardless of whether the peer sent the frame to its local Xbee via API frame 0x10 or 0x11.

The Digi gateways always receives API frames as 0x91, and will see the default endpoints, cluster and profile id if the remote node sent the data via the 0x10 API frame.