CarScan

Car diagnostics glossary

The words you meet in fault code descriptions and live data — explained once, without jargon.

How the exchange works

OBD-II

The on-board diagnostics standard: one connector and one language of requests.

It exists so that any scanner can talk to any car: a 16-pin connector, a set of mandatory requests and a shared list of codes. Everything beyond that list each maker does its own way — which is why fault codes are read everywhere and a service reset is not.

Where you will meet it →

ELM327

The translator chip between the car socket and the phone.

It diagnoses nothing by itself: it takes text commands, sends them to the car and returns the answer. What matters is not the brand but how honestly a clone repeats the original — cheap ones have a trimmed command set.

Where you will meet it →

PID

Parameter number: the car returns one specific value under it.

For example 0C is engine RPM and 05 is coolant temperature. The app asks for a number, the car answers with a value; names and units the app supplies itself.

Where you will meet it →

DTC — fault code

A record in a module's memory that readings went outside the allowed range.

The letter names the system (P powertrain, B body, C chassis, U network), the digits say what exactly did not add up. A code names a symptom, not a broken part.

Where you will meet it →

CAN bus

The wire over which the car's units talk to each other and to you.

A car has not one unit but a dozen: engine, gearbox, ABS, airbags. They are linked by a shared bus, and the scanner connects to the same one. Two things follow: the adapter answers fast while the car answers slowly (it waits for the unit), and «no reply from the unit» means the question went out and nobody was there.

Where you will meet it →

MIL — check engine light

The dashboard light the control unit turns on when a fault is stored.

Steady means a fault is stored and you can usually drive on. Flashing means misfires are happening right now and raw fuel is reaching the catalytic converter: driving on damages it.

Where you will meet it →

Mixture and fuel

Lambda sensor (oxygen sensor)

A sensor in the exhaust: it judges by leftover oxygen whether the mixture is rich or lean.

There is one before the catalytic converter (control) and one after it (monitor). By the first the unit adjusts fuelling, by the second it checks whether the converter still works.

Where you will meet it →

Bank 1 and bank 2

One half of the cylinders on V-type and boxer engines.

Bank 1 is the one containing cylinder number one. An inline engine has a single bank, so «bank 2» never appears in its codes. The bank number tells you which side of the engine to look at.

Where you will meet it →

Fuel trim

How far the control unit departs from the calculated fuelling.

The short-term one changes every second, the long-term one remembers a persistent offset. A steady plus means the unit has to add fuel: either air is leaking in or fuelling falls short.

Where you will meet it →

Lean and rich mixture

Less fuel than calculated is lean, more is rich.

Lean runs the engine hot and stumbles under load; rich smells of petrol, smokes and kills the converter. The same «drives badly» feeling comes from either — only diagnostics tells them apart.

Where you will meet it →

MAF sensor

The sensor that measures how much air enters the engine.

The unit decides how much fuel to inject from this reading. A dirty meter under-reads, the mixture goes lean, the driver presses harder, and consumption rises with the effort. That is why it is checked before expensive parts are replaced.

Where you will meet it →

Catalytic converter

A part in the exhaust that burns off what the cylinders did not.

It works only when hot, so on a cold engine it does nothing — that is its design, not a fault. Its health shows in the rear oxygen sensor: with a healthy converter it stays flat, with a tired one it starts copying the front sensor's swings. It rarely dies on its own: misfires and a rich mixture kill it.

Where you will meet it →

Exhaust recirculation (EGR)

Returning part of the exhaust to the intake to lower combustion temperature.

It is needed at mid load; at idle and full throttle the unit does not ask for it. The valve clogs with soot, and then the command is there while the flow is not. A blanking plate removes the code and adds two problems: combustion temperature rises and the particulate filter clogs faster.

Where you will meet it →

Misfire

A cylinder did not fire: the mixture failed to ignite or was not there.

The unit spots them by uneven crankshaft rotation. The code names the cylinder, but the cause may be the plug, the coil, the injector or compression — the code alone does not say.

Where you will meet it →

What the app shows

Freeze frame

A snapshot of the readings at the moment the fault was stored.

RPM, load, temperature, speed — everything as it was at that second. It shows whether the trouble happened cold or warm, at idle or under load.

Where you will meet it →

Readiness monitors

Flags showing which internal checks the unit has managed to run.

After clearing faults or disconnecting the battery they reset and refill over several drives. Incomplete monitors are exactly why a healthy car gets turned away at an inspection.

Where you will meet it →

VIN — vehicle identification number

Seventeen characters that identify the car uniquely.

It is read by the same kind of request as everything else. Make, model and year follow from it — the app puts them into the report so the mechanic does not have to ask.

Where you will meet it →

Request modes (01–0A)

The kinds of question a scanner asks the car.

01 is live data, 02 the freeze frame, 03 stored codes, 04 clearing, 07 pending codes, 09 the VIN. There is nothing to choose: the app asks for whatever the open screen needs.

Where you will meet it →

Pending codes

A deviation was noticed once, but the light is not on yet.

The unit waits to see whether it repeats on the next drive. Such codes are visible in the app and are useful: the trouble is only starting and can still be caught before the light.

Where you will meet it →

Clearing faults

Erasing records from the unit's memory — together with the monitors.

Clearing does not fix anything: if the cause remains, the code comes back. It also resets the readiness monitors, so an inspection right afterwards is a bad idea.

Where you will meet it →

Limp mode

A protective state in which the unit deliberately limits the engine.

The car will not go past sixty, will not rev above three thousand, sometimes shuts off the turbo. This is not a fault in itself but a decision: the unit saw something that makes normal driving unsafe. A code is already stored at that moment — and it explains why.

Where you will meet it →

Service interval reset

Resetting the «service due» counter after maintenance.

It is not part of the OBD-II standard: every maker does it its own way, and on some cars it cannot be done through the socket at all. The app says so in advance instead of trying blindly.

Where you will meet it →