XBee‐PRO®900HP/XBee‐PRO®XSCRFModules
©2014DigiInternationalInc. 59
Data bytes that need to be escaped:
• 0x7E – Frame Delimiter
•0x7D – Escape
• 0x11 – XON
• 0x13 – XOFF
Example - Raw serial data frame (before escaping interfering bytes):
0x7E 0x00 0x02 0x23 0x11 0xCB
0x11 needs to be escaped which results in the following frame:
0x7E 0x00 0x02 0x23 0x7D 0x31 0xCB
Note: In the above example, the length of the raw data (excluding the checksum) is 0x0002 and the
checksum of the non-escaped data (excluding frame delimiter and length) is calculated as:
0xFF - (0x23 + 0x11) = (0xFF - 0x34) = 0xCB.
Length
The length field has two-byte value that specifies the number of bytes that will be contained in the frame data
field. It does not include the checksum field.
Frame Data
Frame data of the serial data frame forms an API-specific structure as follows:
SerialDataFrame&API‐specificStructure:
The cmdID frame (API-identifier) indicates which API messages will be contained in the cmdData frame
(Identifier-specific data). Note that multi-byte values are sent big endian.The XBee modules support the
following API frames:
Note that requests are less than 0x80, and responses are always 0x80 or higher.
APIFrameNamesandValue s SenttotheModule
API Frame Names API ID
AT Command
0x08
AT Command - Queue Parameter Value
0x09
TX Request 0x10
Explicit TX Request 0x11
Remote Command Request
0x17
APIFrameNamesandValue s ReceivedfromtheModule
API Frame Names API ID
AT Command Response
0x88
Modem Status 0x8A
Transmit Status 0x8B
RX Indicator (AO=0) 0x90
Explicit Rx Indicator (AO=1) 0x91
Node Identification Indicator (AO=0) 0x95
Remote Command Response
0x97
Length
(Bytes 2-3)
Checksum
(Byte n + 1)
MSB LSB 1 Byte
Start Delimiter
(Byte 1)
0x7E
Frame Data
(Bytes 4-n)
API-specific Structure
Identifier-specific Data
cmdData
API Identifier
cmdID