Classic Car

Reading a Fault Code Without a Scanner on an Older Car

Many pre-OBD2 cars can flash stored fault codes through the check engine light itself. The method is genuine, and it is also brand-specific, not universal.

By Antoni DaskalskiPublished 7 August 20263 min read

A code reader is the obvious answer to "what is wrong with my car," and on a genuinely older car it is frequently the wrong answer for a simple reason: the OBD2 port every consumer scanner expects to plug into did not exist yet.

Why a scanner does not help here

OBD2 became mandatory in the US from model year 1996 (later in the EU — 2001 for petrol, 2004 for diesel). Any OBD2 scanner is built around that connector and that standardised protocol. A car built before its market's OBD2 mandate simply has no matching port — plugging in a scanner is not an option, not a worse option.

What many pre-OBD2 cars can still do

Many manufacturers built basic self-diagnosis into their cars well before OBD2 standardised it — commonly by having the onboard computer flash stored fault codes through the check-engine light itself. The general principle: a specific trigger (often bridging two particular terminals on a diagnostic connector, sometimes a dedicated procedure with the ignition) puts the computer into a mode where it blinks the light in a pattern — a count of long and short flashes corresponding to a code number — which gets counted and matched against that manufacturer's code list.

This is genuine, well-documented technology from the OBD-I era, used across a range of manufacturers through the 1980s and into the mid-1990s. It is also, deliberately, not something this page gives exact terminal numbers or flash-count tables for.

Why no universal procedure follows

OBD-I was never standardised the way OBD2 later was. Every manufacturer implemented their own version — different connector, different terminals, different trigger sequence, different code list. A flash-code procedure that is correct for one 1980s car says nothing reliable about a different make, or even a different model year from the same manufacturer. Publishing a single generic procedure here would create exactly the kind of unverified, possibly-wrong technical claim this site's own standard exists to avoid.

What actually matters

Confirm your specific car has this capability, and how, before attempting it. A factory service manual for your exact make and model year is the reliable source — it will state whether flash-code self-diagnosis exists on that car and give the correct trigger terminals and code table. A forum dedicated to your specific model is the realistic second option.

Getting it wrong is usually just unproductive, not dangerous — on most systems, bridging the wrong terminals fails to produce codes rather than causing damage. Some systems are more sensitive to a wrong connection risking a short circuit, which is exactly why confirming the correct procedure first matters.

A basic multimeter still has a role even where flash codes exist. A multimeter for car owners covers checks — battery condition, charging voltage, a bad earth — that flash codes were never designed to catch, since most OBD-I systems monitor a narrower set of faults than a modern ECU does.

The mistake to avoid

Assuming a car without an OBD2 port has no self-diagnosis option at all, or going the opposite direction and applying a flash-code procedure found for a different make. Confirm what your specific car actually supports before either giving up on the car telling you anything, or trying a method that was never built for it.

If flash codes are not available for the car in question, the rest of an older car's roadside readiness is worth having anyway — a code you cannot read is still a car that might strand you, and the roadside kit does not depend on diagnosing the cause first.

Questions people actually ask

Does every pre-1996 car support flash codes?

No. It depends entirely on the manufacturer and whether the car has any onboard diagnostic system at all — some earlier carbureted cars have no computer to interrogate in the first place. The method is genuine and widely used across the OBD-I era, but it was never standardised the way OBD2 later was, so a procedure for one make says nothing reliable about another.

Is this the same as OBD2?

No — it is the predecessor. OBD2 standardised the connector, the protocol and the code format across manufacturers from 1996 in the US. Before that, "OBD-I" systems existed on many cars but each manufacturer implemented diagnostics differently, which is exactly why there is no single universal flash-code procedure to publish here.

Can this damage the car if done wrong?

Getting the trigger sequence wrong on most systems simply fails to produce codes rather than causing damage, but bridging the wrong terminals on some systems risks a short circuit. Confirm the correct terminals for your specific make and model year from a service manual before bridging anything, rather than guessing from a general description.

Why bother with this instead of just buying a code reader?

Because most consumer OBD2 scanners plug into a port that simply does not exist on a genuinely pre-OBD2 car — there is nothing to plug into. Flash codes are not a cheaper alternative to a scanner on these cars; they are often the only self-diagnosis option that exists at all, short of manufacturer-specific proprietary tools.