XBP24-BPIT-004 Digi International, XBP24-BPIT-004 Datasheet - Page 14

• Manufacturer Part Number: XBP24-BPIT-004
• Description: Zigbee / 802.15.4 Modules XBee-PRO Znet 2.5 PCB Antenna
• Manufacturer: Digi International

Specifications of XBP24-BPIT-004

• Rohs: yes
• Frequency Band: 2.4 GHz
• Line Of Sight Range: 100 m
• Data Rate: 250 Kbps
• Sensitivity: - 102 dBm
• Operating Supply Voltage: 3 V to 3.4 V
• Output Power: 63 mW
• Antenna Connector Type: PCB
• Maximum Operating Temperature: + 85 C

XBee ZNet 2.5/XBee‐PRO ZNet 2.5 ZigBee OEM RF Modules v1.x4x
2.1.4. Serial Interface Protocols
RTS Flow Control
Transparent Operation
API Operation
If RTS flow control is enabled (D6 command), data in the serial transmit buffer will not be sent out
the DOUT pin as long as RTS is de-asserted (set high). The host device should not de-assert RTS
for long periods of time to avoid filling the serial transmit buffer. If an RF data packet is received,
and the serial transmit buffer does not have enough space for all of the data bytes, the entire RF
data packet will be discarded.
The XBee modules support both transparent and API (Application Programming Interface) serial
interfaces.
When operating in transparent mode, the modules act as a serial line replacement. All UART data
received through the DIN pin is queued up for RF transmission. When RF data is received, the data
is sent out through the DOUT pin. The module configuration parameters are configured using the
AT command mode interface.
Data is buffered in the serial receive buffer until one of the following causes the data to be
packetized and transmitted:
1. No serial characters are received for the amount of time determined by the RO (Packetization
Timeout) parameter. If RO = 0, packetization begins when a character is received.
2. Maximum number of characters that will fit in an RF packet is received (72 bytes).
3. The Command Mode Sequence (GT + CC + GT) is received. Any character buffered in the serial
receive buffer before the sequence is transmitted.
RF modules that contain the following firmware versions will support Transparent Mode:
1.0xx (coordinator) and 1.2xx (router/end device).
API operation is an alternative to transparent operation. The frame-based API extends the level to
which a host application can interact with the networking capabilities of the module. When in API
mode, all data entering and leaving the module is contained in frames that define operations or
events within the module.
Transmit Data Frames (received through the DIN pin (pin 3)) include:
Receive Data Frames (sent out the DOUT pin (pin 2)) include:
The API provides alternative means of configuring modules and routing data at the host
application layer. A host application can send data frames to the module that contain address and
payload information instead of using command mode to modify addresses. The module will send
data frames to the application containing status packets; as well as source, and payload
information from received data packets.
The API operation option facilitates many operations such as the examples cited below:
->Transmitting data to multiple destinations without entering Command Mode
->Receive success/failure status of each transmitted RF packet
->Identify the source address of each received packet
RF modules that contain the following firmware versions will support API operation: 1.1xx
(coordinator) and 1.3xx (router/end device).
© 2008 Digi International, Inc.
• RF Transmit Data Frame
• Command Frame (equivalent to AT commands)
• RF-received data frame
• Command response
• Event notifications such as reset, associate, disassociate, etc.
13