Digi XBEEXSC XBee-PRO XSC RF Module User Manual manual xs oem rf module v42b5
Digi International Inc XBee-PRO XSC RF Module manual xs oem rf module v42b5
UserManual.wiki
>
Digi
>
XBEEXSC User Manual
>
User Manual
Contents
1.
User Manual
2.
Antenna List
User Manual
Navigation menu
Upload a User Manual
Namespaces
Wiki Guide
HTML
PDF
Info
Views
User Manual
Discussion / Help
Navigation
![XBee‐PRO™XSCRFModule‐ProductManual90000938‐A[2008.2.25]©2008DigiInternational,Inc. ii© 2008 Digi International, Inc. All rights reservedNopartofthecontentsofthismanualmaybetransmittedorreproducedinanyformorbyanymeanswithoutthewrittenpermissionofDigiInternational,Inc.XBee‐PRO™isaregisteredtrademarkofDigiInternationalInc.TechnicalSupport:Phone:(801)765‐9885LiveChat:www.digi.comE‐mail:support@digi.com](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-2.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 11PreliminaryDraft2.1.3. Flow ControlFigure2‐03. InternalDataFlowDiagram(Thefivemostcommonly‐usedpinsignalsshown.)DI (Data In) Buffer and Flow ControlWhen serial data enters the XBee-PRO Module through the DI Pin, then the data is stored in the DI Buffer until it can be transmitted.When the RO parameter threshold is satisfied (refer to Transmit Mode and Command Descriptions sections for more information), the module attempts to initialize an RF connection. If the module is already receiving RF data, the serial data is stored in the module's DI Buffer. 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 XBee-PRO OEM RF Module).How to eliminate the need for flow control:• Send messages that are smaller than the DI buffer size. The size of the DI buffer varies according to the packet size and parity setting used.• Interface at a lower baud rate (BD parameter) than the fixed RF data rate.Two cases in which the DI Buffer may become full and possibly overflow:• If the serial interface data rate is set higher than the RF data rate of the module, the module will receive data from the host faster than it can transmit the data over-the-air.• If the module is receiving a continuous stream of RF data or if the module is monitoring data on a network, 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 no longer detects RF data in the network.Hardware Flow Control (CTS). When the DI buffer is 17 bytes away from being full; by default, the module de-asserts (high) CTS to signal to the host device to stop sending data [refer to FT (Flow Control Threshold) and CS (DO2 Configuration) Commands]. CTS is re-asserted after the DI Buffer has 34 bytes of memory available.Software Flow Control (XON). XON/XOFF software flow control can be enabled using the FL (Software Flo DO (Data Out) Buffer and Flow ControlDO (Data Out) Buffer and Flow ControlWhen RF data is received, the data enters the DO buffer and is then sent out the serial port to a host device. Once the DO Buffer reaches capacity, any additional incoming RF data is lost.Two cases in which the DO Buffer may become full and possibly overflow:• 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.• 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.Hardware Flow Control (RTS). If RTS is enabled for flow control (RT Parameter = 2), data will not be sent out the DO Buffer as long as RTS (pin 16) is de-asserted.Software Flow Control (XOFF). XON/XOFF software flow control can be enabled using the FL (Software Flow Control) Command. This option only works with ASCII data.](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-11.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 13PreliminaryDraftRF PacketFigure2‐06. RFPacketComponents* When streaming multiple RF packets, the RF Initializer is only sent in front of the first packet.RF InitializerAn RF initializer is sent each time a new connection sequence begins. The RF initializer contains channel information that notifies receiving modules of information such as the hopping pattern used by the transmitting module. The first transmission always sends an RF initializer.An RF initializer can be of various lengths depending on the amount of time determined to be required to prepare a receiving module. For example, a wake-up initializer is a type of RF initializer used to wake remote modules from Sleep Mode (Refer to the FH, LH, HT and SM Commands for more information). The length of the wake-up initializer should be longer than the length of time remote modules are in cyclic sleep.HeaderThe header contains network addressing information that filters incoming RF data. The receiving module checks for a matching VID, Hopping Channel and Destination Address. Data that does not pass through all three network filter layers is discarded.Figure2‐07. AddressingLayerscontainedintheHeaderCRC (Cyclic Redundancy Check)To verify data integrity and provide built-in error checking, a 16-bit CRC (Cyclic Redundancy Check) is computed for the transmitted data and attached to the end of each RF packet. On the receiving end, the receiving module computes the CRC on all incoming RF data. Received data that has an invalid CRC is discarded [See Receive Mode section, next page].](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-13.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 14PreliminaryDraft2.2.3. Receive ModeIf a module detects RF data while operating in Idle Mode, the module transitions into Receive Mode to start receiving RF packets. Figure2‐08. ReceptionofRFDataAfter a packet is received, the module checks the CRC (cyclic redundancy check) to ensure that the data was transmitted without error. If the CRC data bits on the incoming packet are invalid, the packet is discarded. If the CRC is valid, the packet proceeds to the DO Buffer.The module returns to Idle Mode after valid RF data is no longer detected or after an error is detected in the received RF data. If serial data is stored in the DI buffer while the module is in Receive Mode, the serial data will be transmitted after the module is finished receiving data and returns to Idle Mode.2.2.4. Sleep ModeSleep Modes enable the XBee-PRO Module to operate at minimal power consumption when not in use. Three Sleep Mode options are available: •Pin Sleep •Cyclic Sleep For the module to transition into Sleep Mode, the module must have a non-zero SM (Sleep Mode) Parameter and one of the following must occur:• The module is idle (no data transmission or reception) for a user-defined period of time [Refer to the ST (Time before Sleep) Command].• SLEEP is asserted (only for Pin Sleep option).In Sleep Mode, the module will not transmit or receive data until the module first transitions to Idle Mode. All Sleep Modes are enabled and disabled using SM Command. Transitions into and out of Sleep Modes are triggered by various events as shown in the table below.Tab le2‐01. SummaryofSleepModeConfigurationsPin Sleep (SM = 1)Pin Sleep requires the least amount of power. In order to achieve this state, SLEEP pin must be asserted (high). The module remains in Pin Sleep until the SLEEP pin is de-asserted. After enabling Pin Sleep, the SLEEP pin controls whether the XBee-PRO Module is active or in Sleep Mode. When SLEEP is de-asserted (low), the module is fully operational. When SLEEP is asserted (high), the module transitions to Sleep Mode and remains in its lowest power-consuming state until the SLEEP pin is de-asserted. SLEEP is only active if the module is setup to operate in this mode; otherwise the pin is ignored.Sleep Mode SettingTransition into Sleep ModeTransition out of Sleep ModeRelated CommandsTypical Power ConsumptionPin Sleep(SM = 1)Microcontroller can shut down and wake modules by asserting (high) SLEEP (pin 2). Note: The module will complete a transmission or reception before activating Pin Sleep.De-assert (low) SLEEP (pin 2). SM 50 µACyclic Sleep(SM = 3-8)Automatic transition to Sleep Mode occurs in cycles as defined by the SM (Sleep Mode) Command.Note: The cyclic sleep time interval must be shorter than the “Wake-up Initializer Timer” (set by LH Command).After the cyclic sleep time interval elapses. Note: Module can be forced into Idle Mode if PW (Pin Wake-up) Command is issued.SM, ST, HT, LH, PW76 µA when sleeping](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-14.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 17PreliminaryDraft2.2.5. Command ModeTo modify or read module parameters, the module must first enter into Command Mode, the state in which incoming characters are interpreted as commands. Two command types are available for pro-gramming the module:• AT Commands• Binary CommandsFor modified parameter values to persist in the module registry, changes must be saved to non-vola-tile memory using WR (Write) Command. Otherwise, parameters are restored to previously saved val-ues after the module is powered off and then on again.AT CommandsTo Enter AT Command Mode:• Send the 3-character command sequence "+++" and observe guard times before and after the command characters. [refer to ‘Default AT Command Mode Sequence’ below.] The ‘Termi-nal’ tab (or other serial communications software) of the X-CTU Software can be used to enter the sequence.[OR]• Assert (low) the CONFIG pin and either turn the power going to the module off and back on. (If using a Digi XBIB-R Interface Board, the same result can be achieved by holding the Data-In line low (also known as a break) while rebooting the module by pressing the reset button on the module assembly [module assembly = module mounted to an interface board]).Default AT Command Mode Sequence (for transition to Command Mode):• No characters sent for one second [refer to the BT (Guard Time Before) Command]• Input three plus characters (“+++”) within one second [refer to the CC (Command Sequence Character) Command.]• No characters sent for one second [refer to the AT (Guard Time After) Command.]To Send AT Commands:Send AT commands and parameters using the syntax shown below.Figure2‐11.SyntaxforsendingATCommandsTo read a parameter value stored in the module register, leave the parameter field blank.The preceding example would change the module’s Destination Address to "0x1F". To store the new value to non-volatile (long term) memory, the Write (ATWR) command must subsequently be sent before powering off the module.System Response. When a command is sent to the 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:• If no valid AT Commands are received within the time specified by CT (Command Mode Time-out) Command, the module automatically returns to Idle Mode. [OR]• Send ATCN (Exit Command Mode) Command.For an example of programming the RF module using AT Commands and descriptions of each config-urable parameter, refer to the "RF Module Configuration" chapter.](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-17.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 18PreliminaryDraftBinary CommandsSending and receiving parameter values using binary commands is the fastest way to change operating parameters of the module. Binary commands are used most often to sample signal strength (RS parameter) and/or error counts; or to change module addresses and channels for polling systems when a quick response is necessary. Since the sending and receiving of parameter values takes place through the same data path as 'live' data (received RF payload), interference between the two types of data can be a concern.Common questions regarding the use of binary commands: • What are the implications of asserting CMD while live data is being sent or received? • After sending serial data, is there a minimum time delay before CMD can be asserted? • Is a time delay required after CMD is de-asserted before payload data can be sent? • How to discern between live data and data received in response to a command?CMD (pin 5) must be asserted in order to send binary commands to the module. The CMD pin can be asserted to recognize binary commands anytime during the transmission or reception of data. The status of the CMD signal is only checked at the end of the stop bit as the byte is shifted into the serial port. The application does not allow control over when data is received, except by waiting for dead time between bursts of communication.If the command is sent in the middle of a stream of payload data to be transmitted, the command will essentially be executed in the order it is received. If the radio is continuously receiving data, the radio will wait for a break in the received data before executing the command. The CTS signal will frame the response coming from the binary command request [Figure 2-012].A minimum time delay of 100 µs (after the stop bit of the command byte has been sent) must be observed before pin 5 can be de-asserted. The command executes after all parameters associated with the command have been sent. If all parameters are not received within 0.5 seconds, the module aborts the command and returns to Idle Mode.Note: When parameters are sent, they are two bytes long with the least significant byte sent first. Binary commands that return one parameter byte must be written with two parameter bytes. Refer to “Programming Examples” section [pXX] for a binary programming example.Commands can be queried for their current value by sending the command logically ORed (bit-wise) with the value 0x80 (hexadecimal) with CMD asserted. When the binary value is sent (with no parameters), the current value of the command parameter is sent back through the DO pin.Figure2‐012.BinaryCommandWritethenReadSignal#4isCMD(pin16)Signal#1istheDIN(pin3)signal totheradioSignal#2istheDOUT(pin2)signal fromtheradioSignal#3isCTS(pin12)In this graph, a value was written to a register and then read out to verify it. While not in the middle of other received data, note that the CTS signal outlines the data response out of the module.IMPORTANT: For the XBee-PRO Module to recognize a binary command, the RT (DI2 Configuration) parameter must be set to one. If binary programming is not enabled (RT ? 1), the module will not rec-ognize that the CMD pin is asserted and therefore will not recognize the data as binary commands.](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-18.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 20PreliminaryDraft3.2. Command Reference TableTable3‐01. ATCommands(TheRFModuleexpectsnumericalvaluesinhexadecimal.ʺdʺdenotesdecimalequivalent.)).NOTE: AT Commands issued without a parameter value will return the currently stored parameter.AT CommandBinaryCommand AT Command Name Range Command Category # Bytes ReturnedFactoryDefaultAT 0x05 (5d) Guard Time After 0x02 – 0xFFFF [x 100 msec] Command Mode Options 2 0x0A (10d)BD 0x15 (21d) Interface Data RateStandard baud rates: 0 – 6Non-standard baud rates:0x7D – 0xFFFFSerial Interfacing 2 0x03 9600bpsBT 0x04 (4d) Guard Time Before 2 – 0xFFFF [x 100 msec] Command Mode Options 2 0x0A (10d)CC 0x13 (19d) Command Sequence Character 0x20 – 0x7F Command Mode Options 1 0x2B (“+”)CD 0x28 (40d) DO3 Configuration 0 - 4 Serial Interfacing 1 0CN 0x09 (9d) Exit AT Command Mode - Command Mode Options - -CS 0x1F (31d) DO2 Configuration 0 – 4 Serial Interfacing 1 0CT 0x06 (6d) Command Mode Timeout 0x02 – 0xFFFF [x 100 msec] Command Mode Options 2 0xC8 (200d)DB RSSI level in dBm of the most recent packet 0 - 0x70 [read-only] Diagnostics 1DT 0x00 (0d) Destination Address 0 – 0xFFFF Networking 2 0E0 0x0A (10d) Echo Off - Command Mode Options - -E1 0x0B (11d) Echo On - Command Mode Options - -ER 0x0F (15d) Receive Error Count 0 – 0xFFFF Diagnostics 2 0FH 0x0D (13d) Force Wake-up Initializer - Sleep (Low Power) - -FL 0x07 (7d) Software Flow Control 0 – 1 Serial Interfacing 1 0FR Forces the module to Reset (Special)FT 0x24 (36d) Flow Control Threshold 0 – (DI buffer – 0x11) [bytes] Serial Interfacing 2 variesGD 0x10 (16d) Receive Good Count 0 – 0xFFFF Diagnostics 2 0HP 0x11 (17d) Hopping Channel 0 – 6 Networking 1 0HT 0x03 (3d) Time before Wake-up Initializer 0 – 0xFFFF [x 100 msec] Sleep (Low Power) 2 0xFFFFID 0x27 (39d) Module VID User settable: 0x10 - 0x7FFFRead-only: 0x8000 – 0xFFFF Networking 2 -LH 0x0C (12d) Wake-up Initializer Timer 0 – 0xFF [x 100 msec] Sleep (Low Power) 1 1MK 0x12 (18d) Address Mask 0 – 0xFFFF Networking 2 0xFFFF NB 0x23 (35d) Parity 0 – 4 Serial Interfacing 1 0PC 0x1E (30d) Power-up Mode 0 – 1 Command Mode Options 1 0PW 0x1D (29d) Pin Wake-up 0 – 1 Sleep (Low Power) 1 0RE 0x0E (14d) Restore Defaults - (Special) - -RN 0x19 (25d) Delay Slots 0 – 0xFF [slots] Networking 1 0RO 0x21 (33d) Packetization Timeout 0 – 0xFFFF [x 200 µsec] Serial Interfacing 2 0RP 0x22 (34d) RSSI PWM Timer 0 - 0x7F [x 100 msec] Diagnostics 1 0RR 0x18 (24d) Retries 0 – 0xFF Networking 1 0RS 0x1C (28d) RSSI 0x06 – 0x36 [read-only] Diagnostics 1 -RT 0x16 (22d) DI2 Configuration 0 - 2 Serial Interfacing 1 0SB 0x36 (54d) Stop Bits 0 - 1 Serial Interfacing 1 0SH 0x25 (37d) Serial Number High 0 – 0xFFFF [read-only] Diagnostics 2 -SL 0x26 (38d) Serial Number Low 0 – 0xFFFF [read-only] Diagnostics 2 -SM 0x01 (1d) Sleep Mode 0, 1, 3 - 8 Sleep (Low Power) 1 0ST 0x02 (2d) Time before Sleep 0x10 – 0xFFFF [x 100 msec] Sleep (Low Power) 2 0x64 (100d)SY 0x17 (23d) Time before Initialization 0 – 0xFF [x 100 msec] Networking 1 0 (disabled)TR 0x1B (27d) Transmit Error Count 0 – 0xFFFF Diagnostics 2 0TT 0x1A (26d) Streaming Limit 0 – 0xFFFF [0 = disabled] Networking 2 0xFFFFVR 0x14 (20d) Firmware Version 0 - 0xFFFF [read-only] Diagnostics 2 -WR 0x08 (8d) Write - (Special) - -](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-20.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 21PreliminaryDraft3.3. Command Descriptions Commands in this section are listed alphabetically. Command categories are designated between the “< >” symbols that follow each command title. Modules expect numerical values in hexadecimal and those values are designated by a “0x” prefix.Modules operating within the same network should contain the same firmware version.AT (Guard Time After) CommandBD (Interface Data Rate) CommandCommand Summary DescriptionAT Command: ATAT <Command Mode Options> AT Command is used to set the time-of-silence that follows the command sequence character (CC Command). By default, AT Command Mode will activate after one second of silence. Refer to the AT Commands section [p] to view the default AT Command Mode Sequence.Binary Command: 0x05 (5 decimal)Parameter Range:0x02 – 0xFFFF [x 100 milliseconds]Number of bytes returned: 2Default Parameter Value: 0x0A (10 decimal)Related Commands: BT (Guard Time Before), CC (Command Sequence Character)Command Summary DescriptionAT Command: ATBD <Serial Interfacing> BD Command allows the user to adjust the UART interface data rate and thus modify the rate at which serial data is sent to the module. The new baud rate does not take effect until the CN (Exit AT Command Mode) Command is issued. The RF data rate is not affected by the BD Command.Although most applications will only require one of the seven standard baud rates, non-standard baud rates are also supported.Note: If the serial data rate is set to exceed the fixed RF data rate of the module, flow control may need to be implemented as described in the Pin Signals and Flow Control sections of this manual.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 X-CTU Software, non-standard interface data rates can only be set and read using the X-CTU ‘Terminal’ tab. Non-standard rates are not accessible through the ‘Modem Configuration’ tab.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.Binary Command: 0x15 (21 decimal)Parameter Range (Standard baud rates): 0 – 6(Non-standard baud rates): 0x7D – 0xFFFF (125d – 65535d)Parameter ValueBAUD (bps)Configuration0 12001 24002 48003 96004 192005 384006 57600Number of bytes returned: 2Default Parameter Value: Set to equal module’s factory-set RF data rate.](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-21.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 22PreliminaryDraftTable3‐02. ParameterSentvs.ParameterStoredBT (Guard Time Before) CommandCC (Command Sequence Character) CommandCD (DO3 Configuration) CommandBD Parameter Sent (HEX) Interface Data Rate (bps) BD Parameter Stored (HEX)0 1200 04 19,200 46 57600 612C 300 12BE100 57600 E883Command Summary DescriptionAT Command: ATBT <Command Mode Options> BT Command is used to set the DI pin silence time that must precede the command sequence character (CC Command) of the AT Command Mode Sequence. Refer to the AT Commands section [p] to view the default AT Command Mode Sequence.Binary Command: 0x04 (4 decimal)Parameter Range:2 – 0xFFFF [x 100 milliseconds]Default Parameter Value: 0x0A (10 decimal) Number of bytes returned: 2Related Commands: AT (Guard Time After), CC (Command Sequence Character)Command Summary DescriptionAT Command: ATCC <Command Mode Options> CC Command is used to set the ASCII character to be used between Guard Times of the AT Command Mode Sequence (BT+ CC + AT). The AT Command Mode Sequence activates AT Command Mode (from Idle Mode). Refer to the AT Commands section [p] to view the default AT Command Mode Sequence.Binary Command: 0x13 (19 decimal)Parameter Range: 0x20 – 0x7FDefault Parameter Value: 0x2B (ASCII “+” sign) Number of bytes returned: 1Related Commands: AT (Guard Time After), BT (Guard Time Before)DescriptionAT Command: ATCDBinary Command: 0x28 (40 decimal) <Command Mode Options> CD Command is used to define the behavior of the DO3/RX LED line.Parameter Range: 0 – 3Parameter Value Configuration0RX LED1Default high2Default low3 (reserved)4Assert only when packet addressed to module is sentDefault Parameter Value: 0Number of bytes returned: 1](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-22.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 23PreliminaryDraftCN (Exit AT Command Mode) CommandCS (DO2 Configuration) CommandCT (Command Mode Timeout) CommandDB (RSSI in dBm) CommandCommand Summary DescriptionAT Command: ATCN <Command Mode Options> CN Command is used to explicitly exit AT Command Mode.Binary Command: 0x09 (9 decimal)Command Summary DescriptionAT Command: ATCS <Serial Interfacing> CS Command is used to select the behavior of the DO2 pin signal. This output can provide RS-232 flow control, control the TX enable signal (for RS-485 or RS-422 operations), or set the default level for the I/O line passing function. By default, DO2 provides RS-232 CTS (Clear-to-Send) flow control.Binary Command: 0x1F (31 decimal)Parameter Range:0 – 4Parameter Value Configuration0RS-232 flow control1 RS-485 TX enable low2high3 RS-485 TX enable high4lowDefault Parameter Value: 0Number of bytes returned: 1Minimum Firmware Version Required: 4.27DCommand Summary DescriptionAT Command: ATCT <Command Mode Options> CT Command sets the amount of time before AT Command Mode terminates automatically. After a CT time of inactivity, the module exits AT Command Mode and returns to Idle Mode. AT Command Mode can also be exited manually using CN (Exit AT Command Mode) Command.Binary Command: 0x06 (6 decimal)Parameter Range:0x02 – 0xFFFF [x 100 milliseconds]Default Parameter Value: 0xC8 (200 decimal, 20 seconds)Number of bytes returned: 2Command Summary DescriptionAT Command: ATDB <Diagnostics> DB command returns the signal level of the last packet received in dBm. This reading is useful for determining range characteristics of the Modules under various conditions of noise and distance.Once the command is issued, the module will return the value in dBm. 0x32 (50d) = -50 dBm (strong signal), and 0x64 (100d) = -100 dBm (weak signal).Binary Command: Not availableParameter Range:00x00 to 0x70 [read-only]Number of bytes returned: returned: 1Related Commands: RS (RSSI Level)](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-23.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 28PreliminaryDraftHT (Time before Wake-up Initializer) CommandID (Modem VID) CommandCommand Summary DescriptionAT Command: ATHT <Sleep (Low Power)> If any modules within range are running in a “CyclicSleep” setting, a wake-up initializer must be used by the transmitting module for sleeping modules to remain awake [refer to the LH (“Wake-up InitializerTimer”) Command]. When a receiving module in Cyclic Sleep wakes, it must detect the wake-up initializer in order to remain awake andreceive data. The value of HT Parameter tells the transmitter, “After a period of inactivity (no transmitting or receiving) lasting HT amount of time, send a long wake-up initializer”. HT Parameter should be set to match the inactivity timeout [specified by ST (Time before Sleep) Command]used by the receiver(s). From the receiving module perspective, after HT time elapses and the inactivitytimeout [ST Command] is met, the receiver goes into cyclic sleep. In cyclic sleep, the receiver wakes once per sleep interval to check for a wakeup initializer. When a wake-up initializer is detected, the module will stay awake to receive data. The wake-up initializer must be longer than thecyclic sleep interval to ensure that sleeping modules detect incoming data. When HT time elapses, the transmitter then knows that it needs to send a long Wake-up Initializer for all receivers to be able to remain awake andreceive the next transmission. Matching HT to the time specified by ST on the receiving module guarantees that all receivers will detect the next transmission.Binary Command: 0x03 (3 decimal)Parameter Range:0 – 0xFFFF [x 100 milliseconds]Default Parameter Value: 0xFFFF (means that long wake-up initializer will not be sent)Number of bytes returned: 2Related Commands: LH (Wake-up Initializer Timer), SM (Sleep Mode), ST (Time before Sleep)Command Summary DescriptionAT Command: ATID <Networking> Set/Read the “Vendor Identification Number”. Only modemswith matching IDs can communicate with each other. Modules with nonmatchingVIDs will not receive unintended data transmission.Binary Command: 0x27 (39 decimal)Parameter Range (user-settable):0x10 - 0x7FFFF (Factory-set and read-only):0x8000 – 0xFFFFNumber of bytes returned: 2](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-28.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 29PreliminaryDraftLH (Wake-up Initializer Timer) CommandMK (Address Mask) CommandCommand Summary DescriptionAT Command: ATLH <Sleep (Low Power)> LH Command adjusts the duration of time for which the RF initializer is sent.When receiving modules are put into Cyclic Sleep Mode, they power-down after a period of inactivity [specified by ST (Time before Sleep) Command] and will periodically awaken and listenfor transmitted data. In order for the receiving modules to remain awake, they must detect~35ms of the wake-up initializer. LH Command must be used whenever a receiver is operating in Cyclic Sleep Mode. This lengthensthe Wake-up Initializer to a specific amount of time (in tenths of a second). The Wake-up Initializer Time must be longer than the cyclic sleep time that is determined by SM (Sleep Mode)Command. If the wake-up initializer time were less than the Cyclic Sleep interval, the connection would be at risk of missing the wake-up initializer transmission. Refer to Figures 3.1 & 3.2 of the SM Command description to view diagrams of correct and incorrect configurations. The images help visualize the importance that the value of LH be greater than the value of SM.Binary Command: 0x0C (12 decimal)Parameter Range:0 – 0xFF [x 100 milliseconds]Default Parameter Value: 1Number of bytes returned: 1Related Commands: HT (Time before Wake-up Initializer), SM (Sleep Mode), ST (Time before Sleep)Command Summary DescriptionAT Command: ATMK <Networking> MK Command is used to set/read the Address Mask.All data packets contain the Destination Address of the transmitting module.When an RF data packet is received, the transmitter’s Destination Address is logically “ANDed” (bitwise) with the Address Mask of the receiver. The resulting value must match the Destination Address or theAddress Mask of the receiver for the packet to be received and sent out themodule’s DO serial port. If the “ANDed” value does not match either theDestination Address or the Address Mask of the receiver, the packet is discarded. (All “0” values are treated as “irrelevant” values and are ignored.)Binary Command: 0x12 (18 decimal)Parameter Range:0 – 0xFFFFDefault Parameter Value: 0xFFFF (Destination address (DT parameter) of the transmitting module must exactly match the destination address of the receiving module.)Number of bytes returned: 2Related Commands: DT (Destination Address), HP (Hopping Channel), ID (Module VID), MY (Source Address)](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-29.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 31PreliminaryDraftPW (Pin Wake-up) CommandRE (Restore Defaults) CommandRN (Delay Slots) CommandCommand Summary DescriptionAT Command: ATPW <Sleep (Low Power)> Under normal operation, a module in Cyclic Sleep Mode cycles from an active state to a low-power state at regular intervals until data is ready to be received. If the PW Parameter is set to 1, SLEEP (pin 2) can be used to wake the module from Cyclic Sleep. If the SLEEP pinis de-asserted (low), the module will be fully operational and will not go into Cyclic Sleep. Once SLEEP is asserted, the module will remain active for the period of time specified by ST (Time before Sleep) Command, and will return to Cyclic Sleep Mode (if no data is ready to be transmitted). PWCommand is only valid if Cyclic Sleep has been enabled.Binary Command: 0x1D (29 decimal)Parameter Range:0 – 1Parameter Value Configuration0 Disabled1EnabledDefault Parameter Value: 0Number of bytes returned: 1Related Commands: SM (Sleep Mode), ST (Time before Sleep)Minimum Firmware Version Required: 4.22Command Summary DescriptionAT Command: ATRE <Diagnostics> RE Command restores all configurable parameters to factorydefault settings. However, RE Command will not write the default values tonon-volatile (persistent) memory. Unless the WR (Write) Command isissued after the RE command, the default settings will not be saved in theevent of module reset or power-down.Binary Command: 0x0E (14 decimal)Command Summary DescriptionAT Command: ATRN <Networking> RN Command is only applicable if retries have beenenabled [RR (Retries) Command], or if forced delays will be inserted intoa transmission [refer to TT (Streaming Limit) Command]. RN Command isused to adjust the time delay that the transmitter inserts before attemptingto resend a packet. If the transmitter fails to receive an acknowledgementafter sending a packet, it will insert a random number of delay slots(ranging from 0 to (RN minus 1)) before attempting to resend the packet.Each delay slot lasts for a period of 38ms.If two modules attempted to transmit at the same time, the random timedelay after packet failure would allow one of the two modules to transmitthe packet successfully, while the other would wait until the channelopens up to begin transmission.Binary Command: 0x19 (25 decimal)Parameter Range:0 – 0xFF [slots]Default Parameter Value: 0 (no delay slots inserted) Number of bytes returned: 1](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-31.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 32PreliminaryDraftRO (Packetization Timeout) Command.RP (RSSI PWM Timer) CommandTab le3‐03. PWMChartA 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. A parameter value of 0xFF permanently enables the PWM output and it will always reflect the value of the last received RF packet.PWM output shares the Config input pin. When the module is powered, the Config pin will be an input. During the power-up sequence, the Config pin will be read to determine whether the module is going into AT Command Mode. After this, if RP parameter is a non-zero value, the Config pin will be configured as an output and set low until the first RF packet is received. With a non-zero RP parameter, the Config pin will be an input for RP ms after power up. Command Summary DescriptionAT Command: ATRO <Serial Interfacing> RO Command is used to specify/read the time ofsilence (no bytes received) after which transmission begins. After a serialbyte is received and if no other byte is received before the RO timeout,the transmission will start.Binary Command: 0x21 (33 decimal)Parameter Range:0 – 0xFFFF [x 200 µs]Default Parameter Value: 0 Number of bytes returned: 2Minimum Firmware Version Required: 4.2AACommand Summary DescriptionAT Command: ATRP <Diagnostics> RP Command is used to enable a PWM (“Pulse Width Modulation”)output on the Config pin which is calibrated to show the level thereceived RF signal is above the sensitivity level of the module. The PWMpulses vary from zero to 95 percent. Zero percent means the received RFsignal is at or below the published sensitivity level of the module. The followingtable shows levels above sensitivity and PWM values.The total period of the PWM output is 8.32 ms. There are 40 steps in thePWM output and therefore the minimum step size is 0.208 ms.Binary Command: 0x22 (34 decimal)Parameter Range:0 - 0x7F[x 100 milliseconds]Default Parameter Value: 0 (disabled) Number of bytes returned: 1dBm above Sensitivity PWM percentage(high period / total period)10 47.5 %20 62.5 %30 77.5 %](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-32.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 33PreliminaryDraftRR (Retries) CommandRS (RSSI) CommandCommand Summary DescriptionAT Command: ATRR Networking> RR Command specifies the number of retries that can be sentfor a given RF packet. Once RR Command is enabled (set to a non-zerovalue), RF packet acknowledgements and retries are enabled. After transmittinga packet, the transmitter will wait to receive an acknowledgementfrom a receiver. If the acknowledgement is not received in the period oftime specified by the RN (Delay Slots) Command, the transmitter will transmitthe original packet again. The packet will be transmitted repeatedlyuntil an acknowledgement is received or until the packet has been sent RRtimes.Note: For retries to work correctly, all modules in the system must haveretries enabled.Binary Command: 0x18 (24 decimal)Parameter Range:0 – 0xFFDefault Parameter Value: 0 (disabled)Number of bytes returned: 1Command Summary DescriptionAT Command: ATRS <Diagnostics> RS Command returns the signal level of the last packetreceived. This reading is useful for determining range characteristics of themodules under various conditions of noise and distance.Once the command is issued, the module will return a value between 0x6and 0x36 where 0x36 represents a very strong signal level and 0x4 indicatesa low signal level.Binary Command: 0x1C (28 decimal)Parameter Range: 0x06 – 0x36 [read-only]Number of bytes returned: 1](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-33.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 34PreliminaryDraftRT (DI2 Configuration) CommandSB (Stop Bits) CommandSH (Serial Number High) CommandSL (Serial Number Low) CommandCommand Summary DescriptionAT Command: ATRT <Serial Interfacing> RT command is used to dictate the behavior of theDI2/RTS/CMD line. RT Command must be issued to enable RTS flow controlor binary programming.Binary Command: 0x16 (22 decimal)Parameter Range:0 – 2Parameter Value Configuration0 disabled1 Enable Binary Programming2Enable Flow ControlDefault Parameter Value: 0Number of bytes returned: 1Command Summary DescriptionAT Command: ATSB SB Command is used to set/read the number of stop bits in the data packets.Binary Command: 0x36 (54 decimal)Parameter Range:0 – 1Parameter Value Configuration01 stop bits12 stop bitsDefault Parameter Value: 0Number of bytes returned: 1Command Summary DescriptionAT Command: ATSH <Diagnostics> Set/Read the serial number high word of the module.Binary Command: 0x25 (37 decimal)Parameter Range:0 – 0xFFFF [read-only]Number of bytes returned: 2Related Commands: SL (Serial Number Low)Command Summary DescriptionAT Command: ATSH <Diagnostics> Set/Read the serial number low word of the module.Binary Command: 0x26 (38 decimal)Parameter Range:0 – 0xFFFF [read-only]Number of bytes returned: 2Related Commands: SH (Serial Number High)](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-34.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 35PreliminaryDraftSM (Sleep Mode) CommandST (Time before Sleep) CommandCommand Summary DescriptionAT Command: ATSM <Sleep Mode (Low Power)> SM Command is used to adjust Sleep Mode settings. By default, Sleep Mode is disabled and the module remains continually active. SM Command allows the module to run in a lower-powerstate and be configured in one of eight settings. Cyclic Sleep settings wake the module after the amount of time designatedby SM Command. If the module detects a wake-up initializer during the time it is awake, it will synchronize with the transmitter and start receiving data after the wake-up initializer runs its duration. Otherwise, itreturns to Sleep Mode and continue to cycle in and out of inactivity until the Wake-up Initializer is detected. If a Cyclic Sleep setting is chosen, the ST, LH and HT parameters must also be set as described in the “SleepMode” section of this manual.Binary Command: 0x01Parameter Range:0,1 3-8Parameter Value Configuration0 Disabled1Pin Sleep3Cyclic 0.5 second sleep (Module wakes every 0.5 seconds)4 Cyclic 1.0 second sleep5 Cyclic 2.0 second sleep6 Cyclic 4.0 second sleep7 Cyclic 8.0 second sleep8 Cyclic 16.0 second sleepDefault Parameter Value: 0Number of bytes returned: 1Related Commands: For Pin Sleep – PC (Power-up Mode), PW (Pin Wake-up) For Serial Port Sleep – ST (Time before Sleep)For Cyclic Sleep – ST (Time before Sleep), LH (Wake-up Initializer Timer), HT (Time Before Wake-up Initializer), PW (Pin Wake-up)Command Summary DescriptionAT Command: ATST <Sleep Mode (Low Power)> ST Command sets the period of time (intenths of seconds) in which the module remains inactive before enteringinto Sleep Mode. For example, if the ST Parameter is set to 0x64 (100decimal), the module will enter into Sleep mode after 10 seconds of inactivity(no transmitting or receiving). This command can only be used ifCyclic Sleep or Serial Port Sleep Mode settings have been selected usingSM (Sleep Mode) Command.Binary Command: 0x02Parameter Range:0x10 – 0xFFFF [x 100 milliseconds]Default Parameter Value: 0x64 (100 decimal)Number of bytes returned: 2Related Commands: SM (Sleep Mode), LH (Wake-up Initializer Timer), HT (Time before Wake-up Initializer)](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-35.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 36PreliminaryDraftSY (Time before Initialization) CommandTR (Transmit Error Count) CommandCommand Summary DescriptionAT Command: ATSY <Networking> SY Command keeps a communication channel open as long as module transmits or receives before the active connection expires. It can be used to reduce latency in a query/response sequence and should be set 100 ms longer than the delay between transmissions. This command allows multiple Modules to share a hopping channelfor a given amount of time after receiving data. By default, all packets include an RF initializer that contains channel information used to synchronize any listening receivers to the transmitter’s hopping pattern. Once a new module comes within range, it is able to instantly synchronize to thetransmitter and start receiving data. If no new modules are introduced into the system, the synchronization information becomes redundant once moduleshave become synchronized.SY Command allows the modules to remove this information from the RF Initializer after the initial synchronization. For example, changing the SY Parameter to 0x14 (20 decimal) allows all modules to remain in sync for 2seconds after the last data packet was received. Synchronization information is not re-sent unless transmission stops for more than 2 seconds. This command allows significant savings in packet transmission time.Warning: Not recommended for use in an interference-prone environment. Interference can break up the session and the communications channel will not be available again until SY time expires. With SY set to zero, the channel session is opened and closed with each transmission - resulting in a more robust link with more latency.Binary Command: 0x17 (23 decimal)Parameter Range:0 – 0xFF[x 100 milliseconds]Default Parameter Value: 0 (Disabled - channel initialization information is sent with each RF packet.)Number of bytes returned: 1Command Summary DescriptionAT Command: ATTR <Diagnostics> TR Command records the number of retransmit failures.This number is incremented each time a packet is not acknowledged withinthe number of retransmits specified by the RR (Retries) Command. Ittherefore counts the number of packets that were not successfully receivedand have been dropped.The TR Parameter is not non-volatile and will therefore be reset to zeroeach time the module is reset.Binary Command: 0x1B (27 decimal)Parameter Range:0 – 0xFFFFDefault Parameter Value: 0 Number of bytes returned: 2Related Commands: RR (Retries)](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-36.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 33PreliminaryDraftAppendixA:AgencyCertificationsFCC (United States) CertificationThe XBee-PRO™ XSC OEM 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.In order to operate under Digi’s FCC Certification, OEMs/integrators must comply with the following regulations:Labeling RequirementsWARNING: 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 text shown in the figure below.FigureA‐01. RequiredFCCLabelforOEMproductscontainingtheXBee‐PRO™XSCOEMRFModuleFCC NoticesIMPORTANT: The XBee-PRO™ XSC 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 Digi 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.Limited Modular ApprovalThis is an RF module approved for Limited Modular use operating as a mobile transmitting device with respect to section 2.1091 and is limited to OEM installation for Mobile and Fixed applications only. During final installation, end-users are prohibited from access to any programming parameters. Professional installation adjustment is required for setting module power and antenna gain to meet EIRP compliance for high gain antenna(s).1. The system ntegrator must ensure that the text provided with this device [Figure A-01] is placed on the outside of the final product and within the final product operation manual.2. The XBee-PRO™ XSC OEM RF Module may only be used with antennas that have been tested and approved for use with this module [refer to to Table A-1.Contains FCC ID: MCQ-XBEEXSCThe enclosed device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (i.) this device may not cause harmful interference and (ii.) this device must accept any inter-ference received, including interference that may cause undesired operation.](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-38.png)
![XBee‐PRO™XSCOEMRFModules©2008DigiInternational,Inc. 40PreliminaryDraftContact DigiFor the best in wireless data solutions and support, please use the following resources:Office hours are 8:00 am - 5:00 pm [U.S. Mountain Time]Technical Support: Phone. (866) 765-9885 toll-free U.S.A. & Canada (801) 765-9885 WorldwideLive Chat. www.digi.com E-Mail. support @digi.com](https://usermanual.wiki/Digi/XBEEXSC.User-Manual/User-Guide-907800-Page-45.png)