The automotive diagnostic field guide
Check engine.
Clear head.
A few characters on a scanner.
A better understanding of what comes next.
Reference first. Diagnosis next.
EXAMPLE TROUBLE CODE
P0300Random/Multiple Cylinder Misfire Detected
Community code reference
11,786dictionary entries
2diagnostic guides
33vehicle makes
Every reference has a source.See how the guide is built01 / Your vehicle, your context
Start with your make.
Make labels help you find a reference. Year, engine and model documentation determine whether it applies.
02 / From the code library
Small code.
Useful context.
Random/Multiple Cylinder Misfire Detected
Catalyst System Efficiency Below Threshold Bank 1
System Too Lean Bank 1
EVAP System Leak Detected - Large Leak
Replace Hybrid/EV Battery Pack
Lost Communication With ECM/PCM A
Read the first letter
Four systems.
A place to begin.
A code’s prefix puts the signal in context. Explore the reference by vehicle system.
Powertrain
Engine, transmission and powertrain diagnostic references. Exact vehicle and module context still matters.
Body
Body-system diagnostic references. Confirm the reporting module and vehicle-specific definition.
Chassis
Chassis-system diagnostic references. Read the vehicle warnings before deciding whether to continue.
Network
Communication and network diagnostic references. A communication code does not identify a failed module by itself.
03 / More than a make badge
Bring your vehicle into focus.
Good diagnosis starts with good questions
Read the code.
Keep the context.
The name of a fault is not proof of a failed part. Use the reference to understand the signal, then build the evidence.
Into the field guidesCapture the full picture.
Keep the exact code, scan report, symptoms and vehicle details together.
Know what the source supports.
Code-definition data and a manufacturer’s model-specific guidance answer different questions.
Choose an informed next step.
Start with the documented checks. Understand the limits before buying a part or clearing a code.