Encompass® MultiProtocol Reader System Guide TransCore 8600 Jefferson Street NE Albuquerque, New Mexico 87113 P/N 411880
© 2005 TC IP, Ltd. All rights reserved. TRANSCORE, AMTECH, and EGO are registered trademarks of TC IP, Ltd, and are used under license. All other trademarks listed are the property of their respective owners. Contents are subject to change. Printed in the U.S.A. For further information, contact: TransCore 8600 Jefferson Street NE Albuquerque, New Mexico 87113 USA Phone: Fax: .
WARNING TO USERS IN THE UNITED STATES FEDERAL COMMUNICATIONS COMMISSION (FCC) LOCATION AND MONITORING SERVICE STATEMENT 47 CFR §90.351 NOTE: The user is required to obtain a Part 90 site license from the FCC to operate this radio frequency identification (RFID) device in the United States and Canada. FCC ID number is FIHE6PT90V1. IC ID number is 1584A-E6RSS137V1. Access the FCC Web site at www.fcc.gov/Forms/Form601/601.html or at wireless.fcc.gov/index.
Health Limits for Encompass® Multiprotocol Reader Using External Antenna (902 to 921.5 MHz) Within the United States, environmental guidelines regulating safe exposure levels are issued by the Occupational Safety and Health Administration (OSHA). Section 1910.97 of OSHA Safety and Health Standards 2206 legislates a maximum safe exposure limit of 10 milliwatts per square centimeter (mW/cm2) averaged over 6 minutes at 902 MHz.
Contents
Contents Health Limits ............................................................................................................v RF Levels From TransCore Equipment ................................................................. v 1 Before You Begin Purpose of the Guide .......................................................................................... 1-3 Intended Audience............................................................................................... 1-3 Guide Topics ..........
ix Encompass Multi-Protocol Reader System Guide Traffic Requirements.......................................................................................... 4-3 Tag Transaction or Handshake ..................................................................... 4-4 Capture Zone or Lane Footprint .................................................................... 4-4 RF Factors .........................................................................................................
Command Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Data Acknowledge Message .......................................................................6-11 Command Response Message....................................................................6-12 Asynchronous Response Message .............................................................6-13 Software Flow Control Message ..................................................................6-14 Unsolicited Status Message ........................................................................
xi
Encompass Multi-Protocol Reader System Guide A Acronyms and Glossary B Block Diagrams Encompass System............................................................................................. B-3 C System Technical Specifications Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encompass Multi-Protocol Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Supply Fault Detection . . . . . . . . . . . . . . . . . .
xii
1 Before You Begin
Chapter 1 Before You Begin This chapter provides an overview of the Encompass Multi-Protocol Reader System Guide. Purpose of the Guide This Encompass Multi-Protocol System Guide provides an overview of the reader systems as well as a list of the reader software commands and diagnostic and hardware interface information. Intended Audience The intended audience for this guide is those personnel responsible for operating the Encompass Multi-Protocol Reader.
1-3
Encompass Multi-Protocol Reader System Guide Related Documentation See the following related document: Encompass Reader Quick Reference Guide (in process) Typographical Conventions Used in this Manual The following conventions are used in this manual. Not all of the conventions are used in this version. Table 1-1 Typographical Conventions Convention Indication This procedure might cause harm to the equipment and/or the user. A caution sign indicates concerns about a procedure.
1-4
Licensing Requirements To operate a radio frequency (RF) system in a given country, the user first must obtain permission from the regulatory agency that controls radio operations in that country. Most countries require type and safety approval, as well as licensing for RF transmitters. Users in all countries should check with the appropriate local authorities for licensing requirements.
Encompass Multi-Protocol Reader System Guide
1-6
2 Developing the Installation Site Plan
Chapter 2 Developing the Installation Site Plan This chapter will provide guidelines for the following tasks: Assessing the Site and Formulating a Frequency Plan Site Layout and Traffic Flow Electrical and Communications Requirements Encompass and Tag Model Interoperability Reading of Mixed Population Tags Antenna Selection Antenna and Tag Alignment Polarization Site Preparation Checklist Components Checklist Task Checklist
2-3
Encompass Multi-Protocol Reader System Guide
2-4
3 Installing and Configuring the Encompass
Chapter 3 Installing and Configuring the Encompass This chapter provides instructions for installing and configuring the Encompass system. It also describes the individual components of the Encompass system. Overview of the Encompass TransCore’s Encompass is an integrated high-speed, multi-protocol 915-MHz radio fre- quency identification (RFID) reader system that includes an RF transceiver board and processor in a single assembly.
3-3
Encompass Multi-Protocol Reader System Guide Figure 3-1 Connector Locations on Encompass Enclosure Power The Encompass requires 19V DC to 28V DC or 19V AC to 27V AC RMS voltage source. Table 3-1 lists the Encompass external power connector specifications. Table 3-1 Encompass Power Connection Specifications Connector Type Wire Gauge Two-Pin Terminal Block 12 – 30 AWG Voltage 19V to 28V DC or 19V to 27V AC RMS Note If AC is used do not ground one end of the AC input, the AC supply must float.
3-4
Installing and Configuring the Encompass Antenna Connector Figure 3-2 Antenna Connector Location Table 3-2 lists the RF antenna connector parameters. Table 3-2 RF Antenna Connector Specifications Connector Type SMA Female Output Power Up to 2 watts RF Antenna Multiplexing/RF System Test Connector This connector is used when a single Encompass is used to operate multiple lanes. Ethernet Connector The Encompass communicates with a host via an Ethernet communications protocol.
3-5
Encompass Multi-Protocol Reader System Guide Table 3-3 RS-232 Connector Specifications (continued) Baud Bits Parity Stop Bits Flow Control 9600 8 None 1 None Note: If you connect the Encompass directly to a PC’s serial port, you must use a null- modem. By using the version command, you can display data about the configuration of the Encompass including its Internet Protocol (IP) address. (Mike, any more info here?) RS-232B/TDM Connector Information to be provided.
3-6
Installing and Configuring the Encompass 2. Run setup.exe and follow the commands to install the Host. The setup procedure installs an icon named Encompass Host on your computer desktop. The following sections tell you how to use the Encompass Host software. Connecting to the Encompass Reader with the Host Software 1. Double-click on the Encompass Host icon. 2. Select UDP on the main screen. 3. In the UDP Command Link Config field, enter the IP address of the reader.
3-7
Encompass Multi-Protocol Reader System Guide
3-8
4 Lane Tuning Guidelines
Chapter 4 Lane Tuning Guidelines This chapter explains the importance of lane tuning for optimum automatic vehicle identification (AVI) system performance and describes the Encompass functions and features that can assist you in tuning an AVI lane. Why You Need to Tune a Lane Lane tuning is the procedure by which an installer can optimize the radio frequency (RF) characteristics and the signal timing of an AVI-equipped toll lane for the performance dictated by the lane’s traffic requirements.
4-3
Encompass Multi-Protocol Reader System Guide • Maximum traffic speed in the lane, which is used to determine the required length of the capture zone; also known as the footprint • The type of lane, that is, express or mixed-use lane • The presence of vehicle framing devices such as light curtains, which may dictate the desired location of the first read point • The presence of alternate toll collection devices, such as coin machines in mixeduse lanes, which may dictate the desired first read point
4-4
Lane Tuning Guidelines To Be Provided. Figure 4-1 Field Size, Shape, and Antenna Polarization Define the Reading Range One concern for lane tuning is how large the footprint needs to be for acceptable system reliability. A rule of thumb frequently applied to this problem is that there should be time for a minimum of four complete transactions as the vehicle passes through the capture zone. Thus, the system that has the more complex transaction requires the larger footprint.
4-5
Encompass Multi-Protocol Reader System Guide 3 reads @ 4 milliseconds each = 12 milliseconds 3 writes @ 4 milliseconds each = 12 milliseconds 5 GENACKs @ 0.8 milliseconds each= 4 milliseconds = 28 milliseconds total, each full handshake To complete 4 full handshakes (simply a rule of thumb), the vehicle would need to be in the footprint for 112 milliseconds. If the agency requires 100 mph operation, the vehicles travel one foot in 6.8 milliseconds. At this speed, the footprint would need to be 16.
4-6
Lane Tuning Guidelines • The downlink and uplink source frequencies and interference from lanes sharing same or close frequencies • The antenna-tag orientation RF power is the most important RF factor in lane tuning. Thirty dBm translates to onewatt nominal power. Increasing the RF power will, in general, increase the footprint.
4-7
Encompass Multi-Protocol Reader System Guide ATA Tag Protocol TBD IAG Tag Protocol TBD Frequency Considerations — Multiple Protocols TBD Antenna-Tag Orientation Antennas need to be oriented to match the tag orientation (Figure 4-2). Antennas also need to match the tag placement and vice versa. For example, if the tag is placed in the center of the windshield, the antennas should be placed overhead, centered, or nearly centered in the lane.
4-8
Lane Tuning Guidelines Figure 4-3 Upper Center Interior Windshield Tag Placement Figure 4-4 Correct Exterior Tag Placement Antenna Uptilt Angle Adjusting the antenna uptilt angle directly affects the footprint and the point of first tag read (Figure 4-5). As expected, a greater uptilt angle will move the point of first tag read farther from the antenna.
defined read zones.
Encompass Multi-Protocol Reader System Guide ing license plate tags. Note: TransCore does not recommend placing the antenna uptilt angles at less than five degrees. Figure 4-5 Overhead Antenna Tilt Angle Antenna Positioning Within the Lane In lanes where the antennas are mounted side by side, TransCore recommends that you install the transmit antenna toward the driver side of the traffic lane and the receive antenna toward the passenger side of the traffic lane.
4-10
Lane Tuning Guidelines enable you to operate the lane at a lower RF power, which is usually the preferred operational mode.
4-11
Encompass Multi-Protocol Reader System Guide
4-12
Lane Tuning Guidelines
4-13
Encompass Multi-Protocol Reader System Guide
4-14
5 Optimizing Encompass Reader System Performance
Chapter 5 Optimizing Encompass Reader System Performance This chapter provides information to optimize the Encompass performance and reduce cross-lane interference. Cross-Lane Interference in RFID Systems Radio frequency identification (RFID) systems are subject to various types of interference that can affect the level of communications between a tag and a reader system. A type of interference that can result from the operation of the reader system is called cross-lane interference.
5-3
Encompass Multi-Protocol Reader System Guide Identifying Cross-Lane Interference Cross-lane interference is identified by an area in the RF read zone, or footprint, which has areas where a tag cannot be read. If a toll lane has been operating satisfactorily and then begins to show a degradation in system performance, that is, an increasing number of missed reads or a spotty read pattern, there is a probability that crosslane interference is occurring.
5-4
Optimizing Encompass Reader System Performance Diagnosing Cross-Lane Interference To diagnose this type of interference, first set the RF power in all lanes to a moderate setting of 6 to 9 decibels (dB) for both downlink and uplink antennas. Next, tune a single lane. When tuning a lane be sure to use a tag and vehicle that have been used consistently at your site. Once the lane has been tuned and you determine that it is working satisfactorily, perform lane tuning procedures in the adjacent lane.
5-5
Encompass Multi-Protocol Reader System Guide Time-Division Multiplexing In situations where cross-lane interference can occur in an installation, and frequency management is not sufficient to solve the problem, you may need to use time-division multiplexing (TDM). By using the TDM function in readers, individual readers operate only during interleaved time periods.
5-6
Optimizing Encompass Reader System Performance Because the TDM signals are based on RS–485 signals, you can extend the length of the TDM bus by using RS–485 repeaters or by using fiber with converters. Either of these two modifications should be used only when absolutely necessary in situations where the TDM lengths need to exceed the 1000-foot (305-m) maximum distance. Table 5-2 shows the pin designations and descriptions for the TDM connector.
5-7
Encompass Multi-Protocol Reader System Guide Figure 5-3 Typical Plaza Configuration Using TDM The frequency settings and the 9-millisecond TDM time slots were determined based on a Title 21 tag transaction. For other installations, the frequencies and TDM duration need to be determined based on the type of transaction and expected vehicle speeds for that installation. Figure 5-4 shows a timing diagram for the readers in each of the time slots.
5-8
Optimizing Encompass Reader System Performance Table 5-3 TDM Timing Settings Time Slot TDM Delay TDM Duration TDM Synchronization Perioda T1 0 ms (setting = 0) 9 ms (setting = 18) 31 ms (setting = 31) T2 10 ms (setting = 20) 9 ms (setting = 18) 32 ms (setting = 32) T3 20 ms (setting = 40) 9 ms (setting = 18) 33 ms (setting = 33) a. Master reader TDM synchronization period equals 30 milliseconds. Note: The TDM synchronization period is set in 1.
5-9
Encompass Multi-Protocol Reader System Guide TDM bus in the event of either a TDM connection failure, or a failure of the TDM circuit in the master reader, which also reduces the number of readers that will generate TDM failure messages in any one of these failure scenarios. Physical Remedies By adjusting the angle or position of the downlink and uplink antennas, you may be able to minimize cross-lane interference. Warning Switch off RF power before working on antennas.
5-10
Optimizing Encompass Reader System Performance Adjusting the Antenna Side Angle In the eGo 4110A Reader System, you can adjust an antenna’s side angle so that the RF transmits toward the center of the toll lane, placing the RF footprint into the lane. If the side angle is too small, the footprint can project into the lane nearest to the tilted antenna.
5-11
Encompass Multi-Protocol Reader System Guide
5-12
6 General Software Information
Chapter 6 General Software Information This chapter provides general software information about the design of Encompass system application software, as well as information required for using reader system components in the design and integration of an automated toll, traffic management, or automatic vehicle identification (AVI) system.
6-3
Encompass Multi-Protocol Reader System Guide host PC is set to Dynamic TransCore recommends that you set the IP address to Static. Table 6-1 lists the connector pin assignments.
6-4
General Software Information Table 6-3 RS-232B/TDM Connector Parameters Pin Signal Description 1 TXD Transmit Data 2 RXD Receive Data 3 DTR Data Terminal Ready (not connected) 4 RTS Request to Send 5 CTS Clear to Send 6 GND Ground 7 TDM + TDM positive signal 8 TDM - TDM negative signal Diagnostic RS–232 Serial Communications The Encompass can communicate via a serial, RS–232, communications protocol (Table 6-4).
6-5
Encompass Multi-Protocol Reader System Guide Table 6-5 Diagnostic RS-232 Connector Parameters Pin Signal Description 1 5V PWR 5V power supply for I/O board 2 GND GND 3 I/O Signal 1 Input/output signal 1 4 I/O Signal 2 Input/output signal 2 5 I/O Signal 3 Input/output signal 3 6 I/O Signal 4 Input/output signal 4 7 Tag in Field 1 Contact Closure 1 for Tag in Field Signal 8 Tag in Field 2 Contact Closure 2 for Tag in Field Signal Reader Command Protocol The Encompass implements com
sages, command response messages, asynchronous response messages and if required 6-6
General Software Information software flow control messages to the host. The host on receiving command response messages, asynchronous response messages and software flow control messages from the Encompass sends data acknowledge messages to the Encompass. Additionally, the Encompass sends unsolicited status messages to the host. The host on receiving unsolicited status messages from the Encompass sends data acknowledge messages to the Encompass.
6-7
Encompass Multi-Protocol Reader System Guide = command, a word that specifies the system command. See the command sections for details. = command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details. [] = optional data payload that varies in length from 0 to 65 bytes and is associated with each specific command. See the command sections for details.
6-8
General Software Information [] where = length, a word that specifies the number of bytes in the entire message. = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details. = command, word that specifies the system command. See the command sections for details.
6-9
Encompass Multi-Protocol Reader System Guide Software Flow Control Message The Encompass after receiving command request messages from the host optionally sends software flow control messages to the host as required for system operation. The host optionally sends software flow control messages to the Encompass as required for host operation.
6-10
General Software Information = status, a word that specifies the system status. See the response sections for details. [] = optional data payload that varies in length from 0 to 63 bytes and is associated with each specific response. See the response sections for details. = checksum, a byte that specifies the checksum of the message. Serial Communications Protocol The serial communications protocol implements the TransCore error correction protocol (ECP) serial standard.
6-11
Encompass Multi-Protocol Reader System Guide Data Acknowledge Message The Encompass after receiving command request messages from the host sends data acknowledge messages to the host. The host after receiving command response messages, asynchronous response messages, software flow control messages and unsolicited status messages from the Encompass sends data acknowledge messages to the Encompass.
6-12
General Software Information where - start of message, byte that specifies the start of the message which is defined as the ASCII character &. - length, word that specifies the number of bytes in the entire message. - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details. - command, word that specifies the system command. See the command sections for details.
6-13
Encompass Multi-Protocol Reader System Guide - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details. - response, word that specifies the system response. See the response sections for details. [] - optional data payload that varies in length from 0 to 63 bytes and is associated with each specific response. See the response sections for details.
6-14
General Software Information - end of message, byte that specifies the end of the message which is defined as the ASCII character %. Unsolicited Status Message The Encompass sends unsolicited status messages to the host as required for system operation.
6-15
Encompass Multi-Protocol Reader System Guide
6-16
7 Configuration Commands and Responses
Chapter 7 Configuration Commands and Responses This chapter describes the Encompass interface commands that are used to configure the reader. Configuring the Encompass Encompass Readers have been preconfigured for most needed operations. Parameters such as attenuation, step-lock settings, and tag command sequences are set when the reader powers up. The Set Frequency command is the only required configuration command. You must issue this command before the Encompass Reader can read tags.
Unused Source 0XH 7-3
Encompass Multi-Protocol Reader System Guide Table 7-1 Set Frequency Command Parameters Unused A Counter XXH Unused B Counter LSBs Carriage Return 0XH 0DH Table 7-2 shows the Set Frequency Response parameters.
7-4
Configuration Commands and Responses System Interface Command Group Commands This section describes the system commands used to configure the Encompass.
7-5
Encompass Multi-Protocol Reader System Guide System Identify System Identify Command Data System Identify Command System Identify Response Data System Identify Command Data Payload 0000H Data Payload 0000H Vendor Name Version ID Part Number Serial Number System Identify Data Sizes System Identify Data Data Size Vendor Name 15 Bytes Version ID 15 Bytes Part Number 15 Bytes Serial Number 15 Bytes Set Communications Baud Rate Set Communications Baud Rate Command Data Set Communications Baud
Baud Rate Data Code 7-6 XXH
Configuration Commands and Responses Set Communications Baud Rate Response Data Set Communications Baud Rate Command Data Payload 0001H Baud Rate Data Codes Baud Rate Data Code 19,200 bps 0CH 38,400 bps (System Default) 0DH 57,600 bps 0EH 115,200 bps 0FH Get Communications Baud Rate Get Communications Baud Rate Command Data Get Communications Baud Rate Command Get Communications Baud Rate Response Data Data Payload 0002H Data Payload Get Communications Baud Rate Command 0002H Baud Rate
7-7
Encompass Multi-Protocol Reader System Guide Set Time and Date Data Payload Set Time and Data Command Data Set Time and Date Command 0003H Hours XXH Minutes XXH Seconds XXH Hundredths of Seconds XXH Month XXH Day XXH Year XXH Data Payload Set Time and Data Response Data Set Time and Date Command 0003H Time and Date Data Ranges Time and Date Data Data Range Hours 0 to 23 (00H to 17H) Minutes 0 to 59 (00H to 3BH) Seconds 0 to 59 (00H to 3BH) Hundredths of Seconds 0 to 99 (00H t
7-8
Configuration Commands and Responses Get Time and Date Data Payload Get Time and Data Command Data Get Time and Date Command Get Time and Data Response Data 0004H Data Payload Set Time and Date Command 0004H Hours XXH Minutes XXH Seconds XXH Hundredths of Seconds XXH Month XXH Day XXH Year XXH Firmware Download Firmware Download Command Data Firmware Download Command Firmware Download Response Data Firmware Download Command Data Payload 0005H Data Payload 0005H
7-9
Encompass Multi-Protocol Reader System Guide The Firmware Download command is implemented as defined for both UDP/IP Fast Ethernet and serial communications.
7-10
Configuration Commands and Responses Get Number of Stored Tag Response Messages Get Number of Stored Tag Response Messages Command Data Get Number of Stored Tag Response Messages Command Get Number of Stored Tag Response Messages Response Data Data Payload 0008H Data Payload Get Number of Stored Tag Response Messages Command 0008H Number of Stored Tag Response Messages XXXXH Delete All Stored Tag Response Messages Delete All Stored Tag Response Messages Command Data Data Payload Delete All Stor
7-11
Encompass Multi-Protocol Reader System Guide Get System Startup Status Command Data Get System Startup Status Command Get System Startup Status Response Data Data Payload 000AH Data Payload Get System Startup Status Command 000AH System Startup Module Number (System Initialization) XXXXH System Timer Initialization Status Error Number XXXXH System BMU Initialization Status Error Number XXXXH System Queue Create Status Error Number XXXXH System Task Create Status Error Number XXXXH Get Lane
7-12
Configuration Commands and Responses Get System Interface Status Get System Interface Status Command Data Get System Interface Status Command Get System Interface Status Response Data Data Payload 000CH Data Payload Get System Interface Status Command 000CH Module Number XXXXH Error Number XXXXH Get DigBrd Hdwr Remote Inventory Get Digital Board Hardware Remote Inventory Command Data Get Digital Board Hardware Remote Inventory Command Get Digital Board Hardware Remote Inventory Response Data G
7-13
Encompass Multi-Protocol Reader System Guide Hardware Remote Inventory Data Sizes Hardware Remote Inventory Data Data Size Vendor Name 15 Bytes Version ID 15 Bytes Part Number 15 Bytes Serial Number 15 Bytes Get DigBrd CPU Boot Fmwr Remote Inventory Get Digital Board CPU Boot Firmware Remote Inventory Command Data Get Digital Board CPU Boot Firmware Remote Inventory Command Get Digital Board CPU Boot Firmware Remote Inventory Response Data Get Digital Board CPU Boot Firmware Remote Inventory C
7-14
Configuration Commands and Responses Get Digital Board CPU Application Firmware Remote Inventory Response Data Get Digital Board CPU Application Firmware Remote Inventory Command Data Payload 000FH Vendor Name Version ID Part Number Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory Get Digital Board FPGA UDP/IP Core Firmware Remote Inventory Command Data Data Payload Get Digital Board FPGA UPD/IP Core Firmware Remote Inventory Command 0010H Get Digital Board FPGA UDP/IP Core Firmware Remote Invento
7-15
Encompass Multi-Protocol Reader System Guide Firmware Remote Inventory Data Data Size Vendor Name 15 Bytes Version ID 15 Bytes Part Number 15 Bytes Set UDP/IP Core Lane Controller Parameters Set UDP/IP Core Lane Controller Parameters Command Data Data Payload Set UDP/IP Core Lane Controller Parameters Command 0011H IP Address (MSW) XXXXH IP Address (LSW) XXXXH Port Number XXXXH Set UDP/IP Core Lane Controller Parameters Response Data Set UDP/IP Core Lane Controller Parameters Command Da
7-16
Configuration Commands and Responses Get UDP/IP Core Lane Controller Parameters Response Data Data Payload Get UDP/IP Core Lane Controller Parameters Command 0012H IP Address (MSW) XXXXH IP Address (LSW) XXXXH Port Number XXXXH Set UDP/IP Core IP Address Set UDP/IP Core IP Address Command Data Data Payload Set UDP/IP Core IP Address Command 0013H IP Address (MSW) XXXXH IP Address (LSW) XXXXH Set UDP/IP Core IP Address Response Data Set UDP/IP Core IP Address Command Data Payload 0013H
7-17
Encompass Multi-Protocol Reader System Guide Get UDP/IP Core Lane Controller Parameters Command Data Data Payload Get UDP/IP Core IP Address Command 0014H IP Address (MSW) XXXXH IP Address (LSW) XXXXH Get UDP/IP Core Port Number Get UDP/IP Core Port Number Command Data Get UDP/IP Core Port Number Command Get UDP/IP Core Port Number Command Data Data Payload 0015H Data Payload Get UDP/IP Core Port Number Command 0015H Port Number XXXXH
7-18
8 Tag Command Processing
Chapter 8 Tag Command Processing This chapter provides definitions of and instructions for reading from and writing to a tag, as well as explanations of the tag command codes. Reader Operation The reader can operate in one of two command sequences, either read or write. The tag command sequences for the Read and Write operations are detailed in the following sections. Write Commands To be provided. Read Commands To be provided Host Commands Required for Tag Processing To be provided.
8-3
Encompass Multi-Protocol Reader System Guide
8-4
9 System Diagnostics and Preventive Maintenance
Chapter 9 System Diagnostics and Preventive Maintenance This chapter provides information on the following subjects: Error Messages Troubleshooting Preventive Maintenance Schedule Visual Inspection Encompass Repair Removal and Replacement Procedures Technical Support Troubleshooting Indications and Actions To be provided.
9-3
Encompass Multi-Protocol Reader System Guide
9-4
A Acronyms and Glossary
Appendix A Acronyms and Glossary A AC alternating current ACK acknowledge (data valid) antenna passive device that converts RF energy into magnetic energy (RF signal) ATA American Trucking Associations refers to a standard RF communications protocol and data storage method. ATA-type tags are read only.
A-3
Encompass Multi-Protocol Reader System Guide DC direct current dB decibel(s) dBi decibel(s), referencing isotropic radiator E ECP error correcting protocol eGo Proprietary name for ANS INCITS 256-2001 and ISO 18000-6 compliant TransCore products. A registered trademark of TC IP, Ltd.
A-4
Acronyms and Glossary I I/O input/output IAG Inter-Agency Group, distributor of IAG tags ID identification; encoded information unique to a particular tag in inch(es) interface connection point for communications with another device IRQ interrupt request J JP jumper pin K k kilo (103) kg kilogram(s) L lane controller device that is used to integrate all activity that occurs in a toll lane.
A-5
Encompass Multi-Protocol Reader System Guide milli one-thousandth (10-3) mode method of operation MPI TransCore’s Multi-Protocol Reader ms milliseconds mW milliwatt(s) N NEMA National Electrical Manufacturers Association O OSHA Occupational Safety and Health Administration P PC personal computer PLL phase-lock loop protocol specified convention for the format of data messages communicated between devices PWA printed wiring assembly R RAM random access memory read process of acquiri
A-6
Acronyms and Glossary S s second(s) SeGo SeGo is a superset of the TransCore eGo protocol. SRAM static random access memory som start of message system a reader, RF module, antenna, and tag, which are described by the general application and interfaces with each other and any connected devices that are defined as being outside the system.
A-7
Encompass Multi-Protocol Reader System Guide W W watt(s) write process of recording data, for example, writing to computer memory or to a tag’s memory. Writing erases previous data stored at the specified memory locations.
A-8
B Block Diagrams
Appendix B Block Diagrams This appendix shows the block diagrams for the interface connections between the components as well as the individual Encompass System components.
B-3
Encompass Multi-Protocol Reader System Guide
B-4
C System Technical Specifications
Appendix C System Technical Specifications This appendix provides reference information for the Encompass System components. Component Specifications This appendix describes the engineering specifications for the Encompass System components. Encompass Multi-Protocol Reader Power Supply Fault Detection Each voltage supply has fault detection to determine if the voltage supply is functioning correctly. Output tolerance is tested to ±5 percent.
C-3
Encompass Multi-Protocol Reader System Guide Table C-1 Antenna Environmental Tolerances Environment Specification Dust NEMA pub 250-1991, Sec. 6.5, page 18 Rain NEMA pub 250-1991, Sec. 6.4, page 17 and Sec. 6.7, page 19 Corrosion resistance NEMA pub 250-1991, Sec. 6.9, page 20 Shock 5 G ½-sine pulse, 10 ms duration, 3 axes Vibration 0.
C-4
D Hardware Interfaces
Appendix D Hardware Interfaces This appendix describes the physical interconnections within an Encompass System. Hardware Interfaces This appendix describes the hardware interfaces in the Encompass and to external components, such as antennas. Figure D-1 shows the basic hardware interconnections for the Encompass.
D-3
Encompass Multi-Protocol Reader System Guide Communications The Encompass communicates with a host via Ethernet or serial communicaitons. Ethernet The connector is an RJ-45 jack. This interface is 10-base T. Table D-1 lists the pinouts.
D-4
Hardware Interfaces Table D-3 RS-232B/TDM Connector Parameters Pin Signal Description 1 TXD Transmit Data 2 RXD Receive Data 3 DTR Data Terminal Ready (not connected) 4 RTS Request to Send 5 CTS Clear to Send 6 GND Ground 7 TDM + TDM positive signal 8 TDM - TDM negative signal Table D-4 RS-232 Diagnostics Connector Parameters Pin Signal Description 1 5V PWR 5V power supply for I/O board 2 GND GND 3 I/O Signal 1 4 I/O Signal 2 5 I/O Signal 3 6 I/O Signal 4 7 Tag
D-5
Encompass Multi-Protocol Reader System Guide Hardware Diagnostic Port Table D-5 Encompass Hardware Diagnostic Port Parameters Pin Signal Source Description 1 I RF I Channel from RF receiver 2 Q RF Q Channel from RF receiver 3 RSSI RF RSSI Detector Output, high for I low for Q. 4 RANGE_ADJ_CNTL RF Range Adjust_Control Signal 5 +3.3V Digital +3.
D-6
Hardware Interfaces Table D-5 Encompass Hardware Diagnostic Port Parameters (continued) 27 GND Ground 28 Tx Serial Comm Digital Transmit Serial Signal 29 Rx Serial Comm RF Receive Serial Signal 30 GoodTagRead Digital Active High Pulse from FPGA1 31 CRC Failed Digital Active High Pulse from FPGA1 32 ActivatePort Digital Enable the Test Port Buffer when the Connector plugged in 33 GND 34 SW1 Digital GPIO from MPC852 35 SW2 Digital GPIO from MPC852 36 SW3 Digital GPIO from
D-7
Encompass Multi-Protocol Reader System Guide • Connector E22, RF system test data is the same as connector B11 on the digital board. • Connector E29, RF system test data is the same as connector B11 on the digital board. This connector is used to connect the data cables from the Encompass to the antenna multiplexer board and the RF system test boards. • Connector E23 is the RF in signal.
D-8
