The code reader's companion: tools, codes, and what the data means

The wiki has the code pages — this is the page about the act of reading them: the tool classes and what each can honestly do, the code layers and what each layer knows, the freeze-frame and PID basics that turn a blinking hex string into a diagnosis. It is the companion that sits between your tool and our fault-code library.

The tool classes — what each one is for

The class stack is not either/or — the mature setup is a dongle that lives in the car plus the codes-in flow for depth. The mhd-adapter-guide owns the hardware compatibility law (the cheap clone dongles are where datalogs go to die); mhd-codes-and-flash-recovery owns the DME error-code side of the flash tooling.

The two code layers — and why you want both

The same event can wear both names — 2A82 is P0012 underneath — and our fault-code pages carry both names on purpose: the generic layer is what the handheld sees, the manufacturer layer is what the diagnosis runs on. When a tool shows only "P0012 CAMSHAFT POSITION A TIMING OVER-RETARDED BANK 1" it is telling you the truth, but the factory's own document for 2A82 is where the enablement conditions and the two-item problem list live.

Freeze-frame — the scene of the fault

Freeze-frame is the operating-condition snapshot stored when a code sets. The core fields and what they buy you:

The discipline: capture the frame before clearing anything, and read it against the code's factory enablement conditions — the 2A82 document, for instance, gates on system voltage above 10 V and coolant between 0 and 110 °C, so a frame outside those gates means the code set under conditions the factory didn't even design the check for.

PIDs — the channels, in diagnosis order

A PID is one live channel — the needle, not the code. The ones that earn their screen space, in the order the wiki's triage flow uses them:

1. 01Actual vs target cam position (intake and exhaust) — the VANOS lag story before it becomes a code (the datalog guide plots it).
2. 02Rail pressure, actual vs target — the fuel story at a glance: low-pressure side starves the pump, high-pressure deviation is injectors/HPFP.
3. 03Boost actual vs requested (or WGDC) — the air story; the what-wgdc-means page owns the wastegate half of that channel.
4. 04Ignition timing corrections / misfire counters per cylinder — the detonation and misfire truth that predates any code; per-cylinder counters are the manufacturer layer's gift.
5. 05Coolant and oil temperature — the two temperatures people conflate; oil lags coolant by minutes and half the "overheats" are one reading mistaken for the other.
6. 06Lambda / AFR and fuel trims — the mixture referee between the air story and the fuel story.

The reading-your-datalog guide turns these into lap-readable traces; the is-it-the-tune-or-the-car page is the decision tree when several of them move at once.

The factory's own test order — the citation for triage

The service layer does not leave test order to vibes. The idling-quality test sequence in the factory documents orders the compression check before the running-smoothness check — mechanical truth first, then the electronics that depend on it. That order is the wiki's triage philosophy in one citation, and it scales: compression, then spark, then fuel, then control — because every layer up assumes the layer below is sound.

Read-clear discipline — the loop that actually converges

1. 01Read and save the full fault memory — manufacturer layer if your tool has it, freeze frames attached.
2. 02Decode before you touch anything — the codes-in flow or the matching fault-code page here; know the enablement conditions and the factory's own problem list before forming a theory.
3. 03Fix, don't clear — clearing is the last step, not the first; a code cleared without a fix is a timer set for the same conversation.
4. 04Clear, then drive the enablement window — warm the car into the conditions the code gates on. A code that doesn't return inside its own gate is either fixed or was never diagnosed.
5. 05Log the verify pass — the misfire counters and cam deviations tell you it's fixed before the DME files the paperwork.

The limp-mode page owns what a reduced-power state is telling you; the no-start page owns the crank-but-no-fire ordering; both consume this page's tooling.