Operations and Maintenance Manual

_
JANUS
®
Multi-Protocol Reader 2.4 Maintenance Instructions
Confidential UM 360467-110 Revision: B Page 148 of 247
© Kapsch TrafficCom Canada Inc. 2021
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-2: List of Log Files Types
Log File Type
Description
tagtxns_yyyy-mm-dd
Daily Tag Transaction log. Summary of individual OBU passages.
event_yyyy-mm-dd
Daily Event log. Contains a periodic report of reader health and
transaction count totals.
trouble_yyyy-mm-dd
Trouble Log. Lists any unusual system anomaly (e.g. switchover).
CAUTION:
Log file formats are not under ICD control and the format may
change without prior notification. Log files are for diagnostic
purposes only and are not guaranteed to be maintained in
non-volatile storage.
Tag Transaction Logs
The reader generates an entry for each transaction in a daily tag transaction log. A sample transaction summary
for a TDM OBU passage:
2020-10-22T23:05:15.121582+00:00 sitename-pri IAG__: VOTE> Ch:4 St:Pgm Txn:00002 Ag:0000
Sn:00000403 Pr:TDM AHs:06 THs:19 >LC
2020-10-22T23:05:15.121838+00:00 sitename-pri IAG__: 4-06
Note that a single vehicle passage can generate multiple reports. Which reports are generated depend on the LC
Reporting settings configured on the Lane Controller page. The report types and the fields they contain
described in Table 4-3.
Table 4-3: List of Fields in a Transaction Log Report
Field
Description
IREAD
Optional initial read report when transponder first enters capture zone. Informational report
VOTE
Transaction report at voting time
POST
Optional post-capture zone report if lane assignment or programming status has changed.
Informational report
Ch
Channel number. Indicates the assigned channel (1-8). Channel 1 corresponds to the leftmost RF
module in the RF rack.