Why Are OBD2 Monitors Not Ready? Causes Explained

What “Not Ready” Actually Means

A readiness monitor is a self-test run by the vehicle computer for one emissions-related system, such as the catalytic converter, oxygen sensors, or evaporative emissions system. When a monitor shows “ready” or “complete,” that test has run and passed. When it shows “not ready” or “incomplete,” the test has simply not finished yet.

That distinction matters. “Not ready” is not a fault code, and it does not by itself say the system is broken. It says the computer has no completed result to report. An emissions test cannot pass a vehicle on an untested system, which is why too many incomplete monitors can cause a rejection even when the check engine light is off.

“Unsupported” is different: it means the vehicle was not built with that monitor, so driving will never make it ready, and it should not count against the car.

Continuous monitors, such as misfire and fuel system, run whenever the engine runs. Non-continuous monitors, such as catalyst, oxygen sensor, and evaporative emissions, run only when specific conditions are met, so they are the ones most often left not ready.

The Most Common Reason: The Memory Was Reset

In many cases, the answer is recent history, not a new failure. The vehicle computer stores completed monitor results in volatile memory. Lose power, clear the memory, or replace the computer, and those results are gone. The monitors must then run again from the beginning.

A disconnected, dead, or replaced battery is the classic example. The same reset happens when a scanner clears diagnostic trouble codes, when a repair shop clears codes after a repair, or when the powertrain control module is replaced or reprogrammed. A software update can have a similar effect. None of these actions damages the monitors, but all of them restart the clock.

Clearing a code just before a test usually backfires: the light may go out, but the readiness evidence goes with it, and a still-present fault may return during the drive cycles needed to restore readiness.

A weak battery or a poor power or ground connection to the computer can cause repeated resets as well. If monitors keep returning to not ready after normal driving, or if the clock, radio presets, and other memory settings also reset, power supply is worth checking before assuming a sensor has failed. The Missouri Gateway Vehicle Inspection Program readiness guidance lists battery replacement, cleared memory, power or grounding problems, unmet test requirements, and software updates among the common reasons monitors stay not completed.

The Drive Cycle Has Not Happened Yet

Even with no fault present, monitors will not complete on short, repetitive trips alone. Each non-continuous monitor has enable criteria: conditions that must be true before the computer is allowed to run the test. Until those conditions occur together, the monitor waits.

Common enable criteria include a cold start, full warm-up to normal operating temperature, steady cruising, gentle acceleration, and a period of deceleration with the throttle closed. Some tests also need a specific fuel level, a moderate outside temperature, or a period of sitting with the engine off. The exact sequence is called a drive cycle, and it varies by manufacturer, model, and monitor.

Mileage alone is therefore a poor guide: fifty stop-and-start miles may never give the catalyst monitor its steady cruise, and fifty highway miles may never give the EVAP monitor its cold-start conditions. Mixed driving over several days usually covers more of the required conditions.

The evaporative emissions, or EVAP, monitor is often the last to complete. It commonly needs a cold start after the vehicle has sat for several hours, a fuel tank that is neither nearly empty nor nearly full, and moderate ambient temperature. Extreme cold or heat, a very full or very low tank, or a recent refuelling can delay it. On some vehicles it takes several suitable cycles, not just one drive.

A Fault Is Stopping the Test From Running

Sometimes a monitor is not ready because it cannot run, not because it has not had time. A monitor may be blocked by a fault in a related system. For example, a faulty oxygen sensor can prevent the catalyst monitor from running, because the catalyst test depends on oxygen sensor data. Fixing the downstream symptom without fixing the upstream fault will not set the monitor.

Pending codes deserve attention here. A pending code means a fault was seen once but has not yet been confirmed, so the check engine light may still be off. That pending fault can still block related monitors. A scanner check that shows pending codes, even with no light, is therefore a useful clue when readiness stalls.

Other blockers include a thermostat stuck open so the engine never reaches normal temperature, a loose or damaged fuel cap or EVAP leak that prevents the EVAP test from passing its conditions, disconnected sensors, and aftermarket tuning or parts that change the computer programming or disable a monitored system. In those cases, more driving will not help until the blocker is diagnosed and repaired.

How to Tell Which Reason Applies to Your Car

Start with recent history. Ask whether the battery was disconnected, replaced, or went flat, whether codes were cleared, or whether a repair or update was done recently. If any of those happened, a reset is the most likely explanation, and the next step is suitable driving, not parts replacement.

Next, check the scanner readout monitor by monitor. Note which monitors are ready, which are not ready, and which are unsupported. If almost all non-continuous monitors are not ready, a recent reset is likely. If only one monitor is stuck while the rest have completed, look at that system and its enable criteria first.

Then check for codes, including pending codes, and for basic enable conditions: coolant temperature reaching normal, fuel level in the middle range for an EVAP test, and a cold start after the car has sat. If the engine runs cold, the fuel tank is nearly full or empty, or driving has been only short trips, those conditions may explain the delay.

Finally, if several days of mixed driving, cold starts, and steady cruising still leave a monitor unset, the cause is more likely a fault, a power problem, or a manufacturer-specific issue, and a technician should check live data and that monitor’s exact enable criteria.

What to Do Next

For most drivers, the practical order is simple: fix any known fault first, do not clear codes again, drive normally with varied conditions for several days, and recheck readiness with a scanner before booking a test. A scanner that can show readiness is useful here, because it removes the guesswork about whether the car is actually ready. That is also why a scanner check for emissions readiness is worth doing at home before a test station visit.

If time is short, look up the manufacturer drive cycle for the specific vehicle rather than guessing. A generic cycle can help, but a manufacturer cycle lists the cold start, idle time, speeds, and deceleration steps that vehicle actually needs. Follow it on a safe road, and do not try to perform precise speed or deceleration steps in traffic.

Before a test, confirm how many incomplete monitors your state allows. The general EPA-based pattern is up to two incomplete non-continuous monitors for 1996–2000 vehicles and one for 2001 and newer vehicles, but state rules and exceptions vary, so check the local program. Our guide to how many OBD2 monitors can be incomplete explains that limit in more detail, and our guide to what incomplete readiness means covers the status itself.

If a code returns during the drive cycles, stop and diagnose that code. It is not a readiness problem anymore; it is the fault the monitor was designed to find. Clearing it again will only reset readiness and delay a pass. Similarly, if a code was cleared recently and the light stays off, our guide to how long a cleared code stays gone explains why the absence of a light is not yet proof the fault is fixed.

Frequently Asked Questions

Does “not ready” mean my car has failed an emissions test?

Not necessarily. It means the computer has not completed the required self-tests, so the test cannot confirm the systems are working. A vehicle can be rejected for too many incomplete monitors even with no fault code and no check engine light.

How long after a battery disconnect will monitors be ready again?

There is no fixed time. Many vehicles need several days of mixed driving, including cold starts and steady cruising, while the EVAP monitor can take longer. Recheck with a scanner rather than relying on days or miles alone.

Will driving 50 to 100 miles set all the monitors?

Mileage helps only if the driving includes the conditions each monitor needs. Short trips, a cold engine, or a fuel level outside the EVAP range can leave monitors incomplete even after 100 miles, while varied driving can set them sooner.

Why is the EVAP monitor usually the last one to complete?

The EVAP test often needs a cold start after a soak period, a moderate fuel level, and moderate temperature. If any of those conditions are missing, the computer postpones the test, so it commonly finishes after the other monitors.

Can I pass with one monitor not ready?

Often, yes, for 2001 and newer vehicles, if it is a non-continuous monitor and your state follows the usual EPA-based allowance. Older vehicles may be allowed two. Check your state program, because exceptions and specific monitor rules apply.

Should I disconnect the battery to clear a code before a test?

No. Disconnecting the battery clears codes but also resets all readiness monitors to not ready. That makes a test rejection more likely, not less, and it does not fix the fault behind the code.

Conclusion

Monitors are most often not ready because they were reset, because the right driving conditions have not happened yet, or because a fault is blocking the test. Check battery and code-clearing history first, then which monitors are stuck and whether their conditions have been met. Fix a returning fault, avoid clearing codes again, drive with varied conditions, and verify readiness before the test.