Guides

Code & symptom guides

Every guide here follows the same shape: what the code is actually measuring, the live-data test that narrows it down, and an honest account of where a phone adapter stops and hands on the car begin.

Code guides

You have a specific code and want to know what it really means before anyone quotes you a part.

  • P0420 — Catalyst efficiency below threshold — the code people get quoted a converter for.
  • P0171 — System too lean — where fuel trims tell you the answer in about two minutes.
  • P0300 — Random misfire — and the per-cylinder counters that show which one it really is.
  • P0301 — Cylinder 1 misfire — and the swap test that proves the cause in one drive.
  • P0455 — Large EVAP leak — check the gas cap first, and don't clear it before an inspection.

Symptom guides

Something's wrong and there's no code yet — or the light is on and you want to know how worried to be.

What these are for

Most code articles online are dictionary entries: here is the code, here is the official description, here are five parts you might buy. They're written to be found, not to be useful, and they leave out the part that actually saves money — how to tell which of those five it is.

These guides are built the other way round. Each one centres on a test you can genuinely run from the driver's seat with a cheap Bluetooth LE adapter: watch these two sensors, compare them under these conditions, and here's what each result rules out. That's how the problem gets narrowed before anything is taken apart.

Two rules run through all of them:

  • A code narrows. Tests confirm. No code, on its own, identifies a failed part. Anything claiming otherwise is selling something.
  • The limits get stated. Every guide ends with what a phone adapter genuinely cannot see — smoke testing, compression, backpressure, physical inspection. A tool that won't tell you where it stops isn't being confident, it's being useless.

Reading codes, watching live sensor data, checking emissions readiness, and testing the battery are free in Fixiom — always, no credits and no subscription. Every test described across these guides sits inside that free half.

Also useful: what an AI mechanic can honestly do, and the adapter buying guide covering which Bluetooth LE units actually work with third-party apps.

Common questions

Do I need an adapter to use these guides?+

To read the code and run the live-data tests, yes — a Bluetooth LE OBD2 adapter, typically $20–30, plugged into the port under the dash. The explanations are useful without one, but the tests are what make these guides different from a code dictionary.

Will these work on my car?+

Every car sold in the US from 1996 onward has the standard OBD2 port and reports the generic codes and live data these guides use. Some manufacturer-specific data varies, and Fixiom shows only what your vehicle actually answers rather than inventing readings.

Can a code tell me exactly which part failed?+

No. A code tells you which circuit or system noticed something out of range — often several different faults produce the same code. Narrowing to a specific cause is what the live-data tests in these guides are for, and confirming it usually takes a physical test.

A code narrows it down. Live data tells you which one it is.

Codes, live data, emissions checks, and the battery test are free in Fixiom — always. The AI mechanic is there for the reasoning in between.

Get the app