Operations and Maintenance Manual

MPR 4.1

Reader Maintenance Instructions

Confidential UM UM360479-100 Revision: Draft B4 Page 81 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

• Changes to the reader configuration at power up

• Reader status changes, such as PSM status, etc.

• Reader faults detected

Trouble Logs

Unusual Reader issues generate trouble logs. During service, the technician should first examine these

trouble log files to see if there are any reported issues with the Reader.

Examine the Log Files page for instances of one or more trouble <date> file in the list of log files.

A typical report in a trouble log is:

2010-05-31T10:52:35.723+00:00 [lab3_5] SYNCR: Reader SYNC lost

Note: As an alternative, Kapsch Service can remotely connect to the Reader and examine the trouble

log to quickly identify and resolve any issues. It is up to the system administrator or integrator to

determine when to grant Kapsch Service remote access to the LC network IP addresses.

The following list depicts the possible sources of trouble messages found in the trouble <date> file.

• The Status file integrity check fails. Possible cause: there may be data for up to 40 million OBUs in a Status

file.

• The Reader software recorded a:

o Failed CGC health

o Failed Ethernet LC link. Possible cause: a fault external to the Reader

o Failed Ethernet inter-Reader link (when enabled). Possible cause: a fault external to the Reader