HORNER HE800WCM802 Owner's manual

Supplement for
HE800WCM802 and HE800WCM900
HE-WCM802* and HE-WCM900*
(* Denotes Plastic Models)
SmartStack
Wireless Communication
OEM RF Modem
20 June 2005 MAN0789-01

PAGE220JUN2005WCM802/900

WCM802/90020JUN2005PAGE3
PREFACE
This manual explains how to use the SmartStack Wireless Communication OEM RF Modem
(HE800WCM802/WCM900).
Copyright (C) 2005 Horner APG, LLC., 640 North Sherman Drive Indianapolis, Indiana 46201. All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated
into any language or computer language, in any form by any means, electronic, mechanical, magnetic, optical,
chemical, manual or otherwise, without the prior agreement and written permission of Horner APG, Inc.
Copyrights of part of this manual belong to MaxStream, Inc.
All software described in this document or media is also copyrighted material subject to the terms and conditions
of the Horner Software License Agreement.
Information in this document is subject to change without notice and does not represent a commitment on the
part of Horner APG.
SmartStack, SmartStix and CsCAN are trademarks of Horner APG.
XStream is a registered trademark of MaxStream, Inc.
For user manual updates and assistance, contact Technical Support:
North America:
[phone]
www.heapg.com
Europe:
(+) 353-21-4321-266
www.horner-apg.com

PAGE420JUN2005WCM802/900
LIMITED WARRANTY AND LIMITATION OF LIABILITY
Horner APG,LLC. ("HE-APG") warrants to the original purchaser that the WCM802 / WCM900 module manufactured by HE-
APG is free from defects in material and workmanship under normal use and service. The obligation of HE-APG under this
warranty shall be limited to the repair or exchange of any part or parts which may prove defective under normal use and
service within two (2) years from the date of manufacture or eighteen (18) months from the date of installation by the original
purchaser whichever occurs first, such defect to be disclosed to the satisfaction of HE-APG after examination by HE-APG of
the allegedly defective part or parts. THIS WARRANTY IS EXPRESSLY IN LIEU OF ALL OTHER WARRANTIES
EXPRESSED OR IMPLIED INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR USE AND OF
ALL OTHER OBLIGATIONS OR LIABILITIES AND HE-APG NEITHER ASSUMES, NOR AUTHORIZES ANY OTHER
PERSON TO ASSUME FOR HE-APG, ANY OTHER LIABILITY IN CONNECTION WITH THE SALE OF THIS WCM802 /
WCM900 module. THIS WARRANTY SHALL NOT APPLY TO THIS WCM802 / WCM900 module OR ANY PART
THEREOF WHICH HAS BEEN SUBJECT TO ACCIDENT, NEGLIGENCE, ALTERATION, ABUSE, OR MISUSE. HE-APG
MAKES NO WARRANTY WHATSOEVER IN RESPECT TO ACCESSORIES OR PARTS NOT SUPPLIED BY HE-APG. THE
TERM "ORIGINAL PURCHASER", AS USED IN THIS WARRANTY, SHALL BE DEEMED TO MEAN THAT PERSON FOR
WHOM THE WCM802 / WCM900 module IS ORIGINALLY INSTALLED. THIS WARRANTY SHALL APPLY ONLY WITHIN
THE BOUNDARIES OF THE CONTINENTAL UNITED STATES.
In no event, whether as a result of breach of contract, warranty, tort (including negligence) or otherwise, shall HE-
APG or its suppliers be liable of any special, consequential, incidental or penal damages including, but not limited
to, loss of profit or revenues, loss of use of the products or any associated equipment, damage to associated
equipment, cost of capital, cost of substitute products, facilities, services or replacement power, down time costs,
or claims of original purchaser's customers for such damages.
To obtain warranty service, return the product to your distributor with a description of the problem, proof of
purchase, post paid, insured and in a suitable package.
ABOUT PROGRAMMING EXAMPLES
Any example programs and program segments in this manual or provided on accompanying diskettes are included
solely for illustrative purposes. Due to the many variables and requirements associated with any particular
installation, Horner APG cannot assume responsibility or liability for actual use based on the examples and
diagrams. It is the sole responsibility of the system designer utilizing the WCM802 / WCM900 module to
appropriately design the end system, to appropriately integrate the WCM802 / WCM900 module and to make
safety provisions for the end equipment as is usual and customary in industrial applications as defined in any
codes or standards which apply.
Note: The programming examples shown in this manual are for illustrative
purposes only. Proper machine operation is the sole responsibility of the
system integrator.

WCM802/90020JUN2005PAGE5
Contents
1. SmartStack Wireless Communication OEM RF Modems 7
Features 7
Worldwide Acceptance 7
Specifications 8
Pin Signals 9
Electrical Characteristics 10
Timing Specifications 10
Mechanical Drawings 11
2. RF Operation 12
Serial Communications 12
UART-Interfaced Data Flow 12
Flow Control 13
Modes of Operation 14
Idle Mode 14
Transmit Mode 14
Receive Mode 16
Sleep Mode 16
Command Mode 17
3. Advanced Programming 19
Programming the Module 19
AT Command Example 19
Binary Command Example 19
Command Descriptions (Short) 20
Command Descriptions (Long) 21
Appendix A: Agency Certifications 34
FCC Certification 34
OEM Labeling Requirements 35
Antenna Usage 35
FCC-Approved Antennas 36
European Compliance (2.4 GHz only) 37
OEM Labeling Requirements 37
Restrictions 37
Europe (2.4 GHz) Approved Antenna List 38
IC (Industry Canada) Certification 38
Appendix B: Additional Information 39
Technical Support 39

PAGE620JUN2005WCM802/900
NOTES

WCM802/90020JUN2005PAGE7
1.SmartStackWireless
CommunicationOEMRFModems
The Horner SmartStack Wireless Communication OEM RF Modems (HE800WCM802 / HE800WCM900 /HE-
WCM802* and HE-WCM900*) are drop-in wireless solutions that transfer a standard asynchronous serial data
stream over-the-air between devices. The Wireless Communication Modems (WCM802 / WCM900) stand out in the
RFd2d (radio frequency device-to-device) segment of the wireless market with their unique combination of high-
performance, ease-of-use and low price.
* HE- denotes plastic case version of the SmartStack module instead of the metal case version, which is indicated
by an HE800 prefix in the part number.
Note: The WCM802 and the WCM900 modules are not compatible with each other and can not be used to
communicate with one another.
Features
Long Range
HE800WCM900 / HE-WCM900 (900 MHz) Range:
• Indoor/Urban: up to 1500’ (450 m)
• Outdoor line-of-sight: up to 7 miles (11 km) w/ 2.1 dBm dipole
antenna
• Outdoor line-of-sight: up to 20 miles (32 km) w/ high gain antenna
HE800WCM802 / HE-WCM802 (2.4 GHz) Range:
• Indoor/Urban: up to 600’ (180 m)
• Outdoor line-of-sight: up to 3 miles (5 km) w/ 2.1 dBm dipole
antenna
• Outdoor line-of-sight: up to 10 miles (16 km) w/ high gain antenna
• Receiver Sensitivity: -110 dBm (900 MHz), -105 dBm (2.4 GHz)
Advanced Networking & Security
• True peer-to-peer (no “master” required), point-to-point, point-to-
multipoint, multidrop
• Retries and Acknowledgements
• 7 hopping channels, each with over 65,000 available network
addresses
• FHSS (Frequency Hopping Spread Spectrum)
Worldwide Acceptance
FCC Certified (USA) - Go to Appendix A for FCC Requirements. Systems that contain WCM802 /WCM900
Modules can inherit FCC Certification
ISM (Industrial, Scientific & Medical) frequency band
Manufactured under ISO 9001:2000 registered standards
WCM900 (900 MHz) OEM RF Modules are approved for use in US, Canada,
Australia, Israel (and more).
WCM802 (2.4 GHz) Modules add Europe (EU) and other approvals.
Easy-to-Use
5 VDC (± 0.25 V) power supply
Continuous RF data stream
up to 19.2 kbps
No configuration required
Advanced configurations available
through standard AT Commands
Portable
(small form factor easily designed into a
wide range of data radio systems)
Software-selectable serial interfacing
rates
MODBUS, CTS, RTS, DTR, DCD (& more)
I/O Support
Support for multiple data formats
(parity, start and stop bits, etc.)
XII™ Interference Immunity
Power-saving Sleep Modes

PAGE820JUN2005    WCM802/900
Specifications
Table1.1.WCM802/WCM900OEMRFModuleSpecifications
Specification WCM900 (900 MHz) OEM RF Module WCM802 (2.4 GHz) OEM RF Module
Performance
Indoor/Urban Range up to 1500’ (450 m) up to 600’ (180 m)
Outdoor line-of-sight Range Up to 7 miles (11 km) w/ dipole antenna
Up to 20 miles (32 km) w/ high-gain antenna Up to 3 miles (5 km) w/ dipole antenna Up to 10 miles (16 km) w/ high-gain antenna
Interface Data Rate Software selectable 1200 - 57600 bps
Throughput Data Rate 9,600 bps 19,200 bps 9,600 bps 19,200 bps
RF Data Rate 10,000 bps 20,000 bps 10,000 bps 20,000 bps
Transmit Power Output 100 mW (20 dBm) 100 mW (20 dBm) 50 mW (17 dBm) 50 mW (17 dBm)
Receiver Sensitivity -110 dBm -107 dBm -105 dBm -102 dBm
General
Frequency Range 902-928 MHz 2.4000-2.4835 GHz
Spread Spectrum Frequency Hopping, Wide band FM modulator
Network Topology Peer-to-Peer, Point-to-Multipoint, Point-to-Point, Multidrop
Channel Capacity 7 hop sequences share 25 frequencies
Serial Data Interface CMOS UART
Power Requirements
Supply Voltage 5 VDC (± 0.25 V) regulated
Transmit Current 150 mA
Receive Current 50 mA
Power Down Current < 26 µA
Physical Properties
Module Board Size 1.600” x 2.825” x 0.350” (4.06 cm x 6.86 cm x 0.89 cm)
Weight 0.8 oz (24 g)
Connector 11-pin & 4-pin, 0.1” spaced male Berg-type headers
Operating Temperature 0 to 70º C (commercial), -40 to 85º C (industrial)
Antenna
Integrated Wire (optional) ¼ wave monopole, 3” (7.62 cm) length, 1.9 dBi Gain
Connector (optional) Reverse-polarity SMA or MMCX
Impedance 50 ohms unbalanced
Certifications
FCC Part 15.247 OUR9XSTREAM OUR-24XSTREAM
Industry Canada (IC) 4214A-9XSTREAM 4214A 12008
Europe N/A ETSI, CE

WCM802/90020JUN2005PAGE9
Pin Signals
Figure1.1.WCM802/WCM900OEMRFModulePinNumbers(bottomview,pinsprotruding)
Table1.2.J1PinSignalDescriptions
(Low‐assertedsignalsdistinguishedwithahorizontallineoversignalname.)
Module
Pin Signal Name I/O When Active Function
(clear-to-send) flow control – When pin is driven low,
UART host is permitted to send serial data to the module.
Refer to the Serial Communications [p9] and CS Command
[p19] sections for more information.
1 DO2 / /
RS-485 Enable O* low
RS-485 Enable – To configure this pin to enable RS-485 (2-
wire or 4-wire) communications, refer to the Serial
Communications [p9] and CS Command [p19] sections.
2 DI3 / SLEEP I* high By default, DI3 pin is notused. To configure this pin to support Sleep Modes, refer to the Sleep Mode [p13],SM
Command [p27] and PW Command [p24] sections.
3 DO (data out) O* n/a Serial data exiting the module (to the UART host).Refer to
the Serial Communications [p9] section for more information.
4 DI (data in) I n/a Serial data entering the module (from UART host). Refer to
the Serial Communications [p9] section for more information.
(request-to-send) flow control – By default,this pin is not
used. To configure this pin to regulate the flow of serial data
exiting the module, refer to the Serial Communications [p9]
and RT Command [p26] sections.
5 DI2 / / CMD I** low
CMD –Refer to Binary Commands [p15] and RT Command
[p26] sections to enable binary command programming.
6 I* low Re-boot module.
7 DO3 / RX LED O high Pin is driven high during RF data reception; otherwise, the
pin is driven low. Refer to the CD Command [p19] to enable.
low - Pin pulses low during RF transmission.
8 / PWR O high PWR – Indicates power is on and module is not in Sleep
Mode.
9 I*** low Pin can be used as a backup method for entering Command Mode during power-up. Primary method is with “+++”. Refer
to the Command Mode [p14] section for more information.
10 VCC I - 5 VDC regulated (± 0.25)
11 GND - - Ground
*Modulehas10KΩinternalpull‐upresistor
**Modulehas10KΩinternalpull‐downresistor
*** Modulehas100KΩinternalpull‐upresistor
Note: When integrating the WCM802 / WCM900 Module with a Host PC Board, all lines that are not
used should be left disconnected (floating).
Table1.3.J2PinSignalDescriptions
Module
Pin Signal Name
1 reserved
2 GND
3 GND
4 GND
J2Pinsareusedprimarilyformechanicalstabilityandmaybeleftdisconnected.

PAGE1020JUN2005    WCM802/900
Electrical Characteristics
Figure1.2.SystemBlockDiagram
Basicwirelesslinkbetweenhosts
The data flow sequence is initiated when the first byte of data is received in the DI Buffer of the transmitting module
(WCM802 / WCM900 Module A). As long as WCM802 / WCM900 Module A is not already receiving RF data, data in the DI
Buffer is packetized, then transmitted over-the-air to WCM802 / WCM900 Module B.
Note: The WCM802 and the WCM900 modules are not compatible with each other and can not be used to
communicate with one another.
Timing Specifications
Figure1.3.TimingSpecifications(“A”and“B”refertoFigure1.2.)
Table1.4.ACCharacteristics(SYparameter=0,symbolscorrespondtoFigure1.2andFigure1.3.)
Symbol Description 19200 baud rate
(32 byte packet) 19200 timing (B=number of bytes) 9600 baud rate (32 byte packet) 9600 timing (B=number of bytes)
TTX Latency from the time data is
transmitted until received 54.0 ms
For 0 < B < 64,
T = 41.6 + (0.4 * B) ms
For B > 63,
T = 66.8 ms
72.0 ms
For 0 < B < 40,
T = 46.27 + (0.73 * B) ms
For B >= 39 bytes,
T = 74.80 ms
TTL Time that /PWR pin is
driven low 8.4 ms
For 0 < B < 14,
T = 3.24 + (0.4 * B) ms
For B > 13,
T = 8.48 ms
16.8 ms
For 0 < B < 14,
T = 6.50 + (0.8 * B) ms
For B > 13,
T = 16.80 ms
TRL Time that RX LED pin is
driven high 13.6 ms
For 0 < B < 65,
T = 0.79 + (0.408 * B)
For B > 64,
T = 26.9 ms
25.6 ms
For 0 < B < 37,
T = 1.63 + (0.794 * B)
For B > 36,
T = 30.2 ms
TST Channel Initialization Time 35.0 ms 35.0 ms 35.0 ms 35.0 ms

WCM802/90020JUN2005PAGE11
Table1.5.DCCharacteristics(Vcc=4.75–5.25VDC)
Symbol Parameter Condition Min Typical Max Units
VIL Input Low Voltage All inputsignals -0.5 0.3 * Vcc V
VIH Input High Voltage All except
pin 0.6 * Vcc Vcc + 0.5 V
VIH2 Input High Voltage pin * 0.9 * Vcc Vcc + 0.5 V
VOL Output Low Voltage IOL = 20 mA,
Vcc = 5V
0.7
0.5 V
VOH Output High Voltage IOH = -20 mA,
Vcc = 5V 4.0 2.0 V
IIL Input Leakage
Current I/O Pin Vcc = 5.5V, pin low (absolute value) 3 µA
IIH Input Leakage
Current I/O Pin Vcc = 5.5V, pin high (absolute value) 3 µA
IIL2 , , DO (Vcc – VI) / 10 ** mA
IIL3 CONFIG (Vcc – VI) / 47 ** mA
IIH2 (Vcc – VI) / 10 ** mA
*Resetpulsemustlastatleast250nanoseconds
**VI=theinputvoltageonthepin
Mechanical Drawings
Figure1.4.WCM802/WCM900ModuleMechanicalDrawings(shownwithRPSMAantennaconnector)

PAGE1220JUN2005    WCM802/900
2.RFOperation
Serial Communications
The WCM802 / WCM900 OEM RF Module interfaces to a host device through a CMOS-level
asynchronous serial port. Through its serial port, the module can communicate with any UART
voltage compatible device or through a level translator to any RS-232/485/422 device.
UART-Interfaced Data Flow
Devices that have a UART interface can connect directly through the pins of the WCM802 /
WCM900 Module as is shown in the figure below.
Figure2.1.SystemDataFlowDiagraminaUART‐interfacedenvironment
(Low‐assertedsignalsdistinguishedwithhorizontallineoversignalname.)
Serial Data
Data enters the prName Module through the DI pin (pin 4) as an asynchronous serial signal. The
signal should idle high when no data is being transmitted.
The UART performs tasks, such as timing and parity checking, that are needed for data
communications. Serial communication consists of two UARTs configured with compatible
parameters (baud rate, parity, start bits, stop bits, data bits) to have successful communication.
Each data packet consists of a start bit (low), 8 data bits (least significant bit first) and a stop bit
(high). The following figure illustrates the serial bit pattern of data passing through the module.
Figure2.2.UARTdatapacket0x1F(decimalnumber“31”)astransmittedthroughtheWCM802/WCM900
Module
ExampleDataFormatis8‐N‐1(bits–parity‐#ofstopbits)

WCM802/90020JUN2005PAGE13
Flow Control
Figure2.3.InternalDataFlowDiagram(Thefivemostcommonly‐usedpinsignalsshown.)
DI (Data In) Buffer and Flow Control
When serial data enters the WCM802 / WCM900 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 section [p11] and
command descriptions [17] 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 WCM802 / WCM900 OEM RF
Module).
How to eliminate the need for flow control:
1. 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.
2. 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:
1. 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.
2. 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 (Pin 4) 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 ( ). When the DI buffer is 17 bytes away from being full; by
default, the module de-asserts (high) to signal to the host device to stop sending data [refer
to FT (Flow Control Threshold) and CS (DO2 Configuration) Commands]. 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 Flow Control) Command. This option only works with ASCII data.
DO (Data Out) Buffer and Flow Control
When 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:
1. If the RF data rate is set higher than the interface data rate of the module, the module will
receive data from the transmitting module faster than it can send the data to the host.
2. If the host does not allow the module to transmit data out from the DO buffer because of
being held off by hardware or software flow control.
Hardware Flow Control ( ). If is enabled for flow control (RT Parameter = 2), data will
not be sent out the DO Buffer as long as (pin 5) 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.

PAGE1420JUN2005    WCM802/900
Modes of Operation
WCM802 / WCM900 OEM RF Modules operate in five modes.
Figure2.4.WCM802/WCM900ModesofOperation
Themodulecanonlybeinonemodeatatime.
Idle Mode
When not receiving or transmitting data, the module is in Idle Mode. The module uses the same
amount of power in Idle Mode as it does in Receive Mode.
The module shifts into the other modes of operation under the following conditions:
• Serial data is received in the DI Buffer (Transmit Mode)
• Valid RF data is received through the antenna (Receive Mode)
• Command Mode Sequence is issued (Command Mode)
• Sleep Mode condition is met (Sleep Mode)
After responding to any of the preceding conditions, the module automatically transitions back
into Idle Mode.
Transmit Mode
When the first byte of serial data is received from the UART in the DI buffer, the module attempts
to shift to Transmit Mode and initiate an RF connection with other modules.
Figure2.5.TransmissionofDataÆ
Once in Transmit Mode, the
module initializes a
communications channel. Channel
initialization is the process of
sending an RF initializer that
synchronizes receiving modules
with the transmitting module.
When streaming multiple RF
packets, the RF Initializer is only
sent in front of the first packet.
During channel initialization,
incoming serial data accumulates
in the DI buffer.
After the channel is initialized, data
in the DI buffer is grouped into packets (up to 64 bytes in each packet) and is transmitted. The
module continues to transmit data packets until the DI buffer is empty. Once transmission is
finished, the module returns to Idle Mode. This progression is shown in Figure 2.5.
As the transmitting module nears the end of the transmission, it inspects the DI buffer to see if
more data exists to be transmitted. This could be the case if more bytes arrived from the host
after the transmission began. If more data is pending, the transmitting module assembles a
subsequent packet for transmission.

WCM802/90020JUN2005PAGE15
RF Packet
Figure2.6.RFPacketComponents
* When streaming multiple RF packets, the RF Initializer is only sent in front of the first packet.
RF Initializer
An 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.
Header
The header contains network addressing information that filters incoming RF data. The receiving
module checks for matching a VID, Hopping Channel and Destination Address. Data that does not
pass through all three network filter layers is discarded.
Figure2.7.NetworkLayersContainedintheHeader
CRC (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].

PAGE1620JUN2005    WCM802/900
Receive Mode
If a module detects RF data while operating in Idle Mode, the module transitions into Receive
Mode to start receiving RF packets.
Figure2.8.ReceptionofRFDataÆ
After 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.
Sleep Mode
Sleep Modes enable the WCM802 / WCM900 Module to operate at minimal power consumption
when not in use. Three Sleep Mode options are available:
• Pin Sleep (Host Controlled)
• Serial Port Sleep (Wake on Serial Port activity)
• Cyclic Sleep (Wake on RF activity)
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:
1. The module is idle (no data transmission or reception) for a user-defined period of time [See
ST (Time before Sleep) Command].
2. SLEEP (pin 2) 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.
Table2.1.SummaryofSleepModeConfigurations
Sleep Mode
Setting Transition into Sleep Mode Transition out of Sleep Mode Related Commands Typical Power Consumption
Pin 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 even if Pin Sleep
is activated.
De-assert (low)
SLEEP (pin 2). SM 26 µA
Serial Port Sleep
(SM = 2)
Automatic transition to Sleep Mode occurs
after a user-defined period of inactivity (no
transmitting or receiving of data).The
period of activity is defined using the ST
(Time before Sleep) Command.
When serial byte is
received on the DI pin
(pin 4). SM, ST 1 mA
Cyclic 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, PW 76 µA when sleeping
FormoreinformationaboutSleepModes,refertotheindividualcommandslistedin“RelatedCommands”
columnofthetable.SMCommandisthebeststartingpointforimplementingSleepModeconfigurations.

WCM802/90020JUN2005PAGE17
Command Mode
To 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 programming the module:
• AT Commands
• Binary Commands
For modified parameter values to persist in the module registry, changes must be saved to non-
volatile memory using WR (Write) Command. Otherwise, parameters are restored to previously
saved values after the module is powered off and then on again.
AT Commands
To Enter AT Command Mode:
1. Send the 3-character command sequence “+++” and observe guard times before and after
the command characters. [See “Default AT Command Mode Sequence” below.] The
“Terminal” tab (or other serial communications software) of the RADIOSET Software can be
used to enter the sequence.
[OR]
2. Assert (low) the pin and either turn the power going to the module off and back on.
Default AT Command Mode Sequence (for transition to Command Mode):
• No characters sent for one second [see BT (Guard Time Before) Command]
• Input three plus characters (“+++”) within one second [see CC (Command Sequence
Character) Command.]
• No characters sent for one second [see AT (Guard Time After) Command.]
To Send AT Commands:
Send AT commands and parameters using the syntax shown below:
Figure2.9.SyntaxforsendingATCommands
NOTE: To read a parameter value stored in a register, leave the parameter field blank.
The preceding example would change the module Destination Address to “1F”. To store the new
value to non-volatile (long term) memory, subsequently send the Write (ATWR) Command.
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:
1. Send ATCN (Exit Command Mode) Command.
[OR]
2. If no valid AT Commands are received within the time specified by CT (Command Mode
Timeout) Command, the Module automatically returns to Idle Mode.
For an example that illustrates programming the module using AT Commands, refer to the
“Advanced Programming” chapter.

PAGE1820JUN2005    WCM802/900
Binary Commands
Sending and receiving register values using binary commands is the fastest way to change the
operating parameters of the module. Binary commands are used most often to sample the signal
strength (RS command) and/or error counts or change module address and channels for polling
systems when a quick response is necessary. Since the sending and receiving register values
takes place through the same serial data path as 'live' data (received RF payload), interference
between the two can be a concern.
Common questions about using binary command mode:
• What are the implications of asserting CMD in any of the various states while live data is
being sent or received?
• Specifically, is there a minimum time delay after serial data is sent before which we can
assert CMD and send a command?
• Is a delay required after CMD is de-asserted before we can send normal data?
• How can we know if data being received is the response from a command or live data?
Answers: The CMD line can be asserted to send a command to the radio anytime during
transmission or reception of data. Note that 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. 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 signal will frame the response coming
from the binary command request (see graphic below).
CMD (pin 5) must be asserted in order to send binary commands to an WCM802 / WCM900
Module. CMD can be asserted to recognize commands anytime during transmission or reception
of data. 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 always two bytes long with the least significant byte sent first.
Commands can be queried for their current value by sending the command logically ORed with
the value 0x80 (hexadecimal) with CMD asserted. When the binary value is sent (with no
parameters), the current value of the command parameter is sent back through the DO pin.
Figure2.10.BinaryCommandWritethenRead
Signal#4isCMD(pin5)
Signal#1istheDIN(pin4)signal
totheradio
Signal#2istheDOUT(pin3)signal
fromtheradio
Signal#3is(pin1)
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 signal outlines the data response out of the module.
IMPORTANT: For the WCM802 / WCM900 Module to recognize a binary command, RT (DI2
Configuration) Command must be issued. If binary programming is not enabled
(RT ≠1), the module will not recognize that the CMD pin (Pin 5) is asserted and
therefore will not recognize the data as binary commands.

WCM802/90020JUN2005PAGE19
3.AdvancedProgramming
Programming the Module
For information about entering and exiting AT and Binary Command Modes, refer to the
Command Mode section [p14].
AT Command Example
To Send AT Commands (Using the Terminal tab of the RadioSet Software)
Example: Both of the following examples change the module’s destination address to 0x1A0D and
save the new address to non-volatile memory. <CR> stands for “Carriage Return”.
Method1(Onelinepercommand)
Send AT Command System Response
+++ OK <CR> (Enter into Command Mode)
ATDT <Enter> 0 <CR> (Read current destination address)
ATDT1A0D <Enter> OK <CR> (Change destination address)
ATWR <Enter> OK <CR> (Write to non-volatile memory)
ATCN <Enter> OK <CR> (Exit Command Mode)
Method 2 (Multiple commands on one line)
Send AT Command System Response
+++ OK <CR> (Enter into Command Mode)
ATDT <Enter> 0 <CR> (Read current destination address)
ATDT1A0D,WR,CN <Enter> OK <CR> (Execute commands)
Note: In order to use a host PC and the RADIOSET Software Terminal tab to send data to the module,
the PC com port settings must match the following module parameter values: baud, parity & stop
bits.
Use the “PC Settings” tab to configure PC com port settings to match module parameter values.
[Refer to BD (Baud Rate) and NB (Parity) Commands for module parameter values.]
Binary Command Example
To Send Binary Commands:
Example: Use binary commands to change the WCM802 / WCM900 Module’s destination address
to 0x1A0D and save the new address to non-volatile memory.
1. RT Command must be set to “1” in AT Command Mode to enable binary programming.
2. Assert CMD (Pin 5 is driven high). (Enter Binary Command Mode)
3. Send Bytes: 00 (Send DT (Destination Address) Command)
0D (Least significant byte of parameter bytes)
1A (Most significant byte of parameter bytes)
08 (Send WR (Write) Command)
4. De-assert CMD (Pin 5 is driven low) (Exit Binary Command Mode)
Note: (pin 1) is de-asserted high when commands are being executed. Hardware flow control
must be disabled as will hold off parameter bytes.
HornerprovidesRADIOSET
Softwareforprogramming
themoduleusingAT
Commands.
Toinstall,double‐clickthe
“RADIOSET.exe”file,then
followthepromptsofthe
installationscreens.

PAGE2020JUN2005    WCM802/900
Command Descriptions (Short)
Table3.1.WCM802/WCM900Commands
(TheWCM802/WCM900Moduleexpectsnumericalvaluesinhexadecimal.“d”denotesdecimalequivalent.)
AT
Command Binary Command AT Command Name Range Command Category # Bytes Returned Factory Default
AT 0x05 (5d) Guard Time After 0x02 – 0xFFFF [x 100 msec] Command Mode Options 2 0x0A (10d)
BD 0x15 (21d) Baud Rate 0 – 6 Serial Interfacing 1 RF data rate
BT 0x04 (4d) Guard Time Before 0 – 0xFFFF [x 100 msec] Command Mode Options 2 0x0A (10d)
CC 0x13 (19d) Command Sequence Character 0x20 – 0x7F Command Mode Options 1 0x2B (“+”)
CD v 4.2B* 0x28 (40d) DO3 Configuration 0 - 3 Serial Interfacing 1 0
CN 0x09 (9d) Exit AT Command Mode - Command Mode Options - -
CS v 4.27D* 0x1F (31d) DO2 Configuration 0 – 4 Serial Interfacing 1 0
CT 0x06 (6d) Command Mode Timeout 0x02 – 0xFFFF [x 100 msec] Command Mode Options 2 0xC8 (200d)
DT 0x00 (0d) Destination Address 0 – 0xFFFF Networking 2 0
E0 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 0
FH 0x0D (13d) Force Wake-up Initializer - Sleep (Low Power) - -
FL 0x07 (7d) Software Flow Control 0 – 1 Serial Interfacing 1 0
FT v 4.27B* 0x24 (36d) Flow Control Threshold 0 – 0xFF [bytes] Serial Interfacing 2 varies
GD 0x10 (16d) Receive Good Count 0 – 0xFFFF Diagnostics 2 0
HP 0x11 (17d) Hopping Channel 0 – 6 Networking 1 0
HT 0x03 (3d) Time before Wake-up Initializer 0 – 0xFFFF [x 100 msec] Sleep (Low Power) 2 0xFFFF
ID v 4.2B* 0x27 (39d) Module VID User settable: 0x10 - 0x7FFF
Read-only: 0x8000 – 0xFFFF Networking 2 -
LH 0x0C (12d) Wake-up Initializer Timer 0 – 0xFF [x 100 msec] Sleep (Low Power) 1 1
MK 0x12 (18d) Address Mask 0 – 0xFFFF Networking 2 0xFFFF
NB v 4.27B* 0x23 (35d) Parity 0 – 4 Serial Interfacing 1 0
PC v 4.22* 0x1E (30d) Power-up Mode 0 – 1 Command Mode Options 1 0
PW v 4.22* 0x1D (29d) Pin Wake-up 0 – 1 Sleep (Low Power) 1 0
RE 0x0E (14d) Restore Defaults - (Special) - -
RN v 4.22* 0x19 (25d) Delay Slots 0 – 0xFF[ slots] Networking 1 0
RO v 4.2AA* 0x21 (33d) Packetization Timeout 0 – 0xFFFF [x 200 µsec] Serial Interfacing 2 0
RP v 4.2AA* 0x22 (34d) RSSI PWM Timer 0 - 0x7F [x 100 msec] Diagnostics 1 0
RR v 4.22* 0x18 (24d) Retries 0 – 0xFF Networking 1 0
RS v 4.22* 0x1C (28d) RSSI 0x06 – 0x36 [Read-only] Diagnostics 1 -
RT 0x16 (22d) DI2 Configuration 0 - 2 Serial Interfacing 1 0
SV v 4.2B* 0x36 (54d) Stop Bits 0 - 1 Serial Interfacing 1 0
SH v 4.27C* 0x25 (37d) Serial Number High 0 – 0xFFFF [Read-only] Diagnostics 2 -
SL v 4.27C* 0x26 (38d) Serial Number Low 0 – 0xFFFF [Read-only] Diagnostics 2 -
SM 0x01 (1d) Sleep Mode 0 – 8 Sleep (Low Power) 1 0
ST 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 v 4.22* 0x1B (27d) Transmit Error Count 0 – 0xFFFF Diagnostics 2 0
TT v 4.22* 0x1A (26d) Streaming Limit 0 – 0xFFFF [0 = disabled] Networking 2 0xFFFF
VR 0x14 (20d) Firmware Version 0 x 0xFFFF [Read-only] Diagnostics 2 -
WR 0x08 (8d) Write - (Special) - -
*Firmwareversioninwhichcommandandparameteroptionswerefirstsupported.