TransCore MPI6000A User Manual

MPI 6000 Multi-Protocol

PRELIMINARY

Reader System Guide

TransCore

8600 Jefferson Street NE

Albuquerque, New Mexico 87113

P/N 411880

PRELIMINARY

©

PRELIMINARY

2005 TC IP, Ltd. All rights reserved. TRANSCORE, AMTECH, and EGO are registered trademarks of

TC IP, Ltd, and are used under license. All other trademarks listed are the property of their respective

owners. Contents are subject to change. Printed in the U.S.A.

For further information, contact:

Tr

ansCore
8600 Jefferson Street NE
Albuquerque, New Mexico 87113 USA

Phone: [phone]
Fax: [phone]

.

WARNING TO USERS IN THE UNITED STATES

PRELIMINARY

FEDERAL COMMUNICATIONS COMMISSION (FCC)

LOCATION AND MONITORING SERVICE STATEMENT

47 CFR §90.351

NOTE: The user is required to obtain a Part 90 site license from the FCC to operate this radio frequency

identification (RFID) device in the United States and Canada. FCC ID number is FIHMPI6000A. IC ID
number is 1584A-MPI6000A. Access the FCC Web site at www.fcc.gov/Forms/Form601/601.html or at

wireless.fcc.gov/index.htm?job=online_filing to obtain additional information concerning licensing

requirements.

NOTE:

requirements.

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 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 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 regulations in effect, the user
may be required to correct the interference at their own expense.

CAUTION: This equipment may not be modified, altered, or changed in any way without permission

from TransCore, LP. Unauthorized modification may void the equipment authorization from the FCC and
will void the TransCore warranty.

Users in all countries should check with the appropriate local authorities for licensing

FCC RADIO FREQUENCY INTERFERENCE STATEMENT

47 CFR §15.105(a)

NO UNAUTHORIZED MODIFICATIONS

47 CFR §15.21

USE OF SHIELDED CABLES IS REQUIRED

47 CFR §15.27(a)

NOTE: Shielded cables and earth grounding the unit is recommended for this equipment to comply with

FCC regulations.

TransCore, LP

USA

Health Limits for Encompass® Multiprotocol Reader

PRELIMINARY

Using External Antenna (902 to 921.5 MHz)

Within the United States, environmental guidelines regulating safe exposure levels are issued by the Occu­pational Safety and Health Administration (OSHA).

Section 1910.97 of OSHA Safety and Health Standards 2206 legislates a maximum safe exposure limit of
10 milliwatts per square centimeter (mW/cm

Although not binding, other organizations such as the American National Standards Institute (ANSI) have
issued similar guidelines that are more restrictive than the OSHA limits (ANSI C95.1). ANSI guidelines
recommend a maximum safe power density in mW/cm

2

) averaged over 6 minutes at 902 MHz.

2

of:

Frequency

1500

Thus, the maximum permissible exposure for general population/uncontrolled exposure at 902 MHz is

0.60 mW/cm

The maximum permissible exposure for occupational/controlled exposures is 3.0 mW/cm2. The average
time is six minutes.

The RF power density generated by the Encompass Multiprotocol Reader was calculated using a maxi­mum antenna gain of 14.0 dBi, equivalent to the antenna gain of the external AA3152 Universal Toll
Antenna (UTA).

Warning

At 2 W transmitted power, 0 dB transmit attenuation, and a distance of 33 inches (82 cm) from the
antenna, the maximum power density calculated was less than 0.60 mW/cm
33 inches (82 cm) from the general public. Maintenance personnel must remain at least 15 inches
(37 cm) from the antenna when the system is operating.

The data confirms that when the UTA, or equivalent antenna, is used with the TransCore Encompass
Multiprotocol Reader, the antenna effectively meets OSHA requirements and thus does not represent an
operating hazard to either the general public or maintenance personnel.

2

. The average time is thirty minutes.

(in MHz)

2

. Install the antenna at least



Contents

PRELIMINARY

PRELIMINARY

Health Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

PRELIMINARY

RF Levels From TransCore Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

1 Before You Begin

Purpose of the Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Guide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Typographical Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . 1-4

Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

U.S. and Canada Licensing . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

2 Developing the Installation Site Plan

Contents

3 Installing and Configuring the MPI 6000

Overview of the MPI 6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Connecting the MPI 6000 for Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

External Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Installing and Using the MPI 6000 Host Software . . . . . . . . . . . . . . . . . . . . . . . 3-6

Installing the Host Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Connecting to the MPI 6000 Reader with the Host Software . . . . . . . . . . . . 3-7

Configuring the MPI 6000 Reader Operating Frequency . . . . . . . . . . . . . . . 3-7

Operating the MPI 6000 Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

4 Lane Tuning Guidelines

Why You Need to Tune a Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Lane Tuning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

ix

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Traffic Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Tag Transaction or Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Capture Zone or Lane Footprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

RF Factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Downlink and Uplink Transmitted RF Power . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Range Control Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Frequency Considerations — Single Protocol . . . . . . . . . . . . . . . . . . . . . . . 4-7

Frequency Considerations — Multiple Protocols . . . . . . . . . . . . . . . . . . . . . 4-8

Antenna-Tag Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Antenna Uptilt Angle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Antenna Positioning Within the Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Signal Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

5 Optimizing MPI 6000 Reader System Performance

Cross-Lane Interference in RFID Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

What Is Cross-Lane Interference? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Determining Acceptable Lane Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Identifying Cross-Lane Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Diagnosing Cross-Lane Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Remedying Cross-Lane Interference

Frequency Separatio

RF Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Time-Division Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Physical Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

6 General Software Information

General Software Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Plan and Organize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Communications Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Communications RS–232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Diagnostic RS–232 Serial Communications . . . . .

Reader Command Protocol

UDP/IP Fast Ethernet Communications Protocol . . . . . . . . . . . . . . . . . . . . . . . 6-7

Command Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Data Acknowledge Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Command Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Asynchronous Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Software Flow Control Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Unsolicited Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Serial Communications Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Command Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

. . . . . . . . . . . . . . . . . . . . . . 6-5

x

Data Acknowledge Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

PRELIMINARY

Command Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Asynchronous Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Software Flow Control Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Unsolicited Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

7 Configuration Commands and Responses

Configuring the MPI 6000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Required Commands to Set Up MPI 6000 Reader. . . . . . . . . . . . . . . . . . . . 7-3

System Interface Command Group Commands . . . . . . . . . . . . . . . . . . . . . . . . 7-5

System Identify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Set Communications Baud Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Get Communications Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Set Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Get Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Firmware Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Reset Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Get Stored Tag Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Get Number of Stored Tag Response Messages. . . . . . . . . . . . . . . . . . . . 7-11

Delete All Stored Tag Response Messages . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Get System Startup Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Get Lane Controller Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Get System Interface Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Get DigBrd Hdwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Get DigBrd CPU Boot Fmwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . 7-14

Get DigBrd CPU Appl Fmwr Remote Inventory . . . . . . . . . . . . . . . . . . . . . 7-14

Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory . . . . . . . . . . . . . 7-15

Get UDP/IP Core Lane Controller Parameters . . . . . . . . . . . . . . . . . . . . . . 7-16

Set UDP/IP Core IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Get UDP/IP Core IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Get UDP/IP Core Port Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Contents

8 Tag Command Processing

Reader Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Write Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Read Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Host Commands Required for Tag Processing. . . . . . . . . . . . . . . . . . . . . . . . . 8-3

9 System Diagnostics and Preventive Maintenance

Troubleshooting Indications and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

xi

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

A Acronyms and Glossary

B Block Diagrams

MPI 6000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

C System Technical Specifications

Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

MPI 6000 Multi-Protocol Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Power Supply Fault Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

AA3152 Universal Toll Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

D Hardware Interfaces

Hardware Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

RS-232 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Hardware Diagnostic Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6

Antenna Multiplexer Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

RF System Test Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

xii

1

PRELIMINARY

Before You Begin

PRELIMINARY

This chapter provides an overview of the MPI 6000 Multi-Protocol Reader

PRELIMINARY

System Guide.

Purpose of the Guide

This 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
interface information.

Intended Audience

The intended audience for this guide is those personnel responsible for operating the
MPI 6000 Multi-Protocol Reader.

Guide Topics

Chapter 1

Before You Begin

and hardware

The MPI 6000 Multi-Protocol System Guide presents the following information.

Chapter 1 - Before You Begin In process

Chapter 2 - Theory of Operation In process

Chapter 3 - System Components In process

Chapter 4 - MPI 6000 System Operation In process

Chapter 5 - Diagnostics Information In process

Appendix A - Acronyms and Glossary In process

Appendix B - Block Diagrams In process

Appendix C - System Technical
Specifications

Appendix D - Hardware Interfaces In process

Appendix E - Reader Defaults In process

Index In process

In

process

1-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Related Documentation

See the following related document:

MPI 6000 Reader Quick Reference Guide (i

n process)

Typographical Conventions Used in this Manual

The following conventions are used in this manual. Not all of the conventions are used
in this version.

Table 1-1 Typographical Conventions

Convention Indication

This procedure might cause harm to the equipment and/or the user.

A caution sign indicates concerns about a procedure.

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 poin
word Note is bold.

Cancel button Bold text identi

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

5 Return A space indicates that you should press the specified keys in the sequence listed,

not at the same t

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

cursor The cursor

ts require the user’s attention. The paragraph is in italics and the

fies the labeling of items as they actually appear on the keyboard,

Esc keys at the same time.

ime.

that you should press and release the left mouse button.

is the flashing vertical line that appears in a selected edit box.

1-4

Licensing Requirements

PRELIMINARY

1-5

To operate a radio frequency (RF) system in a given country, the user first must obtain
permission from the regulatory agency that controls radio operations in that country.
Most countries require type and safety approval, as well as licensing for RF transmit­ters. Users in all countries should check with the appropriate local authorities for
licensing requirements.

Licensing: United States and Canada

This MPI6000 Reader requires a Federal Communications Commission (FCC) Part
90 license to operate in the United States, or an Industry Canada (IC) license to oper-

ate in Canada. The authorized continuous wave frequency bands are 902.25 to

MHz and 910.00 to 921.50 MHz.

The modulated frequency bands are shown in Table 1-2 . For the Emission Designator,
see the FCC or IC grant.

Operational Mode Frequency Range

eGo and SeGo 911.75-919.75 MHz

903.75

18000-6C

Low and High Data Rates

Allegro and T21 912.75-918.75 MHz

IAG and CVISN 914.75-916.75 MHz

Table 1-2 Modulated Frequency Bands

The user is responsible for filing the FCC or IC license according to FCC and IC reg­ulations. You can obtain the needed FCC forms and instruc
cation by accessing the FCC Web site at www.fcc.gov/Forms.

Note: The FCC ID is FIHMPI6000A. The IC ID is 1584A-MPI6000A.
Models: E5, E6.

An FCC or IC license provides the user with the legal authorization to operate
radio frequency identification (RFID) systems on the licensed frequencies
specified in the license. Only an authorized installer or service technician can set the
frequency for the reader to that specified in

The FCC or IC
maintain the system should any other RFID be used in the licensed area after the
reader is ins

license also provides the user with protection and authorization to

talled.

912.75-918.75 MHz

tions for your license appli-

the

at the site

the FCC or IC site license.

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

1-6

2

PRELIMINARY

Developing the Installation Site Plan

PRELIMINARY

Developing the Installation Site Plan

PRELIMINARY

This chapter will provide guidelines for the following tasks:

Assessing the Site and Formulating a Frequency Plan

Site Layout and Traffic Flow

Electrical and Communications Requirements

MPI 6000 and Tag Model Interoperability

Reading of Mixed Population Tags

Antenna Selection

Antenna and Tag Alignment

Polarization

Site Preparation Checklist

Chapter 2

Components Checklist

Task Checklist

2-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

2-4

3

PRELIMINARY

Installing and Configuring the MPI 6000

PRELIMINARY

Installing and Configuring the MPI 6000

PRELIMINARY

This 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 6000

TransCore’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

The MPI 6000 can be integrated into an onsite lane controller or a NEMA enclosure.
The MPI 6000 transmits

The MPI 6000 is capable of supporting any of the following protocols in a given
inst

allation:

• American Trucking Association (ATA), full-frame and half-frame (read-only)

single assembly.

Chapter 3

and receives signals through a single antenna.

• 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-

supporting any two of the above protocols.

ble of

The MPI 6000 is also suitable for a wide variety of automatic vehicle identification
transportation applications, including electronic tolling, open
vehicle registration, parking, and rail applications.

The following sections describe the specifications for the external connections from

MPI 6000 housing.

the

Connecting the MPI 6000 for Operation

External Connectors

This section lists the MPI 6000 external connections. Figure 3-1 shows the MPI 6000
connector locations.

road tolling, electronic

1.*eGo tags are fully compliant with ANSI INCITS 256:2001 and ISO 18000-6 standards. SeGo is a superset of the eGo
protocol.

3-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Figure 3-1 Connector Locations on MPI 6000 Enclosure

Power

The MPI 6000 requires 19V DC to 28V DC or 19V AC to 27V AC RMS voltage
source. Table 3-

Table 3-1 MPI 6000 Power Connection Specifications

Connector Type

Wire Gauge

RF Antenna Connector

The MPI 6000 Reader typically is co
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.

1 lists the MPI 6000 external power connector specifications.

Two-Pin Terminal Block

12 – 30 AWG

19V to 28V DC or 19V to 27V AC RMS

Volt ag e

Polarity

Current

Note I

Either, power supply is polarity independent

2 amps

f AC is used do not ground one end of the AC

input, the AC s

nnected t

upply must float.

o an AA3152 Universal Toll Ante

nna

3-4

Antenna Connector

PRELIMINARY

Installing and Configuring the MPI 6000

Figure 3-2 Antenna Connector Location

Table 3-2 lists the RF antenna connector parameters.

Table 3-2 RF Antenna Connector Specifications

Connector Type

Output Power

RF Antenna Multiplexing/RF System Test Connector

This connector is used when a single MPI 6000 is used to operate multiple

Ethernet Connector

The MPI 6000 communicates with a host via an Ethernet communications protocol.
This connection requires an RJ
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 Connector

The MPI 6000 communicates via a serial, RS
3-3). The diagnostic RS
sequence.

SMA Female

Up to 2 watts

lanes.

–45 connector. If you use a switch between the MPI

–232, communications protocol (Table

–232 port can be used to display the operating system boot

Table 3-3 RS-232 Connector Specifications

Connector Type

Protocol

9 pin D-sub male

RS-232

3-5

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Table 3-3 RS-232 Connector Specifications (continued)

Baud

Bits

Parity

Stop Bits

Flow Control

Note: If you connect the MPI 6000 directly to a PC’
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 her

RS-232B/TDM Connector

Information to be provided.

RS-232 Diagnostic Test Port Connector

Information to be provided.

External Digital Input/Output Connector

9600

8

None

1

None

s serial port, you must use a null-

e?)

Information to be provided.

Global Positioning System Connector

Information to be provided.

Installing and Using the MPI 6000 Host Software

This 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 Software

The MPI 6000 host program is used to communicate with the MPI 6000 and also dis­play tag reads.

To install the MPI 6000 Host software

1. Load (what media is u

computer.

sed? CD? FTP site?) the host software onto the

host

3-6

Installing and Configuring the MPI 6000

PRELIMINARY

2. Run setup.exe and follow the commands to install the Host. The setup

installs an icon named MPI 6000 Host on your computer desktop.

The following sections tell you how to use the MPI 6000 Host software.

procedure

Connecting to the MPI 6000 Reader with the Host Software

1. Double-click on the MPI 6000 Host icon.

2. Select UDP on the main screen.

3. In the UDP Command Link Config field, enter

Write the IP address near
future reference.

4. Select Establish Command

5. Select E.xit.

the Ethernet connector on the

Link.

the IP address of the reader.

MPI 6000 enclosure for

Configuring the MPI 6000 Reader Operating Frequency

1. Select the Configuration tab.

2. Select the Transceiver Configuration sub-ta

3. Set the frequencies to desire values. Nominal values are 918.75 for do
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.

b.

wnlink and

Operating the MPI 6000 Reader

1. Select Tags > FDOT.

2. Enter hex data into the IT2200 Write Data and SeGo Page Data fields. Us

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 Se

parameters for both IT2200 and SeGo tags.

4. Press St

5. Tag

6. To st

7. Press Sto

8. Press Exit to

MPI 60
such as attenuation, step-lock settings, and
reader powers up.

art to begin tag processing.

responses should appear in the IT2200 and SeGo fields.

op the display or the response count, select the check boxes.

p to end tag processing.

close the FDOT page.

00 Readers have been preconfigured for most needed operations. Parameters

quence Field. This sets the Read or Write

tag command sequences are set when the

e 32

3-7

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

3-8

4

PRELIMINARY

Lane Tuning Guidelines

PRELIMINARY

This chapter explains the importance of lane tuning for optimum

PRELIMINARY

automatic vehicle identification (A VI) syste m performance and describes
the MPI 6000 functions and features that can assist you in tuning an AVI
lane.

Why You Need to Tune a Lane

Lane tuning is the procedure by which an installer can optimize the radio frequency
(RF) characteristics and the signal timing of an AVI-equipped toll lane for the perfor­mance dictated by the lane’s traffic requirements. Typically,
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 ty
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.
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.

Furthermore, the type of technologies involved, either IT2200,

Chapter 4

Lane Tuning Guidelines

consideration of these

pe, the geometry of fixed objects near the capture

Required Equipment

You will need the following equipment and tools when you tune a lane:

TBD

Lane Tuning Parameters

Lane tuning parameters can be altered to effect required outcomes. This section lists
the properties that can be used to tune a lane.

Traffic Requirements

The traffic requirements of lane tuning include the following characteristics:

• The duration of the tag transaction, also known as handshake

4-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

• 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 lane

Traffic requirements are further defined by two terms, tag transaction or handshake
and capture zone

Tag Transaction or Handshake

A 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 ma
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
of commands
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.

a write command followed by a GENACK, or some other complex sequence

or lane footprint.

. Each part of the handshake requires time, and the transaction with the

ny cases the

Capture Zone or Lane Footprint

The 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 me
ments of the capture zones of at least five diversely different vehicles equipped with
properly mounted
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.

tags. Ideally, RF margin plots taken at the time the footprint are

asure-

4-4

To Be Provid e d.

PRELIMINARY

Lane Tuning Guidelines

Figure 4-1 Field Size, Shape, and Antenna Polarization Define the Reading

Range

One concern for lane tuning is how large the footprint needs to be for acceptable 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
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 wo
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 milliseconds

5 GENACK @ 0.8 milliseconds per GENACK=

For another example, if the toll agency requires three pages to be read from
followed by three pages of data to be written to the tag, followed by five GENACKS,
the total transaction time is

as the vehicle passes through the

uld be four

4 milliseconds

= 8 milliseconds total, each full

handshake

the tag,

4-5

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

3 reads @ 4 milliseconds each = 12 milliseconds

3 writes @ 4 milliseconds each = 12 milliseconds

GENACKs @ 0.8 milliseconds each=

5

4 milliseconds

= 28 milliseconds total, each full hand-

shake

To complete 4 full handshakes (simply a rule of thumb), the vehicle would need
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
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 i
the transaction.

Note: Please consult with
types of transactions.

Given the uncertainties of any RF link due to reasons already discussed in
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
speed and the size of the footprint.

Once the length of the footprint has been determined, the presence of
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
antennas. A lower gain antenna may be used to increase the side coverage.

Trans

Core to assess the impact of the more sophisticated

minimum period of time relative to the maximum vehicle

mpact the overall statistical reliability of

be mounted higher or

using more sophisticated

light curtains or

in line with other

to be

this section,

RF Factors

The 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)

4-6

Lane Tuning Guidelines

PRELIMINARY

• The downlink and uplink source frequencies and interference from lanes sharing

same or close frequencies

• The antenna-tag orientation

RF power is the most important RF factor in lane tuning. Thirty dBm translates to one­watt nominal power. Increasing
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.

the RF power will, in general, increase the footprint.

Because the RF power can create interference in adjacent or nearby lanes
the performance of the adjacent lane, the RF power should be adjusted so that mini­mum power is used to achieve the desired results.

and degrade

Downlink and Uplink Transmitted RF Power

Downlink 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
lated to such aspects as antenna angle, antenna placement, and tag placement, so use
this information as a starting point and consider other aspect
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
independent of the other tag protocol.

power on the footprint by protocol. Some of these factors are interre-

s of lane tuning when

in use,

Range Control Adjustments

Adjusting 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
to fine tune the first read position.

be used

in a single protocol situation

Frequency Considerations — Single Protocol

TBD

IT2200 or Title 21 Tag Protocol

TBD

This uplink frequency separation should repeat for additional lanes.

eGo Tag Protocol

TBD

4-7

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

ATA Tag Protocol

TBD

IAG Tag Protocol

TBD

Frequency Considerations — Multiple Protocols

TBD

Antenna-Tag Orientation

Antennas need to be oriented to match the tag orientation (Figure 4-2). Antennas also
need to match the tag placement and vice versa. For example, if the tag is placed in the
center of the windshield, the antennas should be
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 ad
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.

placed overhead, centered, or nearly

ditional costs for altering

the lane design, especially

Figure 4-2 Tag Orientation with Linearly Polarized Antenna

4-8

Lane Tuning Guidelines

PRELIMINARY

Figure 4-3 Upper Center Interior Windshield Tag Placement

Figure 4-4 Correct Exterior Tag Placement

Antenna Uptilt Angle

Adjusting the antenna uptilt angle directly affects the footprint and the point of first
tag read (Figure 4-5). As expected, a greater uptilt angle will move the point of first
tag read farther from the antenna. However, at some uptilt angle, a point of diminish­ing return is reached where the RF power is
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
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-

too dispersed to activate the tag at the

start of the capture

4-9

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

ing license plate tags.

Note: Tr ansCore does not recommend placing the antenna uptilt angles at less than five degrees.

Figure 4-5 Overhead Antenna Tilt Angle

Antenna Positioning Within the Lane

In lanes where the antennas are mounted side by side, TransCore recommends that you install the
transmit antenna toward the driver side of the traffic lane and the receive antenna toward the pas­senger side of the traffic lane. Antenna position in the lane also impacts lane performance.
Antenna
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 co

The portion of the footprint with the highest RF margin has the highest probability of a successful
tag transaction.
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
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

mounting brackets should be designed so that you can adjust the antennas from front to

verage to one side or the other.

This portion of the footprint is the area directly under the antenna and extending

low antenna angle. Next, adjust the antenna position so that the first read occurs at the

4-10

Lane Tuning Guidelines

PRELIMINARY

enable you to operate the lane at a lower RF power, which is usually the
ational mode.

Signal Timing

TBD

preferred oper-

4-11

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

4-12

Lane Tuning Guidelines

PRELIMINARY

4-13

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

4-14

5

PRELIMINARY

Optimizing MPI 6000 Reader System

Performance

PRELIMINARY

Optimizing MPI 6000 Reader System

PRELIMINARY

This chapter provides information to optimize the MPI 6000 performance
and reduce cross-lane interference.

Cross-Lane Interference in RFID Systems

Radio 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

of interference that can result from the operation of the reader system is called

type
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.

Chapter 5

Performance

Determining Acceptable Lane Performance

The 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,
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
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.

a test vehicle’s speed is limited by the amount of the toll lane that can be used

mph (32 kph), the vehicle uses 34 milliseconds to travel

5-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Identifying Cross-Lane Interference

Cross-lane interference is identified by an area in the RF read zone, or footprint,
which has areas where a tag cannot be read. If a toll lane has been operating satisfacto­rily and then begins to show a degradation in system performanc
ing number of missed reads or a spotty read pattern, there is a probability that cross­lane interference is occurring.

e, that is, an increas-

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 ca
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, transmissi
cross-lane interference.

ons out of a lane can create areas of possible

ses a

Figure 5-1 RF Footprint Extends Beyond Lane Boundaries

5-4

Optimizing MPI 6000 Reader System Performance

PRELIMINARY

Diagnosing Cross-Lane Interference

To diagnose this type of interference, first set the RF power in all lanes to a moderate
setting of 6 to 9 decibels (dB) for both downlink and uplink antennas. Next, tune a 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.

each adjacent lane tuning causes the previously tuned lane to

If
poorly (i.e.,

spotty read zone or areas of no reads), cross-lane interference is indicated.

start performing

Remedying Cross-Lane Interference

Several 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
site may not be appropriate at another site, so iterative methods of correcting this
interference are necessary.

one

Frequency Separation

Review 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 sa
link frequency, which is generally set to 918.75 MHz. Uplink frequencies should
alternate between 903.00 MHz and 91
four-lane plaza would have the frequencies shown in Tab le 5- 1.

Table 5-1 Frequency Plan for Four-Lane Toll Plaza Using IT2200-series or Title

21 Tag Protocol

Lane Downlink Frequency Uplink Frequency

1 918.75 MHz 903.00 MHz

2 918.75 MHz 910.00 MHz

3 918.75 MHz 903.00 MHz

4 918.75 MHz 910.00 MHz

0.00 MHz in adjacent lanes. For example, a

me down-

RF Power

A 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.

5-5

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Time-Division Multiplexing

In situations where cross-lane interference can occur in an installation, and frequency
management is not sufficient to solve the problem, you may need to use time-division
multiplexing (TDM). By using the TDM function in readers, individual readers oper­ate only during interleaved time periods.

The TDM interconnect is provided via a differential RS
nector that is located on the reader card’s expansion board
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
time eliminates interference

Although you need to configure the readers to
nection for
tion by connecting
in Figure 5-2. No other equipment is necessary for the interconnection circuit. You
need

to follow the polarity conventions as shown becau

dependent.

. Allowing each reader or group of readers to operate at an allotted

from readers in adjacent lanes.

operate using TDM, the interface con-

TDM can be provided to all the readers in a plaza before or during installa-

a pair of wires to the DB9 TDM connector of each reader as shown

–485 interface to a DB9 con-

connector in slot 2. This

se this interface is polarity

Figure 5-2 TDM Configuration Example

TransCore 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.

5-6

Optimizing MPI 6000 Reader System Performance

PRELIMINARY

Because the TDM signals are based on RS
the TDM bus by using RS
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.

Table 5-2 TDM Connector

Pin Name In/Out Description Recommended Connection

1 N/C N/A No connection N/C

2 N/C N/A No connection N/C

3 N/C N/A No connection N/C

4 N/C N/A No connection N/C

5 N/C N/A No connection N/C

6 N/C N/A No connection N/C

7 TDM (+) In/Out TDM synchronization positive Connect all red pin 7 wires

8 TDM (-) In/O

ut TDM synchronization negative Connect all black pin 8 wires

–485 repeaters or by using fiber with converters. Either of

–485 signals, you can extend the length of

together.

together.

9 N/C N/A No connection N/

implement TDM, you must configure only one reader in the group as a mas

To
reader for the TDM function. This reader will have a slightly shorter synchronization
period than the rest of the readers connected to it.

Note: T
the TDM delay and TD

Figure 5-3 illustrates a typical plaza configura
slots with three uplink frequencies. All the readers are configured with a
quency of 916 MHz.

he TDM synchronization period is set in 1.0-millisecond increments, whereas

M duration are set in 0.5-millisecond increments.

tion using TDM. There are three

C

ter

time

downlink fre-

5-7

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Figure 5-3 Typical Plaza Configuration Using TDM

The frequency settings and the 9-millisecond TDM time slots were determined based
on a Title 21 tag transaction. For other installations, the frequencies and TDM 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. Tab l e 5- 3 lists the settings for each reader in each time slot.

Figure 5-4 TDM Timing Diagram

5-8

Table 5-3 TDM Timing Settings

PRELIMINARY

Optimizing MPI 6000 Reader System Performance

Time Slot TDM Delay TDM Duration

T1 0 ms (setting = 0) 9 ms (setting = 18) 31 ms (setting = 31)

T2 10 ms (setting = 20) 9 ms (setting = 18) 32 ms (setting = 32)

T3 20 ms (setting = 40) 9 ms (setting = 18) 33 ms (setting = 33)

a. Master reader TDM synchronization period equals 30 milliseconds.

Note: The TDM synchronization period is set in 1.0-millisecond increments, and the
TDM delay and TDM duration are set in 0.5-millisecond i

The TDM example shown in Figure 5-4 and Tab l e 5 -3 was designed with three time
slots; however, two time slots can be used instead depending on the number of
frequen
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
the time slots to ensure that the re
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

cy channels and the timing. Implementing TDM with three time slots reduces

millisecond be used between each of

aders in the previous time slot have sufficient time to

a duration 1 millisecond longer than the actual duration.

TDM Synchronization

Period

ncrements.

a

All the readers designated as slave readers in the plaza on the same TDM bus are

ndent on the synchronization signal from the master reader. In the event that the

depe
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 sig
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
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

nal break may occur is u

nknown,

used for the

5-9

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

TDM bus in the event of either a TDM connection failure, or a failure of the TDM cir­cuit in the master
TDM failure messages in any

Physical Remedies

By adjusting the angle or position of the downlink and uplink antennas, you may be
able to minimize cross-lane interference.

Warning

Switch off RF power before working on antennas.

Adjusting the Antenna’s Uptilt Angle

Lowering an antenna’s uptilt angle between the antenna cover and th
ally reduces the interference (Figure 5-5).

reader, which also reduces the number of readers that will generate

one of these failure scenarios.

e horizon gener-

Figure 5-5 Antenna Tilt Angle Adjustment

5-10

Optimizing MPI 6000 Reader System Performance

PRELIMINARY

Adjusting the Antenna Side Angle

In the eGo 4110A Reader System, you can adjust an antenna’s side angle
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.

so that the

Figure 5-6 Downlink Antenna Side Angle Adjustment

Adjusting the Antenna Placement

Besides adjusting the antenna angles, you can also move the antenna farther back into
its overhead location so
action area. By shortening the read zone, you may be able to reduce the required RF
output power, which will result in reduced

You can also move the antenna pair from side to side
is used in lanes wher
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 Modifications

In rare instances, applying radar-absorbing foam to fixed areas of the toll plaza (e.g.,
metal roof) may reduce the

that the read zone does not extend as far in front of the trans-

probability of cross-lane interference.

within the lane. This adjustment

e the traffic travels closer to one side than another. For example,

.

incidence of interference.

5-11

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

5-12

6

PRELIMINARY

General Software Information

PRELIMINARY

General Software Information

PRELIMINARY

This 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 Information

All tag programmer commands are preceded by a start-of-message (<som>) amper­sand character (&) followed by an end-of-message (<eom>) percent character (%).
data after the <eom> character is ignored until the next <som> is detected.

Chapter 6

All

Any & character that occurs in the message betwee

verted to the backslash and at character (\@) sequence. Any % character

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 Organize

Tags 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 Protocols

The MPI 6000 communicates with a host by Ethernet or serial communications proto­cols.

n the <som> and <

eom> is con-

is converted

Ethernet

The MPI 6000 can communicate via an Ethernet communications protocol. This con­nection requires an RJ
tor is an RJ-45 jack and uses a 10-base T interface. If you use a switch between
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

–45 connector for the Ethernet receptacle. The Ethernet connec-

the

6-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

host PC is set to Dynamic TransCore recommends that you se

Table 6-1 lists the connector pin assignments.

Table 6-1 Ethernet Connector

Pin Signal Description

1 TPTX+ Output Differential Transmit Data +

2 TPTX- Output Differential Transmit Data -

3 TPRX+ Input Diff

4 NOT CONNECTED N/A

5 NOT CONNECTED N/A

6 TPRX- Input Differential Receive Data -

7 NOT CONNECTED N/A

8 NOT CONNECTED N/A

erential Rece

ive Data +

Communications RS–232

The connector is an industry standard DB-9M plug. Table 6-2 lists this connector pin
assignments.

t the IP address to Static.

Table 6-2 Communications RS-232 Connector Parameters

Pin Signal Description

1 RSD Received line signal detect (not connected)

2 RXD Receive Data

3 TXD Transmit Data

4 DTR Data Terminal Ready (not connected)

5 GND Ground

6 DSR Data Set Ready (not connected)

7 RTS Request to Send

8 CTS Clear to Send

9 RI Ring indicator (not connected)

The RS-232B/Time-division multiplexing (TDM) connector
block header. The
assignments.

TDM signals must be isolated. Table 6-3 lists this connector pin

is an 8-pin terminal

6-4

General Software Information

PRELIMINARY

Table 6-3 RS-232B/TDM Connector Parameters

Pin Signal Description

1 TXD Transmit Data

2 RXD Receive Data

3 DTR Data Terminal Ready (not connected)

4 RTS Request to Send

5 CTS Clear to Send

6 GND Ground

7 TDM + TDM positive signal

8 TDM - TDM negative signal

Diagnostic RS–232 Serial Communications

The MPI 6000 can communicate via a serial, RS–232, communications protocol
(Table 6-4). The diagnostic RS
boot sequence.

Table 6-4 RS-232 Connector Specifications

Connector Type

Protocol

Baud

Parity

Stop Bits

Flow Control

If you connect the MPI 6000 directly to a host PC serial port, you must use a null-

m connector.

mode

–232 port can be used to display the operating system

9 pin D-sub male

RS-232

9600

Bits

8

None

1

None

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-23
tus. Table 6-5 lists this connecto

2 diagnostic connector can be used to check the external input/output sta-

r pin assignments.

6-5

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Table 6-5 Diagnostic RS-232 Connector Parameters

Pin Signal Description

1 5V PWR 5V power supply for I/O board

2 GND GND

3 I/O Signal 1 Input/output signal 1

4 I/O Signal 2 Input/output signal 2

5 I/O Signal 3 Input/output signal 3

6 I/O Signal 4 Input/output signal 4

7 Tag in Field 1 Contact Closure 1 for Tag in Field Signal

8 Tag in Field 2 Contact Closure 2 for Tag in Field Signal

Reader Command Protocol

The 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

Command request messages are initiated and used by the host to request specific

actions to be

Data acknowledge messages are initiated and used by

reception of co
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 i

command request messages

Asynchronous response messages are optionally initiated by the MPI 6000

response to specific command request messages received from the host.

Software flow control messages are initiated and

inform the host to start or stop sending command request messages. Additionally
ware flow control messages are initiated and used by the host to inform the MPI
60000 System to start or

this section.

performed by the MPI 6000.

mmand request messages received from the host. Additionally, data

stop sending messages.

the MPI 6000 to signal the

n response to specific

received from the host.

in

used by the MPI 60000 System to

, soft-

6-6

Unsolicited status messages are initiated and used by the MPI 60000 System

inform the host about specific warning or error conditions in the MPI 60000 System.

The host sends command request messages to
receiving command request mes
sages, command response messages, asynchronous response messages and if required

sages from the host sends data acknowledge mes-

the MPI 6000. The MPI 6000 after

to

General Software Information

PRELIMINARY

software flow control messages to the host. The host on receiving command resp
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 to the MPI 6000.

The MPI 6000 implements message sequence numbers and command sequence num­bers in all
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
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 independe
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
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 seque
priate message as specified above has been missed. See the software
sequence number controls section for more details.

of the message types (e.g. command request, data acknowledge

nce numbers are used on the receiving end to determine if the appro-

messages from the MPI 6000 sends data acknowledge

the receive

ntly track the number

request messages sent to the MPI 6000. The MPI 6000’s

of messages

communication

onse

, command

UDP/IP Fast Ethernet Communications Protocol

The 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 Message

The 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> = messa

sequence number of the message. See the software communication sequence number
controls section for details.

ge sequence number

, a byte that specifies the message

6-7

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

<cmd> = command, a word that specifies the

sections for details.

<cmdSeqNum> = command sequence number, a byte

sequence number of the message. See the software communication sequence number
controls section for details.

[<data>] = optional data payload

ciated

with each specific command. See the command sections for details.

<checksum> = checksum,

a byte that specifies the checksum of the

that varies in length from 0 to 65 bytes and is asso-

system command. See the command

that specifies the command

message.

Data Acknowledge Message

The 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 resp
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

onse messages, software flow control messages

<len> - length, word that specifies the number of bytes in the entire messa
<msgSeqNum> - message sequence number, byte that specifies the message sequenc

number of the message. See the software communication sequence number controls
section for details.

<cmd> - comma

tions for details.

<cmdSeqNum> - command sequence number, byte that specifies the command

sequenc
controls section for details.

<resp> - response, word that specifies the system response. See the response

for details.

<msgSeqNumAck> -

message sequence number of the message being acknowledged. See the software
communication sequence number controls section for details.

<checksum> - checksum, byte

e number of the message. See the software communication sequence number

nd, word that specifies

message sequence number acknowledge

that specifies the checksum of the message.

the system command. See the command sec-

, byte that specifies the

ge.

sections

Command Response Message

The MPI 6000 after receiving command request messages from the host sends com­mand response messages to the host.

e

The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications
command response message

6-8

shown here:

General Software Information

PRELIMINARY

<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <checksum>

where
<len> = length, a word that specifies the number of bytes in the entire message.
<msgSeqNum>

sequence number of the message. See the software communication sequence number
controls section for details.

<cmd> = command, word that specifies the syste

tions for details.

<cmdSeqNum> = command sequence number

sequence number of the message. See the software communication sequence number
controls section for details.

<resp>

tions for details.

[<data>] = optional data payload that varies in length from 0 to 63 by

ciated with each specific response. See the response sections for details.

<checksum> = checksum, a byte

= response, a word that specifies the system response. See the response sec-

= message sequence number

that specifies the chec

, a byte that specifies the message

m command. See the command sec-

, a byte that specifies the command

tes and is asso-

ksum of the message.

Asynchronous Response Message

The 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 communica
asynchronous response message shown here:

tions

<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <checksum>

where
<len> = length, a word that specifies the number of bytes in the entire message.
<msgSeqNum>

sequence number of the message. See the software communication sequence number
controls section for details.

<cmd> = command, word tha

tions for details.

<cmdSeqNum> = command sequence number

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 payloa

ated with each sp

<checksum> = checksum, a byte

= message sequence number

t specifies the syste

d that varies in length from 0 to 63 bytes and is associ-

ecific response. See the response sections for details.

that specifies the chec

, a byte that specifies the message

m command. See the command sec-

, a byte that specifies the command

ksum of the message.

6-9

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Software Flow Control Message

The 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 messa
for host op

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.
<msg

sequence number of the message. See the software communication sequence number
controls section for details.

<cmd> = command, a word that specifies the

sections for details.

<cmdSeqNum> - command sequence number, a byte that specifies the

sequence number of the message. See the software communication sequence number
controls section for details.

<resp>

tions for details.

<checksum> = checksum, a byte that specifies the checksum of the

eration.

SeqNum> = message sequence number

= response, a word that specifies the system response.

, a byte that specifies the message

system command. See the command

ges to the MPI 6000 as required

command

See the response sec-

message.

Unsolicited Status Message

The 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

<len> <msgSeqNum> <cmd> <cmdSeqNum> <status> [<data>] <checksum>

where
<len> = length, a word that specifies the number of bytes in the entire message.

SeqNum> = message sequence number

<msg

sequence number of the message. See the software communication sequence number
controls section for details.

<cmd> = command, a word that specifies the

sections for details.

<cmdSeqNum> = command sequence number, a byte

sequence number of the message. See the software communication sequence number
controls section for details.

message shown here:

, a byte that specifies the message

system command. See the command

that specifies the command

6-10

General Software Information

PRELIMINARY

<status> = status, a word that specifies the system status. See the

for details.

[<data>] = optional data payload that varies in length from 0 to 63 by

ciated with each specific response. See the response sections for details.

<checksum> = checksum, a byte

that specifies the chec

ksum of the message.

response sections

tes and is asso-

Serial Communications Protocol

The serial communications protocol implements the TransCore error correction proto­col (ECP) serial standard.

Command Request Message

The host sends command request messages to the MPI 6000 as required for system
operation.

The host and the MPI 6000 uses the following

st message as shown here:

reque

<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 &.

serial communications command

<le

n> - length, word that specifies the number of bytes in the entire message.

SeqNum> - message sequence number, byte that specifies the message

<msg

number of the message. See the software communication sequence number controls
section for details.

<cmd> - command, word that specifies the system c

tions for details.

<cmdSeqNum> - command sequence number, byte that specifies the command

sequence number of
controls section for details.

[<data>] - optional data payloa

ated with each sp

<crc16>

dancy check of the message exclusive of the <som> and <eom> bytes. The polyn

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

- 16 bit cyclic redundancy check, word that specifies the 16

the message. See the software communication sequence number

d that varies in length from 0 to 65 bytes and is associ-

ecific command. See the command sections for details.

16+X12+X5

+1 with a divisor polynome of 1021H

ommand. See the command sec-

the message which is defined

sequence

bit cyclic redun-

o-

6-11

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Data Acknowledge Message

The MPI 6000 after receiving command request messages from the host sends data
acknowledge messages to the host.

The host after receiving command response messa
sages, software flow control messages and unsolicited status
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> -
<msgSeqNum> - message sequence number, byte that specifies the message sequenc

number of the message. See the software communication sequence number controls
section for details.

<cmd> - comma

tions for details.

<cmdSeqNum> - command sequence number, byte that specifies the command

sequenc
controls section for details.

length, word that specifies the number of bytes in the entire messa

nd, word that specifies

e number of the message. See the software communication sequence number

the system command. See the command sec-

ges, asynchronous resp

messages from the MPI

onse mes-

ge.

e

<resp> - response, word that specifies the system response. See the response

for details.

<msgSeqNumAck> -

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
dancy check of the message exclusive of the <som> and <eom> byte

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

message sequence number acknowledge

16+X12+X5

+1 with a divisor polynome of 1021H

, byte that specifies the

bit cyclic redun­s. The polyno-

the message which is defined

Command Response Message

The 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

<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> [<data>] <crc16> <eom>

message as shown here:

sections

6-12

General Software Information

PRELIMINARY

where
<som> - start of message, byte that specifies the start of the message which is defined

as the ASCII character &.

<le

n>

- length, word that specifies the number of bytes in the entire mess

age.

<msgSeqNum> - message sequence number, byte that specifies the message

number of the message. See the software communication sequence number controls
section for details.

<cmd> - command, word that specifies the system c

tions for details.

<cmdSeqNum> - command sequenc

sequence number of
controls section for details.

<resp> - response, word that specifies the system response. See the response

for details.

[<data>] - optional data payload that varies in length from 0 to 63 bytes and is associ-

ated with each sp

<crc16>
dancy check of the message exclusive of the <som> and <eom> byte

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

- 16 bit cyclic redundancy check, word that specifies the 16

the message. See the software communication sequence number

ecific response. See the response sections for details.

e number, byte that specifies the command

16+X12+X5

+1 with a divisor polynome of 1021H

ommand. See the command sec-

the message which is defined

sequence

sections

bit cyclic redun-

s. The polyno-

Asynchronous Response Message

The 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 &.

<le

n> - length, word that specifies the number of bytes in the entire mess

<msgSeqNum> - message sequence number, byte that specifies the message

number of the message. See the software communication sequence number controls
section for details.

<cmd> - command, word that specifies the system c

tions for details.

ommand. See the command sec-

age.

sequence

6-13

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

<cmdSeqNum> - command sequence number, byte that specifies the command

sequenc
controls section for details.

e number of the message. See the software communication sequence number

<resp> - response, word that specifies the system response. See the response

for details.

[<data>] - optional data payload that varies in length from 0 to 63 bytes and is

ated with each specific response. See the response sections for details.

<crc16>
dancy check of the message exclusive of the <som> and <eom> byte

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

- 16 bit cyclic redundancy check, word that specifies the 16

16+X12+X5

+1 with a divisor polynomial of 1021H

the message which is defined

bit cyclic redun­s. The polyno-

sections

associ-

Software Flow Control Message

The 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 op

The host and the MPI 6000 uses the following seri
control message as

<som> <len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <crc16> <eom>

eration.

al communications software flow

shown here:

where
<som> - start of message, byte that specifies the start of the message which is defined

as the ASCII character &.

<len>

- length,

<msgSeqNum> - message sequence number, byte that specifies the message sequenc

number of the message. See the software communication sequence number controls
section for details.

<cmd> - command, word that specifies

tions for details.

<cmdSeqNum> - command sequence number, byte that specifies the command

sequenc
controls section for details.

<resp>

for details.

<crc16> - 16 bit cyclic redundancy check, word that specifies the 16
dancy check of the message exclusive of the <som> and <eom> byte

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

e number of the message. See the software communication sequence number

- response, word that specifies the system response. See the response

word that specifies the number of bytes in the entire messa

the system command. See the command sec-

16+X12+X5

+1 with a divisor polynome of 1021H

ge.

sections

bit cyclic redun­s. The polyno-

e

6-14

General Software Information

PRELIMINARY

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

the message which is defined

Unsolicited Status Message

The 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

<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 &.

n> - length, word that specifies the number of bytes in the entire mess

<le
<msgSeqNum> - message sequence number, byte that specifies the message

number of the message. See the software communication sequence number controls
section for details.

<cmd> - command, word that specifies the system c

tions for details.

<cmdSeqNum> - command sequenc

sequence number of
controls section for details.

shown here:

age.

sequence

ommand. See the command sec-

e number, byte that specifies the command

the message. See the software communication sequence number

<status> - status, word that specifies the system

details.

[<data>] - optional data payload that varies in length from 0 to 63 bytes and is asso-

ciated with each specific response.

<crc16>
dancy check of the message exclusive of the <som> and <eom> byte

mial for the CRC calculation is X
and an initial value of FFFFH for a CCITT16 type CRC.

<eom> - end of message, byte that specifies the end of

as the ASCII character %.

- 16 bit cyclic redundancy check, word that specifies the 16

See the response sections for details.

16+X12+X5

status. See the response sections for

bit cyclic redun-

s. The polyno-

+1 with a divisor polynomial of 1021H

the message which is defined

6-15

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

6-16

7

PRELIMINARY

Configuration Commands and

Responses

PRELIMINARY

Configuration Commands and Responses

PRELIMINARY

This chapter describes the MPI 6000 interface commands that are used
to configure the reader.

Configuring the MPI 6000

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. 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 Reader

This section describes the configuration commands that are used to set up the MPI

6000.

Set Frequency

This section describes the Set Frequency command that is used to set the MPI 6000
frequency. Figure
Frequency command data.

7-1 shows the command transaction process. Tabl e 7-1 lists the Set

Chapter 7

Figure 7-1 Set Frequency Command Process

This command sets the A Counter and B Counter least significant bits (LSB) for the
specified source.

Table 7-1 Set Frequency Command Parameters

Set Frequency Command Data

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

equency Command 08H

Set Fr

Unused Source 0XH

Data

Payload

7-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Table 7-1 Set Frequency Command Parameters

Unused A Counter XXH

Unused B Counter LSBs 0XH

Carriage Return 0DH

Table 7-2 shows the Set Frequency Response parameters.

Table 7-2 Set Frequency Response Parameters

Set Frequency Response Data

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Set

Frequency Command 08H

Unused Source 0XH

Acknowledge 00H

Carriage Return 0DH

The Source field identifies the source for the associated N Counter information (Table
7-3).

Table 7-3 Descriptions of Sources

Source Definition

0 Source 1

1 Source 2

Data

Payload

A Counter –
The A and B counters combine to form the 18-bit N Counter. The valid
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
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
ues instead of A and B counters.

7-4

This field contains the data for the binary five-bit A Counter of the PLL.

range of the A

valid range of

. This command will be modified to allow the system to send frequency val-

Configuration Commands and Responses

PRELIMINARY

System Interface Command Group Commands

This section describes the system commands used to configure the MPI 6000.

Table 7-4 System Interface Command Group

System Interface Command Command Code

System Identify 0000H

Set Communications Baud Rate 0001H

Get Communications Baud Rate 0002H

Set Time and Date 0003H

Get Time and Date 0004H

Firmware Download 0005H

Reset Reader 0006H

Get Stored Tag Response Message 0007H

Get Number of Stored Tag Response Messages 0008H

Delete All Stored Tag Response Messages 0009H

Get System Startup Status 000AH

Get Lane Controller Interface Status 000BH

Get System Interface Status 000CH

Get DigBrd Hdwr Remote Inventory 000DH

Get DigBrd CPU Boot Fmwr Remote Inventory 000EH

Get DigBrd CPU Appl Fmwr Remote Inventory 000FH

Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory 0010H

Set UDP/IP Core Lane Controller IP Address and Port Number Parameters 0011H

Get UDP/IP Core Lane Controller IP Address and Port Number Parameters 0012H

Set UDP/IP Core IP Address 0013H

Get UDP/IP Core IP Address 0014H

Get UDP/IP Core UDP Port Number 0015H

Each of the system command group commands is listed in this section.

7-5

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

System Identify

System Identify Command Data

System Identify Command 0000H

System Identify Response Data

System I

Vendor Name

Version I D

Part Number

Serial Number

System Identify Data Sizes

dentify Command 0000H

Payload

Payload

Data

Data

7-6

System Identify Data

Vendor Name 15 Bytes

Ve

rsion ID 15 Bytes

Part Number 15 Bytes

Serial Number 15 Bytes

Data

Size

Set Communications Baud Rate

Set Communications Baud Rate Command Data

Set Commun

Baud Rate Data Code XXH

ications Baud Rate Command 0001H

Data

Payload

Configuration Commands and Responses

PRELIMINARY

Set Communications Baud Rate Response Data

Set Communications Baud Rate Command 0001H

Baud Rate Data Codes

Baud Rate

19,200 bps 0CH

38,400 bps (System Default) 0DH

57,600 bps 0EH

115,200 bps 0FH

Payload

Code

Get Communications Baud Rate

Data

Data

Get Communications Baud Rate Command Data

Get Comm

Get Comm

Baud Rate Data Code XXH

unications Baud Rate Command 0002H

Get Communications Baud Rate Response Data

unications Baud Rate Command 0002H

Data

Pa

Data

Payload

yload

7-7

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Set Time and Date

Set Time and Data Command Data

Set Time and Date Command 0003H

Hours XXH

Minutes XXH

Seconds XXH

Hundredths of Seconds XXH

Month XXH

Day XXH

Ye a r XXH

Set Time and Data Response Data

Set Time

and Date Command 0003H

Data

Payload

Data

Payload

Time and Date Data Ranges

Time and Date Data Data Range

Hours 0 to 23 (00H to 17H)

Minutes 0 to 59 (00H to 3BH)

Seconds 0 to 59 (00H to 3BH)

Hundredths of Seconds 0 to 99 (00H 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)

7-8

Get Time and Date

PRELIMINARY

Configuration Commands and Responses

Get Time and Data Command Data

Get Time and Date Command 0004H

Get Time and Data Response Data Data Payload

Set Time and Date Command 0004H

Hours XXH

Minutes XXH

Seconds XXH

Hundredths of Seconds XXH

Month XXH

Day XXH

Ye a r XXH

Data

Payload

Firmware Download

Firmware Download Command Data

Firmware Download Command 0005H

Firmware Download Response Data

Firmw

are Download Command 0005H

Data

Payload

Data

Payload

7-9

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

The Firmware Download command is implemented as defined for
both UDP/IP Fast Ethernet and serial communications.

Reset Reader

Reset Reader Command Data

Reset Reader Command 0006H

Reset Reader Control Word A5A5H

Reset Reader Response Data

Reset Read

er Command 0006H

Data

Payload

Data

Payload

Get Stored Tag Response Message

Get Stored Tag Response Message Command Data

Data

Payload

Get

Stored Tag Response Message Command 0007H

Stored Tag Response Message Number XXXXH

Data

Payload

7-10

Get Stored Tag Response Message Response Data

Get

Stored Tag Response Message Command 0007H

Stored Tag Response Message Number XXXXH

Stored Tag Response Message Data

Configuration Commands and Responses

PRELIMINARY

Get Number of Stored Tag Response Messages

Get Number of Stored Tag Response Messages Command Data

Get Number of Stored Tag Response Messages Command 0008H

Get Number of Stored Tag Response Messages Response Data

Get

Number of Stored Tag Response Messages Command 0008H

Number of Stored Tag Response Messages XXXXH

Data

Payload

Data

Payload

Delete All Stored Tag Response Messages

Delete All Stored Tag Response Messages Command Data

Data

Payload

Delete All Stored Ta

Delete All Stored Tag Response Messages Control Word A5A5H

Delete All Stored Tag Response Messages Response Data

Delete All Stored Ta

g Response Messages Command 0009H

Data

Payload

g Response Messages Command 0009H

Get System Startup Status

7-11

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Get System Startup Status Command Data

Get Syst

Get Syst

System Startup Module Number (System Initialization) XXXXH

System Timer Initializ

Sys

System Queue Create Status Error Number XXXXH

System Task Create Status Error Number XXXXH

em Startup Status Command 000AH

Get System Startup Status Response Data

em Startup Status Command 000AH

ation Status Error Number XXXXH

tem BMU Initialization Status Error Nu

mber XXXXH

Data

Payload

Data

Payload

Get Lane Controller Interface Status

Data

Payload

Data

Payload

7-12

Get Lane Controller Interface Status Command Data

Get

Lane Controller Interface Status Command 000BH

Get Lane Controller Interface Status Response Data

Get

Lane Controller Interface Status Command 000BH

Module Number XXXXH

Error Number XXXXH

Get System Interface Status

PRELIMINARY

Configuration Commands and Responses

Get System Interface Status Command Data

Get System Interface Status Command 000CH

Get System Interface Status Response Data

Get

System Interface Status Command 000CH

Module Number XXXXH

Error Number XXXXH

Data

Payload

Data

Payload

Get DigBrd Hdwr Remote Inventory

Get Digital Board Hardware Remote Inventory

Command Data

Data

Payload

Get Digital Board Hardware Remote Inventory Command 000DH

Get Digital Board Hardware Remote Inventory Response Data

Get Digital Board Hardware Remote Inventory Command 000DH

Vendor Name

Version I D

Part Number

Serial Number

Data

Pa

yload

7-13

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Hardware Remote Inventory Data Sizes

Hardware Remote Inventory Data

Vendor Name 15 Bytes

Version I D 15 Bytes

Part Number 15 Bytes

Serial Number 15 Bytes

Data

Size

Get DigBrd CPU Boot Fmwr Remote Inventory

Get Digital Board CPU Boot Firmware Remote Invent

Command Data

Get Digital Board CPU Boot Firmware Remote Inventory Command 000EH

ory

Data

Payload

Get Digital Board CPU Boot Firmware Remote Invent

Response Data

Get Digital Board CPU Boot Firmware Remote Inventory Command 000EH

Vendor Name

Version I D

Part Number

ory

Data

Payload

Get DigBrd CPU Appl Fmwr Remote Inventory

7-14

Get Digital Board CPU Application Firmware Remote

Command Data

Get Digital Board CPU Application Firmware Remo
Command

te Inventory

Inventory

Data

Payload

000FH

Configuration Commands and Responses

PRELIMINARY

Get Digital Board CPU Application Firmware Remote Inventory

Get Digital Board CPU Application Firmware Remote Inventory
Command

Vendor Name

Version I D

Part Number

Response Data

000FH

Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory

Get Digital Board FPGA UDP/IP Core Firmware Remote Inventory

Command Data

Get Dig
Command

ital Board FPGA UPD/IP Core Firmware Remote Inventory

0010H

Data

Payload

Data

Payload

Get Digital Board

Get Digital Board FPGA UPD/IP Core Firmware Remote Inventory
Command

Vendor Name

ion ID

Vers

Part Number

Firmware Remote Inventory Data Sizes

FPGA UDP/IP Core Firmware Remote Inventory

Response Data

Data

Payl

0010H

oad

7-15

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Firmware Remote Inventory Data

Vendor Name 15 Bytes

rsion ID 15 Bytes

Ve

Part Number 15 Bytes

Data

Size

Set UDP/IP Core Lane Controller Parameters

Set UDP/IP Core Lane Controller Parameters Command Data

Set UDP/IP Core Lane Controller Parame

IP Address (MSW) XXXXH

IP Address (LSW) XXXXH

Por t Number XXXXH

ters Command 0011H

Pa

Data

yload

Set UDP/IP Core Lane Controller Parameters Response Data

Set UDP/IP

Core Lane Controller Parame

ters Command 0011H

Data

Payload

Get UDP/IP Core Lane Controller Parameters

Data

Payload

7-16

Get UDP/IP Core Lane Controller Parameters Command Data

Get UDP/I

P Core Lane Controller Param

eters Command 0012H

Configuration Commands and Responses

PRELIMINARY

Get UDP/IP Core Lane Controller Parameters Response Data

Get UDP/I

IP Address (MSW) XXXXH

IP Address (LSW) XXXXH

Por t Number XXXXH

P Core Lane Controller Param

eters Command 0012H

Data

Payload

Set UDP/IP Core IP Address

Set UDP/IP Core IP Address Command Data

Set UDP/IP

IP Address (MSW) XXXXH

IP Address (LSW) XXXXH

Core IP Address Command 0013H

Data

Payload

Data

Payload

Set UDP/IP

Set UDP/IP Core IP Address Response Data

Core IP Address Command 0013H

Get UDP/IP Core IP Address

Data

Payload

7-17

Get UDP/I

Get UDP/IP Core IP Address Command Data

P Core IP Address Command 0014H

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

Get UDP/IP Core Lane Controller Parameters Command Data

Get UDP/I

IP Address (MSW) XXXXH

IP Address (LSW) XXXXH

Get UDP/IP Core Port Number

Get UDP/IP Co

P Core IP Address Command 0014H

Get UDP/IP Core Port Number Command Data

re Port Number Command 0015H

Get UDP/IP Core Port Number Command Data

Data

Payload

Data

Payload

Data

Payload

Get UDP/IP Co

Por t Number XXXXH

re Port Number Command 0015H

7-18

8

PRELIMINARY

Tag Command Processing

PRELIMINARY

This chapter provides definitions of and instructions for reading from

PRELIMINARY

and writing to a tag, as well as explanations of the tag command codes.

Reader Operation

The reader can operate in one of two command sequences, either read or write. The
tag command sequences for the Read and Write operations are detailed in the follow­ing sections.

Write Commands

To be provided.

Read Commands

To be provided

Chapter 8

Tag Command Processing

Host Commands Required for Tag Processing

To be provided.

8-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

8-4

9

PRELIMINARY

System Diagnostics and

Preventive Maintenance

PRELIMINARY

System Diagnostics and

PRELIMINARY

Preventive Maintenance

This chapter provides information on the following subjects:

Error Messages

Troubleshooting

Preventive Maintenance Schedule

Visual Inspection

MPI 6000 Repair

Removal and Replacement Procedures

Technical Support

Chapter 9

Troubleshooting Indications and Actions

To be provided.

9-3

MPI 6000 Multi-Protocol Reader System Guide

PRELIMINARY

9-4

A

PRELIMINARY

Acronyms and Glossary

PRELIMINARY

A

PRELIMINARY

AC alternating current

ACK acknowledge (data valid)

Appendix A

Acronyms and Glossary

antenna passive device that converts RF energy into magnetic

ATA American

and data storage method. ATA-type tags are

AVI automatic vehicle identification

Trucking Associations refers to a standard RF communications protocol

read only.

energy (RF signal)

B

backscatter portion of an RF signal that is modulated by a tag and radiated back to the reader

baud measure of number of bits per second of a digital signal; for example, 9600

baud = 9600 bits per second

bit The smallest unit of information, consisting of

digit

byte binary

character; for example, one 8-bit ASCII character

a 0 or 1, that is formed from a binary

C

cm centimeter(s)

command data set that is recognized by the receiving device as intending to elicit a specific

response

CRC cyclic redundancy

CTRL control

CTS clear to send

check

D

data information that is processed by a computing device

A-3