Readiness Monitors: Why a Car With No Codes Can Still Fail Inspection

The monitors split into two groups, and the distinction explains almost everything about how long readiness takes.

Continuous monitors run whenever the engine is running and their enabling conditions are met. There are three:

• Misfire — watches crankshaft speed variation for combustion events that did not happen.
• Fuel system — watches whether fuel trim stays within acceptable limits.
• Comprehensive components (CCM) — watches electrical circuits and rationality of sensors and actuators that affect emissions but aren't covered by a dedicated monitor.

These generally show ready very quickly after a reset because the conditions to run them are simply "engine running."

Non-continuous monitors run only when a specific set of conditions is satisfied, and then usually once per drive cycle. Which of these your vehicle supports depends on how it is built:

• Catalyst
• Heated catalyst (only on vehicles with one)
• Evaporative emission system (EVAP)
• Secondary air injection (only where fitted)
• Oxygen sensor
• Oxygen sensor heater
• EGR and/or VVT system
• On diesels: NMHC catalyst, NOx aftertreatment, boost pressure, exhaust gas sensor, particulate filter

A gasoline vehicle with no secondary air injection reports that monitor as "not supported," which is not the same as "not ready" and is not a failure. A good scan tool distinguishes the two clearly.

A monitor is a controlled experiment. To measure whether a catalytic converter is still storing and releasing oxygen, the module needs the exhaust hot, fuel control stable in closed loop, and load steady enough that the reading is not swamped by transients. Run that test during a cold start or hard acceleration and you would get a meaningless result and a false code. So the module refuses to run it until conditions are right.

The EVAP monitor is the fussiest of the group, and the reasons are physical. It tests for leaks by manipulating pressure or vacuum in the fuel tank and watching whether it holds. That requires:

• A fuel level in a middle band — typically somewhere in the region of one-quarter to three-quarters, though the exact window is manufacturer-specific. A nearly empty or nearly full tank changes the vapor volume too much to measure against.
• Ambient and fuel temperature within a range. Extreme heat or cold changes vapor generation.
• Often a cold start, meaning the engine has been off long enough for coolant and intake air temperature to converge on ambient.
• A period of steady operation with no large throttle changes.

This is why a car can be driven for a week and have every monitor ready except EVAP. It's also why topping the tank to full right before an inspection can work against you.

Catalyst and oxygen sensor monitors typically need sustained warm operation at steady cruise. The oxygen sensor heater monitor usually completes early, since it just checks heater circuit behavior at startup.

Every readiness flag drops to not ready when:

• Diagnostic trouble codes are cleared with a scan tool
• The battery is disconnected or goes fully flat
• The powertrain module loses power or is reprogrammed

Driving to "reset the computer" before an inspection is exactly backwards — it is the clearing that caused the problem.

A drive cycle is the sequence of operation that satisfies enough enabling conditions for the monitors to run. Manufacturers publish a specific drive cycle for their vehicles, and they differ meaningfully — required speeds, durations, and cold-soak times vary by make and model. Do not trust a generic drive cycle procedure found on a forum for a vehicle it wasn't written for.

What is broadly true across vehicles:

• Start from a genuine cold soak — engine off for several hours, typically overnight, so coolant and intake air temperature are close to each other and to ambient.
• Include idle time, steady cruise at a moderate speed, and gentle acceleration and deceleration, without hard throttle or hard braking.
• Include more than one key cycle, since some monitors reference conditions at start-up.
• Expect it to take two to several days of ordinary mixed driving if you are not following a specific procedure. Highway-only or short-trip-only driving both tend to leave monitors incomplete, for opposite reasons.

If a monitor refuses to set after genuine varied driving, that itself is diagnostic information. Sometimes a monitor cannot complete because a related fault is preventing it from running, even though no light is on.

Emissions inspection programs check three things: the malfunction indicator lamp state, stored codes, and monitor readiness. A vehicle can fail on readiness alone with no codes and no light.

Allowances vary by jurisdiction and model year. A commonly used rule in US programs is that model year 1996–2000 gasoline vehicles may have up to two incomplete monitors, and 2001 and newer may have one — with EVAP frequently the one that is permitted, precisely because it is so hard to set. But this is set by the state or local program, not by the vehicle, and it does change. Check your own program's current rule rather than assuming.

Practical sequence before an inspection:

1. Scan the vehicle yourself, or have it scanned, and read readiness status. Basic readers show it; many show it as an I/M readiness screen.
2. If monitors are incomplete, do not clear anything. Drive the vehicle normally for several days, including at least one longer trip with a cold start.
3. Re-check readiness. If the same monitor still refuses, that is worth diagnosing rather than repeating.

Having a shop scan for readiness typically costs nothing to $50 as a standalone check. A DIY reader capable of showing readiness costs roughly $25 to $100.

An incomplete monitor is neutral information — it means "not yet tested," not "broken." But there is a real failure mode worth knowing.

Some monitors will not run while a related fault is present or while a related monitor has not completed, because the module knows the test would be invalid. A permanently incomplete EVAP monitor on a vehicle that is otherwise driven appropriately can mean the module is aborting the test — a purge or vent valve not responding, a fuel level sensor reading out of range so the module never believes the tank is in the valid window, or a fault flagged in a prerequisite system.

Diagnosis here is not parts replacement. It is checking whether the module reports the test as aborted, whether the enabling PIDs (fuel level, ambient temperature, intake air temperature) read plausibly, and whether the components the test commands actually respond when commanded. Only then does a specific part become a candidate, and only because a test said so.

One more caution: some tools and services claim to force readiness. Anything that sets a flag without the test having genuinely run is defeating the point of the system, and in inspection contexts it is fraud. The legitimate path is driving the vehicle until the test runs, or fixing whatever is preventing it.

Readiness explains the most confusing inspection outcome there is: no light, no codes, still failed. Knowing that clearing codes wipes readiness stops people from doing the one thing guaranteed to cause the failure, and knowing that EVAP needs a partly-full tank and a cold start turns a week of aimless driving into one deliberate trip. For a technician, monitor status after a repair is the proof the fix held — a completed monitor is the vehicle's own verification, and it beats a hopeful clear-and-return.