CCB Fault Analyser

Load diagnostic reports

Single or bulk TXT upload · stored in the shared server database for all LAN users

Drop one or several .txt files here or click to select single / bulk reports from your computer Choose TXT files Upload Bulk Folder Searches all nested subfolders for TXT files and ignores every other file type. Choose folder

ANALYSIS READY

Event Log report

Fault activations 0 Event rows marked Fail

Fault dates 0 Dates containing a failure

Cleared faults 0 0% of failures

Event records 0 —

Event Log — every record in chronological order Nothing is omitted: Power Up (On), Fail, and Pass records all appear here. Stored Fault Log counters remain separate in the top-right viewer.

S/N	Event date	Event time	Event	Description	State	Cleared at	Duration	Mode	Record	MRTkg/cm²	BPTkg/cm²	BPaltkg/cm²	ERTkg/cm²	20TLkg/cm²	20TTkg/cm²	10Tkg/cm²	BCTkg/cm²	FLTkg/cm²

Occurrence-wise Event Log population Includes On, Fail, Pass, and any other state. Click a row to reveal every occurrence and its environment / pressure data.

	Rank	Event	Description	State	Total occurrences	Event dates	Cleared faults	Unresolved faults	First occurrence	Last occurrence

Num	MRTkg/cm²	BPTkg/cm²	BPaltkg/cm²	ERTkg/cm²	20TLkg/cm²	20TTkg/cm²	10Tkg/cm²	BCTkg/cm²	FLTkg/cm²	Mode	State	Time Stamp	Event	Description

ENTIRE STORED DATABASE

Fault occurrence analysis by locomotive

Each row is one fault, each locomotive is a column, and every cell shows how many times that fault occurred. Faults are ranked from the highest total occurrence count to the lowest.

Loading stored fault analysis…

PERSISTENT SHARED STORAGE

Locomotive-wise Fleet Database

Every imported TXT report and Event Log row is retained in the shared server database. Select a locomotive to fetch its records in exact date-and-time order.

Database key structure Locomotive → Timestamp → Report → Row Collision-safe composite Event Log key

Locomotives0

Stored reports0

Event records0

Fault activations0

Understand Database Structure

STORE 01 · PRIMARY MASTER locomotives Unique key: locomotive_number

One row per locomotive. Report/event/failure totals, first and latest timestamps, installed software versions, and last import time are calculated from its related rows.

STORE 02 · SOURCE ARCHIVE reports Primary key: report_id

Stores the complete raw TXT plus software version, counts, import time, locomotive link, and first/latest Event Log timestamps. Loading Log and Stored Fault Log rows are retained in related tables.

STORE 03 · EVENT FACT TABLE event_occurrences + event_log Identity: locomotive + occurrence start second + event code + state

Stores every accepted On, Fail, and Pass record, fault-clearance linkage, duration, mode, event details, source report, and all nine raw/scaled environment parameters.

Duplicate prevention

Within one TXT and across later files, a row is skipped when locomotive number, paired fault-occurrence start second, event code, and state already exist. Different event codes in the same second remain valid.

Fast retrieval indexes

ix_occurrences_loco_time and ix_event_log_time fetch chronological locomotive data; report and occurrence indexes support source retrieval, analysis, and duplicate lookups.

Stored locomotivesClick a row to retrieve that locomotive’s Event Log

Locomotive No.	Reports	Events	Failures	First Event	Last Event	Software Versions

Open the fleet database or import TXT reports to begin.

					State	Cleared at	Duration	Mode	Record	MRTkg/cm²	BPTkg/cm²	BPaltkg/cm²	ERTkg/cm²	20TLkg/cm²	20TTkg/cm²	10Tkg/cm²	BCTkg/cm²	FLTkg/cm²

No stored fleet data

Bulk upload one or more CCB TXT reports to populate the shared database.

FROM RAW FILE TO FINAL TABLE

Understand the complete algorithm

A short, auditable explanation of every rule applied by the analyser from file upload through parsing, scaling, sorting, storage, and export.

01
Separate the report sections
Software version, Loading Log, stored Fault Log Data, and Event Log Data are parsed independently. Stored Fault Log counters are never mixed into Event Log occurrences.
02
Capture the download software version
The first value, such as 2537_240508, is labelled as the software version used while downloading and saved locally with the report history.
03
Parse and retain Loading Log history
Installation number, date, time, user ID, filename, and the version extracted from the filename are stored as separate fields in chronological order.
04
Parse stored Fault Log Data separately
Current Status, Failure Count, Time Last Failed, Time Last Cleared, code, and description are retained exactly as a separate cumulative-status table.
05
Read fixed Event Log columns
Num, the nine pressure fields, Mode, State, Time Stamp, Event, and Description are mapped by their source positions. The unused Raw A2D, Trgt, and AW4 Press positions are skipped in the visible analysis.
06
Make timestamp the primary variable
MM:DD:YYYY::HH:MM:SS is converted to a real datetime. All rows are sorted by it because the circular record number can wrap from 200 back to 001.
07
Interpret State and pair fault episodes
Fail begins a fault. The next Pass with the same Event and Description clears it and supplies duration. On is an operational event such as Power Up.
08
Scale pressure values to kg/cm²
MRT, BPT, BPalt, ERT, 20TL, 20TT, 10T, BCT, and FLT use (raw ÷ 10) × 0.0703069579. Example: raw 1231 → 123.1 PSI → 8.66 kg/cm². N/A becomes Not Available.
09
Omit unused source fields
Raw A2D, Trgt, and AW4 Press are not used for this analysis, so they are intentionally removed from visible tables and processed exports.
10
Build the Event Log views
The chronological view retains every On, Fail, and Pass row. Data Population groups all rows by Event + Description + State, so their counts remain separate.
11
Store the fleet database
Bulk-uploaded TXT reports are stored on the LAN server for every user. Locomotive number is the fleet-master primary key; Event Log duplicate identity uses locomotive + fault occurrence start second + event code + state.
12
Preserve future reference data
The complete raw TXT, parsed Event Log, software version, Loading Log, and stored Fault Log are retained in the shared SQLite database for efficient future retrieval.
13
Export the processed result
Excel and PDF downloads follow the active filters and use the chronological timestamps and converted kg/cm² values displayed by the analyser.

PRESSURE CONVERSION kg/cm² = (raw value ÷ 10) × 0.0703069579

The original raw value and intermediate PSI value are retained in each converted cell’s tooltip.

Event Log abbreviations and units

ModeSTDBY: standby · L C/I: Lead Cut In · L C/O: Lead Cut Out · TRAIL: trailing mode

StateFail: fault activated · Pass: recovered/cleared · On: brake-system switching or power-up log

EventNumeric Event code

DescriptionEvent or fault description supplied by the CCB report