SmartScan - AEI RF IdentificationThis section lists the headings of this guide in sequential order with their page references. ... or American Trucking Association (ATA). These formats

EUD-2011276-00

SmartScan Reader and Multiplexer

Reference Guide

3 October 2011

© 2011 Southern Technologies Corporation (STC). All rights reserved. Printed in the USA.

Because products evolve and system configurations change, this manual may not be an exact representation of the products and systems that you are using.

STC assumes no responsibility for errors or omissions in this document. Nor does STC

make any commitment to update the information contained herein.

Product and company names mentioned herein are trademarks or registered trademarks of their respective owners.

CAUTION Contact with electrically active parts could result in sparks, burns, and electric shock.

Because of this, you should avoid all electrical hazards when installing, wiring, operating, and maintaining the SmartScan system. Failure to do so could

result in damage to the equipment or serious injury to you.

STC's web site is www.southern-tech.com

their email address is [email protected]

their fax number is 423-499-0045

their phone number is 423-892-3029

EUD-2011276-00, SmartScan Reader and Multiplexer Reference Guide, 3 October 2011 3

Contents This section lists the headings of this guide in sequential order with their page references.

Contents ....................................................................................................................................3 Chapter 1 — Introduction.......................................................................................................5

1.1 Purpose of This Guide ..................................................................................................5 1.2 Key Points.....................................................................................................................5 1.3 AEI Tags .......................................................................................................................6 1.4 SmartScan Product Line ...............................................................................................8 1.5 SmartScan Multiplexer and Readers ............................................................................8 1.6 Disclaimers ...................................................................................................................9 1.7 How to Comment on This Guide.................................................................................10 1.8 How to Order More Copies of This Guide...................................................................10 1.9 Standard Warranty......................................................................................................10

Chapter 2 — 2200-507 Reader .............................................................................................11 2.1 Overview .....................................................................................................................11 2.2 Technical Specifications .............................................................................................13 2.3 Dimensions .................................................................................................................14 2.4 Commands..................................................................................................................15

2.4.1 Data Mode..........................................................................................................15 2.4.2 Command Mode.................................................................................................15 2.4.3 Sending Commands to the Reader....................................................................16

2.5 Communication Port ...................................................................................................17 2.6 Flow Control ................................................................................................................17 2.7 Communication Protocols ...........................................................................................18

2.7.1 Basic Protocol ....................................................................................................18 2.7.2 Data Inquiry Protocol..........................................................................................18 2.7.3 Error Correcting Protocol ...................................................................................19

2.8 Error Messages...........................................................................................................20 2.9 ID Separation ..............................................................................................................21 2.10 Input Circuits .............................................................................................................21 2.11 Output Circuits ..........................................................................................................21 2.12 Program Download ...................................................................................................22

2.12.1 Download Considerations ................................................................................22 2.12.2 Download Procedure........................................................................................23

2.13 Reports .....................................................................................................................25 2.14 Startup ......................................................................................................................25

Chapter 3 — Setup to Read Tags ........................................................................................27 Chapter 4 — 2200-700 Multiplexer.......................................................................................31

4.1 Overview .....................................................................................................................31 4.2 Controller Board..........................................................................................................34

4.2.1 Jumper J1 ..........................................................................................................35 4.2.2 Jumper J2 ..........................................................................................................35

4 3 October 2011, SmartScan Reader and Multiplexer Reference Guide, EUD-2011276-00

4.2.3 Jumper J3 ..........................................................................................................35 4.2.4 Potentiometer R3...............................................................................................35 4.2.5 Terminal Block TB1............................................................................................36 4.2.6 Connector P1 .....................................................................................................36

4.3 Technical Specifications .............................................................................................37 4.4 Dimensions .................................................................................................................38 4.5 Operational Modes .....................................................................................................39 4.6 Output Signals ............................................................................................................39 4.7 RS232 Signals ............................................................................................................40 4.8 Output Scanning Logic ...............................................................................................40

4.8.1 Three-Channel Operational Mode .....................................................................40 4.8.2 Four-Channel Operational Mode .......................................................................41

Chapter 5 — Typical Panel Layouts....................................................................................43 Chapter 6 — Customer Service ...........................................................................................47

6.1 Reaching STC ............................................................................................................47 6.2 Returning Equipment for Repair .................................................................................47 6.3 Reporting Problems or Suggestions ...........................................................................48 6.4 Ordering Spare Parts..................................................................................................48 6.5 Checking on Shipments and Orders...........................................................................48

Appendix A — Protocol Formats ........................................................................................49 A.1 Reader Transmissions ...............................................................................................49 A.2 ECP Host ACK/NAK Response..................................................................................50 A.3 Switch to Command Mode Request...........................................................................51 A.4 Host Transmissions....................................................................................................51 A.5 Reader Command Response.....................................................................................52 A.6 Timing and Synchronization .......................................................................................52 A.7 Reader Addressed Failure Conditions .......................................................................53 A.8 Host Addressed Failure Conditions............................................................................54

Appendix B — Commands...................................................................................................55 B.1 Command Listings......................................................................................................55

B.1.1 Factory Defaults ................................................................................................55 B.1.2 Commands Listed by Number ...........................................................................57

B.2 Command Descriptions ..............................................................................................63 Appendix C — Tag Reporting Examples ............................................................................97

C.1 No Translation, No Date and Time, No Auxiliary Information.....................................97 C.2 Translation, No Date and Time, No Auxiliary Information ..........................................99 C.3 Translation, Date and Time, No Auxiliary Information..............................................100 C.4 Translation, Date and Time, Auxiliary Information ...................................................102 C.5 Translation, No Date and Time, Auxiliary Information..............................................103 C.6 Integrated Multiplexer, Date and Time .....................................................................105 C.7 Integrated Multiplexer, No Date and Time ...............................................................106

Index ......................................................................................................................................109


Chapter 1 — Introduction This chapter summarizes the purpose of this guide, introduces RFID/AEI technology, and overviews the working of some SmartScan components. It also tells how to comment on this guide, tells how to order more copies of this guide, and covers STC's standard warranty. 1.1 Purpose of This Guide The technical staff at Southern Technologies Corporation (STC) created the SmartScan product line. This line consists of readers, processors, modems, and other components. In this guide, you will find detailed information about the SmartScan 2200-507SA Reader and the 2200-700 Multiplexer. Here you will learn how to setup the reader to read tags. Here too, you will learn about protocol formats, commands, flow control, and tag reporting. This guide is for those who buy, install, maintain, manage, or use the SmartScan 2200-507SA Reader and the 2200-700 Multiplexer. 1.2 Key Points Automatic Equipment Identification (AEI), Automated Vehicle Identification (AVI), and Radio Frequency Identification (RFID) are synonymous when referring to tag-reading equipment manufactured by TransCore. A basic RFID/AEI system consists of:

• An antenna

• A reader (transceiver with decoder)

• A radio frequency (RF) tag (transponder) In general use, vehicles and equipment are tagged with a wireless transponder. A reader reads these electronic tags as they pass a stationary antenna. The reader transfers the data read from the tags to a host computer, where it is stored for later processing. RFID/AEI systems use noncontact, not-line-of-sight technology. Tags can be read through poor atmospheric conditions like fog, rain, and snow. Tags can also be read through other poor visual conditions like grime, paint, and encrusted mud.


The figure below shows a tag as it is being read.

In operation, the readers create a radio frequency field that provides a constant carrier wave to activate a tag that is present in the field. When activated, the tag modulates the carrier wave in accordance with the preprogrammed data in the tag and reflects that modulated signal back to the reader. The reader receives the returned signal, processes the radio signal into usable characters, and sends them to a host computer. A reader reads a tag continuously while the tag is in the read field. It takes about 12.5 milliseconds to read the tag once (one frame) and then it repeats. It reads the tag once, twice, and more times until the tag leaves the read field. The tag is read more times on slow-moving vehicles than on fast-moving vehicles. Three key points of general operation are:

• Only one tag can be in the read field at one time. The reader gets confused if more than one tag is reporting at a time.

• The reader only reports a tag to the host computer one time. If the tag must be read again, the reader must be reset by command instruction or by reading a different tag.

• The radio signal is horizontally polarized, such that the horizontal plane of the antenna must match the horizontal position of the tag.

1.3 AEI Tags AEI tags serve only as coded reflectors for the radio frequency signal emitted through the antenna. They aren't radio transmitters. They don't radiate signals by themselves. RFID/AEI tags are categorized as either active or passive. An internal battery powers active tags. Passive tags operate without a separate external power source and obtain operating power from the RF signal generated by the reader. Passive tags are usually lighter than active tags, less expensive, and have a longer operational lifetime.


For the North American transportation industry, there are:

• Static tags (where tag data doesn't change after the tags are programmed)

• Dynamic tags (where tag data can be changed through a wire interface) The static tags can be:

• Beam powered

• Battery powered The dynamic tags can be:

• Battery powered

• Powered through a wire interface The beam-powered tags use some of the RF energy to power the integrated circuit of the tag. Battery-powered tags have a resident lithium battery for this task. These tags generally provide longer read ranges and operation for applications that specify very low RF power limits. For most rail applications, two models of Amtech RFID/AEI tags are used. The tags are the AT5118 and the AT5125. The tag specified by the Association of American Railroads (AAR) for use in North America on most railcars and locomotives is the AT5118 read-only tag, which replaces the AT5110. The AT5125 high-temperature case tag is used on railcars that are exposed to thaw sheds. The AT5118 and AT5125 are referred to as beam-powered tags because they use part of the radio frequency field to power the internal circuitry. With this type of operation, the tags don't require batteries. The AT5707 dynamic tag reports locomotive statistics such as fuel level. The dynamic tag has an external power source and a serial connection to an onboard computer, which updates the information in the tag as changes occur. AEI readers read, verify, and forward tag data through a communication port to a host computer. Data in the tags can be stored and retrieved as straight ASCII characters. In this case, the memory of the tag holds either 10 or 20 characters (depending on the model of tag). Before installation, the tags are programmed offline. A TransCore Tag Programmer (TP) is needed to program tags. The TP connects to a computer via a serial interface. A DOS-based tag-programming software package is supplied with the TP. This software allows you to program tags, by filling in required information on templates that are specific to the different format in which the tags can be programmed. The tag is programmed in six-bit ASCII data format or in a transportation-industry format, as defined by the AAR, International Standardization Organization (ISO), or American Trucking Association (ATA). These formats use data-compression techniques that allow the normal 20 characters programmed into a tag to represent more than 20 characters of data. The basic retrieval technique is the same. However, the tag data must be decoded to create the industry standard format.


SmartScan readers can be programmed to decode certain fields of data. When enabled, owner's initials, equipment number, and side indicator of tags that are in the AAR, ISO, or ATA data formats are decoded before being sent to the host computer. When disabled, the ASCII characters are forwarded as read to the host computer for decoding. 1.4 SmartScan Product Line In today's transportation industry, real-time asset management is achieved by incorporating enhanced information systems into operating systems and planning systems. The SmartScan product line provides these systems with the needed asset information. The SmartScan product line includes products for:

• Train consist listing

• Defect detection

• AEI

• Radio frequency data communications (RFDC)

• Terminal management software The advantage of the SmartScan product line is its ability to integrate seamlessly these enhanced information systems into transportation management systems. The modular architecture of the SmartScan family enables the individual products to operate in a standalone information mode or to be combined in an enhanced information system. As members of the SmartScan family of products, the SmartScan multiplexer and readers provide the AEI functions needed for standalone or integrated applications. 1.5 SmartScan Multiplexer and Readers AEI applications are all different and unique. The SmartScan multiplexer and readers make successful AEI applications easier by providing building blocks for successful projects. You can customize AEI products to meet project requirements. You can select the number of AEI channels, the best antenna, the communications format, the supply power, and the operating frequencies. The SmartScan multiplexer and readers provide versatility in reading and reporting RFID tags. These products can operate as a standalone AEI system. Alternatively, they can be integrated with other equipment such as dedicated processors, vehicle scales, vehicle-loading equipment, terminal management, asset management, and defect management systems. Anywhere equipment identification is required, the SmartScan products provide a cost-effective method of meeting the need.


The 2200-507SA is a standalone reader. It operates as a dedicated AEI tag reader. It can also be combined with the 2200-700 Multiplexer to achieve timeshared, four-channel AEI operation. The figure below shows the 2200-507SA Reader and the 2200-700 Multiplexer.

Their compact size allows the readers to be installed in a dedicated enclosure or integrated in existing or shared equipment enclosures. The 2200-700 Multiplexer allows RF power, supplied by the SmartScan readers, to be timeshared by as many as four channels. Thus, the 2200-700 Multiplexer can reduce the cost of AEI installations by eliminating the need for as many as three out of four readers. Vehicle presence input signals control the selection of multiplexer output channels, enabling only the channels that are selected. For more efficient operation, the multiplexer's logic enables either a two-channel mode or four-channel, depending on which control signals are enabled. 1.6 Disclaimers The correct use of this guide, the environmental conditions at the time of installation, the method of installation itself, and the installation of customer-supplied components are beyond the control of STC. So too are the correct use and maintenance of all or part of the SmartScan system. Therefore, the installer, user, and maintainer must assume the risk of any injury that might occur during installation, use, and maintenance of all or part of the SmartScan system. STC assumes no risk, liability, or responsibility for errors and omissions on the part of the installer, user, or maintainer.


1.7 How to Comment on This Guide We want to hear from you. Tell us what you like or don't like about this guide. Send your comments to:

Southern Technologies Corporation Technical Publications Department 6145 Preservation Drive Chattanooga, Tennessee 37416-3638 USA

All comments become the sole property of STC and none will be returned. 1.8 How to Order More Copies of This Guide When placing an order for more copies of this guide, refer to the order number shown on the cover of this guide. To request pricing and delivery, call 423-892-3029, fax 423-499-0045, or send email to [email protected]. Electronic copies of this guide are also available. 1.9 Standard Warranty Systems manufactured by Southern Technologies Corporation carry a 14-month warranty from date of shipment. Warranty is limited to repair or replacement at the sole discretion of STC, of any goods found to be defective in either materials or workmanship during the 14-month period following shipment. Warranty does not apply to product with signs of obvious abuse, or product that has been improperly installed. STC warrants that goods represented by this warranty statement have been designed and manufactured with all reasonable care and attention to appropriate regulatory documents. STC makes no representation that the goods covered by this warranty are suitable for the application they are used for. Application of the goods is at the sole discretion of the purchaser. Purchaser is responsible for shipment of the defective product to STC. STC will pay the return shipping charges. Products purchased from others, but included in STC systems carry the original manufacturer's warranty, typically 12 months. Warranty claims for these products must be made directly to the original equipment manufacturer.


Chapter 2 — 2200-507 Reader This chapter describes the 2200-507SA Reader. 2.1 Overview The 2200-507SA is STC’s latest offering in standalone readers. It is a plug-and-play replacement for the 2200-503 and 2200-506 series readers. You can integrate it with a 2200-700 Multiplexer to achieve four-channel AEI operation. The 2200-507SA reads and reports RFID tags in the programmed format. It can decode owner's initials, equipment number, and side indicator of tags that are in the AAR, ISO, or ATA data format. It can be integrated with other equipment such as scales, defect detectors, and computer equipment. The 2200-507SA operates from 110 VAC. It is programmable in a narrow-band frequency between 902 and 928 megahertz. Two TTL-level (that is, either 0 VDC or 5 VDC) output signals are available for integration with processing equipment, relay controls, and other devices. Data communication options include either RS232 (for short distances) or RS422 (for longer distances). Use RS422 when the host computer is more than 50 feet (15 meters) from the reader. A reader's data cable pinout is coordinated with that of the 2200-700 Multiplexer to allow easy integration with the use of DB-25 connector and flat cable. As shown below, the 2200-507SA uses three connectors.

RF Power ConectorDB25 Connector

Main Power ConectorLED Indicators


As shown above, the reader has two LEDs. The table below describes what each lit green LED means.

LED Name Meaning When Lit

Power Proper voltage is present. Stays lit as long as the reader is powered up.

Lock A valid tag is in the read field. Stays lit as long as the reader senses a tag.

The figures below show an assembled 2200-507SA Reader and a view of its components.

14-123-001AC Receptacle

14-109-002DB25F Conn

14-106-024SMA Bulkhead

10-100-020Panel Mnt LED (2 pc)

RF Shield 01-118-0026-32 Esna Nut

14-123-001E4 Board Set w/ Insulator Pad

41-105-301Reader Mnt Plate

12-117-006Hex Adapter 3/4" x 6-32 (2 pc)

12-117-009Hex Adapter 1/2" x 6-32 (2 pc)

2200-509ACPower Supply Bd 18VAC

01-108-0166-32 x 1/4" PPH (10 pc)

2200-508Interface/IO Bd


2.2 Technical Specifications Below are the technical specifications for the 2200-507SA Reader. These specifications are subject to change without notice.

• Reader Operating Frequencies: Reader operates between 902 and 928 megahertz. Standard ordering frequencies are 911.5, 918.5, 915, and 903.75 megahertz.

• Enclosure: Dustproof, 13" by 12.86" by 2.01", and zinc-chromate plated steel with a polyester powder overcoat.

• Input Power: 110 VAC

• Operating Temperature: -40°F to +122°F (-40°C to +50°C)

• Communication Interface: RS232 or RS422 (customer selected at time of ordering)

• Reader License Requirements: FCC part 90 site license

• Input / Output: Two user-programmable TTL-level inputs and two TTL-level outputs

• LED Indicators: Input power on and tag lock (read) signal

• RF Connector: SMA coaxial RF socket

• Data Connector: DB-25 socket

• Data Connector Pinout for RS232 1 - Ground (Power) 10 - Unused 19 - Unused 2 - Rxd 11 - Output0 (TTL) 20 - Unused 3 - Txd 12 - Output1 (TTL) 21 - Unused 4 - CTS 13 - +12 VDC 22 - Unused 5 - RTS 14 - Ground (Power) 23 - Unused 6 - Unused 15 - Unused 24 - Unused 7 - Signal Ground 16 - Input0 (TTL) 25 - +12 VDC 8 - Unused 17 - Input1 (TTL) 9 - +5 VDC 18 - Lock Signal (TTL)

• Data Connector Pinout for RS422 The pinout is the same as for RS232, except as noted below

2 - RxA (-) 4 - TxA (-) 3 - RxB (+) 5 - TxB (+)


2.3 Dimensions The figure below shows the outside dimensions of the 2200-507SA Reader.


2.4 Commands Commands are used to control the operation of the readers. Commands are sent from the host computer to the reader while the reader is in command mode or in data mode. The host software may send them. Or, when the host computer is in terminal emulator mode, they may be entered at the host keyboard. 2.4.1 Data Mode Upon power up, the reader is in data mode. In data mode, the reader sends data messages, such as tag IDs and reports, to the host computer. Reports provide information on input status changes (input0 and input1), the presence of a vehicle without tag data, and buffer overflow information. In data mode, the host computer can only send:

• Command 01, which changes the reader from data mode to command mode

• Command 05, which allows the host computer to download software into the reader

• Command 8110, which does a single system check tag test Appendix B - Commands has more information on the above three commands. When in data mode, the reader sends tag IDs to the host computer. If the reader is left in command mode too long, the tag buffer fills and additional tag IDs are lost. Therefore, you must return the reader to data mode as soon as possible to ensure proper transmission of buffered tag IDs. 2.4.2 Command Mode In command mode, the host computer sends commands to the reader. These commands control the operation and configuration of the reader. After the reader receives a command, it sends a command message. Typically, the command message contains the word Error, the word Done, or data relating specifically to the command request. These messages may be of variable length since some commands require information as part of the message.


The host computer sets a timeout delay when a command is sent to the reader. If the timeout delay expires before the host receives a command message from the reader, a logical NAK condition is declared. The host can then resend the command request message. Communications can be lost if the host computer attempts to send certain commands under marginal communication conditions. For example, if the host computer sends a command to change the baud rate and the reader properly receives the request and sends the Done message, one of these conditions may occur.

• If the host computer receives the Done message, both the host computer and the reader switch to the new baud rate. The reader changes the baud rate immediately after issuing the Done message. Communication is maintained.

• If the host computer doesn't receive the Done message sent by the reader, the host would assume that the command wasn't properly sent and wouldn't switch to the new baud rate. Communication is lost.

2.4.3 Sending Commands to the Reader When entering commands from the host keyboard, use basic protocol (not error correcting protocol). Sending manual commands to the reader is a six-step process:

1 Type #01

The start-of-message character is # and 01 is the command. Command 01 switches the reader to command mode, which allows the reader to accept commands from the host computer. In this mode, the tag IDs are stored in the reader and sent when the reader is returned to data mode.

2 Press [Enter]. 3 Type # and the appropriate command number.

Don't type any spaces between the # and the command number.

4 Press [Enter]. 5 Type #00

Command 00 switches the reader to data mode, which allows the reader to send tag IDs to the host computer.

6 Press [Enter].


2.5 Communication Port The SmartScan readers support one communication port, which can be ordered as either RS232 or RS422. The readers maintain the following three sets of parameters that affect serial port communications:

• Port configuration parameters (baud rate, data bits, stop bits, parity)

• Communication protocols (basic, data inquiry, error correcting)

• Flow-control scheme (none, software, hardware) The default serial port configuration for each of these three parameters is as follows:

• 9600 baud, 8 data bits, 1 stop bit, no parity

• Basic protocol

• Software flow control You can change these parameters in command mode by issuing commands from the host computer. 2.6 Flow Control When the host computer isn't ready to receive data from the reader, data can be lost. Flow control allows the host computer to pause the transmission from the reader. To interrupt reader transmissions, the host computer can use:

• Software flow control, where the reader stops sending when it receives the XOFF control character (hexadecimal 13). It resumes sending when it receives the XON character (hexadecimal 11).

• Hardware flow control, where the reader stops sending if it detects that the clear-to-send (CTS) line is no longer asserted. It resumes sending when this line is asserted.

If flow control isn't needed, configure the reader for no flow control (using command 6140). If flow control is needed, you can enable either software flow control (using command 6141) or hardware flow control (using command 6142). The factory default is software flow control enabled. However, software flow control should be disabled while using the error correcting protocol.


2.7 Communication Protocols A protocol is neither a computer program nor a piece of hardware. Rather, it is a set of rules governing the format of messages that are exchanged between readers and host computers. The SmartScan readers support:

• Basic protocol

• Error correcting protocol (ECP)

• Data inquiry protocol 2.7.1 Basic Protocol With basic protocol, the reader sends messages to the host computer without error checking. Also, the host computer sends messages to the reader without error checking. The reader for each host computer transmission returns a Done message or an Error message to the host computer. In basic protocol, the reader doesn't wait for the host computer to acknowledge a message before sending the next message. Therefore, the host computer must be ready to receive reader-sent messages. If necessary, the host computer may halt reader transmissions by using software flow control or hardware flow control. When the host computer is located close to the reader and there are no sources of interference, basic protocol provides reliable communications. 2.7.2 Data Inquiry Protocol Data inquiry protocol is a basic protocol option that allows the host to control transmission of reader tag data. The selection of data inquiry protocol affects data mode operation. As the reader gets tags, it buffers them but doesn't send them. Instead, the host must poll the reader for each tag by sending a CTRL-E control character (hexadecimal 05). The reader sends one message (tag ID or report data) for each CTRL-E it receives until the buffer is empty. Each tag-request message sent by the host computer consists only of the CTRL-E control character. SOMs or EOMs aren't sent. The reader data transmission (tag ID and report data) format is the same as for basic protocol. Selection of data inquiry mode doesn't affect command mode operation.


2.7.3 Error Correcting Protocol Wherever the quality of data communications is suspect, invoke ECP to ensure the integrity of data sent between the reader and the host computer. ECP is selected when the host sends command 610 to the reader after issuing a switch to command mode request. However, basic protocol (not ECP) should be used when commands are entered manually at the keyboard. With ECP, a two-way message interchange is required in both data mode and command mode. The message recipient returning a message to the sender completes the message interchange. If a message isn't received, the sender times out. This has the same effect as if the sender had received either:

• Negative acknowledge (NAK) control character (from the host computer)

• Error message (from the reader) Software flow control is optionally supported. Be careful in the use of software flow control because noise-induced characters may be interpreted by the reader as the XOFF character. This would suspend reader output without the host computer's knowledge. Software flow control should be disabled while using ECP. Communications are done using the seven-bit ASCII code with optional parity. This provides easy setup, testing, and diagnostics with standard ASCII terminals and serial printers. Parity must be enabled to achieve the specified undetected error rate. Each message is framed with the start-of-message (SOM) and end-of-message (EOM) control characters so that the host computer can detect the beginning and end of each message. This convention is most important under marginal communication conditions during which the host computer may receive extraneous noise-induced characters between reader transmissions. In such instances, the host computer ignores any messages that don't conform to the SOM...EOM frame sequence. Error correction is accomplished with use of a cyclic redundancy check (CRC) value that is based on the message data. The CRC of a message is calculated by the originator (reader or host) and is included in the sent message. The recipient (reader or host) also calculates a CRC for the received message. If the sent message data is correct, the CRC calculated by the recipient agrees with the CRC calculated by the originator. If the CRCs don't agree, the message is rejected. Message sequence numbers are also included when using ECP. These sequence numbers are checked to determine if the message received has the correct sequence number. If it doesn't, the message is rejected.


Since a seven-bit ASCII code is used and there are eight data bits per character, the eighth bit can optionally be used to support parity. When parity is used, the CRC calculation includes the parity of each character in the calculation of the CRC value. Parity is required to achieve the most reliable communications. If parity is enabled, both the reader and host must issue a message if any received character has a parity error. However, the message must not be sent before receipt of the EOM control characters (hexadecimal 0D0A). The reader issues an Error message and the host a NAK message. 2.8 Error Messages The reader sends an Error message when:

• A "command" received from the host computer isn't a recognized command

• Information supplied with the command isn't correct

• The reader fails a specified diagnostic test The reader maintains a tag buffer in battery-powered random-access memory (RAM) to save tag IDs received in command mode and when data inquiry protocol is used. This buffer holds up to 195 time-stamped messages. Error messages are sent to the host computer to provide buffer status as it fills. These messages are sent based on the content level of the tag buffer. They aren't sent if uniqueness checking has been disabled to send all IDs (command 40) or buffer all IDs (command 43). In command mode, the reader continuously monitors the level of its tag buffer. If the buffer becomes 75% full, the reader sends an Error04 message to the host. If the buffer becomes 100% full, it sends an Error02 message. Once the buffer is full, incoming tag IDs aren't buffered. They are lost. The reader doesn't resume asynchronous tag transmission until it is returned to data mode (command 00). Upon return to data mode, the reader begins to empty the tag buffer. Once the buffer is no longer full, the reader sends the Error03 message indicating that the tag buffer has been partially cleared, and new IDs are again being stored. When the buffer has emptied to 50%, the reader sends the Error05 message.


2.9 ID Separation The host computer can select a unique ID separation of:

• One ID, using command 4100

• Two IDs, using command 4101 The reader default operation is for a unique ID separation of one ID and a uniqueness timeout of two minutes. The host computer can disable the uniqueness check by:

• Using command 40 to send all IDs

• Using command 43 to buffer and send all IDs In this case, every received tag ID is sent without regard to uniqueness. The host computer can reinstate uniqueness checking with the select ID separation commands 4100 or 4101. 2.10 Input Circuits Both the RS232 and RS422 interfaces used by the SmartScan readers have two input circuits (also known as sense inputs and sensor inputs). They are input0 and input1. The default configuration uses input0 as the presence detection device line. RF power is turned on only when the presence detection device (wheel detector or other device) detects a presence. Input1 isn't used directly by the reader. The host computer uses it. The reader can be configured (using command 82N) to generate input status change reports, which are sent like tag IDs. The host computer can then respond based on the true-or-false status of the inputs. Input0 and input1 are TTL-level inputs that can interface with devices such as optical isolators, relays, and other TTL-level devices. 2.11 Output Circuits Both the RS232 and RS422 interfaces used by the SmartScan readers have two output circuits. They are output0 and output1. Both outputs are software controlled through command 620N. Both are TTL-level signals that can control devices such as optical isolators, relays, and other TTL-level devices.


2.12 Program Download The reader's software is put into the reader flash memory by program download. Program downloads are used to:

• Install program upgrades

• Add features

• Recover from corrupted program data In download mode, the reader only accepts:

• Command 90 (load program block)

• Command 91 (verify flash checksum)

• Command 96 (erase flash memory)

• Command 97 (do destructive memory test)

• Command 99 (exit download mode) 2.12.1 Download Considerations When downloading, consider the following:

• No tags are processed in download mode.

• Only download commands are accepted in download mode. The reader responds to all other commands with an Error message.

• The reader won't accept any program data unless the reader's flash memory has been erased before sending the data. Erasing the flash memory typically takes seven seconds.

• Exiting from download mode re-executes startup. If the new software has been loaded without errors, the reader comes up in data mode. If a flash checksum error is detected, the reader re-enters download mode and sends a sign-on message with a software version of 0.00 and without a serial number.

In download mode, the reader's communication parameters are fixed at 9600 baud, 8 data bits, 1 stop bit no parity, software flow control, and basic protocol. Also, in this mode, the reader doesn't echo host commands.


2.12.2 Download Procedure To download a new program file:

1 Type #01

Command 01 switches the reader to command mode, which allows the reader to accept commands from the host computer. In this mode, the tag IDs are stored in the reader and sent when requested by the host computer.

2 Press [Enter]. This line appears.

#Done

3 Type #05

Command 05 switches the reader to download mode, which allows an external host computer to download new software into the reader flash memory.


#Done

5 Type #96

Command 96 erases the flash memory. Once this command is executed, exit from download mode isn't possible until a new program is loaded into flash memory.


#Done

7 Replacing the letters with an Intel data record, type #90xxxxx

Command 90 transfers one Intel data record from an external host to the reader flash memory. (To load an entire program into reader memory, you must issue one command 90 for each record of the program.) Each Intel data record is a single line of ASCII characters, expressing bytes as hexadecimal pairs. Each Intel data record starts with a colon (hexadecimal 1A) and ends with a carriage return and linefeed (hexadecimal 0D0A).

8 Press [Enter]. If an Intel data record is received, stored, and verified with no errors detected, this line appears.

#Done


9 Repeat steps 7 and 8 until all records have been read into flash memory.

The reader sends a Done message for each record.

10 Type #91

Command 91 calculates a checksum on the new program in flash memory and then compares it with the stored checksum.

11 Press [Enter]. If the calculated checksum matches the stored checksum, this line appears.

#Done

If the calculated checksum doesn't match the stored checksum, this line appears. #Error

12 If you got the Error message, return to step 5.

13 Type #99

Command 99 directs the reader to exit download mode.

14 Press [Enter]. The software re-executes startup to ensure proper initialization of system parameters.

If the flash memory checksum verifies, the reader comes up in data mode and sends the sign-on message. On your computer, lines like these appear. The contents of your sign-on message may be different.

#Model E4 Series Ver 1.05 SN105962 #Copyright 2008 TransCore

If the flash memory checksum doesn't verify, the reader comes up in download mode and sends the sign-on message. On your computer, lines like these appear. The contents of your sign-on message may be different.

#Model E4 Series Ver 0.00 #Copyright 2008 TransCore

Notice that the only difference between the two sign-on messages is the first line.

15 If the flash checksum doesn't verify, repeat steps 1 through 14.


2.13 Reports A reader can be configured to send:

• Presence without tag reports, using command 690N

• Input status change reports, using command 82N Both report messages are handled the same as incoming tag IDs and are buffered behind previously received tag IDs. A presence without tag report is sent in data mode only. This report is sent if a presence is detected without the acquisition of a valid tag ID. If configured with command 82N to send input status change reports, the reader sends a message to the host computer any time the inputs change state. Input status change reports are sent in data mode only. Input status change reporting is disabled by default. 2.14 Startup Upon startup, a reader sends a sign-on message or a boot read-only memory (ROM) failure message. If all is okay, the reader displays the sign-on message whose first line is shown below. It then enters data mode.

Model xxxxx Ver yyyy SNzzzzzz where xxxxx is the model nomenclature, yyyy is the software version number, and zzzzzz is the serial number assigned to the reader being used. The serial number is expressed in decimal digits (0-9), with the first two digits representing the year. Serial number 000000 is the default setting and isn't a valid number. If this number appears in the sign-on message, either the battery has failed or the serial number has never been stored into reader memory. The appropriate serial number is assigned using command 695. If all isn't okay, the reader displays the sign-on message whose first line is shown below. It then enters download mode.

Model xxxxx Ver 0.00 where xxxxx is the model nomenclature.


The software does a checksum function on itself. The function returns a specific value for the particular software version. If the value returned isn't correct, the boot ROM checksum assumes that locations have been corrupted, and a failure condition exists. If the boot ROM checksum isn't correct, a boot failure message is sent. If the failure message doesn't transmit, a communications error has occurred or the boot failed because it couldn't send the failure message. If the version number of the failure message is 0.00 and there is no serial number, the flash memory checksum has failed, and the reader is operating out of boot ROM. In this case, the reader enters download mode and waits for a new program to be loaded into the flash memory.


Chapter 3 — Setup to Read Tags This chapter describes how to setup a SmartScan reader to read tags. To setup the 2200-507SA Reader to read tags:

1 Be sure you have on hand a 2200-507SA, a computer, a 915-megahertz antenna, a programmed RFID tag, and all connecting cables.

2 Connect a standard 25-pin serial communication cable between the 2200-507SA and the computer's communication port (COM1 or COM2).

The 2200-507SA simulates Data Communication Equipment (DCE). Thus, a null modem isn't required.

3 Connect a 50-ohm coaxial cable between the 2200-507SA's SMA coaxial RF connector and the 915-megahertz antenna.

4 Be sure your computer has appropriate communications software installed. That is, be sure your computer is running a terminal emulation program, such as ProComm or HyperTerminal.

5 Configure the communications software for full duplex, 9600 baud, no parity, 8 data bits, and 1 stop bit.

6 Plug the appropriate end of a power cable into the main power connector on the 2200-507SA.

RF Power ConectorDB25 Connector

Main Power ConectorLED Indicators


7 Plug the other end of the power cable into a grounded three-wire AC outlet.

The receptacle should be tight and securely grounded. The AC power service should be a stable 110 volts.

On the 2200-507SA, the Power LED lights.

On your computer, lines like these appear. These lines are called the sign-on message. The contents of your sign-on message may be different.


The reader is initialized in data mode.

The following shows how to change to command mode, set the time and date, turn RF power on, return to data mode, and read a tag.

8 Type #01

All reader commands are two, three, four, or five digits long and are preceded by the start-of-message character (#).

Command 01 switches the reader to command mode, which allows the reader to accept commands from the computer. In this mode, the reader doesn't send tag IDs to the computer as they are received. Instead, the IDs are stored in the reader's tag buffer for transmission when the reader is returned to data mode.


#Done

Many commands respond with Done (called the Done message) or with Error (called the Error message), indicating whether or not the command was recognized and completed. Like commands, all reader responses are preceded by the # character.

10 Replacing the letters with digits, type #20hh:mm:ss.ss

Command 20 sets the time. Type the time with no spaces between characters and using colons as delimiters. Entry format is 20hh:mm:ss.ss, where 20 is command number, hh is hours, mm is minutes, and ss.ss is seconds. Time is in 24-hour format, where 8 a.m. is 08:00, noon is 12:00, 8 p.m. is 20:00, and midnight is 00:00. Thus, for 26.7 seconds past 3:49 p.m., type 2015:49:26.70.


11 Press [Enter]. If you entered the command correctly, this line appears.

#Done

If you didn't enter the command correctly, this line appears. #Error


13 Replacing the letters with digits, type #21mm/dd/yy

Command 21 sets the date. Type the date with no spaces between characters and using slashes as delimiters. Entry format is 21mm/dd/yy, where 21 is command number, mm is month, dd is day, and yy is year. For days and months from 1 through 9, type leading zeros. Thus, for 3 June 2012, type 2106/03/12.

14 Press [Enter]. If you entered the command correctly, this line appears.

#Done

If you didn't enter the command correctly, this line appears. #Error


16 Type #6401

Command 6401 directly controls the RF module, turning on RF power.


#Done

18 Type #00

Command 00 switches the reader to data mode, which allows the reader to send tag IDs to the computer.



#Done

At this point, the 2200-507SA is ready to report tag reads.

20 Place a programmed RFID tag in front of the antenna.

On the 2200-507SA Reader, the Lock LED lights while the tag is in front of the antenna.

On your computer, a line like this appears. The contents of your line will be different.

#ABCDEFGHIJKLMNOPQRST&06:00:13.41 08/26/12

In the sample line above, # is the start-of-message character, the letters A through T are 20 characters representing tag data, & is the time-and-date delimiter, and 06:00:13.41 08/26/12 is the time and date.

Appendix C – Tag Reporting Examples shows how to read tags, resulting in five different outcomes. Covered are decoding and not decoding data, appending and not appending date and time, and appending and not appending auxiliary information.


Chapter 4 — 2200-700 Multiplexer This chapter describes the 2200-700 Multiplexer. 4.1 Overview The 2200-700 Multiplexer expands the capabilities of the SmartScan readers by sharing the readers' single RF channel with up to four antennas. By timesharing the reader, project installation costs are reduced by as much as 50 percent. The 2200-700 Multiplexer distributes the reader's RF power in a two-channel, three-channel, or four-channel scanning mode. This timesharing function of the 2200-700 Multiplexer can be setup to operate on demand or continuously. In Demand mode, external TTL-level presence input signals select which outputs are made active. Strapping the presence inputs active at an internal terminal block activates the continuous mode. The figure below shows the connectors that the 2200-700 Multiplexer uses.

The rightmost RF output connector is channel 1. The leftmost RF output connector is channel 4.


The figures below show an assembled 2200-700 Multiplexer and a view of its components.


Inside the 2200-700 Multiplexer are these two major components.

• RF switch

• Controller board The figure below shows the location of these components.

RF Switch

Controller Board

The RF switch directs the output of the reader to one of four antennas. The Controller board is described in the next section, 4.2 Controller Board.


4.2 Controller Board The Controller board provides:

• Inputs to monitor four presence detector signals

• Outputs to control the RF switch Based on which presence inputs are active, logic circuitry on the Controller board determines which antenna outputs to make active. A tuned free-running oscillator on the Controller board determines the rates at which the antenna outputs are switched. The figure below shows a Controller board.

Jumper (J1)Jumper (J2)

Connector (P1)

Potentiometer (R3)

Jumper (J3)

Terminal Block (TB1)


4.2.1 Jumper J1 Jumper J1 configures the 2200-700 Multiplexer for three-channel or four-channel timing. When J1 is wired, the multiplexer supports three RF antennas. When not wired, the multiplexer supports four RF antennas. This is a factory default. If all channels are active, the timing cycle for three-channel operation is 192 milliseconds. If all channels are active, the timing cycle for four-channel operation is 256 milliseconds. 4.2.2 Jumper J2 Jumper J2 selects what type of presence input TTL state is an active state. When the right two pads of J2 are wired, +5 VDC is selected. This is a factory default. When the left two pads are wired, 0 VDC is selected (that is, open collector is selected). 4.2.3 Jumper J3 Three TTL-level (that is, either 0 VDC or 5 VDC) output signals are available: sense0, sense1, and presence. Sense0 and sense1 are binary representations of which channel is active. When sense0 and sense1 are integrated with the reader, the state of these signals can be reported in the auxiliary information section of tag reads. This auxiliary read indicates which channel read the tag. Jumper J3 configures these outputs with a selectable delay period to allow for the readers' latency reporting time. The table below shows the delay for each selection on J3.

Selection Delay Period 1 7.4-millisecond delay (± 0.4 milliseconds) 2 9.4-millisecond delay (± 0.5 milliseconds) 3 11.8-millisecond delay (± 0.6 milliseconds) 4 14.0-millisecond delay (± 0.7 milliseconds)

4.2.4 Potentiometer R3 Potentiometer R3 adjusts the switching rate of the multiplexer. The switching rate was set at the factory and shouldn't need to be changed by the customer. Should it become necessary to change the switching rate, proceed with care. Using appropriate test equipment, place one probe on the test pad labeled clock (on the Controller board) and another on ground. Turn R3 until a frequency of 15.625 hertz or a period of 64 milliseconds is seen. Turn R3 to the right (clockwise) to increase the amount of time a RF antenna is active. Turn it to the left (counterclockwise) to decrease the amount of time a RF antenna is active.


4.2.5 Terminal Block TB1 When used, the eight-position terminal block TB1 connects the multiplexer to the presence detectors. TB1 can be used as an auxiliary connector for RS232 communications and presence input signals. The figure below shows what is wired to each terminal.

When continuous mode is required, jumper J2 should be wired to select open collector (that is, the left two pads should be wired). When wired this way, the controller scans all channels that aren't wired to Gnd on TB1. To disable or deselect a channel, wire the appropriate input signal (In1 through In4) to Gnd. 4.2.6 Connector P1 A DB-25 connector connects the multiplexer to the reader.


4.3 Technical Specifications Below are the technical specifications for the 2200-700 Multiplexer. These specifications are subject to change without notice.

• RF Operating Frequencies The multiplexer operates in a frequency range between 902 to 928 megahertz.

• Enclosure Dustproof, 7.09" by 7.06" by 2.51", zinc-chromate plated steel with a polyester powder overcoating.

• Input Power +5 VDC and +12 VDC

• Current Requirements +5 VDC at 0.05 amperes +12 VDC at 0.05 amperes

• Operating Temperature -40°F to +122°F (-40°C to +50°C)

• Input/Output Four TTL-level inputs for channel selection; one TTL-level output for input active indication; two TTL-level binary signals indicating channel.

• RF Connector Input = one SMA coaxial RF socket Output = four N-type coaxial sockets

• Data Connector DB-25 socket.

• Data Connector Pinout 1 - Ground (Power) 14 - Ground (Power) 2 - Rxd (RS232) 15 - Unused 3 - Txd (RS232) 16 - Sense0 Output (TTL) 4 - Unused 17 - Sense1 Output (TTL) 5 - Unused 18 - Unused 6 - Unused 19 - Unused 7 - Signal Ground (RS232) 20 - Presence Input4 (TTL level) 8 - Unused 21 - Presence Input3 (TTL level) 9 - +5 VDC 22 - Presence Input2 (TTL level) 10 - Unused 23 - Presence Input1 (TTL level) 11 - Unused 24 - Presence Output (TTL level) 12 - Unused 25 - +12 VDC 13 - +12 VDC


4.4 Dimensions The figure below shows the dimensions of the 2200-700 Multiplexer.


4.5 Operational Modes The 2200-700 Multiplexer operates in either:

• Demand mode

• Continuous mode In demand mode, the multiplexer timing is selected and the RF output channels enabled by activating the corresponding presence input signal. The 2200-700 Multiplexer scans each activated channel, in order (1 through 4), for 64 milliseconds. For efficiency, the cycle timing is divided into two 128-millisecond periods. Jumper J2 (on the Controller board) allows the presence input signals to be set for a +5 VDC signal level active (open-inactive state) or an open signal active (ground-inactive state). Factory default is for +5 VDC active signal. In continuous mode, channel timings work the same as in demand mode. The difference is that the channels are manually strapped for continuous operations on the TB1 (on the Controller board). The active select J2 (on the Controller board) must be set for open-active state, then the channels that aren't required to be active can be wired to ground on TB1. 4.6 Output Signals Three TTL-level (that is, either 0 VDC or 5 VDC) output signals are available: sense0, sense1, and presence. Sense0 and sense1 operate with the readers input signals of the same name. The states of both sense0 and sense1 are a binary representation of the active RF channel. When these signals are routed to the appropriate reader inputs and the reader setup includes reporting auxiliary information, then the channel that read the tag is reported in the auxiliary information field of the tag read. Because of the latency time in decoding tag reads and in augmenting auxiliary information, the sense0 and sense1 signals are delayed up to 14 milliseconds to compensate for tags read late in the scanning period. The Presence output signal is a TTL-level signal that indicates that one or more of the Presence inputs are active. This signal can be used as an advisory to a local processor that a presence input is active. Or the signal can be used to activate the reader's RF power if wired to sense0 input. In this case, the presence output signal replaces the sense0 signal and active channel information can't be reported through the tag read.


4.7 RS232 Signals The 2200-700 Multiplexer accommodates wiring of RS232 communication signals to TB1 (on the Controller board). The multiplexer routes these signals to the appropriate pins on the DB-25 connector for routing to the reader. This may be a useful connection option if a pre-made straight-through wiring cable is used for the reader-to-multiplexer data communication interface. 4.8 Output Scanning Logic Standard wiring for the 2200-700 Multiplexer supports four antennas. When one channel is active, the scan period is 128 milliseconds. When two channels are active, the scan period is either 128 or 256 milliseconds, depending on which channel is active. When three or four channels are active, the scan period is 256 milliseconds. At the factory, a modification can be made to jumper J1 (on the Controller board) to support only up to three antennas. When three channels are active, this modification decreases the scan period to 192 milliseconds. 4.8.1 Three-Channel Operational Mode For three-channel operational mode, if only channels 1, 2, or both are active, the controller scans between channels 1 and 2, with a scan period of 128 milliseconds. When only channel 3 is active, the scan period is 128 milliseconds, with a 50 percent duty cycle for channel 3. However, when a channel from both sections is active, the scan period is 192 milliseconds. The table below shows the status of the 2200-700 Multiplexer's output channel activity with each combination of input activity. The letter H is an active signal level. Scan period is the time required for a complete scan cycle, in three-channel operational mode. Channel Input Status RF Output Channel Activity Status

Input1 Input2 Input3 Output1 Output2 Output3 Scan Period

- - - - - - N/A H - - 64 msec - - 128 msec - H - - 64 msec - 128 msec H H - 64 msec 64 msec - 128 msec - - H - - 64 msec 128 msec H - H 64 msec - 64 msec 192 msec - H H - 64 msec 64 msec 192 msec H H H 64 msec 64 msec 64 msec 192 msec


4.8.2 Four-Channel Operational Mode For four-channel operational mode, if only channels 1, 2, or both are active, the controller scans between channels 1 and 2, with a scan period of 128 milliseconds. The same logic is applied to channels 3 and 4. However, when a channel from both sections is active, the scan period is 256 milliseconds. The table below shows the status of the 2200-700 Multiplexer's output channel activity (that is, the time when the given output channel in active) with each combination of input activity. The letter H is an active signal level. Scan period is the time required for a complete scan cycle, in four-channel operational mode. Channel Input Status RF Output Channel Activity Status

Input1 Input2 Input3 Input4 Output1 Output2 Output3 Output4 Scan Period

- - - - - - - - N/A H - - - 64 msec - - - 128 msec - H - - - 64 msec - - 128 msec H H - - 64 msec 64 msec - - 128 msec - - H - - - 64 msec - 128 msec H - H - 64 msec - 64 msec - 256 msec - H H - - 64 msec 64 msec - 256 msec H H H - 64 msec 64 msec 64 msec - 256 msec - - - H - - - 64 msec 128 msec H - - H 64 msec - - 64 msec 256 msec - H - H - 64 msec - 64 msec 256 msec H H - H 64 msec 64 msec - 64 msec 256 msec - - H H - - 64 msec 64 msec 128 msec H - H H 64 msec - 64 msec 64 msec 256 msec - H H H - 64 msec 64 msec 64 msec 256 msec H H H H 64 msec 64 msec 64 msec 64 msec 256 msec



Chapter 5 — Typical Panel Layouts The figure below shows the panel layout for a typical two-antenna application.


The figure below shows the terminal wiring for a typical two-antenna application.


The figure below shows the panel layout for a typical four-antenna application.


The figure below shows the terminal wiring for a typical four-antenna application.


Chapter 6 — Customer Service At STC, the customer is number one. STC is committed to products that work and customers that are satisfied. Nothing less is acceptable. This chapter tells how to get answers for questions, fixes for problems, and parts for spares. 6.1 Reaching STC You can reach STC by mail, phone, fax, and email. By mail, you can reach STC at: Southern Technologies Corporation 6145 Preservation Drive Chattanooga, Tennessee 37416-3638 USA Mail and shipments are replied to as soon as possible, normally within one working day. Equipment repair may take longer. By telephone, except on major holidays, you can reach STC at 423-892-3029, Monday through Friday, from 8:00 a.m. until 5:00 p.m. Eastern time. After business hours, a machine answers the calls. These calls are returned promptly the next business day. By fax, you can reach STC at 423-499-0045. The fax machine can receive faxes at all times. Faxes are replied to as soon as possible, normally within one working day. By email, you can reach STC at [email protected]. Email is replied to as soon as possible, normally within one working day. 6.2 Returning Equipment for Repair Return any defective or malfunctioning equipment to STC for repair or replacement. You don't need a return authorization number. You don't even need to make a phone call first. Just ship it directly to the Repair Department at the address above. With the returned equipment, include:

• Complete address where the equipment is to be returned.

• Name and phone number of the person who should be contacted to answer questions about the equipment.

• Written explanation of the equipment defect or malfunction.

• Any reports or other data that would be helpful in diagnosing the problem.

• If out of warranty, Purchase Order Number for the order or credit card number (to be charged) with its expiration date.


6.3 Reporting Problems or Suggestions If you have any problems, suggestions, or questions related to STC equipment, phone the Engineering Department at the phone number above. When calling, state the equipment you are calling about. Your call will then be directed to the right person. 6.4 Ordering Spare Parts If you need any spare parts to support STC equipment, phone or fax the Sales Department at the phone numbers above. When calling, state that you are calling to order parts. Your call will then be directed to the right person. When placing the order, reference the STC part numbers listed in this guide. However, if you don't have the part numbers, the sales staff can obtain them for you and provide you with current pricing and availability. When faxing, include:

• Purchase Order Number for the order or credit card number (to be charged) with its expiration date.

• Complete address where the parts are to be shipped.

• Complete address where the invoice is to be mailed.

• Name and phone number of the person who should be contacted to answer questions about the order.

• Your fax number, if available.

• For each item ordered, part number, complete description, and quantity needed. 6.5 Checking on Shipments and Orders If you need to check on the status of any shipment or order, phone or fax the Sales Department at the phone numbers above. When calling, state that you are checking the status of a shipment or order. Your call will then be directed to the right person. Have your Purchase Order Number ready when you call. However, if you don't have the order number, the sales staff can obtain it for you and provide you with the status of the shipment or order. When faxing, include:

• Purchase Order Number for the shipment or order being checked.

• Name and phone number of the person who should be contacted after the order status is checked.

• Your fax number, if available.


Appendix A — Protocol Formats The SmartScan readers support:

• Basic protocol

• Error correcting protocol

• Data inquiry protocol This appendix describes basic, ECP, and data inquiry protocol formats. Also covered are timing, synchronization, and failure conditions. In the text below, the symbols < > represent required data. The symbols [ ] represent optional data. These symbols aren't part of the message syntax. A.1 Reader Transmissions The reader can send data to the host computer using any of the three protocols. The basic protocol format is: <SOM><DATA><EOM> The ECP format is: <SOM><SEQ><DATA><CRC><EOM> The data inquiry protocol format is: <SOM><DATA><EOM> where: CRC Cyclic redundancy check. This field contains four ASCII digits that represent the 16-bit CRC

calculated on the message. Once the host receives a properly framed message, it calculates a CRC. The calculation is applied to the character string that immediately follows the SOM character and ends with the character before the first CRC character. The sent CRC is compared with the received CRC. If they aren't the same, the message is assumed to have been received in error and a NAK message is sent.

DATA An ASCII string up to 72 characters long. This string may contain tag data, a presence without tag report, an input status change report, an error message, or a sign-on message. Time, date, and auxiliary information may also be included.

EOM End-of-message control characters (hexadecimal 0D0A). If the host receives a SOM character in the middle of a data message, the message in progress is ignored. The assumption is that an EOM was lost while the reader was resending the previous message.


SEQ Sequence number that is an even number in the range 0-E. The reader maintains this

number. The host acknowledges reader transmissions by sending an ACK with the same sequence number received from the reader. The reader updates its sequence number upon receipt of a valid host ACK. If an ACK isn't received, the reader resends the message. A reader transmission sequence isn't considered complete until the reader receives an ACK and updates its sequence number.

SOM Start-of-message control character (hexadecimal 23). A.2 ECP Host ACK/NAK Response With ECP, the host computer responds to all data message transmissions from the reader with this ACK or NAK response format. <SOM><SEQ><ACK/NAK><CRC><EOM> where: ACK Acknowledge control character (hexadecimal 06). CRC Cyclic redundancy check. This field contains four ASCII digits that represent the 16-bit CRC

calculated on the message. EOM End-of-message control characters (hexadecimal 0D0A). NAK Negative ACK control character (hexadecimal 15). SEQ An echo of the sequence number received from the reader. The sequence number should

correspond to the data message that is being positively or negatively acknowledged by the host. If the reader receives an ACK message with the incorrect sequence number, the data message is resent. The host computer is responsible for resetting its anticipated data message sequence number to that of the reader before communications can resume without error.

SOM Start-of-message control character (hexadecimal 23). The reader sets a user-programmable timeout delay at the time each message is sent (based on command 612NN, where NN = timeout delay). The timeout delay can be disabled for diagnostic purposes by setting NN = FF. If the timeout delay expires before the reader receives an ACK or NAK message from the host, a logical NAK condition is declared. If the reader receives a NAK or timeout, the data message is resent. When the reader receives an ACK message, the message is treated as having been properly received by the host. The sequence number is then incremented, and pointers are advanced to the next message in the reader's message queue to prepare for sending the next message.


A.3 Switch to Command Mode Request The host may issue command 01, switch to command mode, while in data mode. The basic protocol format is: <SOM><CMD><EOM> The ECP format is: <SOM><SEQ><CMD><CRC><EOM> where: CMD Switch to command mode, command number (ASCII characters 01) CRC Cyclic redundancy check. This field contains four ASCII digits that represent the 16-bit

CRC calculated on the message. EOM End-of-message control characters (hexadecimal 0D0A). SEQ The sequence number is generated by the host computer separately from that appearing in

data messages sent by the reader. SOM Start-of-message control character (hexadecimal 23).

A.4 Host Transmissions The host computer initiates synchronous communications between the reader and itself. The host computer begins a sequence by issuing a command. The reader responds accordingly. The host computer can send data to the reader using any of the three protocols. The basic protocol format is: <SOM><CMD>[DATA]<EOM> The ECP format is: <SOM><SEQ><CMD>[DATA]<CRC><EOM> The data inquiry protocol format is: <CTRL-E> where: CMD Command code, a string that contains 2 to 5 ASCII hexadecimal characters. CRC Cyclic redundancy check. This field contains four ASCII digits that represent the 16-bit

CRC calculated on the message. CTRL-E ASCII CTRL-E (hexadecimal 05). When in data inquiry mode, each transmission of a

CTRL-E by the host causes the reader to send one tag ID. DATA Optional data field, an ASCII string of up to 20 characters in length. For example, the

set date command is 2Imm/dd/yy. EOM End-of-message control characters (hexadecimal 0D0A). SEQ Sequence number that is an odd number in the range 1-F. Upon receiving a host

command, the reader echoes the command's sequence number in its response. The host updates its sequence number upon receipt of a valid reader message. If the sequence number isn't updated before transmission of the next command, the reader won't service the new command. Instead, it resends its previous message. A command-message sequence isn't considered complete until the host updates its sequence number.

SOM Start-of-message control character (hexadecimal 23).


A.5 Reader Command Response The basic protocol format is: <SOM><RESP><EOM> The ECP format is: <SOM><SEQ><RESP><CRC><EOM> where: CRC Cyclic redundancy check. This field contains four ASCII digits that represent the 16-bit

CRC calculated on the message. EOM End-of-message control characters (hexadecimal 0D0A). RESP Response string. The reader will return Done, Error, or another ASCII string depending on

the host transmission. This string can be up to 72 characters long. SEQ Echo of sequence number received in host command message. SOM Start-of-message control character (hexadecimal 23).

A.6 Timing and Synchronization The ECP is largely independent of baud rate. Readers support an ECP timeout on both send and receive. In addition, for readers, a protection mechanism prevents the assignment of mismatched ECP timeout and baud rate values. Readers won't allow the host to alter the ECP timeout (command 612NN) if the specified timeout is too short for the current baud rate. Conversely, readers won't allow the host to alter the baud rate (command 100N) if the specified baud rate is too fast for the current ECP timeout. The receiver's minimum timeout delay should equal the time to send the longest anticipated message at the current baud rate setting. Additional margin should be included for idle periods between characters (that is, for processing overhead, if any). Likewise, the sender must set a timeout delay equal to the delay of nine characters at the current baud rate setting (that is, the time required to shift out the EOM characters plus the time to shift in the ACK or NAK message to be received) plus a processing allowance for the receiver to process the message and check for error conditions. The reader supports baud rates between 110 and 38,400. The host can remotely set communication parameters of the reader in command mode, but this action isn't recommend if communication conditions are marginal. After the reader receives new communication parameters, the reader sends a Done message and switches to the new configuration immediately. It is the responsibility of the host computer to switch its communication parameters immediately after the transaction is complete.


As noted, the message initiator (that is, the reader in data mode and the host computer in command mode) starts a timeout counter at the time a message is sent. If the timeout expires before receiving a message, a logical NAK condition is declared, and the message is assumed to have been received in error. In this instance, the message is resent until a message is received. The message recipient (that is, the host computer in data mode and the reader in command mode) starts a timeout counter when a SOM character is received. If the timeout expires without the receiver having received EOM characters, the message in progress is ignored and the receiver waits for the next SOM character. If a second SOM character is received before EOM characters are, the message in progress is ignored and a new message is assumed to be underway. While the reader is in command mode, all received tag IDs are buffered but not sent. Thus, it is important that the host limit the period during which the reader remains in command mode to avoid overflowing the readers tag ID buffer and subsequently losing tag IDs. A.7 Reader Addressed Failure Conditions If the reader detects an illegal sequence number in a host command message, it discards the received message and doesn't send a response. If the reader receives an illegal or wrong sequence number in an ACK message, it responds as if a NAK was received. It resends the data. If the reader detects a bad CRC in a host command message, it discards the received message. No response is sent. If it receives a bad CRC in an ACK message, it responds as if a NAK was received. It resends the data. If the reader receives an illegal command, it returns an Error message. If the reader sends an asynchronous message and the host doesn't send an ACK before the ECP timeout occurs, the reader resends the message. If the reader receives a SOM character and doesn't receive EOM characters before the ECP timeout occurs, it discards the incomplete message and resets its receiver. If the reader sends asynchronous data while the host computer is sending a command, the reader gives priority to receiving the command. It processes the command and sends a message before it resends the asynchronous data.


A.8 Host Addressed Failure Conditions If the host computer detects an illegal or wrong sequence number in a reader response, it resends the command with the same sequence number. If the host detects an illegal sequence number in an asynchronous reader transmission, it sends a NAK message. If the host detects a bad CRC in a reader message, it resends the command with the same sequence number. If the host detects a bad CRC in an asynchronous reader transmission, it sends a NAK message. If the reader doesn't respond to a host command within a specified interval, the host resends the command with the same sequence number. If the host receives a SOM character and doesn't receive EOM characters within a specified timeout interval, it discards the incomplete message and resets its receiver. If the host receives an asynchronous reader transmission while sending a command, it ignores the asynchronous message and waits for the reader's response. The reader resends asynchronous data after it sends the command message.


Appendix B — Commands Commands are used to control the operation of the readers. Commands are sent from the host computer to the reader while the reader is in command mode or in data mode. The host software may send them. Or, when the host computer is in terminal emulator mode, they may be entered at the host keyboard. This appendix lists all commands and then describes each one. Command numbers consist of two, three, four, or five hexadecimal digits. (For example, 00, 67A, 1005, 60E3, and 612FE are all valid commands.) If the letters N or NN follow a number, that part of the command number is variable. If this is the case with the command you want to issue, replace each letter N with an appropriate hexadecimal digit. B.1 Command Listings This section contains three tables. The first two list the factory defaults, those changeable by users and those not. The third one lists all the commands available to users. B.1.1 Factory Defaults The table below lists the factory defaults that aren't changeable by the user. Parameter SettingEnd-of-line delay Zero millisecondsMinimum presence true period Zero millisecondsPeriodic check tag interval 30 minutesStart-of-message character # (hexadecimal 23)


The table below lists the factory defaults that are changeable by the user. Parameter Setting Command Operating mode Data mode 00 Baud rate 9600 baud 1005 Stop bits One stop bit 1010 Parity None 1020 Time and date appended Enabled (appended) 302 Auxiliary information appended Disabled (not appended) 310 Unique ID code criteria Separation of one ID 4100 Wiegand mode Disabled 450 Tag translation mode Disabled 452 Wiegand transmit mode One second 4601 Dual-frame-tag processing mode Reset uniqueness on A, send A to host 480 Reader ID number 00 6000 Communication protocol Basic 610 ECP timeout 12.7 seconds 612FE Flow control Software flow control 6141 Buffer control mode Disabled 6160 Echo mode Enabled 6171 Output control Predefined 621 RF-by-input control Enabled 641 Output pulse duration 228 milliseconds 67C Presence without tag reports Disabled 6900 RF-off control Timeout or presence false condition 6922 RF timeout Never expires 693F Input inversion Disabled 6940 Serial number 000000 695 Store hardware configuration Hardware configuration not known 696 Periodic system check tag Disabled 810 Check tag location Internal 8160 Input status change reports Disabled 820


B.1.2 Commands Listed by Number The table below lists the commands by number. Number Command Reader Message 00 Switch to data mode Done 01 Switch to command mode Done 05 Switch to download mode Done or Error 06 Send buffer entry Done, Error, or tag data 1000 Set baud rate to 110 bps Done or Error 1001 Set baud rate to 300 bps Done or Error 1002 Set baud rate to 1200 bps Done or Error 1003 Set baud rate to 2400 bps Done or Error 1004 Set baud rate to 4800 bps Done or Error 1005 Set baud rate to 9600 bps Done or Error (default) 1006 Set baud rate to 19,200 bps Done or Error 1007 Set baud rate to 38,400 bps Done or Error 1010 Select one stop bit Done (default) 1011 Select two stop bits Done 1020 Select no parity Done (default) 1021 Select even parity Done 1022 Select odd parity Done 20 Set time (20hh:mm:ss.ss) Done or Error 21 Set date (21mm/dd/yy) Done or Error 22 Display time and date hh:mm:ss.ss mm/dd/yy 300 Don't append time and date Done or Error 302 Append time and date Done or Error (default) 310 Don't append auxiliary information Done or Error (default) 311 Append auxiliary information Done or Error 40 Send all IDs Done or Error 4100 Select one ID separation Done (default) 4101 Select two ID separation Done 4102 Select three ID separation Done 4103 Select four ID separation Done 4200 Select one valid ID code Done 4201 Select two valid ID codes Done 4202 Select three valid ID codes Done 4203 Select four valid ID codes Done 43 Buffer all ID codes Done 440 Reset Uniqueness Done 450 Disable Wiegand mode Done 451 Enable Wiegand mode Done 452 Disable tag translation mode Done 453 Enable tag translation mode Done


Number Command Reader Message 46NN Set Wiegand retransmit interval

NN = 01-FF seconds Done

48N Select dual-frame-tag processing mode N = 0 Reset uniqueness on A, send A N = 1 Reset uniqueness on B, send B N = 2 Reset uniqueness an A, send both N = 3 Reset uniqueness on B, send both

Done or Error

505 Display software version Model xxxxx Ver yyyy SNzzzzzz xxxxx = model of reader yyyy = version number of software zzzzzz = serial number of reader

506 Display hardware configuration information ASCII string (up to 20 characters) 520 Display reader power fail bit PWRB Px R0

P0 = power failure hasn't occurred P1 = power failure has occurred R0 = not applicable

521 Display reader ID number RDID xx xx = 00-FF

522 Display communication port parameters MAIN Bx Sx Px D0 B0 = 110 bps B1 = 300 bps B2 = 1200 bps B3 = 2400 bps B4 = 4800 bps B5 = 9600 bps B6 = 19,200 bps B7 = 38,400 bps S0 = one stop bit S1 = two stop bits P0 = no parity P1 = even parity P2 = odd parity D0 = EOL delay of 0 msec

524 Display appended information status IDAP Tx Dx Xx T0 = time not appended T1 = time appended D0 = date not appended D1 = date appended X0 = auxiliary information not appended X1 = auxiliary information appended

525 Display communication protocol status ECPS Px Txx Xx P0 = basic protocol enabled P1 = ECP enabled P2 = data inquiry protocol enabled Txx = ECP timeout X0 = no flow control X1 = software flow control enabled X2 = hardware flow control enabled


Number Command Reader Message 526 Display I/O status IOST Cx Ox Ix Dx

C0 = host controls outputs C1 = predefined output mode O0 = both outputs off O1 = output0 on O2 = output1 on O3 = both outputs on I0 = both inputs false I1 = input0 true I2 = input1 true I3 = both inputs true Dx = output pulse duration (4 ms to 752 ms)

527 Display RF status RFST Cx Ox T1 C0 = RF controlled by host C1 = RF-by-input control O0 = RF off O1 = RF on T1 = uniqueness timeout of 2 minutes

529 Display presence input status PRST Px D0 Ax Tx Ix P0 = disable presence without tag reports P1 = enable presence without tag reports D0 = min presence true period of 0 msec A0 = RF off on timeout Al = RF off on timeout or tag A2 = RF off on timeout or no presence Tx = RF timeout period I0 = input inversion disabled I1 = input inversion enabled

530 Display RF0 filter status RF0S Ux Vx Tx U0 = one ID separation U1 = two ID separations U2 = three ID separations U3 = four ID separations U4 = send all IDs U5 = buffer all IDs V0 = one acquisition for valid ID V1 = two acquisitions for valid ID V2 = three acquisitions for valid ID V3 = four acquisitions for valid ID T1 = variable timeout of 2 minutes T2 = variable timeout of 15 seconds T3 = variable timeout of 30 seconds

532 Display Wiegand mode status TOF x 0 = Wiegand mode disabled 1 = Wiegand mode enabled

533 Display Wiegand retransmit interval WTI xx xx = 01-FF seconds

534 Display tag translation mode status TT x 0 = tag translation mode disabled 1 = tag translation mode enabled


Number Command Reader Message 535 Display buffer control mode status BCM x

0 = buffer control mode disabled 1 = buffer control mode enabled

536 Display dual-frame-tag processing mode DUAL x 0 = reset uniqueness on A, send A 1 = reset uniqueness on B, send B 2 = reset uniqueness on A, send both 3 = reset uniqueness on B, send both

537 Display echo mode status ECHO x 0 = echo mode disabled 1 = echo mode enabled

540 Display flash checksum PCKS I0000 Exxxx xxxx = 4-byte ASCII checksum

543 Display boot checksum BCKS xxxx xxxx = 4-byte ASCII checksum

550 Display periodic check tag status SCTS Mx T5 M0 = periodic check tag disabled M1 = periodic check tag enabled T5 = periodic interval of 30 minutes

551 Display selected check tag option CTAG x 0 = internal check tag option 1 = external check tag option

560 Display input status change report options SSTC Ex Mx E0 = status change reports disabled E1 = status change reports enabled M0 = reporting disabled M1 = report changes on input0 M2 = report changes on input1 M3 = report changes on either input

60NN Set reader ID number NN = 00-FF

Done or Error

610 Select basic protocol Done 611 Select error correcting protocol Done 612NN Select ECP timeout period

NN = 01-FE Done or Error

613 Select data inquiry protocol Done 6140 Disable flow control Done 6141 Enable software flow control Done 6142 Enable hardware flow control Done 6160 Disable buffer control mode Done 6161 Enable buffer control mode Done 6170 Disable echo Done 6171 Enable echo Done 6200 Turn off output0 and output1 Done 6201 Turn on output0, turn off output1 Done 6202 Turn on output1, turn off output0 Done 6203 Turn on output0 and output1 Done 621 Select predefined output mode Done


Number Command Reader Message 63 Reset reader Model xxxxx Ver yyyy SNzzzzzz

xxxxx = model of reader yyyy = version number of software zzzzzz = serial number of reader

6400 Turn off RF power Done 6401 Turn on RF power Done 641 Select RF-by-input control Done 642NN Select RF operating frequency Done 643NN Select RF operating range (distance) Done 65 Reset power fail bit Done 660 Test external RAM Done or Error 661 Display diagnostic results DIAG Rx Ex Dx Cx

R0 = boot ROM OK R1 = boot failed E0 = flash memory OK E1 = flash memory failed D0 = external RAM OK D1 = external RAM failed C0 = RTC OK C1 = RTC failed

664 Test real-time clock Done or Error 667 Verify boot ROM checksum Done or Error 668 Verify flash memory checksum Done or Error 669 Do all diagnostics Done or Error 66F Load default operating parameters Done or Error 67N Set output pulse duration

N = 0-F Done or Error

6900 Disable presence without tag reports Done 6901 Enable presence without tag reports Done 6920 Turn RF off on timeout Done 6921 Turn RF off on timeout or tag acquired Done 6922 Turn RF off on timeout or presence false Done 693N Set RF timeout period

N = 0-F Done or Error

6940 Disable input inversion Done 6941 Enable input inversion Done 695 Set serial number (695ssssss) Done 696 Store hardware configuration string

(696ss...ss) Done


Number Command Reader Message 777 Report buffered handshake data Buffered Handshakes %00-0-nn-1

nn = total valid ID frames 810 Disable periodic check tag Done 8110 Do system check tag test Done 8120 Enable periodic check tag Done 8160 Select internal check tag Done 8161 Select external check tag Done or Error 820 Disable status change reports Done 821 Report change on input0 Done 822 Report change on input1 Done 823 Report changes on input0 and input1 Done 90 Load one record of a program Done, Read Error, Program Error, or Verify

Error 91 Verify flash checksum Done or Error 96 Erase flash memory Done 97 Do destructive flash test Done or Error 99 Exit download mode Model xxxxx Ver yyyy SNzzzzzz

xxxxx = model of reader yyyy = version number of software zzzzzz = serial number of reader


B.2 Command Descriptions This section describes each command. In the following text, the symbols < > represent required variable message data. These symbols aren't part of the message syntax. 00 Switch to Data Mode Command 00 switches the reader to data mode, which allows the reader to send tag IDs to the host. This is a factory default. After the reader executes command 00, it sends a Done message to the host computer. 01 Switch to Command Mode Command 01 switches the reader to command mode, which allows the reader to accept commands from a host computer. In this mode, the reader doesn't send tag IDs to the host computer as they are received. Instead, the IDs are stored in the reader's tag buffer for transmission when requested by the host computer. After the reader executes command 01, it sends a Done message to the host computer. 05 Switch to Download Mode Command 05 switches the reader to download mode, which allows a host computer to download new software into the reader's flash memory. In download mode, the reader's communication parameters are fixed at 9600 baud, 8 data bits, 1 stop bit no parity, software flow control, and basic protocol. Also, in this mode, the reader doesn't echo host commands. To exit download mode, the host computer must send command 99. If in command mode, the reader executes command 05 and then sends a Done message to the host computer. If in data mode, the reader sends an Error message to the host computer. 06 Send Buffer Entry Command 06 allows the host computer to request data (tag IDs and reports) from the reader. This command is supported if ECP is selected (command 611) and buffer control mode is enabled (command 6161).


If the reader receives command 06 and it has data in its message buffer, it sends the buffered message of highest priority. Report data isn't sent until all tag IDs have been sent. If the reader's message buffer is empty, it sends a Done message to the host computer. If the reader receives this command when ECP isn't enabled, it sends an Error message to the host computer. If the reader receives this command when buffer control mode isn't enabled, it sends an Error message to the host computer. 100N Set Baud Rate Command 100N sets the reader's baud rate. The factory default is 9600 baud (command 1005). The N variable specifies the baud rate as follows:

Command Baud Rate Selected 1000 110 baud 1001 300 baud 1002 1200 baud 1003 2400 baud 1004 4800 baud 1005 9600 baud 1006 19,200 baud 1007 38,400 baud

If the currently selected ECP timeout is sufficient for the requested baud rate, the reader sends a Done message to the host computer. If the currently selected ECP timeout isn't sufficient for the requested baud rate, the reader sends an Error message. If the reader sent an Error message, ECP timeout must be increased before command 100N can be resent. Also, if a valid hexadecimal digit isn't substituted for N in command 100N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 1008, the reader sends it an Error message. 1010 Select One Stop Bit Command 1010 selects one stop bit for reader character transmission. This is a factory default. Command 1011 selects two stop bits for reader character transmission. After the reader executes command 1010, it sends a Done message to the host computer. 1011 Select Two Stop Bits Command 1011 selects two stop bits for reader character transmission. Command 1010 selects one stop bit for reader character transmission. After the reader executes command 1011, it sends a Done message to the host computer.


102N Select Parity Command 102N selects the reader parity setting. The factory default is no parity (command 1020). The N variable specifies parity as follows:

Command Data Bits Parity Selected 1020 8 Select no parity 1021 7 Select even parity 1022 7 Select odd parity

After the reader executes command 102N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 102N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 1024, the reader sends it an Error message. 20 Set Time Command 20 sets the time. Type the time with no spaces between characters and using colons as delimiters. Entry format is 20hh:mm:ss.ss, where 20 is command number, hh is hours, mm is minutes, and ss.ss is seconds. Time is in 24-hour format, where 8 a.m. is 08:00, noon is 12:00, 8 p.m. is 20:00, and midnight is 00:00. Thus, for 26.7 seconds past 3:49 p.m., type 2015:49:26.70. If hundredths of a second aren't specified, the reader sets the hundredths register to 00. For times from midnight through 09:59, type leading zeros. If the format of command 20 is correct, the reader executes the command and then sends a Done message to the host computer. If it isn't correct, the reader sends an Error message to the host computer. 21 Set Date Command 21 sets the date. Type the date with no spaces between characters and using slashes as delimiters. Entry format is 21mm/dd/yy, where 21 is command number, mm is month, dd is day, and yy is year. For days, months, or years from 1 through 9, type leading zeros. Thus, for 3 July 2009, type 2107/03/09.


If the format of command 21 is correct, the reader executes the command and then sends a Done message to the host computer. If it isn't correct, the reader sends an Error message to the host computer. 22 Display Time and Date Command 22 displays the reader's current time and date. One space separates the time and the date. The reader sends hh:mm:ss.ss mm/dd/yy, where hh is hours, mm is minutes, ss.ss is seconds, mm is month, dd is day, and yy is year. 300 Don't Append Time and Date Command 300 tells the reader to not append the time and date to transmitted IDs, error messages, presence without tag reports, and input status change reports. If the tag buffer is empty, the reader executes command 300 and then sends a Done message to the host computer. If the tag buffer contains data, the reader sends an Error message to the host computer. Command 63 may be sent to clear the buffer. However, executing command 63 loses tag ID data. If this is unacceptable, allow the tag buffer to empty before re-issuing command 300. 302 Append Time and Date Command 302 tells the reader to append the time and date to transmitted IDs, error messages, presence without tag reports, and input status change reports. This is a factory default. Command 300 stops appending the time and date. If the tag buffer is empty, the reader executes command 302 and then sends a Done message to the host computer. If the tag buffer contains data, the reader sends an Error message to the host computer. Command 63 may be sent to clear the buffer. However, executing command 63 loses tag ID data. If this is unacceptable, allow the tag buffer to empty before re-issuing command 302. After executing command 302, the reader sends messages as xx&hh:mm:ss.ss mm/dd/yy, where xx is tag ID, error message, or report, hh is hours, mm is minutes, ss.ss is seconds, mm is month, dd is day, and yy is year. One space separates the time from the date.


310 Don't Append Auxiliary Information Command 310 tells the reader to not append auxiliary information to transmitted IDs, error messages, presence without tag reports, and input status change reports. This is a factory default. If the tag buffer is empty, the reader executes command 310 and then sends a Done message to the host computer. If the tag buffer contains data, the reader sends an Error message to the host computer. Command 63 may be sent to clear the buffer. However, executing command 63 loses tag ID data. If this is unacceptable, allow the tag buffer to empty before re-issuing command 310. 311 Append Auxiliary Information Command 311 tells the reader to append auxiliary information to transmitted IDs, presence without tag reports, and input status change reports. Auxiliary information isn't appended to error messages. Command 310 stops appending auxiliary information. If the tag buffer is empty, the reader executes command 311 and then sends a Done message to the host computer. If the tag buffer contains data, the reader sends an Error message to the host computer. Command 63 may be sent to clear the buffer. However, executing command 63 loses tag ID data. If this is unacceptable, allow the tag buffer to empty before re-issuing command 311. After executing command 311, the reader sends messages as mm%xx-y-zz-q, where mm is message data, xx is the reader ID (value can be set with command 60NN), y is the antenna number (value fixed at 0), zz is the number of reads of the previous tag, and q is status of input0 and input1. 40 Send All IDs Command 40, which is for diagnostic purposes only, tells the reader to transmit all IDs without regard for uniqueness. Uniqueness testing is bypassed and no data is buffered. The tag buffer must be empty before the reader accepts this command. If the tag buffer is empty, the reader executes command 40 and then sends a Done message to the host computer. If the tag buffer contains data, the reader sends an Error message to the host computer. After diagnostics is complete, reinstate the unique ID code criteria using command 410N.


410N Select Unique ID Code Criteria Command 410N directs the reader to select, buffer, and send IDs under certain conditions. An ID is buffered if, in the interval since the new ID was last received, previously decoded IDs have changed value at least N+1 times, or the uniqueness timeout has occurred. IDs that don't pass the test are lost. The factory default is command 4100, which selects a separation of one ID.

Command Uniqueness Criteria 4100 Separation of 1 ID 4101 Separation of 2 IDs 4102 Separation of 3 IDs 4103 Separation of 4 IDs

Each time the reader receives a tag ID, the uniqueness filter compares the ID with the contents of a comparison register. This register contains four items. Item1 is the most recent ID, but only if different from item2. Item2 is the second-most recent ID, but only if different from item3. Item3 is the third-most recent ID, but only if different from item4. Item4 is the fourth-most recent ID, but only if different from item1. When the uniqueness filter is set to a separation of one ID, the new ID is sent only if it is different from item1. When set to a separation of two IDs, the new ID is sent only if it is different from the first two items. The uniqueness test has a time limit. If an ID is buffered, it won't be accepted again until the specified time has elapsed, or until the receipt of the specified number of ID separations, or until other IDs reset uniqueness. After the reader executes command 410N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 410N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 4106, the reader sends it an Error message. 420N Valid ID Code Criteria Command 420N directs the reader to validate an ID received only after it has been obtained a specified number of times in sequence. Values for N are 0 through 3. The factory default is command 4200, which selects one valid ID code.

Command Code Criteria 4200 1 Valid ID Code 4201 2 Valid ID Codes 4202 3 Valid ID Codes 4203 4 Valid ID Codes


The validation procedure is executed before the unique ID test (the 410N commands). IDs that don't pass the validation test aren't reported. For example, command 4203 specifies that the same ID must be obtained from the antenna/RF module 4 times in succession before it is considered for the uniqueness test. This feature is useful in installations where RF reflections may cause a single tag to be read multiple times or where an occasional ID might be read from fringe areas. After the reader executes command 420N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 420N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 4206, the reader sends it an Error message. 43 Buffer All IDs Command 43, which is for diagnostic purposes only, buffers and transmits all received IDs. It effectively cancels any uniqueness criteria previously set by select unique ID code criteria (command 410N). After the reader executes command 43, it sends a Done message to the host computer. After diagnostics is complete, reinstate the unique ID code criteria using command 410N. 440 Reset Uniqueness Command 440 resets all uniqueness filters. After the reader executes command 440, it sends a Done message to the host computer. 450 Disable Wiegand Mode Command 450 disables Wiegand mode. This is a factory default. (This feature is only available in readers having Wiegand capability. The SmartScan readers don't have this capability.) Command 451 enables Wiegand mode. After the reader executes command 450, it sends a Done message to the host computer. 451 Enable Wiegand Mode Command 451 enables Wiegand mode. (This feature is only available in readers having Wiegand capability. The SmartScan readers don't have this capability.) Command 450 disables Wiegand mode. After the reader executes command 451, it sends a Done message to the host computer.


452 Disable Tag Translation Mode Command 452 disables tag translation mode. This is a factory default. Incoming full-frame tags are directly converted to ASCII. They aren't translated from AAR format to ASCII. Command 453 enables tag translation mode. After the reader executes command 452, it sends a Done message to the host computer. 453 Enable Tag Translation Mode Command 453 enables tag translation mode. Specific data fields (such as owner ID and car number) are extracted from the tags, translated according to AAR standards, and converted to ASCII. Tags that aren't programmed in AAR format are directly converted to ASCII. The reader doesn't translate data from half-frame or dual-frame tags. Command 452 disables tag translation mode. After the reader executes command 453, it sends a Done message to the host computer. 46NN Set Wiegand Retransmit Interval Command 46NN sets the time delay to control the reader retransmission of Wiegand data of a tag remaining in the read zone. The factory default is 01 second (command 4601). The NN value specifies the time delay in seconds. Any hexadecimal value from 01 through FF (that is, from 1 through 255 seconds) is allowed for NN. Uppercase and lowercase characters are allowed. This feature is only available in readers having Wiegand capability. The SmartScan readers don't have this capability. After the reader executes command 46NN, it sends a Done message to the host computer. If valid hexadecimal digits aren't substituted for NN in command 46NN, the reader sends an Error message to the host computer. 48N Select Dual-Frame-Tag Processing Mode Command 48N selects the dual-frame-tag processing mode. Dual-frame tags consist of an A frame and a B frame. The dual-frame-tag processing mode selected determines what frame is used to reset uniqueness and what frame or frames are sent to the host computer. The factory default is command 480, which resets uniqueness on A frame and sends A frame. The handshake count for a dual-frame tag equals the number of A frame handshakes plus the number of B frame handshakes. (Command 536 displays the selected dual-frame-tag processing mode.)


The value for N specifies the processing mode as follows:

Command Processing Mode 480 reset uniqueness on A, send A 481 reset uniqueness on B, send B 482 reset uniqueness on A, send both A and B 483 reset uniqueness on B, send both A and B

After the reader executes command 48N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 48N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 486, the reader sends it an Error message. 505 Display Software Version Command 505 displays the reader model number, software version information, and assigned serial number. The reader sends Model xxxxx Ver yyyy SNzzzzzz, where xxxxx is the model nomenclature, yyyy is the software version number, and zzzzzz is the serial number assigned to the reader being used (with the first two digits representing the year). 506 Display Hardware Configuration Information Command 506 displays hardware configuration information stored into the reader memory during system testing. After the reader executes command 506, it sends an ASCII string (from 1 to 20 characters in length) to the host computer. 520 Display Reader Power Fail Bit Command 520 displays the value of the reader power fail bit. The power fail bit changes from 0 to 1 when power to the reader is interrupted. To reset the bit, use reset reader (command 63) or reset power fail bit (command 65). On initial power up, the host computer sends one of these two commands to clear the power fail bit. If no power failure was detected, the reader sends PWRB P0 R0 to the host computer. If power failure was detected, the reader sends PWRB P1 R0 to the host computer.


521 Display Reader ID Number Command 521 displays the reader ID that is sent in the auxiliary information field. After the reader executes command 521, it sends RDID xx, where xx is a hexadecimal value from 00 through FF. 522 Display Communication Port Parameters Command 522 displays the selected communication port parameters, including the baud rate (command 100N), the number of stop bits (command 1010 or command 1011), the parity scheme (command 102N), and the end-of-line delay. After the reader executes command 522, it sends MAIN B<0-7> S<0-1> P<0-2> D0, where: B0 110 bits per second B1 300 bits per second B2 1200 bits per second B3 2400 bits per second B4 4800 bits per second B5 9600 bits per second (factory default) B6 19,200 bits per second B7 38,400 bits per second S0 one stop bit (factory default) S1 two stop bits P0 no parity (factory default) P1 even parity P2 odd parity D0 0-millisecond end-of-line delay (fixed) For example, if factory defaults are assigned, the reader sends MAIN B5 S0 P0 D0 to the host computer. The information sent in response to command 522 applies to data mode and command mode operation only. In download mode, default communication parameters are used. 524 Display Appended Information Status Command 524 displays the information being appended to the reader transmissions. Appended information is selected using command 302 (to append time and date) and command 311 (to append auxiliary information).


After the reader executes command 524, it sends IDAP T<0-1> D<0-1> X<0-1>, where: T0 time not appended T1 time appended (factory default) D0 date not appended D1 date appended (factory default) X0 auxiliary information not appended (factory default) X1 auxiliary information appended For example, if factory defaults are assigned, the reader sends IDAP T1 D1 X0 to the host computer. Time and date are appended. Auxiliary information isn't appended. Time and date may be appended to IDs, error messages, presence without tag reports, and input status change reports. Auxiliary information may only be appended to IDs, presence without tag reports, and input change reports. 525 Display Communication Protocol Status Command 525 displays selected communication protocol (command 61N), selected mode of flow control (command 614N), and ECP timeout (command 612NN). After the reader executes command 525, it sends ECPS P<0-2> T<01-FF> X<0-2>, where: P0 basic protocol enabled (factory default) P1 ECP enabled P2 data inquiry protocol enabled T01 ECP timeout of 50 milliseconds, which is 01 times 50 milliseconds T02 ECP timeout of 100 milliseconds, which is 02 times 50 milliseconds T03 ECP timeout of 150 milliseconds, which is 03 times 50 milliseconds • • • TFD ECP timeout of 12,650 milliseconds, which is 253 times 50 milliseconds TFE ECP timeout of 12,700 milliseconds (factory default) TFF ECP timeout disabled X0 flow control disabled X1 software flow control enabled (factory default) X2 hardware flow control enabled For example, if factory defaults are assigned, the reader sends ECPS P0 TFE X1 to the host computer.


526 Display I/O Status Command 526 displays the current input/output status. The reader message indicates whether outputs are being controlled externally by the host computer through output control commands (620N) or internally through predefined output mode (command 621). It also displays the status of two outputs, two inputs, and the selected output pulse duration (command 67N). After the reader executes command 526, it sends IOST C<0-1> O<0-3> I<0-3> D<0-F>, where: C0 host controls outputs C1 predefined output mode O0 both outputs off (both 0 VDC) O1 output0 on, output1 off O2 output0 off, output1 on O3 both outputs on (both 5 VDC) I0 both inputs false (both 0 VDC) I1 input0 true, input1 false I2 input1 true, input0 false I3 both inputs true (both 5 VDC) D0 4 milliseconds output pulse duration D1 8 milliseconds output pulse duration D2 12 milliseconds output pulse duration D3 16 milliseconds output pulse duration D4 20 milliseconds output pulse duration D5 24 milliseconds output pulse duration D6 32 milliseconds output pulse duration D7 40 milliseconds output pulse duration D8 48 milliseconds output pulse duration D9 60 milliseconds output pulse duration DA 76 milliseconds output pulse duration DB 152 milliseconds output pulse duration DC 228 milliseconds output pulse duration (factory default) DD 300 milliseconds output pulse duration DE 376 milliseconds output pulse duration DF 752 milliseconds output pulse duration The table below shows the voltage of output0 and output1 based on the current status of the outputs.

Output Status

Output0 (Pin 11)

Output1 (Pin 12)

O0 0 VDC 0 VDC O1 5 VDC 0 VDC O2 0 VDC 5 VDC O3 5 VDC 5 VDC


The table below shows the voltage of input0 and input1 based on the current status of the outputs.

Input Status

Input0 (Pin 16)

Input1 (Pin 17)

I0 0 VDC 0 VDC I1 5 VDC 0 VDC I2 0 VDC 5 VDC I3 5 VDC 5 VDC

527 Display RF Status Command 527 displays the status of the RF module. The reader response indicates whether RF is controlled externally by the host computer (command 6400 or command 6401) or internally by input0 (command 641). It also displays the current RF status and the uniqueness timeout, which is fixed at two minutes. After the reader executes command 527, it sends RFST C<0-1> O<0-1> T1, where: C0 RF controlled by host computer C1 RF controlled by presence detector on input0 (factory default) O0 RF off O1 RF on T1 uniqueness timeout of two minutes (fixed) For example, if factory defaults are assigned, the reader sends RFST C1 O0 T1 to the host computer. 529 Display Presence Input Status Command 529 displays the parameters associated with presence detection and RF control. The reader's message indicates if presence without tag reports are enabled or disabled (command 690N), if input inversion is enabled (command 6941) or disabled (command 6940), and the minimum presence true period (always true). It also reports the selected RF timeout (command 693N) and the selected means of RF-off control (command 692N). If presence without tag reports is enabled (command 6901), the reader sends a report if a presence is detected without the subsequent acquisition of a valid tag.


After the reader executes command 529, it sends PRST P<0-1> D0 A<0-2> T<0-F> I<0-1>, where: P0 presence without tag reports disabled (factory default) P1 presence without tag reports enabled D0 minimum presence true period of 0 milliseconds (fixed) A0 RF-off on timeout only A1 RF-off on timeout or tag A2 RF-off on timeout or presence condition false (factory default) T0 RF timeout of 0 milliseconds (always expired) T1 RF timeout of 4 milliseconds T2 RF timeout of 8 milliseconds T3 RF timeout of 12 milliseconds T4 RF timeout of 20 milliseconds T5 RF timeout of 24 milliseconds T6 RF timeout of 32 milliseconds T7 RF timeout of 48 milliseconds T8 RF timeout of 60 milliseconds T9 RF timeout of 92 milliseconds TA RF timeout of 152 milliseconds TB RF timeout of 300 milliseconds TC RF timeout of 452 milliseconds TD RF timeout of 600 milliseconds TE RF timeout of 752 milliseconds TF infinite, never expires (factory default) I0 input inversion disabled (factory default) I1 input inversion enabled For example, if factory defaults are assigned, the reader sends PRST P0 D0 A2 TF I0 to the host computer. 530 Display RF0 Filter Status Command 530 displays the parameter set for the RF channel input, including the selected unique ID code criteria (command 410N) and the valid ID code criteria, which are fixed at one acquisition.


After the reader executes command 530, it sends RF0S U<0-5> V<0-3> T<1-3>, where: U0 one ID separation (factory default) U1 two ID separations U2 three ID separations U3 four ID separations U4 send all IDs U5 buffer all IDs V0 one acquisition for valid ID (factory default) V1 two acquisitions for valid ID V2 three acquisitions for valid ID V3 four acquisitions for valid ID T1 variable timeout of 2 minutes (factory default) T2 variable timeout of 15 seconds T3 variable timeout of 30 seconds For example, if factory defaults are assigned, the reader sends RF0S U0 V0 T1 to the host computer. 532 Display Wiegand Mode Status Command 532 displays Wiegand mode status, enabled or disabled. (This feature is only available in readers having Wiegand capability. The SmartScan readers don't have this capability.) If Wiegand mode is disabled, the reader sends TOF 0 to the host computer. If Wiegand mode is enabled, the reader sends TOF 1 to the host computer. 533 Display Wiegand Retransmit Interval Command 533 displays the Wiegand retransmit interval. (This feature is only available in readers having Wiegand capability. The SmartScan readers don't have this capability.) Command 46NN sets the time delay to control the reader retransmission of Wiegand data of a tag remaining in the read zone. The factory default is one second. After the reader executes command 533, it sends WTI nn, where nn is number of seconds (01-FF). 534 Display Tag Translation Mode Status Command 534 displays tag translation mode status, enabled or disabled. (Command 452 disables tag translation mode. Command 453 enables tag translation mode.) If enabled, incoming full-frame tags in AAR format are translated according to ISO standards. If tag translation mode is disabled, the reader sends TT 0 to the host computer. If it is enabled, the reader sends TT 1 to the host computer.


535 Display Buffer Control Mode Status Command 535 displays buffer control mode (BCM) status, enabled or disabled. Command 6160 disables BCM. Command 6161 enables BCM. If buffer control mode is disabled, the reader sends BCM 0 to the host computer. If it is enabled, the reader sends BCM 1 to the host computer. 536 Display Dual-Frame-Tag Processing Mode Command 536 displays the selected dual-frame-tag processing mode. The mode used determines which frame of a dual-frame tag resets uniqueness and which frame or frames are sent to the host computer. Command 48N selects the dual-frame-tag processing mode. After the reader executes command 536, it sends DUAL n, where n is: 0 reset uniqueness on A, send A 1 reset uniqueness on B, send B 2 reset uniqueness on A, send both A and B 3 reset uniqueness on B, send both A and B 537 Display Echo Mode Status Command 537 displays echo mode status. In basic protocol (command 610) and data inquiry protocol (command 613), the reader may be configured to enable (command 6171) or disable (command 6170) the echo of received commands. If echo status is disabled, the reader sends ECHO 0 to the host computer. If it is enabled, the reader sends ECHO 1 to the host computer. 540 Display Flash Checksum Command 540 displays the flash memory checksum. After the reader executes command 540, it sends PCKS I0000 Exxxx, where xxxx is the four-byte ASCII representation of the boot ROM checksum. 543 Display Boot Checksum Command 543 displays the boot ROM checksum. After the reader executes command 543, it sends BCKS xxxx, where xxxx is the four-byte ASCII representation of the boot ROM checksum.


550 Display Periodic Check Tag Status Command 550 displays parameters for the periodic check tag function. The periodic check tag function can be enabled (command 8120) or disabled (command 810). The check tag interval is fixed at 30 minutes. While a system check tag test is being done (command 8110), the periodic check tag function is disabled. If the periodic check tag is disabled, the reader sends SCTS M0 T5 to the host computer. If the periodic check tag is enabled, the reader sends SCTS M1 T5 to the host computer. 551 Display Selected Check Tag Option Command 551 displays the selected check tag option. (Command 8160 selects the internal check tag option. This is a factory default. Command 8161 selects the external check tag option.) If the internal check tag is enabled, the reader sends CTAG 0 to the host computer. If the external check tag is enabled, the reader sends CTAG 1 to the host computer. 560 Display Input Status Change Report Options Command 560 displays the input status change reporting options. Status change reporting may be disabled by command 82N. After the reader executes command 560, it sends SSTC E<0-1> M<0-3>, where: E0 input status change reports disabled (factory default) E1 input status change reports enabled M0 reporting disabled (factory default) M1 changes on input0 reported M2 changes on input1 reported M3 changes on either input reported For example, if factory defaults are assigned, the reader sends SSTC E0 M0 to the host computer. 60NN Set Reader ID Number Command 60NN sets the reader ID that is sent in the auxiliary data field (command 311). The factory default is 00 (command 6000). The NN value specifies the reader ID. Any hexadecimal value from 00 through FF is allowed for NN. Uppercase and lowercase characters are allowed. After the reader executes command 60NN, it sends a Done message to the host computer. If valid hexadecimal digits aren't substituted for NN in command 60NN, the reader sends an Error message to the host computer.


610 Select Basic Protocol Command 610 selects the basic protocol. This is a factory default. (Command 611 selects the error correcting protocol. Command 613 selects the data inquiry protocol.) After the reader executes command 610, it sends a Done message to the host computer. 611 Select Error Correcting Protocol Command 611 selects the ECP. (Command 610 selects the basic protocol. This is a factory default. Command 613 selects the data inquiry protocol.) Don't switch to ECP (command 611) unless the host is prepared to acknowledge each reader transmission. After the reader executes command 611, it sends a Done message to the host computer. 612NN Select ECP Timeout Period Command 612NN selects the timeout interval for ECP. This timeout applies to the transmission of tag, report, and error messages and must be acknowledged by the host computer. The transmit timeout is initiated immediately after the end-of-message sequence CR/LF is sent. If the host doesn't acknowledge the message within the specified interval, the reader times out and then resends the message. The receive timeout is initiated upon receipt of the start-of-message character. If the end-of-message character isn't received within the specified interval, the reader discards the partially received message and then resets its receiver. The factory default is FE (command 612FE). The NN value specifies the timeout interval for ECP. Any hexadecimal value from 01 through FF is allowed for NN. Uppercase and lowercase characters are allowed. 61201 ECP timeout of 50 milliseconds, which is 01 times 50 milliseconds 61202 ECP timeout of 100 milliseconds, which is 02 times 50 milliseconds 61203 ECP timeout of 150 milliseconds, which is 03 times 50 milliseconds • • • 612FD ECP timeout of 12,650 milliseconds, which is 253 times 50 milliseconds 612FE ECP timeout of 12,700 milliseconds (factory default) 612FF ECP timeout disabled After the reader executes command 612NN, it sends a Done message to the host computer. If valid hexadecimal digits aren't substituted for NN in command 612NN, the reader sends an Error message to the host computer. If the specified timeout (NN) is too short for the current baud rate, the reader sends an Error message to the host computer.


613 Select Data Inquiry Protocol Command 613 selects the data inquiry protocol. (Command 610 selects the basic protocol. This is a factory default. Command 611 selects the error correcting protocol.) After the reader executes command 613, it sends a Done message to the host computer. 614N Select Flow Control Option Command 614N selects the flow control option for reader-to-host communications. The factory default is software flow control enabled (command 6141). In download mode, flow control isn't host-selectable. It is fixed at the default setting. However, during data mode and command mode operation, these flow control options are available.

Command Flow Control Option 6140 Disable flow control 6141 Enable software flow control 6142 Enable hardware flow control

After the reader executes command 614N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 614N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 6144, the reader sends it an Error message. If the reader is configured for software flow control, it stops sending when it receives an XOFF character. It doesn't resume sending until it receives an XON character. If the reader is configured for hardware flow control, it stops transmission when it detects that the CTS line is no longer asserted. It resumes transmission when this line is asserted again. Flow control should be disabled while using the ECP. 6160 Disable Buffer Control Mode Command 6160 disables BCM. This is a factory default. Buffer control is an ECP option that prevents unsolicited (asynchronous) reader transmissions. If buffer control isn't active, the reader sends data to the host computer when the data is received. The host computer must acknowledge the data. Command 6161 enables BCM. After the reader executes command 6160, it sends a Done message to the host computer.


6161 Enable Buffer Control Mode Command 6161 enables BCM. Buffer control is an ECP option that prevents asynchronous reader transmissions. When buffer control is enabled using command 6161, the reader sends only in response to command 06, send buffer entry. The exception to this rule occurs on startup when the reader sends its sign-on message asynchronously. Command 6160 disables BCM. If BCM is enabled, the host must request tag IDs and reports from the reader using command 06. If the reader receives this command and it has data in its buffer, it sends the buffered message of highest priority (tag IDs first and then reports). If the reader's buffer is empty, it sends a Done message instead. The reader returns an Error message if it receives command 06 when BCM isn't enabled. If BCM is enabled, the reader won't support ECP ACK or NAK messages from the host. Since all messages are sent in response to a host command, acknowledgment from the host isn't required. Instead, the ECP sequence numbers are used to ensure data integrity. If the host receives an erroneous reader message, it should resend command 06 with the same sequence number. This causes the reader to search and replace its previous message. If BCM is enabled, the reader won't use the timeout to trigger retransmission of data because in buffer control, reader data is sent only when requested by the host. After the reader executes command 6161, it sends a Done message to the host computer. 6170 Disable Echo Command 6170 disables the reader's echo of received host commands. If operating in basic protocol or data inquiry protocol, the reader echoes by default. As the reader receives a host command, it echoes each character of the command. Once the entire command has been received and processed, the reader sends its response. If echoing is disabled with command 6170, the reader won't echo the command but only sends its response. In ECP or download mode, the reader never echoes. After the reader executes command 6170, it sends a Done message to the host computer. 6171 Enable Echo Command 6171 enables the reader's echo of received host commands. This is a factory default. Command 6170 disables the reader's echo. After the reader executes command 6171, it sends a Done message to the host computer.


620N Output Control Command 620N provides direct control of two output lines that may be used to operate external hardware, such as gates or traffic lights. This command disables predefined output mode (command 621). The value for N specifies the output state requested as follows:

Command Output Control Option 6200 Turn off output0 and output1 6201 Turn on output0, turn off output1 6202 Turn on output1, turn off output0 6203 Turn on output0 and output1

After the reader executes command 620N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 620N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 6206, the reader sends it an Error message. If either Wiegand mode (command 451) or the external check tag option (command 8161) is enabled, the host computer can't directly control output1. The SmartScan readers don't have Wiegand capability.) 621 Select Predefined Output Mode Command 621 configures the reader for predefined output mode. (This is a factory default.) In this mode, both output lines, output0 and output1, are asserted upon receipt of a valid unique tag ID. The output line remains asserted for the time specified by output pulse duration (command 67N). Any direct control command (620N) disables the predefined output mode. After the reader executes command 621, it sends a Done message to the host computer. If the predefined output modes enabled, the reader won't assert output1 upon receipt of a tag ID if Wiegand mode is enabled (command 451) or if the external check tag option is enabled (command 8161).


63 Reset Reader Command 63 resets the power fail bit, clears all buffers, resets tag uniqueness, turns off both-output lines, sends the sign-on message, and returns to data mode. All buffered data is lost when command 63 is executed. After the reader executes command 63, it sends the sign-on message. On the host computer, lines like these appear. The contents of your sign-on message will be different.


The format of the first line is Model xxxxx Ver yyyy SNzzzzzz, where xxxxx is the model nomenclature, yyyy is the software version number, and zzzzzz is the serial number assigned to the reader being used (with the first two digits representing the year). 6400 Turn Off RF Power Command 6400 directly controls the RF module, turning off RF power. Either this command or command 6401 overrides RF-by-input control. After the reader executes command 6400, it sends a Done message to the host computer. 6401 Turn On RF Power Command 6401 directly controls the RF module, turning on RF power. Either this command or command 6400 overrides RF-by-input control. After the reader executes command 6401, it sends a Done message to the host computer. 641 Select RF-By-Input Control Command 641 configures the reader for RF-by-input control. This is a factory default. The reader turns RF on when it detects a presence through input0. The reader turns RF off according to the selected RF control algorithm command 692N. After the reader executes command 641, it sends a Done message to the host computer.


642NN Select RF Operating Frequency

CAUTION The authorized frequency band in the USA is 902 to 904 MHz and 909.75 to 921.75 MHz.

Command 642NN sets the reader RF frequency from 902 to 028 MHz in 500-kHz steps, where NN is a hexadecimal value from 00 to 34. There is no default frequency value. After the reader's frequency is set, the value is stored in battery-backed RAM (that is, in nonvolatile RAM, NVRAM). This value is not altered by power-down, loading default parameters, or a flash download or new software. Issuing another 624NN command can only change it. If the NVRAM becomes corrupted, the correct operating frequency cannot be guaranteed. If this happens, the RF section shuts down and the reader sends an Error message (Error06) to the host. Until the frequency is reset using the 624NN command, the unit displays the same Error message every time it is powered up or when an attempt is made to enable the RF by host or by external sensor. Below are the commands to set the operating frequency. Command

Operating Frequency in MHz

Approved for Use in the USA

62600 902 Yes 62601 902.5 Yes 62602 903 Yes 62603 903.5 Yes 62604 904 Yes 62605 904.5 No 62606 905 No 62607 905.5 No 62608 906 No 62609 906.5 No 6260A 907 No 6260B 907.5 No 6260C 908 No 6260D 908.5 No 6260E 909 No 6260F 909.5 No 62610 910 Yes 62611 910.5 Yes 62612 911 Yes 62613 911.5 Yes


Command

Operating Frequency in MHz

Approved for Use in the USA

62614 912 Yes 62615 912.5 Yes 62616 913 Yes 62617 913.5 Yes 62618 914 Yes 62619 914.5 Yes 6261A 915 Yes 6261B 915.5 Yes 6261C 916 Yes 6261D 916.5 Yes 6261E 917 Yes 6261F 917.5 Yes 62620 918 Yes 62621 918.5 Yes 62622 919 Yes 62623 919.5 Yes 62624 920 Yes 62625 920.5 Yes 62626 921 Yes 62627 921.5 Yes 62628 922 No 62629 922.1 No 6262A 923 No 6262B 923.5 No 6262C 924 No 6262D 924.5 No 6262E 925 No 6262F 925.5 No 62630 926 No 62631 926.5 No 62632 927 No 62633 927.5 No 62634 928 No

After the reader executes command 642NN, it sends a Done message to the host computer.


643NN Select RF Operating Range (Distance) Command 643NN selects the read range where NN is a hexadecimal value from 00 to 1F. The range increases with increasing NN value. The RF output range can be adjusted for 32 discrete values, show below: 00 08 10 18 01 09 11 19 02 0A 12 1A 03 0B 13 1B 04 0C 14 1C 05 0D 15 1D 06 0E 16 1E 07 0F 17 1F where 00 is the shortest range and 1F is the longest range. The default range value is 1F. After the reader executes command 643NN, it sends a Done message to the host computer. 65 Reset Power Fail Bit Command 65 resets the power fail bit to 0. (The bit changes from 0 to 1 when power is restored to the reader.) Upon reader power up, the host sends either this command or command 63 to initialize this bit. Command 520 displays the value of the reader power fail bit. After the reader executes command 65, it sends a Done message to the host computer. 660 Test External RAM Command 660 does a read-and-write test of external data memory. The contents of RAM aren't disturbed by this test. Command 660 updates information displayed by the display diagnostic results (command 661). If passed RAM test, the reader sends a Done message to the host computer. If failed RAM test, the reader sends an Error message to the host computer. 661 Display Diagnostic Results Command 661 displays the results of previous diagnostics. The information displayed by this command is updated when the reader receives any diagnostic command. This information is preserved after power down. Command 669 updates every field in this message. If diagnostics have never been done, the information displayed by this command isn't predictable.


After the reader executes command 560, it sends DIAG R<0-1> E<0-1> D<0-1> C<0-1>, where: R0 boot ROM OK R1 boot failed E0 flash memory OK E1 flash memory failed D0 external RAM OK D1 external RAM failed C0 real-time clock OK C1 real-time clock failed 664 Test Real-Time Clock Command 664 tests the real-time clock (RTC). The reader tests the RTC by retrieving both the date and time and verifying their validity. This command updates information displayed by the display diagnostic results command 661. If real-time clock is okay, the reader sends a Done message to the host computer. If real-time clock failed test, the reader sends an Error message to the host computer. 667 Verify Boot ROM Checksum Command 667 calculates and verifies the boot ROM checksum. This command updates information displayed by the display diagnostic results command 661. If boot ROM is okay, the reader sends a Done message to the host computer. If boot ROM failed test, the reader sends an Error message to the host computer. 668 Verify Flash Memory Checksum Command 668 calculates and verifies the flash memory checksum. This command updates information displayed by the display diagnostic results command 661. If flash memory is okay, the reader sends a Done message to the host computer. If flash memory failed test, the reader sends an Error message to the host computer.


669 Do All Diagnostics Command 669 does a test on:

• External RAM

• Boot ROM

• Flash memory

• Real-time clock This command also initiates a system check tag operation and updates information that can be displayed with command 661. If all tests passed, the reader sends a Done message to the host computer. If one or more tests failed, the reader sends an Error message to the host computer. 66F Load Default Operating Parameters Command 66F loads all the factory default operating parameters. If all parameters loaded okay, the reader sends a Done message to the host computer. If a parameter load failed, the reader sends an Error message to the host computer. 67N Set Output Pulse Duration Command 67N sets the output pulse duration for the predefined output mode command 621. This command specifies the time that output lines are asserted upon receipt of a valid and unique tag ID. The factory default is 228 milliseconds (command 67C).


The variable N specifies an output pulse duration of from 4 to 752 milliseconds. (Actual pulse length output of the reader may vary from the specified value by up to four milliseconds.) Any hexadecimal value from 0 through F is allowed for N. Uppercase and lowercase characters are allowed.

Command Number

Delay in Milliseconds

670 4 671 8 672 12 673 16 674 20 675 24 676 32 677 40 678 48 679 60 67A 76 67B 152 67C 228 67D 330 67E 376 67F 752

Additional IDs may be received during the selected output pulse duration. However, the timing restarts upon each successive ID acquisition. This command should be used with discretion. For example, when the tag acquisition interval is short compared to the selected pulse duration, distinct pulses may not be generated. After the reader executes command 67N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 67N, the reader sends an Error message to the host computer. For example, if the host computer requests execution of command 67W, the reader sends it an Error message. 690N Select Presence Without Tag Report Option Command 690N selects the presence without tag reporting option. Command 6900 disables presence without tag reporting. This is a factory default. Command 6901 enables presence without tag reporting. If enabled, input reports are sent when a presence is detected without the subsequent acquisition of a valid tag. After the reader executes command 690N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 690N, the reader sends an Error message to the host computer.


692N Select RF Control Algorithm Command 692N selects the algorithm for turning off RF power when RF-by-input control is enabled using command 641. Command 6922 turns off RF power either after the timeout period or upon the presence false condition, whichever occurs first. This is a factory default. Command 6920 turns off RF power based on the timeout established by command 693N. Command 6921 allows RF power to be turned off either after the timeout period or upon acquisition of a valid tag ID, whichever occurs first. After the reader executes command 692N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 692N, the reader sends an Error message to the host computer. 693N Select RF Timeout Period Command 693N selects the RF timeout period used by RF control algorithm command 692N. Command 693F disables the RF timeout. This is a factory default. The reader turns off the RF immediately following the acquisition of a valid tag, whether or not it is unique. Values for N range from 0 through F.

Command Timeout in Milliseconds 6930 0 (always expired) 8931 4 8932 8 6933 12 8934 20 8935 24 8936 32 6937 48 6938 60 6939 92 693A 152 693B 300 893C 452 693D 600 693E 752 693F infinite (never expires)

After the reader executes command 693N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 693N, the reader sends an Error message to the host computer.


6940 Disable Input Inversion Command 6940 disables input inversion. This is a factory default. Command 6941 enables input inversion. After the reader executes command 6940, it sends a Done message to the host computer. 6941 Enable Input Inversion Command 6941 enables input inversion. When enabled, an active circuit input is interpreted as an inactive circuit and an inactive circuit input is interpreted as an active circuit. This feature allows greater flexibility in the attachment of external equipment to the reader inputs. Command 6940 disables input inversion. After the reader executes command 6941, it sends a Done message to the host computer. 695 Set Serial Number Command 695 assigns the reader serial number. Type the number with no spaces between characters. Entry format is 695ssssss, where ssssss is the serial number. The serial number may contain up to six ASCII alphanumeric characters. Uppercase or lowercase letters are allowed. The factory default serial number is 000000. Once assigned, the serial number is preserved during power down and the loading of default parameters. After the reader executes command 695, it sends a Done message to the host computer. 696 Store Hardware Configuration String Command 696 stores hardware configuration information into reader memory. Type the information with no spaces between characters. Entry format is 696ss...ss, where ss...ss is the hardware configuration string that may contain up to 20 ASCII alphanumeric characters. Uppercase or lowercase letters are allowed. Once assigned, configuration information is preserved during power down and the loading of default parameters. After the reader executes command 696, it sends a Done message to the host computer.


777 Report Buffered Handshake Data Command 777 reports buffered handshake data. After the reader executes command 777, it sends a simulated tag report with auxiliary data appended. The reader sends Buffered Handshakes %00-0-nn-1, where nn is the handshake count (that is, the total valid ID frames). 810 Disable Periodic Check Tag Command 810 disables the periodic operation of the system check tag. This is a factory default. Command 8120 enables the operation. After the reader executes command 810, it sends a Done message to the host computer. 8110 Do System Check Tag Test Command 8110 does a single system check tag test. (Command 810 disables the periodic operation of the system check tag. This is a factory default. Command 8120 enables the periodic operation of the system check tag.) It may be executed either in data mode or command mode. If the internal check tag option is selected using command 8160, internal check tag circuitry emits a single ID that is received and stored by the reader in the normal manner. If the external check tag is enabled, the reader asserts output1. If a real tag is in the field at the time, the check tag operation is stopped. After the reader executes command 8110, it sends a Done message to the host computer. 8120 Enable Periodic Check Tag Command 8120 enables the periodic operation of the system check tag. (Command 810 disables the operation. This is a factory default.) The reader does a system check tag test every 30 minutes. These tests continue until either command 810 or command 8110 is received. After the reader executes command 8120, it sends a Done message to the host computer. 8160 Select Internal Check Tag Command 8160 selects the internal check tag option. This is a factory default. Upon receiving either command 8110 or command 8120, the reader starts a check tag operation using internal check tag circuitry. This circuitry emits a single ID (system check tag) that is received and stored in the normal manner. After the reader executes command 8160, it sends a Done message to the host computer.


8161 Select External Check Tag Command 8161 selects the external check tag option. Upon receiving command 8110 or 8120, the reader asserts output1. The external check tag used must be an AT5715 tag, field programmed as desired and connected to the output1 terminals. If the external check tag option is selected, the host isn't allowed to directly control the state of output1 with command 620N because output1 is used as a dedicated line for the check tag. Also, if predefined output mode is enabled (command 621), the reader asserts output0 only upon receiving a valid tag ID. It doesn't assert output1. After the reader executes command 8161, it sends a Done message to the host computer. If Wiegand mode is enabled, the reader sends an Error message to the host computer. This is because Wiegand mode and the external check tag option are mutually exclusive. Both the Wiegand mode and the external check tag option require the use of output1. 82N Select Input Status Change Report Option Command 82N selects the input lines to be monitored to report any change in input status. The enabled input lines are monitored for any changes in their logic states. If a change is detected, the reader generates an input status change message and treats it as a tag ID. If the auxiliary information option is enabled, the input status field displays the current input values. The factory default is disable status change reports (command 820). The values for N specify the following report options.

Command Report Option 820 Disable status change reports 821 Report change on input0 822 Report change on input1 823 Report changes on input0 and input1

After the reader executes command 82N, it sends a Done message to the host computer. If a valid hexadecimal digit isn't substituted for N in command 82N, the reader sends an Error message to the host computer. 90 Load One Record of a Program Command 90 transfers one Intel data record from an external host to the reader flash memory. (To load an entire program file into reader memory, you must issue one command 90 for each record of the program.) The flash memory must have been previously erased using command 96. Each Intel data record is a single line of ASCII characters, expressing bytes as hexadecimal pairs. Each Intel data record starts with a colon (hexadecimal 1A) and ends with a carriage return and linefeed (hexadecimal 0D0A).


The reader must be operating in download mode (command 05) before it accepts command 90. If an Intel data record has been received, stored, and verified with no errors detected, the reader sends a Done message to the host computer. If an error occurred during the transfer of the record, the reader sends a Read Error message. If an error occurred during the programming of the flash memory, the reader sends a Program Error message. If an error occurred during the verification of the programmed data, the reader sends a Verify Error message. 91 Verify Flash Checksum Command 91 calculates a checksum on a new program in flash memory and then compares it with the stored checksum. If the calculated checksum matches the stored checksum, the reader sends a Done message to the host computer. If the calculated checksum doesn't match the stored checksum, the reader sends an Error message to the host computer. 96 Erase Flash Memory Command 96 erases the flash memory. Once this command is executed, exit from download mode isn't possible until a new program is loaded into flash memory. After the reader executes command 96, it sends a Done message to the host computer. 97 Do Destructive Flash Test Command 97 does a test on the flash memory. Various patterns are programmed into the memory and verified. This test writes over any program previously stored in the flash memory. Therefore, a download of software is required afterwards. Once this command is executed, exit from download mode isn't possible until a new program is loaded into flash memory. If flash memory is okay, the reader sends a Done message to the host computer. If flash memory failed, the reader sends an Error message to the host computer. 99 Exit Download Mode Command 99 directs the reader to exit download mode. The reader re-executes startup to ensure proper initialization of the reader.


If the flash memory checksum verifies, the reader comes up in data mode and sends the sign-on message. On the host computer, lines like these appear. The contents of your sign-on message will be different.


If the flash memory checksum doesn't verify, the reader comes up in download mode and sends the sign-on message. On the host computer, lines like these appear. The contents of your sign-on message will be different.

#Model E4 Series Ver 0.00 #Copyright 2008 TransCore

Notice that the only difference between the two sign-on messages is the first line. If the flash memory checksum verifies, the first line is as shown below. Model xxxxx Ver yyyy SNzzzzzz where xxxxx is the model nomenclature, yyyy is the software version number, and zzzzzz is the serial number assigned to the reader being used. The serial number is expressed in decimal digits (0-9), with the first two digits representing the year. Serial number 000000 is the default setting and isn't a valid number. If this number appears in the sign-on message, either the battery has failed or the serial number has never been stored into reader memory. The appropriate serial number is assigned using command 695. If the flash memory checksum doesn't verify, the first line is as shown below.

Model xxxxx Ver 0.00 where xxxxx is the model nomenclature.


Appendix C — Tag Reporting Examples This appendix shows how to configure a reader for tag reads with seven different outcomes. Covered are decoding and not decoding AAR data; appending and not appending date and time; appending and not appending auxiliary information; and integrating and not integrating a multiplexer. The examples show tag reporting using tags programmed to the AAR standard, and several report configurations. The tag reporting configurations apply to all tags, even those programmed in six-bit ASCII or another data format. All examples of data configurations are available from the 2200-507SA Readers. For the first five examples, the readers aren't integrated with a 2200-700 Multiplexer. For the last two, they are. C.1 No Translation, No Date and Time, No Auxiliary Information The example below shows tag reads with tags programmed in AAR format and the reader not decoding the data. Date and time aren't appended. Auxiliary information isn't appended. Multiplexer isn't integrated. To read tags programmed in AAR format and not translate them to ASCII:

1 Be sure you are up and running.

Chapter 3 - Setup to Read Tags describes how to setup a 2200-507SA Reader to read tags.

2 To switch the reader to command mode, type #01


#Done

4 Type #6401



#Done

6 Type #452

Command 452 disables tag translation mode. Incoming full-frame tags are directly converted to ASCII. They aren't translated from AAR format to ASCII.



#Done

8 Type #300

Command 300 tells the reader to not append the time and date to transmitted IDs, error messages, presence without tag reports, and input status change reports.


#Done

10 Type #310

Command 310 tells the reader to not append auxiliary information to transmitted IDs, error messages, presence without tag reports, and input status change reports.


#Done

12 To switch the reader to data mode, type #00


#Done

14 Pass three AAR programmed tags in front of the antenna, one at a time.

Lines like these appear. The contents of your lines will be different. #FEZ>QXD QAD NAS #FEZ>_$@:QAD NAS #FVA/#Q!*QAD NAS

In the sample lines above, # is the start-of-message character followed by 20 ASCII characters of tag data. The first line is the first tag read. The last line is the third tag read.


C.2 Translation, No Date and Time, No Auxiliary Information The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time aren't appended. Auxiliary information isn't appended. Multiplexer isn't integrated. To read tags programmed in AAR format and translate them to ASCII:



2 Be sure your reader is in command mode.

Command 01 switches the reader to command mode.

3 Be sure RF power is turned on.


4 Type #453

Command 453 enables tag translation mode. Specific data fields (such as owner ID and car number) are extracted from the tags, translated according to AAR standards, and converted to ASCII. Tags that aren't programmed in AAR format are directly converted to ASCII. The reader doesn't translate data from half-frame or dual-frame tags.


#Done

6 Type #300



#Done

8 Type #310



#Done




#Done


Passing the same tags that where used in the first example, in the same order, in front of the antenna, yield lines like these. The contents of your lines will be different.

#19 EXXO 123456 0 #19 EXXO 987654 1 #19 STCA 246802 1

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, and side indicator (0 is left side; 1 is right side). No other information is decoded. The first line is the first tag read. The last line is the third tag read.

C.3 Translation, Date and Time, No Auxiliary Information The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time are appended. Auxiliary information isn't appended. Multiplexer isn't integrated. To read tags programmed in AAR format and translate them to ASCII:







4 To enable tag translation mode, type #453


#Done


6 Type #302

Command 302 tells the reader to append the time and date to transmitted IDs, error messages, presence without tag reports, and input status change reports.


#Done

8 Type #310



#Done



#Done



#19 EXXO 123456 0 &06:00:13.41 08/06/99 #19 EXXO 987654 1 &06:00:16.02 08/06/99 #19 STCA 246802 1 &06:00:18.25 08/06/99

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, side indicator (0 is left side; 1 is right side), time-and-date delimiter (&), time, and date. No other information is decoded. The first line is the first tag read. The last line is the third tag read.


C.4 Translation, Date and Time, Auxiliary Information The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time are appended. Auxiliary information is appended. Multiplexer isn't integrated. To read tags programmed in AAR format and translate them to ASCII:









#Done

6 Type #302



#Done

8 Type #311

Command 311 tells the reader to append auxiliary information to transmitted IDs, presence without tag reports, and input status change reports. Auxiliary information isn't appended to error messages.


#Done




#Done



#19 EXXO 123456 0 &06:00:13.41 08/06/99%00-0-37-1 #19 EXXO 987654 1 &06:00:16.02 08/06/99%00-0-16-1 #19 STCA 246802 1 &06:00:18.25 08/06/99%00-0-16-1

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, side indicator (0 is left side; 1 is right side), time-and-date delimiter (&), time, date, auxiliary-information delimiter (%), reader ID (00), antenna number (0), number of reads of the previous tag, current input sensor status (1). No other information is decoded. The first line is the first tag read. The last line is the third tag read.

C.5 Translation, No Date and Time, Auxiliary Information The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time aren't appended. Auxiliary information is appended. Multiplexer isn't integrated. To read tags programmed in AAR format and translate them to ASCII:









#Done


6 Type #300



#Done

8 Type #311



#Done



#Done



#19 EXXO 123456 0 %00-0-37-1 #19 EXXO 987654 1 %00-0-16-1 #19 STCA 246802 1 %00-0-16-1

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, side indicator (0 is left side; 1 is right side), auxiliary-information delimiter (%), reader ID (00), antenna number (0), number of reads of the previous tag, current input sensor status (1). No other information is decoded. The first line is the first tag read. The last line is the third tag read.


C.6 Integrated Multiplexer, Date and Time The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time are appended. Auxiliary information is appended. Multiplexer is integrated. To read tags programmed in AAR format and translate them to ASCII:









#Done

6 Type #302



#Done

8 Type #311



#Done




#Done

12 Pass five AAR programmed tags.

A reader with a multiplexer, having four connected antennas, produced lines like these. The contents of your lines will be different.

#19 EXXO 123456 0 &06:00:13.41 08/06/99%00-0-37-0 #19 EXXO 987654 1 &06:00:14.09 08/06/99%00-0-16-1 #19 STCA 246802 1 &06:00:14.10 08/06/99%00-0-16-3 #19 EXXO 321654 0 &06:00:14.22 08/06/99%00-0-22-2 #19 EXXO 827252 1 &06:00:14.24 08/06/99%00-0-18-1

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, side indicator (0 is left side; 1 is right side), time-and-date delimiter (&), time, date, auxiliary-information delimiter (%), reader ID (00), antenna number (0), number of reads of the previous tag, which antenna read this tag. No other information is decoded.

When a multiplexer is implemented with four antennas connected, the last digit of the tag line varies from zero to three. For example, when 0, the tag was read by the antenna connected to multiplexer channel 1. When 2, the tag was read by the antenna connected to channel 3.

In the example above, the first line is the first tag read by the antenna connected to the multiplexer channel 1. The antenna on channel 2 read the tags in the second and fifth lines. The third line is the first tag read by the antenna on channel 4. The fourth line is the first tag read by the antenna on channel 3.

C.7 Integrated Multiplexer, No Date and Time The example below shows tag reads with tags programmed in AAR format and the reader decoding the data. Date and time aren't appended. Auxiliary information is appended. Multiplexer is integrated.


To read tags programmed in AAR format and translate them to ASCII:









#Done

6 Type #300



#Done

8 Type #311



#Done



#Done


12 Pass five AAR programmed tags.

A reader with a multiplexer, having four connected antennas, produced lines like these. The contents of your lines will be different.

#19 EXXO 123456 0 %00-0-37-0 #19 EXXO 987654 1 %00-0-16-1 #19 STCA 246802 1 %00-0-16-3 #19 EXXO 321654 0 %00-0-22-2 #19 EXXO 827252 1 %00-0-18-1

In the sample lines above, # is the start-of-message followed by the equipment group code (19 is railcar), owner's initials, identification number, side indicator (0 is left side; 1 is right side), auxiliary-information delimiter (%), reader ID (00), antenna number (0), number of reads of the previous tag, which antenna read this tag. No other information is decoded.

When a multiplexer is implemented with four antennas connected, the last digit of the tag line varies from zero to three. For example, when 0, the tag was read by the antenna connected to multiplexer channel 1. When 2, the tag was read by the antenna connected to channel 3.

In the example above, the first line is the first tag read by the antenna connected to the multiplexer channel 1. The antenna on channel 2 read the tags in the second and fifth lines. The third line is the first tag read by the antenna on channel 4. The fourth line is the first tag read by the antenna on channel 3.


Index This section lists the page numbers for keywords and phrases used in this guide. 110-120 VAC, 11, 13, 28 12 VDC, 13, 37 19,200 baud rate, 57, 58, 64, 72 2200-507SA Reader, 5, 9, 11, 12, 13, 14, 27, 28, 30, 97, 99, 100, 102, 103, 105, 107 2200-700 Multiplexer, 5, 9, 11, 31, 32, 33, 35, 37, 38, 39, 40, 41, 97 24-hour format, 28, 65 5 VDC, 11, 13, 35, 37, 39, 74, 75 9600 baud rate, 17, 22, 27, 56, 57, 58, 63, 64, 72 AAR (Association of American Railroads), 7, 8, 11, 70, 77, 97-108 ACK (hexadecimal 06), 50, 52, 53, 82 acknowledge control character (hexadecimal 06), 50, 52, 53, 82 active tags, 6 address of STC, 10, 47 AEI (automatic equipment identification), 5, 6, 7, 8, 9, 11 AEI tags, 6, 7, 9 American National Standard Code for Information Interchange (ASCII), 7, 8, 19, 20, 23, 49, 50, 51, 52,

58, 60, 70, 71, 78, 92, 94, 97, 98, 99, 100, 102, 103, 105, 107 American Trucking Association (ATA), 7, 8, 11, 49 amperes, 37 antenna, 5, 6, 8, 27, 30, 34, 35, 43, 44, 45, 46, 67, 69, 98, 100, 101, 103, 104, 106, 108 ASCII (American National Standard Code for Information Interchange), 7, 8, 19, 20, 23, 49, 50, 51, 52,

58, 60, 70, 71, 78, 92, 94, 97, 98, 99, 100, 102, 103, 105, 107 asset management, 8 Association of American Railroads (AAR), 7, 8, 11, 70, 77, 97, 98, 99, 100, 101, 102, 103, 104, 105,

106, 107, 108 AT5110, 7 AT5118, 7 AT5125, 7 AT5707, 7 ATA (American Trucking Association), 7, 8, 11, 49 automatic equipment identification (AEI), 5, 6, 7, 8, 9, 11 auxiliary information, 30, 35, 39, 49, 57, 58, 67, 72, 73, 94, 97, 98, 99, 101, 102, 104, 105, 107 basic protocol, 16, 18, 19, 22, 49, 51, 52, 58, 60, 63, 73, 78, 80, 81, 82 batteries, 6, 7, 20, 25, 85, 96 battery-powered tags, 7 baud rate, 16, 17, 22, 27, 52, 56, 57, 63, 64, 72, 80 BCKS (boot checksum), 60, 78 BCM (buffer control mode), 60, 63, 64, 78, 81, 82 beam-powered tags, 7 boot checksum (BCKS), 60, 78 buffer control mode (BCM), 60, 63, 64, 78, 81, 82 buffer overflow, 15 business hours of STC, 47


carriage-return control character (hexadecimal 0D), 80 carrier wave, 6 cautions, dangers, warnings, 2, 85 channel, 9, 11, 31, 35, 36, 37, 39, 40, 41, 76, 106, 108 channel input status, 40, 41 check tag, 15, 55, 56, 60, 62, 79, 83, 89, 93, 94 checking on shipments and orders, 48 checksum, 22, 24, 26, 60, 61, 62, 78, 88, 95, 96 clear to send (CTS), 13, 17, 81 coaxial cables, 27 COM1, 27 COM2, 27 comment on this guide, 10 computer, 5, 6, 7, 8, 11, 15-25, 27-30, 49, 50, 51, 52, 53, 54, 55, 56, 59, 63, 64, 65, 66, 67, 68, 69, 70,

71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 continuous mode, 31, 36, 39 CRC (cyclic redundancy check), 19, 20, 49, 50, 51, 52, 53, 54 CTS (clear to send), 13, 17, 81 customer service, 47 cyclic redundancy check (CRC), 19, 20, 49, 50, 51, 52, 53, 54 dangers, warnings, cautions, 2, 85 Data Communication Equipment, 27 data connector, 13, 37 data inquiry protocol, 18, 20, 49, 51, 58, 60, 73, 78, 80, 81, 82 data mode, 15, 16, 18, 19, 20, 22, 24, 25, 28, 29, 51, 53, 55, 57, 63, 72, 81, 84, 93, 96, 98, 100, 101,

102, 104, 105, 107 date and time, 28, 30, 57, 66, 72, 88, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107 DB-25, 11, 13, 36, 37, 40 defects, 8, 11, 47 demand mode, 31, 39 diagnostics, 19, 61, 67, 69, 87 disclaimers, 9 download mode, 22, 23, 24, 25, 26, 57, 62, 63, 72, 81, 82, 95, 96 dual-frame tags, 70, 78, 99 dynamic tags, 7 echo, 22, 50, 52, 56, 60, 63, 78, 82 ECP status, 58, 73 end-of-message (EOM) control characters (hexadecimal 0D0A), 19, 20, 23, 49-54, 80, 94 EOM (end-of-message), 19, 20, 23, 49, 50, 51, 52, 53, 54, 80, 94 error correcting protocol, 16, 17, 18, 19, 49, 50, 51, 52, 53, 56, 58, 60, 63, 64, 73, 80, 81, 82 error message, 18, 19, 20, 22, 24, 28, 29, 49, 53, 63, 64, 65, 66, 67, 68, 69, 70, 71, 73, 79, 80, 81, 82,

83, 85, 87, 88, 89, 90, 91, 94, 95, 98, 99, 101, 102, 104, 105, 107 Error02, 20 Error03, 20 Error04, 20 Error05, 20 Error06, 85 fax number of STC (423-499-0045), 2, 10, 47 FCC license requirements, 13 flash checksum, 22, 24, 60, 62, 78, 95 flash memory, 22, 23, 24, 26, 61, 62, 63, 78, 88, 94, 95, 96


flow control, 5, 17, 18, 19, 22, 56, 58, 60, 63, 73, 81 four-antenna application, 45, 46 four-channel operational mode, 41 ground, 13, 35, 37, 39 hardware flow control, 17, 18, 58, 60, 73, 81 host addressed failure conditions, 54 host computer, 5, 6, 7, 8, 11, 15-25, 49, 50, 51, 52, 53, 54, 55, 56, 59, 63, 64, 65, 66, 67, 68, 69, 70, 71,

72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 host transmissions, 51 how to comment on this guide, 10 how to order more copies of this guide, 10 I/O status (IOST), 59, 74 input circuits, 21 input control, 56, 59, 61, 84, 91 input0, 13, 15, 21, 59, 60, 62, 67, 74, 75, 79, 84, 94 input1, 13, 15, 21, 37, 40, 41, 59, 60, 62, 67, 74, 75, 79, 94 input2, 37, 40, 41 input3, 37, 40, 41 input4, 37, 41 International Standardization Organization (ISO), 7, 8, 11, 77 IOST (I/O status), 59, 74 ISO (International Standardization Organization), 7, 8, 11, 77 J1, 35, 40 J2, 35, 36, 39 J3, 35 jumpers, 35, 36, 39, 40 leading zeros, 29, 65 LED (light-emitting diode), 12, 13, 28, 30 license requirements, 13 light-emitting diode (LED), 12, 13, 28, 30 linefeed control character (hexadecimal 0A), 80 Lock LED on reader, 30 milliseconds, 35, 39, 40, 41, 58, 59, 72 modem, 27 multiplexer (2200-700), 5, 9, 11, 31, 32, 33, 35, 37, 38, 39, 40, 41, 97 negative ACK control character (hexadecimal 15), 16, 19, 20, 49, 50, 52, 53, 54, 82 N-type, 37 order more copies of this guide, 10 order status, 48 ordering spare parts, 48 orders, checking on, 48


output circuits, 21 output control, 74, 83 output mode, 59, 60, 74, 83, 89, 94 output0, 13, 21, 59, 60, 74, 83, 94 output1, 13, 21, 40, 41, 59, 60, 74, 83, 93, 94 output2, 40, 41 output3, 40, 41 output4, 41 panel layouts, 43, 45 parameters, system, 24 parity, 17, 19, 20, 22, 27, 56, 57, 58, 63, 65, 72 passive tags, 6 phone number of STC (423-892-3029), 2, 10, 47 pinout, 11, 13, 37 placing an order for more copies of this guide, 10 potentiometer, 35 printer, 19 protocol, 5, 16, 17, 18, 19, 20, 22, 49, 51, 52, 56, 58, 60, 63, 73, 78, 80, 81, 82 questions about STC equipment, 48 R3, 35 radio frequency, 5, 6, 7, 9, 13, 21, 27, 28, 29, 31, 33, 34, 35, 37, 39, 40, 41, 56, 59, 61, 69, 75, 76, 84,

85, 87, 91, 97, 99, 100, 102, 103, 105, 107 radio frequency data communications (RFDC), 8 radio frequency identification (RFID), 5, 6, 7, 8, 11, 27, 30 railcar, 100, 101, 103, 104, 106, 108 RAM (random-access memory), 20, 61, 85, 87, 88, 89 random-access memory (RAM), 20, 61, 85, 87, 88, 89 reaching STC, 47 reader addressed failure conditions, 53 reader ID, 58, 60, 67, 72, 79, 103, 104, 106, 108 reader transmissions, 49 read-only memory (ROM), 25, 26, 61, 78, 88, 89 real-time clock (RTC), 61, 88 receive data (Rxd), 13, 37 relays, 11, 21 reporting problems or suggestions, 48 request to send (RTS), 13 returning equipment for repair, 47 RF status, 59, 75 RFDC (radio frequency data communications), 8 RFID (radio frequency identification), 5, 6, 7, 8, 11, 27, 30 RFID/AEI, 5, 6, 7 ROM (read-only memory), 25, 26, 61, 78, 88, 89 RS232, 11, 13, 17, 21, 36, 37, 40 RS422, 11, 13, 17, 21 RTC (real-time clock), 61, 88 RTS (request to send), 13 Rxd (receive data), 13, 37


SCTS (status of check tag status), 60, 79 serial interface, 7 serial number, 22, 25, 26, 58, 61, 62, 71, 84, 92, 96 serial port, 17 shipments, checking on, 48 software flow control, 17, 18, 19, 22, 56, 58, 60, 63, 73, 81 software version number, 25, 71, 84, 96 SOM (start-of-message), 16, 19, 28, 30, 49, 50, 51, 52, 53, 54, 55, 80, 98, 100, 101, 103, 104, 106, 108 spare parts, ordering, 48 standard warranty, 10 start-of-message (SOM) control character (hexadecimal 23), 16, 19, 28, 30, 49-55, 80, 98, 100, 101,

103, 104, 106, 108 static tags, 7 status of check tag status (SCTS), 60, 79 STC’s fax number (423-499-0045), 2, 10, 47 STC’s phone number (423-892-3029), 2, 10, 47 suggestions on STC equipment, 48 system parameters, 24 tag data, 7, 15, 18, 30, 49, 57, 98 tag IDs, 15, 16, 18, 20, 21, 23, 25, 28, 29, 51, 53, 57, 59, 63, 64, 66, 67, 68, 69, 77, 82, 83, 89, 91, 94 tag translation mode, 57, 59, 70, 77, 97, 99, 100, 102, 103, 105, 107 TB1, 36, 39, 40 telephone number of STC (423-892-3029), 2, 10, 47 terminal block, 31, 36, 39, 40 three-channel operational mode, 40 time and date, 30, 88, 97, 99, 100, 102, 103, 105, 106 timeout, 16, 21, 50, 52, 53, 54, 56, 58, 59, 60, 61, 64, 68, 73, 75, 76, 77, 80, 82, 91 transistor-transistor logic (TTL), 11, 13, 21, 31, 35, 37, 39 transmit data (Txd), 13, 37 transmitter-off control character (hexadecimal 13), 17, 19, 81 transmitter-on control character (hexadecimal 11), 17, 81 TTL (transistor-transistor logic), 11, 13, 21, 31, 35, 37, 39 two-antenna application, 43, 44 warnings, cautions, dangers, 2, 85 warranty, 10 XOFF, 17, 19, 81 XON, 17, 81 year, 25, 29, 51, 57, 58, 61, 62, 65, 66, 71, 84, 96

SmartScan - AEI RF IdentificationThis section lists the headings of this guide in sequential order with their page references. ... or American Trucking Association (ATA). These formats

Documents