Workshop manuals include fault-finding tables organised by symptom: the engine won’t start, engine runs rough at idle, engine lacks power, and so on. For each symptom, the manual lists possible causes in order of probability and includes diagnostic tests to confirm or rule out each cause. Using these tables effectively is faster than guessing at random parts.
Structure of a Fault-Finding Table
A typical fault-finding table lists the symptom at the top (e.g., “Engine stalls at idle”), followed by a numbered list of possible causes ordered roughly from most to least common. Each cause has an associated test or inspection procedure. For example: “1. Vacuum leak – perform smoke test of intake system. 2. Dirty throttle body – inspect and clean. 3. Faulty idle air control valve – test operation.” Working through the list in order usually identifies the problem within the first few items.
Combining with OBD-II Data
Fault-finding tables are most effective when combined with fault code data and live sensor data from an OBD-II scanner. A code like P0171 (system too lean) combined with the fault-finding table’s list of lean causes narrows the search quickly. Live data like fuel trim values, coolant temperature, and oxygen sensor readings confirm which suspected cause matches what the engine is actually doing. See our OBD-II codes guide for more on interpreting codes.
Starting with the Simplest Causes
Good fault-finding practice starts with the simplest and cheapest possible causes, not the most expensive. A loose fuel cap is always easier to check than replacing an oxygen sensor, even if both appear in the cause list. A blown fuse is always easier to check than replacing an ECM. The fault-finding tables generally list causes in order of frequency, but you should also consider order of effort – if cause #4 takes 5 minutes to verify and cause #2 takes an hour, check cause #4 first.
When Fault-Finding Tables Don’t Help
Fault-finding tables work well for common faults but can fall short for intermittent problems, multiple simultaneous faults, or unusual combinations of symptoms. When the standard approach fails, try these techniques: keep a log of exactly when symptoms occur (cold vs hot, wet vs dry, accelerating vs decelerating) to narrow conditions, compare live data streams to known good values in the workshop manual, use a multimeter or oscilloscope to check sensors and actuators in real time (see our multimeter guide), and systematically substitute known-good components if you have access to them.
Symptom-Based vs System-Based Diagnosis
Symptom-based diagnosis (using the fault-finding tables) is fastest for common problems. System-based diagnosis (understanding how each system works and testing each component in sequence) is slower but more thorough for difficult cases. The best mechanics use both: start with the fault-finding table for an initial list of suspects, then switch to system-based testing if the simple causes don’t pan out. Your workshop manual supports both approaches with both symptom tables and detailed system descriptions.
Vehicle-specific fault-finding tables, diagnostic procedures, and system descriptions are in your workshop manual. MechanicMate offers PDF workshop manuals for over 960 models at mechanicmate.net/shop.
— MechanicMate . Questions or a second opinion? [email protected].