XBP24-DMWIT-250 Digi International, XBP24-DMWIT-250 Datasheet - Page 42

• Manufacturer Part Number: XBP24-DMWIT-250
• Description: XBEE-PRO MESH 2.4 EXTENDED
• Manufacturer: Digi International
• Series: XBEE-PRO™r

Specifications of XBP24-DMWIT-250

• Frequency: 2.4GHz
• Data Rate - Maximum: 250kbps
• Modulation Or Protocol: ISM
• Applications: General Purpose
• Power - Output: 18dBm
• Sensitivity: -100dBm
• Voltage - Supply: 2.8 V ~ 3.4 V
• Current - Receiving: 55mA
• Current - Transmitting: 250mA
• Data Interface: PCB, Through Hole
• Antenna Connector: On-Board, Wire Whip
• Operating Temperature: -40°C ~ 85°C
• Package / Case: Module
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Memory Size: -
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: Q4542387

6. API Operation
XBee/XBee‐PRO DigiMesh 2.4 RF Modules
As an alternative to Transparent Operation, API (Application Programming Interface) Operations are available. API operation
requires that communication with the module be done through a structured interface (data is communicated in frames in a
defined order). The API specifies how commands, command responses and module status messages are sent and received from
the module using a UART Data Frame.
Please note that Digi may add new frame types to future versions of firmware, so please build into your software interface the
ability to filter out additional API frames with unknown Frame Types.
API Frame Specifications
Two API modes are supported and both can be enabled using the AP (API Enable) command. Use the following AP parame-
ter values to configure the module to operate in a particular mode:
When this API mode is enabled (AP = 1), the UART data frame structure is defined as follows:
Any data received prior to the start delimiter is silently discarded. If the frame is not assembled correctly or if the
checksum fails, the module will either discard the data or wait for further data, which can cause the preceding
packet to fail also.
When this API mode is enabled (AP = 2), the UART data frame structure is defined as follows:
Escape characters. When sending or receiving a UART data frame, specific data values must be escaped (flagged)
so they do not interfere with the data frame sequencing. To escape an interfering data byte, insert 0x7D and follow
it with the byte to be escaped XOR’d with 0x20.
Data bytes that need to be escaped:
API Operation (AP parameter = 1)
API Operation - with Escape Characters (AP parameter = 2)
Start Delimiter
Start Delimiter
UART Data Frame Structure:
UART Data Frame Structure ‐ with escape control characters:
(Byte 1)
(Byte 1)
0x7E
0x7E
Example - Raw UART Data Frame (before escaping interfering bytes): 
• AP = 1: API Operation
• AP = 2: API Operation (with escaped characters)
• 0x7E – Frame Delimiter
• 0x7D – Escape
• 0x11 – XON
• 0x13 – XOFF
© 2010 Digi International, Inc.
MSB = Most Significant Byte, LSB = Least Significant Byte
MSB = Most Significant Byte, LSB = Least Significant Byte
0x7E 0x00 0x02 0x23 0x11 0xCB
0x11 needs to be escaped which results in the following frame: 
0x7E 0x00 0x02 0x23 0x7D 0x31 0xCB
MSB
MSB
(Bytes 2-3)
(Bytes 2-3)
Length
Length
LSB
LSB
Characters Escaped If Needed
API-specific Structure
API-specific Structure
Frame Data
Frame Data
(Bytes 4-n)
(Bytes 4-n)
(Byte n + 1)
(Byte n + 1)
Checksum
Checksum
1 Byte
1 Byte
42