XBee/XBee-PRO S2C 802.15.
Revision history—90001500 Revision Date Description A March 2016 Initial release of the document B April 2016 Updated the antenna tables. Added the Listen Before Talk requirement to the European certifications. Updated the maximum throughput specification. Trademarks and copyright Digi, Digi International, and the Digi logo are trademarks or registered trademarks in the United States and other countries worldwide.
Contents XBee/XBee-PRO S2C 802.15.
Over-the-air (OTA) firmware update Addressing Send packets to a specific device Addressing modes Encryption Maximum Payload Maximum payload rules Maximum payload summary tables Work with Legacy devices Networking MAC Mode configuration XBee retries configuration Transmit status based on MAC mode and XBee retries configurations Peer-to-peer networks Master/Slave networks Clear Channel Assessment (CCA) CCA operations Serial interface Serial port selection UART data flow Flow control SPI operation SPI signals
AT commands Special commands WR (Write) RE (Restore Defaults) FR (Software Reset) Networking and security commands C8 (802.15.
D3 (DIO3/AD3) D4 (DIO4 ) D5 (DIO5/ASSOCIATED_INDICATOR) D8 (DIO8/SLEEP_REQUEST) P0 (RSSI/PWM0 Configuration) P1 (PWM1 Configuration) P2 (SPI_MISO) M0 (PWM0 Duty Cycle) M1 (PWM1 Duty Cycle) P5 (SPI_MISO) P6 (SPI_MOSI) P7 (SPI_SSEL ) P8 (SPI_SCLK) P9 (SPI_ATTN ) PR (Pull-up/Down Resistor Enable) PD (Pull up/down direction) IU (I/O Output Enable) IU (Send I/O Sample to Serial Port) IT (Samples before TX) IS (Force Sample) IO (Digital Output Level) IC (DIO Change Detect) IR (Sample Rate) RP (RSSI PWM Timer) I/O
API frames Modem Status frame - 0x8A AT Command frame - 0x08 AT Command - Queue Parameter Value frame - 0x09 AT Command Response frame - 0x88 Remote AT Command Request frame - 0x17 Remote Command Response frame - 0x97 TX Request: 64-bit address frame - 0x00 TX Request: 16-bit address - 0x01 TX Status frame - 0x89 RX Packet: 64-bit Address frame - 0x80 Receive Packet: 16-bit address frame - 0x81 RX (Receive) Packet: 64-bit address IO - 0x82 RX Packet: 16-bit address IO - 0x83 102 103 104 106 107 109 110 111
XBee/XBee-PRO S2C 802.15.4 RF Module User Guide XBee/XBee-PRO S2C 802.15.4 RF Modules are embedded solutions providing wireless end-point connectivity to devices. These devices use the IEEE 802.15.4 networking protocol for fast point-tomultipoint or peer-to-peer networking. They are designed for high-throughput applications requiring low latency and predictable communication timing. There are two footprints for the XBee/XBee-PRO S2C 802.15.4 RF Module hardware: through-hole (TH) and surface-mount (SMT).
Technical specifications Performance specifications Power requirements General specifications Regulatory approvals Serial communication specifications GPIO specifications XBee/XBee-PRO S2C 802.15.
Technical specifications Performance specifications Performance specifications The following table provides the performance specifications for the device. Specification XBee value XBee-PRO value Indoor / urban range Up to 200 ft (60 m) Up to 300 ft. (90 m) Outdoor RF line-of-sight range Up to 4000 ft (1200 m) Up to 2 miles (3200 m) Transmit power output (software selectable) 6.3 mW (8 dBm), Boost mode1 63 mW (18 dBm)2 3.1 mW (5 dBm), Normal mode Channel 26 max power is 0.
Technical specifications Regulatory approvals Specification XBee XBee-PRO Operating frequency ISM 2.4 GHz Supported channels 11 - 26 12 - 23 Form factor TH: 2.438 x 2.761 cm (0.960 x 1.087 in) SMT: 2.199 x 3.4 x 0.305 cm (0.866 x 1.33 x 0.120 in) TH: 2.438 x 3.294 cm (0.960 x 1.297 in) SMT: 2.199 x 3.4 x 0.305 cm (0.866 x 1.33 x 0.120 in) Operating temperature -40 to 85º C (industrial) Antenna options TH: PCB antenna, U.
Technical specifications GPIO specifications Specifications Module Pin Number UART Pins XBee (Surface Mount) XBee (Through-hole) DOUT 3 2 DIN / CONFIG 4 3 CTS / DIO7 25 12 RTS / DIO6 29 16 SPI The SC2 (Serial Communication Port 2) of the Ember 357 is connected to the SPI port. Specifications Module Pin Number SPI Pins XBee (Surface Mount) XBee (Through-hole) SPI_SCLK 14 18 SPI_SSEL 15 17 SPI_MOSI 16 11 SPI_MISO 17 4 GPIO specifications XBee/XBee-PRO S2C 802.15.
Technical specifications GPIO specifications GPIO Electrical Specification Value Output source/sink current for pin numbers 2, 3, 4, 9, 12, 13, 15, 16, 17, and 19 on the TH modules 4 mA Output source/sink current for pad numbers 7, 8, 24, 31, and 33 on the SMT modules 8 mA Output source/sink current for pin numbers 6, 7, 11, 18, and 20 on the TH modules 8 mA Total output current (for GPIO pads) 40 mA XBee/XBee-PRO S2C 802.15.
Hardware Antenna options Mechanical drawings Mounting considerations Pin signals Design notes XBee/XBee-PRO S2C 802.15.
Hardware Antenna options Antenna options The ranges specified are typical when using the integrated whip (1.5 dBi) and dipole (2.1 dBi) antennas. The printed circuit board (PCB) antenna option provides advantages in its form factor, however, it typically yields shorter range than the whip and dipole antenna options when transmitting outdoors. For more information, refer to the XBee and XBee-PRO OEM RF Module Antenna Considerations Application Note (http://ftp1.digi.
Hardware Mounting considerations The following drawings show the XBee-PRO through-hole device. Mounting considerations We design the through-hole module to mount into a receptacle so that you do not have to solder the module when you mount it to a board. The development kits may contain RS-232 and USB interface boards that use two 20-pin receptacles to receive modules. The following illustration shows the module mounting into the receptacle on the RS-232 interface board. XBee/XBee-PRO S2C 802.15.
Hardware Pin signals Century Interconnect and Samtec manufacture the 2 x 10 pin 2 mm spacing receptacles on Digi development boards.
Hardware Pin signals Pin Name Direction Function 4 SPI_MISO Output Serial Peripheral Interface (SPI) Data Out 5 RESET Input Module reset (reset pulse must be at least 200 ns). This must be driven as an open drain/collector. The device drives this line low when a reset occurs. Never drive this line high.
Hardware Pin signals Pin Name Direction Function 5 [Reserved] Output Do not connect 6 RESET Input Module reset (reset pulse must be at least 200 ns). This must be driven as an open drain/collector. The device drives this line low when a reset occurs. Never drive this line high.
Hardware Design notes Pin Name Direction Function 30 DIO3/AD3 Both Digital IO 3 / Analog input 3 31 DIO2/AD2 Both Digital IO 2 / Analog input 2 32 DIO1/AD1 Both Digital IO 1 / Analog input 1 33 DIO0/AD0 Both Digital IO 0 / Analog input 0 34 [Reserved] - Do not connect 35 GND - Ground 36 RF Both RF connection 37 [Reserved] - Do not connect Notes Minimum connections: VCC, GND, DOUT and DIN. Minimum connections for updating firmware: VCC, GND, DIN, DOUT, RTS and DTR.
Hardware Design notes Position the antennas away from metal objects whenever possible. Metal objects between the transmitter and receiver can block the radiation path or reduce the transmission distance. Objects that are often overlooked include: n metal poles n metal studs n structure beams n concrete, which is usually reinforced with metal rods If you place the device inside a metal enclosure, use an external antenna.
Hardware Design notes Through-hole keepout XBee/XBee-PRO S2C 802.15.
Hardware Design notes Surface-mount keepout RF pad version The RF Pad is a soldered antenna connection on the surface-mount device. The RF signal travels from pin 36 on the module to the antenna through a single ended RF transmission line on the PCB. This line should have a controlled impedance of 50 Ω. For the transmission line, we recommend either a microstrip or coplanar waveguide trace on the PCB.
Hardware Design notes n The top two layers of the PCB have a controlled thickness dielectric material in between. The second layer has a ground plane which runs underneath the entire RF Pad area. This ground plane is a distance d, the thickness of the dielectric, below the top layer. n The top layer has an RF trace running from pin 36 of the module to the RF pin of the RPSMA connector. The RF trace's width determines the impedance of the transmission line with relation to the ground plane.
Hardware Design notes Number Description 1 XBee surface-mount pin 36 2 50 Ω microstrip trace 3 Back off ground fill at least twice the distance between layers 1 and 2 4 RF connector 5 Stitch vias near the edges of the ground plane 6 Pour a solid ground plane under the RF trace on the reference layer Implementing these design suggestion will help ensure that the RF Pad module performs to specifications. XBee/XBee-PRO S2C 802.15.
Modes Serial modes Transceiver modes XBee/XBee-PRO S2C 802.15.
Modes Serial modes Serial modes The firmware operates in several different modes. Two top-level modes establish how the device communicates with other devices through its serial interface: Transparent operating mode and API operating mode. The following modes describe how the serial port sends and receives data. Transparent operating mode Devices operate in this mode by default. We also call this mode “AT mode.” The device acts as a serial line replacement when it is in Transparent operating mode.
Modes Serial modes controlling multiple devices remotely. API mode is a frame-based protocol that allows you to direct data on a packet basis. It can be particularly useful in large networks where you need control over the operation of the radio network or when you need to know which node a data packet is from. The device communicates UART or SPI data in packets, also known as API frames. This mode allows for structured communications with serial devices.
Modes Transceiver modes The preceding example would change the device's destination address (Low) to 0x1F. Respond to AT commands When you send a command to the device, the device parses and runs the command. If the command runs successfully, the device returns an OK message. If the command errors, the device returns an ERROR message. When reading parameters, the device returns the current parameter value instead of an OK message.
Operation Configure the device using XCTU Over-the-air (OTA) firmware update Addressing Encryption Maximum Payload Networking Clear Channel Assessment (CCA) Serial interface SPI operation I/O support Sleep support Node discovery About remote configuration commands XBee/XBee-PRO S2C 802.15.
Operation Configure the device using XCTU Configure the device using XCTU XBee Configuration and Test Utility (XCTU) is a multi-platform program that enables developers to interact with Digi radio frequency (RF) devices through a graphical interface. The application includes built-in tools that make it easy to set up, configure, and test Digi RF devices. For full support of the XBee/XBee-PRO S2C 802.15.4 RF Module, you must use XCTU version 6.3.0 or higher.
Operation Encryption Broadcast PAN ID The Broadcast PAN ID is also 0xFFFF. Its effect is to traverse all PANs in the vicinity. Typically, this only makes sense during association time when sending beacon requests to find PAN IDs. Short and long addresses A short address is 16 bits and a long address is 64 bits. The short address is set with the MY parameter.
Operation Maximum Payload Factor Effect on Maximum Payload Packet overhead Reduce by 5 This penalty for enabling encryption is unavoidable due to the 802.15.4 protocol. Source address Reduce by 6 This penalty is unavoidable because the 802.15.4 requires encrypted packets to be sent with a long source address, even if a short address would otherwise be used. Destination address Reduce by 6 This penalty only applies if sending to a long address rather than a short address.
Operation Maximum Payload 3. If you are using the application header, the maximum achievable payload is reduced by: n 2 bytes if not using encryption. n 4 bytes if using encryption. 4. If you are using the long source address, the maximum achievable payload is reduced by 6 bytes (size of long address (8) - size of short address (2) = 6). 5. If you are using encryption, the short source addresses are promoted to long source addresses, so the maximum achievable payload is reduced by 6 bytes. 6.
Operation Networking The new XBee/XBee-PRO S2C 802.15.4 RF Modules enhance transmission by implementing a transmission queue that allows the device to transmit to several devices at the same time. Broadcast transmissions are performed in parallel with the unicast transmissions. This enhancement in the XBee/XBee-PRO S2C 802.15.4 RF Module can produce problematic behavior under certain conditions if the receiver is a Legacy 802.15.4 module (S1 hardware).
Operation Networking 2. Enables or disables MAC acknowledgment request for unicast packets. When MAC ACK is enabled (MM = 0 or 2), transmitting devices send packets with an ACK request so receiving devices send an ACK back (acknowledgment of RF packet reception) to the transmitter. If the transmitting device does not receive the ACK, it re-sends the packet up to three times or until the ACK is received. Modes 1 and 3 disable MAC acknowledgment.
Operation Networking Destination reachable Destination unreachable Retries CCA failure happened Retries TX MAC App status Retries Mac ACK Config TX status Enabled 00 up (Success) to 3 0 01 (No 3 acknowledgment received) 0 02 3 (CCA failure) 0 Disabled 00 0 (Success) 0 00 (Success) 0 02 3 (CCA failure) 0 MAC App TX status 0 MAC App The following table applies when: l Digi Header is enabled and XBee Retries (RR parameter) is bigger than 0.
Operation Networking Master/Slave networks In a Master Slave network, there is a coordinator and one or more end devices. When end devices associate to the coordinator, they become members of that Personal Area Network (PAN). As such, they share the same channel and PAN ID. PAN IDs must be unique to prevent miscommunication between PANs. Depending on the A1 and A2 parameters, association may assist in automatically assigning the PAN ID and the channel.
Operation Networking Bit Hex value Meaning 0 0x01 Allow PAN ID reassignment 1 0x02 Allow channel reassignment 2 0x04 Allow association By default, A2 is 0, which prevents devices from associating to the coordinator. So, if CE is 1 and A2 bit 2 is 0, the device still creates a network, but end devices are unable to associate to it. If A2 bit 2 is set, then joining is allowed after the coordinator forms a network. If A2 bit 0 is set, the coordinator issues an active scan.
Operation Networking should be set to match the SP and ST values of the end nodes. The coordinator will hold onto an indirect message until it receives a poll from the device to which the message is addressed, or until a timeout, whichever occurs first. The timeout is 2.5 times the value of SP. After an indirect message is sent, subsequent messages to the same address will be sent directly for a period of time equal to the ST parameter.
Operation Networking Code Meaning 0x04 Active Scan found a PAN coordinator in a beacon-enabled network, which is not a supported feature. 0x05 Active Scan found a PAN, but the PAN ID does not match the configured PAN ID on the requesting end device and bit 0 of A1 is not set to allow reassignment of PAN ID. 0x06 Active Scan found a PAN on a channel does not match the configured channel on the requesting end device and bit 1 of A1 is not set to allow reassignment of the channel.
Operation Clear Channel Assessment (CCA) Clear Channel Assessment (CCA) 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, a delay is inserted before a transmission takes place.
Operation Serial interface Serial port selection The device has two serial ports and only one is active at a time. To be active, a port must be enabled and in use. The UART is always enabled. The SPI is enabled if it is configured. To be configured, SPI_MISO, SPI_ MOSI, SPI_SSEL , and SPI_CLK must all be configured as peripherals. On the surface-mount device, these lines are configured as peripherals by setting P5, P6, P7, and P8 to 1. This is also the default configuration for surface-mount devices.
Operation Serial interface Flow control The XBee/XBee-PRO S2C 802.15.4 RF Module maintains buffers to collect serial and RF data that it receives. The serial receive buffer collects incoming serial characters and holds them until the device can process them. The serial transmit buffer collects the data it receives via the RF link until it transmits that data out the serial port. The following figure shows the process of device buffers collecting received serial data.
Operation SPI operation the serial transmit buffer does not have enough space for all of the data bytes, it discards the entire RF data packet. If the device sends data out the UART when RTS is de-asserted (set high) the device could send up to five characters out the UART port after RTS is de-asserted. Cases in which the DO buffer may become full, resulting in dropped RF packets: 1.
Operation SPI operation SPI_MISO: When SPI_CLK is active, the device outputs the data on SPI_MISO at the SPI_CLK rate. If there are other SPI slave devices connected to the same SPI master, then the SPI_MISO output from XBee device must be externally tri-stated when SPI_SSEL is de-asserted to prevent multiple devices from driving SPI_MISO. SPI_MOSI: The SPI master outputs data on this line at the SPI_CLK rate after it selects the desired slave.
Operation I/O support Slave mode characteristics In slave mode, the following apply: n SPI Clock rates up to 5 MHz (5 Mb/s) are possible. n Data is MSB first. n It uses Frame Format Mode 0. This means CPOL= 0 (idle clock is low) and CPHA = 0 (data is sampled on the clock’s leading edge). The picture below diagrams Mode 0. n The SPI port is setup for API mode and is equivalent to AP = 1. The following picture show the frame format for SPI communications.
Operation I/O support Digital I/O line support Digital I/O is available on pins D0 through D8. Each of these pins may be configured as 3, 4, or 5 with the following meanings: n 3 is digital input n 4 is digital output low n 5 is digital output high Pins D0 through D8 are available for digital input, but only D0 through D7 are available for digital output.
Operation I/O support where: 83 Indicates RX Packet: 16-bit Address IO frame (0x83). 00 00 Indicates 16-bit source address. 00 Indicates RSSI (does not apply). 00 Indicates options. 01 Indicates the number of samples. 03 3E Mask to indicate which lines are sampled (A0, D8, D5, D4, D3, D2, and D1). 01 2A Digital sample that indicates that D8 is high, D5 is high, D4 is low, D3 is high, D2 is low, and D1 is high.
Operation I/O support Multiple samples per packet The IT parameter specifies how many I/O samples can be transmitted in a single OTA packet. Any single-byte value (0 - 0xFF) is accepted for input. However, the value is adjusted downward based on how many I/O samples can fit into a maximum size packet; see Maximum Payload on page 33. A query of the IT parameter after changes are applied tells how many I/O samples actually occur.
Operation I/O support Although samples may be taken every millisecond, IR*IT should be at least 20 milliseconds. This allows time for OTA transmission and output on the serial port of the receiving module. Destination node On the destination node, the IU parameter enables the serial port to output I/O samples it receives. IU is set to 1 by default. If IU is set and the destination node is not in Command mode, it displays samples it receives on its serial port in API format.
Operation I/O support neither based on the settings of the IA (I/O Input Address) and IU (I/O Output Enable) parameters. For more information, see SO (Sleep Options) on page 77, IA (I/O Input Address) on page 91, and IU (I/O Output Enable) on page 89. Sample rate (interval) The Sample Rate (Interval) feature allows enabled ADC and DIO pins to be read periodically on devices that are not configured to operate in Sleep Mode.
Operation Sleep support a matching value for output. For example, if an ADC0 sample is received, then P0 must be configured with 2 for PWM output. Otherwise, the analog signal will not be reflected with a matching PWM signal. Likewise, if the sample indicates that D2 is high, but D2 is not set to 4 or 5 on the receiving device, then the D2 pin will not be affected by I/O line passing.
Operation Sleep support Pin Sleep mode (SM = 1) Pin Sleep mode minimizes quiescent power (power consumed when in a state of rest or inactivity). This mode is voltage level-activated; when Sleep_RQ (pin 9 for through-hole, pin 10 for surface-mount) is asserted, the device finishes any transmit, receive or association activities, enters Idle mode, and then enters a state of sleep. The device does not respond to either serial or RF activity while in pin sleep.
Operation Sleep support Sleep mode SM command setting Sleep current Pin sleep 1 <1 µA @ 25ºC Cyclic sleep 4 <1 µA @ 25ºC Cyclic sleep with pin wake-up 5 <1 µA @ 25ºC Low sleep current is achieved by driving PWM outputs high during sleep and by using internal pullups/pull-downs on disabled/unused pins. The sleep pins are set up for sleeping as specified in Sleep pins on page 55. Additionally, pins that are outputs (other than PWM outputs) continue to output the same levels during sleep.
Operation Node discovery 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 uses direct transmission for all subsequent data transmissions to that device address until ST time occurs with no activity (at which point it reverts to using indirect transmissions for that device address).
Operation About remote configuration commands Node discovery in compatibility mode Node discovery (without an NI string parameter) in compatibility mode operates the same in compatibility mode as it does outside of compatibility mode with one minor exception: If C8 bit 1 is set and if requesting node is operating in API mode and if no responses are received by the time NT times out, then an API AT command response of OK (API frame type 0x88) is sent out the serial port rather than giving no response at al
Operation About remote configuration commands CAUTION! It is important to set the short address to 0xFFFE when sending to a long address. Any other value causes the long address to be ignored. This is particularly problematic in the case where nodes are set up with default addresses of 0 and the 16bit address is erroneously left at 0.
AT commands Special commands Networking and security commands RF interfacing commands Sleep commands Serial interfacing commands I/O settings commands I/O line passing Diagnostic commands Command mode options XBee/XBee-PRO S2C 802.15.
AT commands Special commands Special commands The following AT commands are special commands. WR (Write) Writes parameter values to non-volatile memory so that parameter modifications persist through subsequent resets. Writing parameters to non-volatile memory does not apply the changes immediately. However, since non-volatile memory is used to determine initial configuration following reset, the written parameters are applied following a reset.
AT commands Bit Meaning 01 Networking and security commands Setting Description TX 0 compatibility Transmissions are optimized as follows: 1. Maximum transmission size is affected by multiple factors (MM, MY, DH, DL, and EE). See Maximum payload rules on page 33. In the best case, with no app header, short source and destination addresses, and no encryption, the maximum transmission size is 116 bytes. 2.
AT commands Networking and security commands Default 0 CH (Operating Channel) Set or read the operating channel devices used to transmit and receive data. The channel is one of three addressing configurations available to the device. The other configurations are the PAN ID (ID command) and destination addresses (DL and DH commands). In order for devices to communicate with each other, they must share the same channel number.
AT commands Networking and security commands Default 0 DL (Destination Address Low) Set or read the upper 32 bits of the 64-bit destination address. When you combine DH with DL, it defines the destination address that the device uses for transmissions in Transparent mode. The destination address is also used for I/O sampling in both Transparent and API modes. 0x000000000000FFFF is the broadcast address. It is also used as the polling address when the device functions as end device.
AT commands Networking and security commands Default Set in the factory MM (MAC Mode) The MM command is used to set and read the MAC Mode value. The MM command disables/enables the use of a Digi header contained in the 802.15.4 RF packet. By default (MM = 0), Digi Mode is enabled and the module adds an extra header to the data portion of the 802.15.4 packet.
AT commands Networking and security commands Parameter range 0-6 Default 0 0x10 RN (Random Delay Slots) Sets or reads the minimum value of the back-off exponent in the CSMA-CA algorithm. The Carrier Sense Multiple Access - Collision Avoidance (CSMA-CA) algorithm was engineered for collision avoidance (random delays are inserted to prevent data loss caused by data collisions). If RN = 0, there is no delay between a request to transmit and the first iteration of CSMA-CA.
AT commands Networking and security commands Default [read-only] NT (Node Discover Timeout) Sets the amount of time a base node waits for responses from other nodes when using the ND (Node Discover) command. The NT value is transmitted with the ND command. Remote nodes set up a random hold-off time based on this time. Once the ND command has ended, the base discards any response it receives. Parameter range 0x1 - 0xFC (x 100 ms) Default 0x19 (2.
AT commands Networking and security commands 1. The receiving device returns a success response in a AT Command Response (0x88) frame. 2. If there is no response from a module within (NT * 100) milliseconds or you do not specify a parameter (by leaving it blank), the receiving device returns an ERROR message.
AT commands Networking and security commands Bit Parameter 7 0x12 8 0x13 9 0x14 10 0x15 11 0x16 12 0x17 13 0x18 (not available on XBee-PRO) 14 0x19 (not available on XBee-PRO) 15 0x1A (not available on XBee-PRO) Default 0x1FFE SD (Scan Duration) Sets or reads the scan duration exponent.
AT commands Networking and security commands Parameter range 0 - 0x0F (exponent) Default 4 A1 (End Device Association) Sets or reads the End Device association options. Parameter range 0 - 0x0F (bit field) Bit field: Bit Meaning Setting Description 0 0 Only associates with Coordinator operating on PAN ID that matches device ID. 1 May associate with Coordinator operating on any PAN ID. 0 Only associates with Coordinator operating on matching CH channel setting.
AT commands Networking and security commands Bit Meaning Setting Description 0 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.
AT commands Networking and security commands Default N/A FP (Force Poll) Requests indirect messages being held by a Coordinator. The FP command is deferred until changes are applied. This prevents indirect messages from arriving at the end device while it is operating in Command mode. Parameter range N/A Default N/A AS (Active Scan) Sends a Beacon Request to a Broadcast address (0xFFFF) and Broadcast PAN (0xFFFF) on every channel in SC.
AT commands Networking and security commands Total scan time is this time multiplied by the number of channels to be scanned (as determined by the SC parameter). Refer to the scan table in SD (Scan Duration) on page 68 to determine scan times. If using API Mode, no ’s are returned in the response. For more information, see Operate in API mode on page 97. Parameter range 0-6 Default N/A ED (Energy Detect) Starts an energy detect scan.
AT commands RF interfacing commands Default 0 KY (AES Encryption Key) Sets the 128-bit network security key value that the device uses for encryption and decryption. This command is write-only. If you attempt to read KY, the device returns an OK status. Set this command parameter the same on all devices in a network. The entire payload of the packet is encrypted using the key and the CRC is computed across the ciphertext.
AT commands RF interfacing commands Parameter range 0-4 The following table shows the TX power versus the PL setting. XBee modules PL setting PM setting Channel(s) TX power* (dBm) 4 1 11 to 25 8 4 0 11 to 25 5 3 1 11 to 25 6 3 0 11 to 25 3 2 1 11 to 25 4 2 0 11 to 25 1 1 1 11 to 25 2 1 0 11 to 25 -1 0 1 11 to 25 -2 0 0 11 to 25 -5 X 1 26 -5 X 0 26 -8 * Highest power level is tested during manufacturing. Other power levels are approximate.
AT commands Sleep commands This command is disabled on the XBee-PRO and is forced on by the software to provide extra sensitivity. Boost mode imposes a slight increase in current draw. Parameter range 0-1 Setting Meaning 0 Boost mode disabled 1 Boost mode enabled Default 1 CA (CCA Threshold) Set or read the Clear Channel Assessment (CCA) threshold. Prior to transmitting a packet, the device performs a CCA to detect energy on the channel.
AT commands Sleep commands Parameter Description 2 Reserved 3 Reserved 4 Cyclic Sleep Remote 5 Cyclic Sleep Remote with pin wakeup Default 0 ST (Time before Sleep) Sets or reads the wake time of the device. The ST parameter is only valid for end devices configured with Cyclic Sleep settings (SM = 4 - 5) and for coordinators. Coordinator and End Device ST values must be equal.
AT commands Serial interfacing commands DP should be > 0. Parameter range 1 - 0x68B0 (x 10 ms) Default 0x3E8 (10 seconds) SO (Sleep Options) Set or read the sleep options bit field of a device. This command is a bitmask. You can set or clear any of the available sleep option bits.
AT commands Serial interfacing commands Non-standard interface data rates The firmware interprets any value from 0x4B0 through 0x3D090 as an actual baud rate. When the firmware cannot configure the exact rate specified, it configures the closest approximation to that rate. For example, to set a rate of 57600 b/s send the following command line: ATBDE100. Then, to find out the closest approximation, send ATBD to the console window.
AT commands Serial interfacing commands NB (Parity) Set or read the parity settings for UART communications. The device does not actually calculate and check the parity; it only interfaces with devices at the configured parity and stop bit settings.
AT commands Serial interfacing commands Default 1 D6(DIO6/RTS) The DIO6/RTS pin configuration (pin 16 for through-hole, pin 29 for surface-mount). Parameter range 0, 1, 3 - 5 Parameter Description 0 Disabled 1 RTS flow control 2 N/A 3 Digital input 4 Digital output, low 5 Digital output, high Default 0 AP (API Enable) The API mode setting. The device can format the RF packets it receives into API frames and send them out the serial port.
AT commands I/O settings commands Parameter Description 0 API disabled (operate in transparent mode) 1 API enabled 2 API enabled (w/escaped control characters) Default 0 I/O settings commands The following AT commands are I/O settings commands. D0 (DIO0/AD0) The DIO0/AD0 pin configuration (pin 20 for through-hole, pin 33 for surface-mount).
AT commands I/O settings commands Parameter Description 3 Digital input 4 Digital output, low 5 Digital output, high Default 0 D2 (DIO2/AD2) The DIO2/AD2 pin configuration (pin 18 for through-hole, pin 31 for surface-mount). Parameter range 0-5 Parameter Description 0 Disabled 1 SPI_CLK for through-hole device 2 ADC 3 Digital input 4 Digital output, low 5 Digital output, high Default 0 D3 (DIO3/AD3) The DIO3/AD3 pin configuration (pin 17 for through-hole, pin 30 for surface-mount).
AT commands I/O settings commands Parameter Description 3 Digital input 4 Digital output, low 5 Digital output, high Default 0 D4 (DIO4 ) The DIO4 pin configuration (pin 11 for through-hole, pin 24 for surface-mount).
AT commands I/O settings commands Parameter Description 3 Digital input 4 Digital output, default low 5 Digital output, default high Default 1 D8 (DIO8/SLEEP_REQUEST) The DIO8/SLEEP_REQUEST pin configuration (pin 9 for through-hole, pin 10 for surface-mount). This command enables you to configure the pin to function as a digital input. This line is also used with Pin Sleep, but pin sleep ignores the D8 configuration. It is always used to control pin sleep, regardless of configuration of D8.
AT commands I/O settings commands Parameter Description 0 Disabled 1 RSSI PWM0 output 2 PWM0 output Default 1 P1 (PWM1 Configuration) The PWM1 pin configuration (pin 7 for through-hole, pin 8 for surface-mount). If the IA (I/O Input Address) parameter is correctly set and P1 is configured as PWM1 output, incoming AD0 samples automatically modify the PWM1 value. Parameter range 0, 2 Parameter Description 0 Disabled 2 PWM1 output Default 0 P2 (SPI_MISO) The SPI_MISO pin configuration (pin 4).
AT commands I/O settings commands Before setting the line as an output: 1. Enable PWM0 output (P0 = 2). 2. Apply settings (use CN or AC). To configure the duty cycle of PWM0: The PWM period is 64 µs and there are 0x03FF (1023 decimal) steps within this period. When M0 = 0 (0% PWM), 0x01FF (50% PWM), 0x03FF (100% PWM), and so forth. Parameter range 0 - 0x3FF Default 0 M1 (PWM1 Duty Cycle) The duty cycle of the PWM1 line (pin 8 for through-hole, pin 9 for surface-mount).
AT commands I/O settings commands Parameter Description 0 Disabled 1 SPI_MOSI Default 1 P7 (SPI_SSEL ) The SPI_SSEL pin configuration (pin 15). This only applies to surface-mount devices. Parameter range 1, 2 Parameter Description 0 Disabled 1 SPI_SSEL Default 1 P8 (SPI_SCLK) The SPI_SCLK pin configuration (pin 14). This only applies to surface-mount devices.
AT commands I/O settings commands Parameter Description 0 Disabled 1 SPI_ATTN Default 1 PR (Pull-up/Down Resistor Enable) The bit field that configures the internal pull-up/down resistor status for the I/O lines. If you set a PR bit to 1, it enables the pull-up/down resistor; 0 specifies no internal pull-up/down resistor. The following table defines the bit-field map for both the PR and PD commands. The PD (Pull Direction) parameter determines the direction of the internal pull-up/down resistor.
AT commands I/O settings commands IU (I/O Output Enable) IU (Send I/O Sample to Serial Port) The IU command disables or enables I/O UART output. When enabled (IU = 1), received I/O line data packets are sent out the UART. The data is sent using an API frame regardless of the current AP parameter value. Parameter range Parameter Description 0 Disabled 1 Enabled Default 1 IT (Samples before TX) Sets or reads the number of samples to collect before transmission.
AT commands I/O settings commands Default N/A IO (Digital Output Level) Sets digital output levels. This allows DIO lines setup as outputs to be changed through Command Mode. Parameter range 8-bit bit map; each bit represents the level of an I/O line setup as an output Default - IC (DIO Change Detect) Set or read the digital I/O pins to monitor for changes in the I/O state. Each bit enables monitoring of DIO0 - DIO7 for changes. If detected, data is transmitted with DIO data only.
AT commands I/O line passing Default 0x28 (four seconds) I/O line passing The following AT commands are I/O line passing commands. IA (I/O Input Address) The source address of the device to which outputs are bound. Setting all bytes to 0xFF disables I/O line passing. Setting IA to 0xFFFF allows any I/O packet addressed to this device (including broadcasts) to change the outputs.
AT commands I/O line passing T3 (D3 Timeout) Specifies how long pin D3 holds a given value before it reverts to configured value. If set to 0, there is no timeout. Parameter range 0 - 0xFF (x 100 ms) Default 0xFF T4 (D4 Timeout) Specifies how long pin D4 holds a given value before it reverts to configured value. If set to 0, there is no timeout. Parameter range 0 - 0xFF (x 100 ms) Default 0xFF T5 (D5 Timeout) Specifies how long pin D5 holds a given value before it reverts to configured value.
AT commands Diagnostic commands PT (PWM Output Timeout) Specifies how long both PWM outputs (P0, P1) output a given PWM signal before it reverts to the configured value (M0/M1). If set to 0, there is no timeout. This timeout only affects these pins when they are configured as PWM output. Parameter range 0 - 0xFF (x 100 ms) Default 0xFF VL (Version Long) Shows detailed version information including the application build date and time.
AT commands Command mode options The command measures RSSI in -dBm. For example if DB returns 0x60, then the RSSI of the last packet received was -96 dBm. This value is volatile (the value does not persist in the device's memory after a power-up sequence). Parameter range [Read-only] 0x17 - 0x5C (XBee) 0x24 - 0x64 (XBee-PRO) [Read-only] 0-0xFF Default - EC (CCA Failures) Resets or reads the count of Clear Channel Assessment (CCA) failures.
AT commands Command mode options Parameter range 2 - 0x1770 (x 100 ms) Default 0x64 (10 seconds) CN (Exit Command mode) Makes the device exit Command mode, applying changes. Parameter range N/A Default N/A AC (Apply Changes) Immediately applies new settings without exiting Command mode. Applying changes means that the device is re-initialized based on changes made to its parameter values. Once changes are applied, the device immediately operates according to the new parameter values.
AT commands Command mode options Parameter range 0 - 0xFF Default 0x2B (+) XBee/XBee-PRO S2C 802.15.
Operate in API mode API mode overview API frames XBee/XBee-PRO S2C 802.15.
Operate in API mode API mode overview API mode overview As an alternative to Transparent operating mode, you can use API operating mode. API mode provides a structured interface where data is communicated through the serial interface in organized packets and in a determined order. This enables you to establish complex communication between devices without having to define your own protocol.
Operate in API mode API mode overview Frame fields Byte Description Length 2-3 Most Significant Byte, Least Significant Byte Characters escaped if needed Frame Data 4-n API-specific structure Checksum n + 1 1 byte Escape characters When sending or receiving a UART data frame, you must escape (flag) specific data values so they do not interfere with the data frame sequencing. To escape an interfering data byte, insert 0x7D and follow it with the byte to be escaped XOR’d with 0x20.
Operate in API mode n API mode overview Data contains the data itself. This information and its order depend on the what type of frame that the Frame type field defines.
Operate in API mode API mode overview 2. Keep only the lowest 8 bits from the result. 3. Subtract this quantity from 0xFF. To verify the checksum of an API frame: 1. Add all bytes including the checksum; do not include the delimiter and length. 2. If the checksum is correct, the last two digits on the far right of the sum will equal 0xFF.
Operate in API mode API frames API frames The device sends multi-byte values in big-endian format. The XBee/XBee-PRO S2C 802.15.4 RF Module supports API frames in the following table. Request frames are less than 0x80 and responses are always 0x80 or higher.
Operate in API mode API frames Modem Status frame - 0x8A Description Devices send the status messages in this frame in response to specific conditions. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode API frames AT Command frame - 0x08 Description Use this frame to query or set device parameters on the local device. This API command applies changes after running the command. You can query parameter values by sending the 0x08 AT Command frame with no parameter value field (the two-byte AT command is immediately followed by the frame checksum). A 0x88 response frame is populated with the parameter value that is currently set on the device.
Operate in API mode API frames Frame data fields Offset Example Frame ID 4 0x4D (M)1 AT command 5 0x44 (D) 6 0x4C (L) Parameter value 7-10 0x00000FFF Checksum 11 0x0C 1M was arbitrarily selected. XBee/XBee-PRO S2C 802.15.
Operate in API mode API frames AT Command - Queue Parameter Value frame - 0x09 Description This frame allows you to query or set device parameters. In contrast to the AT Command (0x08) frame, this frame queues new parameter values and does not apply them until you issue either: n The AT Command (0x08) frame (for API type) n The AC command When querying parameter values, the 0x09 frame behaves identically to the 0x08 frame. The device returns register queries immediately and not does not queue them.
Operate in API mode API frames AT Command Response frame - 0x88 Description A device sends this frame in response to an AT Command (0x08) frame and a queued AT command 0x09. Some commands send back multiple frames; for example, the ND command. This command ends by sending a frame with a status of 0 (OK) and no value. In the particular case of ND, a frame is received via a remote node in the network and when the process is finished, the AT command response is received.
Operate in API mode API frames Frame data fields Offset Example AT command Command status 5 0x42 (B) 6 0x44 (D) 7 0x00 8 0xF0 Command data Checksum XBee/XBee-PRO S2C 802.15.
Operate in API mode API frames Remote AT Command Request frame - 0x17 Description Used to query or set device parameters on a remote device. For parameter changes on the remote device to take effect, you must apply changes, either by setting the apply changes options bit, or by sending an AC command to the remote. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode API frames Remote Command Response frame - 0x97 Description If a device receives this frame in response to a Remote Command Request (0x17) frame, the device sends an AT Command Response (0x97) frame out the serial interface. Some commands, such as the ND command, may send back multiple frames. For details on the behavior of ND, see ND (Network Discover) on page 65. Format The following table provides the contents of the frame.
Operate in API mode API frames TX Request: 64-bit address frame - 0x00 Description This frame causes the device to send payload data as an RF packet. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode API frames TX Request: 16-bit address - 0x01 Description A TX Request message causes the device to transmit data as an RF Packet. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98. Frame data fields Offset Description Frame type 3 0x01 Frame ID 4 Identifies the data frame for the host to correlate with a subsequent ACK (0x89). If set to 0, the device does not send a response.
Operate in API mode API frames TX Status frame - 0x89 Description When a TX request: 64-bit address (0x00) or 16-bit address (0x01) is complete, the device sends a TX Status frame. This message indicates if the packet transmitted successfully or if there was a failure. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode API frames Frame data fields Offset Example Length MSB 1 0x00 LSB 2 0x03 Frame type 3 0x89 Frame ID 4 0x01 Status 5 0x00 Checksum 6 0x75 XBee/XBee-PRO S2C 802.15.
Operate in API mode API frames RX Packet: 64-bit Address frame - 0x80 Description When a device receives an RF data packet from a device configured to use 64-bit addressing (MY = FFFF or FFFE), it sends this frame out the serial interface. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98. Frame data fields Offset Description Frame type 3 0x80 64-bit source address 4-11 The sender's 64-bit address.
Operate in API mode API frames Receive Packet: 16-bit address frame - 0x81 Description When the device receives an RF packet from a device configured to use 16 bit addressing (MY < FFFE), it sends this frame out the serial interface. Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode API frames RX (Receive) Packet: 64-bit address IO - 0x82 Description When the device receives an I/O sample from a remote device configured to use 64-bit addressing, the I/O data is sent out the UART using this frame type Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98.
Operate in API mode Frame data fields API frames Total number of Offset samples Description 19 ADC0 MSB 20 ADC0 LSB ... N/A n -1 ADCn mSB n ADCn LSB If the sample set includes any ADC data, each enabled analog input returns a two-byte value indicating the A/D measurement of that input. ADC channel data is represented as an unsigned 10-bit value right-justified on a 16-bit boundary. Analog samples are ordered sequentially from AD0 to AD5.
Operate in API mode API frames RX Packet: 16-bit address IO - 0x83 Description When the device receives an I/O sample from a remote device configured to use 16-bit addressing, the I/O data is sent out the UART using this frame type Format The following table provides the contents of the frame. For details on frame structure, see API frame specifications on page 98. Total number Frame data of fields Offset samples Description Frame type 3 N/A 0x83 Source Address 4-5 N/A MSB first, LSB last.
Operate in API mode API frames Total number Frame data of fields Offset samples Description Analog samples 13 ADC0 MSB 14 ADC0 LSB If the sample set includes any ADC data, each enabled analog input returns a two-byte value indicating the A/D measurement of that input. ADC channel data is represented as an unsigned 10-bit value right-justified on a 16-bit boundary. Analog samples are ordered sequentially from AD0 to AD5. ...
Certifications United States (FCC) Europe Canada (IC) XBee/XBee-PRO S2C 802.15.
Certifications United States (FCC) United States (FCC) The XBee/XBee-PRO S2C 802.15.4 RF Modules comply 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, 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. 2.
Certifications United States (FCC) 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.
The XBee and XBee-PRO ZB RF Modules can be installed utilizing antennas and cables constructed with non-standard connectors (RPSMA, RPTNC, etc.) An adapter cable may be necessary to attach the XBee connector to the antenna connector. The modules are FCC approved for fixed base station and mobile applications for the channels indicated in the tables below. If the antenna is mounted at least 25 cm (10 in) from nearby persons, the application is considered a mobile application.
Part number Type (description) A24-HASM- Dipole (Half-wave articulated RPSMA - 5.25") 525 Gain (dBi) Min. Application* separation Channels 11-24 Channel Channel 25 26 2.1 Fixed 25 cm N/A N/A N/A Certifications XBee/XBee-PRO S2C 802.15.4 RF Module User Guide Required antenna cable loss (dB) Omni-directional antennas A24-F2NF Omni-directional (Fiberglass base station) 2.1 Fixed/Mobile 25 cm N/A N/A N/A A24-F3NF Omni-directional (Fiberglass base station) 3.
Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-24 Channel Channel 25 26 A24-P16NF Flat Panel 16.0 Fixed 2m N/A 6.1 13.6 A24-P19NF Flat Panel 19.0 Fixed 2m 1.1 9.1 16.6 Certifications XBee/XBee-PRO S2C 802.15.4 RF Module User Guide Required antenna cable loss (dB) Yagi antennas A24-Y6NF Yagi (6-element) 8.8 Fixed 2m N/A N/A 3.9 A24-Y7NF Yagi (7-element) 9.0 Fixed 2m N/A N/A 4.1 A24-Y9NF Yagi (9-element) 10.0 Fixed 2m N/A N/A 5.
The following table shows the antennas approved for use with the XBee S2C TH RF Module. Required antenna cable loss (dB) Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-24 Channel Channel 25 26 Certifications XBee/XBee-PRO S2C 802.15.4 RF Module User Guide XBee S2C TH RF Module Integral antennas 29000294 Integral PCB antenna -0.5 Fixed/Mobile 25 cm N/A N/A N/A A24-QI Monopole (Integrated whip) 1.5 Fixed/Mobile 25 cm N/A N/A N/A 2.
Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-24 Channel Channel 25 26 A24-F9NF Omni-directional (Fiberglass base station) 9.5 Fixed 2m N/A N/A 0.9 A24-F10NF Omni-directional (Fiberglass base station) 10.0 Fixed 2m N/A N/A 1.4 A24-F12NF Omni-directional (Fiberglass base station) 12.0 Fixed 2m N/A N/A 3.4 A24-W7NF Omni-directional (Fiberglass base station) 7.
Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-24 Channel Channel 25 26 A24-Y12NF Yagi (12-element) 12.0 Fixed 2m N/A 2.4 7.9 A24-Y13NF Yagi (13-element) 12.0 Fixed 2m N/A 2.4 7.9 A24-Y15NF Yagi (15-element) 12.5 Fixed 2m N/A 2.9 8.4 A24-Y16NF Yagi (16-element) 13.5 Fixed 2m N/A 3.9 9.4 A24-Y16RM Yagi (16-element, RPSMA connector) 13.5 Fixed 2m N/A 3.9 9.4 A24-Y18NF Yagi (18-element) 15.0 Fixed 2m 0.4 5.4 10.
The following table shows the antennas approved for use with the XBee-PRO S2C SMT RF Module. Required antenna cable loss (dB) Part Number Type (Description) Gain (dBi) Min Application* Separation Channels 11-23† Channel 24† Certifications XBee/XBee-PRO S2C 802.15.4 RF Module User Guide XBee-PRO S2C SMT RF Module Internal antennas 29000313 Integral PCB antenna 0.0 Fixed/Mobile 25 cm N/A N/A A24-QI Monopole (Integrated whip) 1.
Type (Description) Gain (dBi) Min Application* Separation Channels 11-23† Channel 24† A24-F9NF Omni-directional (Fiberglass base station) 9.5 Fixed 2m N/A N/A A24-F10NF Omni-directional (Fiberglass base station) 10 Fixed 2m N/A N/A A24-F12NF Omni-directional (Fiberglass base station) 12 Fixed 2m N/A 1.6 A24-W7NF Omni-directional (Fiberglass base station) 7.2 Fixed 2m N/A N/A A24-M7NF Omni-directional (Mag-mount base station) 7.
Type (Description) Gain (dBi) Min Application* Separation Channels 11-23† Channel 24† A24-Y12NF Yagi (12-element) 12.0 Fixed 2m 1.6 5.1 A24-Y13NF Yagi (13-element) 12.0 Fixed 2m 1.6 5.1 A24-Y15NF Yagi (15-element) 12.5 Fixed 2m 2.1 5.6 A24-Y16NF Yagi (16-element) 13.5 Fixed 2m 3.1 6.6 A24-Y16RM Yagi (16-element, RPSMA connector) 13.5 Fixed 2m 3.1 6.6 A24-Y18NF Yagi (18-element) 15.0 Fixed 2m 4.6 8.1 Part Number Certifications XBee/XBee-PRO S2C 802.15.
The following table shows the antennas approved for use with the XBee-PRO S2C TH RF Module. Required antenna cable loss (dB) Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-23† Channel 24† Certifications XBee/XBee-PRO S2C 802.15.4 RF Module User Guide XBee-PRO S2C TH RF Module Integral antennas 29000294 Integral PCB antenna -0.5 Fixed/Mobile 25 cm N/A N/A A24-QI Monopole (Integrated whip) 1.
Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-23† Channel 24† A24-F9NF Omni-directional (Fiberglass base station) 9.5 Fixed 2m N/A N/A A24-F10NF Omni-directional (Fiberglass base station) 10.0 Fixed 2m N/A N/A A24-F12NF Omni-directional (Fiberglass base station) 12.0 Fixed 2m N/A 1.4 A24-W7NF Omni-directional (base station) 7.2 Fixed 2m N/A N/A A24-M7NF Omni-directional (Mag-mount base station) 7.
Part number Type (description) Gain (dBi) Min. Application* separation Channels 11-23† Channel 24† A24-Y12NF Yagi (12-element) 12.0 Fixed 2m 1.4 4.4 A24-Y13NF Yagi (13-element) 12.0 Fixed 2m 1.4 4.4 A24-Y15NF Yagi (15-element) 12.5 Fixed 2m 1.9 4.9 A24-Y16NF Yagi (16-element) 13.5 Fixed 2m 2.9 5.9 A24-Y16RM Yagi (16-element, RPSMA connector) 13.5 Fixed 2m 2.9 5.9 A24-Y18NF Yagi (18-element) 15.0 Fixed 2m 4.4 7.4 Certifications XBee/XBee-PRO S2C 802.15.
Certifications Europe RF exposure If you are an integrating the XBee into another product, you must include the following Caution statement in OEM product manuals to alert users of FCC RF exposure compliance: CAUTION! To satisfy FCC RF exposure requirements for mobile transmitting devices, a separation distance of 25 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 are not recommended.
Certifications Canada (IC) 2. Set the CA command as described in CA (CCA Threshold) on page 75 to enable LBT at the required noise threshold level. Declarations of conformity Digi has issued Declarations of Conformity for the XBee RF Modules concerning emissions, EMC, and safety. Files can be obtained by contacting Digi Support. Important note Digi does not list the entire set of standards that must be met for each country.
Certifications Canada (IC) For XBee S2C through hole Contains Model S2CTH Radio, IC: 1846A-S2CTH The integrator is responsible for its product to comply with IC ICES-003 & FCC Part 15, Sub. B Unintentional Radiators. ICES-003 is the same as FCC Part 15 Sub. B and Industry Canada accepts FCC test report or CISPR 22 test report for compliance with ICES-003.
Load 802.15.4 firmware on ZB devices Background Load 802.15.4 firmware XBee/XBee-PRO S2C 802.15.
Load 802.15.4 firmware on ZB devices Background Background Our XBee/XBee-PRO ZB RF modules are built on the same hardware as the XBee/XBee-PRO S2C 802.15.4 RF Module. It is possible to load 802.15.4 firmware on existing ZB modules. The table below shows which part numbers are compatible with 802.15.4 firmware. Note Currently the 802.15.4 firmware is approved for use only in the United States, Canada, and Europe.
Load 802.15.4 firmware on ZB devices Load 802.15.4 firmware 4. When you get to the Update firmware dialog box, in the Function set area, click the 802.15.4 option, and the newest firmware version. 5. Click Update and follow the instructions. 6. When the updating process successfully completes, your device runs 802.15.4 firmware. You can change back to ZigBee firmware at any time by following the same process and selecting the ZigBee firmware option instead. XBee/XBee-PRO S2C 802.15.
Migrate from XBee through-hole to surface-mount devices We design the XBee surface mount and through-hole devices to be compatible with each other and offer the same basic feature set. The surface mount form factor has more I/O pins. Because the XBee device was originally offered in only the through-hole form factor, we offer this section to help you migrate from the through-hole to the surface-mount form factor. Pin mapping Mount the devices XBee/XBee-PRO S2C 802.15.
Migrate from XBee through-hole to surface-mount devices Pin mapping Pin mapping The following table shows the pin mapping for the surface-mount (SMT) pins to the through-hole (TH) pins. The pin names are from the XBee S2C SMT device.
Migrate from XBee through-hole to surface-mount devices SMT Pin # Name Mount the devices TH Pin # 28 DIO5/ASSOC 15 29 DIO6/RTS 16 30 DIO3/AD3 17 31 DIO2/AD2 18 32 DIO1/AD1 19 33 DIO0/AD0 20 34 [Reserved] 35 GND 36 RF 37 [Reserved] Mount the devices One important difference between the SMT and TH devices is the way they mount to a printed circuit board (PCB). Each footprint requires different mounting techniques.
Migrate from XBee through-hole to surface-mount devices Mount the devices The round holes in the diagram are for the TH design, and the semi-oval pads are for the SMT design. Pin 1 of the TH design is lined up with pad 1 of the SMT design, but the pins are actually offset by one pad; see Pin mapping on page 143. By using diagonal traces to connect the appropriate pins, the layout will work for both devices. PCB design and manufacturing on page 146 contains information on attaching the SMT device.
PCB design and manufacturing The XBee/XBee-PRO S2C 802.15.4 RF Module is designed for surface mount on the OEM PCB. It has castellated pads to allow for easy solder attach inspection. The pads are all located on the edge of the module, so there are no hidden solder joints on these modules. Recommended solder reflow cycle Recommended footprint and keepout Flux and cleaning Rework XBee/XBee-PRO S2C 802.15.
PCB design and manufacturing Recommended solder reflow cycle Recommended solder reflow cycle The following table provides the recommended solder reflow cycle. The table shows the temperature setting and the time to reach the temperature; It does not show the cooling cycle. Time (seconds) Temperature (degrees C) 30 65 60 100 90 135 120 160 150 195 180 240 210 260 The maximum temperature should not exceed 260°C.
PCB design and manufacturing Recommended footprint and keepout Match the solder footprint to the copper pads, but you may need to adjust it depending on the specific needs of assembly and product standards. We recommend a stencil thickness of 0.15 mm (0.005 in). Place the component last and set the placement speed to the slowest setting.
PCB design and manufacturing Flux and cleaning Flux and cleaning We recommend that you use a “no clean” solder paste in assembling these devices. This eliminates the clean step and ensures that you do not leave unwanted residual flux under the device where it is difficult to remove. In addition: n Cleaning with liquids can result in liquid remaining under the device or in the gap between the device and the host PCB. This can lead to unintended connections between pads.
PCB design and manufacturing Rework following information is given as a guideline in such cases to increase the chances of success during rework, though the warranty is still voided. The module may be removed from the OEM PCB by the use of a hot air rework station, or hot plate. Care should be taken not to overheat the module. During rework, the module temperature may rise above its internal solder melting point and care should be taken not to dislodge internal components from their intended positions.
