DTC off vs erasing fault codes — what actually changes in the file

A DTC is not a piece of data stored in the file like a document — it is an entry in the ECU's diagnostic table. The software runs monitors: routines that continuously test a sensor, an actuator or a subsystem against expected conditions. When a monitor fails, the diagnostic manager stores the code and a freeze frame, and — depending on the entry — lights the MIL or triggers limp mode.

Each entry in the table carries its own logic: enable conditions, debounce counters, MIL behaviour and the fail-safe path. That is why two codes on the same component can behave completely differently.

Erasing codes with a scan tool (OBD mode $04) empties the fault memory: stored and pending codes, freeze frames and counters — and it resets the readiness monitors to 'not complete'.

What it does not change is detection. The monitoring routines keep running exactly as before; on the next drive cycle that satisfies their conditions, the same test fails and the same code comes back — with a physically removed DPF, a welded EGR or a dead sensor, it is guaranteed. Permanent DTCs go further: a scan tool cannot erase them at all until the monitor passes on its own.

A DTC-off patch modifies the calibration so the fault is never registered in the first place. Depending on the ECU family that is done one of two ways:

• The DTC mask or deactivation table — the entry's enable bit or classification byte is changed so the diagnostic manager ignores that failure path entirely.
• The monitoring routine itself — when no usable mask exists for a code, the branch or function call that detects the fault is neutralised in the code area.

The result: the fault is never stored, counters never accumulate and the MIL path tied to that code can never trigger. To the ECU, the condition simply does not exist.

On a mask-based ECU the difference is a byte or two per code inside the DTC table. On routine-based ECUs it is a few patched instructions. Either way it is small and targeted — exactly the kind of change our DTC OFF service shows in its per-order audit trail.

Everything else is untouched: maps, other fault codes, immobiliser data. Checksums are recomputed so the file writes cleanly with standard tools.

• Readiness monitors can remain 'not ready' on some setups — relevant where inspections check OBD readiness.
• A masked code stays invisible forever — keep the original file so you can restore diagnostics later.
• Some codes share detection logic; a blanket 'all codes off' can hide unrelated real faults. Disable only what your hardware change requires.

If the cause is still fitted and working, fix the car — a DTC-off is for components that are physically gone or intentionally bypassed.

Disabling emissions-related monitors is intended for off-road and motorsport use where legal. On public-road vehicles it may be prohibited — check your local regulations before modifying a file.