📍 Main Guide: Best OBD2 Scanners (Researched and Compared). See our full researched comparison of the top picks.

If your check engine light is on and your emissions test is coming up, you might be tempted to plug in an OBD2 scanner, clear the codes, and hope the light stays off long enough to pass. It seems logical on the surface. No light, no problem. But in practice, this approach almost always backfires, and understanding why can save you a wasted trip to the inspection station and a failing sticker.

Every modern vehicle equipped with an OBD2 port (all cars and light trucks sold in the US from 1996 onward) runs a set of internal self-tests called readiness monitors. These monitors tell the emissions inspector far more than the check engine light alone. Clearing your codes resets those monitors to an incomplete state, which is itself a reason to fail in most states, regardless of whether any fault codes are present. This guide explains how the system works, what inspectors actually check, and the right steps to take when your car has codes before a test.

What Emissions Tests Actually Check

State emissions programs in the US vary by state, but the majority of modern I/M (Inspection and Maintenance) programs use an OBD2 plug-in test. The inspector connects a scan tool to your vehicle’s OBD2 port, typically located under the dashboard on the driver’s side, and reads three things:

  • MIL status: Whether the malfunction indicator lamp (the check engine light) is commanded on by the vehicle’s computer. A commanded-on MIL is an automatic failure in virtually every OBD2-based program.
  • Stored fault codes (DTCs): Diagnostic trouble codes that triggered the MIL. Inspectors in most states record these, though in some programs the MIL status alone is what triggers failure, not the code itself.
  • Readiness monitor status: This is the part most drivers overlook. The OBD2 system includes a series of self-tests, typically between 8 and 11 depending on the vehicle and fuel type, that the car’s computer runs during normal driving. Each monitor must report as either complete (ready) or not applicable. If too many report as incomplete (also called not ready), the vehicle fails, even with no active codes and no check engine light.

The EPA’s OBD2 regulations, which underpin most state I/M programs, are documented in 40 CFR Part 86 and related guidance. States that receive federal highway funding are generally required to run programs meeting EPA standards, though the specific pass/fail thresholds for incomplete monitors vary by state and model year.

Why Clearing Codes Causes Monitor Failures

When you clear codes using an OBD2 scanner, or when a shop disconnects and reconnects the battery, the vehicle’s powertrain control module (PCM) resets all stored diagnostic information. This includes the fault codes themselves, the freeze frame data captured when a fault occurred, and critically, the readiness monitor completion status. Every monitor goes back to incomplete.

The vehicle then has to re-run each self-test during real driving before those monitors will return to complete status. Some monitors complete quickly. The misfire monitor and fuel system monitor are continuous monitors, meaning they run constantly and will usually show ready within a short drive. Others are non-continuous monitors and require specific drive cycle conditions to complete:

  • Catalyst monitor: Checks whether the catalytic converter is functioning within spec. Requires a highway-speed cruise followed by deceleration, typically taking 20 to 40 minutes of varied driving.
  • Oxygen sensor monitor: Tests upstream and downstream O2 sensors. Also requires a mix of idle, city, and highway driving.
  • EVAP monitor: Checks the evaporative emissions system for leaks. This one is notoriously slow to complete and is sensitive to fuel level (most vehicles want the tank between one-quarter and three-quarters full) and cold start conditions.
  • EGR monitor: Tests exhaust gas recirculation, when equipped. Requires specific load and RPM conditions.

If you clear codes today and take your car for inspection tomorrow, there is a very high probability that several non-continuous monitors will still show incomplete, resulting in a fail for insufficient readiness, not because of any actual emissions fault.

State Rules on Incomplete Monitors

Every OBD2-based state program sets a threshold for how many incomplete monitors are acceptable. These thresholds are generally based on EPA guidance and model year:

  • 1996 to 2000 model year vehicles: Most states allow up to two incomplete monitors (excluding EVAP, which is sometimes treated separately in older programs).
  • 2001 and newer model year vehicles: Most states allow only one incomplete monitor. Some states allow zero incomplete monitors.
  • EVAP-specific rules: Some states, particularly those with Enhanced I/M programs, treat an incomplete EVAP monitor as an automatic failure regardless of model year, because EVAP is one of the highest-impact monitors for hydrocarbon emissions.

States with OBD2 I/M programs include California, New York, Texas, Florida, Illinois, Pennsylvania, Ohio, Michigan, Colorado, Virginia, and dozens of others. A handful of states, mostly rural or sparsely populated, still run tailpipe sniff tests or no emissions program at all. You should confirm the exact rules for your state through your state DMV or Department of Environmental Quality, since threshold rules can change when a state updates its I/M program.

The short version: if you cleared codes within the past few days, there is a strong chance you will fail on incomplete monitors alone, before the inspector even looks at whether there is an active fault.

The Drive Cycle: How to Get Monitors Ready

If your codes were cleared, either by you or by a shop, your only real option before testing is to complete a drive cycle that allows the monitors to run to completion. There is no shortcut, and you cannot manually trigger the monitors by holding down buttons or using a scan tool in most vehicles.

The generic EPA drive cycle, which covers most vehicles, follows these general steps:

  • Start with a cold start (engine coolant below 86 degrees Fahrenheit and within 11 degrees of ambient air temperature). This usually means the car has been sitting overnight.
  • Idle for two to three minutes after startup to allow the oxygen sensor to warm up.
  • Accelerate moderately to 55 mph and hold that speed for three minutes. This allows the catalyst monitor to run.
  • Decelerate without using the brakes to below 20 mph. This triggers the fuel cut-off portion of the catalyst test.
  • Accelerate again to 60 to 65 mph and hold for five minutes. This completes the O2 sensor test.
  • Decelerate naturally again to a stop.
  • Perform a series of city driving cycles at 25 to 45 mph with gradual acceleration and deceleration.

After completing a cycle like this, connect an OBD2 scanner and check the readiness monitor status before heading to the inspection station. Most scan tools display this as a list showing ready or not ready (or complete/incomplete) for each monitor. Only go in for testing once all applicable monitors show ready. If the EVAP monitor is still incomplete, adjust your fuel level to the midpoint range and try another cold-start cycle the next morning.

Vehicle-specific drive cycles exist for many makes and models and are often more efficient than the generic EPA cycle. Your vehicle’s factory service manual, or the manufacturer’s technical service bulletins (TSBs), may include a specific drive cycle designed to complete all monitors in a single trip.

What to Do When You Have an Actual Code

If your check engine light is on because of a genuine fault, clearing the code is not a solution, it is a delay. The underlying problem that triggered the code will almost certainly trigger it again within the drive cycle needed to complete your readiness monitors. You will end up right back where you started, with an active code and potentially a more expensive repair after the issue has had more time to develop.

The correct approach when a code is present before an emissions test is to diagnose and repair the fault first, then verify the repair is complete, then allow the drive cycle to confirm it. Here is a practical sequence:

  • Read the code before clearing anything. An OBD2 scanner will show you the DTC. Common emissions-related codes include P0420 (catalyst efficiency below threshold), P0442 or P0455 (EVAP leaks), P0171 or P0174 (fuel system lean), and P0300-series (misfires). Record the code, freeze frame data, and any pending codes before touching the clear button.
  • Research the code or take it to a shop. A code like P0420 can have multiple causes, from a failing catalytic converter to an exhaust leak near the O2 sensor to a contaminated sensor. Replacing parts without diagnosis is expensive and may not fix the root problem.
  • Repair the fault. Once you know what failed, fix it. For repairs under certain thresholds, many states offer a waiver program if you have spent enough on repairs and the vehicle still cannot pass. Check your state program for the specific repair cost threshold and waiver eligibility rules.
  • Clear codes only after the repair. Once the repair is done, clearing the code and running the drive cycle confirms that the fix actually worked. If the code comes back during the drive cycle, the repair is incomplete.
  • Confirm monitors are complete before testing. Check readiness status with your scanner one more time right before going in. If all applicable monitors show ready and no MIL is commanded on, you are in a good position to pass.

Emissions Waivers and Repair Cost Limits

If your vehicle genuinely cannot pass emissions due to a costly repair, most states with Enhanced I/M programs offer a waiver that allows registration even with a failing vehicle, provided the owner has made a good-faith repair effort above a minimum cost threshold. These thresholds are set by the state and reviewed periodically. Common examples include minimum repair expenditures in the range of several hundred dollars, though the exact amounts differ by state and model year.

To qualify for a waiver you typically need:

  • Receipts from a licensed repair facility showing the work performed and total cost.
  • Proof that the repairs were directed at the emissions failure cause (not unrelated work).
  • A re-test showing the vehicle still fails after the repair.

Waivers are usually good for one registration cycle, not permanently. The vehicle will need to pass legitimately in subsequent years, or qualify again. Contact your state’s DMV or motor vehicle inspection program directly to get current waiver amounts and documentation requirements, as they can change year to year.

Low-income assistance programs also exist in some states. California’s Consumer Assistance Program (CAP), for example, offers subsidized repairs or vehicle retirement buy-back options for qualifying residents whose vehicles fail emissions.

Using an OBD2 Scanner to Prepare for an Emissions Test

Owning an OBD2 scanner is one of the most practical steps a driver can take to avoid a surprise emissions failure. Before scheduling your inspection, you can use a scanner at home to check exactly what the inspection station will see:

  • Check MIL status: Confirm the check engine light is not commanded on. This is different from whether the light is illuminated on the dashboard. A scanner will show the ECU-commanded state directly.
  • Read active and pending codes: Pending codes have not yet triggered the MIL but are close. They will not cause a fail today but may before the monitors complete, so they are worth addressing.
  • Review readiness monitors: The monitor status screen (sometimes labeled I/M Readiness or OBD Monitor Status) shows complete, incomplete, or not supported for each system. Not supported simply means that monitor does not apply to your vehicle or fuel type. Only incomplete monitors count against you.
  • Check freeze frame data: If a code was recently cleared, freeze frame data may already be gone, but if you have an active code, freeze frame shows the engine conditions at the moment the fault was detected, which helps with diagnosis.

You do not need a professional shop-grade scanner for this. Most entry-level OBD2 readers display live readiness monitor status and DTCs. Some Bluetooth adapters paired with a phone app can also read this information, though app quality varies. The key feature to confirm before buying is explicit readiness monitor display, since not all budget tools show this clearly.

Frequently Asked Questions

Will clearing check engine codes help me pass an emissions test?

Almost never. Clearing codes resets your OBD2 readiness monitors to incomplete, and most states will fail a vehicle for having too many incomplete monitors, even if there is no active fault code and the check engine light is off. You would then need to complete a full drive cycle before retesting. If there is an actual underlying fault, the code will typically return during the drive cycle anyway, leaving you in the same position. The right approach is to diagnose and fix the fault that triggered the code in the first place.

How long do I need to drive after clearing codes before an emissions test?

There is no fixed time or mileage, because readiness monitors complete based on specific driving conditions, not elapsed time or distance. Simple monitors like misfire and fuel system can complete within minutes of normal driving. More demanding ones like the catalyst monitor and EVAP monitor can take one to several full drive cycles, often including a cold start, highway cruise, deceleration, and city driving. For most vehicles, plan on at least one to two complete cold-start drive cycles over two or three days of mixed driving before all monitors show complete. Use an OBD2 scanner to verify readiness status before going in for your test.

What happens if my car has an incomplete EVAP monitor at the inspection?

In most Enhanced I/M states, an incomplete EVAP monitor will cause a failure, either because it counts against the incomplete monitor limit (usually one allowed for 2001-and-newer vehicles) or because the state treats EVAP as a mandatory-complete monitor. The EVAP monitor is one of the slowest to complete because it requires specific cold-start and fuel level conditions. Make sure your fuel tank is between one-quarter and three-quarters full, avoid topping off the tank (which can saturate the charcoal canister), and allow the car to sit cold overnight before the next drive cycle attempt. Check with your state’s I/M program for specific EVAP rules.

Can a shop clear codes right before inspection to make my car pass?

A shop can clear codes, but this does not guarantee a pass and in most cases simply delays the inevitable. Any competent shop should warn you that clearing codes resets readiness monitors, which will cause a failure for insufficient readiness if you test too soon. Some unethical shops have been known to clear codes and send customers directly to inspection hoping the monitors stay incomplete long enough to sneak through, but this is deceptive and rarely works with modern programs. If a shop suggests clearing codes as a solution to an emissions failure, treat that as a red flag and seek a second opinion.

What is the difference between a pending code and an active code for emissions purposes?

An active (confirmed) fault code is one that has triggered the malfunction indicator lamp. This is a guaranteed fail at emissions. A pending code is a fault that the OBD2 system has detected but has not yet confirmed through a second consecutive detection event, so the check engine light has not turned on yet. Pending codes do not cause an emissions failure on their own in most state programs, but they are a warning sign. If you drive through a monitor completion cycle with a pending code present, that code may confirm and illuminate the MIL before you reach the inspection station. Pending codes are worth diagnosing before your test even though they are not an immediate failure trigger.

The Bottom Line

The bottom line is that clearing check engine codes before an emissions test is a strategy that almost always backfires, because modern OBD2 programs test readiness monitor completion, not just the check engine light. If you have a code, diagnose and repair the fault, allow the monitors to complete through a proper drive cycle, confirm readiness with your own scanner, and then go in for testing. That sequence gives you a legitimate pass and avoids the cost and hassle of multiple failed inspection trips.

Related Guides