Operations and Maintenance Manual

_
MPR 4.1 Reader Maintenance Instructions
Confidential UM UM360479-100 Revision: Draft B4 Page 80 of 246
© Kapsch TrafficCom Canada Inc. 2022
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
Field
Description
Ag
Agency ID of transponder in capture zone.
Ahs
The number of handshakes (Reads) that occurred on the assigned Port up to voting time. (note RPVs
currently count as 1)
THs
For a TDM Transaction:
The total number of handshakes (Reads) that occurred on the assigned Port for the previous TDM
transaction on the same RF Port. (Note RPVs currently count as 1). A value of 00 is reported after reset or
power-up. A value greater than 99 is indicated as 99.
For a Non-TDM Transaction:
The total number of handshakes (Reads) that occurred on the assigned Port for the previous non-TDM
transaction on the same RF Port. A value of 00 is reported after reset or power-up. A value greater than 99
is indicated as 99.
GUARD
Shown for a transaction assigned to a RF Port set to Guard. These transactions will always show !LC to
indicate that no report for the LC is generated. Tag programming is disabled for Guard Ports.
?LA
In a POST report, indicates that a lane assignment change was detected between the voting time report and
the post time report. May be an indication that voting time is not optimal.
?PS
In a POST report, indicates that a programming status change was detected between the voting time report
and the post time report.
>LC
>LC indicates transaction is to be reported to lane controller (connection present or not). Only appears on
the Active CTM
!LC
!LC indicates transaction is suppressed (e.g. GUARD lane or CrossR transactions or CTM is Inactive).
Cx-HS
HS tag handshakes seen up to voting/post time on the MasterSet center Reader. Note: Does not appear
unless there is inter-reader communication.
Lx-HS
HS tag handshakes seen up to voting/post time on the MasterSet left Reader. Note: Does not appear unless
there is inter-reader communication.
Rx-HS
HS tag handshakes seen up to voting/post time on the MasterSet right Reader. Note: Does not appear
unless there is inter-reader communication.
Event Logs
The event log is generated to record any reader events or changes (for example, if the power supply
status changes). During service, the technician should first examine the event log files to see if there
are any reported events with the reader.
The following list depicts the possible sources of event messages found in the event log.
• Changes to the reader configuration