Most technicians use maybe a fifth of what their scan tool can do. They pull codes, clear codes, and maybe watch a couple of live data lines. That is enough to find the easy faults and nowhere near enough to find the ones that pay well. Here is what the other functions actually tell you.
A code is a symptom, not a diagnosis
Start here, because everything else follows from it. A code such as a lean bank one fault does not mean a sensor is bad. It means the module saw a value outside its expected range and set a flag. The cause could be a vacuum leak, a fuel delivery problem, a contaminated sensor, an exhaust leak ahead of the sensor, or a wiring fault.
The code narrows the search area. It does not name the part. Every technician knows this in theory and plenty forget it under pressure.
Freeze frame: the conditions when the fault happened
Freeze frame is a snapshot the module captured at the moment the code set. It is the most underused screen on the tool.
Look at engine speed, load, coolant temperature, vehicle speed and fuel trim. Those five values tell you the situation you need to recreate. A fault that set at low speed, low load, on a fully warm engine is a very different problem from one that set at high load on a cold start. If you cannot reproduce the fault, freeze frame tells you how to try.
It also catches lies. If a customer reports the light comes on at highway speed but freeze frame shows the fault set at idle in a cold engine, you now know to test differently.
Fuel trim: the engine telling you what it is compensating for
Short term fuel trim shows what the module is doing right now. Long term fuel trim shows what it has learned to do over time. Read them together.
The useful technique is to watch trims at different loads. A lean condition that is worst at idle and improves as you raise engine speed points toward unmetered air — a vacuum leak that becomes proportionally smaller as airflow increases. A lean condition that gets worse under load points the other way, toward fuel delivery: a weak pump, a restricted filter, dirty injectors.
Comparing banks on a V engine narrows it further. Both banks lean suggests something common — air, fuel supply, a mass airflow reading. One bank lean suggests something on that side: an injector, an exhaust leak ahead of the sensor, a vacuum line.
Mode 6: results the module already collected
Mode 6 shows the results of the monitors the module ran, with the actual measured value and the pass or fail limits. This is where you find faults that have not yet set a code.
A misfire counter that is climbing on one cylinder but has not crossed the threshold is a misfire you can catch before the customer comes back. A catalyst monitor sitting just inside its limit is a converter that will set a code in a few thousand miles. A customer who says the light comes on sometimes and it is off when they arrive — Mode 6 often shows you exactly which monitor is struggling.
The values are usually raw and need the manufacturer definitions to interpret. It is worth the lookup.
Readiness monitors: whether the car has actually tested itself
Monitors tell you which self tests the module has completed since the last clear. This matters for two reasons.
The obvious one is emissions testing — a car with incomplete monitors will fail. The less obvious one is verification. If you repair a fault, clear codes and hand the car back with monitors incomplete, you have not confirmed your repair. You have confirmed the light is off. Running the drive cycle so the relevant monitor completes is how you know the job is done.
Bidirectional controls: stop guessing, start commanding
If your tool supports it, bidirectional control is the fastest diagnostic path available. Instead of testing whether a circuit could work, you command it and watch.
Command the fuel pump on and listen. Command a cooling fan and see whether it spins. Command an injector off one at a time and watch which one changes engine speed least. Cycle an ABS valve during a bleed. Each of these replaces a chain of inference with a direct observation.
Graphing beats numbers
Numbers scrolling on a screen hide patterns. Graph them and the pattern jumps out. A sensor that drops out for a fraction of a second is nearly invisible as a number and obvious as a line.
Graph related values together. Throttle position against engine speed against load shows you whether the module is seeing what the driver is doing. Both oxygen sensor signals on one screen show you converter activity at a glance.
Record the drive, review it in the bay
For intermittents, set the tool to record, take the road test, and review afterwards. Trying to read a screen while driving is unsafe and you will miss the event anyway. Recording lets you scroll back to the exact moment the symptom appeared and see every parameter at once.
Know what your tool cannot do
Generic scan tools read generic data. Manufacturer-specific data, module configuration and many bidirectional functions need either the factory tool or a capable aftermarket platform. Knowing which side of that line you are on stops you concluding a system is fine when your tool simply cannot see it.
The habit that matters most
Before you clear a single code, write down what was there: the codes, the freeze frame values, the fuel trims, the failed monitors. Once you clear, that information is gone and the customer will not be able to tell you what it said.
Technicians who record first and clear second find intermittent faults. Technicians who clear first come back to the same car twice.
Related reading
- Scan Tools by Tier: What to Buy at Each Stage of Your Career
- How to Read a Wiring Diagram: A Technician’s Guide
- 22 Shop Tricks Veteran Technicians Use
ARNAZ Group operates 10 Midas shops across Southeast Michigan and cross-trains technicians at every level. See our technician openings.