Operations and Maintenance Manual

_
JANUS
®
Multi-Protocol Reader Ver. 2: Maintenance Instructions
Confidential UM 360463-202: A12 (Draft) Page 204 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
Event
Cause
Enabling
Test Tag failure
When the number of RF channels with failed
test tag reaches the set threshold, the
Reader will switch over to the redundant side
if the redundant side is running and has no
switchover conditions present. If the
redundant side is not functioning, the test tag
failure is ignored.
User must enable Test Tag
State for each RF channel
from the Test Tag tab on the
Configuration page
Reader recovery actions
For certain failures, the Reader will automatically initiate the recovery actions outlined in Table 6-5.
Table 6-5: Failures and the Reader Recovery Actions they trigger
Failure
Reader Recovery Action
CGC Health failure
reinitializes CGC on failed side
Serial LC link down
re-attempts connection on failed side once every
second
Ethernet LC link down
re-attempts connection on failed side once every
second or up to 10 seconds based on load
Inter-Reader Ethernet link down
switches to Badger style CRA on failed side to re-
attempt connection
Viewing MRFM fault codes
The MRFM-S sends binary fault codes from its LC COM port as part of a heartbeat message every 5 seconds.
These fault codes are Byte 4 and 3 of the heartbeat message and can be viewed on a computer connected to
the reader LC COM port.
Prerequisites: A computer equipped with RealTerm (or equivalent).
1. Connect the computer to the MRFM LC COM port using RealTerm (see Using RealTerm to connect to the
MRFM, page 261). Data from the MRFM will be visible in the RealTerm window.
2. If several messages appear in the RealTerm program, identify the heartbeat message by identifying Byte 9.
The value of Byte 9 is always 10111011.
3. Note the values of Byte 4 and Byte 3. Check Table 6-6 to determine if there is an MRFM fault.