Operations and Maintenance Manual

JANUS

Multi-Protocol Reader 2.4 Maintenance Instructions

Confidential UM 360467-110 Revision: B Page 150 of 247

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

FILE: UM 360467-110 REV B3 MPR 2.4 CLEAN.DOCX 03/02/2021 1:01

Kapsch TrafficCom

Event Logs

The reader generates periodic entries into a daily event log file whenever the reader is operational. A sample

periodic entry, showing reader CPU and memory condition:

reader1-pri STAT_: {stat |6307| 444} CPU load: 10% RAM avail: 82%

The reader also generates a periodic tag transaction summary into the event log. A portion of this entry would

appear similar to the following:

Channel Prot Status Txns AvgHS Voting Latency Speed

3 TDM PGM 616 20.1 100 100 0

The interesting fields are typically Txns (the count of OBU passages) and AvgHS (the average total handshake

for all transactions of the specified protocol in the specified channel for the reporting interval).

Note that external events (for example power cycling a lane controller attached to a reader) can generate event

log entries, and the presence of such entries does not necessarily indicate a reader issue.

The following lists some of the possible sources of messages found in the event log.

• Changes to the reader configuration (made by an operator or a lane controller)

• Periodic OBU transaction count statistics.

• Periodic Reader CPU and Memory monitoring status.

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

• Lane controller connection outages (serial or Ethernet).

• Inter-Reader connection outages.

Trouble Logs

Unusual faults or error conditions are reported into a daily trouble log file. On the reader web interface,

examine the Log page under the "Trouble logs" section for a list of trouble log files. A daily trouble log file is only

present for a day in which there was something to report.

During service, the technician should first look for any trouble logs and review their content.

The following lists some of the possible sources of messages found in the trouble log:

• A reader startup message indicates a possible power interruption.

• A missing backplane CFM module.

• An RF module has stopped working or has been removed.

• CGC Health failure

• Switch-over to Secondary (if enabled for LC or Inter-reader fault conditions)