Axle Counters vs Track Circuits: How to Choose, and What Breaks in Service
A practical comparison of axle counters and track circuits for railway train detection — selection criteria, reset procedures, common failure modes, and what to monitor on each. Written from field experience on Indian Railways installations.
Two Ways to Answer One Question
Every signalling system has to answer a single question continuously and safely: is this section of track occupied? Get it wrong in the permissive direction — reporting clear when a train is present — and you have a collision.
Two technologies dominate. Track circuits use the rails themselves as an electrical conductor and detect the train's axles shorting that circuit. Axle counters place sensors at each end of a section and count wheels in and out; if the counts match, the section is clear.
Both are proven. Both are safe when correctly applied. But they fail in completely different ways, and choosing between them is one of the more consequential decisions in a signalling design.
Related: Track Circuit Working Principle & Types — the electrical fundamentals this post assumes.
How an Axle Counter Actually Works
The counting head is a pair of inductive sensors mounted on the rail web. Each sensor generates a magnetic field; a passing steel wheel disturbs it.
direction of travel ──────────────>
wheel
( )
┌──────┴──────┐
═════╧═════════════╧═════ rail
S1 S2 two sensors, offset by ~100 mm
S1 triggers, then S2 → count IN (+1)
S2 triggers, then S1 → count OUT (-1)
The two-sensor offset is the whole trick. A single sensor could only say "metal present." Two sensors in a known physical order give you direction, which means a wheel that rolls partway over the head and rolls back does not corrupt the count.
The evaluator compares totals:
IN count at entry head = 48
OUT count at exit head = 48
────
section state = CLEAR
IN count at entry head = 48
OUT count at exit head = 44
────
section state = OCCUPIED (4 axles unaccounted for)
SSDAC vs MSDAC
Indian Railways deployments generally use one of two configurations:
| SSDAC | MSDAC | |
|---|---|---|
| Full name | Single Section Digital Axle Counter | Multi Section Digital Axle Counter |
| Sections covered | One | Several (typically up to 8) |
| Detection points | 2 | Multiple, shared between sections |
| Cost per section | Higher | Lower at scale |
| Failure blast radius | One section | All sections on that evaluator |
| Typical use | Isolated sections, level crossings | Station areas, multi-section yards |
The blast-radius row is the one that gets underweighted at design time. An MSDAC evaluator fault can take out an entire station's detection simultaneously. That is a very different operational incident from losing one SSDAC section.
The Real Comparison
Vendor literature compares detection accuracy. In service, that is rarely the deciding factor — both are accurate. What actually differs:
| Factor | Track Circuit | Axle Counter |
|---|---|---|
| Ballast condition sensitivity | High — wet/dirty ballast causes false occupancy | None |
| Rail condition sensitivity | High — rust, contamination cause poor shunting | Low |
| Traction return current immunity | Poor — needs impedance bonds, careful design | Good |
| Maximum section length | Limited (~1–2 km typical) | Long (several km) |
| Broken rail detection | Yes — inherent to the principle | No |
| Insulated rail joints needed | Yes (a maintenance liability) | No |
| Recovery from disturbance | Self-restoring | Requires a reset |
| Failure mode | Usually fails to occupied (safe) | Fails to occupied, but needs intervention |
| Sensitivity to nearby metal work | Low | Moderate — track machines can inject counts |
The broken-rail row matters more than it looks
A track circuit passes current through the rail. Break the rail and the circuit opens, and the section shows occupied. You get broken rail detection for free as a side effect of the detection principle.
An axle counter does not. Its sensors are at the section boundaries; the rail between them could be fractured and the system would happily report the section clear. If you replace track circuits with axle counters across a route, you have silently removed a broken-rail protection you previously relied on. That has to be a conscious decision, compensated elsewhere.
The reset row is the operational reality
This is where axle counters generate work. Track circuits are self-restoring: fix the wet ballast, the circuit recovers on its own. Axle counters hold their count state. Any event that corrupts the count — a power dip, a sensor fault, a track machine working inside the section, an axle stopping directly over a head — leaves a discrepancy that only a human can clear.
Reset Procedures, and Why They Are Deliberately Awkward
A reset tells the system "trust me, this section is empty." If that assertion is wrong, the consequence is a signal cleared into an occupied section. So the procedure is designed to be hard to do casually.
The typical two-stage sequence:
1. PREPARATORY RESET
Operator presses preparatory reset.
System arms, but the section stays OCCUPIED.
2. PHYSICAL VERIFICATION
Staff confirm on the ground that the section is clear.
This step is the actual safety control.
3. CO-OPERATIVE / FINAL RESET
Two authorised persons act together (or a train
is passed through to re-establish the count).
Section returns to CLEAR.
Two points that matter in practice:
- The verification step is the safety control, not the button presses. The interlock exists to force a human to go and look. Treating reset as a routine keystroke defeats the entire design.
- Reset frequency is a diagnostic signal. A section needing weekly resets is telling you something — a marginal sensor, a failing power supply, EMI from traction. Log resets and trend them. Frequent resets are a symptom, not a chore.
Failure Modes Worth Knowing
Count discrepancy after track machine working. Tampers and other on-track plant have steel wheels the system may or may not count consistently. Standard practice is to disable/block the section for planned work and reset afterward, rather than let the machine corrupt live counts.
Axle standing over a detection head. A train stopped with a wheel parked directly over a sensor can cause repeated edge triggers as it rocks. Better evaluators debounce this; older ones may drift.
EMI from traction return. On 25 kV AC lines, return current and harmonics couple into sensor cabling. Symptoms are intermittent phantom counts with no train present, often correlating with heavy traction load. Cable routing, screening, and screen earthing are the fixes — chasing the evaluator is usually wasted effort.
Power supply dips. Brownouts can reset the evaluator's volatile state without a clean restart. This shows up as an unexplained discrepancy after a supply event. Check supply logs against discrepancy timestamps before suspecting the sensors.
Sensor mounting loosening. The sensor-to-rail geometry is specified tightly. Vibration loosens brackets, the gap changes, sensitivity drifts, and you get intermittent missed counts — the most dangerous direction of error, since missed counts can make an occupied section look clear. Mounting torque checks belong in routine maintenance.
What to Monitor Remotely
If you are instrumenting axle counters for condition monitoring, the useful signals are:
Per detection point:
- sensor supply voltage
- sensor current / oscillator amplitude (drift = mounting or sensor degradation)
- count events with timestamps
Per section:
- current IN / OUT totals
- discrepancy events (count + timestamp)
- reset events (type, operator, timestamp)
Per evaluator:
- supply voltage and dips
- internal temperature
- communication link health
- self-test / diagnostic status
The two highest-value derived metrics:
- Reset rate per section per month. Ranks your fleet by which sections are actually degrading. This alone justifies the monitoring effort.
- Oscillator amplitude trend per sensor. A slow downward drift is mounting movement or sensor aging, and it is visible weeks before intermittent missed counts start.
Both are trend metrics, not thresholds. A single reading tells you little; the slope tells you what is about to fail.
Related: SNMP for Industrial & Railway Device Monitoring — how to get this telemetry off the equipment and into an NMS.
A Selection Checklist
Choose track circuits when:
- Broken rail detection is part of your safety argument
- Sections are short and ballast/drainage is well maintained
- You want self-restoring behaviour with no operator intervention
- Existing infrastructure (impedance bonds, IRJs) is already in place
Choose axle counters when:
- Sections are long, or ballast/rail conditions cause chronic false occupancy
- You want to eliminate insulated rail joints as a maintenance liability
- Traction return current makes track circuit design difficult
- You can support the reset discipline operationally
Reconsider carefully when:
- You are replacing track circuits wholesale and would lose broken rail detection with nothing compensating
- Staffing cannot reliably support correct reset procedure — the technology assumes that discipline
- One MSDAC evaluator would concentrate failure risk across a whole station
Frequently Asked Questions
What is the main difference between an axle counter and a track circuit?
A track circuit detects a train by using the rails as an electrical circuit that the axles short out. An axle counter counts wheels into and out of a section with sensors at each boundary and compares the totals. The track circuit is condition-sensitive but self-restoring; the axle counter is condition-tolerant but needs a manual reset after any count corruption.
Why do axle counters need a reset at all?
Because they hold state. The system's knowledge of occupancy is a running count, not a live measurement. If anything corrupts that count — a power dip, a sensor fault, on-track plant — the system cannot know on its own whether the section is genuinely occupied. Only physical verification by a human can re-establish the truth, which is what the reset procedure enforces.
Do axle counters detect broken rails?
No. This is the most important functional difference. Broken rail detection is an inherent side effect of the track circuit principle, and axle counters do not provide it. Any migration from track circuits to axle counters must account for that loss explicitly.
What is the difference between SSDAC and MSDAC?
SSDAC covers a single section with its own evaluator. MSDAC covers multiple sections from a shared evaluator, which is cheaper per section but concentrates failure risk — one evaluator fault can affect every section it serves.
Which is better for Indian Railways conditions?
It depends on the location rather than the country. Axle counters are strong where ballast contamination, monsoon drainage, or heavy traction return current make track circuits unreliable — which describes many sections. Track circuits remain preferable where broken rail detection is required and conditions are well maintained. Most real networks run both, chosen per location.