Diagnose and Troubleshoot Automotive Engine and Electrical/Electronic System Faults
What this domain tests
This domain tests systematic diagnosis: verifying the complaint, retrieving diagnostic trouble codes (DTCs), reading scan-tool data, and testing circuits with a digital multimeter. Expect no-start, misfire, charging, and sensor-circuit scenarios.
Core rules and concepts
- Follow a logical sequence: verify the complaint, perform visual inspection, retrieve DTCs and freeze-frame data, test the circuit, then repair and confirm.
- A DTC identifies a circuit or system fault, not automatically the failed part. Use the wiring diagram and test the circuit.
- For voltage-drop testing, place the meter across the connection under load; a good connection typically drops less than about 0.1 V.
- Check the basics: battery state of charge, fuses, grounds, fuel pressure, spark, and compression. An engine needs air, fuel, spark or heat, and compression.
- Use the correct meter range and back-probe connectors carefully; do not pierce insulation unless the procedure allows it.
Worked example
A vehicle sets P0301, misfire on cylinder 1. The technician swaps the ignition coil from cylinder 1 to cylinder 2 and clears the code. If the misfire moves to cylinder 2, the coil is suspect. If it stays on cylinder 1, test the injector, spark plug, wiring, and compression. The reasoning is to move a known part and observe whether the fault follows it.
Traps that cost marks
Replacing the part named in the code without circuit tests; skipping visual checks; using a test light on computer-controlled circuits; misreading min/max on the meter; and failing to confirm the repair with a road test or live data.
Key points
- A DTC points to a system, not always a part.
- Use freeze-frame data to match the fault conditions.
- Voltage drop should be low under load.
- Swap known-good parts to isolate misfires.
- Confirm every repair with a retest.