TransCore MPI6000 LMS TRANSMITTER User Manual 411880

TransCore LMS TRANSMITTER 411880

USERS MANUAL

MPI 6000 Multi-Protocol Reader System GuideTransCore, Inc.19111 Dallas Parkway, Suite 300Dallas, Texas 75287-3106September 2005P/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.Products covered by this document are protected by one or more of the following U.S. patents 4,739,328; 4,864,158; 4,999,636; 5,030,807; 5,550,547; 5,606,322; 5,673,037; 5,912,632; 5,942,987; and foreign equivalent patents. Other patents pending.For further information, contact:TransCore19111 Dallas Parkway, Suite 300Dallas, Texas 75287-3106 USAPhone: (972) 733-6600Fax: (972) 733-6699TransCore Action Center (TrAC)Phone: (800) 755-0378For comments or questions about this document, e-mail tech.pubs@transcore.com.
ivWARNING TO USERS IN THE UNITED STATESFEDERAL COMMUNICATIONS COMMISSION (FCC) RADIO FREQUENCY INTERFERENCE STATEMENT47 CFR §15.105(a)NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of the Federal Communications Commission (FCC) rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency (RF) energy and may cause harmful interference to radio communications if not installed and used in accordance with the instruction manual. Operating this equipment in a residential area is likely to cause harmful interference, in which case, depending on the laws in effect, the users may be required to correct the interference at their own expense.NO UNAUTHORIZED MODIFICATIONS47 CFR §15.21CAUTION: This equipment may not be modified, altered, or changed in any way without permission from TransCore, Inc. Unauthorized modification may void the equipment authorization from the FCC and will void the TransCore warranty.USE OF SHIELDED CABLES IS REQUIRED47 CFR §15.27(a)Shielded cables must be used with this equipment to comply with FCC regulations.A license issued by the FCC is required to operate this RF identification device in the United States. Contact TransCore, Inc. for additional information concerning licensing requirements for specific devices.TransCore, Inc.USA
Health LimitsWithin the United States, environmental guidelines regulating safe exposure levels are issued by the Occu-pational Safety and Health Administration (OSHA).For equipment operating from 300 to 1500 MHz the FCC limits on radiation exposure are contained in CFR title 47 part 1.1310.Note: Frequency (f) is expressed in MHz.At 902 MHz (worst case frequency for MPI 6000 operating band) these levels areRF Levels From TransCore EquipmentPower density is given in milliwatts per centimeter (mW/cm) and is calculated aswhereP = antenna input power (mW)G = antenna gain referenced to an isotropic radiatorD = distance from antenna (cm)For TransCore’s IT2200 AVI system at maximum levels ofP = 1 W or 1000 mW, maximumG = 14dBi or 25.1; AA3152 Universal Toll AntennaS = 0.60 mW/cm2, General Public Exposure LimitS = 3.0 mW/cm2, Occupational/Controlled LimitExposure Classification Power Density Averaging TimeOccupational/Controlled Exposure f/300 mW/cm26 minutesGeneral Public/Uncontrolled Exposure f/1500 mW/cm230 minutesExposure Classification Power Density Averaging TimeOccupational/Controlled Exposure 3.0 mW/cm26 minutesGeneral Public/Uncontrolled Exposure 0.6 mW/cm230 minutes24DPGSπ=
MPI 6000 Multi-Protocol System GuideFor the maximum power level (2 watts) the minimum safe distance is = 2.68 ft (81.5 cm) for General Public Exposure Limit, and 1.2 ft (36.46 cm) for Occupational/Controlled LimitFor a typical operating power level of 0.5W (-6dB attenuation from maximum power) the minimum safe dis-tance is = 1.339 ft (40.8 cm) for General Public Exposure Limit, and 0.6 ft (18.3 cm) for Occupational/Controlled LimitAny distance beyond 2.68 ft (0.82 m) from the antenna is compliant. Because antennas typically are mounted at heights of 18 ft (5.5 m), the minimum compliance distance should be met and maintained. Typical exposure levels should be below FCC exposure limits.For example, a 6 ft (1.8 m) tall person standing in the center of the main lobe of the antenna would experience maximum RF levels of 0.03 mW/cm2, and typical levels of 0.0075mW/cm2. Even for the more stringent Gen-eral Public Exposure Limit, the maximum exposure is 1/40th of the compliance level, and the typical exposure level is 4 times lower than that. For locations not centered in the main lobe of the antenna, the drop off in antenna gain reduces the radiation exposure for that area. A person standing 6 ft (1.8 m) to the side of an antenna would experience an additional approximate 10dB drop in power density.For these reasons, the MPI 6000 falls within FCC exposure limits.SPGDπ4=SPGDπ4=
Contents
ixContentsHealth Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vRF Levels From TransCore Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v1 Before You BeginPurpose of the Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Guide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Typographical Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . 1-4Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5U.S. Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52 Developing the Installation Site Plan3 Installing and Configuring the MPI 6000Overview of the MPI 6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Connecting the MPI 6000 for Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3External Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Installing and Using the MPI 6000 Host Software . . . . . . . . . . . . . . . . . . . . . . . 3-6Installing the Host Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Connecting to the MPI 6000 Reader with the Host Software . . . . . . . . . . . . 3-7Configuring the MPI 6000 Reader Operating Frequency . . . . . . . . . . . . . . . 3-7Operating the MPI 6000 Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74 Lane Tuning GuidelinesWhy You Need to Tune a Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Lane Tuning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
MPI 6000 Multi-Protocol Reader System GuidexTraffic Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Tag Transaction or Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Capture Zone or Lane Footprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4RF Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Downlink and Uplink Transmitted RF Power . . . . . . . . . . . . . . . . . . . . . . . . 4-7Range Control Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Frequency Considerations — Single Protocol . . . . . . . . . . . . . . . . . . . . . . . 4-7Frequency Considerations — Multiple Protocols . . . . . . . . . . . . . . . . . . . . . 4-8Antenna-Tag Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Antenna Uptilt Angle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Antenna Positioning Within the Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Signal Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115 Optimizing MPI 6000 Reader System PerformanceCross-Lane Interference in RFID Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3What Is Cross-Lane Interference? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Determining Acceptable Lane Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Identifying Cross-Lane Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Diagnosing Cross-Lane Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Remedying Cross-Lane Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Frequency Separation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5RF Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Time-Division Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Physical Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106 General Software InformationGeneral Software Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Plan and Organize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Communications Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Communications RS–232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Diagnostic RS–232 Serial Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Reader Command Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6UDP/IP Fast Ethernet Communications Protocol . . . . . . . . . . . . . . . . . . . . . . . 6-7Command Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Data Acknowledge Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Command Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Asynchronous Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Software Flow Control Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Unsolicited Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Serial Communications Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Command Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
ContentsxiData Acknowledge Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Command Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Asynchronous Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Software Flow Control Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Unsolicited Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-157 Configuration Commands and ResponsesConfiguring the MPI 6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Required Commands to Set Up MPI 6000 Reader. . . . . . . . . . . . . . . . . . . . 7-3System Interface Command Group Commands . . . . . . . . . . . . . . . . . . . . . . . . 7-5System Identify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Set Communications Baud Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Get Communications Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Set Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Get Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Firmware Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Reset Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Get Stored Tag Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Get Number of Stored Tag Response Messages. . . . . . . . . . . . . . . . . . . . 7-11Delete All Stored Tag Response Messages . . . . . . . . . . . . . . . . . . . . . . . . 7-11Get System Startup Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Get Lane Controller Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Get System Interface Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Get DigBrd Hdwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Get DigBrd CPU Boot Fmwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . 7-14Get DigBrd CPU Appl Fmwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . 7-14Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory . . . . . . . . . . . . . 7-15Get UDP/IP Core Lane Controller Parameters . . . . . . . . . . . . . . . . . . . . . . 7-16Set UDP/IP Core IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Get UDP/IP Core IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Get UDP/IP Core Port Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-188 Tag Command ProcessingReader Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Write Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Read Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Host Commands Required for Tag Processing. . . . . . . . . . . . . . . . . . . . . . . . . 8-39 System Diagnostics and Preventive MaintenanceTroubleshooting Indications and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
MPI 6000 Multi-Protocol Reader System GuidexiiA Acronyms and GlossaryB Block DiagramsMPI 6000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3C System Technical SpecificationsComponent Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3MPI 6000 Multi-Protocol Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3Power Supply Fault Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3AA3152 Universal Toll Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3D Hardware InterfacesHardware Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4RS-232 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4Hardware Diagnostic Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6Antenna Multiplexer Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7RF System Test Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
1Before You Begin
1-3Chapter 1Before You BeginThis chapter provides an overview of the MPI 6000 Multi-Protocol Reader System Guide.Purpose of the GuideThis MPI 6000 Multi-Protocol System Guide provides an overview of the reader sys-tems as well as a list of the reader software commands and diagnostic and hardware interface information.Intended AudienceThe intended audience for this guide is those personnel responsible for operating the MPI 6000 Multi-Protocol Reader.Guide TopicsThe MPI 6000 Multi-Protocol System Guide presents the following information.Chapter 1 - Before You Begin In processChapter 2 - Theory of Operation In processChapter 3 - System Components In processChapter 4 - MPI 6000 System Operation In processChapter 5 - Diagnostics Information In processAppendix A - Acronyms and Glossary In processAppendix B - Block Diagrams In processAppendix C - System Technical SpecificationsIn processAppendix D - Hardware Interfaces In processAppendix E - Reader Defaults In processIndex In process
MPI 6000 Multi-Protocol Reader System Guide1-4Related DocumentationSee the following related document:MPI 6000 Reader Quick Reference Guide (in process)Typographical Conventions Used in this ManualThe following conventions are used in this manual. Not all of the conventions are used in this version.Table 1-1 Typographical Conventions Convention IndicationThis procedure might cause harm to the equipment and/or the user.A caution sign indicates concerns about a procedure.Code Code, including keywords and variables within text and as separate paragraphs, and user-defined program elements within text appear in courier typeface.Dialog Box Title Title of a dialog box as it appears on screen.Screen Title Title of a screen as it appears on screen.Menu Item Appears on a menu.Note Additional information that further clarifies the current discussion. These important points require the user’s attention. The paragraph is in italics and the word Note is bold.Cancel button Bold text identifies the labeling of items as they actually appear on the keyboard, on a button, as a menu item, and so forth.Ctrl-Esc A hyphen indicates actions you should perform simultaneously. For example, Ctrl-Esc means to press the Ctrl and Esc keys at the same time.5 Return A space indicates that you should press the specified keys in the sequence listed, not at the same time.before Text in italics indicates emphasis.Customer > Find Bold text followed by a > and more bold text indicates the order of command selections to reach a specific function. click Click means that you should press and release the left mouse button.cursor The cursor is the flashing vertical line that appears in a selected edit box.
Before You Begin1-5Licensing RequirementsTo operate a radio frequency (RF) system in a given country, the user must first 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 transmit-ters.TransCore data and literature are available to assist with approval and licensing activ-ities.U.S. LicensingMPI 6000 systems users in the U.S. must obtain a license from the Federal Communi-cations Commission (FCC). The authorized frequency bands in the U.S. are 902 to 904 MHz and 909.75 to 921.75 MHz.The user is responsible for filing the FCC license according to FCC regulations, but the TransCore dealer should provide assistance and support as necessary to complete these forms.An FCC license provides the user with the legal authorization to operate the MPI 6000 systems on the licensed frequencies at the site specified in the license. Only an autho-rized installer or service technician can set the frequency for MPI 6000 to that speci-fied in the FCC site license.The FCC license also provides the user with protection and authorization to maintain the system should any other RF identification product be used in the licensed area after the MPI 6000 equipment is installed. pointer The pointer is the arrow in the window that shows the movement of the mouse.Table 1-1 Typographical Conventions (continued)
MPI 6000 Multi-Protocol Reader System Guide1-6
2Developing the Installation Site Plan
2-3Chapter 2Developing the Installation Site PlanThis chapter will provide guidelines for the following tasks: Assessing the Site and Formulating a Frequency PlanSite Layout and Traffic FlowElectrical and Communications RequirementsMPI 6000 and Tag Model InteroperabilityReading of Mixed Population TagsAntenna SelectionAntenna and Tag AlignmentPolarizationSite Preparation ChecklistComponents ChecklistTask Checklist
MPI 6000 Multi-Protocol Reader System Guide2-4
3Installing and Configuring the MPI 6000
3-3Chapter 3Installing and Configuring the MPI 6000This chapter provides instructions for installing and configuring the MPI 6000 system. It also describes the individual components of the MPI 6000 system.Overview of the MPI 6000TransCore’s MPI 6000 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.The MPI 6000 can be integrated into an onsite lane controller or a NEMA enclosure. The MPI 6000 transmits and receives signals through a single antenna.The MPI 6000 is capable of supporting any of the following protocols in a given installation:•American Trucking Association (ATA), full-frame and half-frame (read-only)•California Title 21 (read-only)•eGo®1 (read-only)•Inter-Agency Group (IAG) (read/write)•Super eGo (SeGo)* (read/write)•TransCore IT2200 (read/write)Where multiple tag protocols are used in the same installation, the MPI 6000 is capa-ble of supporting any two of the above protocols.The MPI 6000 is also suitable for a wide variety of automatic vehicle identification transportation applications, including electronic tolling, open road tolling, electronic vehicle registration, parking, and rail applications.The following sections describe the specifications for the external connections from the MPI 6000 housing.Connecting the MPI 6000 for OperationExternal ConnectorsThis section lists the MPI 6000 external connections. Figure 3-1 shows the MPI 6000 connector locations.1.*eGo tags are fully compliant with ANSI INCITS 256:2001 and ISO 18000-6 standards. SeGo is a superset of the eGo protocol.
MPI 6000 Multi-Protocol Reader System Guide3-4Figure 3-1 Connector Locations on MPI 6000 EnclosurePowerThe MPI 6000 requires 19V DC to 28V DC or 19V AC to 27V AC RMS voltage source. Table 3-1 lists the MPI 6000 external power connector specifications.RF Antenna Connector The MPI 6000 Reader typically is connected to an AA3152 Universal Toll Antenna by a single low-loss RF cable. The antenna configuration is designed for overhead mounting on a gantry or sign structure. Figure 3-2 shows the antenna connector on the MPI 6000 enclosure.Table 3-1 MPI 6000 Power Connection SpecificationsConnector Type Two-Pin Terminal Block Wire Gauge 12 – 30 AWGVoltage19V to 28V DC or 19V to 27V AC RMSNote If AC is used do not ground one end of the AC input, the AC supply must float.Polarity Either, power supply is polarity independentCurrent 2 amps
Installing and Configuring the MPI 60003-5Figure 3-2 Antenna Connector LocationTable 3-2 lists the RF antenna connector parameters.RF Antenna Multiplexing/RF System Test ConnectorThis connector is used when a single MPI 6000 is used to operate multiple lanes.Ethernet ConnectorThe MPI 6000 communicates with a host via an Ethernet communications protocol. This connection requires an RJ–45 connector. If you use a switch between the MPI 6000 and a host PC, you do not need a crossover cable. If you connect the MPI 6000 directly to a host PC then you need a crossover cable. If you set the host PC to Dynamic, TransCore recommends that you set the IP address to Static.RS–232A Serial Communications ConnectorThe MPI 6000 communicates via a serial, RS–232, communications protocol (Table 3-3). The diagnostic RS–232 port can be used to display the operating system boot sequence. Antenna ConnectorTable 3-2 RF Antenna Connector SpecificationsConnector Type SMA Female Output Power Up to 2 wattsTable 3-3 RS-232 Connector Specifications Connector Type 9 pin D-sub male Protocol RS-232
MPI 6000 Multi-Protocol Reader System Guide3-6Note: If you connect the MPI 6000 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 MPI 6000 including its Internet Protocol (IP) address. (Mike, any more info here?)RS-232B/TDM ConnectorInformation to be provided. RS-232 Diagnostic Test Port ConnectorInformation to be provided.External Digital Input/Output ConnectorInformation to be provided.Global Positioning System ConnectorInformation to be provided.Installing and Using the MPI 6000 Host SoftwareThis section provides instructions for installing the MPI 6000 host software on your host computer. You do not need the host to operate the MPI 6000, you can design an application programming interface using the MPI 6000 commands. Those configura-tion commands are explained in “Configuration Commands and Responses” on page 7-3 of this system guide.If you choose to use TransCore’s host software program, follow the instructions in the following sections.Installing the Host SoftwareThe MPI 6000 host program is used to communicate with the MPI 6000 and also dis-play tag reads.To install the MPI 6000 Host software1. Load (what media is used? CD? FTP site?) the host software onto the host computer. Baud 9600Bits 8Parity NoneStop Bits 1Flow Control NoneTable 3-3 RS-232 Connector Specifications (continued)
Installing and Configuring the MPI 60003-72. Run setup.exe and follow the commands to install the Host. The setup procedure installs an icon named MPI 6000 Host on your computer desktop.The following sections tell you how to use the MPI 6000 Host software.Connecting to the MPI 6000 Reader with the Host Software1. Double-click on the MPI 6000 Host icon.2. Select UDP on the main screen.3. In the UDP Command Link Config field, enter the IP address of the reader.Write the IP address near the Ethernet connector on the MPI 6000 enclosure for future reference.4. Select Establish Command Link.5. Select E.xit.Configuring the MPI 6000 Reader Operating Frequency1. Select the Configuration tab.2. Select the Transceiver Configuration sub-tab.3. Set the frequencies to desire values. Nominal values are 918.75 for downlink and 903 for uplink. Values must be between 902.25 and 903.75 or between 910 and 918.75 for the downlink. Values must be between 912.75 and 918.75 for the uplink.Operating the MPI 6000 Reader1. Select Tags > FDOT.2. Enter hex data into the IT2200 Write Data and SeGo Page Data fields. Use 32 hex characters for IT2200 (Allegro) and 16 hex characters for SeGo. This is the data that is going to be written to the tag.3. Select Read or Write in the SeGo Sequence Field. This sets the Read or Write parameters for both IT2200 and SeGo tags.4. Press Start to begin tag processing. 5. Tag responses should appear in the IT2200 and SeGo fields.6. To stop the display or the response count, select the check boxes.7. Press Stop to end tag processing.8. Press Exit to close the FDOT page.MPI 6000 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.
MPI 6000 Multi-Protocol Reader System Guide3-8
4Lane Tuning Guidelines
4-3Chapter 4Lane Tuning Guidelines This chapter explains the importance of lane tuning for optimum automatic vehicle identification (AVI) system performance and describes the MPI 6000 functions and features that can assist you in tuning an AVI lane.Why You Need to Tune a LaneLane 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 perfor-mance dictated by the lane’s traffic requirements. Typically, consideration of these factors is necessary for each individual lane, although in some installations it may be possible to identify broader solutions, then apply these solutions to certain classes of lanes having similar characteristics, followed by additional fine tuning on an individ-ual lane-by-lane basis. This process is necessitated by the radio link, which is subject to varying factors such as lane type, the geometry of fixed objects near the capture zone, interference from external sources, adjacent lane interference, natural non-homogeneity of RF field strength within the ideal capture zone, and varying tag envi-ronments. These factors may vary widely within an installation and from lane to lane within the same plaza. Furthermore, the type of technologies involved, either IT2200, American Trucking Association (ATA), eGo, eGo Plus, Title 21 or Inter-Agency Group (IAG), will play a significant role in tuning the lanes for operation. Knowing the appropriate factors and available tools is necessary for the set-up and troubleshoot-ing of AVI lanes.Required EquipmentYou will need the following equipment and tools when you tune a lane:TBDLane Tuning ParametersLane tuning parameters can be altered to effect required outcomes. This section lists the properties that can be used to tune a lane.Traffic RequirementsThe traffic requirements of lane tuning include the following characteristics:•The duration of the tag transaction, also known as handshake
MPI 6000 Multi-Protocol Reader System Guide4-4•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 mixed-use lanes, which may dictate the desired first read point•The width of the laneTraffic requirements are further defined by two terms, tag transaction or handshake and capture zone or lane footprint.Tag Transaction or HandshakeA handshake is defined as one complete transaction between a tag and the AVI equip-ment. The handshake is defined as a complete transaction because in many cases the transaction consists of more than a simple read. The transaction may be a read com-mand followed by a general acknowledgment (GENACK), or a read command fol-lowed by a write command followed by a GENACK, or some other complex sequence of commands. Each part of the handshake requires time, and the transaction with the tag cannot be considered complete unless all the components have been completed. To this end, there will be a minimum time associated with the handshake. It may be as lit-tle as a few milliseconds, or as high as 30 milliseconds or more.Capture Zone or Lane FootprintThe footprint is the length of the capture zone measured on the pavement, starting at the point of the first tag read and ending where tag reads stop, typically three or four feet past the receive antenna (Figure 4-1). This value is based on the actual measure-ments of the capture zones of at least five diversely different vehicles equipped with properly mounted tags. Ideally, RF margin plots taken at the time the footprint are measured on a foot-by-foot basis, but for the basic measurements discussed in this guide, all that is needed is the total footprint length from first read to last read.
Lane Tuning Guidelines4-5Figure 4-1 Field Size, Shape, and Antenna Polarization Define the Reading RangeOne concern for lane tuning is how large the footprint needs to be for acceptable sys-tem 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.For example, if a toll agency requires an IT2200 tag read followed by a string of five GENACKs, this constitutes a complete transaction, and the total time would be four milliseconds for the IT2200 tag read plus four milliseconds for the five GENACKs for a total of eight milliseconds for the entire handshake. Four complete handshakes require 32 milliseconds. If the same agency has a maximum speed requirement of 60 mph through the lane, this translates to 88 feet per second, or 11.36 milliseconds/foot. The agency could use the system with a footprint that is 32 milliseconds in duration, which at 60 mph, translates to 11.36 milliseconds per foot or 2.82 feet. Any additional footprint increases the reliability of the system because the system provides more chances for the tag to interact with the reader.1 read @ 4 milliseconds per read = 4 milliseconds5 GENACK @ 0.8 milliseconds per GENACK= 4 milliseconds = 8 milliseconds total, each full handshakeFor another example, if the toll agency requires three pages to be read from the tag, followed by three pages of data to be written to the tag, followed by five GENACKS, the total transaction time isTo Be Provided.
MPI 6000 Multi-Protocol Reader System Guide4-63 reads @ 4 milliseconds each = 12 milliseconds3 writes @ 4 milliseconds each = 12 milliseconds5 GENACKs @ 0.8 milliseconds each= 4 milliseconds= 28 milliseconds total, each full hand-shakeTo 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.47 feet long to satisfy this requirement.This footprint value can change depending on the use of time division multiplexing (TDM), which will increase the footprint requirements, or by using more sophisticated polling methods, which may reduce the footprint requirements. Furthermore, the times presented in this example for the individual components of the transaction can vary. For example, a password-protected read or write operation can take longer to com-plete than an ordinary read or write and can impact the overall statistical reliability of the transaction. Note: Please consult with TransCore to assess the impact of the more sophisticated types of transactions.Given the uncertainties of any RF link due to reasons already discussed in this section, a short transaction of only a few milliseconds has a statistically better chance of suc-ceeding than will a complex, longer 30-millisecond transaction. The tag is assumed to remain in the footprint for a minimum period of time relative to the maximum vehicle speed and the size of the footprint.Once the length of the footprint has been determined, the presence of light curtains or detection loops may dictate the point at which the first tag read should occur. Also, manned lanes or mixed-use lanes typically require that the tag read occur at least a few feet in front of the toll collection point. The speed requirements may be reduced for these lanes and, hence, the footprint size. The point of the first read may be controlled by antenna placement, uptilt angle, and RF power, which are discussed later in this chapter. Likewise, if the lane is exceptionally wide or if there is a need for better cov-erage toward the lane sides, the antenna may be mounted higher or in line with other antennas. A lower gain antenna may be used to increase the side coverage.RF FactorsThe RF factors involved in tuning an AVI system may include the following parame-ters:•The downlink and uplink transmitted RF power•Range control adjustments that can be made to the receiver•Antenna type•Antenna mounting, that is, lane position (relative to payment point, angle, and height)
Lane Tuning Guidelines4-7•The downlink and uplink source frequencies and interference from lanes sharing same or close frequencies•The antenna-tag orientationRF power is the most important RF factor in lane tuning. Thirty dBm translates to one-watt nominal power. Increasing the RF power will, in general, increase the footprint. There are other factors involved such as antenna angle and placement that may affect the footprint, but increasing RF power will generally increase the signal and increase both the footprint and the RF margins in the lane.Because the RF power can create interference in adjacent or nearby lanes and degrade the performance of the adjacent lane, the RF power should be adjusted so that mini-mum power is used to achieve the desired results.Downlink and Uplink Transmitted RF PowerDownlink signal is the signal transmitted from the reader to the tag, and uplink signal is the signal reflected back to the receiver from the tag. The impact of the downlink and uplink power on footprint and lane performance is heavily dependent on the pro-tocol type(s) in use in the lane. Table x-x (to be provided) is a general guide to the influence of RF power on the footprint by protocol. Some of these factors are interre-lated to such aspects as antenna angle, antenna placement, and tag placement, so use this information as a starting point and consider other aspects of lane tuning when operating on any given lane.Both downlink and uplink power are adjustable by tag protocol. In other words, in multiple protocol systems, the RF power can be adjusted for each tag protocol in use, independent of the other tag protocol.Range Control AdjustmentsAdjusting the range control allows the user to adjust the footprint separate from any setting of the RF power. It is an adjustment on the sensitivity of the receiver and is done independently for each tag protocol. The units are in decibels and vary from 0 to 20dB, with the higher number giving the smaller footprint. Range control always exerts an effect on the footprint and performance separate from the tag protocol, but the degree of the effect may be dependent on RF power and antenna parameters as well. The most common use of range control is in multiple protocol situations, where the first read point of tags with two differing protocols must be made to coincide within a lane. In this situation, the power and antenna parameters are adjusted so that the weaker protocol tags are reading at the appointed position, then range control is used to adjust the first read point of the stronger protocol tags down to the same posi-tion as the other protocol. Range control can also be used in a single protocol situation to fine tune the first read position.Frequency Considerations — Single ProtocolTBDIT2200 or Title 21 Tag ProtocolTBDThis uplink frequency separation should repeat for additional lanes.eGo Tag ProtocolTBD
MPI 6000 Multi-Protocol Reader System Guide4-8ATA Tag ProtocolTBDIAG Tag ProtocolTBDFrequency Considerations — Multiple ProtocolsTBDAntenna-Tag OrientationAntennas 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. If the tag is placed to the side of the windshield, the antennas should be placed overhead to the side matching the tag placement, or a side-mounted antenna should be used. There are some exceptions to this, and in the overall system planning, any variation from this rule should be discussed with TransCore at the earli-est possible time to minimize additional costs for altering the lane design, especially after construction has started. Incorrect antenna placement may render the system’s performance unacceptable and result in the eventual and expensive refitting of antenna and communication hardware. Figure 4-3 shows interior tag mounting loca-tions, and Figure 4-4 shows exterior tag mounting locations.Figure 4-2 Tag Orientation with Linearly Polarized Antenna
Lane Tuning Guidelines4-9Figure 4-3 Upper Center Interior Windshield Tag PlacementFigure 4-4 Correct Exterior Tag PlacementAntenna Uptilt AngleAdjusting 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. However, at some uptilt angle, a point of diminish-ing return is reached where the RF power is too dispersed to activate the tag at the start of the footprint. Increasing the antenna angle beyond this point will not move the first read point farther out and may actually decrease the RF margin within the cap-ture zone. Also, increasing the angle may produce an area near the start of the capture zone with spotty reads. The most commonly used range for antenna uptilt angles is from 10 to 25 degrees with the lower angles producing the sharpest, most clearly defined read zones. Setting the antenna uptilt angle below 10 degrees may cause problems in reading tags mounted on windshields that are nearly vertical and in read-
MPI 6000 Multi-Protocol Reader System Guide4-10ing license plate tags.Note: TransCore does not recommend placing the antenna uptilt angles at less than five degrees.Figure 4-5 Overhead Antenna Tilt AngleAntenna Positioning Within the LaneIn 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 pas-senger side of the traffic lane. Antenna position in the lane also impacts lane performance. Antenna mounting brackets should be designed so that you can adjust the antennas from front to back and from side to side. In lanes that have no vehicle framing, such as some express lanes, the front-to-back adjustment is not critical and can be minimized or eliminated. But, in these lanes it is still valid to have at least ±2 feet (±0.61 m) of side adjustment. Side adjustment may be critical in places where vehicles tend to travel to one side or another, such as in lanes that are wider than 12 feet (3.65 m). You can move the pair of antennas from side to side so that the centerline between the antenna pair is located over the area of the lane where the majority of traffic travels. RF reflec-tors, such as toll booths and Jersey barriers, may require you to make side adjustments to achieve adequate coverage to one side or the other.The portion of the footprint with the highest RF margin has the highest probability of a successful tag transaction. This portion of the footprint is the area directly under the antenna and extending forward (upstream) a number of feet. If the length of the footprint is not an issue, such as the situa-tion in some lower speed mixed-use lanes, but the point of first read is critical, it may be advisable to use a low antenna angle. Next, adjust the antenna position so that the first read occurs at the desired point. Adjust the antenna position instead of fixing the antenna position and adjusting the first read point by manipulating the antenna uptilt angle or the RF power. This adjustment may
Lane Tuning Guidelines4-11enable you to operate the lane at a lower RF power, which is usually the preferred oper-ational mode.Signal TimingTBD
MPI 6000 Multi-Protocol Reader System Guide4-12
Lane Tuning Guidelines4-13
MPI 6000 Multi-Protocol Reader System Guide4-14
5Optimizing MPI 6000 Reader System Performance
5-3Chapter 5Optimizing MPI 6000 Reader System PerformanceThis chapter provides information to optimize the MPI 6000 performance and reduce cross-lane interference.Cross-Lane Interference in RFID SystemsRadio frequency identification (RFID) systems are subject to various types of interfer-ence 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.What Is Cross-Lane Interference?Cross-lane interference occurs when the RF generated in one toll lane interrupts the RFID operation in another lane that causes the affected lane to perform poorly. Before diagnosing cross-lane interference, it is necessary to understand what constitutes a sat-isfactorily performing lane.Determining Acceptable Lane PerformanceThe criteria for optimal lane performance are usually set by the customer and can vary according to the site requirements. In testing, acceptable lane operation criteria typi-cally are determined by the length of the RF footprint and the speed of the test vehicle. Usually, a test vehicle’s speed is limited by the amount of the toll lane that can be used for starting and stopping distances. Usually, testing speed is limited to 20 miles per hour (mph) or 32 kilometers per hour (kph) or less.An ideally performing toll lane will produce one handshake for every 4 milliseconds of transaction time. At 20 mph (32 kph), the vehicle uses 34 milliseconds to travel through 1.0 foot (0.3 m) of the footprint. If the footprint is 8 feet (2.4 m), this means that the vehicle will spend approximately 272 milliseconds in the footprint. Based on a vehicle speed of 20 mph (32 kph) and an 8-foot (2.4m) footprint, this yields an ideal maximum number of 68 handshakes. Nulls and voids within the RF footprint will lower this number, as will any other local sources of RF noise and stray reflections. A rule of thumb for lane performance is to have 40 to 60 handshakes within an 8-foot (2.4m) footprint with a test vehicle traveling at 20 mph (32 kph). A system that oper-ates with less than 40 handshakes should be tested for cross-lane interference.
MPI 6000 Multi-Protocol Reader System Guide5-4Identifying Cross-Lane InterferenceCross-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 satisfacto-rily and then begins to show a degradation in system performance, that is, an increas-ing number of missed reads or a spotty read pattern, there is a probability that cross-lane interference is occurring.Cross-lane interference can be caused by the following:•A downlink antenna transmitting strong RF beyond its lane boundaries•Reflection of RF from fixed objects (e.g., toll plazas with low, metal roofs)•Reflection of RF from moving objects (e.g., a passing tractor-trailer in an adjacent lane)A typical toll lane application encompasses more than a single lane. In some cases a toll plaza can have more than eight lanes with each lane having separate RF transmit-ting (downlink) and receiving (uplink) antennas. As shown in Figure 5-1, the RF transmitted within a lane is not bound by physical dividers such as lane barriers. With multiple-lane applications, transmissions out of a lane can create areas of possible cross-lane interference.Figure 5-1 RF Footprint Extends Beyond Lane Boundaries
Optimizing MPI 6000 Reader System Performance5-5Diagnosing Cross-Lane InterferenceTo 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 sin-gle lane. When tuning a lane be sure to use a tag and vehicle that have been used con-sistently at your site.Once the lane has been tuned and you determine that it is working satisfactorily, per-form lane tuning procedures in the adjacent lane. Continue for each lane in the toll plaza.If each adjacent lane tuning causes the previously tuned lane to start performing poorly (i.e., spotty read zone or areas of no reads), cross-lane interference is indicated.Remedying Cross-Lane InterferenceSeveral methods exist to remedy cross-lane interference. These remedies are accom-plished by software or hardware changes, or a combination of both. A remedy at one site may not be appropriate at another site, so iterative methods of correcting this interference are necessary.Frequency SeparationReview the toll plaza frequency plan that was developed during the eGo 4110A Reader System installation phase. There are two frequencies for each reader: down-link and uplink. For the eGo 4110A Reader System, all readers share the same down-link frequency, which is generally set to 918.75 MHz. Uplink frequencies should alternate between 903.00 MHz and 910.00 MHz in adjacent lanes. For example, a four-lane plaza would have the frequencies shown in Table 5-1.RF PowerA good rule of thumb when configuring a toll plaza is to set the RF attenuation at a lower output and increase the RF power level as needed for optimal system operation. This practice may provide you with RF attenuation settings at which your reader sys-tem can operate with minimal adjustment for cross-lane interference.Table 5-1 Frequency Plan for Four-Lane Toll Plaza Using IT2200-series or Title 21 Tag ProtocolLane Downlink Frequency Uplink Frequency1918.75 MHz 903.00 MHz2918.75 MHz 910.00 MHz3918.75 MHz 903.00 MHz4918.75 MHz 910.00 MHz
MPI 6000 Multi-Protocol Reader System Guide5-6Time-Division MultiplexingIn 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 oper-ate only during interleaved time periods.The TDM interconnect is provided via a differential RS–485 interface to a DB9 con-nector that is located on the reader card’s expansion board connector in slot 2. This connection provides a synchronization interface between readers where RF interfer-ence between readers is reduced by multiplexing the RF reader transmission to inde-pendent time slots. Allowing each reader or group of readers to operate at an allotted time eliminates interference from readers in adjacent lanes.Although you need to configure the readers to operate using TDM, the interface con-nection for TDM can be provided to all the readers in a plaza before or during installa-tion by connecting a pair of wires to the DB9 TDM connector of each reader as shown in Figure 5-2. No other equipment is necessary for the interconnection circuit. You need to follow the polarity conventions as shown because this interface is polarity dependent.Figure 5-2 TDM Configuration ExampleTransCore recommends Belden 89182 or 8132 cable. Using these low-loss, low-capacitance twisted-pair cable, the maximum distance is 1000 feet (305 m). Cables with lower capacitance can be used to run the TDM cables for longer distances while maintaining signal integrity. This maximum distance may be slightly longer or shorter depending on the cable used.
Optimizing MPI 6000 Reader System Performance5-7Because 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.To implement TDM, you must configure only one reader in the group as a master reader for the TDM function. This reader will have a slightly shorter synchronization period than the rest of the readers connected to it.Note: The TDM synchronization period is set in 1.0-millisecond increments, whereas the TDM delay and TDM duration are set in 0.5-millisecond increments.Figure 5-3 illustrates a typical plaza configuration using TDM. There are three time slots with three uplink frequencies. All the readers are configured with a downlink fre-quency of 916 MHz.Table 5-2 TDM Connector Pin Name In/Out Description Recommended Connection1 N/C N/A No connection N/C2 N/C N/A No connection N/C3 N/C N/A No connection N/C4 N/C N/A No connection N/C5 N/C N/A No connection N/C6 N/C N/A No connection N/C7TDM (+) In/Out TDM synchronization positive Connect all red pin 7 wires together.8TDM (-) In/Out TDM synchronization negative Connect all black pin 8 wires together.9 N/C N/A No connection N/C
MPI 6000 Multi-Protocol Reader System Guide5-8Figure 5-3 Typical Plaza Configuration Using TDMThe 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 dura-tion 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. Table 5-3 lists the settings for each reader in each time slot.Figure 5-4 TDM Timing Diagram
Optimizing MPI 6000 Reader System Performance5-9Note: The TDM synchronization period is set in 1.0-millisecond increments, and the TDM delay and TDM duration are set in 0.5-millisecond increments.The TDM example shown in Figure 5-4 and Table 5-3 was designed with three time slots; however, two time slots can be used instead depending on the number of frequency channels and the timing. Implementing TDM with three time slots reduces the time avaliable for a transaction in a given lane by a factor of three. Similarly, implementing TDM with two time slots reduces the time avaliable for a transaction in a given lane by a factor of two. Although it is possible to implement four or more time slots, it is unlikely that more than three time slots are necessary or beneficial.TransCore recommends that a guard-band of 1 millisecond be used between each of the time slots to ensure that the readers in the previous time slot have sufficient time to settle before the readers in the next time slot become active. This procedure can be done by setting the TDM delay on each reader to account for a duration that is 1 milli-second longer than the actual duration and setting the TDM synchronization period to a value that accounts for a duration 1 millisecond longer than the actual duration.All the readers designated as slave readers in the plaza on the same TDM bus are dependent on the synchronization signal from the master reader. In the event that the synchronization pulse from the master reader stops functioning, or the TDM signal from the master reader becomes disconnected from the rest of the readers in the plaza, a provision in the readers allows a slave reader to serve as a backup master reader and supply the synchronization pulse. Although this situation will cause the slave reader to send an error message to the lane controller, the slave reader will continue to function and provide the TDM synchronization pulse for the other operational readers on the remaining TDM bus.Because the location in the plaza where the signal break may occur is unknown, TransCore recommends that provisions for a break anywhere in the line be consid-ered. Although the TDM synchronization period settings for the slave readers could all be set at the same single value of 1 millisecond longer than the value used for the TDM synchronization period on the master reader, they should be set at unique values increasing at 1 millisecond for each reader, starting at a value 1 millisecond higher than that of the master reader. This setting ensures that only one reader will provide the synchronization pulse to a given group of readers in the plaza remaining on the Table 5-3 TDM Timing SettingsTime Slot TDM Delay TDM Duration TDM Synchronization PeriodaT1 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.
MPI 6000 Multi-Protocol Reader System Guide5-10TDM bus in the event of either a TDM connection failure, or a failure of the TDM cir-cuit 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 RemediesBy adjusting the angle or position of the downlink and uplink antennas, you may be able to minimize cross-lane interference.WarningSwitch off RF power before working on antennas.Adjusting the Antenna’s Uptilt AngleLowering an antenna’s uptilt angle between the antenna cover and the horizon gener-ally reduces the interference (Figure 5-5).Figure 5-5 Antenna Tilt Angle Adjustment
Optimizing MPI 6000 Reader System Performance5-11Adjusting the Antenna Side AngleIn 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. If the side angle is too large and the RF footprint is projecting toward the other antenna, you can reduce the side angle so that the antenna’s RF footprint is evenly placed within the correct lane boundaries. Figure 5-6 shows the downlink antenna being tilted toward the center of the lane.Figure 5-6 Downlink Antenna Side Angle AdjustmentAdjusting the Antenna PlacementBesides adjusting the antenna angles, you can also move the antenna farther back into its overhead location so that the read zone does not extend as far in front of the trans-action area. By shortening the read zone, you may be able to reduce the required RF output power, which will result in reduced probability of cross-lane interference.You can also move the antenna pair from side to side within the lane. This adjustment is used in lanes where the traffic travels closer to one side than another. For example, in manned toll lanes, traffic tends to drive closer to the left side of the lane. The cen-terline between the antennas can be shifted to the left to compensate for this tendency.Other Site ModificationsIn rare instances, applying radar-absorbing foam to fixed areas of the toll plaza (e.g., metal roof) may reduce the incidence of interference.
MPI 6000 Multi-Protocol Reader System Guide5-12
6General Software Information
6-3Chapter 6General Software InformationThis chapter provides general software information about the design of MPI 6000 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.General Software InformationAll tag programmer commands are preceded by a start-of-message (<som>) amper-sand character (&) followed by an end-of-message (<eom>) percent character (%). All data after the <eom> character is ignored until the next <som> is detected.Any & character that occurs in the message between the <som> and <eom> is con-verted to the backslash and at character (\@) sequence. Any % character is converted to the \? character sequence. All \ characters are converted to the \\ sequence. All <som> and <eom> character conversions are performed after the cyclic redundancy check (CRC) has been performed on the transmit data and before the CRC is per-formed on the receive data.Reader commands contain only the message information and are not preceded by the & and are not followed by the %.Plan and OrganizeTags compatible with the eGo 4110A Reader System have sophisticated memory organization. TransCore encourages the user to become familiar with the use and organization of tag memory. Before starting a programming session, TransCore rec-ommends that you plan and organize the development steps.Communications ProtocolsThe MPI 6000 communicates with a host by Ethernet or serial communications proto-cols.EthernetThe MPI 6000 can communicate via an Ethernet communications protocol. This con-nection requires an RJ–45 connector for the Ethernet receptacle. The Ethernet connec-tor is an RJ-45 jack and uses a 10-base T interface. If you use a switch between the MPI 6000 and the host personal computer (PC), no crossover cable is required. If the MPI 6000 is connected directly to the host PC then a crossover cable is required. If the
MPI 6000 Multi-Protocol Reader System Guide6-4host PC is set to Dynamic TransCore recommends that you set the IP address to Static. Table 6-1 lists the connector pin assignments.Communications RS–232The connector is an industry standard DB-9M plug. Table 6-2 lists this connector pin assignments.The RS-232B/Time-division multiplexing (TDM) connector is an 8-pin terminal block header. The TDM signals must be isolated. Table 6-3 lists this connector pin assignments.Table 6-1 Ethernet ConnectorPin Signal Description1TPTX+ Output Differential Transmit Data +2TPTX- Output Differential Transmit Data -3 TPRX+ Input Differential Receive Data +4NOT CONNECTED N/A5NOT CONNECTED N/A6TPRX- Input Differential Receive Data -7NOT CONNECTED N/A8NOT CONNECTED N/ATable 6-2 Communications RS-232 Connector ParametersPin Signal Description1RSD Received line signal detect (not connected)2RXD Receive Data3TXD Transmit Data4DTR Data Terminal Ready (not connected)5GND Ground6DSR Data Set Ready (not connected)7RTS Request to Send8CTS Clear to Send9RI Ring indicator (not connected)
General Software Information6-5Diagnostic RS–232 Serial CommunicationsThe MPI 6000 can communicate via a serial, RS–232, communications protocol (Table 6-4). The diagnostic RS–232 port can be used to display the operating system boot sequence. If you connect the MPI 6000 directly to a host PC serial port, you must use a null-modem connector.Diagnostic Commands (Mike?)By using the version command, you can display data about the configuration of the MPI 6000 including its Internet protocol (IP) address.The RS-232 diagnostic connector can be used to check the external input/output sta-tus. Table 6-5 lists this connector pin assignments.Table 6-3 RS-232B/TDM Connector Parameters Pin Signal Description1TXD Transmit Data2RXD Receive Data3DTR Data Terminal Ready (not connected)4RTS Request to Send5CTS Clear to Send6GND Ground7TDM + TDM positive signal8TDM - TDM negative signalTable 6-4 RS-232 Connector SpecificationsConnector Type 9 pin D-sub male Protocol RS-232 Baud 9600Bits 8Parity NoneStop Bits 1Flow Control None
MPI 6000 Multi-Protocol Reader System Guide6-6Reader Command ProtocolThe MPI 6000 implements command requests, data acknowledgements, command responses, asynchronous responses, software flow control, and unsolicited status mes-sages as required for AVI system configuration and operation. The messages are defined in this section.Command request messages are initiated and used by the host to request specific actions to be performed by the MPI 6000.Data acknowledge messages are initiated and used by the MPI 6000 to signal the reception of command request messages received from the host. Additionally, data acknowledge messages are initiated and used by the host to signal the reception of command response, asynchronous response, software flow control and unsolicited sta-tus messages received from the MPI 6000. Command response messages are initiated by the MPI 6000 in response to specific command request messages received from the host.Asynchronous response messages are optionally initiated by the MPI 6000 in response to specific command request messages received from the host.Software flow control messages are initiated and used by the MPI 60000 System to inform the host to start or stop sending command request messages. Additionally, soft-ware flow control messages are initiated and used by the host to inform the MPI 60000 System to start or stop sending messages.Unsolicited status messages are initiated and used by the MPI 60000 System to inform the host about specific warning or error conditions in the MPI 60000 System.The host sends command request messages to the MPI 6000. The MPI 6000 after receiving command request messages from the host sends data acknowledge mes-sages, command response messages, asynchronous response messages and if required Table 6-5 Diagnostic RS-232 Connector ParametersPin Signal Description15V PWR 5V power supply for I/O board2GND GND3I/O Signal 1 Input/output signal 14I/O Signal 2 Input/output signal 25I/O Signal 3 Input/output signal 36I/O Signal 4 Input/output signal 47Tag in Field 1 Contact Closure 1 for Tag in Field Signal8Tag in Field 2 Contact Closure 2 for Tag in Field Signal
General Software Information6-7software flow control messages to the host. The host on receiving command response messages, asynchronous response messages and software flow control messages from the MPI 6000 sends data acknowledge messages to the MPI 6000.Additionally, the MPI 6000 sends unsolicited status messages to the host. The host on receiving unsolicited status messages from the MPI 6000 sends data acknowledge messages to the MPI 6000.The MPI 6000 implements message sequence numbers and command sequence num-bers in all of the message types (e.g. command request, data acknowledge, command response, asynchronous response, software flow control and unsolicited status). The host and the MPI 6000 must implement independent transmit and receive counters for both the message sequence numbers and the command sequence numbers. The trans-mit counters are used in the generation of the transmitted messages and the receive counters are used in the received message out-of-sequence error checking. An out-of-sequence error indicates that a message has been missed.The host’s message sequence numbers independently track the number of messages sent to the MPI 6000. The MPI 6000’s message sequence numbers independently track the number of messages sent to the host. These message sequence numbers are used on the receiving end to determine if a message has been missed. See the software communication sequence number controls section for more details.The host’s command sequence numbers for each command group independently track the number of command request messages sent to the MPI 6000. The MPI 6000’s command sequence numbers for each command group independently track the num-ber of software flow control and unsolicited status messages sent to the host. These command sequence numbers are used on the receiving end to determine if the appro-priate message as specified above has been missed. See the software communication sequence number controls section for more details.UDP/IP Fast Ethernet Communications ProtocolThe UDP/IP fast Ethernet communications protocol implements the UDP/IP fast Ethernet protocol as specified in the RealFast UDP/IP Core Design Specification (RealFast Document Number RFHC04026-V042).Command Request MessageThe host sends command request messages to the MPI 6000 as required for system operation. The host and the MPI 6000 uses the following UDP/IP fast Ethernet com-munications command request message shown here:<len> <msgSeqNum> <cmd> <cmdSeqNum> [<data>] <checksum>where<len> = length, a word that specifies the number of bytes in the entire message.<msgSeqNum> = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.
MPI 6000 Multi-Protocol Reader System Guide6-8<cmd> = command, a word that specifies the system command. See the command sections for details.<cmdSeqNum> = command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.[<data>] = optional data payload that varies in length from 0 to 65 bytes and is asso-ciated with each specific command. See the command sections for details.<checksum> = checksum, a byte that specifies the checksum of the message.Data Acknowledge MessageThe MPI 6000 sends data acknowledge messages to the host after receiving command request messages from the host.The host sends data acknowledge messages to the MPI 6000 after receiving command response messages, asynchronous response messages, software flow control messages and unsolicited status messages from the MPI 6000. The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications data acknowledge message as shown here:<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <msgSeqNumAck> <checksum>where<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> - response, word that specifies the system response. See the response sections for details.<msgSeqNumAck> - message sequence number acknowledge, byte that specifies the message sequence number of the message being acknowledged. See the software communication sequence number controls section for details.<checksum> - checksum, byte that specifies the checksum of the message.Command Response MessageThe MPI 6000 after receiving command request messages from the host sends com-mand response messages to the host.The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications command response message shown here:
General Software Information6-9<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <checksum>where<len> = length, a word that specifies the number of bytes in the entire message.<msgSeqNum> = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> = command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> = command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> = response, a word that specifies the system response. See the response sec-tions for details.[<data>] = optional data payload that varies in length from 0 to 63 bytes and is asso-ciated with each specific response. See the response sections for details.<checksum> = checksum, a byte that specifies the checksum of the message.Asynchronous Response MessageThe MPI 6000 after receiving command request messages from the host optionally sends asynchronous response messages to the host.The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications asynchronous response message shown here:<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <checksum>where<len> = length, a word that specifies the number of bytes in the entire message.<msgSeqNum> = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> = command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> = command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> = response, a word that specifies the system response. See the response sec-tions for details.[<data>] - optional data payload that varies in length from 0 to 63 bytes and is associ-ated with each specific response. See the response sections for details.<checksum> = checksum, a byte that specifies the checksum of the message.
MPI 6000 Multi-Protocol Reader System Guide6-10 Software Flow Control MessageThe MPI 6000 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 MPI 6000 as required for host operation. The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications software flow control message shown here:<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <checksum>where<len> = length, a word that specifies the number of bytes in the entire message.<msgSeqNum> = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> = command, a word that specifies the system command. See the command sections for details.<cmdSeqNum> - command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> = response, a word that specifies the system response. See the response sec-tions for details.<checksum> = checksum, a byte that specifies the checksum of the message.Unsolicited Status MessageThe MPI 6000 sends unsolicited status messages to the host as required for system operation.The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications unsolicited status message shown here:<len> <msgSeqNum> <cmd> <cmdSeqNum> <status> [<data>] <checksum>where<len> = length, a word that specifies the number of bytes in the entire message.<msgSeqNum> = message sequence number, a byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> = command, a word that specifies the system command. See the command sections for details.<cmdSeqNum> = command sequence number, a byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.
General Software Information6-11<status> = status, a word that specifies the system status. See the response sections for details.[<data>] = optional data payload that varies in length from 0 to 63 bytes and is asso-ciated with each specific response. See the response sections for details.<checksum> = checksum, a byte that specifies the checksum of the message.Serial Communications ProtocolThe serial communications protocol implements the TransCore error correction proto-col (ECP) serial standard.Command Request MessageThe host sends command request messages to the MPI 6000 as required for system operation.The host and the MPI 6000 uses the following serial communications command request message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> [<data>] <crc16> <eom>where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.[<data>] - optional data payload that varies in length from 0 to 65 bytes and is associ-ated with each specific command. See the command sections for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynome of 1021H and an initial value of FFFFH for a CCITT16 type CRC.<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.
MPI 6000 Multi-Protocol Reader System Guide6-12Data Acknowledge MessageThe MPI 6000 after receiving command request messages from the host sends data acknowledge messages to the host.The host after receiving command response messages, asynchronous response mes-sages, software flow control messages and unsolicited status messages from the MPI 6000 sends data acknowledge messages to the MPI 6000. The host and the MPI 6000 uses the following serial communications data acknowl-edge message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <msgSeqNumAck> <crc16> <eom>where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> - response, word that specifies the system response. See the response sections for details.<msgSeqNumAck> - message sequence number acknowledge, byte that specifies the message sequence number of the message being acknowledged. See the software communication sequence number controls section for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynome of 1021H and an initial value of FFFFH for a CCITT16 type CRC.<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.Command Response MessageThe MPI 6000 after receiving command request messages from the host sends com-mand response messages to the host.The host and the MPI 6000 uses the following serial communications command response message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <crc16> <eom>
General Software Information6-13where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> - response, word that specifies the system response. See the response sections for details.[<data>] - optional data payload that varies in length from 0 to 63 bytes and is associ-ated with each specific response. See the response sections for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynome of 1021H and an initial value of FFFFH for a CCITT16 type CRC.<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.Asynchronous Response MessageThe MPI 6000 after receiving command request messages from the host optionally sends asynchronous response messages to the host.The host and the MPI 6000 uses the following serial communications asynchronous response message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <crc16> <eom>where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.
MPI 6000 Multi-Protocol Reader System Guide6-14<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> - response, word that specifies the system response. See the response sections for details.[<data>] - optional data payload that varies in length from 0 to 63 bytes and is associ-ated with each specific response. See the response sections for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynomial of 1021H and an initial value of FFFFH for a CCITT16 type CRC.<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.Software Flow Control MessageThe MPI 6000 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 MPI 6000 as required for host operation.The host and the MPI 6000 uses the following serial communications software flow control message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <crc16> <eom>where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<resp> - response, word that specifies the system response. See the response sections for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynome of 1021H and an initial value of FFFFH for a CCITT16 type CRC.
General Software Information6-15<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.Unsolicited Status MessageThe MPI 6000 sends unsolicited status messages to the host as required for system operation.The host and the MPI 6000 uses the following serial communications unsolicited sta-tus message as shown here:<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <status> [<data>] <crc16> <eom>where<som> - start of message, byte that specifies the start of the message which is defined as the ASCII character &.<len> - length, word that specifies the number of bytes in the entire message.<msgSeqNum> - message sequence number, byte that specifies the message sequence number of the message. See the software communication sequence number controls section for details.<cmd> - command, word that specifies the system command. See the command sec-tions for details.<cmdSeqNum> - command sequence number, byte that specifies the command sequence number of the message. See the software communication sequence number controls section for details.<status> - status, word that specifies the system status. See the response sections for details. [<data>] - optional data payload that varies in length from 0 to 63 bytes and is asso-ciated with each specific response. See the response sections for details.<crc16> - 16 bit cyclic redundancy check, word that specifies the 16 bit cyclic redun-dancy check of the message exclusive of the <som> and <eom> bytes. The polyno-mial for the CRC calculation is X16+X12+X5+1 with a divisor polynomial of 1021H and an initial value of FFFFH for a CCITT16 type CRC.<eom> - end of message, byte that specifies the end of the message which is defined as the ASCII character %.
MPI 6000 Multi-Protocol Reader System Guide6-16
7Configuration Commands and Responses
7-3Chapter 7Configuration Commands and ResponsesThis chapter describes the MPI 6000 interface commands that are used to configure the reader.Configuring the MPI 6000MPI 6000 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 MPI 6000 Reader can read tags.Required Commands to Set Up MPI 6000 ReaderThis section describes the configuration commands that are used to set up the MPI 6000.Set FrequencyThis section describes the Set Frequency command that is used to set the MPI 6000 frequency. Figure 7-1 shows the command transaction process. Table 7-1 lists the Set Frequency command data.Figure 7-1 Set Frequency Command ProcessThis command sets the A Counter and B Counter least significant bits (LSB) for the specified source.Table 7-1 Set Frequency Command ParametersSet Frequency Command Data Data PayloadBit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0Set Frequency Command 08HUnused Source 0XH
MPI 6000 Multi-Protocol Reader System Guide7-4Table 7-2 shows the Set Frequency Response parameters.The Source field identifies the source for the associated N Counter information (Table 7-3).A Counter – This field contains the data for the binary five-bit A Counter of the PLL. The A and B counters combine to form the 18-bit N Counter. The valid range of the A Counter data field is 00H to 1FH.B Counter LSBs – This field contains the LSB for the binary 13-bit B Counter of the PLL. The A and B counters combine to form the 18-bit N Counter. The valid range of the data field is 0H to 3H. The B Counter value is 007XH, where X = B Counter LSBs.The PLL frequency spreadsheet contains the values used to set the A Counter and the B Counter. This command will be modified to allow the system to send frequency val-ues instead of A and B counters.Unused A Counter XXHUnused B Counter LSBs 0XHCarriage Return 0DHTable 7-1 Set Frequency Command ParametersTable 7-2 Set Frequency Response Parameters Set Frequency Response Data Data PayloadBit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0Set Frequency Command 08HUnused Source 0XHAcknowledge 00HCarriage Return 0DHTable 7-3 Descriptions of SourcesSource Definition0Source 11Source 2
Configuration Commands and Responses7-5System Interface Command Group CommandsThis section describes the system commands used to configure the MPI 6000.Each of the system command group commands is listed in this section.Table 7-4 System Interface Command GroupSystem Interface Command Command CodeSystem Identify 0000HSet Communications Baud Rate 0001HGet Communications Baud Rate 0002HSet Time and Date 0003HGet Time and Date 0004HFirmware Download 0005HReset Reader 0006HGet Stored Tag Response Message 0007HGet Number of Stored Tag Response Messages 0008HDelete All Stored Tag Response Messages 0009HGet System Startup Status 000AHGet Lane Controller Interface Status 000BHGet System Interface Status 000CHGet DigBrd Hdwr Remote Inventory 000DHGet DigBrd CPU Boot Fmwr Remote Inventory 000EHGet DigBrd CPU Appl Fmwr Remote Inventory 000FHGet DigBrd FPGA UDP/IP Core Fmwr Remote Inventory 0010HSet UDP/IP Core Lane Controller IP Address and Port Number Parameters 0011HGet UDP/IP Core Lane Controller IP Address and Port Number Parameters 0012HSet UDP/IP Core IP Address 0013HGet UDP/IP Core IP Address 0014HGet UDP/IP Core UDP Port Number 0015H
MPI 6000 Multi-Protocol Reader System Guide7-6System IdentifySystem Identify Data SizesSet Communications Baud RateSystem Identify Command Data Data PayloadSystem Identify Command 0000HSystem Identify Response Data Data PayloadSystem Identify Command 0000HVendor NameVersion IDPart NumberSerial NumberSystem Identify Data Data SizeVendor Name 15 BytesVersion ID 15 BytesPart Number 15 BytesSerial Number 15 BytesSet Communications Baud Rate Command Data Data PayloadSet Communications Baud Rate Command 0001HBaud Rate Data Code XXH
Configuration Commands and Responses7-7Baud Rate Data CodesGet Communications Baud RateSet Communications Baud Rate Response Data Data PayloadSet Communications Baud Rate Command 0001HBaud Rate Data Code19,200 bps 0CH38,400 bps (System Default) 0DH57,600 bps 0EH115,200 bps 0FHGet Communications Baud Rate Command Data Data PayloadGet Communications Baud Rate Command 0002HGet Communications Baud Rate Response Data Data PayloadGet Communications Baud Rate Command 0002HBaud Rate Data Code XXH
MPI 6000 Multi-Protocol Reader System Guide7-8Set Time and DateTime and Date Data RangesSet Time and Data Command Data Data PayloadSet Time and Date Command 0003HHours XXHMinutes XXHSeconds XXHHundredths of Seconds XXHMonth XXHDay XXHYe a r XXHSet Time and Data Response Data Data PayloadSet Time and Date Command 0003HTime and Date Data Data RangeHours 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 to 63H)Month 1 to 12 (01H to 0CH)Day 1 to 31 (01H to 1FH)Ye a r 0 to 99 (00H to 63H)
Configuration Commands and Responses7-9Get Time and DateFirmware DownloadGet Time and Data Command Data Data PayloadGet Time and Date Command 0004HGet Time and Data Response Data Data PayloadSet Time and Date Command 0004HHours XXHMinutes XXHSeconds XXHHundredths of Seconds XXHMonth XXHDay XXHYe a r XXHFirmware Download Command Data Data PayloadFirmware Download Command 0005HFirmware Download Response Data Data PayloadFirmware Download Command 0005H
MPI 6000 Multi-Protocol Reader System Guide7-10The Firmware Download command is implemented as defined for both UDP/IP Fast Ethernet and serial communications.Reset ReaderGet Stored Tag Response MessageReset Reader Command Data Data PayloadReset Reader Command 0006HReset Reader Control Word A5A5HReset Reader Response Data Data PayloadReset Reader Command 0006HGet Stored Tag Response Message Command Data Data PayloadGet Stored Tag Response Message Command 0007HStored Tag Response Message Number XXXXHGet Stored Tag Response Message Response Data Data PayloadGet Stored Tag Response Message Command 0007HStored Tag Response Message Number XXXXHStored Tag Response Message Data
Configuration Commands and Responses7-11Get Number of Stored Tag Response MessagesDelete All Stored Tag Response MessagesGet System Startup StatusGet Number of Stored Tag Response Messages Command Data Data PayloadGet Number of Stored Tag Response Messages Command 0008HGet Number of Stored Tag Response Messages Response Data Data PayloadGet Number of Stored Tag Response Messages Command 0008HNumber of Stored Tag Response Messages XXXXHDelete All Stored Tag Response Messages Command Data Data PayloadDelete All Stored Tag Response Messages Command 0009HDelete All Stored Tag Response Messages Control Word A5A5HDelete All Stored Tag Response Messages Response Data Data PayloadDelete All Stored Tag Response Messages Command 0009H
MPI 6000 Multi-Protocol Reader System Guide7-12Get Lane Controller Interface StatusGet System Startup Status Command Data Data PayloadGet System Startup Status Command 000AHGet System Startup Status Response Data Data PayloadGet System Startup Status Command 000AHSystem Startup Module Number (System Initialization) XXXXHSystem Timer Initialization Status Error Number XXXXHSystem BMU Initialization Status Error Number XXXXHSystem Queue Create Status Error Number XXXXHSystem Task Create Status Error Number XXXXHGet Lane Controller Interface Status Command Data Data PayloadGet Lane Controller Interface Status Command 000BHGet Lane Controller Interface Status Response Data Data PayloadGet Lane Controller Interface Status Command 000BHModule Number XXXXHError Number XXXXH
Configuration Commands and Responses7-13Get System Interface StatusGet DigBrd Hdwr Remote InventoryGet System Interface Status Command Data Data PayloadGet System Interface Status Command 000CHGet System Interface Status Response Data Data PayloadGet System Interface Status Command 000CHModule Number XXXXHError Number XXXXHGet Digital Board Hardware Remote Inventory Command Data Data PayloadGet Digital Board Hardware Remote Inventory Command 000DHGet Digital Board Hardware Remote Inventory Response Data Data PayloadGet Digital Board Hardware Remote Inventory Command 000DHVendor NameVersion IDPart NumberSerial Number
MPI 6000 Multi-Protocol Reader System Guide7-14Hardware Remote Inventory Data SizesGet DigBrd CPU Boot Fmwr Remote InventoryGet DigBrd CPU Appl Fmwr Remote InventoryHardware Remote Inventory Data Data SizeVendor Name 15 BytesVersion ID 15 BytesPart Number 15 BytesSerial Number 15 BytesGet Digital Board CPU Boot Firmware Remote Inventory Command DataData PayloadGet Digital Board CPU Boot Firmware Remote Inventory Command 000EHGet Digital Board CPU Boot Firmware Remote Inventory Response DataData PayloadGet Digital Board CPU Boot Firmware Remote Inventory Command 000EHVendor NameVersion IDPart NumberGet Digital Board CPU Application Firmware Remote Inventory Command DataData PayloadGet Digital Board CPU Application Firmware Remote Inventory Command000FH
Configuration Commands and Responses7-15Get DigBrd FPGA UDP/IP Core Fmwr Remote InventoryFirmware Remote Inventory Data SizesGet Digital Board CPU Application Firmware Remote Inventory Response DataData PayloadGet Digital Board CPU Application Firmware Remote Inventory Command000FHVendor NameVersion IDPart NumberGet Digital Board FPGA UDP/IP Core Firmware Remote Inventory Command DataData PayloadGet Digital Board FPGA UPD/IP Core Firmware Remote Inventory Command0010HGet Digital Board FPGA UDP/IP Core Firmware Remote Inventory Response DataData PayloadGet Digital Board FPGA UPD/IP Core Firmware Remote Inventory Command0010HVendor NameVersion IDPart Number
MPI 6000 Multi-Protocol Reader System Guide7-16Set UDP/IP Core Lane Controller ParametersGet UDP/IP Core Lane Controller ParametersFirmware Remote Inventory Data Data SizeVendor Name 15 BytesVersion ID 15 BytesPart Number 15 BytesSet UDP/IP Core Lane Controller Parameters Command Data Data PayloadSet UDP/IP Core Lane Controller Parameters Command 0011HIP Address (MSW) XXXXHIP Address (LSW) XXXXHPort Number XXXXHSet UDP/IP Core Lane Controller Parameters Response Data Data PayloadSet UDP/IP Core Lane Controller Parameters Command 0011HGet UDP/IP Core Lane Controller Parameters Command Data Data PayloadGet UDP/IP Core Lane Controller Parameters Command 0012H
Configuration Commands and Responses7-17Set UDP/IP Core IP AddressGet UDP/IP Core IP AddressGet UDP/IP Core Lane Controller Parameters Response Data Data PayloadGet UDP/IP Core Lane Controller Parameters Command 0012HIP Address (MSW) XXXXHIP Address (LSW) XXXXHPort Number XXXXHSet UDP/IP Core IP Address Command Data Data PayloadSet UDP/IP Core IP Address Command 0013HIP Address (MSW) XXXXHIP Address (LSW) XXXXHSet UDP/IP Core IP Address Response Data Data PayloadSet UDP/IP Core IP Address Command 0013HGet UDP/IP Core IP Address Command Data Data PayloadGet UDP/IP Core IP Address Command 0014H
MPI 6000 Multi-Protocol Reader System Guide7-18Get UDP/IP Core Port NumberGet UDP/IP Core Lane Controller Parameters Command Data Data PayloadGet UDP/IP Core IP Address Command 0014HIP Address (MSW) XXXXHIP Address (LSW) XXXXHGet UDP/IP Core Port Number Command Data Data PayloadGet UDP/IP Core Port Number Command 0015HGet UDP/IP Core Port Number Command Data Data PayloadGet UDP/IP Core Port Number Command 0015HPort Number XXXXH
8Tag Command Processing
8-3Chapter 8Tag Command ProcessingThis chapter provides definitions of and instructions for reading from and writing to a tag, as well as explanations of the tag command codes.Reader OperationThe 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 follow-ing sections.Write CommandsTo be provided.Read CommandsTo be providedHost Commands Required for Tag ProcessingTo be provided.
MPI 6000 Multi-Protocol Reader System Guide8-4
9System Diagnostics and Preventive Maintenance
9-3Chapter 9System Diagnostics and Preventive MaintenanceThis chapter provides information on the following subjects:Error MessagesTroubleshootingPreventive Maintenance ScheduleVisual InspectionMPI 6000 RepairRemoval and Replacement ProceduresTechnical SupportTroubleshooting Indications and ActionsTo be provided.
MPI 6000 Multi-Protocol Reader System Guide9-4
AAcronyms and Glossary
A-3Appendix AAcronyms and GlossaryAAC alternating currentACK 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.AVI automatic vehicle identificationBbackscatter portion of an RF signal that is modulated by a tag and radiated back to the readerbaud measure of number of bits per second of a digital signal; for example, 9600 baud = 9600 bits per secondbit The smallest unit of information, consisting of a 0 or 1, that is formed from a binary digitbyte binary character; for example, one 8-bit ASCII characterCcm centimeter(s)command data set that is recognized by the receiving device as intending to elicit a specific responseCRC cyclic redundancy checkCTRL controlCTS clear to sendDdata information that is processed by a computing device
MPI 6000 Multi-Protocol Reader System GuideA-4DC direct currentdB decibel(s)dBidecibel(s), referencing isotropic radiatorEECP error correcting protocoleGo Proprietary name for ANS INCITS 256-2001 and ISO 18000-6 compliant TransCore products. A registered trademark of TC IP, Ltd.eom end of messageEEPROM electrically erasable programmable read-only memoryESD electrostatic dischargeFFCC Federal Communications Commissionfield physical area/space in which a tag can be read by the reader; also, an element of a data record/frame, for example, division within a tag's data frameframe consecutive bits of data in memory that are read and written as a groupfrequency bands range of RF frequencies assigned for transmission by an RF deviceft foot or feetHhex hexadecimalhexadecimal base 16 numbering system that uses the characters 0 through 9 and A through F to rep-resent the digits 0 through 15host device, generally a computer, that is connected to reader system components through the communications portHz hertz
Acronyms and GlossaryA-5II/O input/outputIAG Inter-Agency Group, distributor of IAG tagsID identification; encoded information unique to a particular tagin inch(es)interface connection point for communications with another deviceIRQ interrupt requestJJP jumper pinKkkilo (103)kg kilogram(s)Llane controller device that is used to integrate all activity that occurs in a toll lane. lb pound(s)LED light-emitting diodeMmessage combination of fields, frames, and pages as required by the system to transmit or receive associated command and response data to and from the reader and host com-putermmeter(s)mA milliamp(s)Mega million (106)MB megabyte(s)MHz megahertz
MPI 6000 Multi-Protocol Reader System GuideA-6milli one-thousandth (10-3)mode method of operationMPI TransCore’s Multi-Protocol Readerms millisecondsmW milliwatt(s)NNEMA National Electrical Manufacturers AssociationOOSHA Occupational Safety and Health AdministrationPPC personal computerPLL phase-lock loopprotocol specified convention for the format of data messages communicated between devicesPWA printed wiring assemblyRRAM random access memoryread process of acquiring data from a device, for example, from a tag or from computer memoryreader controlled interrogating device capable of acquiring data from a device, for example, acquiring and interrupting data from a tagread zone physical area in which a tag can be read by the reader systemRF radio frequencyRFID radio frequency identificationRTS request to send
Acronyms and GlossaryA-7Sssecond(s)SeGo SeGo is a superset of the TransCore eGo protocol.SRAM static random access memorysom start of messagesystem 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.Ttag small, self-contained device acting as an identifying transponderTDM time-division multiplexing, used in this document to refer to the use of time-division multiplexing of multiple readers in proximity of each other.Title 21 state of California code of regulations, Chapter 16, Title 21, which is the standard used for AVI/DSRC (digital short-range communications) protocoltoll any application of the system equipment wherein the equipment is used to assist in the orderly collection of money in exchange for the passage of a vehicle through a partic-ular installation pointTrAC TransCore Action Centertransponder a tagUUART universal asynchronous receiver-transmitterUTA universal toll antennaVVvolt(s)VCC voltage controlled currentVer version (software)
MPI 6000 Multi-Protocol Reader System GuideA-8WWwatt(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.
BBlock Diagrams
B-3Appendix BBlock DiagramsThis appendix shows the block diagrams for the interface connections between the components as well as the individual MPI 6000 System components.MPI 6000 SystemFigure B-1 MPI 6000 Hardware Interconnection Block Diagram
MPI 6000 Multi-Protocol Reader System GuideB-4
CSystem Technical Specifications
C-3Appendix CSystem Technical SpecificationsThis appendix provides reference information for the MPI 6000 System components.Component SpecificationsThis appendix describes the engineering specifications for the MPI 6000 System com-ponents.MPI 6000 Multi-Protocol ReaderPower Supply Fault DetectionEach voltage supply has fault detection to determine if the voltage supply is function-ing correctly. Output tolerance is tested to ±5 percent. If any of the voltage supplies fail, the fault signal from the power supply to the digital board defaults to low. AA3152 Universal Toll AntennaThe AA3152 antenna specifications are as follows:•Operates in the location and monitoring service band (902 to 928 MHz).•Optimum radiation pattern — Virtually no side or back lobes help to confine antenna coverage to a single lane.•Weatherproof — Each antenna is housed in a radome made of materials with favorable electrical characteristics and resistance to ultraviolet radiation.•Bandpass filtering helps to attenuate interference from other RF sources.Environmental SpecificationsThe AA3152 UTAs can withstand the environmental tolerances shown in Table C-1.
MPI 6000 Multi-Protocol Reader System GuideC-4Table C-1 Antenna Environmental TolerancesEnvironment SpecificationDust NEMA pub 250-1991, Sec. 6.5, page 18Rain NEMA pub 250-1991, Sec. 6.4, page 17 and Sec. 6.7, page 19Corrosion resistanceNEMA pub 250-1991, Sec. 6.9, page 20Shock 5 G ½-sine pulse, 10 ms duration, 3 axesVibration 0.5 Grms 10-500 HzTemperature range -40°F to +167°F (-40°C to +75°C)Humidity 100% condensing
DHardware Interfaces
D-3Appendix DHardware InterfacesThis appendix describes the physical interconnections within an MPI 6000 System.Hardware InterfacesThis appendix describes the hardware interfaces in the MPI 6000 and to external com-ponents, such as antennas.Figure D-1 shows the basic hardware interconnections for the MPI 6000.Figure D-1 MPI 6000 Hardware Interconnection Block Diagram
MPI 6000 Multi-Protocol Reader System GuideD-4CommunicationsThe MPI 6000 communicates with a host via Ethernet or serial communicaitons.EthernetThe connector is an RJ-45 jack. This interface is 10-base T. Table D-1 lists the pin-outs.RS-232 ConnectorsTable D-1 Ethernet Connector Pin-outsPin Signal Description1TPTX+ Output Differential Transmit Data (+)2TPTX- Output Differential Transmit Data (-)3 TPRX+ Input Differential Receive Data (+)4Not connected N/A5Not connected N/A6TPRX- Input Differential Receive Data (-)7Not connected N/ANot connected N/ATable D-2 RS-232A Communications Connector ParametersPin Signal Description1RSD Received line signal detect (not connected)2RXD Receive Data3 TXD Transmit Data4DTR Data Terminal Ready (not connected)5GND Ground6DSR Data Set Ready (not connected)7RTS Request to Send8CTS Clear to Send9RI Ring indicator (not connected)
Hardware InterfacesD-5Table D-3 RS-232B/TDM Connector ParametersPin Signal Description1TXD Transmit Data2RXD Receive Data3 DTR Data Terminal Ready (not connected)4RTS Request to Send5CTS Clear to Send6GND Ground7TDM + TDM positive signal8TDM - TDM negative signalTable D-4 RS-232 Diagnostics Connector ParametersPin Signal Description15V PWR 5V power supply for I/O board2GND GND3 I/O Signal 14I/O Signal 25I/O Signal 36I/O Signal 47Tag in Field 1 Contact Closure 1 for Tag in Field Signal8Tag in Field 2 Contact Closure 2 for Tag in Field Signal
MPI 6000 Multi-Protocol Reader System GuideD-6Hardware Diagnostic Port Table D-5 MPI 6000 Hardware Diagnostic Port Parameters Pin Signal Source Description1 I RF I Channel from RF receiver2 Q RF Q Channel from RF receiver3RSSI RF RSSI Detector Output, high for I low for Q.4RANGE_ADJ_CNTL RF Range Adjust_Control Signal5+3.3V Digital +3.3V 6Spare RF7GND Ground8Spare RF9Spare RF10 IAG_New_Sig_Det RF IAG New Signal Detection Line11 IAG RF IAG Channel from RF receiver12 GND Ground13 Config Type 0 Digital Configuration Selection bit 114 Config Type 1 Digital Configuration Selection bit 215 Config Type 2 Digital Configuration Selection bit 316 Config Type 3 Digital Configuration Selection bit 417 Tag Ty p e A ck RF Acks the tag type inputs and indicates that the DL & DOM DACS are settled.18 Ready to Tx RF Ready to Transmit19 Config Load Digital Signal to RF to load new config.20 MOD Digital RF Modulation Signal21 RF ON/OFF Digital RF On Off Control22 UL/DL Cntrl Digital Controls whether active source is Uplink or Downlink23 TDM Digital TDM Sync Pulse24 GPS 1pps Digital 1 pulse per second signal for Frequency stabilization25 Error (txcvr fault) RF RF Error Indicator active low26 Power Supply Fault Digital Fault Signal from the Power Supply Board
Hardware InterfacesD-7Antenna Multiplexer ConnectorsThe antenna multiplexer is used to drive multiple antennas in multiple AVI lanes.Connector D21 is the same as connector B11 on the digital board. Connector D28 is the same as connector B11 on the digital board. This connector is used to connect the data cables from the MPI 6000 to the antenna multiplexer and the RF System Test boards.RF System Test ConnectorsThe RF system test checks the ... 27 GND Ground28 Tx Serial Comm Digital Transmit Serial Signal29 Rx Serial Comm RF Receive Serial Signal30 GoodTagRead Digital Active High Pulse from FPGA1 31 CRC Failed Digital Active High Pulse from FPGA132 ActivatePort Digital Enable the Test Port Buffer when the Connector plugged in33 GND Ground34 SW1 Digital GPIO from MPC85235 SW2 Digital GPIO from MPC85236 SW3 Digital GPIO from MPC85237 SW4 Digital GPIO from MPC85238 DecoderOutput Digital Decoder Bit Stream from FPGA139 PLL Clock (decoder) Digital PLL Clock from FPGA140 GND Digital GroundTable D-5 MPI 6000 Hardware Diagnostic Port Parameters (continued)Table D-6 Antenna Multiplexer Connector Pin-outsConnector Designator Pin Signal DescriptionD16 RF input1 1RF Input/Output RF input/output signalD17 RF output 1 1RF Input/Output RF input/output signalD18 RF output 2 1RF Input/Output RF input/output signalD19 RF output 3 1RF Input/Output RF input/output signalD20 RF output 4 1RF Input/Output RF input/output signal
MPI 6000 Multi-Protocol Reader System GuideD-8•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 MPI 6000 to the antenna multiplexer board and the RF system test boards.•Connector E23 is the RF in signal.Table D-7 RF System Test Connector Pin-outPin Signal Description1RF Input/Output RF input output signal

Navigation menu