How to use an OBD-II scanner: pull your own codes for $25
A beginner's guide to plugging in a code reader, interpreting the results, and deciding whether you need a shop or a parts-store fix.
Every car sold in the US since 1996 has a standardized OBD-II diagnostic port, usually under the dashboard on the driver's side. A basic Bluetooth scanner (like the FIXD or BlueDriver) costs $25-100 and pairs with a free phone app to read and clear trouble codes.
To pull codes: plug the scanner into the port, turn the ignition to ON (don't start the engine), and let the scanner connect. It will display any stored Diagnostic Trouble Codes (DTCs) in the format P0XXX (powertrain), B0XXX (body), C0XXX (chassis), or U0XXX (network). Powertrain codes are by far the most common.
A code tells you WHAT the computer detected, not necessarily WHAT FAILED. For example, P0420 (catalyst efficiency below threshold) could be a failing catalytic converter — or just a bad downstream O2 sensor. P0171 (system too lean) could be a vacuum leak, a dirty MAF sensor, or a weak fuel pump. The code narrows the search; a good technician does the actual diagnosis.
Pending codes are faults the computer has seen once but hasn't confirmed — they may clear on their own. Confirmed codes have triggered the check engine light. Clearing codes turns off the light but doesn't fix the problem — if the fault is real, the light will return within a few drive cycles. Never clear codes right before an emissions test; the monitors need time to run and incomplete monitors will cause a test failure.0
Information is for educational purposes only. Always consult a qualified mechanic for diagnosis and repair. AutoAt's knowledge base is AI-assisted and regularly updated but may not reflect the most current manufacturer specifications. Always verify critical specifications with official service manuals. Repair procedures described here may require professional tools, training, and certifications. Attempting repairs beyond your skill level can be dangerous.