Operations and Maintenance Manual

MPR 4.1

Reader Maintenance Instructions

Confidential UM UM360479-100 Revision: Draft B4 Page 76 of 246

All information contained herein is proprietary to, and may only be used with express, written permission from, Kapsch TrafficCom Canada Inc.

FILE: UM360479-100 REV B4 DRAFT WIP MPR-4.1 READER OPERATIONS AND MAINTENANCE MANUAL (002).DOCX

05/25/2022 11:18

Kapsch TrafficCom

If the reader detects that the sync bus is driven high prior to the expiry of this delay, the reader exits

delay mode and performs one of the following actions.

• Sets its driver high and falls into synchronization frame start delay if programmed

• Sets its driver high and begins firing its Frame sequence.

Synchronization frame start delay

Synchronization frame start delay programs how long the Reader waits after Reader-to-Reader sync

has occurred. Its internal driver is set to a high state before firing the next frame and/or frame

sequence.

Sync recovery time

Sync recovery time is a programmable variable that indicates how long the reader searches/waits for

synchronization on the reader network before firing its frame sequence. It is recommended that this

value be programmed at least 125% of the total frame sequence.

If the reader detects that the sync bus is driven high prior to the expiry of this time, the reader exits

recovery mode, sets its driver high and begins firing its frame sequence.

Sync recovery attempt limit:

Sync recovery attempt limit is used to indicate how many Sync Recovery Time periods must expire

before the Reader no longer searches/waits for synchronization before firing its tag acquisition

sequence independent of the reader network. A loss of reader synchronization message will be

transmitted via the lane controller interface.

If this limit is programmed with a zero (0) value, the Reader will always wait for Sync Recovery Time

to expire before firing its sequence.

Sync-on-skipped-sync frame

Sync-on-skipped-sync frame is used when more than 3 protocols are selected in the frame sequence.

A two sequences-skip is used to indicate where the sequence starts.

How Reader synchronization operates at the toll location

After interrogating all of the assigned ports, each Reader will provide a ‘sync ready’ signal on its SYNC

Connector. Only when the configuration parameter Enable Reader –to-Reader Sync checkbox is

selected under the SYNC tab does synchronization occur.

As busy Readers become ready they will not send any more RF trigger signals until the sync bus

indicates that all Readers are ready. Once the last Reader in the network generates its ready signal, all

Readers on the sync bus simultaneously generate OBU trigger pulses starting with the RF module in