Diagnostics & Drivability (OBD-II)
Read the codes. Fix the actual problem.
Diagnostics & Drivability is the highest-leverage credential in modern automotive work. This certification proves you can systematically diagnose drivability problems using OBD-II tools, scope patterns, fuel trim analysis, and lab scopes. Everything below is free β no login, no paywall. Work through the skill areas, drill them in Study Mode, and when you're ready, prove it with the certification exam.
Your readiness to certify
Drill all 60 concepts in Study Mode. Mark each one βGot itβ once you know it cold. When every concept is cleared, you're ready for the DIA exam.
What you'll be able to do
- OBD-II mode operation, generic vs. enhanced PIDs
- Fuel trim analysis (short and long term)
- Misfire diagnosis (mechanical, ignition, fuel, and injection sources)
- Oxygen sensor and wideband A/F sensor operation
- MAF, MAP, TP, and other input sensor diagnostics
- CAN bus fundamentals and network diagnostics
- Lab scope waveforms: injector, coil, alternator, secondary ignition
- Systematic drivability diagnostic flow
Skill areas
Jump to any area β each one distills the concepts you need to master it.
OBD-II Modes
8 concepts- Mode $02 (freeze frame) captures RPM, load, coolant temp, fuel trims, and other parameters at the exact moment a code was set. This is invaluable for reproducing the failure condition during diagnosis β the vehicle tells you WHERE it was operating when it failed.
- Generic OBD-II is the legally-mandated subset (mostly emissions). Enhanced data (accessed via manufacturer-specific protocols or advanced scan tools) reveals transmission, chassis, body, and thousands more manufacturer parameters. Diagnosing modern vehicles beyond emissions requires enhanced scan tool access.
- OBD-II monitors run automatically when specific drive conditions are met. Readiness status shows whether they've completed since the last code clear or battery disconnect. Failed emissions test may reflect not-ready monitors, not actual failures. Many states require monitors to be 'ready' before an emissions test.
- Small EVAP leaks are hard to find without a smoke machine. Gas cap is a first check (loose or bad gasket). Then smoke pressurizes the system to find visible smoke escape. Purge and vent valves, canister, hoses, and fuel tank connections are all common leak points. Some vehicles have specific TSBs for common leak locations.
- OBD-II requires most codes to occur on two consecutive drive cycles before triggering the check engine light and being 'confirmed'. Pending codes are early warnings β useful for catching intermittent issues before they trigger a full code. Some scan tools show them as 'monitor status' or 'pending DTCs'.
- Mode $06 exposes the raw test data OBD-II monitors use. For example, catalyst efficiency ratios, misfire counts per 200 revolutions, EVAP leak test pressures. When a monitor is 'not ready' or a code is intermittent, Mode $06 shows the underlying values β enabling pinpoint diagnosis.
- After clearing codes, monitor readiness resets to 'not ready'. Specific drive conditions (varying speeds, temperatures, cruise times) are required to run each monitor. If a monitor isn't run, states won't pass the vehicle. Manufacturer service data specifies each vehicle's drive cycle.
- P0420 sets when catalyst efficiency drops below spec. Mode $06 shows the actual ratio measured. A rating of 0.05 (barely above 0.02 threshold, for example) means the cat is on its way out. A rating deep in fail range (like 0.001) means completely failed. This detail informs the repair discussion.
Fuel Trims
8 concepts- STFT responds instantly to O2 sensor input. Positive values mean the ECU adds fuel because sensors detect lean. Negative values mean it subtracts fuel because sensors detect rich. Sustained values above Β±10% suggest a real issue that will eventually set a fuel trim code (P0171/P0172).
- Vacuum leaks introduce a fixed amount of unmetered air. At idle (low total flow), this is a large percentage β big trim correction. At cruise (high flow), same leak is a small percentage β small correction. Load-dependent fuel trim behavior is the fingerprint of a vacuum leak.
- Negative trims mean the ECU is subtracting fuel to compensate for something adding it. Common causes: leaky injector (adds fuel at rest), high fuel pressure (regulator failure), saturated EVAP canister (adds hydrocarbons via purge), or MAF reading air higher than actual (ECU adds fuel for phantom air).
- Fuel trims should be similar between banks. Split trims indicate a bank-specific problem: injector leak on the negative bank, vacuum leak on the positive bank, or O2 sensor error. Bank 1 = cylinder 1's bank. Bank 2 = opposite bank. Verify manufacturer's bank designations.
- Vacuum leaks cause higher trims at idle, dropping at cruise. The opposite pattern (small at idle, larger at cruise) points to MAF issues β the sensor is under-reporting more at higher airflows, requiring the ECU to add more fuel. MAF cleaning or replacement is warranted.
- Fuel trims should adjust smoothly. Erratic swings mean unstable input. Failing O2 sensors send erratic voltage. Bad grounds cause voltage reference errors. Poor connectors cause intermittent readings. Scan tool history and O2 waveforms narrow the specific cause.
- OBD-II fuel trims average over time. Brief transient events (a stumble on tip-in) may not affect long-term averages but are noticeable to the driver. Scope-level tools (injector waveform, wideband O2 during acceleration) capture these transients. Common causes: accelerator pump equivalent function, sudden vacuum leak change, throttle body issues.
- Asymmetric trims are diagnostic gold. The high-trim bank is being under-fueled β vacuum leak specific to that bank's runners, or fuel supply issue. The other bank running normally proves the shared fuel system upstream is functional. Systematic testing of that bank's intake runners and injectors narrows it down.
Misfire
8 concepts- Swap-testing is the fastest way to identify component vs. cylinder issue. If the misfire moves with the swapped component, that's the failure. If it stays on cylinder 1 after all swaps, the problem is inside the cylinder (compression, valve, injector wiring, mechanical) β deeper investigation needed.
- Under load, cylinder pressures rise, requiring higher voltage to ionize the spark gap. Weak coils or worn plugs that work at idle can't perform. Similarly, fuel pressure that's marginal at idle can drop unacceptably under high demand. Lean conditions (vacuum leaks, dirty MAF) worsen under load.
- The crankshaft position sensor is precise enough to measure each cylinder's contribution. A firing cylinder accelerates the crank slightly; a misfire fails to. The ECU counts these events per 200-1000 revolutions. Enough misses trigger P0301-P0308 (specific cylinder) or P0300 (random) codes.
- After ruling out compression, spark, and fuel, the remaining causes are mechanical (bent cam lobe, weak valve spring) or electrical (harness damage, PCM injector/coil driver failure). Cracked spark plug insulators arc internally β invisible without a scope. These are the harder-to-find causes that separate expert diagnosticians.
- Cold-only misfires are often materials expanding to seal what was leaking cold (spark plug cracks) or components with adequate performance hot but marginal cold (weak coils, dirty injectors). Cracks in coil boots let spark leak to ground in cold moisture. Systematic testing at cold identifies the culprit.
- OBD-II categorizes misfires by severity. Type A (flashing CEL) means catalyst-damaging levels β stop driving. Type B (steady CEL) is emissions-relevant. Type C is less severe. The flashing CEL is your fastest visual cue that immediate stop is warranted.
- Modern misfire monitors detect events well below what a driver feels. A stored P0301 with no felt symptom still requires investigation β the trend usually worsens. Ignoring can lead to catalyst damage (a much more expensive repair) and eventual full failure. Diagnose while it's still cheap.
- With spark and fuel confirmed, mechanical causes remain: compression, valve sealing, ring health. Cracked coils or wet spark plug wells cause the spark to bypass the plug β visually check plug wells, spray water on components during misfire to isolate. Bent valves from prior timing events cause specific-cylinder misfire.
O2 Sensors
7 concepts- Traditional narrow-band O2 sensors output low voltage (~0.1V) when the exhaust is lean and high voltage (~0.9V) when rich. The rapid switching around 0.45V (crossover) indicates a healthy sensor. Slow response or stuck values indicate sensor failure or a lean/rich condition.
- Traditional O2 sensors only tell rich vs. lean around stoichiometric. Widebands (also called AFR sensors) measure the exact ratio, which is essential for lean-burn engines, direct injection, and diesel. They use a pump cell and Nernst cell β more complex, but far more informative for tuning and diagnostics.
- A healthy catalyst stores and releases oxygen, buffering the rapid switching from upstream sensors. Downstream voltage should be relatively steady around 0.6-0.7V. When downstream mirrors upstream, the cat has failed. But before condemning it, rule out: bad O2 sensors, exhaust leaks, misfires, or fuel system issues.
- A DMM in min/max mode captures the range. A lab scope reveals timing, rise/fall speed, and any anomalies invisible to a DMM. Slow switching, limited range (stuck lean or rich), or flat response indicate a failing sensor. Scan tool data is helpful but slower response than direct scope readings.
- Zirconia sensors require ~600Β°F+ to generate voltage. Cold start emissions are elevated during this warm-up because the ECU operates in open-loop (no O2 feedback). Modern heated sensors reach operating temp in ~30 seconds. Failed heater circuit codes (like P0135) mean warm-up is delayed.
- P0135 says the ECU's heater monitor detected an issue. Could be the sensor's internal heater (open element), wiring (broken), fuse, or relay. Voltage at connector proves power supply; resistance across heater pins verifies the element. Replacing the sensor without checking wiring often results in return visits.
- O2 sensors report what they read. A sensor showing 'always rich' might actually be reading a real over-fueling condition. Similarly, 'always lean' can be reading a real vacuum leak or exhaust leak that dilutes exhaust with atmospheric oxygen. Rule out actual causes before condemning the sensor.
Input Sensors
7 concepts- MAF sensors report airflow in g/s. Rough rule of thumb: idle MAF β engine displacement in liters. A 2.0L engine should show ~2 g/s at idle. Deviations indicate contamination (MAF cleaner), physical damage, or wiring problems. Compare to expected from manufacturer or reference vehicles.
- MAP sensors output a voltage or frequency proportional to manifold pressure. Key on, engine off = atmospheric (highest signal). Idle = high vacuum = lowest signal. Applying a hand vacuum pump directly to the sensor and watching the signal change is the definitive test.
- TPS should provide a smooth voltage sweep. Sudden drops to 0V or spikes indicate worn resistive tracks (in potentiometer-type sensors) or bad segments. Modern Hall-effect and non-contact TPS designs fail differently β often with sudden 'off' or stuck values. Scan tool data or scope reveals the fault.
- CKP is the master timing reference. Without it, the ECU can't determine crank position and won't fire injectors or ignition. Complete failure = no start. Intermittent failure = intermittent stalling. Test by scoping the signal while cranking β no signal or noisy signal = sensor or tone ring problem.
- Coolant temperature sensors are typically thermistors β resistance changes with temp. Open circuit (broken wire, failed sensor) reports as maximum resistance, which translates to -40Β°F or the low end of the ECU's scale. Short circuit reports as maximum temp. Both need repair β the ECU makes fueling decisions from this signal.
- Intermittent no-stall stalls require capturing data during the event. Modern scan tools with graphing/recording can save extended sessions. When the stall occurs, review what changed β did RPM drop suddenly? Did a sensor value spike? Did fuel pressure collapse? The captured data reveals the root cause pattern.
- P0102 says the ECU sees the MAF signal below expected. Causes: MAF contamination (dirty hot-wire element under-reads), bad MAF, MAF wiring issues, or intake air leaks bypassing the MAF (unmetered air lowers apparent MAF reading relative to actual airflow). Systematic testing rules out cheaper causes first.
CAN Bus
6 concepts- CAN bus (Controller Area Network) is the primary data network in modern vehicles. Modules broadcast data (RPM, coolant temp, speed, etc.) on a shared bus. This eliminates individual wiring for every signal β every module sees every message and responds to relevant ones. Bus faults affect multiple modules simultaneously.
- Multiple modules failing simultaneously points to shared infrastructure: power/ground (common issues), CAN bus wires (shorts, breaks), or terminating resistors. Between CAN-H and CAN-L, you should read ~60 ohms (two 120-ohm terminators in parallel). Bad terminator = communication failure across the bus.
- CAN uses differential signaling β CAN-H and CAN-L are mirror images. A healthy scope pattern shows this mirroring. Common faults: one wire shorted to power/ground shows a stuck line, damaged twist shows asymmetric noise, bus errors show corrupted patterns. Scope diagnosis is essential for intermittent CAN issues.
- 'No comm' means the module isn't responding to the diagnostic tool's queries. First rule out easy causes: power, ground, connector integrity, CAN bus reaching the module. If all inputs are good and the module is truly not responding, it may be internally failed β but only after confirming all supporting infrastructure.
- The CAN bus is precision-engineered. Adding devices that broadcast improperly, or physically altering the bus wiring, causes network faults that can be difficult to trace. Always use manufacturer-approved installation methods. If custom CAN integration is needed, use certified aftermarket CAN gateways designed for the vehicle.
- Modern vehicles have multiple CAN networks β high-speed for critical systems (powertrain, ABS), low-speed for body electronics, and separate buses for infotainment. Gateway modules bridge these while filtering messages for security and rate limiting. Diagnostic tools often connect through the gateway, which affects what data is accessible.
Scope Waveforms
7 concepts- Scan tools poll data at variable rates (often 5-20 times/second). A scope shows continuous voltage β capturing microsecond-level events, waveform shape, timing between events, and noise/anomalies. Injector waveforms, coil primary, secondary ignition, and O2 switching are best diagnosed with a scope.
- Injector waveforms show the ECU-controlled pulse width, the inductive spike (~30-60V) when current is cut, and β with current probe β the actual coil current profile. Sticking injectors, partial opening, worn returns, and PCM driver problems all show characteristic waveform anomalies.
- Firing line is the initial spike required to jump the plug gap. Under load or with worn plugs it climbs. Very high firing lines (25+ kV) indicate excessively worn plugs, high resistance in wires/coils, or lean mixtures. Wide variations between cylinders point to specific-cylinder issues.
- Normal coil primary shows 12V during dwell buildup, then drops to near-0V during triggering. Stuck-high means no triggering β usually a wiring issue between PCM and coil, or PCM driver failure. Stuck-low means the coil is being held on continuously (rare, usually PCM issue) β will overheat and destroy the coil.
- Cranking current tells multiple stories. High draw = worn starter or high engine drag. Rhythmic peaks correspond to compression strokes β variance reveals compression differences. Voltage drop during cranking reveals battery capacity. All in one 15-second scope capture without disassembly.
- Amp clamp on the battery cable during cranking reveals current draw β a spec is typically 150-250A for gasoline engines. Excessive current = worn starter (motor windings) or high engine drag. Battery voltage drop during crank should stay above 9.6V; below means weak battery or excessive load.
- During dwell, coil primary should build to near-battery voltage (13-14V running). Reaching only 8V means the circuit has excessive resistance β bad ignition switch, degraded coil primary wiring, corroded connector, or weak alternator output. Weak dwell = weak spark = misfires under load.
Systematic Diagnostic
9 concepts- 'Runs poorly' means nothing until characterized. When exactly? Under what conditions? Test drive to reproduce. Scan tool codes and freeze frame. Live data at symptom conditions. Only after characterization does hypothesis-driven testing make sense. Skipping this leads to expensive parts-swapping.
- Systematic diagnostics eliminates possibilities in a logical sequence. Start with quick, cheap tests (visual, basic scan data). Move to more involved tests (compression, scope) as possibilities narrow. Documenting each test result prevents re-testing. This methodology is what separates diagnostic professionals from parts-swappers.
- Being stuck is normal in complex diagnostics. Re-verify assumptions (Am I sure the symptom is real? Am I sure this test result is correct?). Check TSBs for known issues. Use forums and technical hotlines. Sometimes describing the problem to another tech reveals your own error. Never guess with the customer's money.
- The CEL is a symptom, not a diagnosis. Reading codes is step one. Freeze frame shows when the code set. Monitor readiness reveals whether other tests have run. Live data during test drive shows real-time behavior. All this before deciding on repair scope β informs both the customer and the technician.
- Customers have the right to make informed cost decisions. The professional approach is transparency: this cheaper option treats the symptom, not the cause; the real problem may return; here's the risk. Document in the invoice: 'Customer declined XYZ despite recommendation.' Protects you legally and preserves the relationship.
- Multiple codes often trace to one root cause. A bad crank sensor might set misfire codes, cam correlation, and fuel trim codes all at once. Fixing the crank sensor may clear everything. Address fundamentals (sensors, power, ground, timing) before symptomatic codes (misfires, catalyst, trims). Order matters.
- Long diagnostics happen β modern vehicles are complex. Communicating early and honestly (before hours pile up further) preserves trust and lets the customer make informed decisions. Some issues require specialized equipment or dealer-level scanners β being honest about limitations builds long-term reputation.
- Never inherit another shop's diagnosis β you own the outcome, not them. Do independent diagnostics, verify (or refute) their findings, and give your own recommendation. Sometimes prior shops were right. Sometimes they were parts-swapping without diagnosis. Only your own diagnosis is defensible.
- Verification prevents comebacks. Confirm the original symptom is resolved. Check that no related issues emerged (e.g., replacing a coil doesn't cause a wiring stub to be pinched). Codes should stay cleared after test drive. Documentation on invoice provides your customer record and protects you legally.
Studied the material? Get DIA certified.
The Diagnostics & Drivability (OBD-II) exam turns what you just learned into a verifiable credential drivers and shops can look up. 75 questions Β· 90 minutes Β· 78% to pass Β· $19.99.
Studying here is free forever. There's no obligation to take the exam.