Your scan tool told you what the car thinks. It didn't tell you what's true. That's the gap. That's where techs get stuck, throw parts, and eat the comeback. Here's what actually happens in most shops. Code comes up. Tech pulls data. Data looks weird. Tech guesses. Parts go on. Sometimes it works. Sometimes the car comes back and now you're upside down on a job you already collected for. None of that is a tool problem. Every shop has a scope. Most of them have one sitting in a drawer with the leads still bagged. Tools don't buy skill. Process does. This class gives you the process. Verify the concern. Read core PIDs to target the system. Pick the right test. Capture and compare to known good. Verify the fix. Same sequence, every car, every time. You'll learn to capture a stable waveform in under two minutes, prove ignition, injector, and cam-crank faults with the scope instead of guessing, read burn time and fuel trims for what they're actually telling you, and decide fast whether you're diagnosing, programming, or relearning. WHAT WE COVER Core PIDs and what they mean as go / no-go Fuel trims and what to test next Trigger types, timebase, and stable captures Low amp, high amp, and when each one wins Secondary ignition, burn time, and injector current ramp VVT desired vs actual, PWM, and CAN network checks REAL CASES, START TO FINISH We walk a Ford F-150 with two lean codes and a stack of already-replaced parts, and a Lexus IS300 with dead cylinders after a timing job. Both diagnosed on the scope. Both root-caused. You see the captures, the misses, and the fix. WHAT YOU LEAVE WITH Reference captures and a workflow you can run Monday morning. Not theory. A repeatable process that stops the guessing. Two nights. Eight hours. Taught by someone who does this work every day.