Diagnostic Strategy

After clearing fault codes, or after a battery disconnection, the warning light may go off but the vehicle will fail an emissions inspection until its readiness monitors have run to completion. “Not ready” or “incomplete” readiness monitors are one of the most common reasons a vehicle is turned away at an emissions test station. Understanding […]

Continue Reading  

If your scan tool displays a DTC with a colon and two hex digits — P0130:11, U0121:87, C1234:2F — those extra characters are the failure type byte (FTB). They appear alongside the base DTC code and tell you exactly what kind of fault the module detected on that circuit or function. Understanding the FTB turns […]

Continue Reading  

The steering angle sensor calibration step is one of the most commonly skipped post-repair procedures in a workshop — and one of the most consequential. A correctly installed steering angle sensor that has not been calibrated will set stability control faults, disable traction and stability systems, and on modern vehicles with ADAS features, prevent lane […]

Continue Reading  

Intermittent faults defeat most technicians because the car won’t misbehave on command. The fix isn’t better luck — it’s a systematic approach to capturing evidence when the fault happens and recreating it when it doesn’t. Why intermittent faults are different A permanent fault is a debugging problem. An intermittent fault is a physics problem: something […]

Continue Reading  

A full page of fault codes is one of the most daunting things a scan tool can show you — and one of the most misdiagnosed. The instinct is to work through the list top to bottom, replacing or testing components one by one until the codes stop coming back. That approach fails because most […]

Continue Reading  

When a warning light comes on, most people — and many technicians — go straight to the code. The code names a sensor or circuit, and the temptation is to treat that as the diagnosis. It isn’t. A DTC tells you what a control module measured and found out of range. It does not tell […]

Continue Reading  

Freeze frame data is a snapshot of exactly what the engine and vehicle were doing the moment a fault code was stored. Most people glance at it, note the code name, and start testing at idle in the driveway — which is exactly the wrong approach if the fault set at 65 mph under heavy […]

Continue Reading  

Replacing a part based on a code description feels like a logical move — the code says “O2 sensor circuit low,” you buy an O2 sensor, you fit it, the code comes back. You’ve spent money, wasted time, and you’re no closer to the actual fault. This pattern is so common it has a name: […]

Continue Reading