Check Engine Light: Free Code Read or Factory Scan? What It Costs

When the check engine light comes on, the engine control module has stored at least one diagnostic trouble code. A parts store will plug a handheld reader into the OBD port under your dash and show you that code for free. It takes two minutes and you leave with a slip of paper that says something like P0420 or P0455 and a one-line description.

That is a real piece of information. It tells you which system tripped the light, and it settles the fear that the engine is about to fail when the code is minor. What it does not do is tell you what broke, and the gap between those two things is where most of the money wasted on check engine lights goes.

What you are getting is the narrowest view the car offers. The reader is pulling generic powertrain codes, the ones that start with P0, from one module. Everything else the vehicle knows about itself stays behind the glass, and the description on the slip is a category, not a diagnosis.

A modern vehicle has dozens of control modules talking to each other over a network, and the engine module is only one voice. A basic code reader does not hear the rest. Here is what is left out:

• Manufacturer-specific codes. Codes starting with P1, and many codes in the B, C and U ranges, are defined by the automaker. Many generic readers either skip them or show a number with no description.
• Every other module. Transmission, ABS and stability control, airbag, body control, climate, steering and instrument cluster each keep their own fault memory. A transmission code behind a harsh shift will not appear on a reader that only talks to the engine.
• The conditions recorded with the code. When a code sets, the module saves a record of what the engine was doing at that moment. That record often says more than the code does, and most free reads do not show it.
• Live sensor behavior. How the sensors and components behave while the engine runs is what separates a failed part from a part that is reporting a problem somewhere else. A handheld reader shows a code, not the behavior behind it.
• Tests the tool can command. A factory tool can operate components on demand and run the manufacturer's own test plan for the exact code on the exact vehicle. A handheld reader cannot command anything.
• Pending and history codes. Faults that have not yet turned on the light, or that set once and cleared, are often invisible to a basic reader but visible to a full scan.

None of this means the free read is wrong. It means the free read is a headline, and the rest of the story is still in the car.

Most readers have a button that erases the code and turns the light off. It is tempting to press it and see whether the light stays off. Understand what you are actually doing: you are deleting the module's evidence, including the record of the conditions when the fault set, and resetting the monitors that let the car check itself.

If the condition that set the code is still present, the module will see it again and the light will return, sometimes within a mile and sometimes after two weeks of driving cycles. In the meantime you have lost the data that would have made diagnosis faster. A cleared code also means the readiness monitors are not set, which can matter if an emissions inspection is coming up.

Clearing a code is appropriate after a repair, to confirm the fix held. It is not a fix on its own, and a light that has been cleared several times is a harder car to diagnose than one that was left alone. If the light is on now, leave it on and bring the car in with the codes stored.

A trouble code describes what a module measured, not what broke. The gap between those two things is where money gets wasted on parts that did not need replacing.

Take the two codes on that sample slip. A catalyst efficiency code names the catalytic converter in its description, and the converter is one of the most expensive parts on the car. Yet the module is only reporting what its sensors saw. Several different problems upstream of the converter, in the exhaust, in the sensors themselves or in the way the engine is running, can produce the same reading. Replace the converter on the strength of the description and you can spend a great deal and still have the light on.

An evaporative emissions code says the fuel vapor system is not holding pressure. The possible causes range from a small seal to a valve, a hose, a canister or the filler neck, with prices that vary just as widely. A free read cannot tell you which one you have. A factory tool can test the system directly on the car, which usually settles it in one visit.

Both examples carry the same lesson. The code is the starting point of a diagnosis, not the conclusion. Buying the part named in the code description is a guess, and guesses on a modern car are expensive.

A steady check engine light with the car running normally is usually a get-it-checked-soon situation rather than a pull-over-now situation. Note how the car behaves and when the light came on, avoid long highway trips if you can, and have it scanned within a few days.

A flashing check engine light is different. On nearly every make, a flashing light means the module is detecting an active misfire severe enough to send unburned fuel into the exhaust. There it can overheat and damage the catalytic converter within a short drive. Pull over when it is safe, shut the engine off, and have the car looked at before driving it further.

Stop driving as well if the light is joined by any of these:

• A temperature warning or visible steam from under the hood.
• An oil pressure warning light.
• Loss of power, heavy shaking or stalling.
• Smoke from the exhaust or a strong fuel smell.
• A transmission that will not shift or is slipping.

If the light has come on along with a brake, ABS, airbag or traction control warning, treat the combination as urgent even if the engine feels fine. Those systems have their own modules and their own fault memory, which is exactly what a full scan reads.

A full system diagnostic at our shop uses the manufacturer's own diagnostic software, the same factory-level tools the dealer's technicians use, for every make we see, domestic, Asian and European alike. Instead of a generic reader guessing at the data, you get the tool that was written for the car.

The visit covers every module on the vehicle, not just the engine, with stored, pending and history codes from each. We review the data recorded behind the codes that matter, run the manufacturer's own tests where the fault calls for them, and work the problem through to a root cause, which is the part a code reader can never give you.

You leave with a written report listing fault codes by module, the root cause and the recommended repair, so you or your repair shop can fix the right thing once. Most diagnostics are completed the same day. If you already know the fault and just want confirmation before or after a repair, a pre or post repair scan is a smaller job with its own lower price.

Our Full System Diagnostic starts at $150. Electrical and No-Start Diagnosis, which involves more hands-on testing of wiring, grounds and power supplies, starts at $150. A Pre or Post Repair Scan starts at $150. Dealers commonly charge $150 to $300 for a comparable scan, and in return you get the same factory tools plus a written report you can hand to any shop.

Diagnostics happen at our Massachusetts shop, where the factory tools are connected and the report is produced. Bring the vehicle in, or if it will not start or is not safe to drive, have it towed. Book through our auto diagnostics page or call (617) 383-9331 for a free quote, and you will have a firm price within two hours. We see vehicles from Boston, Cambridge and the surrounding towns. If the free read left you with a code and no answer, this is the next step.