Idling is not the answer. Most cars need two to five complete drive cycles, roughly 50 to 200 miles of real driving, after codes are cleared or the battery comes off, and the EVAP monitor is nearly always the last one to finish.
That is the honest answer to how long does a car need to run to reset readiness monitors: there is no universal number, because the computer is counting conditions, not minutes. A 20-minute idle in the driveway might knock out one small test and do nothing at all for the catalyst, oxygen sensor, or evaporative emissions system.
Below is what each monitor actually wants from the drive, a generic cycle you can finish in about half an hour, and the handful of reasons a monitor stays incomplete no matter how many miles you put on the car.
Table of Contents
- How Long Does a Car Need to Run to Reset Readiness Monitors?
- What Are Readiness Monitors?
- Engine Runtime vs. Complete Drive Cycle
- How to Reset Readiness Monitors
- What Conditions Let Monitors Complete?
- How Long Do Different Monitor Types Take?
- What Resets Your Monitors in the First Place
- Why Readiness Monitors May Stay Incomplete
- Common Drive Cycle Mistakes
- How to Check Readiness Monitor Status
- When a Drive Cycle Is Not Enough
- Frequently Asked Questions
- Can a car reset readiness monitors by idling for 20 minutes?
- How many drive cycles are usually needed after clearing codes?
- Does disconnecting the battery reset readiness monitors?
- Why do my readiness monitors stay incomplete after a long drive?
- Should I clear codes before trying to complete a drive cycle?
- How do I know if all readiness monitors are complete?
- Conclusion
How Long Does a Car Need to Run to Reset Readiness Monitors?
Idling alone will not reset most readiness monitors. A typical vehicle needs two to five completed drive cycles, about 50 to 200 miles total, with 20 to 60 minutes of actual driving in each cycle. Engine runtime is one condition out of roughly a dozen that a monitor is checking for.
What drives the variation between one car and the next:
- Monitor design. Each manufacturer programs different enable criteria, so two cars of the same year can have completely different timing.
- What reset the monitors. A battery disconnect clears everything at once. A scan tool code clear also wipes freeze-frame data and pending codes, which can cost you a cycle.
- Fuel level and temperature. EVAP tests care about both, and EVAP is the slowest monitor on most vehicles.
- Stored fault history. If a code set on the same component recently, that monitor is inhibited until the repair verifies.
- Ambient conditions. A cold-soaked engine in cold air gives a monitor its best chance. A warm start in traffic gives it almost nothing.
The honest framing, and the one that matches how manufacturers and state inspection programs describe it: there is no universal drive cycle. Your owner’s manual or manufacturer service information is the authoritative source for your specific car. Everything below is general guidance that holds across most gasoline vehicles built since OBD-II became standard.
What Are Readiness Monitors?
Readiness monitors are self-test routines inside your car’s OBD-II emissions computer. Each one checks whether a specific piece of the emissions system is behaving correctly, and each reports one of a few statuses back to a scan tool or the dash.
The four statuses you will see:
- Ready or complete. The test ran and finished. This is what you want before an emissions test.
- Not ready or incomplete. The test either never started or was suspended before it finished. This one comes back on its own with the right driving.
- Not supported. The vehicle does not use that monitor, or the manufacturer is not required to report it. It will never show ready, and that is normal.
- Blocked or inhibited. A fault on a related component is stopping the test from running at all.
Monitors split into continuous and noncontinuous groups. Continuous monitors, the misfire and fuel system monitors on most cars, test continuously from the moment the engine starts and are usually ready within a single warm drive. Noncontinuous monitors, including catalyst, EVAP, oxygen sensor, secondary air injection and EGR or variable valve timing, only run after a defined series of conditions is met.
That distinction is why mileage alone is a poor yardstick. A long highway trip at steady speed satisfies the fuel system monitor and very little else.
Engine Runtime vs. Complete Drive Cycle
A drive cycle is a specific sequence of driving that touches every condition a monitor needs, usually beginning with a cold start and ending with a key-off period. Engine runtime is just the minutes the engine is running. Confusing the two is the single most common reason people are still not ready after a long trip.
| Elapsed time | What the car is doing | What it can actually accomplish |
|---|---|---|
| 0 to 5 minutes | Cold start, engine idling | Logs the startup values a monitor needs to see. Nothing else. |
| 5 to 15 minutes | Slow city driving with stops and accelerations | Feeds the misfire, fuel system and O2 sensor heater monitors |
| 15 to 20 minutes | Steady cruise at roughly 40 to 55 mph | Closes the loop on fuel trims, begins catalyst and O2 sensor data collection |
| 20 to 30 minutes | Coast down to a stop with the engine in closed loop, then park | Lets the catalyst and EGR monitors compare stored and incoming oxygen sensor data |
| Several hours later | Key-off soak, engine fully cold | Clears the way for the EVAP leak test on the next start |
| Next morning | Second drive, shorter city segment with a fuel level swing | Allows the EVAP monitor to complete |
You will see videos online claiming that five minutes above 55 mph resets everything. It does not. The catalyst monitor needs a cold start and a coast-down deceleration, and EVAP needs specific fuel level and soak conditions. Highway miles at a constant speed tick off a fraction of what is required.
Idling is the opposite case. Engine-on time with no speed, no load change and no deceleration gives the computer almost nothing to record, which is why a driveway idling session can easily end with every noncontinuous monitor still incomplete.
How to Reset Readiness Monitors
Use the vehicle’s prescribed drive cycle, then confirm the result with a scan tool. Do not skip the verification step, and do not clear codes right before a test.
- Check for trouble codes first. Read stored, pending and permanent codes before you drive. A pending code on an emissions component will block that monitor until it is resolved.
- Look at the physical basics. Confirm the battery is fully charged and the terminals are clean, the oil is at level, and there are no obvious exhaust leaks near the catalytic converter or the EVAP system.
- Set the fuel level correctly. Aim for between a quarter and three quarters of a tank. A tank topped to the brim can inhibit the EVAP test on some vehicles.
- Start the cycle with a cold engine. Let the car sit overnight, or at minimum for several hours, so the coolant and intake air temperature have dropped to ambient.
- Run a mixed drive. About 10 minutes of stop-and-go city driving, then 15 to 20 minutes at steady highway speed, then a coast-down to a stop without touching the brake.
- Let the car soak. Park it for several hours, ideally overnight. The EVAP monitor usually will not run until this key-off period has passed.
- Drive a second shorter cycle. Include at least one full tank-to-quarter fuel swing if you can manage it, and end with a steady cruise and a coast-down.
- Verify before you go. Re-scan and confirm that all required monitors show ready. Do not assume. That scan is the only proof.
Disconnecting the battery is one way to reset monitors, but it is also the most destructive option. It wipes radio presets, clock, memory seats, window one-touch settings and, on many cars, throttle body and transmission adaptations. Use a scan tool code clear instead unless your manufacturer procedure calls for a disconnect, and remember that a code clear also erases the freeze-frame data you might need for diagnosis.
What Conditions Let Monitors Complete?
Monitors run on enable criteria, a checklist of conditions that must all be true within a window. The list typically includes engine coolant temperature, intake air temperature, ambient temperature, barometric pressure, fuel level, engine load, vehicle speed, engine speed, time since start, key-off time, closed-loop operation, and gear state.
Some conditions matter more than others. Steady-state cruise at a moderate load for a few minutes is what gives the catalyst monitor a stable baseline. A deceleration with the throttle closed and the engine still in closed loop is what gives it the comparison data. A fuel level swing is what the EVAP monitor watches for, because it needs to see the system sealed, then check for leaks as the pressure changes.
Suspend conditions work the other way. If you open the fuel door, fill the tank, or let the engine idle for a long period with no load, a running monitor can pause. Ambient temperature and battery voltage are also enable criteria on many vehicles, which is why a weak battery keeps monitors from starting at all.
The practical takeaway: a monitor needs a change in conditions, not a quantity of them. Repeated identical driving teaches the computer nothing new.
How Long Do Different Monitor Types Take?
Typical timing runs from a single cycle for the fastest monitors to several cycles plus a soak for the slowest. These are ranges, not guarantees, and your service information is the final word.
| Monitor | Typical drive cycles | Typical distance or time | What limits it |
|---|---|---|---|
| Misfire | 1 | 15 to 20 minutes of driving | Needs the engine running and tracking combustion under varied load |
| Fuel system | 1 to 2 | 20 to 40 minutes | Needs closed-loop operation at a steady cruise |
| O2 sensor heater | 1 | 10 to 15 minutes | Needs a cold start and the heater circuit drawing current |
| Oxygen sensor | 1 to 2 | 20 to 40 minutes | Needs closed loop plus enough time above 1,000 rpm to switch sensors |
| Catalyst efficiency | 2 to 3 | 50 to 100 miles | Needs a cold start, a cruise baseline and a coast-down comparison |
| Secondary air injection | 1 to 2 | 20 to 50 miles | Needs a cold start and a specific decel or low-speed event on many designs |
| EGR or variable valve timing | 2 to 3 | 50 to 100 miles | Needs a defined load range, often between roughly 20 and 70 percent engine load |
| EVAP | 2 to 4 | 100 to 200 miles, plus an overnight soak | Needs a specific fuel level, a key-off soak and a fuel level swing |
| Comprehensive component | 1 to 2 | 20 to 60 minutes | Checks individual input and output devices one at a time |
Why the EVAP monitor is always last
The evaporative emissions system is the slowest because it has the most conditions attached. It wants a cold soak, a key-off period of several hours, a fuel level in a specific window, and then a change in that fuel level while the system is sealed. Owners on forums consistently report EVAP as the one that never sets, and it is nearly always the fuel level or the missing soak, not a broken part.
How long the catalyst monitor takes
The catalyst monitor compares upstream and downstream oxygen sensor switching to estimate storage versus incoming efficiency, so it needs data on both sides of the catalyst. A documented case had a car drive about 200 miles with every monitor complete except the catalyst, because the driving was short trips and highway cruising with no coast-down phase. One technician-monitored drive cycle set it in a single session.
Why the oxygen sensor monitor stalls out
The oxygen sensor monitor wants the engine to warm up, enter closed loop, and then spend real time above roughly 1,000 rpm. Lots of slow city idling with light throttle will not get there. If the sensor is aged or the exhaust has a leak, the monitor can run and still report incomplete, and no amount of additional driving fixes a bad sensor.
What Resets Your Monitors in the First Place
Monitors go back to not ready whenever something wipes the memory or forces the emissions system to be re-verified. Knowing which one happened tells you how many cycles to expect.
- Battery disconnection. A dead or disconnected battery is the most complete reset there is. On most vehicles it clears stored codes, pending codes, freeze-frame data and readiness status in one move. Some cars retain data through a brief disconnect, so the reset may be partial.
- Code clear with a scan tool. This does the same reset without touching your settings, but it also erases freeze-frame and freeze-frame-adjacent data that a technician would want to see.
- An emissions repair. Replacing an oxygen sensor, catalytic converter, EVAP purge valve, EGR valve or injectors usually sets a code on that system, which blocks the matching monitor until the repair verifies.
- Module replacement or reprogramming. A new or reflashed ECM, PCM or transmission module arrives with readiness reset, and adaptation values may need to relearn on top of that.
- An extended loss of power. Several consecutive days of a weak battery can trigger a deep sleep in some modules. Treat it like a disconnect.
One thing none of these do is prove anything. Clearing a code erases the record of a fault; it does not repair the part. Readiness monitors exist precisely because that distinction matters, and a monitor that goes ready after a clear tells you the system ran, not that the underlying problem is fixed.
Why Readiness Monitors May Stay Incomplete
When a monitor refuses to set, the cause is almost always one of these:
- Battery disconnected or weak. A low voltage event can cancel a monitor mid-test. A fully dead battery during a test loses the test entirely.
- Fuel level at the wrong point. A full tank or a nearly empty one can block the EVAP test. Aim for a quarter to three quarters.
- Codes still present. A pending or stored code on the same system inhibits the monitor for that component.
- Short trips only. Ten-minute errands never reach the cruise and coast-down conditions the catalyst and EGR monitors need.
- Warm start. Starting the cycle after the car has already been driven defeats the cold-start requirement for several monitors.
- Aftermarket tire size. If your speedometer reads low, you may never reach the road speed the computer wants. Check with the vehicle speed data the scan tool reports, not the gauge.
- A failed component. A bad oxygen sensor, leaking exhaust gasket, stuck purge valve or clogged EGR passage will keep a monitor incomplete no matter how much you drive.
- Manufacturer-specific procedure. Some cars have documented drive cycles for a particular monitor, and the generic one will not satisfy it.
One last warning: clearing codes right before an emissions test resets readiness and guarantees a not-ready result. This is the most common self-inflicted failure and it is entirely avoidable.
Common Drive Cycle Mistakes
Most failed drive cycles fail quietly. The car moves, the miles add up, and nothing sets. These are the mistakes that cause it most often.
- Filling up the tank right before the drive. A topped-off fuel tank is a leading cause of a stuck EVAP monitor. Leave the tank between a quarter and three quarters full.
- Starting with a warm engine. A cycle that begins ten minutes after you drove the car to the parts store is not a cold start, and several monitors will not enable.
- Pure highway miles. Steady speed at a constant load is the one pattern the catalyst, EGR and secondary air monitors are not looking for.
- Rolling to a stop instead of braking. Coast-down deceleration with the throttle closed is a required phase. Touching the brake at the last moment ends it early.
- Running the cycle in stop-and-go traffic. The crawl and constant re-acceleration can suspend tests that need steady cruise. Run the cycle at night or on a rural road where you can hold a steady speed.
- Skipping the soak. Driving, parking for twenty minutes and driving again does nothing for EVAP. Owners who fixed it reported parking the car for eight to ten hours between the two drives.
- Believing the speedometer. With a different tire size than stock, your gauge can read low or high, and you may never reach the road speed the computer is looking for. Read actual vehicle speed from the scan tool instead.
- Clearing codes again on test day. This resets every monitor to not ready and undoes weeks of driving. It is the most common way people cause the exact failure they are trying to avoid.
How to Check Readiness Monitor Status
You can read readiness with any OBD-II scanner that shows Mode 01 PID 41 data, and most cars built in the last two decades also expose a simplified menu in the instrument cluster. Plug the scanner into the port under the dash, read stored, pending and permanent codes, then open the readiness or I/M readiness screen.
Reading the results:
| What the screen shows | What it means | What to do |
|---|---|---|
| All required monitors ready, no codes | The system ran and passed | Go to the test |
| Monitors ready, a pending code present | The monitor ran and detected a fault that has not yet confirmed | Fix it before testing. It will set a confirmed code |
| Monitors ready, a stored code present | A past or present fault, monitor result not trustworthy | Diagnose before testing |
| One or more monitors not ready, no codes | Normal after a reset. The system has not finished testing yet | Run a proper drive cycle |
| Monitors not ready and codes present | A real fault is blocking the test | Diagnose. More driving will not help |
| Monitor shows not supported | The vehicle does not use that monitor | Nothing. This is normal |
| Monitors ready, permanent code present | A fault the monitor confirmed; it cannot be erased with a scanner | The repair has not verified. Expect a failure |
Beyond the readiness list, a professional scan tool can show Mode 06 test values and freeze-frame data, which is how a monitor that is about to fail gets caught before the code sets. An inexpensive reader will not show you that.
When a Drive Cycle Is Not Enough
There are sensible thresholds for escalating from driving to diagnosing.
- After 2 to 3 full drive cycles, a healthy gas vehicle should have most required monitors ready. The catalyst and EGR monitors may still be working.
- After 5 complete cycles with the same monitor stuck, stop driving and check for codes. Something is inhibiting it.
- After 10 or more cycles with no change, the monitor is not going to set on its own. That is a diagnosis, not a patience problem.
State emissions rules vary, and the number of monitors that must be ready changes by program and by model year. Some states allow a limited allowance, commonly one readiness monitor, or apply an age or vehicle-type exemption. Others require every applicable monitor. Check your state’s current program guidance for 2026 before you go, and do not assume a rule from a forum post written years ago.
Get professional help sooner rather than later if the check engine light is flashing, the engine is overheating, you smell strong fuel, or the engine is misfiring badly. None of those are drive-cycle problems, and driving harder to set a monitor can make them worse.
One more consideration: if your car is diesel, the timing picture changes completely. Diesel particulate filter and NOx aftertreatment monitors are the slowest of all and often require their own regeneration events. A drive cycle designed for a gasoline engine will not touch them.
Frequently Asked Questions
Can a car reset readiness monitors by idling for 20 minutes?
Rarely. Idling with no speed, no load change and no deceleration gives the computer almost nothing to record, so the catalyst, oxygen sensor, EGR and EVAP monitors stay incomplete. A cold idle can clear the startup data a few quick monitors want, and a long idle with the air conditioning and defroster running may help one or two. Treat idling as preparation, not as a drive cycle.
How many drive cycles are usually needed after clearing codes?
Most gasoline vehicles need two to five completed drive cycles, roughly 50 to 200 miles, before all required monitors show ready. The misfire, fuel system and heater monitors usually come in on the first cycle. The catalyst typically needs two or three, and EVAP often needs several plus an overnight soak between drives.
Does disconnecting the battery reset readiness monitors?
Yes, on most vehicles it clears stored codes, pending codes and readiness status, though behavior varies by make and some cars keep data through a short disconnect. The cost is side effects: radio presets, clock, memory settings and throttle body adaptations are commonly lost, and adaptations then relearn over the following drive cycles, which adds time before everything reports ready again.
Why do my readiness monitors stay incomplete after a long drive?
Most often the drive did not contain the conditions the monitor needs rather than too few miles. Steady highway cruising skips the cold start, the stop-and-go accelerations and the coast-down deceleration. A warm engine at the start, a full fuel tank, a short soak, or an underlying code on that same system will also hold a monitor incomplete no matter how far you drive.
Should I clear codes before trying to complete a drive cycle?
No, not as a way to make monitors ready. Clearing codes resets readiness, so you will start from zero and the not-ready result at the test is guaranteed. Clear codes only when a repair has been made, only when your manufacturer procedure calls for it, and only after you have captured any freeze-frame data you might need. Then run a full drive cycle.
How do I know if all readiness monitors are complete?
Scan the car and open the I/M readiness or Mode 01 PID 41 screen. Every monitor your state requires should show ready or complete, with no confirmed or permanent codes present. A monitor showing not supported is normal and will never read ready. Verify a second time right before the test, since a monitor can be reset by an unhandled battery fault.
Conclusion
Start with the first action that actually moves the needle: find the drive cycle your manufacturer specifies, run it from a cold start with the fuel level between a quarter and three quarters, and include the overnight soak that EVAP requires.
Then verify with a scan tool rather than assuming. If the same monitor is still incomplete after five complete cycles, stop driving and get it diagnosed instead of adding more miles. And never treat a short idle as proof that your readiness monitors are complete.