Operations and Maintenance Manual

_
JANUS
®
Multi-Protocol Reader Ver. 2: Maintenance Instructions
Confidential UM 360463-202: A12 (Draft) Page 142 of 291
© Kapsch TrafficCom Canada Inc. 2013
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
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.
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
 Changes to the reader configuration at power up
 Reader status changes, such as PSM status, etc.
 Reader faults detected