Diagnostic Strategy

What is a good step-by-step diagnostic process for a check engine light?

Verify the complaint, scan all modules and save data, check bulletins, form a plan from the codes and data, test before replacing, then repair and verify under the original conditions.

What is mode 6 data and why is it useful?

Short answer: Mode 6 shows the actual test results and limits for the computer's emissions self-tests, so you can spot a component that is close to failing before it sets a code.

Generic OBD-II service mode 6, also called on-board monitoring test results, lists the individual tests behind the readiness monitors along with the measured value and the minimum and maximum limits. Misfire counts per cylinder, catalyst efficiency, oxygen sensor response and EVAP leak test results are common examples.

Its value is in the margins. A cylinder that shows a handful of misfires per drive cycle while others show zero may not have set a code yet, but it tells you where a rough idle complaint lives. A catalyst test value that barely passes warns that a P0420 is coming.

Mode 6 is not always easy to read. Some manufacturers use test IDs and scaling that need translation, and good scan tools decode those into plain names and units. Use it after repairs too, since it shows whether tests now pass with room to spare.

Should I replace the part a code names?

Short answer: Not without testing; a code describes a failed self-test, and wiring, connectors, power or ground problems, or another system can cause it just as easily as the named part.

A code like P0113, intake air temperature circuit high, means the computer saw a voltage outside its expected range. That could be a failed sensor, but it could also be an open wire, a corroded connector pin, or a missing reference voltage. Replacing the sensor fixes only one of those possibilities.

Test the circuit before buying parts. With the sensor unplugged, check for reference voltage and ground at the connector. Back-probe with the sensor connected to see the actual signal while you wiggle the harness. A voltage drop test on the ground finds high resistance that a simple continuity check misses.

Testing takes a few minutes with a good meter and back-probe pins, and it prevents comebacks. It also gives you a clear story to tell the customer about why the part failed, or why it did not need replacing at all.

How do I diagnose an intermittent problem that will not set a code when the car is in the shop?

Use freeze frame and the customer's description to recreate the conditions, record data during the event, and wiggle-test wiring while monitoring the circuit.

Why should I check technical service bulletins before diagnosing?

Short answer: Bulletins describe known problems, updated parts and software fixes for specific vehicles, so checking them first can point straight to a proven repair and save diagnostic time.

Vehicle makers publish technical service bulletins when a pattern problem is found. A bulletin may describe the symptom, the codes, the cause, and the fix, which could be a software update, a revised part or a repair procedure.

Checking bulletins at the start of a job is quick. It can explain a complaint that does not fit normal diagnosis and confirm whether the vehicle needs an update. Recalls and campaigns should also be checked, since they may be covered by the maker.

A bulletin is a guide, not proof of the cause; verify the vehicle matches the bulletin's conditions before applying the fix. Follow the maker's procedure and safety precautions in the bulletin.