Operations and Maintenance Manual

_
MPR 4.1 Reader Maintenance Instructions
Confidential UM UM360479-100 Revision: Draft B4 Page 78 of 246
© Kapsch TrafficCom Canada Inc. 2022
All information contained herein is proprietary to, and may only be used with express, written permission from, Kapsch TrafficCom Canada Inc.
FILE: UM360479-100 REV B4 DRAFT WIP MPR-4.1 READER OPERATIONS AND MAINTENANCE MANUAL (002).DOCX
05/25/2022 11:18
Kapsch TrafficCom
Log files
The log files for OBU transactions are saved by the Reader. 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 only.
Table 4-2: List of Available Log Files
Log File Type
Description
tagtxns_yyyy-mm-dd
Daily tag Transaction log.
event_yyyy-mm-dd
Daily event log files. Event log contain a periodic report of system
health and transaction count totals.
trouble_yyyy-mm-dd
Trouble Log. Content lists any unusual system anomaly (e.g.
switchover).
Transaction logs
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.
Each transaction can generate multiple report for a transaction. Which reports are provided depend
on the selection of reports in the Lane Controller page. The report types and the fields they contain
described in Table 4-3.