Rebuilt salvage cars: what OBD tells you about crash damage you cannot see

A rebuilt salvage car is not automatically a bad buy. Plenty of them, repaired properly, run for years and cost a third less than a comparable clean-title example. The problem lies elsewhere: rebuild quality ranges from “indistinguishable from factory” all the way down to “welded, painted, warning lamps extinguished”.

And here is what matters: body repair can be judged by eye, electrical repair cannot. A paint gauge finds filler. A lift finds a bent rail. Neither tells you whether the airbags deployed, whether the original ABS module is still in place, or whether the forward camera can actually see the road after the windshield was replaced. That only shows through the diagnostic port.

What we are looking for

After a serious impact, four things happen to a car, and all four leave traces in module memory:

1. The passive safety system fired — airbags, seatbelt pretensioners, sometimes a fuel pump cut-off.
2. Modules and wiring were physically destroyed — units in the front of the car sit exactly where the impact arrives.
3. Some modules were replaced — frequently from a donor vehicle rather than new.
4. Driver-assistance sensors shifted or were swapped — the bumper radar, the windshield camera.

A good share of that list can be hidden from the eye. None of it can be hidden from the data bus. Here is what to grab hold of.

1. The SRS module: the single most important check of the visit

After the airbags deploy, the restraints control module writes a crash record and enters a state that clearing a code will not undo. There is one legitimate path out: replace the module, or have it factory-reprogrammed.

The cheap path is different — make the dashboard lamp stop illuminating. The methods vary, from fitting a known-clean donor module to wiring in resistors that mimic intact squib circuits. The visible outcome is identical: clean dash, relaxed driver.

Over OBD this shows up three ways:

• The SRS module does not answer at all. It is absent from the module list. That is not “everything is fine” — that is “nobody responds to the request”. The associated code is U0151, lost communication with the restraints control module.
• The module answers but carries its own codes. B-series faults, for example B0001, the driver airbag deployment circuit. Basic scan tools often skip this series entirely, and that is exactly what the seller is counting on.
• The module answers, has no codes, but the SRS lamp never flashes at key-on. A healthy module runs a self-test at every start and lights the lamp for three to five seconds. A lamp that never illuminates means either a removed bulb or a module that has stopped reporting for itself.

That last one takes five seconds and no equipment at all. Turn the ignition on and watch the cluster.

2. U-codes: who else went quiet

A front-end impact tears more than sheet metal. Harnesses, connectors, and the modules inside the crush zone fail first, and after a rebuild anything at all might be sitting in their place.

U-series codes record precisely this — a module stopped answering:

Code	Who is silent	Why it matters after a crash
U0100	Engine control module	Wiring or the unit itself sits in the impact zone
U0121	ABS module	Lives in the engine bay, among the first to suffer
U0151	Restraints control module	See above — the critical one
U0140	Body control module	Runs lighting, locks, windows
U0155	Instrument cluster	Swapping the cluster is a common route to a “reset” odometer

A single U-code can be nothing more than a corroded connector. Two or more U-codes across different modules is no longer coincidence — it is a damage map.

How bus faults actually work, and how to tell a dead module from a bad contact, is covered separately in the body control module and bus fault guide.

3. A module from somebody else’s car

A cheap rebuild almost always means donor modules. Sometimes that is perfectly fine. Sometimes the unit is installed without ever being adapted — and then the car runs, but it does not run the way it should.

What diagnostics reveal:

• The VIN stored in the module does not match the VIN on the body. Many modules hold the VIN internally and return it on request. A mismatch is direct evidence of a swap. What the VIN encodes is covered in the VIN decoder guide.
• The module’s configuration does not match the car. A unit from a version with a different engine or without all-wheel drive brings somebody else’s settings along with it.
• Persistent configuration faults that return after clearing. The module reports waiting on a component this car does not have.

Adapting and coding modules to a specific vehicle is a large topic in its own right; the manufacturer coding overview gives the groundwork.

4. Driver assistance: working, or only pretending

If the car has adaptive cruise, lane keeping, or automatic emergency braking, all of them require calibration after body repair. The bumper radar and the windshield camera have to be aimed to within a fraction of a degree — otherwise the system sees a road that is not where it thinks it is.

The worst case here is not “the system does not work”. The worst case is the system works and is wrong: braking for nothing, or failing to see the car ahead.

Diagnostically this surfaces as calibration faults in the relevant modules and as a “not calibrated” status in live data. What to verify after a windshield or bumper replacement is in the ADAS calibration guide.

5. A special case: flood damage

Flood cars turn up regularly, and they are the worst category — worse than an impact. An impact is local; water gets everywhere.

Water does not produce one characteristic code. It produces a scattered set of illogical faults that refuse to add up to a single failure:

• Several sensors across unrelated systems report shorts or open circuits.
• Codes disappear after drying out and return a week later.
• Modules in the lowest points of the body — the body control module, the amplifier, units under the seats — answer intermittently.

The tell that separates this from ordinary wear: the faults have no logical connection to one another. A fuel level sensor, a rain sensor, and the left rear window motor do not fail simultaneously on their own.

Read the codes twice, a few days apart. A stable picture is an ordinary fault. A different picture every time means the wiring is corroding.

The order to work in

1. Ignition on, watch the cluster, five seconds. Does the SRS lamp flash at start-up? If not, there is no reason to go further.
2. Module roll call. Who answers, who does not. Write down the absentees.
3. Codes from every system, not just the engine. B, C and U series matter more here than P.
4. Module VINs against the body VIN.
5. Calibration status for driver assistance, if fitted.
6. A second reading a few days later if flood damage is suspected.

Red flags

• The SRS module is missing from the list or silent.
• The SRS lamp does not illuminate at key-on.
• Two or more U-codes across different modules.
• A module VIN that does not match the body.
• A set of faults with nothing in common.

Any single item on this list is reason enough to stop the inspection and have a very different conversation about price. Or no conversation at all.

What OBD will not show you here

Being honest about the limits:

• Body geometry. That is a measuring bench, and nothing but a measuring bench.
• Weld quality and rust protection.
• Whether the airbags were replaced with genuine parts — diagnostics sees that the circuit is intact, not what is sitting in it.
• The car’s history before it was rebuilt. That is auction databases and history reports, a separate tool entirely.

Diagnostics through the port answers one question, but answers it quickly and cheaply: does the car’s electronics agree with what the seller is telling you? If it does not, the remaining questions are no longer for a scanner.

The general protocol for checking any used car — readiness monitors, step order, what each step catches — is in the companion article; this one covers what gets added for rebuilt vehicles.

What you need

An adapter with an ELM327 v1.5 or later chip in the Bluetooth version, and an Android phone. Our app communicates over Bluetooth SPP; BLE and Wi-Fi adapters will not connect to it. Reading B, C and U series codes — the entire reason for coming here — works from the first connection.

Download the app and run the module roll call on your own car before you go and look at somebody else’s.