XBP09-DMDK Digi International, XBP09-DMDK Datasheet - Page 11

• Manufacturer Part Number: XBP09-DMDK
• Description: KIT STARTER PROMESH XBEE PRO
• Manufacturer: Digi International
• Series: XBEE-PRO™r
• Type: Transceiver, XBeePror

Specifications of XBP09-DMDK

• Frequency: 900MHz
• Wireless Frequency: 900 MHz
• Interface Type: RS-232, USB, UART
• Modulation: FHSS
• Security: 128 bit AES
• Operating Voltage: 3.3 V
• Output Power: 50 mW
• Antenna: RPSMA
• For Use With/related Products: Xbee-PRO Modules
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Other names: 602-1130

XBee‐PRO® 900 OEM RF RF Modules
API Operation
RTS Flow Control
Transparent Operation
Serial-to-RF Packetization
If flow RTS 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.
When operating in Transparent Operation, 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 the DOUT pin. The module configuration parameters are configured using the AT
command mode interface. (See RF Module Operation --> Command Mode.)
Data is buffered in the serial receive buffer until one of the following causes the data to be
packetized and transmitted:
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.
The maximum number of characters that will fit (256) in an RF packet is received.
The Command Mode Sequence (GT + CC + GT) is received. Any character buffered in the serial
receive buffer before the sequence is transmitted.
API (Application Programming Interface) Operation is an alternative to the default 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
To implement API operations, refer to the API Operation chapter 6.
© 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, etc.
11