MaxStream XBP24-PKC-...-U... User manual

355 South 520 West, Suite 180
Lindon, UT 84042
Phone: [phone]
Fax: [phone]
[e-mail]
www.MaxStream.net (live chat suport)
XBee-PRO PKG-U™ USB RF Modem
XBee-PRO USB RF Modem
RF Modem Operation
RF Modem Configuration
Appendices
Product Manual v1.x82
For XBee-PRO RF Modem Part Numbers: XBP24-PKC-...-U...
IEEE®802.15.4 Stand-alone USB RF Modems by MaxStream, Inc.
M100281
2006.04.24

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved ii
© 2006 MaxStream, Inc. All rights reserved
Nopartofthecontentsofthismanualmaybetransmittedorreproducedinany
formorbyanymeanswithoutthewrittenpermissionofMaxStream,Inc.
XBee‐PROPKG‐U™isatrademarkofMaxStream,Inc.
TechnicalSupport:Phone:(801)765‐9885
LiveChat:www.maxstream.net
E‐mail:rf‐[email protected]

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved iii
Contents
1. XBee-PRO USB RF Modem 4
1.1. Features Overview 4
1.1.1. Worldwide Acceptance 4
1.2. Specifications 5
1.3. Mechanical Drawings 5
1.4. External Interface 6
1.5. Pin Signals 6
2. RF Modem Operation 7
2.1. Driver Installations 7
2.1.1. USB Background Information 7
2.2. Transparent Operation 8
2.3. API Operation 8
2.4. IEEE 802.15.4 Networks 9
2.4.1. NonBeacon 9
2.4.2. NonBeacon (w/ Coordinator) 9
2.4.3. Association 10
2.5. Modes of Operation 13
2.5.1. Idle Mode 13
2.5.2. Transmit / Receive Modes 13
2.5.3. Sleep Mode 15
2.5.4. Command Mode 17
2.6. Addressing 18
2.6.1. Unicast Mode 18
2.6.2. Broadcast Mode 18
3. RF Modem Configuration 19
3.1. Programming the RF Modem 19
3.1.1. Programming Examples 19
3.2. Command Reference Tables 20
3.3. Command Descriptions 26
3.4. API Operation 40
3.4.1. API Frame Specifications 40
3.4.2. API Types 41
Appendix A: Agency Certifications 45
FCC Certification 45
OEM Labeling Requirements 45
FCC Notices 45
FCC-Approved Antennas (2.4 GHz) 46
European Certification 47
OEM Labeling Requirements 47
Restrictions 47
Declarations of Conformity 47
Antenna Usage (Europe) 48
IC (Industry Canada) Certification 48
Labeling Requirements 48
Appendix B: Additional Information 49
1-Year Warranty 49
Ordering Information 49
Contact MaxStream 50

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 4
1.XBee‐PROUSBRFModem
The XBee-PRO USB RF Modem is an IEEE 802.15.4 compliant solution that
has a USB interface built-in to its design. Out-of-box, the modem sustains
outstanding range (2-3x the range of typical 802.15.4 solutions) and
requires no additional configuration for reliable RF communications.
The modem transfers a standard asynchronous serial data stream between
two or more devices. Simply feed data into one modem, then the data is
sent out the other end of the wireless link. Its built-in USB interface allows
for rapid integration into existing data systems.
1.1. Features Overview
Long Range Data Integrity
Range
• Indoor/Urban: up to 300’ (100m)
• Outdoor line-of-sight: up to 1 mile (1.6km)
Transmit Power: 60 mW (18 dBm),
100 mW (20 dBm) EIRP
Receiver Sensitivity: -100 dBm
RF Data Rate: 250,000 bps
Advanced Networking & Security
Retries and Acknowledgements
DSSS (Direct Sequence Spread Spectrum)
Each direct sequence channels has over
65,000 unique network addresses available
Source/Destination Addressing
Unicast & Broadcast Communications
Point-to-point, point-to-multipoint
and peer-to-peer topologies supported
Coordinator/End Device networking
128 bit Encryption (downloadable firmware
Low Power
Power Currents
• Receive Current: 90 mA
• Transmit Current: 300 mA
• Power-down Current: < 25 mA
Easy-to-Use
No configuration necessary for out-of box
RF communications
Free X-CTU Software
(Testing and configuration software)
Built-in USB interfacing
Small form factor
Network compatible with other
802.15.4 devices
AT and API Command Modes for
configuring modem parameters
Free & Unlimited Technical Support
1.1.1. Worldwide Acceptance
FCC Approved (USA) Refer to Appendix A [p45] for FCC Requirements.
Systems that include XBee-PRO RF Modems inherit MaxStream Certifications.
Operates within the ISM (Industrial, Scientific & Medical) 2.4 GHz frequency band
Manufactured under ISO 9001:2000 registered standards
XBee-PRO RF Modems are optimized for use in US, Canada, Australia, Israel and
Europe (contact MaxStream for complete list of approvals).

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 5
1.2. Specifications
*WhenoperatinginEurope:XBee‐PRORFModemsmustbeconfiguredtooperateatamaximumtransmit
poweroutputlevelof10dBm.SetthePLparameterto“0”(10dBm)inordertoadheretoEuropeanregulations.
1.3. Mechanical Drawings
Figure1‐01. MechanicaldrawingsoftheXBee‐PROUSBRFModem
Table1‐01. SpecificationsoftheXBee‐PROPKG‐UUSBRFModem
Specification XBee-PRO USB RF Modem
Performance
Indoor/Urban Range (w/ 2.1 dB dipole antenna) up to 300’ (100 m)
Outdoor/Urban Range (w/ 2.1 dB dipole antenna) up to 4000’ (1200 m)
Transmit Power Output 60 mW, 100 mw (20 dBm) EIRP*
Receiver Sensitivity -100 dBm (1% packet error rate)
Interface Data Rate 1200 - 115200 bps (non-standard baud rates also supported)
RF Data Rate 250,000 bps
Networking & Security
Operating Frequency ISM 2.4 GHz
Modulation DSSS (Direct Sequence Spread Spectrum)
Supported Network Topologies Point-to-point, Point-to-Multipoint, Peer-to-Peer & Mesh (coming soon)
Number of Channels (software selectable) 12 Direct Sequence Channels
Addressing Layers PAN ID, Channel & Source/Destination Addresses
Antenna
Connector RPSMA (reverse polarity SMA)
Impedance 50 ohms unbalanced
Power Requirements
Power Supply Powered through USB port
Receive Current 90 mA
Transmit Current 300 mA (Average current when streaming data (@9600bps) = 92 mA)
Power-down Current < 25 mA
Physical Properties
Size 4.500” x 2.750” x 1.125” (11.4cm x 7.0cm x 2.9cm)
Weight 5.25 oz. (150 g)
Data Connection USB
Operating Temperature 0 - 70º C (Commercial)
Certifications (partial list)
United States (FCC Part 15.247) OUR-XBEEPRO
Industry Canada (IC) 4214A XBEEPRO
Europe (CE) ETSI (Max. 10 mW transmit power output)*

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 6
1.4. External Interface
1.5. Pin Signals
1-02a. I/O & Power LEDs
Figure1‐02. FrontView LEDs indicate RF modem activity as follows:
Yellow (top LED) = Serial Data Out (to host)
Green (middle) = Serial Data In (from host)
Red (bottom) = Power/TX Indicator (Red LED is illuminated
when RF modem is powered)
1-02b. RSSI LEDs
RSSI LEDs indicate the amount of fade margin present in an active
wireless link. Fade margin is defined as the difference between the
incoming signal strength and the modem's receiver sensitivity.
3 LEDs ON = Very Strong Signal (> 30 dB fade margin)
2 LEDs ON = Strong Signal (> 20 dB fade margin)
1 LED ON = Moderate Signal (> 10 dB fade margin)
0 LED ON = Weak Signal (< 10 dB fade margin)
1-02c. USB Port
Standard Type-B USB connector is used to communicate with USB
host and power the RF modem.
1-03a. DIP Switch
Figure1‐03. BackView DIP Switch functions are not supported in this release. Future down-
loadable firmware versions will support the DIP Switch configurations.
1-03b Reset Switch
The Reset Switch is used to reset (re-boot) the RF modem.
1-03c. Antenna Port
Port is a 50ΩRF signal connector for connecting to an external
antenna. The connector type is RPSMA (Reverse Polarity SMA)
female. The connector has threads on the outside of a barrel and a
male center conductor.
Table1‐02. USBsignalsandtheirimplantationsontheXBee‐PRORFModem
Pin Name Description Implementation
1 VBUS Power Power the RF modem
2 D- Transmitted & Received Data Transmit data to and from the RF modem
3 D+ Transmitted & Received Data Transmit data to and from the RF modem
4 GND Ground Signal Ground
1-02a. I/O & Power LEDs
1-02b. RSSI LEDs
1-02c. USB Port
1-03a. DIP Switch
1-03b. Reset Switch
1-03c. Antenna Port

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 7
2.RFModemOperation
After the appropriate drivers have been installed and the XBee-PRO USB RF Modem is connected
to the USB port, the PC will see the modem as a standard com port. This com port redirection can
only occur after installing the 'Hardware USB Bus' and 'Virtual Com Port' drivers [see instructions
below]. Once the USB connection is made and drivers are installed, any software that is able to
communicate through a com port can be used to interface with the modem. MaxStream’s propri-
etary X-CTU Software includes a ‘Terminal’ tab that can be used for configuring the modem and
monitoring communications. Alternatively, software such as HyperTerminal can be used.
2.1. Driver Installations
The XBee-PRO USB RF Modem is a "plug-and-play" device that should automatically be detected
by the PC. To interface between the modem and a PC, two drivers must be installed. After the
modem is detected, the PC will display an installation wizard that facilitates driver installations.
Drivers for Windows, Macintosh & LINUX operating systems are included on the MaxStream CD.
To Install Drivers:
2.1.1. USB Background Information
USB has two types of devices: Those that supply drivers (a host, such as a PC); and those that
require a driver (a client, such as the XBee-PRO USB RF Modem). When a USB client is plugged
into a host, the host prompts for a driver. Once a driver is located, the host loads the driver on the
first use of the USB client; then reloads the installed driver on all subsequent uses.
A USB client should not be plugged into another client. If another USB client (such as a USB video
camera) is plugged into a MaxStream USB RF Modem (also a client), the devices will not commu-
nicate. It would be incorrect to attach a USB modem to a host on one end and attach a USB
modem to a USB client at the other end. Virtually all USB peripherals (video cameras, PDA cradles,
printers, etc.) are USB clients.
Some client devices can act as a host. This is known as "USB on-the-go". An appropriate USB on-
the-go enabled device (such as a PDA with USB on-the-go support) may connect to and utilize a
MaxStream USB RF Modem. Contact MaxStream for information about device drivers.
The following steps were recorded while using the Windows XP operating system.
1. Connect the XBee-PRO RF Modem to a PC using a USB cable.
["Found New Hardware Wizard" dialog box appears.]
2. Verify the MaxStream CD is inserted into the drive.
3. Select "Install from a specific list or location (Advanced)" option;
then select the 'Next' button.
4. a. Select the 'Search for the best driver in these locations' option.
b. Check 'Search removable media (CD-ROM...)' box; then select the 'Next' button.
[Hardware Installation "Windows Logo Testing" alert box appears.]
5. Select the 'Continue Anyway' button.
6. Select the 'Finish' button.
7. Repeat steps 2 through 6 to install the next driver.
8. Reboot computer if prompted to do so.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 8
2.2. Transparent Operation
By default, XBee-PRO RF Modems operate in Transparent Mode. When operating in this mode, the
modems act as a serial line replacement - all UART data received through the DI pin is queued up
for RF transmission. When RF data is received, the data is sent out the DO pin.
When the RO (Packetization Timeout) parameter threshold is satisfied [refer to RO command
description], the modem attempts to initialize an RF transmission. If the modem cannot immedi-
ately transmit (for instance, if it is already receiving RF data), the serial data continues to be
stored in the DI Buffer. Data is packetized and sent at any RO timeout or when 100 bytes (maxi-
mum packet size) are received.
The modem operates as described above unless the Command Mode Sequence is detected. The
Command Mode Sequence consists of three copies of the command sequence character [CC
parameter] surrounded by before and after guard times [GT parameter].
If the DI buffer becomes full, hardware or software flow control must be implemented in order to
prevent overflow (loss of data between the host and modem).
2.3. API Operation
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 modem.
When in API mode, all data entering and leaving the modem is contained in frames that define
operations or events within the modem.
Transmit Data Frames (received through the Data In) include:
• RF Transmit Data Frame
• Command Frame (equivalent to AT commands)
Receive Data Frames (sent out the Data Out) include:
• Showing a received RF packet
• A response to a command
• Showing events such as reset, associate, disassociate, etc.
The API provides alternative means of configuring modems and routing data at the host applica-
tion layer. A host application can send data frames to the modem that contain address and payload
information instead of using command mode to modify addresses. The modem will send data
frames to the application containing status packets; as well as source, RSSI and payload informa-
tion from received data packets.
The API operation option facilitates many operations such as the examples cited below:
To implement API operations, refer to API sections [p40].
-> Change destination addresses without having to enter command mode
-> Receive success/failure status of each RF packet
-> Identify the source address of each received packet

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 9
2.4. IEEE 802.15.4 Networks
The following IEEE 802.15.4 network types are available to the RF modem:
•NonBeacon
• NonBeacon (w/ Coordinator)
The following terms will be used to explicate the network system types:
2.4.1. NonBeacon
By default, XBee-PRO RF Modems are configured to support NonBeacon communications (no Coor-
dinator). NonBeacon systems operate within a Peer-to-Peer network topology and are not depen-
dent upon Master/Slave relationships. This means that modems remain synchronized without use
of master/server configurations and each modem in the network shares both roles of master and
slave. MaxStream's peer-to-peer architecture features fast synchronization times and fast cold
start times. This default configuration accommodates a wide range of RF data applications.
Figure2‐01. NonBeaconPeer‐to‐PeerArchitecture
A peer-to-peer network can be established by
configuring each modem to operate as an End Device (CE = 0), disabling End Device Association
on all modems (A1 = 0) and setting ID and CH parameters to be identical across the network.
2.4.2. NonBeacon (w/ Coordinator)
A device is configured as a Coordinator by setting the CE (Coordinator Enable) parameter to “1”.
Coordinator power-up is governed by the A2 (Coordinator Association) command.
In a NonBeacon (w/ Coordinator) system, the Coordinator can be configured to use direct or indi-
rect transmissions. If the SP (Cyclic Sleep Period) parameter is set to “0”, the Coordinator will send
data immediately. Otherwise, the SP parameter determines the length of time the Coordinator will
retain the data before discarding it. Generally, SP (Cyclic Sleep Period) and ST (Time before Sleep)
parameters should be set to match the SP and ST settings of the End Devices.
Association plays a critical role in the implementation of a NonBeacon (w/ Coordinator) system. Refer
to the Association section [p10] for more information.
Table2‐01. Termsanddefinitions(Applicablenetworkingnetworktypesaredesignatedwithin<brackets>.)
Term Definition
Association <NonBeacon (w/ Coordinator) systems only>
The establishment of membership between End Devices and a Coordinator.
Coordinator <NonBeacon (w/ Coordinator) systems only> A central RF modem that is configured to provide synchronization services through the
transmission of beacons.
End Device When in the same network as a Coordinator - RF modems that rely on a Coordinator for
synchronization and can be put into states of sleep for low-power applications.
PAN Personal Area Network - A data communication network that includes one or more End
Devices and optionally a Coordinator.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 10
2.4.3. Association
Association is the establishment of membership between End Devices and a Coordinator. Associa-
tion is only applicable in NonBeacon (w/ Coordinator) systems. The establishment of membership
is useful in scenarios that require a central unit (Coordinator) to relay messages to or gather mes-
sages from several remote units (End Devices), assign channels or assign PAN IDs.
An RF data network that consists of one Coordinator and one or more End Devices forms a PAN
(Personal Area Network). Each device in a PAN has a PAN Identifier [ID (PAN ID) parameter]. PAN
IDs must be unique to prevent miscommunication between PANs. The Coordinator PAN ID is set
using the ID (PAN ID) and A2 (Coordinator Association) commands.
An End Device can associate to a Coordinator without knowing the address, PAN ID or channel of
the Coordinator. The A1 (End Device Association) parameter bit fields determine the flexibility of
an End Device during association. The A1 parameter can be used for an End Device to dynamically
set its destination address, PAN ID and/or channel.
Coordinator / End Device Setup and Operation
To configure a modem to operate as a Coordinator, set the CE (Coordinator Enable) parameter to
‘1’. Set the CE parameter of End Devices to ‘0’ (default). Coordinator and End Devices should con-
tain matching firmware versions.
NonBeacon (w/ Coordinator) Systems
In a NonBeacon (w/ Coordinator) system, the Coordinator can be configured to use direct or indi-
rect transmissions. If the SP (Cyclic Sleep Period) parameter is set to ‘0’, the Coordinator will send
data immediately. Otherwise, the SP parameter determines the length of time the Coordinator will
retain the data before discarding it. Generally, SP (Cyclic Sleep Period) and ST (Time before Sleep)
parameters should be set to match the SP and ST settings of the End Devices.
Coordinator Power-up
Coordinator power-up is governed by the A2 (Coordinator Association) command. On power up,
the Coordinator undergoes the following sequence of events:
1. Check A2 parameter- Reassign_PANID Flag
Set (bit 0 = 1) - The Coordinator issues an Active Scan. The Active Scan selects one channel
and transmits a BeaconRequest command to the broadcast address (0xFFFF) and broadcast
PAN ID (0xFFFF). It then listens on that channel for beacons from any Coordinator operating on
that channel. The listen time on each channel is determined by the SD (Scan Duration) param-
eter value.
Once the time expires on that channel, the Active Scan selects another channel and again
transmits the BeaconRequest as before. This process continues until all channels have been
scanned, or until 5 PANs have been discovered. When the Active Scan is complete, the results
include a list of PAN IDs and Channels that are being used by other PANs. This list is used to
assign an unique PAN ID to the new Coordinator. The ID parameter will be retained if it is not
found in the Active Scan results. Otherwise, the ID (PAN ID) parameter setting will be updated
to a PAN ID that was not detected.
Not Set (bit 0 = 0) - The Coordinator retains its ID setting. No Active Scan is performed.
For example: If the PAN ID of a Coordinator is known, but the operating channel is not; the A1
command on the End Device should be set to enable the ‘Auto_Associate’ and
‘Reassign_Channel’ bits. Additionally, the ID parameter should be set to match the PAN ID of
the associated Coordinator.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 11
2. Check A2 parameter - Reassign_Channel Flag (bit 1)
Set (bit 1 = 1) - The Coordinator issues an Energy Scan. The Energy Scan selects one channel
and scans for energy on that channel. The duration of the scan is specified by the SD (Scan
Duration) parameter. Once the scan is completed on a channel, the Energy Scan selects the
next channel and begins a new scan on that channel. This process continues until all channels
have been scanned.
When the Energy Scan is complete, the results include the maximal energy values detected on
each channel. This list is used to determine a channel where the least energy was detected. If
an Active Scan was performed (Reassign_PANID Flag set), the channels used by the detected
PANs are eliminated as possible channels. Thus, the results of the Energy Scan and the Active
Scan (if performed) are used to find the best channel (channel with the least energy that is not
used by any detected PAN). Once the best channel has been selected, the CH (Channel) param-
eter value is updated to that channel.
Not Set (bit 1 = 0) - The Coordinator retains its CH setting. An Energy Scan is not performed.
3. Start Coordinator
The Coordinator starts on the specified channel (CH parameter) and PAN ID (ID parameter).
Note, these may be selected in steps 1 and/or 2 above. The Coordinator will only allow End
Devices to associate to it if the A2 parameter “Allow_Association” flag is set. Once the Coordina-
tor has successfully started, the Associate LED will blink 1 time per second. (The LED is solid if
the Coordinator has not started.)
4. Coordinator Changes
Once a Coordinator has started, changing A2 (Reassign_Channel or Reassign_PANID bits), ID,
CH, or MY will cause the Coordinator to restart. Changing the A2 Allow_Association bit will not
restart the Coordinator. In a non-beaconing system, any End Devices that associated to the
Coordinator prior to a Restart will not be alerted to the Coordinator restart. Thus, if the Coordi-
nator were to change its ID, CH or MY settings, the End Devices would no longer be able to
communicate with the non-beacon Coordinator. Once a Coordinator has started, the ID, CH, MY
or A2 (Reassign_Channel or Reassign_PANID bits) should not be changed.
End Device Power-up
End Device power-up is governed by the A1 (End Device Association) command. On power up, the
End Device undergoes the following sequence of events:
1. Check A1 parameter - AutoAssociate Bit
Set (bit 2 = 1) - End Device will attempt to associate to a Coordinator. (refer to steps 2-3).
Not Set (bit 2 = 0) - End Device will not attempt to associate to a Coordinator. The End Device
will operate as specified by its ID, CH and MY parameters. Association is considered complete
and the Associate LED will blink quickly (5 times per second). When the AutoAssociate bit is not
set, the remaining steps (2-3) do not apply.
2. Discover Coordinator (if Auto-Associate Bit Set)
The End Device issues an Active Scan. The Active Scan selects one channel and transmits a
BeaconRequest command to the broadcast address (0xFFFF) and broadcast PAN ID (0xFFFF). It
then listens on that channel for beacons from any Coordinator operating on that channel. The
listen time on each channel is determined by the SD parameter.
Once the time expires on that channel, the Active Scan selects another channel and again
transmits the BeaconRequest command as before. This process continues until all channels
have been scanned, or until 5 PANs have been discovered. When the Active Scan is complete,
the results include a list of PAN IDs and Channels that are being used by detected PANs.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 12
The End Device selects a Coordinator to associate with according to the A1 parameter
“Reassign_PANID” and “Reassign_Channel” flags:
Reassign_PANID Bit Set (bit 0 = 1)- End Device can associate with a PAN with any ID value.
Reassign_PANID Bit Not Set (bit 0 = 0) - End Device will only associate with a PAN whose
ID setting matches the ID setting of the End Device.
Reassign_Channel Bit Set (bit 1 = 1) - End Device can associate with a PAN with any CH
value.
Reassign_Channel Bit Not Set (bit 1 = 0)- End Device will only associate with a PAN whose
CH setting matches the CH setting of the End Device.
After applying these filters to the discovered Coordinators, if multiple candidate PANs exist, the
End Device will select the PAN whose transmission link quality is the strongest. If no valid Coor-
dinator is found, the End Device will either go to sleep (as dictated by its SM (Sleep Mode)
parameter) or retry Association.
Note - An End Device will also disqualify Coordinators if they are not allowing association (A2 -
AllowAssociation bit); or, if the Coordinator is not using the same NonBeacon scheme as the
End Device. (They must both be programmed with NonBeacon code.)
3. Associate to Valid Coordinator
Once a valid Coordinator is found (step 2), the End Device sends an AssociationRequest mes-
sage to the Coordinator. It then waits for an AssociationConfirmation to be sent from the Coor-
dinator. Once the Confirmation is received, the End Device is Associated and the Associate LED
will blink rapidly (2 times per second). The LED is solid if the End Device has not associated.
4. End Device Changes once an End Device has associated
Changing A1, ID or CH parameters will cause the End Device to disassociate and restart the
Association procedure.
If the End Device fails to associate, the AI command can give some indication of the failure.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 13
2.5. Modes of Operation
XBee-PRO RF Modems operate in five modes.
Figure2‐02. XBee‐PRORFModem
ModesofOperation
2.5.1. Idle Mode
When not receiving or transmitting data, the RF modem is in Idle Mode. The modem shifts into the
other modes of operation under the following conditions:
• Transmit Mode (Serial data is received in the DI Buffer)
• Receive Mode (Valid RF data is received through the antenna)
• Sleep Mode (Sleep Mode condition is met)
• Command Mode (Command Mode Sequence is issued)
2.5.2. Transmit / Receive Modes
RF Data Packets
Each transmitted data packet contains a <Source Address> and <Destination Address> field. The
<Source Address> matches the address of the transmitting modem as specified by the MY (Source
Address) parameter (if MY >= 0xFFFE), the SH (Serial Number High) or the SL (Serial Number
Low) parameters. The <Destination Address> field is created from the DH and DL parameter val-
ues. The <Source Address> and/or <Destination Address> fields will either contain a short 16-bit
or long 64-bit address.
The RF data packet structure follows the 802.15.4 specification.
Direct and Indirect Transmission
There are two methods to transmit data. The first method, Direct Transmission, transmits data
immediately to the <Destination Address>. The second method, Indirect Transmission, retains a
packet for a period of time and transmits the data only after the destination modem (<RF Modem
Source Address> = <Data Destination Address>) requests the data. Indirect Transmissions can
only occur on a Coordinator. Thus, if all devices in a network are End Devices, only Direct Trans-
missions will occur. Indirect Transmissions are useful to ensure packet delivery to a sleeping
device. The Coordinator currently is able to retain up to 2 indirect messages.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 14
Direct Transmission
A NonBeaconing Coordinator can be configured to only use Direct Transmission by setting the SP
(Cyclic Sleep Period) parameter to “0”. Also, a NonBeaconing Coordinator using indirect transmis-
sions will revert to direct transmission if it knows the destination modem is awake.
To enable this behavior, the ST (Time before Sleep) value of the Coordinator must be set to match
the ST value of the End Device. Once the End Device either transmits data to the Coordinator or
polls the Coordinator for data, the Coordinator will use direct transmission for all subsequent data
transmissions to that modem address until ST time (or number of beacons) occurs with no activity
(at which point it will revert to using indirect transmissions for that modem address). “No activity”
means no transmission or reception of messages with a specific address. Global messages will not
reset the ST timer.
Indirect Transmission
To configure Indirect Transmissions in a PAN (Personal Area Network), the SP (Cyclic Sleep Period)
parameter value on the Coordinator must be set to match the longest sleep value of any End
Device. The SP parameter represents time in NonBeacon systems and beacons in Beacon-enabled
systems. The sleep period value on the Coordinator determines how long (time or number of bea-
cons) the Coordinator will retain an indirect message before discarding it.
In NonBeacon networks, an End Device must poll the Coordinator once it wakes from Sleep to
determine if the Coordinator has an indirect message for it. For Cyclic Sleep Modes, this is done
automatically every time the modem wakes (after SP time). For Pin Sleep Modes, the A1 (End
Device Association) parameter value must be set to enable Coordinator polling on pin wake-up.
Alternatively, an End Device can use the FP (Force Poll) command to poll the Coordinator as
needed.
Transmission Algorithm
Prior to transmitting a packet, a CCA (Clear Channel Assessment) is performed on the channel to
determine if the channel is available for transmission. The detected energy on the channel is com-
pared with the CA (Clear Channel Assessment) parameter value. If the detected energy exceeds
the CA parameter value, the packet is not transmitted.
Also, a delay is inserted before a transmission takes place. This delay is settable using the RN
(Backoff Exponent) parameter. If RN is set to “0”, then there is no delay before the first CCA is per-
formed. The RN parameter value is the equivalent of the “minBE” parameter in the 802.15.4 spec-
ification. The transmit sequence follows the 802.15.4 specification.
Acknowledgement
If the transmission is not a broadcast message, the modem will expect to receive an acknowledge-
ment from the destination device. If an acknowledgement is not received, the packet will be resent
up to 3 more times. If the acknowledgement is not received after all transmissions, an ACK failure
is recorded.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 15
2.5.3. Sleep Mode
Sleep Modes enable the RF modem to enter states of low-power consumption when not in use. In
order to enter Sleep Mode, one of the following conditions must be met (in addition to the modem
having a non-zero SM parameter value):
• DTR (Data Terminal Ready) is de-asserted.
• The modem is idle (no data transmission or reception) for the amount of time defined by the
ST (Time before Sleep) parameter. [NOTE: ST is only active when SM = 4-6]
The SM command is central to setting Sleep Mode configurations. By default, Sleep Modes are dis-
abled (SM = 0) and the modem remains in Idle/Receive Mode. When in this state, the modem is
constantly ready to respond to serial or RF activity.
Pin/Host-controlled Sleep Modes
Pin Hibernate (SM = 1)
• Pin/Host-controlled
• Typical power-down current: < 25 mA
• Wake-up time: 13.2 msec
Pin Hibernate Mode minimizes quiescent power (power consumed when in a state of rest or inac-
tivity). This mode is voltage level-activated; when DTR is de-asserted, the modem will finish any
transmit or receive activities, enter Idle Mode and then enter a state of sleep. The modem will not
respond to either serial or RF activity while in pin sleep.
To wake a sleeping modem operating in Pin Hibernate Mode, assert DTR (Data Terminal Ready).
The modem will wake when DTR is asserted and is ready to transmit or receive when the CTS line
is low. When waking the modem, the pin must be asserted at least two 'byte times' after CTS goes
low. This assures that there is time for the data to enter the DI buffer.
Pin Doze (SM = 2)
• Pin/Host-controlled
• Typical power-down current: < 25 mA
• Wake-up time: 2 msec
Pin Doze Mode functions as does Pin Hibernate Mode; however, Pin Doze features faster wake-up
time and higher power consumption. This mode is voltage level-activated; when DTR is de-
asserted, the modem will finish any transmit or receive activities, enter Idle Mode and then enter
a state of sleep. The modem will not respond to either serial or RF activity while in pin sleep.
To wake a sleeping modem operating in Pin Doze Mode, assert DTR (Data Terminal Ready). The
modem will wake when DTR is asserted and is ready to transmit or receive when the CTS line is
low. When waking the modem, the pin must be asserted at least two 'byte times' after CTS goes
low. This assures that there is time for the data to enter the DI buffer.
Table2‐02. SleepModeConfigurations
SleepMode
Setting Transition into Sleep Mode Transition out of Sleep Mode (wake) Characteristics Related Commands Power Consumption
Pin Hibernate
(SM = 1) De-assert DTR (Data Terminal Ready) Assert DTR Pin/Host-controlled (SM) < 25 mA
Pin Doze
(SM = 2) De-assert DTR (Data Terminal Ready) Assert DTR Pin/Host-controlled (SM) < 25 mA
Cyclic Sleep
(SM = 4 - 6)
Automatic transition to
Sleep Mode as defined by
the SM (Sleep Mode) and
ST (Time before Sleep)
parameters.
Transition occurs after the
cyclic sleep time interval
elapses. The time interval
isdefinedbytheSP (Cyclic
Sleep Period) parameter.
RFmodem wakesin
pre-determined time
intervals to detect if
RF data is present. (SM), SP, ST < 25 mA
when sleeping

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 16
Cyclic Sleep Modes
Cyclic Sleep Remote (SM = 4)
• Typical Power-down Current: < 25 mA (when asleep)
• Wake-up time: 2 msec
The Cyclic Sleep Modes allow modems to periodically check for RF data. When the SM parameter is
set to ‘4’, the modem is configured to sleep, then wakes once a cycle to check for data from a
modem configured as a Cyclic Sleep Coordinator (SM = 6). The Cyclic Sleep Remote sends a poll
request to the Coordinator at a specific interval set by the SP (Cyclic Sleep Period) parameter. The
Coordinator will transmit any queued data addressed to that specific remote upon receiving the
poll request.
If no data is queued for the remote, the Coordinator will not transmit and the remote will return to
sleep for another cycle. If queued data is transmitted back to the remote, it will stay awake to
allow for back and forth communication until the ST (Time before Sleep) timer expires.
Also note that CTS will go low each time the remote wakes, allowing for communication initiated
by the remote host if desired.
Cyclic Sleep Remote with Pin Wake-up (SM = 5)
Use this mode to wake a sleeping remote modem through either the RF interface or by the asser-
tion of DTR for event-driven communications. The cyclic sleep mode works as described above
(Cyclic Sleep Remote) with the addition of a pin-controlled wake-up at the remote modem. The
DTR pin is edge-triggered, not level-triggered. The modem will wake when a low is detected then
set CTS low as soon as it is ready to transmit or receive.
Any activity will reset the ST (Time before Sleep) timer so the modem will go back to sleep only
after there is no activity for the duration of the timer. Once the modem wakes (pin-controlled),
further pin activity is ignored. The modem transitions back into sleep according to the ST time
regardless of the state of the pin.
<Cyclic Sleep Coordinator (SM = 6)>
• Typical current = Receive current
• Always awake
This parameter value (SM=6) exists solely for backwards compatibility with firmware version 1.x60. If
backwards compatibility with the older firmware version is not required, always use the CE (Coordina-
tor Enable) command to enable a Coordinator.
Use this mode to configure a modem to wake cyclic sleeping remotes through the RF interface.
The cyclic sleep Coordinator will accept a message addressed to a specific remote 16 or 64-bit
address and hold it in a buffer until the remote wakes and sends a poll to request the message.
Messages not sent directly (buffered and requested) are called "Indirect messages". The Coordina-
tor will only queue one indirect message at a time. The Coordinator will hold the indirect message
for a period 2.5 times the sleeping period indicated by the SP (Cyclic Sleep Period) parameter. The
Coordinator's SP parameter should be set to match the value used by the remotes.
The ST parameters of the Coordinator and remotes should be set to the same value because the
Coordinator will track the 'awake' period of the recent 10 remotes to wake. If the Coordinator
receives additional messages addressed to a remote that should be awake, the Coordinator will
send a direct message to that remote instead of queuing it. The Coordinator is always awake so
that any remote unit can transmit either a poll request or a data message at any time.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 17
2.5.4. Command Mode
AT Command Mode
To Enter AT Command Mode:
Default AT Command Mode Sequence (for transition to Command Mode):
• No characters sent for one second [GT (Guard Times) parameter = 0x3E8]
• Input three plus characters (“+++”) within one second [CC (Command Sequence Character)
parameter = 0x2B.]
• No characters sent for one second [GT (Guard Times) parameter = 0x3E8]
All of the parameter values in the sequence can be modified to reflect user preferences.
To Send AT Commands:
Figure2‐03.SyntaxforsendingATCommands
To read a parameter value stored in the RF modem’s register, leave the parameter field blank.
The preceding example would change the RF modem Destination Address (Low) to “0x1F”. To
store the new value to non-volatile (long term) memory, subsequently send the WR (Write) com-
mand.
For modified parameter values to persist in the modem’s registry, changes must be saved to non-
volatile memory using the WR (Write) Command. Otherwise, parameters are restored to previ-
ously saved values after the modem is powered off and then on again (or re-booted).
System Response. When a command is sent to the RF modem, the modem will parse and exe-
cute the command. Upon successful execution of a command, the modem returns an “OK” mes-
sage. If execution of a command results in an error, the modem returns an “ERROR” message.
To Exit AT Command Mode:
For an example that illustrates programming the RF modem using AT Commands, refer to the "RF
Modem Configuration" chapter [p19].
Send the 3-character command sequence “+++” and observe guard times before and after the
command characters. [Refer to the “Default AT Command Mode Sequence” below.]
Send AT commands and parameters using the syntax shown below.
1. Send ATCN (Exit Command Mode) Command.
[OR]
2. If no valid AT Commands are received within the time specified by CT (Command Mode
Timeout) Command, the RF modem automatically returns to Idle Mode.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 18
2.6. Addressing
Every RF data packet sent over-the-air contains a Source Address and Destination Address field in
its header. The RF modem conforms to the 802.15.4 specification and supports both short 16-bit
addresses and long 64-bit addresses. A unique 64-bit IEEE source address is assigned at the fac-
tory and can be read with the SL (Serial Number Low) and SH (Serial Number High) commands.
Short addressing must be configured manually. A modem will use its unique 64-bit address as its
Source Address if its MY (16-bit Source Address) value is “0xFFFF” or “0xFFFE”.
To send a packet to a specific modem using 64-bit addressing: Set Destination Address (DL + DH)
to match the Source Address (SL + SH) of the intended destination modem.
To send a packet to a specific modem using 16-bit addressing: Set DL (Destination Address Low)
parameter to equal the MY parameter and set the DH (Destination Address High) parameter to ‘0’.
2.6.1. Unicast Mode
By default, the RF modem operates in Unicast Mode. Unicast Mode is the only mode that supports
retries. While in this mode, receiving modems send an ACK (acknowledgement) of RF packet
reception to the transmitter. If the transmitting modem does not receive the ACK, it will re-send
the packet up to three times or until the ACK is received.
Short 16-bit addresses. The modem can be configured to use short 16-bit addresses as the
Source Address by setting (MY < 0xFFFE). Setting the DH parameter (DH = 0) will configure the
Destination Address to be a short 16-bit address (if DL < 0xFFFE). For two modems to communi-
cate using short addressing, the Destination Address of the transmitter modem must match the
MY parameter of the receiver.
The following table shows a sample network configuration that would enable Unicast Mode com-
munications using short 16-bit addresses.
Long 64-bit addresses. The RF modem’s serial number (SL parameter concatenated to the SH
parameter) can be used as a 64-bit source address when the MY (16-bit Source Address) parame-
ter is disabled. When the MY parameter is disabled (set MY = 0xFFFF or 0xFFFE), the modem’s
source address is set to the 64-bit IEEE address stored in the SH and SL parameters.
When an End Device associates to a Coordinator, its MY parameter is set to 0xFFFE to enable 64-
bit addressing. The 64-bit address of the modem is stored as SH and SL parameters. To send a
packet to a specific modem, the Destination Address (DL + DH) on one modem must match the
Source Address (SL + SH) of the other.
2.6.2. Broadcast Mode
Any RF modem within range will accept a packet that contains a broadcast address. When config-
ured to operate in Broadcast Mode, receiving modems do not send ACKs (Acknowledgements) and
transmitting modems do not automatically re-send packets as is the case in Unicast Mode.
To send a broadcast packet to all modems regardless of 16-bit or 64-bit addressing, set the desti-
nation addresses of all the modems as shown below.
Sample Network Configuration (All modems in the network):
• DL (Destination Low Address) = 0x0000FFFF
• DH (Destination High Address) = 0x00000000 (default value)
NOTE: When programming the modem, parameters are entered in hexadecimal notation (without the
“0x” prefix). Leading zeros may be omitted.
Table2‐03. SampleUnicastNetworkConfiguration(using16‐bitaddressing)
Parameter RF Modem 1 RF Modem 2
MY (Source Address) 0x01 0x02
DH (Destination Address High) 0 0
DL (Destination Address Low) 0x02 0x01

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 19
3.RFModemConfiguration
3.1. Programming the RF Modem
Refer to the Command Mode section [p17] for more information about entering Command Mode,
sending AT commands and exiting Command Mode. For information regarding modem program-
ming using API Mode, refer to the API Operation sections [p40].
3.1.1. Programming Examples
Setup
Sample Configuration: Modify RF Modem Destination Address
Sample Configuration: Restore RF Modem Defaults
The programming examples in this section require the installation of MaxStream's X-CTU Soft-
ware and a USB connection to a PC.
1. Install MaxStream's X-CTU Software to a PC by double-clicking the "setup_X-CTU.exe" file.
(The file is located on the MaxStream CD and under the 'Software' section of the following
web page: www.maxstream.net/helpdesk/download.php)
2. Connect the RF modem to a PC.
3. Launch the X-CTU Software and select the 'PC Settings' tab. Verify the baud and parity set-
tings of the Com Port match those of the RF modem.
NOTE: Failure to enter AT Command Mode is most commonly due to baud rate mismatch.
Ensure the ‘Baud’ setting on the ‘PC Settings’ tab matches the interface data rate of the RF
modem (by default, BD parameter = 3 (which corresponds to 9600 bps)).
Example: Utilize the 'Terminal' tab of the X-CTU Software to change the RF modem's DL (Desti-
nation Address Low) parameter and save the new address to non-volatile memory.
After establishing a serial connection between the RF modem and a PC [refer to the 'Setup' sec-
tion above], select the ‘Terminal’ tab of the X-CTU Software and enter the following command
lines (‘CR’ stands for carriage return):
Method 1 (One line per command))
Send AT Command
+++
ATDL <Enter>
ATDL1A0D <Enter>
ATWR <Enter>
ATCN <Enter>
System Response
OK <CR> (Enter into Command Mode)
{current value} <CR> (Read Destination Address Low)
OK <CR> (Modify Destination Address Low)
OK <CR> (Write to non-volatile memory)
OK <CR> (Exit Command Mode)
Method 2 (Multiple commands on one line)
Send AT Command
+++
ATDL <Enter>
ATDL1A0D,WR,CN <Enter>
System Response
OK <CR> (Enter into Command Mode)
{current value} <CR> (Read Destination Address Low)
OK <CR> (Execute commands)
Example: Utilize the 'Modem Configuration' tab of the X-CTU Software to restore default param-
eter values of the RF modem.
After establishing a connection between the RF modem and a PC [refer to the 'Setup' section
above], select the 'Modem Configuration' tab of the X-CTU Software.
1. Select the 'Read' button.
2. Select the 'Restore' button.

XBee‐PROPKG‐U™USBRFModem–802.15.4‐ProductManualv1.x82[2006.04.24]
©2006MaxStream,Inc.,Confidential&Proprietary‐AllRightsReserved 20
3.2. Command Reference Tables
XBee-PRO RF Modems expect numerical values in hexadecimal. Hexadecimal values are desig-
nated by a “0x” prefix. Decimal equivalents are designated by a “d” suffix. Table rows are sorted
by command category, then by logic of most commonly used.
All modems operating within the same network should contain the same firmware version.
Special Commands
Networking Commands
Table3‐01. XBee‐PROCommands‐Special
AT
Command Command Category Name and Description Parameter Range Default
FR Special Software Reset. Responds immediately with an OK then performs a hard reset
~100ms later. --
RE Special Restore Defaults. Restore modem parameters to factory defaults. - -
WR Special Write. Write parameter values to non-volatile memory so that parameter modifications
persist through subsequent power-up or reset.
Note: Once WR is issued, no additional characters should be sent to the modem until
after the response "OK\r" is received. --
Table3‐02. XBee‐PROCommands‐Networking(Sub‐categoriesdesignatedwithin{brackets})
AT
Command Command Category Name and Description Parameter Range Default
CH Networking
{Addressing} Channel. Set/Read the channel number used for transmitting and receiving between RF modems. Uses 802.15.4 protocol channel numbers. 0x0C - 0x17 0x0C (12d)
ID Networking
{Addressing} PAN ID. Set/Read the PAN (Personal Area Network) ID. Use 0xFFFF to send messages to all PANs. 0xFFFF 0x3332 (13106d)
DH Networking
{Addressing}
Destination Address High. Set/Read the upper 32 bits of the 64-bit destination
address. When combined with DL, it defines the destination address used for
transmission. To transmit using a 16-bit address, set DHparameter to zero andDL less
than 0xFFFF. 0x000000000000FFFF is the broadcast address for the PAN. 0 - 0xFFFFFFFF 0
DL Networking
{Addressing}
Destination Address Low. Set/Read the lower 32 bits of the 64-bit destination
address. When combined with DH, DL defines the destination address used for
transmission. To transmit using a 16-bit address, set DHparameter to zero andDL less
than 0xFFFF. 0x000000000000FFFF is the broadcast address for the PAN. 0 - 0xFFFFFFFF 0
MY Networking
{Addressing} 16-bit Source Address. Set/Read the RF modem 16-bit source address. Set MY =
0xFFFF to disable reception of packets with 16-bit addresses. 64-bit source address
(serial number) and broadcast address (0x000000000000FFFF) is always enabled. 0 - 0xFFFF 0
SH Networking
{Addressing} Serial Number High. Read high 32 bits of the RF modem's unique IEEE 64-bit address. 64-bit source address is always enabled. 0 - 0xFFFFFFFF [read-only] Factory-set
SL Networking
{Addressing} Serial Number Low. Read low 32 bits of the RF modem's uniqueIEEE 64-bit address. 64-bit source address is always enabled. 0 - 0xFFFFFFFF [read-only] Factory-set
RN Networking
{Addressing} Random Delay Slots. Set/Read the minimum value of the back-off exponent in the
CSMA-CA algorithm thatis used for collision avoidance. If RN= 0, collision avoidance
is disabled during the first iteration of the algorithm (802.15.4 - macMinBE). 0 - 3 [exponent] 0
MM Networking
{Addressing}
MAC Mode. Set/Read MAC Mode value. MAC Mode enables/disables the use of a
MaxStream header in the 802.15.4 RF packet. When Mode 0 is enabled (MM=0),
duplicate packet detection is enabled as well as certain AT commands. Modes 1 and 2
are strict 802.15.4 modes. 0 - 2 0
NI Networking
{Identification}
Node Identifier. Stores a string identifier. The register only accepts printable ASCII
data.Astring can notstartwith a space.Carriagereturn endscommand.Commandwill
automatically end when maximum bytes for the string have been entered. This string is
returned as part of the ND (Node Discover) command. This identifier is also used with
the DN (Destination Node) command.
20 byte ACII string -
ND Networking
{Identification}
NodeDiscover. Discovers and reportsall RF modemsfound.Thefollowinginformation
is reported for each modem discovered (refer to long command description regarding
differences between Transparent and API operation).
MY<CR>
SH<CR>
SL<CR>
DB<CR>
NI<CR><CR>
After 2.5 seconds, the command ends by returning a <CR> (carriage return).
ND also accepts a Modem Identifier as a parameter. In this case, only a modem
matching the supplied identifier will respond.
optional 20 Byte NI value