Guide · Level Crossing Monitoring

Level Crossing Flasher Fault Detection: A Practical Guide

A flasher fault is any condition where one or both of the alternating warning lamps at a railway level crossing fails to operate as designed. Left undetected, flasher faults compromise the visual warning system that protects road users — and they often go unreported until a routine inspection, or worse, an incident. This guide covers what causes flasher faults, how operators detect them remotely, and what signals to monitor to catch them early.

What is a level crossing flasher?

A flasher (or flasher unit) controls the alternating illumination of the warning lamps mounted on a level crossing signal mast. In a typical installation, two red lamps flash in opposition at roughly 45–65 cycles per minute when a train is approaching. The flasher unit drives them via a relay or solid-state switching circuit, sequenced by the level crossing control logic.

Failure of any element in this chain — lamps, driver, wiring, controller, or power supply — constitutes a flasher fault. Because the lamps are the road user's primary visual warning, flasher faults are categorised as safety-critical in every jurisdiction.

Common causes of flasher faults

• Lamp filament failure — single or both lamps open-circuit, often after thermal cycling
• Flasher driver failure — relay contacts welded, solid-state switch shorted or open
• Control circuit wiring — broken conductor, corrosion at terminals, or earth leakage
• Supply voltage out of range — battery discharge, charger fault, or mains brownout
• Timing or sequence error — controller logic fault causing both lamps on, both off, or wrong rate
• Environmental damage — water ingress, vibration loosening connections, vandalism

How to detect flasher faults remotely

Reliably detecting an individual lamp failure from current alone isn't trivial. The same lamp circuit draws different current at different battery voltages, and a healthy two-lamp circuit looks identical to a faulty four-lamp circuit by raw current. The robust approach is to count lamps, calibrated against a learned baseline.

Learning phase

During commissioning — or any scheduled maintenance where the lamp circuit is verified healthy — the on-site logic application records two reference values:

• Average lamp current divided by the configured number of lamps, giving a per-lamp current value
• The primary lamp battery bank voltage at the time of learning

Both values are retained as the calibration reference for that site. Re-learning re-baselines after lamp replacement or other planned changes.

Runtime detection

During normal operation, every flash cycle the logic application:

1. Gate condition — confirms lamp current has met the configured minimum threshold, so the calculation only runs when the lamps are actually energised
2. Smooth — samples lamp current through a 100-point moving-window average to reject noise and switching transients
3. Voltage compensate — adjusts the measured current for the difference between the present battery voltage and the learned voltage
4. Count lamps — divides the compensated current by the learned per-lamp value to produce a real-time number-of-lamps figure

The result is a continuously updated count of how many lamps are actually drawing current. Comparing this against the configured expected count is what surfaces individual lamp failures, independent of battery state.

Alarms

A complete flasher monitoring program covers more than just lamp count. The following alarms are raised by the on-site logic application when a fault condition is detected. Each is mapped to a severity in the operations console and relayed immediately to the central platform, with SMS fallback when cellular comms are unavailable.

Alarm	Condition
Flasher Active, No Lamp Current	The crossing is active but no lamp current is detected
Lamp Current on Inactive Flasher	Lamp current is present but the crossing isn't active
Flasher Excessive Activity	The flasher switches on and off continuously over a defined period
Flasher Time Exceeded	The flasher has remained active for longer than the configured maximum
Flasher Active, No Track Detected	The flasher is active but no train is detected on the track
Minor Lamp Fault	One lamp has failed — number-of-lamps count drops by one
Major Lamp Fault	Two or more lamps have failed — count drops by two or more

What to monitor in practice

For a complete flasher monitoring program, instrument the following signals at each crossing:

Signal	Purpose
Lamp current (per lamp)	Detect open/short, filament wear
Lamp voltage	Confirm drive is present and within spec
Flasher control signal	Verify controller intent vs. lamp state
Battery voltage	Power supply integrity
Cabinet door / tamper	Security, change-of-state log

Why early detection matters

Undetected flasher faults are a Category A safety risk in most rail safety frameworks. Standards such as EN 50129 (Europe) and AS 7658 (Australia) require continuous functional monitoring of warning systems, with a defined fault response time. Compliance aside, the operational case is straightforward: remote detection cuts mean-time-to-repair (MTTR) from days — typical when faults are found by inspection — to hours, and replaces unplanned site visits with planned, condition-based maintenance.

For a fleet of 100 crossings, the difference compounds. Even a modest reduction in MTTR translates into measurable reductions in road-user exposure to inoperative warning systems, and a meaningful drop in unplanned maintenance cost.

Frequently asked questions