OBD II Monitor Logic: DTC Setting, Clearing, and MIL Operation

The short version — A fault has to show up on two trips before the MIL turns on, it needs three clean trips to turn back off, and permanent DTCs won't clear for anybody but the PCM itself — no scan tool, no battery disconnect trick.

How a Code Gets Born: Pending → Confirmed

OBD II watches emissions-related components and sets a DTC any time a monitored parameter drifts outside its allowed range. That's the whole point of the system — it's a standardized way to catch a failure that could increase tailpipe emissions, and to warn the driver with the MIL.

But the PCM doesn't just throw the lamp on the first time it sees a problem. Here's the sequence:

• Trip one, fault detected: the code is stored as a pending code. No MIL yet.
• Trip two, same fault, enable criteria met again: the code matures into a confirmed/active DTC, and now the MIL is commanded on.

Why does this matter on the test and in the shop? Because a customer can come in with a pending code and no lamp, and that's normal system behavior — not a sign the bulb is burned out. The pending-to-confirmed process requires two trips where the enable criteria are actually met, not just two key cycles.

How a Code (and the Lamp) Goes Away

Once the MIL is lit, it doesn't take a repair to turn it off — it takes the monitor passing on its own.

• If the fault doesn't come back for three consecutive good trips — meaning three drive cycles where the monitor actually ran and passed — the MIL goes out.
• The DTC itself stays in memory even after the lamp is out. The lamp status and the stored code are two different things. A tech pulling codes weeks later can still find that history even though the light isn't on anymore.

This is a common test trap: extinguishing the MIL does not equal erasing the DTC. They're separate events with separate rules.

Permanent DTCs: The Code Nobody Can Cheat

A permanent DTC is a special category that cannot be erased by a scan tool command or by pulling the battery. The only way it clears is if the PCM's own monitor confirms, over the required number of drive cycles, that the original fault is truly gone.

Why does this category even exist? Permanent DTCs were created specifically to stop technicians from clearing codes and readiness data just to slide a vehicle through an emissions or I&M test without fixing anything. Before this existed, a tech (or a customer) could disconnect the battery right before the test, wipe the code and the readiness monitors, and pass a test on a car that still has the underlying problem. Permanent DTCs close that loophole — the fix has to actually work, and the PCM has to verify it itself.

Freeze Frame, Readiness, and the Scan Tool's Job

When a fault is first detected, the PCM grabs a freeze frame — a snapshot of engine data like RPM, load, coolant temp, fuel trims, and vehicle speed at that exact moment. This snapshot exists so a tech can try to recreate the same conditions later and actually catch the fault in action instead of guessing.

A scan tool is how you view all of this: pending codes, confirmed codes, permanent codes, freeze frame data, and monitor readiness (I/M readiness) status. Readiness status tells you whether each monitor has completed its self-test since the last time codes were cleared.

This connects directly back to the permanent DTC discussion: clearing codes or disconnecting the battery resets all the non-permanent readiness monitors back to "not ready." In areas where the emissions test checks readiness status, that means the vehicle has to run through the applicable drive cycles all over again before it can even be tested. So a tech who clears codes right before sending a car for inspection may actually make it fail — not for a DTC, but for incomplete readiness.

Easy to Mix Up

• Pending vs. confirmed DTC — pending is trip one, no MIL. Confirmed is trip two (same fault, criteria met again), MIL on. Don't confuse "code stored" with "lamp lit."
• MIL off vs. DTC erased — three good trips turns the lamp off. The code stays in the PCM's memory regardless. Turning off the light is not the same as clearing the code.
• Confirmed DTC vs. permanent DTC — a confirmed DTC clears with a scan tool or a battery disconnect. A permanent DTC clears only when the PCM's monitor verifies the fault is gone over its required drive cycles — a scan tool command does nothing to it.
• Readiness reset vs. code clearing — both happen together when you clear codes or drop the battery, but they're conceptually different: one is diagnostic history, the other is monitor test-completion status, and readiness is what the I/M test station usually cares about.

Check Yourself

Question: A customer's scan tool shows a pending DTC but the MIL is not on. Is something wrong with the lamp circuit?

No. A pending code means the fault was detected on the first trip only. The MIL isn't commanded on until the same fault is confirmed on a second trip where enable criteria are met again. No lamp at this stage is normal, expected behavior.

Question: Technician A says clearing codes with a scan tool will erase a permanent DTC. Technician B says only the PCM itself, through its own monitor confirming the fault is gone over the required drive cycles, can clear a permanent DTC. Who is right?

Technician B is right. Permanent DTCs cannot be erased by a scan tool command or by disconnecting the battery. They are designed specifically so a real repair — verified by the PCM's own monitor over the required number of trips — is the only way to clear them.

Question: A confirmed DTC has had its MIL turn off after three good trips. Does that mean the code is gone from memory, and does clearing codes affect anything besides the DTC list?

No, the code is not gone — the DTC stays stored even after the MIL goes out; only the lamp status changed. And yes, clearing codes (or disconnecting the battery) also resets all non-permanent monitor readiness statuses to "not ready," which means the vehicle must complete its drive cycles again before it can pass an emissions test in areas that check readiness.