Operations and Maintenance Manual

ManualsBrandsKAPSCH TRAFFICCOM CANADA ManualsElectronicsNon-multilateration LMS transmitter and receiver

141

142

143

144

145

146

147

148

149

150

JANUS

Multi-Protocol Reader Ver. 2: Maintenance Instructions

Confidential UM 360463-202: A12 (Draft) Page 143 of 291

These drawings and specifications contain confidential and proprietary information and are the property of Kapsch TrafficCom Canada Inc. and are issued in strict

confidence and will be kept confidential and used solely for the purpose intended and for no other purpose and shall not be transmitted, reproduced, copied, and/or

used as the basis for manufacture or sale of apparatus unless otherwise agreed to in writing by Kapsch TrafficCom Canada Inc.

FILE: MPR2_OPERATIONS_AND_MAINTENANCE-MANUAL_REV A12.DOCX 05/08/2014 11:24

Kapsch TrafficCom

Trouble Logs

Unusual Reader issues generate trouble logs (for example, if a switchover has occurred). 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.

 No detection of a CFM backplane memory module.

 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 forced a switchover on detection of:

o Failed CGC health

o Failed serial LC link (when enabled). Possible cause: a fault external to the Reader

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

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