Why I Don’t Trust Fault Codes

Back in 1994, nobody talked about DPFs. There was no AdBlue, no NOx sensors and certainly no particulate matter sensors. Engine control units were relatively simple, diagnostics were basic, and if you owned a decent multimeter, you were already ahead of the game. Cars were mechanical, mechanics relied on experience, and sometimes a little luck.

Then everything changed.

Electronic control units became increasingly sophisticated. OBD systems arrived, diagnostic scanners grew more powerful every year, and suddenly almost every workshop believed the same thing:

“The computer knows what’s wrong.”

For a while, I believed it too.

Thirty years later, I know better.

A diagnostic tool never tells you what is broken. It only tells you that something has happened which the ECU did not expect. That may sound like a small distinction, but it is one of the most important lessons any diagnostician will ever learn.

A fault code is not a diagnosis. It is a symptom. More accurately, it is the ECU raising its hand and saying, “Something doesn’t make sense anymore.”

Almost every day I receive the same phone call.

“Hi Andras, my DPF is blocked.”

My reply is always the same.

“How do you know?”

The answer rarely changes.

“Because that’s what the scanner says.”

At that point, I already know the conversation is going to take much longer than expected.

Many drivers—and, unfortunately, many technicians—treat fault codes as final verdicts. P2002? Replace the DPF. P2463? Blocked DPF. P2458? Another DPF problem.

Except… that isn’t what those codes actually mean.

They simply tell us that the regeneration process failed to complete under the conditions expected by the ECU. They don’t tell us why.

Imagine your phone displays the message: “Message failed to send.” Was there no signal? Was the Wi-Fi down? Had the battery died? Or had the recipient simply switched off their phone?

The message itself doesn’t tell you.

Neither does a fault code.