XBP09-XC009-DK Digi International, XBP09-XC009-DK Datasheet - Page 18

• Manufacturer Part Number: XBP09-XC009-DK
• Description: KIT STARTER XBEE PRO 900MHZ
• Manufacturer: Digi International
• Series: XBEE-PRO™r
• Type: Transceiver, XBeePror

Specifications of XBP09-XC009-DK

• Frequency: 900MHz
• Wireless Frequency: 900 MHz
• Operating Voltage: 3.3 V
• Output Power: 100 mW
• Antenna: U.FL, RPSMA, Whip
• Operating Temperature Range: - 40 C to + 85 C
• For Use With/related Products: Xbee-PRO Modules
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 602-1133; Q4227731; XBP09-XC009-DK

XBee‐PRO® XSC OEM RF Modules
Binary Commands
Sending and receiving parameter values using binary commands is the fastest way to change
operating parameters of the module. Binary commands are used most often to sample signal
strength (RS parameter) and/or error counts; or to change module addresses and channels for
polling systems when a quick response is necessary. Since the sending and receiving of parameter
values takes place through the same data path as 'live' data (received RF payload), follow the CTS
pin as outlined in Figure 2-012 to distinguish between the two types of data (commands vs 'live'
data).
Common questions regarding the use of binary commands:
CMD (pin 5) must be asserted in order to send binary commands to the module. The CMD pin can
be asserted to recognize binary commands anytime during the transmission or reception of data.
The status of the CMD signal is only checked at the end of the stop bit as the byte is shifted into
the serial port. The application does not allow control over when data is received, except by
waiting for dead time between bursts of communication.
If the command is sent in the middle of a stream of payload data to be transmitted, the command
will essentially be executed in the order it is received. If the radio is continuously receiving data,
the radio will wait for a break in the received data before executing the command. The CTS signal
will frame the response coming from the binary command request [Figure 2-012].
A minimum time delay of 100 µs (after the stop bit of the command byte has been sent) must be
observed before pin 5 can be de-asserted. The command executes after all parameters associated
with the command have been sent. If all parameters are not received within 0.5 seconds, the
module aborts the command and returns to Idle Mode.
Note: Binary commands that return only one parameter byte must also be written with two parameter
bytes, 0-padded, LSB first.
Refer to “Programming Examples” section [pXX] for a binary programming example.
Commands can be queried for their current value by sending the command logically ORed (bit-
wise) with the value 0x80 (hexadecimal) with CMD asserted. When the binary value is sent (with
no parameters), the current value of the command parameter is sent back through the DO pin.
Figure 2‐012.Binary Command Write then Read
Signal #4 is CMD (pin 16)
Signal #1 is the DIN (pin 3) signal
to the radio
Signal #2 is the DOUT (pin 2) signal
from the radio
Signal #3 is CTS (pin 12)
In this graph, a value was written to a
register and then read out to verify it.
While not in the middle of other received
data, note that the CTS signal outlines the
data response out of the module.
IMPORTANT: For the XBee module to recognize a binary command, the RT (DI2 Configuration) param-
eter must be set to one. If binary programming is not enabled RT = 0 or 2, the module will not recog-
nize that the CMD pin is asserted and therefore will not recognize the data as binary commands.
© 2008 Digi International, Inc.
• What are the implications of asserting CMD while live data is being sent or received?
• After sending serial data, is there a minimum time delay before CMD can be asserted?
• Is a time delay required after CMD is de-asserted before payload data can be sent?
• How to discern between live data and data received in response to a command?
18