MaxStream XBEEPRO XBEE-PRO OEM RF MODULE User Manual revised users manual

Download:
Mirror Download [FCC.gov]
Document ID	608560
Application ID	8Qtc2TBazcaOa59KwpzzMA==
Document Description	revised users manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	81.88kB (1023508 bits)
Date Submitted	2005-12-05 00:00:00
Date Available	2005-11-02 00:00:00
Creation Date	2005-12-02 09:39:11
Producing Software	Acrobat Distiller 7.0.5 (Windows)
Document Lastmod	2005-12-02 10:02:13
Document Title	product-manual_XBee.XBee-PRO_OEM_RF-Modules_v1.07c.book
Document Creator	FrameMaker 7.1
Document Author:	roberte

XBee™/XBee-PRO™ OEM RF Modules
XBee/XBee-PRO OEM RF Modules
RF Module Operation
RF Module Configuration
Appendices
Product Manual v1.x7C BETA
For OEM RF Module Part Numbers: XB24-...-001, XB24-...-002
XBP24-...-001, XBP24-...-002
ZigBee™/IEEE® 802.15.4 OEM RF Modules by MaxStream, Inc.
355 South 520 West, Suite 180
Lindon, UT 84042
Phone: (801) 765-9885
Fax: (801) 765-9895
rf-xperts@maxstream.net
www.MaxStream.net (live chat suport)
M100232
2005.12.02
XBee™/XBee‐PRO™ OEM RF Modules ‐ Product Manual v1.x7C BETA [2005.12.02]
© 2005 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™ and XBee‐PRO™ are trademarks of MaxStream, Inc.
ZigBee™ is a registered trademark of the ZigBee Alliance.
Technical Support:
Phone: (801) 765‐9885
Live Chat: www.maxstream.net
E‐mail: rf‐xperts@maxstream.net
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
ii
XBee™/XBee‐PRO™ OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Contents
1. XBee/XBee-PRO OEM RF Modules
1.1. Key Features 4
Appendix A: Agency Certifications
48
FCC Certification 48
1.1.1. Worldwide Acceptance 4
OEM Labeling Requirements 48
1.2. Specifications 5
FCC Notices 48
1.3. Mechanical Drawings 5
FCC-Approved Antennas (2.4 GHz) 49
1.4. Pin Signals 6
European Certification 50
1.5. Electrical Characteristics 6
2. RF Module Operation
OEM Labeling Requirements 50
Restrictions 50
Declarations of Conformity 50
2.1. Serial Communications 7
Appendix B: Development Guide
2.1.1. UART Data Flow 7
Development Kit Contents 51
2.1.2. Flow Control 8
Interfacing Options 51
2.1.3. Transparent Operation 9
RS-232 Interface Board 52
2.1.4. API Operation 9
Physical Interface 52
2.2. Networking Systems 10
2.2.1. NonBeacon 10
RS-232 Pin Signals 53
2.2.2. NonBeacon (w/ Coordinator) 10
Wiring Diagrams 54
Adapters 55
2.2.3. Beacon-enabled 11
USB Interface Board 56
2.2.4. Association 12
Physical Interface 56
2.3. Modes of Operation 15
USB Pin Signals 56
2.3.1. Idle Mode 15
2.3.2. Transmit & Receive Modes 15
Appendix C: Additional Information
2.3.3. Sleep Mode 18
57
1-Year Warranty 57
2.3.4. Command Mode 20
3. RF Module Configuration
51
21
Ordering Information 57
Contact MaxStream 58
3.1. Programming the RF Module 21
3.1.1. Programming Examples 21
3.2. Command Reference Tables 22
3.3. Command Descriptions 28
3.4. API Operation 43
3.4.1. API Frame Specifications 43
3.4.2. API Types 44
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
iii
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
1. XBee/XBee‐PRO OEM RF Modules
XBee and XBee-PRO Modules were engineered to meet
ZigBee/IEEE 802.15.4 standards and support the unique
needs of low-cost, low-power wireless sensor networks.
The modules require minimal power and provide reliable
delivery of critical data between devices.
The modules operate within the ISM 2.4 GHz frequency
band and are pin-for-pin compatible with each other.
1.1. Key Features
High Performance, Low Cost
XBee
Low Power
XBee
• Indoor/Urban: up to 100’ (30 m)
• TX Current: 45 mA (@3.3 V)
• Outdoor line-of-sight: up to 300’ (100 m)
• RX Current: 50 mA (@3.3 V)
• Transmit Power: 1 mW (0 dBm)
• Power-down Current: < 10 µA
• Receiver Sensitivity: -92 dBm
XBee-PRO
XBee-PRO
• TX Current: 270 mA (@3.3 V)
• Indoor/Urban: up to 300’ (100 m)
• RX Current: 55 mA (@3.3 V)
• Outdoor line-of-sight: up to 1 mile (1500 m)
• Power-down Current: < 10 µA
• Transmit Power: 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
Point-to-point, point-to-multipoint
and peer-to-peer topologies supported
Easy-to-Use
No configuration necessary for out-of box
RF communications
Free X-CTU Software
(Testing and configuration software)
AT and API Command Modes for
configuring module parameters
Small form factor
Network compatible with other
ZigBee/802.15.4 devices
Free & Unlimited Technical Support
128-bit Encryption (downloadable firmware
version coming soon)
Self-routing/Self-healing mesh networking
(downloadable firmware version coming soon)
1.1.1. Worldwide Acceptance
FCC Approval (USA) Refer to Appendix A [p48] for FCC Requirements.
Systems that include XBee/XBee-PRO Modules inherit MaxStream’s Certifications.
ISM (Industrial, Scientific & Medical) 2.4 GHz frequency band
Manufactured under ISO 9001:2000 registered standards
XBee/XBee-PRO RF Modules are optimized for use in US, Canada, Australia, Israel
and Europe (contact MaxStream for complete list of approvals).
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
1.2. Specifications
Table 1‐01.
Specifications of the XBee/XBee‐PRO OEM RF Modules
Specification
XBee
XBee-Pro
Performance
Indoor/Urban Range
up to 100 ft. (30 m)
Up to 300’ (100 m)
Outdoor RF line-of-sight Range
up to 300 ft. (100 m)
Up to 1 mile (1500 m)
Transmit Power Output
1mW (0 dBm)
60 mW (18 dBm) conducted, 100 mW (20 dBm) EIRP
RF Data Rate
250,000 bps
250,000 bps
Interface Data Rate
(software selectable)
1200 - 115200 bps
(non-standard baud rates also supported)
1200 - 115200 bps
(non-standard baud rates also supported)
Receiver Sensitivity
-92 dBm (1% packet error rate)
-100 dBm (1% packet error rate)
Supply Voltage
2.8 – 3.4 V
2.8 – 3.4 V
Transmit Current (typical)
45 mA (@ 3.3 V)
270 mA (@ 3.3 V)
Receive Current (typical)
50 mA (@ 3.3 V)
55 mA (@ 3.3 V)
Power-down Current
< 10 µA
< 10 µA
Operating Frequency
ISM 2.4 GHz
ISM 2.4 GHz
Dimensions
0.960” x 1.087” (2.438cm x 2.761cm)
0.960” x 1.297” (2.438cm x 3.294cm)
Operating Temperature
-40 to 85º C (industrial)
-40 to 85º C (industrial)
Antenna Options
U.FL Connector, Chip Antenna or Whip Antenna
U.FL Connector, Chip Antenna or Whip Antenna
Supported Network Topologies
Point-to-Point, Point-to-Multipoint,
Peer-to-Peer and Mesh (coming soon)
Point-to-Point, Point-to-Multipoint,
Peer-to-Peer and Mesh (coming soon)
Number of Channels
(software selectable)
16 Direct Sequence Channels
13 Direct Sequence Channels
Filtration Options
PAN ID, Channel and Source/Destination Addresses
PAN ID, Channel and Source/Destination Addresses
FCC Part 15.247
OUR-XBEE
pending
Industry Canada (IC)
pending
pending
Europe
pending
pending
Power Requirements
General
Networking & Security
Agency Approvals
1.3. Mechanical Drawings
Figure 1‐01. Mechanical drawings of the XBee/XBee‐PRO OEM RF Modules (antenna options not shown)
XBee and XBee‐PRO RF Modules are pin‐for‐pin compatible.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
1.4. Pin Signals
Figure 1‐02. XBee/XBee‐PRO RF Module Pin Number
(top sides shown ‐ shields on bottom)
Table 1‐02.
Pin Assignments for the XBee and XBee‐PRO Modules
(Low‐asserted signals are distinguished with a horizontal line above signal name.)
Pin #
Name
Direction
Description
VCC
Power supply
DOUT
Output
UART Data Out
DIN / CONFIG
Input
UART Data In
CD* / DOUT_EN* / DO8*
Output
Carrier Detect, TX_enable or Digital Output 8
RESET
Input
Module Reset
PWM0 / RSSI
Output
PWM Output 0 or RX Signal Strength Indicator
[reserved]
Do not connect
[reserved]
Do not connect
DTR / SLEEP_RQ / DI8
Input
Pin Sleep Control Line or Digital Input 8
10
GND
Ground
11
RF_TX* / AD4* / DIO4*
Either
Transmission Indicator, Analog Input 4 or Digital I/O 4
12
CTS / DIO7*
Either
Clear-to-Send Flow Control or Digital I/O 7
13
ON / SLEEP
Output
Module Status Indicator
14
VREF*
Input
Voltage Reference for A/D Inputs
15
Associate / AD5* / DIO5*
Either
Associated Indicator, Analog Input 5 or Digital I/O 5
16
RTS / AD6* / DIO6*
Either
Request-to-Send Flow Control, Analog Input 6 or Digital I/O 6
17
COORD_SEL* / AD3* / DIO3*
Either
Analog Input 3, Digital I/O 3 or Coordinator Select
18
AD2* / DIO2*
Either
Analog Input 2 or Digital I/O 2
19
AD1* / DIO1*
Either
Analog Input 1 or Digital I/O 1
20
AD0* / DIO0*
Either
Analog Input 0 or Digital I/O 0
* Functions not supported at the time of this release.
Design Notes:
• Minimum connections are: VCC, GND, DOUT and DIN.
• Signal Direction is specified with respect to the module
• Module includes a 50k Ω pull-up resistor attached to RESET
• Several input pull-ups can be configured using the PE command
• Unused pins should be left disconnected
1.5. Electrical Characteristics
Table 1‐03.
Symbol
DC Characteristics of the XBee & XBee‐PRO (VCC = 2.8 ‐ 3.4 VDC)
Parameter
Condition
VIL
Min
Typical
Max
Input Low Voltage
All Digital Inputs
VIH
Input High Voltage
All Digital Inputs
VOL
Output Low Voltage
IOL = 2 mA, VCC >= 2.7 V
Units
0.35 * VCC
0.7 * VCC
0.5
VOH
Output High Voltage
IOH = -2 mA, VCC >= 2.7 V
VCC - 0.5
IIIN
Input Leakage Current
VIN = VCC or GND, all inputs, per pin
0.025
uA
IIOZ
High Impedance Leakage Current
VIN = VCC or GND, all I/O High-Z, per pin
0.025
TX
Transmit Current
VCC = 3.3 V
45
(XBee)
RX
Receive Current
VCC = 3.3 V
50
(XBee)
PWR-DWN
Power-down Current
SM parameter = 1
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
< 10
uA
270
(PRO)
mA
55
(PRO)
mA
uA
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2. RF Module Operation
2.1. Serial Communications
The XBee/XBee-PRO OEM RF Modules interface to a host device through a logic-level asynchronous serial port. Through its serial port, the module can communicate with any logic and voltage
compatible UART; or through a level translator to any serial device (For example: RS-232/485/
422 or USB interface board).
2.1.1. UART Data Flow
Devices that have a UART interface can connect directly to the pins of the RF module as shown in
the figure below.
Figure 2‐01. System Data Flow Diagram in a UART‐interfaced environment
(Low‐asserted signals distinguished with horizontal line over signal name.)
Serial Data
Data enters the module UART through the DI pin (pin 3) as an asynchronous serial signal. The signal should idle high when no data is being transmitted.
Each data byte consists of a start bit (low), 8 data bits (least significant bit first) and a stop bit
(high). The following figure illustrates the serial bit pattern of data passing through the module.
Figure 2‐02. UART data packet 0x1F (decimal number ʺ31ʺ) as transmitted through the RF module
Example Data Format is 8‐N‐1 (bits ‐ parity ‐ # of stop bits)
The module UART performs tasks, such as timing and parity checking, that are needed for data
communications. Serial communications depend on the two UARTs to be configured with compatible settings (baud rate, parity, start bits, stop bits, data bits).
Both the module and host (PC) settings can be viewed and adjusted using MaxStream's proprietary X-CTU Software. Use the "PC Settings" tab to configure host settings. Use the "Terminal" or
"RF Module Configuration" tab to configure the module settings.
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 module (by default, BD
parameter = 3 (9600 bps)).
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.1.2. Flow Control
Figure 2‐03. Internal Data Flow Diagram
DI (Data In) Buffer
When serial data enters the RF module through the DI pin (pin 3), the data is stored in the DI
Buffer until it can be processed.
Hardware Flow Control (CTS). When the DI buffer is 17 bytes away from being full; by default,
the module de-asserts CTS (high) to signal to the host device to stop sending data [refer to D7
(DIO7 Configuration) parameter]. CTS is re-asserted after the DI Buffer has 34 bytes of memory
available.
How to eliminate the need for flow control:
1.
Send messages that are smaller than the DI buffer size.
2.
Interface at a lower baud rate [BD (Interface Data Rate) parameter] than the throughput
data rate.
Case in which the DI Buffer may become full and possibly overflow:
If the module is receiving a continuous stream of RF data, any serial data that arrives on the DI
pin is placed in the DI Buffer. The data in the DI buffer will be transmitted over-the-air when the
module is no longer receiving RF data in the network.
Refer to the RO (Packetization Timeout) [p38], BD (Baud Rate) [p30] and D7 (DIO7 Configuration) [p33]
command descriptions for more information.
DO (Data Out) Buffer
When RF data is received, the data enters the DO buffer and is sent out the serial port to a host
device. Once the DO Buffer reaches capacity, any additional incoming RF data is lost.
Hardware Flow Control (RTS). If RTS is enabled for flow control (D6 (DIO6 Configuration)
Parameter = 1), data will not be sent out the DO Buffer as long as RTS (pin 16) is de-asserted.
Two cases in which the DO Buffer may become full and possibly overflow:
1.
If the RF data rate is set higher than the interface data rate of the module, the module will
receive data from the transmitting module faster than it can send the data to the host.
2.
If the host does not allow the module to transmit data out from the DO buffer because of
being held off by hardware or software flow control.
Refer to the D6 (DIO6 Configuration) [p33] command description for more information.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.1.3. Transparent Operation
By default, XBee/XBee-PRO RF Modules operate in Transparent Mode. When operating in this
mode, the modules 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 module attempts to initialize an RF transmission. If the module cannot immediately 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 (maximum packet size) are received.
The module 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 module).
2.1.4. 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 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 DI pin (pin 3)) include:
• RF Transmit Data Frame
• Command Frame (equivalent to AT commands)
Receive Data Frames (sent out the DO pin (pin 2)) 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 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, RSSI and payload information from received data packets.
The API operation option facilitates many operations such as the examples cited below:
-> 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
To implement API operations, refer to API sections [p43].
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.2. Networking Systems
NonBeacon and Beacon-enabled systems require different firmware versions be loaded to the
module. Both firmware versions can be loaded to the module using MaxStream’s X-CTU Software.
The available configurations operate within the following networking system types:
• NonBeacon
• NonBeacon (w/ Coordinator)*
• Beacon-enabled*
* Networking system types not supported at the time of this release (v1.x7C BETA)
The following terms will be used to explicate the networking system types:
Table 2‐01.
Terms and definitions (Applicable networking system types are designated within .)
Term
Definition
Active Period
 A period of time that follows a beacon in which wireless data
communication can take place within a PAN.
Association

The establishment of membership between End Devices and a Coordinator.
Beacon
 Transmissions used to synchronize networked RF modules,
identify the PAN and describe the structure of the superframes.
Coordinator

A central RF module that is configured to provide synchronization services through the
transmission of beacons.
End Device
When in the same network as a Coordinator - RF modules 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.
2.2.1. NonBeacon
By default, XBee/XBee-PRO RF Modules are configured to support NonBeacon (no Coordinator)
communications. NonBeacon systems operate within a Peer-to-Peer network topology and are not
dependent upon Master/Slave relationships. This means that modules remain synchronized without use of master/server configurations and each module 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‐04. NonBeacon Peer‐to‐Peer Architecture
A peer-to-peer network can be established by
configuring each module to operate as an End Device (CE = 0), disabling End Device Association
on all modules (A1 = 0) and setting ID and CH parameters to be identical across the network.
2.2.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 indirect 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 [p12] for more information.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
10
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.2.3. Beacon-enabled
A Beacon-enabled network relies upon a Coordinator that sends a periodic beacon to all devices in
the network. The beacon is used to synchronize communications with End Devices and determine
wake periods.
Beacon-enabled networks are governed by the Beacon Order and active Superframe Order (BE
and SF parameters respectively) as defined by the Coordinator. All transmissions between the
Coordinator and End Device(s) must occur during the active portion of the Superframe.
Figure 2‐05. Beacon & Superframe Order (relative to time)
The period between successive beacons is bound by a Superframe. Each superframe period contains an Active and Inactive period. The SF command specifies the Active portion of the Superframe. If SF = BE, there is no Inactive period. If SF < BE, an Inactive period exists.
Durations of time are determined by the following formulas:
• Actual time is calculated from BE as: Time (msec) = (2 ^ BE) * 15.36 ms
• Actual Active Period time is calculated from SF as: Time (msec) = (2 ^ SF) * 15.36 ms.
Proper settings of the BE and SF parameters are application specific.
For example: A sensor may need to relay a few bytes of information every 4 minutes. A proper
configuration for such a scenario would set BE = 14 (4.19 min), SF = 1 (30.7 ms). Thus, after
each periodic beacon, transmissions may occur in a 30.7ms window; then the radios are silent.
Beacon-enabled communications are contention-based. This means a module will only transmit if
it first detects that no other transmissions are present.
End devices always use indirect messaging [refer to “Indirect Transmission” section, p16] and End
devices will always sleep during inactive periods.
For more information, refer to the BE and SF command descriptions ([p31] and [p40] respectively).
In Relation to Cyclic Sleep Configurations
End Devices can be configured to sleep during the Inactive period of the Superframe. This requires
the End Device be configured to operate as a Cyclic Sleep Remote [SM (Sleep Mode) parameter =
4) and SP (Cyclic Sleep Period) = 0].
In this scenario, the End Device will wake for each beacon to determine if the Coordinator is holding a message for it. If a message exists, it will poll the Coordinator to extract the data. Alternatively, End Devices can sleep through multiple beacons. For example, with BE = 4 (245 ms), and
SF = 1 (30.7 ms), an End Device could be configured to wake every 9th beacon (2.2 sec) by setting SP = 9. Note that SP on the Coordinator should match the highest SP on any End Device since
the Coordinator’s SP parameter determines the number of beacons that a Coordinator will hold a
message for an End Device to poll it. If sleeping through multiple beacons, the End Device will be
awake for at least one full beacon period before returning to sleep.
Sleep Modes and Association play critical roles in the implementation of a Beacon-enabled system.
Refer to the Sleep Mode [p18] and Association [following paragraph] sections for more information.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
11
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.2.4. Association
Association is the establishment of membership between End Devices and a Coordinator. It is only
applicable in Beacon-enabled and NonBeacon (w/ Coordinator) systems. The establishment of
membership is useful in scenarios that require a central unit (Coordinator) to relay messages to or
gather messages 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.
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.
Coordinator and End Device Setup and Operation
To configure a module 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 contain matching firmware versions (Beacon-enabled or NonBeacon).
Beacon-enabled Systems
If an End Device contains Beacon-enabled firmware and the AutoAssociate bit of the A1 (End
Device Association Options) parameter is set, the End Device will attempt to associate to a beaconing Coordinator. To ensure the Coordinator is detected, set the SD (Scan Duration) parameter
to be equal to or greater than the BE (Beacon Order) parameter of the Coordinator.
The frequency of beacons is determined by the BE (Beacon Order) parameter. End Devices can be
configured to sleep through multiple beacons or wake on every beacon. An ‘active period’ exists
after each beacon where communications can take place throughout the PAN. Communication
cannot take place outside of this active period. The active period after each beacon is determined
by the SF (Superframe) parameter. For example, if BE = 8 and SF = 2, beacons will be sent out
every 3.93 seconds and an active period of 61 ms exists after every beacon.
When a beaconing Coordinator receives data for an End Device, it will retain the message until the
End Device requests the data. This is called an ‘indirect transmission’. The beaconing Coordinator
will add the destination address of the message to the pending addresses field of the beacon. If an
End Device receives the beacon and finds its address included in the beacon, it will request the
data from the Coordinator. The Coordinator will only retain an indirect message for SP (Cyclic
Sleep Period) beacons. Refer to the Sleep Mode sections for more information [p18].
Consider the following guidelines when configuring a beaconing Coordinator:
• Set the SP (Cyclic Sleep Period) parameter to the largest SP setting of any End Device in the
PAN. (SP parameter determines the number of beacons that an End Device will sleep through
and thus, the number of beacons the Coordinator should retain an Indirect Message.)
• The ID (PAN ID) and CH (Channel) settings should be configured in conjunction with the A2
(Coordinator Association) parameter setting.
• If multiple Coordinators exist, the CD (Scan Duration) parameter should be set at least to the
largest BE value of any Coordinator that is expected to be operating in the area of the coordinator that is being configured.
NonBeacon (w/ Coordinator) Systems
In a NonBeacon (w/ Coordinator) system, the Coordinator can be configured to use direct or indirect 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.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
12
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
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 - Reassign_PANID Flag
Set - The Coordinator issues an Active Scan. The Active Scan selects one channel and transmits
a beacon request 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 Duraction) Parameter value. (To
ensure detection of all operating PANs, it is essential that SD be equal to the highest beacon
order (BE) of any beaconing Coordinators expected to be found.) Once the time expires on that
channel, the Active Scan selects another channel and again transmits the beacon request 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 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 - The Coordinator retains its ID setting. No active scan is performed.
2. Check A2 - Reassign_Channel Flag
Set - 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 SD. 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) parameter value is updated
to that channel.
Not Set - The Coordinator retains its CH setting. No energy scan is performed.
3. Start Coordinator
The Coordinator starts on the specified channel (CH) and PAN ID (ID). Note, these may be
selected in steps 1 and/or 2 above. If Beaconing code is used, the Coordinator will start with the
specified Beacon Order (BE) and Superframe Order (SF). The Coordinator will only allow End
Devices to associate to it if the A2 - Allow_Association flag is set. Once the Coordinator has successfully started, the Associate LED will blink 1x 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, MY, or BE/SF (for Beaconing Coordinator) 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 Coordinator 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.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
13
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
End Device Power-up
On power-up, the End Device undergoes the following sequence:
1. Check A1 - Auto-Associate Bit
Set - The End Device will attempt to associate to a Coordinator. (See steps 2-3).
Not Set - The End Device will not attempt to associate to a Coordinator. The End Device will
operate as specified by ID, CH, MY, etc. Association is considered complete, and the Associate
LED will blink quickly (5x per second). In this case, 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
beacon request 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 SD. (To ensure detection of all operating PANs, it
is essential that SD be equal to the highest beacon order (BE) of any beaconing Coordinators.)
Once the time expires on that channel, the Active Scan selects another channel and again
transmits the beacon request 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. The
End Device selects a Coordinator to associate with according to the A1 Reassign_PANID and
Reassign_Channel flags:
• Reassign_PANID Bit Set- The End Device can associate with a PAN with any ID value.
• Reassign_PANID Bit Not Set- The End Device will only associate with a PAN whose ID setting
matches the ID setting of the End Device.
• Reassign_Channel Bit Set- The End Device can associate with a PAN with any CH value.
• Reassign_Channel Bit Not Set- The 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 Coordinator is found, the End Device will wait for a random delay (value between 0 and AR hundredths of a second) and then retry association. Note - an End Device will also disqualify
Coordinators if they are not allowing association (A2 - Allow Association bit), or, if the Coordinator is not using the same Beacon/Non-Beacon scheme as the End Device. (They must both be
programmed with beaconing code, or both programmed with non-beaconing code.)
3. Associate to Valid Coordinator
Once a valid Coordinator is found (step 2), the End Device sends an Association Request message to the Coordinator. It then waits for an Association Confirmation to be sent from the Coordinator. Once the Confirmation is received, the End Device is Associated and the Associate LED
will blink rapidly (2x 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 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.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
14
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.3. Modes of Operation
XBee/XBee-PRO RF Modules operate in five modes.
Figure 2‐06. XBee/XBee‐PRO RF Module
Modes of Operation
2.3.1. Idle Mode
When not receiving or transmitting data, the RF module is in Idle Mode. The RF module 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.3.2. Transmit & Receive Modes
RF Data Packets
Each transmitted data packet contains a  and  field. The
 matches the address of the transmitting radio as specified by either the MY
(Source Address) parameter (if MY >= 0xFFFE), the SH (Serial Number High) and SL (Serial Number Low) parameters. The  field is created from the DH and DL parameter
values. The  and/or  fields will either contain a short 16bit or long 64-bit address.
The RF data packet structure follows the 802.15.4 specification.
[Refer to the Addressing section [p16] for more information]
Direct and Indirect Transmission
There are two methods to transmit data. The first method, Direct Transmission, transmits data
immediately to the . The second method, Indirect Transmission, retains a
packet for a period of time and transmits the data only after the destination module ( = ) requests the data. Indirect Transmissions can
only occur on a Coordinator. Thus, if all devices in a network are End Devices, only Direct Transmissions 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.
Note: A Beaconing Coordinator uses Indirect Transmission for all transmissions.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
15
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
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 transmissions will revert to direct transmission if it knows the destination module 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 module address until ST time (or number of beacons) occurs with no activity
(at which point it will revert to using indirect transmissions for that module 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 beacons) the Coordinator will retain an indirect message before discarding it.
In a Beacon-enabled network, the Coordinator transmits the destination addresses of all pending
indirect messages with each beacon. When an End Device receives the beacon, it will automatically poll the Coordinator and request the data (if it finds its address in the beacon).
In a NonBeacon network, 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 radio 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 compared with the CA (Clear Channel Assessment) parameter value. If the detected energy exceeds
the CA parameter value, the packet is not transmitted. Also, before transmission 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 performed. The RN is
equivalent of the “minBE” parameter in the 802.15.4 specification. The transmit sequence in both
beacon and NonBeacon modes follow the 802.15.4 specification.
Acknowledgement
If the transmission is not a broadcast message, the radio will expect to receive an acknowledgement 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.
Addressing
When communication occurs between two networked devices, each data packet contains a
 and a  field. The XBee/XBee-PRO RF Module 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 factory and can be read with the SL (Serial
Number Low) and SH (Serial Number High) parameters. Short addressing must be configured
manually. An RF module will use its unique 64-bit address as its Source Address if its MY value is
“0xFFFF” or “0xFFFE”.
To send a packet to a specific RF module using 64-bit addressing, set the Destination Address (DL
+ DH) to match the Source Address (SL + SH) of the intended destination RF module. To send a
packet to a specific RF module using 16-bit addressing, set the DL (Destination Address Low)
parameter to the MY (Source Address) parameter and set the DH (Destination Address High)
parameter to “0”.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
16
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Unicast Mode
Unicast Mode enables acknowledged communications. While in this mode, receiving modules send
an ACK (acknowledgement) of RF packet reception to the transmitter. If the transmitting module
does not receive the ACK, the transmitter will re-send the packet up to three times until the ACK is
received.
Unicast Mode is the only mode that supports retries.
Short 16-bit addresses. The module 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 modules to communicate using short addressing, the Destination Address of the transmitter module must match the
MY parameter of the receiver.
The following table shows a sample network configuration that would enable Unicast Mode communications using 16-bit short addresses.
Table 2‐02.
Sample Unicast Configuration (using 16‐bit addressing)
Parameter
RF Module 1
RF Module 2
0x02
MY (Source Address)
0x01
DH (Destination Address High)
DL (Destination Address Low)
0x02
0x01
Long 64-bit addresses. The RF module’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) parameter is disabled. When the MY parameter is disabled (set MY = 0xFFFF or 0xFFFE), the module’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 64bit addressing. The 64-bit address of the module is stored as SH and SL parameters. To send a
packet to a specific module, the Destination Address (DL + DH) on one module must match the
Source Address (SL + SH) of the other.
Broadcast Mode
Any RF module will accept a packet that contains a broadcast address. When configured to operate
in Broadcast Mode, receiving modules do not send ACKs (Acknowledgements) and transmitting RF
modules do not automatically re-send packets as is the case in Unicast Mode.
To send a broadcast packet to all modules regardless of 16-bit or 64-bit addressing, set destination addresses of all the modules as shown below.
Sample Configuration (All modules in the network):
• DL (Destination Low Address) = 0x0000FFFF
• DH (Destination High Address) = 0x00000000
NOTE: When programming the module, parameters are entered in hexadecimal notation (without
the “0x” prefix). Leading zeros may be omitted.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
17
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.3.3. Sleep Mode
Sleep Modes enable the RF module 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 module
having a non-zero SM parameter value):
• Sleep_RQ (pin 9) is asserted.
• The module 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-5.]
Table 2‐03.
Sleep Mode Configurations
Sleep Mode Transition into
Setting
Sleep Mode
Transition out of
Sleep Mode (wake)
Characteristics
Related
Commands
Power
Consumption
Pin Hibernate
(SM = 1)
Assert (high) Sleep_RQ
(pin 9)
De-assert (low) Sleep_RQ
Pin/Host-controlled /
NonBeacon systems (SM)
only / Lowest Power
< 10 µA (@3.0
VCC)
Pin Doze
(SM = 2)
Assert (high) Sleep_RQ
(pin 9
De-assert (low) Sleep_RQ
Pin/Host-controlled /
NonBeacon systems
(SM)
only / Fastest Wakeup
< 50 µA
Cyclic Sleep
(SM = 4 - 5)
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
is defined by the SP (Cyclic
Sleep Period) parameter.
RF Module wakes in
pre-determined time
intervals to detect if
RF data is present / (SM), SP, ST
When SM = 5,
NonBeacon systems
only
< 50 µA
when sleeping
The SM command is central to setting Sleep Mode configurations. By default, Sleep Modes are disabled (SM = 0) and the module remains in Idle/Receive Mode. When in this state, the module 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: < 10 µA (@3.0 VCC)
• Wake-up time: 13.2 msec
Pin Hibernate Mode minimizes quiescent power (power consumed when in a state of rest or inactivity). This mode is voltage level-activated; when Sleep_RQ is asserted, the module will finish any
transmit, receive or association activities, enter Idle Mode and then enter a state of sleep. The
module will not respond to either serial or RF activity while in pin sleep.
To wake a sleeping module operating in Pin Hibernate Mode, de-assert Sleep_RQ (pin 9). The
module will wake when Sleep_RQ is de-asserted and is ready to transmit or receive when the CTS
line is low. When waking the module, the pin must be de-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: < 50 µA
• 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.
To wake a sleeping module operating in Pin Doze Mode, de-assert Sleep_RQ (pin 9). The module
will wake when Sleep_RQ is de-asserted and is ready to transmit or receive when the CTS line is
low. When waking the module, the pin must be de-asserted at least two 'byte times' after CTS
goes low. This assures that there is time for the data to enter the DI buffer.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
18
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Cyclic Sleep Modes
Cyclic Sleep Remote (SM = 4)
• Typical Power-down Current: < 50 µA (when asleep)
• Wake-up time: 2 msec
The Cyclic Sleep Modes allow modules to periodically check for RF data. When the SM parameter is
set to ‘4’, the module is configured to sleep, then wakes once a cycle to check for data from a
module configured as a Cyclic Sleep Coordinator (SM = 0, CE = 1). 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 module through either the RF interface or by the deassertion of Sleep_RQ 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 module.
The Sleep_RQ pin is edge-triggered, not level-triggered. The module 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 module will go back to sleep only
after Sleep_RQ is asserted and there is no activity for the duration of the timer. Once the module
wakes (pin-controlled), further pin activity is ignored. The module transitions back into sleep
according to the ST time regardless of the state of the pin.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
19
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
2.3.4. Command Mode
To modify or read RF Module parameters, the module must first enter into Command Mode - a
state in which incoming characters are interpreted as commands. Two command modes are supported: AT Command Mode and ATI Command Mode.
A robust set of AT Commands is available for programming and customizing the module.
AT Command Mode
To Enter AT Command Mode:
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.]
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:
Send AT commands and parameters using the syntax shown below.
Figure 2‐07. Syntax for sending AT Commands
To read a parameter value stored in the RF module’s register, leave the parameter field blank.
The preceding example would change the RF module Destination Address (Low) to “0x1F”. To
store the new value to non-volatile (long term) memory, subsequently send the WR (Write) command.
For modified parameter values to persist in the module’s registry, changes must be saved to nonvolatile memory using the WR (Write) Command. Otherwise, parameters are restored to previously saved values after the module is powered off and then on again (or re-booted).
System Response. When a command is sent to the RF module, the module will parse and execute the command. Upon successful execution of a command, the module returns an “OK” message. If execution of a command results in an error, the module returns an “ERROR” message.
To Exit AT Command Mode:
1.
Send ATCN (Exit Command Mode) Command.
2.
If no valid AT Commands are received within the time specified by CT (Command Mode
Timeout) Command, the RF module automatically returns to Idle Mode.
[OR]
For an example of programming the RF module using AT Commands and descriptions of each configurable parameter, refer to the "RF Module Configuration" chapter [p21].
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
20
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
3. RF Module Configuration
3.1. Programming the RF Module
Refer to the “Command Mode” section [p20] for more information about entering Command Mode,
sending AT commands and exiting Command Mode.
3.1.1. Programming Examples
Setup
The programming examples in this section require the installation of MaxStream's X-CTU Software and a serial connection to a PC. (MaxStream stocks RS-232 and USB boards to facilitate
interfacing 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.
Mount the RF module to an interface board, then connect the module assembly to a PC.
3.
Launch the X-CTU Software and select the 'PC Settings' tab. Verify the baud and parity settings of the Com Port match those of the RF module.
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 module (by default, BD parameter = 3 (which corresponds to 9600 bps)).
Sample Configuration: Modify RF Module Destination Address
Example: Utilize the 'Terminal' tab of the X-CTU Software to change the RF module's DL (Destination Address Low) parameter and save the new address to non-volatile memory.
After establishing a serial connection between the RF module and a PC [refer to the 'Setup' section 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 
ATDL1A0D 
ATWR 
ATCN 
System Response
OK  (Enter into Command Mode)
{current value}  (Read Destination Address Low)
OK  (Modify Destination Address Low)
OK  (Write to non-volatile memory)
OK  (Exit Command Mode)
Method 2 (Multiple commands on one line)
Send AT Command
+++
ATDL 
ATDL1A0D,WR,CN 
System Response
OK  (Enter into Command Mode)
{current value}  (Read Destination Address Low)
OK  (Execute commands)
Sample Configuration: Restore RF Module Defaults
Example: Utilize the 'Modem Configuration' tab of the X-CTU Software to restore default parameter values of the RF module.
After establishing a connection between the RF module 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.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
21
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
3.2. Command Reference Tables
RF modems expect numerical values in hexadecimal. Hexadecimal values are designated by the
“0x” prefix. Decimal equivalents are designated by the “d” suffix. Table rows are sorted by command category, then by logic of most commonly used.
Special
Table 3‐01.
XBee/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 module parameters to factory defaults.
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 module until
after the response "OK\r" is received.
WR
Networking
Table 3‐02.
XBee/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 modules. Uses 802.15.4 protocol channel numbers.
0x0B - 0x1A (XBee)
0x0C - 0x18 (XBee-PRO)
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
0 - 0xFFFFFFFF
transmission. To transmit using a 16-bit address, set DH parameter to zero and DL less
than 0xFFFF. 0x000000000000FFFF is the broadcast address for the PAN.
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
0 - 0xFFFFFFFF
transmission. To transmit using a 16-bit address, set DH parameter to zero and DL less
than 0xFFFF. 0x000000000000FFFF is the broadcast address for the PAN.
MY
Networking
{Addressing}
16-bit Source Address. Set/Read the RF module 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
SH
Networking
{Addressing}
Serial Number High. Read high 32 bits of the RF module'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 module's unique IEEE 64-bit address.
0 - 0xFFFFFFFF [read-only]
64-bit source address is always enabled.
Factory-set
RN
Networking
{Addressing}
Random Delay Slots. Set/Read the minimum value of the back-off exponent in the
CSMA-CA algorithm that is 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]
MI
Networking
{Identification}
Modem Identifier. Stores a string identifier. The register only accepts printable ASCII
data. A string can not start with a space. Carriage return ends command. Command will
automatically end when maximum bytes for the string have been entered. This string is
returned as part of the MD (Modem Discover) command. This identifier is also used with
the DM (Destination Modem) command.
20 byte ACII string
Networking
{Identification}
Modem Discover. Discovers and reports all XBee Modems found. The following
information is reported for each modem discovered (refer to long command description
regarding differences between Transparent and API operation).
MY
SH
optional - MI
SL
MI
After 500 msec, the command ends by returning a  (carriage return).
MD also accepts a Modem Identifier as a parameter. In this case only a modem
matching the supplied identifier will respond.
Networking
{Identification}
Destination Modem. Resolves a Modem Identifier string to a physical address. The
following events occur upon successful command execution:
1. DL and DH are set to the address of the modem with the matching Modem Identifier.
20 byte ACII string
2. OK is returned.
If there is no response from a modem within 200 msec or a parameter is not specified
(left blank), the command is terminated and ERROR is returned.
MD
DM
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
22
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Table 3‐02.
XBee/XBee‐PRO Commands ‐ Networking (Sub‐categories designated within {brackets})
AT
Command
Command
Category
Name and Description
Parameter Range
Default
CE
Networking
{Association}
Coordinator Enable. Set/Read the coordinator setting.
0-1
0 = End Device
1 = Coordinator
SD
Networking
{Association}
Scan Duration. Set/Read the scan duration exponent.
End Device - Duration of Active Scan during Association. On beacon system, set SD =
BE of coordinator. SD must be set at least to the highest BE parameter of any
Beaconing Coordinator with which an End Device or Coordinator wish to discover.
Coordinator - If ‘ReassignPANID’ option is set on Coordinator [refer to A2 parameter],
SD determines the length of time the Coordinator will scan channels to locate existing
PANs. If ‘ReassignChannel’ option is set, SD determines how long the Coordinator will
perform an Energy Scan to determine which channel it will operate on.
0-0x0F [exponent]
‘Scan Time’ is measured as (# of channels to scan] * (2 ^ SD) * 15.36ms). The number
of channels to scan is set by the SC command. The XBee can scan up to 16 channels
(SC = 0xFFFF). The XBee PRO can scan up to 13 channels (SC = 0x3FFE).
Example: The values below show results for a 13 channel scan:
If SD = 0, time = 0.246 sec
SD = 8, time = 62.91 sec
SD = 2, time = 0.983 sec
SD = 10, time = 4.19 min
SD = 4, time = 3.93 sec
SD = 12, time = 16.77 min
SD = 6, time = 15.73 sec
SD = 14, time = 67.07 min
BE
Networking
{Association}
Beacon Order.  Set/Read the exponent used in calculating
beacon order. Beacon order specifies how often the coordinator transmits a beacon.
The actual time (msec) is calculated from BE as: Time = ((2 ^ BE) * 15.36 ms)
End devices automatically update their BE to match the coordinator upon association.
0-0x0E [exponent]
SF
Networking
{Association}
Superframe Order.  Set/Read the exponent used in
calculating superframe order. The superframe order specifies the length of the active
portion of the superframe (including the beacon frame). The SF parameter should be
set less than or equal to the BE parameter or upon exiting command mode, SF will be
set to equal BE. The actual Active Period time (ms) is calculated from SF as:
Time = (2 ^ SF) * 15.36 ms.
0-0x0E [exponent]
SA
Networking
{Association}
Resync Attempts.  Set/Read the number of times an End
Device will attempt to reacquire a lost beacon before disassociating from a Beaconing
Coordinator.
0-0x0F [# of attempts]
Networking
{Association}
End Device Association. Set/Read End Device association options.
bit 0 - ReassignPanID
0 - Will only associate with Coordinator operating on PAN ID that matches modem ID
1 - May associate with Coordinator operating on any PAN ID
bit 1 - ReassignChannel
0 - Will only associate with Coordinator operating on Channel that matches CH setting
1 - May associate with Coordinator operating on any Channel
bit 2 - AutoAssociate
0 - 0x0F [bit field]
0 - Device will not attempt Association
1 - Device attempts Association until success
Note: This bit is used only for Non-Beacon systems. End Devices in Beacon-enabled
system must always associate to a Coordinator
bit 3 - PollCoordOnPinWake
0 - Pin Wake will not poll the Coordinator for indirect (pending) data
1 - Pin Wake will send Poll Request to Coordinator to extract any pending data
bits 4 - 7 are reserved
Networking
{Association}
Coordinator Association. Set/Read Coordinator association options.
bit 0 - ReassignPanID
0 - Coordinator will not perform Active Scan to locate available PAN ID. It will operate
on ID (PAN ID).
1 - Coordinator will perform Active Scan to determine an available ID (PAN ID). If a
PAN ID conflict is found, the ID parameter will change.
bit 1 - ReassignChannel 0 - Coordinator will not perform Energy Scan to determine free channel. It will operate 0 - 7 [bit field]
on the channel determined by the CH parameter.
1 - Coordinator will perform Energy Scan to find a free channel, then operate on that
channel.
bit 2 - AllowAssociation 0 - Coordinator will not allow any devices to associate to it.
1 - Coordinator will allow devices to associate to it.
bits 3 - 7 are reserved
A1
A2
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
23
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Table 3‐02.
AT
Command
XBee/XBee‐PRO Commands ‐ Networking (Sub‐categories designated within {brackets})
Command
Category
Name and Description
Parameter Range
Default
AI
Networking
{Association}
Association Indication. Read errors with the last association request:
0x00 - Successful Completion - Coordinator successfully started or End Device
association complete
0x01 - Active Scan Timeout
0x02 - Active Scan found no PANs
0x03 - Active Scan found PAN, but the CoordinatorAllowAssociation bit is not set
0x04 - Active Scan found PAN, but Coordinator and End Device are not
configured to support beacons
0x05 - Active Scan found PAN, but the Coordinator ID parameter does not match
the ID parameter of the End Device
0x06 - Active Scan found PAN, but the Coordinator CH parameter does not match the
CH parameter of the End Device
0x07 - Energy Scan Timeout
0x08 - Coordinator start request failed
0x09 - Coordinator could not start due to invalid parameter
0x0A - Coordinator Realignment is in progress
0x0B - Association Request not sent
0x0C - Association Request timed out - no reply was received
0x0D - Association Request had an Invalid Parameter
0x0E - Association Request Channel Access Failure. Request was not transmitted CCA failure
0x0F - Remote Coordinator did not send an ACK after Association Request was sent
0x10 - Remote Coordinator did not reply to the Association Request, but an ACK was
received after sending the request
0x11 - [reserved]
0x12 - Sync-Loss - Lost synchronization with a Beaconing Coordinator
0x13 - Disassociated - No longer associated to Coordinator
0 - 0x13 [read-only]
DA
Networking
{Association}
Force Disassociation. End Device will immediately disassociate from a Coordinator (if
associated) and reattempt to associate.
FP
Networking
{Association}
Force Poll. Request indirect messages being held by a coordinator.
Networking
{Association}
Active Scan. Sends Beacon Request to Broadcast Address (0xFFFF) and Broadcast
PAN (0xFFFF) on every channel. The parameter determines the time the radio will
listen for Beacons on each channel. A PanDescriptor is created and returned for every
Beacon received from the scan. Each PanDescriptor contains the following information:
CoordAddress (SH, SL)
CoordPanID (ID)
CoordAddrMode 
0x02 = 16-bit Short Address
0x03 = 64-bit Long Address
Channel (CH parameter) 
SecurityUse
ACLEntry
SecurityFailure
SuperFrameSpec (2 bytes):
bit 15 - Association Permitted (MSB)
bit 14 - PAN Coordinator
bit 13 - Reserved
bit 12 - Battery Life Extension
bits 8-11 - Final CAP Slot
bits 4-7 - Superframe Order
bits 0-3 - Beacon Order
GtsPermit
RSSI (RSSI is returned as -dBm)
TimeStamp (3 bytes)

A carriage return  is sent at the end of the AS command. The Active Scan is
capable of returning up to 5 PanDescriptors in a scan. The actual scan time on each
channel is measured as Time = [(2 ^ PARAM) * 15.36] ms. Note the total scan time is
this time multiplied by the number of channels to be scanned (!6 for the XBee and 13 for
the XBee-PRO). Also refer to SD command description.
Networking
{Association}
Energy Scan. Sends Energy Detect Scan. The parameter determines length of scan on
each channel. The maximal energy on each channel is returned, each value is followed
by a carriage return. An additional carriage return is sent at the end of the command.
0-7
The values returned represent the detected energy level in units of -dBm. The actual
scan time on each channel is measured as Time = [(2 ^ PARAM) * 15.36] ms. Note the
total scan time is this time multiplied by the number of channels to be scanned. Refer to
SD parameter.
AS
ED
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
24
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
RF Interfacing
Table 3‐03.
XBee/XBee‐PRO Commands ‐ RF Interfacing
AT
Command
Command
Category
Name and Description
PL
RF Interfacing
Power Level. Select/Read the power level at which the RF module transmits conducted
0-4
power.
SC
RF Interfacing
Scan Channel. Set/Read list of channels to scan for all Active and Energy Scans as bit
field. This affects scans initiated in command mode (AS, ED) and during End Device
Association and Coordinator startup:
bit 0 - 0x0B
bit 8 - 0x13
bit 1 - 0x0C
bit 9 - 0x14
0-0xFFFF (bit field)
bit 2 - 0x0D
bit 10 - 0x15
bit 3 - 0x0E
bit 11 - 0x16
bit 4 - 0x0F
bit 12 - 0x17
bit 5 - 0x10
bit 13 - 0x18
bit 6 - 0x11
bit 14 - 0x19
bit 7 - 0x12
bit 15 - 0x1A
0x3FFE
(all XBeePRO
Channels)
CA
RF Interfacing
CCA Threshold. Set/read the CCA (Clear Channel Assessment) threshold. Prior to
transmitting a packet, a CCA is performed to detect energy on the transmit channel. If 0-0x50 [-dBm]
the detected energy is above the CCA Threshold, the radio will not transmit the packet.
0x4B
(-75d dBm)
Parameter Range
Default
Serial Interfacing
Table 3‐04.
AT
Command
AP
XBee/XBee‐PRO Commands ‐ Serial Interfacing
Command
Category
Serial
Interfacing
Name and Description
Parameter Range
Default
API Enable. Enable API Mode.
0-2
0 = Disabled
1 = API enabled
2 = API enabled
(w/escaped control
characters)
0-7
0 = 1200 bps
1 = 2400
2 = 4800
3 = 9600
4 = 19200
5 = 38400
6 = 57600
7 = 115200
(custom rates also supported)
BD
Serial
Interfacing
Interface Data Rate. Set/Read the serial interface data rate for communications
between the RF module serial port and host.
RO
Serial
Interfacing
Packetization Timeout. Set/Read number of character times of inter-character delay
required before transmission. Set to zero to transmit characters as they arrive instead of 0 - 0xFF [x character times]
buffering them into one RF packet.
D7
Serial
Interfacing
DIO7 Configuration. Select/Read options for the DIO7 line of the module.
0-1
0 = Disabled
1 = CTS Flow Control
D6
Serial
Interfacing
DIO6 Configuration. Select/Read options for the DIO6 line of the module. Options
include: RTS flow control.
0-1
0 = Disabled
1 = RTS flow control
D5
Serial
Interfacing
DIO5 Configuration. Configure options for the DIO5 line of the module. Options
include: Associated LED indicator (blinks when associated).
0-1
0 = Disabled
1 = Associated indicator
P0
Serial
Interfacing
PWM0 Configuration. Select/Read function for PWM0.
0-1
0 = Disabled
1 = RSSI
Serial
Interfacing
Pull-up Resistor Enable. Set/Read bitfield to configure internal pull-up resistor status
for I/O lines.
bit 0 - AD4/DIO4/RF_TX
bit 1 - COORD
bit 2 - AD2/DIO2
bit 3 - AD1/DIO1
bit 4 - AD0/DIO0
bit 5 - RTS
bit 6 - SLEEP_RQ
bit 7 - DIN/CONFIG
“1” specifies pull-up enabled, “0” specifies no pull-up
0 - 0xFF
0xFF
PE
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
25
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Sleep (Low Power)
XBee/XBee-PRO Commands - Sleep (Low Power)
AT
Command
Command
Category
Sleep
{NonBeacon}
Name and Description
Parameter Range
Default
Sleep Mode.  Set/Read Sleep Mode configurations.
0-5
0 = No Sleep
1 = Pin Hibernate
2 = Pin Sleep
3 = Reserved
4 = Cyclic sleep remote
5 = Cyclic sleep remote
w/ pin wake-up
0-5
0 = No Sleep
1 = n/a
2 = n/a
3 = Reserved
4 = Cyclic sleep remote
5 = n/a
SM
Sleep
Sleep Mode.  Set/Read Sleep Mode configurations.
{Beacon-enabled}
Sleep
{NonBeacon}
SP
Cyclic Sleep Period.  Set/Read sleep period for cyclic sleeping
remotes. Coordinator and End Device SP values should always be equal. To send
Direct Messages, set SP = 0.
0 - 0x68B0 [x 10 ms]
End Device - SP determines the sleep period for cyclic sleeping remotes. Maximum
sleep period is 268 seconds (0x68B0).
Coordinator - If non-zero, SP determines the time to hold an indirect message before
discarding it. A Coordinator will discard indirect messages after a period of (2.5 * SP).
Cyclic Sleep Period.  Set/Read sleep period for cyclic
sleeping remotes. Coordinator and End Device SP values should always be equal. To
send Direct Messages, set SP = 0.
End Device - SP determines the number of beacons a cyclic sleeping remote will sleep
Sleep
0 - 0x68B0 [beacons]
{Beacon-enabled} through. Because the maximum sleep period is 268 (decimal) seconds, SP must be
selected such that the equation (2^BE * (0.01536 seconds) * SP) < 268 seconds.
Coordinator - SP determines the number of beacons to retain an indirect message
before discarding it. A Coordinator will discard indirect messages after 2 * SP beacons.
Sleep
(Low Power)
DP
Disassociated Cyclic Sleep Period. 
End Device - Set/Read time period of sleep for cyclic sleeping remotes that are
configured for Association but are not associated to a Coordinator. (i.e. If a device is
configured to associate, configured as a Cyclic Sleep remote, but does not find a
Coordinator, it will sleep for DP time before reattempting association.) Maximum sleep
period is 268 seconds (0x68B0). DP should be > 0 for NonBeacon systems.
1 - 0x68B0 [x 10 ms]
Disassociated Cyclic Sleep Period. 
End Device - Set/Read the number of beacons the cyclic sleeping remote will sleep
Sleep
through on a failed association attempt before reattempting association. (i.e. If a device 1 - 0x68B0 [beacons]
{Beacon-enabled}
is configured for Association, configured as a Cyclic Sleep remote, and unable to find a
Coordinator; it will sleep for DP beacon times prior to reattempting association.)
Sleep
{NonBeacon}
ST
Time before Sleep.  Set/Read time period of inactivity (no serial
or RF data is sent or received) before activating Sleep Mode. ST parameter is only valid
with Cyclic Sleep settings (SM = 4 - 5).
1 - 0xFFFF [x 1 ms]
Coordinator and End Device ST values must be equal.
Also note, the GT parameter value must always be less than the ST value. (If GT > ST,
the configuration will render the module unable to enter into command mode.) If the ST
parameter is modified, also modify the GT parameter accordingly.
Time before Sleep.  Set/Read the number of beacons
received with no activity (no serial or RF data is sent or received) before activating
Sleep
{Beacon-enabled} Sleep Mode. ST parameter is only valid with the Cyclic Sleep setting (SM = 4).
The ST parameter is not used by a Beacon-enabled Coordinator.
1 - 0xFFFF [beacons]
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
0x0A (10d)
0x3E8
(1000d)
0x14 (20d)
0x1388
(5000d)
26
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Diagnostics
Table 3‐05.
XBee/XBee‐PRO Commands ‐ Diagnostics
AT
Command
Command
Category
Name and Description
Parameter Range
Default
EC
Diagnostics
CCA Failures. Reset/Read count of CCA (Clear Channel Assessment) failures. This
parameter value increments when the module does not transmit a packet because it
detected energy above the CCA threshold level set with CA command. This count
saturates at its maximum value. Set count to “0” to reset count.
0 - 0xFFFF
EA
Diagnostics
ACK Failures. Reset/Read count of acknowledgment failures. This parameter value
increments when the module expires its transmission retries without receiving an ACK
0 - 0xFFFF
on a packet transmission. This count saturates at its maximum value. Set the parameter
to “0” to reset count.
EH
Diagnostics
Echo. Sends command parameter as RF packet to remote modem which 'echoes' back
the data to the transmitting modem. This command uses the current setting of DL and
1 to 20 bytes
DH when transmitting the parameter. The command ends by sending a  (Carriage
Return).
VR
Diagnostics
Firmware Version. Read firmware version of the RF module.
0 - 0xFFFF [read-only]
Factory-set
HV
Diagnostics
Hardware Version. Read hardware version of the RF modem.
0 - 0xFFFF [read-only]
Factory-set
RP
Diagnostics
RSSI PWM Timer. Enable a PWM (pulse width modulation) output (on pin 3 of the RF
modules) which shows RX signal strength.
0 - 0xFF [x 100 ms]
0x28 (40d)
DB
Diagnostics
Received Signal Strength. Read signal level [in dB] of last good packet received
(RSSI). Absolute value is reported. (For example: 0x58 = -88 dBm) Reported value is
accurate between -40 dBm and RX sensitivity.
0 - 0x64 [read-only]
VL
Diagnostics
Verbose Version. Read detailed version information including application build date,
MAC, PHY and bootloader versions and build dates.
Diagnostics
Energy Scan. Send an “Energy Detect Scan”. This parameter determines the length of
scan on each channel. The maximal energy on each channel is returned and each
value is followed by a carriage return. The values returned represent the detected
0-7
energy level in units of -dBm. The actual scan time on each channel is measured as
Time = [(2 ^ PARAM) * 15.36]ms.
ED
AT Command Options
Table 3‐06.
XBee/XBee‐PRO Commands ‐ AT Command Options
AT
Command
Command
Category
Name and Description
Parameter Range
Default
CT
AT Command
Mode Options
Command Mode Timeout. Set/Read the period of inactivity (no valid commands
received) after which the RF module automatically exits AT Command Mode and
returns to Idle Mode.
2 - 0xFFFF [x 100 ms]
0x64 (100d)
GT
AT Command
Mode Options
Guard Times. Set required period of silence before and after the Command Sequence
Characters of the AT Command Mode Sequence (GT+ CC + GT). The period of silence 0x02 - 0xFFFF [x 1 ms]
is used to prevent inadvertent entrance into AT Command Mode.
0x3E8
(1000d)
CC
AT Command
Mode Options
Command Sequence Character. Set/Read the ASCII character value to be used
between Guard Times of the AT Command Mode Sequence (GT+CC+GT). The AT
Command Mode Sequence enters the RF Module into AT Command Mode.
0x2B
(‘+’ ASCII)
0 - 0xFF
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
27
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
3.3. Command Descriptions
Command descriptions in this section are listed alphabetically. Command categories are designated within "< >" symbols that follow each command title. XBee-PRO RF modules expect parameter values in hexadecimal (designated by the "0x" prefix).
A1 (End Device Association) Command
 The A1 command is
used to set and read End Device association
options.
Use the table below to determine End Device
behavior in relation to the A1 parameter.
Bit number
0 - ReassignPanID
1 - ReassignChannel
AT Command: ATA1
Parameter Range: 0 - 0x0F
Default Parameter Value: 0
End Device Association Option
0 - Will only associate with Coordinator operating on PAN ID that matches modem ID
1 - May associate with Coordinator operating on any PAN ID
0 - Will only associate with Coordinator operating on Channel that matches CH setting
1 - May associate with Coordinator operating on any Channel
0 - Device will not attempt Association
2 - AutoAssociate
3 - PollCoordOnPinWake
4-7
1 - Device attempts Association until success
Note: This bit is used only for Non-Beacon systems. End Devices in a Beaconing system must
always associate to a Coordinator
0 - Pin Wake will not poll the Coordinator for pending (indirect) Data
1 - Pin Wake will send Poll Request to Coordinator to extract any pending data
[reserved]
A2 (Coordinator Association) Command
 The A2 command is
used to set and read Coordinator association
options.
Use the table below to determine Coordinator
behavior in relation to the A2 parameter.
Bit number
0 - ReassignPanID
1 - ReassignChannel
AT Command: ATA2
Parameter Range: 0 - 0x07
Default Parameter Value: 0x06
End Device Association Option
0 - Coordinator will not perform Active Scan to locate available PAN ID. It will operate on ID
(PAN ID).
1 - Coordinator will perform Active Scan to determine an available ID (PAN ID). If a PAN ID
conflict is found, the ID parameter will change.
0 - Coordinator will not perform Energy Scan to determine free channel. It will operate on the
channel determined by the CH parameter.
1 - Coordinator will perform Energy Scan to find a free channel, then operate on that channel.
2 - AllowAssociate
3-7
0 - Coordinator will not allow any devices to associate to it.
1 - Coordinator will allow devices to associate to it.
[reserved]
The binary equivalent of the default value (0x06) is 00000110. ‘Bit 0’ is the last digit of the sequence.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
28
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
AI (Association Indication) Command
 The AI command is
used to indicate occurrences of errors during the
last association request.
AT Command: ATAI
Parameter Range: 0 - 0x13 [read-only]
Use the table below to determine meaning of the returned values.
Returned Value (Hex) Association Indication
0x00
Successful Completion - Coordinator successfully started or End Device association complete
0x01
Active Scan Timeout
0x02
Active Scan found no PANs
0x03
Active Scan found PAN, but the Coordinator Allow Association bit is not set
0x04
Active Scan found PAN, but Coordinator and End Device are not configured to support beacons
0x05
Active Scan found PAN, but the Coordinator ID (PAN ID) parameter does not match the ID parameter of
the End Device
0x06
Active Scan found PAN, but the Coordinator CH (Channel) parameter does not match the CH parameter
of the End Device
0x07
Energy Scan Timeout
0x08
Coordinator start request failed
0x09
Coordinator could not start due to Invalid Parameter
0x0A
Coordinator Realignment is in progress
0x0B
Association Request not sent
0x0C
Association Request timed out - no reply was received
0x0D
Association Request had an Invalid Parameter
0x0E
Association Request Channel Access Failure - Request was not transmitted - CCA failure
0x0F
Remote Coordinator did not send an ACK after Association Request was sent
0x10
Remote Coordinator did not reply to the Association Request, but an ACK was received after sending the
request
0x11
[reserved]
0x12
Sync-Loss - Lost synchronization with a Beaconing Coordinator
0x13
Disassociated - No longer associated to Coordinator
AP (API Enable) Command
 The AP command is used to
enable the RF module to operate using framebased API operation.
AT Command: ATAP
Parameter Range: 0 - 2
Parameter
Configuration
Disabled
(UART operation)
API enabled
(w/out escaped
characters)
API enabled
(with escaped
characters)
Default Parameter Value:0
Refer to the “API Operation” section [p43] when API operation is enabled (AP = 2 or 3).
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
29
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
AS (Active Scan) Command
 The AS command
AT Command: ATAS
is used to send a Beacon Request to a Broadcast
Address (0xFFFF) on every channel. The AS
parameter determines the amount of time the module will listen for Beacons on each channel. A
PanDescriptor is created and returned for every Beacon received from the scan. Each PanDescriptor contains the following information:
CoordAddress (SH + SL parameters)
CoordPanID (ID parameter)
CoordAddrMode 
0x02 = 16-bit Short Address
0x03 = 64-bit Long Address
Channel (CH parameter) 
SecurityUse
ACLEntry
SecurityFailure
SuperFrameSpec (2 bytes):
bit 15 - Association Permitted (MSB)
bit 14 - PAN Coordinator
bit 13 - Reserved
bit 12 - Battery Life Extension
bits 8-11 - Final CAP Slot
bits 4-7 - Superframe Order
bits 0-3 - Beacon Order
GtsPermit
RSSI (- RSSI is returned as -dBm)
TimeStamp (3 bytes)

The carriage return  is sent at the end of the AS command. The Active Scan is capable of
returning up to 5 PanDescriptors in a scan. The actual scan time on each channel is measured as
Time = [(2 ^ PARAM) * 15.36] ms. Note the total scan time is this time multiplied by the number
of channels to be scanned (16 for the XBee and 13 for the XBee-PRO). Refer to the SD command
description for more information.
BD (Interface Data Rate) Command
 The BD command is used to
set and read the serial interface data rate (baud
rate) used between the RF modem and host. This
parameter determines the rate at which serial
data is sent to the RF modem from the host. Modified interface data rates do not take effect until
the CN (Exit AT Command Mode) command is
issued and the system returns the 'OK' response.
When parameters 0-7 are sent to the RF modem,
the respective interface data rates are used (as
shown in the table on the right).
The RF data rate is not affected by the BD parameter. If the interface data rate is set higher than
the RF data rate, a flow control configuration may
need to be implemented.
AT Command: ATBD
Parameter Range: 0 - 7 (standard rates)
Parameter
Configuration (bps)
1200
2400
4800
9600
19200
38400
57600
115200
Default Parameter Value:3
Non-standard Interface Data Rates:
When parameter values outside the range of standard baud rates are sent, the closest interface
data rate represented by the number is stored in the BD register. For example, a rate of 19200
bps can be set by sending the following command line "ATBD4B00". NOTE: When using MaxStream’s X-CTU Software, non-standard interface data rates can only be set and read using the XCTU ‘Terminal’ tab. Non-standard rates are not accessible through the ‘Modem Configuration’ tab.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
30
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
When the BD command is sent with a non-standard interface data rate, the UART will adjust to
accommodate the requested interface rate. In most cases, the clock resolution will cause the
stored BD parameter to vary from the parameter that was sent (refer to the table below). Reading
the BD command (send "ATBD" command without an associated parameter value) will return the
value that was actually stored to the BD register.
Table 3‐07.
Parameters Sent Versus Parameters Stored
BD Parameter Sent (HEX)
Interface Data Rate (bps)
1200
BD Parameter Stored (HEX)
19,200
115,200
12C
300
12B
1C200
115,200
1B207
BE (Beacon Order) Command
 The BE command is used to set
and read the exponent used in the formula that
determines beacon order. The beacon order
specifies how often the coordinator transmits a
beacon.
AT Command: ATBE
Parameter Range: 0 - 0x0E [exponent]
Default Parameter Value: 2
The actual time is calculated from BE as:
Time (msec) = (2 ^ BE) * 15.36 ms.
Table 3‐08.
Beacon Interval Times
BE Parameter Value
10
12
14
Time
15.36 milliseconds
61.44 milliseconds
245.80 milliseconds
983.00 milliseconds
3.93 seconds
15.73 seconds
62.91 seconds
4.19 minutes
End devices automatically update their BE parameter values to match the coordinator upon association.
CA (CCA Threshold) Command
 The CA command is used to set
and read the CCA (Clear Channel Assessment)
threshold.
Prior to transmitting a packet, a CCA is performed
to detect energy on the transmit channel. If the
detected energy is above the CCA Threshold, the
radio will not transmit the packet.
AT Command: ATCA
Parameter Range: 0 - 0x50 [-dBm]
Default Parameter Value: 0x4B
(-75 dBm (decimal))
CC (Command Sequence Character) Command
 The CC command
is used to set and read the ASCII character used
between guard times of the AT Command Mode
Sequence (GT + CC + GT). This sequence enters
the RF module into AT Command Mode so that
data entering the modem from the host is recognized as commands instead of payload.
AT Command: ATCC
Parameter Range: 0 - 0xFF
Default Parameter Value: 0x2B (ASCII “+”)
Related Commands: GT (Guard Times)
Refer to the Command Mode section [p20] for more information regarding the AT Command Mode
Sequence.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
31
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
CE (Coordinator Enable) Command
 The CE command is used to
set and read the behavior (End Device vs. Coordinator) of the module.
AT Command: ATCE
Parameter Range: 0 - 1
Parameter
Configuration
End Device
Coordinator
Default Parameter Value:0
CH (Channel) Command
 The CH command is
used to set and read the channel on which RF
connections are made between RF modules. The
channel is one of three filtration layers available
to the RF module. The other layers are the PAN
ID (ID command) and destination addresses (DL
& DH commands).
AT Command: ATCH
Parameter Range: 0x0B - 0x1A (XBee)
0x0C - 0x18 (XBee-PRO)
Default Parameter Value: 0x0C (12 decimal)
Related Commands: ID (PAN ID), DL
(Destination Address Low, DH (Destination
Address High)
In order for RF modules to communicate with
each other, the RF modules must share the same channel number. Different channels can be used
to prevent RF modules in one network from listening to transmissions of another.
The RF module uses channel numbers of the 802.15.4 standard.
Center Frequency = 2.405 + (CH - 11d) * 5 MHz
(d = decimal)
Refer to the “Addressing” section [p16] for more information.
CN (Exit AT Command Mode) Command
 The CN command
is used to explicitly exit the RF module from AT
Command Mode.
AT Command: ATCN
CT (Command Mode Timeout) Command
 The CT command
is used to set and read the amount of inactive
time that elapses before the RF module automatically exits from AT Command Mode and returns
to Idle Mode.
Use the CN (Exit AT Command Mode) command
to exit AT Command Mode manually.
AT Command: ATCT
Parameter Range: 2 - 0xFFFF
[x 100 milliseconds]
Default Parameter Value: 0x64 (100 decimal,
which equals 10 decimal seconds)
Number of bytes returned: 2
Related Command: CN (Exit AT Command
Mode)
D5 (DIO5 Configuration) Command
 The D5 command is used to
configure options for the DIO5 line of the RF module. When the D5 parameter is set to “1”, the D5
line is used to indicate “Association (membership
with another RF module)” by causing the LED
indicator to blink.
AT Command: ATD5
Parameter Range: 0 - 1
Parameter
Configuration
Disabled
RSSI
Default Parameter Value:1
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
32
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
D6 (DIO6 Configuration) Command
 The D6 command is used to
set and read the behavior of the DIO6 line. This
line can be configured to enable RTS flow control.
AT Command: ATD6
Parameter Range: 0 - 1
Parameter
Configuration
Disabled
RTS Flow Control
Default Parameter Value:0
D7 (DIO7 Configuration) Command
 The D7 command is used to
set and read the behavior of the DIO7 line. CTS
flow control is enabled by default.
AT Command: ATD7
Parameter Range: 0 - 1
Parameter
Configuration
Disabled
CTS Flow Control
Default Parameter Value:1
DA (Force Disassociation) Command
<(Special)> The DA command is used to immediately disassociate an End Device from a Coordinator and reattempt to associate.
AT Command: ATDA
DB (Received Signal Strength) Command
 DB parameter is used to read the
AT Command: ATDB
received signal strength (in dBm) of the last RF
Parameter Range: 0 - 0x64 [read-only]
packet received. Reported values are accurate
between -40 dBm and the RF module's receiver sensitivity.
Absolute values are reported. For example: 0x58 = -88 dBm (decimal). If no packets have been
received (since last reset, power cycle or sleep event), “0” will be reported.
DH (Destination Address High) Command
 The DH command is
used to set and read the upper 32 bits of the RF
module's 64-bit destination address. When combined with the DL (Destination Address Low)
parameter, it defines the destination address
used for transmission.
AT Command: ATDH
Parameter Range: 0 - 0xFFFFFFFF
Default Parameter Value: 0
Related Commands: DL (Destination Address
Low), CH (Channel), ID (PAN VID), MY (Source
Address)
An RF module will only communicate with other
RF modules having the same channel (CH parameter), PAN ID (ID parameter) and destination address
(DH + DL parameters).
To transmit using a 16-bit address, set the DH parameter to zero and the DL parameter less than
0xFFFF. 0x000000000000FFFF (DL concatenated to DH) is the broadcast address for the PAN.
Refer to the “Addressing” section [p16] for more information.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
33
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
DL (Destination Address Low) Command
 The DL command is
used to set and read the lower 32 bits of the RF
module's 64-bit destination address. When combined with the DH (Destination Address High)
parameter, it defines the destination address
used for transmission.
AT Command: ATDL
Parameter Range: 0 - 0xFFFFFFFF
Default Parameter Value: 0
Related Commands: DH (Destination Address
High), CH (Channel), ID (PAN VID), MY (Source
Address)
An RF module will only communicate with other
RF modules having the same channel (CH parameter), PAN ID (ID parameter) and destination address (DH + DL parameters).
To transmit using a 16-bit address, set the DH parameter to zero and the DL parameter less than
0xFFFF. 0x000000000000FFFF (DL concatenated to DH) is the broadcast address for the PAN.
Refer to the “Addressing” section [p16] for more information.
DM (Destination Modem) Command
 The DM command
is used to resolve a MI (Modem Identifier) string
to a physical address. The following events occur
upon successful command execution:
AT Command: ATDM
Parameter Range: 20 Byte ASCII String
1. DL and DH are set to the address of the modem with the matching Modem Identifier.
2. ‘OK’ is returned.
If there is no response from a modem within 200 msec or a parameter is not specified (left blank),
the command is terminated and an ‘ERROR’ message is returned.
DP (Disassociation Cyclic Sleep Period) Command

NonBeacon Firmware
End Device - The DP command is used to set and
read the time period of sleep for cyclic sleeping
remotes that are configured for Association but
are not associated to a Coordinator. (i.e. If a
device is configured to associate, configured as a
Cyclic Sleep remote, but does not find a Coordinator, it will sleep for DP time before reattempting association.) Maximum sleep period is 268
seconds (0x68B0).
AT Command: ATDP
Parameter
Range:
Default
Parameter
Value:
NonBeacon Firmware:
1 - 0x68B0 [x 10 milliseconds]
Beacon-enabled Firmware:
1 - 0x68B0 [beacons]
NonBeacon Firmware: 0x3E8
(1000 decimal)
Beacon-enabled Firmware: 0x14
(20 decimal)
Related Commands: SM (Sleep Mode), SP
(Cyclic Sleep Period), ST (Time before Sleep)
DP should be > 0 for NonBeacon systems.
Beacon-enabled Firmware
End Device - The DP command is used to set and read the number of beacons the cyclic sleeping
remote will sleep through on a failed association attempt before reattempting association. (i.e. If a
device is configured for Association, configured as a Cyclic Sleep remote, and unable to find a
Coordinator; it will sleep for DP beacon times prior to reattempting association.)
SD is used to determine the beacon time since the device, in this mode, is not associated to a
Coordinator. This command may help reduce power consumption if a Coordinator is not found, or
if the Coordinator beacons are not detected for an extended period of time. Maximum sleep period
is 268 seconds. Therefore, DP must be selected such that the equation (2^SD * (0.01536 seconds) * DP) < 268 seconds.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
34
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
EA (ACK Failures) Command
 The EA command is used to reset
AT Command: ATEA
and read the count of ACK (acknowledgement)
Parameter Range: 0 - 0xFFFF
failures. This parameter value increments when
the module expires its transmission retries without receiving an ACK on a packet transmission. This count saturates at its maximum value.
Set the parameter to “0” to reset count.
EC (CCA Failures) Command
 The EC command is used to read
AT Command: ATEC
and reset the count of CCA (Clear Channel
Assessment) failures. This parameter value incre- Parameter Range: 0 - 0xFFFF
ments when the module does not transmit a
packet because it detected energy above the CCA threshold level (set with CA command). This
count saturates at its maximum value.
Set the EC parameter to “0” to reset count.
ED (Energy Scan) Command
 The ED command is
AT Command: ATED
used to send an “Energy Detect Scan”. This
Parameter Range: 0 - 7
parameter determines the length of scan on each
channel. The maximal energy on each channel is
returned and each value is followed by a carriage return. An additional carriage return is sent at
the end of the command.
The values returned represent the detected energy level in units of -dBm. The actual scan time on
each channel is measured as Time = [(2 ^ PARAM) * 15.36] ms.
Note the total scan time is this time multiplied by the number of channels to be scanned. Also refer to
the SD (Scan Duration) table.
EH (Echo) Command
 The EH command is used to send
AT Command: ATEH
command parameter as RF packet to remote
modem which 'echoes' back the data to the trans- Parameter Range: 1 - 20 bytes
mitting modem. This command uses the current
setting of DL and DH when transmitting the parameter.
The command ends by sending a  (Carriage Return).
FP (Force Poll) Command
<(Special)> The FP command is used to request
indirect messages being held by a coordinator.
AT Command: ATFP
FR (Software Reset) Command
 The FR command is used to force a
software reset on the module. The reset simulates powering off and then on again the module.
AT Command: ATFR
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
35
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
GT (Guard Times) Command
 GT Command is
used to set the DI (data in from host) time-ofsilence that surrounds the AT command sequence
character (CC Command) of the AT Command
Mode sequence (GT + CC + GT).
The DI time-of-silence is used to prevent inadvertent entrance into AT Command Mode.
AT Command: ATGT
Parameter Range: 2 - 0xFFFF
[x 1 millisecond]
Default Parameter Value: 0x3E8
(1000 decimal)
Related Command: CC (Command Sequence
Character)
Refer to the Command Mode section [p20] for
more information regarding the AT Command Mode Sequence.
HV (Hardware Version) Command
 The HV command is used to read
the hardware version of the module.
AT Command: ATHV
Parameter Range: 0 - 0xFFFF [Read-only]
ID (Pan ID) Command
 The ID command is
used to set and read the PAN (Personal Area Network) ID of the RF module. Only RF modules with
matching PAN IDs can communicate with each
other. RF modems with non-matching PAN IDs
will not receive unintended data transmission.
AT Command: ATID
Parameter Range: 0 - 0xFFFF
Default Parameter Value:0x3332
(13106 decimal)
Setting the ID parameter to 0xFFFF indicates a global message for all PANs.
Refer to the “Addressing” section [p16] for more information.
MD (Modem Discover) Command
 The MD command
is used to discover and report all modems found.
MD also accepts a Modem Identifier as a parameter. In this case, only a modem matching the supplied identifier will respond.
AT Command: ATMD
Parameter Range: optional - MI
The MD command causes a modem to transmit a globally addressed MD command packet. This
modem will allow responses within a 750 millisecond window. The 750 msec window is large
enough to receive all responses.
In AT Command mode, command completion is designated by a carriage return (0x0D). Since two
carriage returns end a command response, the application will receive three carriage returns at
the end of the command. If no responses are received, then only one carriage return should be
received by the application. When operating in API mode, a frame with no data and status set to
‘OK’ at the end of the command should be received. When the MD command packet is received,
the remote modem sets up a random time delay of up to 500 milliseconds before replying with a
MD response as follows:
Modem Discover Response (AT command mode format):
MY (Source Address) value
SH (Serial Number High) value
SL (Serial Number Low) value
MI (Modem Identifier) value
 <- This is part of the response and not the end of command indicator.
Modem Discover Response (API format - data is binary (except for MI)):
2 bytes for MY (Source Address) value
4 bytes for SH (Serial Number High) value
4 bytes for SL (Serial Number Low) value
NULL-terminated string for MI (Modem Identifier) value (max 20 bytes w/out NULL terminator)
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
36
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
MI (Modem Identifier) Command
 The MI command
is used to set and read a string that identifies a
particular module.
AT Command: ATMI
Parameter Range: 20 Byte ASCII string
Rules:
• The register only accepts printable ASCII data.
• A string can not start with a space.
• A carriage return ends command
• Command will automatically end when maximum bytes for the string have been entered.
This string is returned as part of the MD (Modem Discover) command. This identifier is also used
with the DM (Destination Modem) command.
MY (16-bit Source Address) Command
 The MY command is
used to set and read the 16-bit source address of
the RF module.
By setting MY to 0xFFFF, the reception of RF
packets having a 16-bit address is disabled. The
64-bit address is the module serial number and is
always enabled.
AT Command: ATMY
Parameter Range: 0 - 0xFFFF
Default Parameter Value: 0
Related Commands: DH (Destination Address
High), DL (Destination Address Low), CH
(Channel), ID (PAN ID)
Refer to the “Addressing” section [p16] for more information.
PE (Pull-up Resistor Enable) Command
 The PE command is used to
set/read the bitfield to configure internal pull-up
resistor status for I/O lines. “1” specifies the pullup resistor is enabled. “0” specifies no pull-up.
bit
bit
bit
bit
bit
bit
bit
bit
AD4/DIO4/RF_TX
COORD
AD2/DIO2
AD1/DIO1
AD0/DIO0
RTS
SLEEP_RQ
DIN/CONFIG
AT Command: ATPE
Parameter Range: 0 - 0xFF
Default Parameter Value: 0xFF (all pull -up
resistors are enabled)
For example: Sending the command “ATPE 6F” will turn bits 0, 1, 2, 3, 5 and 6 ON; and bits 4 & 7
will be turned OFF. (The binary equivalent of “0x6F” is “01101111”. Note that ‘bit 0’ is the last
digit in the bitfield.
P0 (PWM0 Configuration) Command
 The P0 command is used to select
and read the function for PWM0 (Pulse Width
Modulation output 0 - pin 6).
Note: The second character in the command is a
zero (“0”), not the letter “O”.
AT Command: ATP0
Parameter Range: 0 - 1
Parameter
Configuration
Disabled
RSSI PWM0 enabled
Default Parameter Value: 1
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
37
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
PL (Power Level) Command
 The PL command is used to
select and read the power level at which the RF
module transmits conducted power.
AT Command: ATPL
Parameter Range: 0 - 4
Parameter
XBee
XBee-Pro
-10 dBm
10 dBm
-6 dBm
12 dBm
-4 dBm
14 dBm
-2 dBm
16 dBm
0 dBm
18 dBm
Default Parameter Value: 4
RE (Restore Defaults) Command
<(Special)> The RE command is used to restore
AT Command: ATRE
all configurable parameters to their factory
default settings. The RE command does not write
restored values to non-volatile (persistent) memory. Issue the WR (Write) command subsequent
to issuing the RE command to save restored parameter values to non-volatile memory.
RN (Random Delay Slots) Command
 The RN command is
used to set and read the minimum value of the
back-off exponent in the CSMA-CA algorithm. The
CSMA-CA algorithm was engineered for collision
avoidance (random delays are inserted to prevent
data loss caused by data collisions).
AT Command: ATRN
Parameter Range: 0 - 3 [exponent]
Default Parameter Value: 0
If RN = 0, collision avoidance is disabled during the first iteration of the algorithm (802.15.4 macMinBE).
CSMA-CA stands for "Carrier Sense Multiple Access - Collision Avoidance". Unlike CSMA-CD (reacts
to network transmissions after collisions have been detected), CSMA-CA acts to prevent data collisions before they occur. As soon as a modem receives a packet that is to be transmitted, it checks
if the channel is clear (no other modem is transmitting). If the channel is clear, the packet is sent
over-the-air. If the channel is not clear, the RF module waits for a randomly selected period of
time, then checks again to see if the channel is clear. After a time, the process ends and the data
is lost.
RO (Packetization Timeout) Command
 RO command is used to set
and read the number of character times of intercharacter delay required before transmission.
AT Command: ATRO
Parameter Range: 0 - 0xFF
[x character times]
RF transmission commences when data is
Default Parameter Value: 3
detected in the DI (data in from host) buffer and
RO character times of silence are detected on the
UART receive lines (after receiving at least 1 byte).
RF transmission will also commence after 100 bytes (maximum packet size) are received in the DI
buffer.
Set the RO parameter to '0' to transmit characters as they arrive instead of buffering them into
one RF packet.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
38
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
RP (RSSI PWM Timer) Command
 The RP command is used to
AT Command: ATRP
enable PWM (Pulse Width Modulation) output on
Parameter Range: 0 - 0xFF
the RF module. The output is calibrated to show
[x 100 milliseconds]
the level a received RF signal is above the sensiDefault
Parameter
Value: 0x28 (40 decimal)
tivity level of the RF module. The PWM pulses
vary from zero to 95 percent. Zero to twenty-nine
percent means the received RF signal is at or below the published sensitivity level of the RF module. The following table shows levels above sensitivity and PWM values.
The total period of the PWM output is 8.32 ms. Because there are 40 steps in the PWM output, the
minimum step size is 0.208 ms.
Table 3‐09.
PWM Percentages
dB above Sensitivity
PWM percentage*
(high period / total period)
10
46.0%
20
63.0%
30
80.1%
* PWM% = (295 + (17.5 * dBm above sensitivity)) / 10.24
A non-zero value defines the time that the PWM output will be active with the RSSI value of the
last received RF packet. After the set time when no RF packets are received, the PWM output will
be set low (0 percent PWM) until another RF packet is received. The PWM output will also be set
low at power-up until the first RF packet is received. A parameter value of 0xFF permanently
enables the PWM output and it will always reflect the value of the last received RF packet.
SA (Resynch Attempts) Command
 The SA command is used to set and read
the number of times an End Device will attempt
to reacquire a lost beacon before disassociating
from a Beaconing Coordinator.
AT Command: ATSA
Parameter Range: 0 - 0x0F [# of attempts]
Default Parameter Value: 0
SC (Scan Channel) Command
 The SC command is used to set
and read the list of channels to scan for all Active
and Energy Scans as a bit field.
This affects scans initiated in command mode [AS
(Active Scan) and ED (Energy Scan) commands]
and during End Device Association and Coordinator startup:
bit
bit
bit
bit
bit
bit
bit
bit
0x0B
0x0C
0x0D
0x0E
0x0F
0x10
0x11
0x12
bit
bit
bit
bit
bit
bit
bit
bit
AT Command: ATSC
Parameter Range: 0 - 0xFFFF [Bit Field]
Default Parameter Value: 0x3FFE (all XBeePRO channels)
8 - 0x13
9 - 0x14
10 - 0x15
11 - 0x16
12 - 0x17
13 - 0x18
14 - 0x19
15 - 0x1A
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
39
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
SD (Scan Duration) Command
 The SD command is
used to set and read the exponent value that
determines the duration (in time) of a scan.
AT Command: ATSD
Parameter Range: 0 - 0x0F
Default Parameter Value: 4
End Device - Duration of Active Scan during
Association. On beacon system, set SD = BE of
coordinator. SD must be set at least to the highest BE parameter of any Beaconing Coordinator
with which an End Device or Coordinator wish to discover.
Coordinator - If the ‘ReassignPANID’ option is set on the Coordinator [refer to A2 parameter],
the SD parameter determines the length of time the Coordinator will scan channels to locate existing PANs. If the ‘ReassignChannel’ option is set, SD determines how long the Coordinator will perform an Energy Scan to determine which channel it will operate on.
Scan Time is measured as (# of Channels to Scan] * (2 ^ SD) * 15.36ms). The number of channels to scan is set by the SC command. The XBee module can scan up to 16 channels (SC =
0xFFFF). The XBee PRO module can scan up to 13 channels (SC = 0x3FFE).
Examples: The values below show results for a 13 channel scan:
If SD
SD =
SD =
SD =
= 0, time
2, time =
4, time =
6, time =
= 0.246 sec
0.983 sec
3.93 sec
15.73 sec
SD
SD
SD
SD
8, time = 62.91 sec
10, time = 4.19 min
12, time = 16.77 min
14, time = 67.07 min
SF (Superframe Order) Command
 The SF command is used to set and read
Parameter Range: 0 - 0x0E [exponent]
the exponent used in calculating superframe
Default Parameter Value: 2
order. The superframe order specifies the length
of the active portion of the superframe (including
the beacon frame). The SF parameter should be set less than or equal to the BE parameter or
upon exiting command mode; SF will be set to equal BE.
The actual Active Period time (msec) is calculated from SF as: Time = (2 ^ SF) * 15.36 ms.
SH (Serial Number High) Command
 The SH command is used to read
the high 32 bits of the RF module's unique IEEE
64-bit address.
The RF module serial number is set at the factory
and is read-only.
AT Command: ATSH
Parameter Range: 0 - 0xFFFFFFFF [read-only]
Related Commands: SL (Serial Number Low),
MY (Source Address)
SL (Serial Number Low) Command
 The SL command is used to read
the low 32 bits of the RF module's unique IEEE
64-bit address.
The RF module serial number is set at the factory
and is read-only.
AT Command: ATSL
Parameter Range: 0 - 0xFFFFFFFF [read-only]
Related Commands: SH (Serial Number High),
MY (Source Address)
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
40
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
SM (Sleep Mode) Command
 The SM command is
used to set and read Sleep Mode settings. By
default, Sleep Modes are disabled (SM = 0) and
the RF module remains in Idle/Receive Mode.
When in this state, the RF module is constantly
ready to respond to either serial or RF activity.
AT Command: ATSM
Parameter Range: 0 - 5
Parameter
Configuration
Disabled
1*
Pin Hibernate
SM command options vary according to the networking system type. By default, the module is
configured to operate in a NonBeacon system.
* Parameter options (1, 2, 3 & 5) are not supported when
operating using Beacon‐enabled firmware.
2*
Pin Doze
3*
(reserved)
Cyclic Sleep Remote
5*
Cyclic Sleep Remote
(with Pin Wake-up)
Default Parameter Value: 0
Related Commands: SP (Cyclic Sleep Period),
ST (Time before Sleep)
SP (Cyclic Sleep Period) Command
 The SP command is
used to set and read the duration of time in which
a remote RF module sleeps. After the cyclic sleep
period is over, the RF module wakes and checks
for data. If data is not present, the RF module
goes back to sleep. The maximum sleep period is
268 seconds (SP = 0x68B0).
The SP parameter is only valid if the RF module is
configured to operate in Cyclic Sleep (SM = 4-6).
Coordinator and End Device SP values should
always be equal.
To send Direct Messages, set SP = 0.
AT Command: ATSP
Parameter
Range:
Default
Parameter
Value:
NonBeacon Firmware:
1 - 0x68B0 [x 10 milliseconds]
Beacon-enabled Firmware:
1 - 0x68B0 [beacons]
NonBeacon Firmware: 0
Beacon-enabled Firmware: 0x0A
(10 decimal)
Related Commands: SM (Sleep Mode), ST
(Time before Sleep), DP (Disassociation Cyclic
Sleep Period, BE (Beacon Order)
NonBeacon Firmware
End Device - SP determines the sleep period for cyclic sleeping remotes. Maximum sleep period is
268 seconds (0x68B0).
Coordinator - If non-zero, SP determines the time to hold an indirect message before discarding it.
A Coordinator will discard indirect messages after a period of (2.5 * SP).
Beacon-enabled Firmware
End Device - SP determines the number of beacons a cyclic sleeping remote will sleep through.
Because the maximum sleep period is 268 (decimal) seconds, SP must be selected such that the
equation (2^BE * (0.01536 seconds) * SP) < 268 seconds.
Coordinator - SP determines the number of beacons to retain an indirect message before discarding it. A Coordinator will discard indirect messages after 2 * SP beacons.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
41
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
ST (Time before Sleep) Command
 The ST command is
used to set and read the period of inactivity (no
serial or RF data is sent or received) before activating Sleep Mode.
NonBeacon Firmware
Set/Read time period of inactivity (no serial or RF
data is sent or received) before activating Sleep
Mode. ST parameter is only valid with Cyclic
Sleep settings (SM = 4 - 5).
Coordinator and End Device ST values must be
equal.
AT Command: ATST
Parameter
Range:
Default
Parameter
Value:
NonBeacon Firmware:
1 - 0xFFFF [x 1 millisecond]
Beacon-enabled Firmware:
1 - 0xFFFF [beacons]
NonBeacon Firmware: 0x1388
(5000 decimal)
Beacon-enabled Firmware: 0
Related Commands: SM (Sleep Mode), ST
(Time before Sleep)
Beacon-enabled Firmware
Set/Read the number of beacons received with no activity (no serial or RF data is sent or received)
before activating Sleep Mode. ST parameter is only valid with the Cyclic Sleep setting (SM = 4).
The ST parameter is not used by a Beacon-enabled Coordinator.
VL (Verbose Version)
 The VL command is used to read
detailed version information about the module.
The information includes: application build date;
MAC, PHY and bootloader versions; and build
dates.
AT Command: ATVL
Parameter Range: 0 - 0xFF
[x 100 milliseconds]
Default Parameter Value: 0x28 (40 decimal)
VR (Firmware Version) Command
 The VR command is used to read
which firmware version is stored in the RF module.
AT Command: ATVR
Parameter Range: 0 - 0xFFFF [read only]
XBee version numbers will have four significant digits. The reported number will show three or
four numbers and is stated in hexadecimal notation. A version can be reported as "ABC" or
"ABCD". Digits ABC are the main release number and D is the revision number from the main
release. "D" is not required and if it is not present, a zero is assumed for D. "B" is a variant designator. The following variants exist:
• "0" - Non-Beacon Enabled 802.15.4 Code
• "1" - Beacon Enabled 802.15.4 Code
WR (Write) Command
<(Special)> The WR command is used to write
AT Command: ATWR
configurable parameters to the RF module's nonvolatile memory (Parameter values remain in RF
module's memory until overwritten by subsequent use of the WR Command).
If changes are made without writing them to non-volatile memory, the RF module reverts back to
previously saved parameters the next time the RF module is powered-on.
NOTE: Once the WR command is sent to the RF module, no additional characters should be sent until
after the “OK/r” response is received.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
42
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
3.4. API Operation
By default, XBee/XBee-PRO RF Modules act as a serial line replacement (Transparent Operation) all UART data received through the DI pin is queued up for RF transmission. When the module
receives an RF packet, the data is sent out the DO pin with no additional information.
Inherent to Transparent Operation are the following behaviors:
• If module parameter registers are to be set or queried, a special operation is required for
transitioning the module into Command Mode [refer to p20].
• In point-to-multipoint systems, the application must send extra information so that the
receiving module(s) can distinguish between data coming from different remotes.
As an alternative to the default 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.
3.4.1. API Frame Specifications
Two API modes are supported and both can be enabled using the AP (API Enable) command. Use
the following AP parameter values to configure the module to operate in a particular mode:
• AP = 0 (default): Transparent Operation (UART Serial line replacement)
API modes are disabled.
• AP = 1: API Operation
• AP = 2: API Operation (with escaped characters)
API Operation (AP parameter = 1)
When this API mode is enabled (AP = 1), the UART data frame structure is defined as follows:
Figure 3‐01. UART Data Frame Structure:
Start Delimiter
(Byte 1)
0x7E
Length
(Bytes 2-3)
MSB
LSB
Frame Data
(Bytes 4-n)
Checksum
(Byte n + 1)
API-specific Structure
1 Byte
MSB = Most Significant Byte, LSB = Least Significant Byte
Any data received prior to the start delimiter is silently discarded. If the frame is not received correctly or if the checksum fails, the module will reply with a module status frame indicating the
nature of the failure.
API Operation - with Escape Characters (AP parameter = 2)
When this API mode is enabled (AP = 2), the UART data frame structure is defined as follows:
Figure 3‐02. UART Data Frame Structure ‐ with escape control characters:
Start Delimiter
(Byte 1)
0x7E
Length
(Bytes 2-3)
MSB
LSB
Frame Data
(Bytes 4-n)
Checksum
(Byte n + 1)
API-specific Structure
1 Byte
Characters Escaped If Needed
MSB = Most Significant Byte, LSB = Least Significant Byte
Escape characters. When sending or receiving a UART data frame, specific data values must be
escaped (flagged) so they do not interfere with the UART or UART data frame operation. To escape
an interfering data byte, insert 0x7D and follow it with the byte to be escaped XOR’d with 0x20.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
43
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Data bytes that need to be escaped:
• 0x7E – Frame Delimiter
• 0x7D – Escape
• 0x11 – XON
• 0x13 – XOFF
Example - Raw UART Data Frame (before escaping interfering bytes):
0x7E 0x00 0x02 0x23 0x11 0xCB
0x11 needs to be escaped which results in the following frame:
0x7E 0x00 0x02 0x23 0x7D 0x31 0xCB
Note: In the above example, the length of the raw data (excluding the checksum) is 0x0002 and
the checksum of the non-escaped data (excluding frame delimiter and length) is calculated as:
0xFF - (0x23 + 0x11) = (0xFF - 0x34) = 0xCB.
Checksum
To test data integrity, a checksum is calculated and verified on non-escaped data.
To calculate: Not including frame delimiters and length, add all bytes keeping only the lowest 8
bits of the result and subtract from 0xFF.
To verify: Add all bytes (include checksum, but not the delimiter and length). If the checksum is
correct, the sum will equal 0xFF.
3.4.2. API Types
Frame data of the UART data frame forms an API-specific structure as follows:
Figure 3‐03. UART Data Frame & API‐specific Structure:
Start Delimiter
(Byte 1)
Length
(Bytes 2-3)
0x7E
MSB
LSB
Frame Data
(Bytes 4- n)
Checksum
(Byte n + 1)
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
cmdID
cmdData
The cmdID frame (API-identifier) indicates which API messages will be contained in the cmdData
frame (Identifier-specific data). Refer to the sections that follow for more information regarding
the supported API types. Note that multi-byte values are sent big endian.
Modem Status
API Identifier: 0x8A
RF Module status messages are sent from the module in response to specific conditions.
Figure 3‐04. Modem Status Frames
Start Delimiter
0x7E
Length
MSB
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x8A
cmdData
Status (Byte 5)
0 = Hardware reset
1 = Watchdog timer reset
2 = Associated
3 = Disassociated
4 = Synchronization Lost
(Beacon-enabled only)
5 = Coordinator realignment
6 = Coordinator reset
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
44
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
AT Command
API Identifier Value: 0x08
Allows for module parameter registers to be queried or set.
Figure 3‐05. AT Command Frames
Start Delimiter
0x7E
Length
MSB
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x08
cmdData
Frame ID (Byte 5)
AT Command (Bytes 6-7)
Identifies the UART data frame for the host to
correlate with a subsequent ACK (acknowledgement).
If set to ‘0’, no response is requested.
Parameter Value (Byte(s) 8-n)
Command Name - Two
ASCII characters that
identify the AT Command.
If present, indicates the requested parameter
value to set the given register.
If no characters present, register is queried.
Figure 3‐06. Example: API frames when reading the DL parameter value of the module.
Byte 1
0x7E
Start Delimiter
Bytes 2-3
0x00
Byte 4
Byte 5
Bytes 6-7
Byte 8
0x08
R (0x52)
D (0x44) L (0x4C)
0x15
API Identifier
Frame ID**
AT Command
Checksum
0x04
Length*
* Length [Bytes] = API Identifier + Frame ID + AT Command
** “R” value was arbitrarily selected.
Figure 3‐07. Example: API frames when modifying the DL parameter value of the module.
Byte 1
0x7E
Start Delimiter
Bytes 2-3
0x00
Byte 4
Byte 5
Bytes 6-7
Bytes 8-11
Byte 12
0x08
M (0x4D)
D (0x44) L (0x4C)
0x00000FFF
0x0C
API Identifier
Frame ID**
AT Command
Parameter Value
Checksum
0x08
Length*
* Length [Bytes] = API Identifier + Frame ID + AT Command + Parameter Value
** “M” value was arbitrarily selected.
AT Command Response
API Identifier Value: 0x88
Response to previous command.
In response to an AT Command message, the module will send an AT Command Response message. Some commands will send back multiple frames (for example, the MD (Modem Discover)
and AS (Active Scan) commands). These commands will end by sending a frame with a status of
ATCMD_OK and no cmdData.
Figure 3‐08. AT Command Response Frames.
Start Delimiter
0x7E
Length
MSB
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x88
cmdData
Frame ID (Byte 5 )
Identifies the UART data frame being reported.
Note: If Frame ID = 0 in AT Command Mode,
no AT Command Response will be given.
AT Command (Bytes 6-7)
Command Name - Two
ASCII characters that
identify the AT Command.
Status (Byte 8)
0 = OK
1 = ERROR
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
Value (Byte(s) 9-n)
The HEX (non-ASCII) value
of the requested register
45
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
TX (Transmit) Request: 64-bit address
API Identifier Value: 0x00
A TX Request message will cause the module to send RF Data as an RF Packet.
Figure 3‐09. TX Packet (64‐bit address) Frames
Start Delimiter
0x7E
Length
MSB
LSB
Frame ID (Byte 5)
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x00
cmdData
Destination Address (Bytes 6-13)
Identifies the UART data frame for the host to
correlate with a subsequent ACK (acknowledgement).
Setting Frame ID to ‘0' will disable response frame.
MSB first, LSB last.
Broadcast =
0x000000000000FFFF
Options (Byte 14)
RF Data (Byte(s) 15-n)
bits 0-7 [reserved at this time] - Set to 0x00
Up to 100 Bytes per packet
TX (Transmit) Request: 16-bit address
API Identifier Value: 0x01
A TX Request message will cause the module to send RF Data as an RF Packet.
Figure 3‐10. TX Packet (16‐bit address) Frames
Start Delimiter
0x7E
Length
MSB
Frame ID (Byte 5)
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x01
cmdData
Destination Address (Bytes 6-7)
Identifies the UART data frame for the host to
correlate with a subsequent ACK (acknowledgement).
Setting Frame ID to ‘0' will disable response frame.
MSB first, LSB last.
Broadcast = 0xFFFF
Options (Byte 8)
RF Data (Byte(s) 9-n)
bits 0-7 [reserved at this time] - Set to 0x00
Up to 100 Bytes per packet
TX (Transmit) Status
API Identifier Value: 0x89
When a TX Request is completed, the module sends a TX Status message. This message will indicate if the packet was transmitted successfully or if there was a failure.
Figure 3‐11. TX Status Frames
Start Delimiter
0x7E
Length
MSB
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x89
cmdData
Frame ID (Byte 5)
Identifies UART data frame being reported.
Note: If Frame ID = 0 in the TX Request, no
AT Command Response will be given.
Status (Byte 6)
0 = Success
1 = No ACK (Acknowledgement) received
2 = CCA failure
3 = Purged
NOTES:
• “STATUS = 1” occurs when all retries are expired and no ACK is received.
• If transmitter broadcasts (destination address = 0x000000000000FFFF), only
“STATUS = 0 or 2” will be returned.
• “STATUS = 3” occurs when Coordinator times out of an indirect transmission.
Timeout is defined as (2.5 x SP (Cyclic Sleep Period) parameter value).
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
46
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
RX (Receive) Packet: 64-bit address
API Identifier Value: 0x80
When the module receives an RF packet, it is sent out the UART using this message type.
Figure 3‐12. RX Packet (64‐bit address) Frames
Start Delimiter
0x7E
Length
MSB
LSB
Checksum
1 Byte
API Identifier
Identifier-specific Data
0x80
cmdData
Source Address (Bytes 5-12)
MSB (most significant byte) first,
LSB (least significant) last
Frame Data
API-specific Structure
RSSI (Byte 13)
Options (Byte 14)
Received Signal Strength Indicator Hexadecimal equivalent of (-dBm) value.
(For example: If RX signal strength = -40
dBm, “0x28” (40 decimal) is returned)
bit 0 [reserved]
bit 1 = Address broadcast
bit 2 = PAN broadcast
bits 3-7 [reserved]
RF Data (Byte(s) 15-n)
Up to 100 Bytes per packet
RX (Receive) Packet: 16-bit address
API Identifier Value: 0x81
When the module receives an RF packet, it is sent out the UART using this message type.
Figure 3‐13. RX Packet (16‐bit address) Frames
Start Delimiter
0x7E
Source Address (Bytes 5-6)
MSB (most significant byte) first,
LSB (least significant) last
Length
MSB
LSB
Frame Data
Checksum
API-specific Structure
1 Byte
API Identifier
Identifier-specific Data
0x81
cmdData
RSSI (Byte 7)
Received Signal Strength Indicator Hexadecimal equivalent of (-dBm) value.
(For example: If RX signal strength = -40
dBm, “0x28” (40 decimal) is returned)
Options (Byte 8)
bit 0 [reserved]
bit 1 = Address broadcast
bit 2 = PAN broadcast
bits 3-7 [reserved]
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
RF Data (Byte(s) 9-n)
Up to 100 Bytes per packet
47
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Appendix A: Agency Certifications
FCC Certification
The XBee/XBee-PRO RF Module complies with Part 15 of the FCC rules and regulations. Compliance with the labeling requirements, FCC notices and antenna usage guidelines is required.
To fulfill FCC Certification requirements, the OEM must comply with the following regulations:
1.
The system integrator must ensure that the text on the external label provided with this
device is placed on the outside of the final product [Figure A-01].
2.
The XBee/XBee-PRO RF Module may be used only with approved antennas that have been
tested with this modem.
OEM Labeling Requirements
WARNING: The Original Equipment Manufacturer (OEM) must ensure that FCC labeling
requirements are met. This includes a clearly visible label on the outside of the final
product enclosure that displays the contents shown in the figure below.
Figure A‐01. Required FCC Label for OEM products containing the XBee/XBee‐PRO RF Module
Contains FCC ID: OUR-XBEE / OUR-XBEEPRO*
The enclosed device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference and (2) this device must accept any interference received, including interference that may cause undesired operation.
* The FCC ID for the XBee is “OUR‐XBEE”. The FCC ID for the XBee‐PRO is “OUR‐XBEEPRO”.
FCC Notices
IMPORTANT: The XBee/XBee-PRO OEM RF Module has been certified by the FCC for use with
other products without any further certification (as per FCC section 2.1091). Modifications not
expressly approved by MaxStream could void the user's authority to operate the equipment.
IMPORTANT: OEMs must test final product to comply with unintentional radiators (FCC section
15.107 & 15.109) before declaring compliance of their final product to Part 15 of the FCC Rules.
IMPORTANT: The RF module has been certified for remote and base radio applications. If the
module will be used for portable applications, the device must undergo SAR testing.
This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses and can
radiate radio frequency energy and, if not installed and used in accordance with the instructions,
may cause harmful interference to radio communications. However, there is no guarantee that
interference will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: Re-orient or relocate the receiving antenna,
Increase the separation between the equipment and receiver, Connect equipment and receiver to
outlets on different circuits, or Consult the dealer or an experienced radio/TV technician for help.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
48
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
FCC-Approved Antennas (2.4 GHz)
The XBee/XBee-Pro OEM RF Module can be installed utilizing antennas and cables constructed with
standard connectors (Type-N, SMA, TNC, etc.) if the installation is performed professionally and
according to FCC guidelines. For installations not performed by a professional, non-standard connectors (RPSMA, RPTNC, etc.) must be used.
The modules are pre-FCC approved for fixed base station and mobile applications on channels
0x0B - 0x18. As long as the antenna is mounted at least 20cm (8 in.) from nearby persons, the
application is considered a mobile application. Antennas not listed in the table must be tested to
comply with FCC Section 15.203 (unique antenna connectors) and Section 15.247 (emissions).
Table A‐01. Antennas approved for use with the XBee/XBee‐PRO OEM RF Modules (Channels 0x0B ‐ 0x18)
Part Number
A24-HSM-450
A24-HABSM
A24-C1
A24-Y4NF
A24-Y6NF
A24-Y7NF
A24-Y9NF
A24-Y10NF
A24-Y12NF
A24-Y13NF
A24-Y15NF
A24-Y16NF
A24-Y16RM
A24-Y18NF
A24-F2NF
A24-F3NF
A24-F5NF
A24-F8NF
A24-F9NF
A24-F10NF
A24-F12NF
A24-F15NF
A24-W7NF
A24-M7NF
A24-P8SF
A24-P8NF
A24-P13NF
A24-P14NF
A24-P15NF
A24-P16NF
A24-P19NF
Type (Description)
Dipole (Half-wave articulated RPSMA - 4.5”)
Dipole (Articulated RPSMA)
Surface Mount
Yagi (4-element)
Yagi (6-element)
Yagi (7-element)
Yagi (9-element)
Yagi (10-element)
Yagi (12-element)
Yagi (13-element)
Yagi (15-element)
Yagi (16-element)
Yagi (16-element, RPSMA connector)
Yagi (18-element)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Fiberglass base station)
Omni-directional (Base station)
Omni-directional (Mag-mount base station)
Flat Panel
Flat Panel
Flat Panel
Flat Panel
Flat Panel
Flat Panel
Flat Panel
Gain
2.1 dBi
2.1 dBi
-1.5 dBi
6.0 dBi
8.8 dBi
9.0 dBi
10.0 dBi
11.0 dBi
12.0 dBi
12.0 dBi
12.5 dBi
13.5 dBi
13.5 dBi
15.0 dBi
2.1 dBi
3.0 dBi
5.0 dBi
8.0 dBi
9.5 dBi
10.0 dBi
12.0 dBi
15.0 dBi
7.2 dBi
7.2 dBi
8.5 dBi
8.5 dBi
13.0 dBi
14.0 dBi
15.0 dBi
16.0 dBi
19.0 dBi
Application*
Fixed/Mobile
Fixed/Mobile
Fixed/Mobile
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed/Mobile
Fixed/Mobile
Fixed/Mobile
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Min. Separation
20 cm
20 cm
20 cm
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
20 cm
20 cm
20 cm
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
2m
Required Cable Loss**
4.2 dB
4.2 dB
8.1 dB
10.9 dB
11.1 dB
12.1 dB
13.1 dB
14.1 dB
14.1 dB
14.6 dB
15.6 dB
15.6 dB
17.1 dB
4.2 dB
5.1 dB
7.1 dB
10.1 dB
11.6 dB
12.1 dB
14.1 dB
17.1 dB
9.3 dB
9.3 dB
8.6 dB
8.6 dB
13.1 dB
14.1 dB
15.1 dB
16.1 dB
19.1 dB
Table A‐02. Antennas approved for use with the XBee/XBee‐PRO OEM RF Modules (Channels 0x0B ‐ 0x17)
Part Number
A24-HSM-450
A24-HABSM
A24-HABUF-P5I
A24-QI
Type (Description)
Dipole (Half-wave articulated RPSMA - 4.5”)
Dipole (Articulated RPSMA)
Dipole (Half-wave articulated bulkhead mount U.FL. w/ 5” pigtail)
Monopole (Integrated whip - XBee 0x0B-0x18, XBee-PRO 0x0B-0x17)
Gain
2.1 dBi
2.1 dBi
2.1 dBi
1.5 dBi
Application*
Fixed/Mobile
Fixed
Fixed
Fixed
Min. Separation
20 cm
20 cm
20 cm
20 cm
* If using the module in a portable application (For example ‐ If the module is used in a handheld device and the antenna is less
than 20cm from the human body when the device is operation): The integrator is responsible for passing additional SAR (Specific
Absorption Rate) testing based on FCC rules 2.1091 and FCC Guidelines for Human Exposure to Radio Frequency Electromagnetic
Fields, OET Bulletin and Supplement C. The testing results will be submitted to the FCC for approval prior to selling the integrated
unit. The required SAR testing measures emissions from the module and how they affect the person.
** Required cable loss only applies to the higher power output “XBee‐PRO” modules and not to the “XBee” modules.
RF Exposure
WARNING: To satisfy FCC RF exposure requirements for mobile transmitting devices, a separation distance of
20 cm or more should be maintained between the antenna of this device and persons during device operation.
To ensure compliance, operations at closer than this distance is not recommended. The antenna used for this
transmitter must not be co-located in conjunction with any other antenna or transmitter.
The preceding statement must be included as a CAUTION statement in manuals for OEM products to alert users on
FCC RF Exposure compliance.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
49
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
European Certification
The XBee/XBee-PRO RF Module has been certified for use in several European countries. For a
complete list, refer to www.maxstream.net.
If the XBee/XBee-PRO RF Modules are incorporated into a product, the manufacturer must ensure
compliance of the final product to the European harmonized EMC and low-voltage/safety standards. A Declaration of Conformity must be issued for each of these standards and kept on file as
described in Annex II of the R&TTE Directive. Furthermore, the manufacturer must maintain a
copy of the XBee/XBee-PRO user manual documentation and ensure the final product does not
exceed the specified power ratings, antenna specifications, and/or installation requirements as
specified in the user manual. If any of these specifications are exceeded in the final product, a
submission must be made to a notified body for compliance testing to all required standards.
OEM Labeling Requirements
The 'CE' marking must be affixed to a visible location on the OEM product.
Figure A‐02. CE Labeling Requirements
The CE mark shall consist of the initials "CE" taking the following form:
• If the CE marking is reduced or enlarged, the proportions given in the above graduated drawing must be respected.
• The CE marking must have a height of at least 5mm except where this is not possible on
account of the nature of the apparatus.
• The CE marking must be affixed visibly, legibly, and indelibly.
Restrictions
France - France imposes restrictions on the 2.4 GHz band. Go to www.art-telecom.Fr or contact
MaxStream for more information.
Norway - Norway prohibits operation near Ny-Alesund in Svalbard. More information can be found
at the Norway Posts and Telecommunications site (www.npt.no).
Declarations of Conformity
MaxStream has issued Declarations of Conformity for the XBee/XBee-PRO RF Modules concerning
emissions, EMC and safety. Files are located in the 'documentation' folder of the MaxStream CD.
Important Note
MaxStream does not list the entire set of standards that must be met for each country. MaxStream
customers assume full responsibility for learning and meeting the required guidelines for each
country in their distribution market. For more information relating to European compliance of an
OEM product incorporating the XBee/XBee-PRO RF Module, contact MaxStream, or refer to the following web sites:
CEPT ERC 70-03E - Technical Requirements, European restrictions and general requirements:
Available at www.ero.dk/.
R&TTE Directive - Equipment requirements, placement on market: Available at www.ero.dk/.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
50
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Appendix B: Development Guide
Development Kit Contents
The XBee Development Kit includes the hardware and software needed to rapidly create long
range wireless links between devices.
Table B‐01. Items Included in the Development Kit
Item
Qty. Description
Part #
XBee-PRO Module
(1) OEM RF Module w/ U.FL antenna connector
(1) OEM RF Module w/ attached wire antenna
XBP24-...UI-...
XBP24-...WI-...
XBee Module
(1) OEM RF Module w/ U.FL antenna connector
(1) OEM RF Module w/ attached wire antenna
(1) OEM RF Module w/ chip antenna
XB24-...UI-...
XB24-...WI-...
XB24-...CI-...
RS-232 Interface Board
Board for interfacing between modules and RS-232 devices
(Converts signal levels, displays diagnostic info, & more)
XBIB-R
USB Interface Board
Board for interfacing between modules & USB devices
(Converts signal levels, displays diagnostic info, & more)
XBIB-U
RS-232 Cable
(6’, straight-through)
Cable for connecting RS-232 interface board with DTE devices
(devices that have a male serial DB-9 port - such as most PCs)
JD2D3-CDS-6F
USB Cable (6’)
Cable for connecting USB interface board to USB devices
JU1U2-CSB-6F
Serial Loopback
Adapter
[Red] Adapter for configuring the module assembly (module + RS-232
interface board) to function as a repeater for range testing
JD2D3-CDL-A
NULL Modem Adapter
(male-to-male)
[Black] Adapter for connecting the module assembly (module + RS-232
interface board) to other DCE (female DB-9) devices
JD2D2-CDN-A
NULL Modem Adapter
(female-to-female)
[Gray] Adapter for connecting serial devices. It allows users to bypass
the radios to verify serial cabling is functioning properly.
JD3D3-CDN-A
9VDC Power Adapter
Adapter for powering the RS-232 interface board
JP5P2-9V11-6F
9V Battery Clip
Clip for remotely powering the RS-232 board w/ a 9V battery
JP2P3-C2C-4I
RPSMA Antenna
RPSMA half-wave dipole antenna (2.4 GHz, 2.1 dB)
A24-HASM-525
RF Cable Assembly
Adapter for connecting RPSMA antenna to U.FL connector
JF1R6-CR3-4I
CD
Documentation and Software
MD0010
Step-by-step instruction on how to create wireless links
& test range capabilities of the modules
MD0026
Quick Start Guide
Interfacing Options
The development kit includes an RS-232 and a USB interface board. Both boards provide a direct
connection to many serial devices and therefore provide access to the RF module registries.
Parameters stored in the registry allow OEMs and integrators to customize the modules to suite
the needs of their data radio systems.
The following sections illustrate how to use the interface boards for development purposes. The
MaxStream Interface board provides means for connecting the module to any node that has an
available RS-232 or USB connector. Since the module requires signals to enter at TTL voltages,
one of the main functions of the interface board is to convert signals between TTL levels and RS232 and USB levels.
Note: In the following sections, an OEM RF Module mounted to an interface board will be referred to as
a "Module Assembly".
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
51
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
RS-232 Interface Board
Physical Interface
B-01a. Reset Switch
The Reset Switch is used to reset (re-boot) the RF module. This
switch only applies when using the configuration tabs of MaxStream’s
X-CTU Software.
Figure B‐01. Front View
B-01b. I/O & Power LEDs
LEDs indicate RF module activity as follows:
B-01c. Serial Port
B-01d. RSSI LEDs
Yellow (top LED) = Serial Data Out (to host)
Green (middle) = Serial Data In (from host)
Red (bottom)
= Power/TX Indicator (LED is on when module
assembly is powered)
B-01b. I/O & Power LEDs
B-01e. Power Connector
B-01a. Reset Switch
B-01c. Serial Port
Standard female DB-9 (RS-232) connector.
B-01d. 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.
LEDs ON
LEDs ON
LED ON
LED ON
Very Strong Signal (> 30 dB fade margin)
Strong Signal (> 20 dB fade margin)
Moderate Signal (> 10 dB fade margin)
Weak Signal (< 10 dB fade margin)
B-01e. Power Connector
5-14 VDC power connector
B-02a. DIP Switch
DIP Switch functions are not supported in this release. Future downloadable firmware versions will support DIP Switch configurations.
Figure B‐02. Back View
B-02b. 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.
B-02b. Antenna Port
B-02a. DIP Switch
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
52
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
RS-232 Pin Signals
Figure B‐03. Pins used on the female RS‐232 (DB‐9) Serial Connector
Table B‐02. Pin Assignments and Implementations
DB-9 Pin
RS-232 Name
Description
Implementation*
DCD
Data-Carrier-Detect
Connected to DSR (pin6)
RXD
Receive Data
Serial data exiting the module assembly
(to host)
TXD
Transmit Data
Serial data entering into the module assembly
(from host)
DTR
Data-Terminal-Ready
Can enable Power-Down on the module assembly
GND
Ground Signal
Ground
DSR
Data-Set-Ready
Connected to DCD (pin1)
RTS / CMD
Request-to-Send /
Command Mode
Provides RTS flow control or
enables Command Mode
CTS
Clear-to-Send
Provides CTS flow control
RI
Ring Indicator
Optional power input that is connected internally to
the positive lead of the front power connector
* Functions listed in the implementation column may not be available at the time of release.
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
53
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Wiring Diagrams
Figure B‐04. DTE Device (RS‐232, male DB‐9 connector) wired to a DCE Module Assembly (female DB‐9)
Figure B‐05. DCE Module Assembly (female DB‐9 connector) wired to a DCE Device (RS‐232, male DB‐9)
Sample Wireless Connection: DTE <--> DCE <--> DCE <--> DCE
Figure B‐06. Typical wireless link between DTE and DCE devices
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
54
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Adapters
The development kit includes several adapters that support the following functions:
• Performing Range Tests
• Testing Cables
• Connecting to other RS-232 DCE and DTE devices
• Connecting to terminal blocks or RJ-45 (for RS-485/422 devices)
NULL Modem Adapter (male-to-male)
Part Number: JD2D2-CDN-A (Black, DB-9 M-M) The male-to-male NULL modem adapter is
used to connect two DCE devices. A DCE device connects with a straight-through cable to the male
serial port of a computer (DTE).
Figure B‐07. Male NULL modem adapter and pinouts
Figure B‐08. Example of a MaxStream Radio Modem (DCE Device) connecting to another DCE device)
NULL Modem Adapter (female-to-female)
Part Number: JD3D3-CDN-A (Gray, DB-9 F-F) The female-to-female NULL modem adapter is
used to verify serial cabling is functioning properly. To test cables, insert the female-to-female
NULL modem adapter in place of a pair of module assemblies (RS-232 interface board + XTend
Module) and test the connection without radio modules in the connection.
Figure B‐09. Female NULL modem adapter and pinouts
Serial Loopback Adapter
Part Number: JD2D3-CDL-A (Red, DB-9 M-F) The serial loopback adapter is used for range
testing. During a range test, the serial loopback adapter configures the module to function as a
repeater by looping serial data back into the radio for retransmission.
Figure B‐10. Serial loopback adapter and pinouts
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
55
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
USB Interface Board
Physical Interface
B-11a. I/O & Power LEDs
LEDs indicate RF module activity as follows:
Figure B‐11. Front View
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 module is powered)
B-11c. USB Port
B-11b. RSSI LEDs
B-11b. RSSI LEDs
B-11a. I/O & Power 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 module's receiver sensitivity.
LEDs ON
LEDs ON
LED ON
LED ON
Very Strong Signal (> 30 dB fade margin)
Strong Signal (> 20 dB fade margin)
Moderate Signal (> 10 dB fade margin)
Weak Signal (< 10 dB fade margin)
B-11c. USB Port
Standard Type-B OEM connector is used to communicate with OEM
host and power the RF module.
B-12a. DIP Switch
DIP Switch functions are not supported in this release. Future downloadable firmware versions will support the DIP Switch configurations.
Figure B‐12. Back View
B-12b Reset Switch
The Reset Switch is used to reset (re-boot) the RF module.
B-12c. 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.
B-12b. Reset Switch
B-12c. Antenna Port
B-12a. DIP Switch
USB Pin Signals
Table B‐03. USB signals and their implantations on the XBee/XBee‐PRO RF Module
Pin
Name
Description
Implementation
VBUS
Power
Power the RF module
D-
Transmitted & Received Data
Transmit data to and from the RF module
D+
Transmitted & Received Data
Transmit data to and from the RF module
GND
Ground Signal
Ground
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
56
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Appendix C: Additional Information
1-Year Warranty
XBee/XBee-PRO RF Modules from MaxStream, Inc. (the "Product") are warranted against defects
in materials and workmanship under normal use, for a period of 1-year from the date of purchase.
In the event of a product failure due to materials or workmanship, MaxStream will repair or
replace the defective product. For warranty service, return the defective product to MaxStream,
shipping prepaid, for prompt repair or replacement.
The foregoing sets forth the full extent of MaxStream's warranties regarding the Product. Repair or
replacement at MaxStream's option is the exclusive remedy. THIS WARRANTY IS GIVEN IN LIEU
OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, AND MAXSTREAM SPECIFICALLY DISCLAIMS
ALL WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MAXSTREAM, ITS SUPPLIERS OR LICENSORS BE LIABLE FOR DAMAGES IN EXCESS
OF THE PURCHASE PRICE OF THE PRODUCT, FOR ANY LOSS OF USE, LOSS OF TIME, INCONVENIENCE, COMMERCIAL LOSS, LOST PROFITS OR SAVINGS, OR OTHER INCIDENTAL, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT, TO
THE FULL EXTENT SUCH MAY BE DISCLAIMED BY LAW. SOME STATES DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES. THEREFORE, THE
FOREGOING EXCLUSIONS MAY NOT APPLY IN ALL CASES. This warranty provides specific legal
rights. Other rights which vary from state to state may also apply.
Ordering Information
Figure C‐01. Divisions of the XBee/XBee‐PRO RF Module Part Numbers
For example:
XBP24-AWI-001 = XBee-PRO OEM RF Module, 2.4 GHz, attached wire antenna, Industrial temperature rating, IEEE 802.15.4 standard
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
57
XBee™/XBee‐PRO OEM RF Modules – Product Manual v1.x7C BETA [2005.12.02]
Contact MaxStream
Free and unlimited technical support is included with every MaxStream Radio Modem sold. For the
best in wireless data solutions and support, please use the following resources:
Documentation:
www.maxstream.net/helpdesk/download.php
Technical Support:
Phone.
(866) 765-9885 toll-free U.S.A. & Canada
(801) 765-9885 Worldwide
Live Chat.
www.maxstream.net
E-Mail.
rf-xperts@maxstream.net
MaxStream office hours are 8:00 am - 5:00 pm [U.S. Mountain Standard Time]
© 2005 MaxStream, Inc., Confidential & Proprietary ‐ All Rights Reserved
58

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Tagged PDF                      : Yes
Page Mode                       : UseOutlines
XMP Toolkit                     : 3.1-702
About                           : uuid:3f6abf59-fe42-4a0e-8082-93198e075840
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Creator Tool                    : FrameMaker 7.1
Modify Date                     : 2005:12:02 10:02:13-07:00
Create Date                     : 2005:12:02 09:39:11Z
Metadata Date                   : 2005:12:02 10:02:13-07:00
Document ID                     : uuid:4e7f8dca-5991-4dfc-8852-fbb4a76f95d0
Instance ID                     : uuid:8bc9583e-005b-4183-ab83-c9e2ead9a2ac
Format                          : application/pdf
Title                           : product-manual_XBee.XBee-PRO_OEM_RF-Modules_v1.07c.book
Creator                         : roberte
Page Count                      : 58
Author                          : roberte

EXIF Metadata provided by EXIF.tools