Operations and Maintenance Manual

JANUS

Multi-Protocol Reader 2.4 Maintenance Instructions

Confidential UM 360467-110 Revision: B Page 147 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

Table 4-1: Boolean Logic Truth Table for Synchronization of two Readers

The truth table above demonstrates the following rule of synchronization operation:

• The sync bus will only be in the ready state when all Readers in the group are in the ready state.

The last Reader to acquire a ready state controls the system synchronization. Most of the time (greater than

95%), the sync bus will be in the busy state. If operating correctly, the sync bus will normally be in the ready

state for about 100 sec.

Transaction Buffering

Transactions from OBUs, are processed by the CTM. When a Reader CTM loses communications with a Lane

Controller (LC), the Reader buffers OBU transactions and error messages (up to a combined total of 1,000,000)

in non-volatile memory (i.e., buffered messages will not be lost during power interruptions or Reader resets).

When the memory is full, new transactions overwrite the oldest buffered transactions. The memory available

for buffering is shared by all RF channels.

When the communication link between an LC and the Reader is re-established, the Reader begins to upload the

buffered transactions to the LC. The Reader will pause uploading buffered transactions to the LC to report any

new transactions as they occur. Buffered transaction reporting resumes after the new transactions have been

reported. Messages from the LC will continue to be acknowledged and acted upon during the upload process.

Log files

The readers generates a number of logs files during its operation. Log files can be viewed from the Log page of

the web interface.

Once space is filled on the respective memory partition, the oldest file from the same file type is deleted to

create memory space for the new data.

A listing of the main log file types appears below. Other log files that may be present are for Kapsch TrafficCom

use.

Reader 1 sync port Tx

Reader 2 sync port Tx

Reader 1 or 2 sync port Rx

0 (ready)

1 (busy)

0 (ready)

1 (busy)