How the misfire monitor counts what it cannot see

Nothing inside a cylinder reports whether combustion happened. The ECU works it out from the crankshaft.

Understanding how explains several things that otherwise seem arbitrary: why misfire codes appear after a clutch job, why rough roads set them, and why the warning lamp sometimes flashes.

Related: P0300 random misfire deep dive.

Crankshaft deceleration is the measurement

Each combustion event accelerates the crankshaft slightly. Between events, it decelerates slightly.

The crankshaft position sensor resolves that variation precisely, using the toothed reluctor ring. A cylinder that fails to fire does not deliver its push, and the crank momentarily fails to accelerate as expected.

The ECU knows the firing order, so it knows which cylinder should have contributed. That is how a misfire is attributed to cylinder 3 rather than to the engine generally.

P0301 to P0304 cylinder misfire diagnostics and P0305 to P0308 on cylinders 5 to 8.

Two thresholds, two responses

The ECU counts misfires within rolling windows of revolutions and compares against two limits.

Type A — catalyst damaging. Enough misfires within a short window to overheat the catalyst. Response: the lamp flashes.

That flash means stop driving. Unburnt fuel is reaching a hot converter and can melt the substrate within minutes: check engine blinking vs solid.

Type B — emissions exceeding. A lower rate over a longer window. Response: a steady lamp and a stored code.

Why the counters are more useful than the code

Misfire counters per cylinder are live data, updating continuously. The code is only a summary.

That makes the counters the practical diagnostic tool:

Observation	Meaning
One cylinder accumulating	That cylinder — coil, plug, injector, compression
Two adjacent accumulating	Head gasket between them, or a shared coil pack
All cylinders on one bank	Bank-specific cause
All cylinders roughly equally	Fuel, air, or the crank signal itself
Counters rising under load only	Ignition under stress, or fuel delivery

Watch the counters during the swap test. Move a coil to another cylinder and see whether the accumulation follows — the counters answer before the code has time to set again.

Ignition coil and spark plug diagnostics.

Why rough roads set misfire codes

Because the measurement is mechanical.

A wheel dropping into a pothole transmits a jolt through the driveline to the crankshaft, and that jolt looks like an acceleration anomaly.

Manufacturers compensate — most systems use the ABS wheel speed sensors to detect rough road conditions and suspend the monitor. On vehicles where that compensation is imperfect, or where a wheel speed sensor is faulty, rough roads produce phantom misfire codes.

ABS wheel speed sensor diagnostics.

Why a crank sensor fault produces misfire codes

Same reason. The measurement depends entirely on a clean crankshaft signal.

A damaged reluctor ring, debris on the teeth, or an incorrect air gap makes the signal irregular — and irregular looks exactly like misfire.

Random misfire codes with no rough running are frequently a crank signal problem, and people replace coils and plugs for it.

P0336 crankshaft sensor range/performance and P0320 to P0322 engine speed input.

After clutch or gearbox work, suspect swarf on the reluctor ring before suspecting the ignition system.

Why low fuel suspends it

Running out of fuel causes misfires that are not the ignition system’s fault. Most systems therefore suspend or reclassify misfire detection below a fuel level threshold, and log it separately.

P0313 and P0314 misfire with low fuel.

What the monitor cannot tell you

It detects that a cylinder did not contribute. It does not know why.

Spark, fuel, compression and timing all produce identical crankshaft signatures. The monitor names the cylinder; you determine the cause.

A cylinder contribution code is the softer version of the same measurement — the cylinder fired but produced less than its share: P0263 to P0266 cylinder contribution and balance.

Sequence

1. Read misfire counters per cylinder, not just the code.
2. Note the pattern — one, adjacent pair, one bank, or all.
3. Check the freeze frame for the conditions.
4. Swap a component and watch the counters.
5. Check the crank signal if misfires are random with no rough running.
6. Check fuel level before diagnosing anything else.

This check needs no workshop — an ELM327 adapter and the free tier of the app cover it. Watch misfire counters per cylinder in real time. They update faster than any code and they name the cylinder immediately.