Mode 05: oxygen sensor monitoring test results

Reading an oxygen sensor waveform and judging whether it is “fast enough” takes practice. Mode 05 removes the judgement: the ECU ran a defined test, measured the result, and stored the number alongside the limits it was compared against.

Related: O2 sensor waveform analysis and oxygen sensor lambda OBD diagnostics.

What it gives you

For each sensor, a set of test results with a measured value, a minimum limit and a maximum limit. Typical tests include:

Test	What it measures
Rich-to-lean switch time	How fast the sensor responds going lean
Lean-to-rich switch time	How fast it responds going rich
Minimum voltage	Lowest value reached
Maximum voltage	Highest value reached
Switch point voltage	Where the sensor crosses

The value against the limits is the diagnosis. A sensor near the edge of its window is ageing and will set a code eventually; one comfortably inside is healthy.

That is more useful than a snapshot, because it tells you the trend rather than the state.

Why it beats watching a live graph

Two reasons.

Consistency. The ECU runs its test under controlled conditions. A live graph is affected by whatever the engine happened to be doing.

Comparability. Comparing one sensor with another, or with the same sensor six months ago, is meaningful when the test conditions were the same.

Track it over time. A switch time that has grown steadily over a year is a sensor approaching the end of its life — visible long before any code: P0133 oxygen sensor slow response.

The limitation worth knowing

Mode 05 was defined for the older CAN-preceding protocols and for narrowband sensors.

Many modern vehicles do not support it, and instead expose equivalent data through Mode 06: Mode 06 advanced diagnostics.

Wideband sensors also do not fit the Mode 05 model, because they do not switch — they measure a continuous ratio: P2237 to P2240 wideband oxygen sensor.

If your vehicle returns nothing for Mode 05, check Mode 06 before concluding anything.

Reading the results

Finding	Interpretation
All values comfortably within limits	Sensors healthy
Switch times near the maximum limit	Ageing sensor — plan for it
One sensor much slower than its pair	That sensor is going
Values outside limits	The code is coming, or already stored
No data returned	Mode 05 unsupported — try Mode 06

Comparing the two upstream sensors on a V-engine is the single most efficient use of this data. They wear at similar rates, so a large difference between them identifies the failing one.

What it does not tell you

Mode 05 tests the sensor. It does not tell you whether the sensor is reporting a real problem.

A sensor that responds quickly and correctly to a genuinely lean mixture will pass every Mode 05 test while reporting a fault. The test is about the instrument, not about the engine.

For the mixture itself, look at fuel trims: fuel trim STFT and LTFT explained.

The practical use

Before buying a used car. Slow switch times mean sensors near replacement, which is a modest cost, and it also predicts a catalyst code in the near future.

After replacing a sensor. Confirm the new one performs inside limits, which catches a bad aftermarket part immediately.

As a periodic check. Once or twice a year on a car you intend to keep. The trend is the value.

Best OBD PIDs to log on a daily driver and how often to do car diagnostics.

Read the sensor test results if your vehicle supports them — an ELM327 adapter and the free tier of the app are all it takes. A number against a limit is a much firmer basis for a decision than a waveform you are trying to judge by eye.