PGE Tuning Lab

Volkswagen airbag module locked with crash data on Golf 6 and Passat B7

A Golf 6 or Passat B7 that has been in an accident keeps its airbag warning on because the module stores crash data and locks itself, and the tester will not clear that entry. The unit has done its job and it now refuses to work again until the crash record is removed. The checks below cover the safe way in, the circuits to measure and the coding that follows.

What the module does after an accident

When a circuit fires, the module writes a crash record into its memory and it stops arming the remaining circuits. The warning lamp stays on and the memory will not clear, whatever the tester does. That behaviour is deliberate, since a unit that has fired once cannot be trusted to fire again without inspection and a reset.

Ask what was replaced after the accident and who did the bodywork. A car that has had the airbags changed still needs the module dealt with, and a car that had the module changed may now have a coding fault instead. Write the list of parts on the sheet, since the paperwork matters as much as the measurement.

Reading address 15 safely

Switch the ignition off, disconnect the battery and wait the period the repair data states before you touch any airbag circuit. Then read the airbag address with the tester and write every code text on the sheet. Do not probe a connector with a meter while the system is powered, since a stray voltage on an igniter line is a hazard to you and to the part. Keep the earth lead off the post and away from it for the whole measurement, and refit each plug before you move to the next circuit, so nothing is left open when the battery goes back on.

Read the memory twice, once before and once after a key cycle, since some entries appear only after the unit has run its self test. Note the part number and the software level of the unit, because the coding you apply later has to match that level. Photograph the label on the unit while it is still in the car.

The crash entry and the locked unit

The memory will carry an entry that names a crash, and that entry is the one that will not clear. A tester that offers to clear it will fail, and a second attempt gives the same result. That failure is the confirmation you are looking for, and it is worth writing on the sheet as evidence.

Check whether the unit also names a circuit that is open or high in resistance. A locked unit can hide a second fault, and that fault will still be there after the reset. Read every entry in the list before you decide, because a reset over a broken circuit leaves the lamp on and the customer unconvinced. A car that came in with the lamp on and no crash record has a different fault, and a reset is not the answer for it. That car needs the circuits tested first, since a locked unit is easy to see and a broken wire is easy to miss.

Measuring the igniter circuits

With the battery off, measure each igniter circuit at the module plug with a dummy load fitted in place of the airbag, and read the resistance the tester reports for that circuit. Never put a meter directly across an igniter, since the meter sends a current through it. The tester shows each circuit as a value and compares it with the window the software expects.

A circuit that reads open has a broken wire or a disconnected plug under a seat, and one that reads low has a short in the loom. Check the plugs under both front seats first, since a seat moved fully forward can pull a connector apart. Write each circuit value on the sheet beside the name the tester gives it. Compare the values across the set, since the window is wide and a circuit at one end of it can still be a poor connection. A value that changes when the seat is moved is the one to chase before the unit goes back.

The sensors and the seat circuits

Read the values for the impact sensors and the seat occupancy mat as well, since those circuits are part of the same system and they set their own entries. A sensor that reads outside its window will keep the lamp on after the module is reset. Check the sensor mountings on the front panel for bending after a light impact.

Look at the wiring under the seats for a chafed loom where it passes the seat frame. A car that has carried heavy loads or had the seats out shows a worn loom at that point, and the fault appears when the seat is moved. Repair the wire with a soldered joint and a sleeve, then read the circuit value again. Take the seat out for that repair rather than working underneath it, since the wire has to be shortened and re-terminated properly. A loom that was repaired before with a crimp is worth opening up, because a crimp in that place works loose within a season.

The unit on the bench

The unit comes out from under the centre console, and the reset is done on the bench with the crash record read first and stored with the job. The board is inspected for damage around the drivers, since a fired circuit leaves heat marks that a reset will not repair. A board with damage at a driver is replaced rather than reset.

After the reset, read the stored record again and confirm the crash entry has gone. Then check the unit answers on the bench with a supply and a bus connection, since a unit that has been reset badly will not code. Keep the reading with the job file, because the next owner may ask what was done.

Coding after the reset

Fit the unit and code it to the car with the tester, matching the coding to the equipment the car actually has. A unit coded for a different set of airbags gives a configuration entry that will not clear. Connect a charger before the routine, since a voltage dip in the middle leaves a half coded unit.

Read the memory after the coding and confirm it is clean. Then switch the ignition off and wait, then switch it on again to watch the lamp do its self test and go out. A lamp that stays on after two cycles sends you back to the circuits you measured, not to the unit.

The final test and the paperwork

With the car assembled, run the engine and read every address on the network for stored faults. A body module that recorded an impact can hold its own entry, and it will keep a warning on the dash even with a clean airbag unit. Deal with those entries before the car is handed over.

Write the work on the job sheet with the unit number, the circuits measured and the coding applied, then keep the old readings with the file. A car with this history needs its records, and the next workshop will ask for them. Note the date of the reset beside the mileage so the history is clear. Tell the owner what the lamp means if it returns, and ask them to bring the car back rather than to clear it with a hand held tool, since a cleared memory hides the evidence the next visit needs.

What is measured on a Golf 6 or Passat B7 with a locked airbag unit
SymptomLikely causeWhat is measured
Warning on, crash entry that will not clearCrash record stored in the unitMemory read twice, then the crash entry confirmed
One circuit reading openPlug under a seat apartCircuit value per igniter with a dummy load fitted
Lamp on after the resetSensor or seat mat out of windowSensor and mat values against the expected window
Configuration entry after codingUnit coded for other equipmentCoding applied against the equipment on the car

Frequently Asked Questions

Can the tester clear crash data?

It will try and it will fail, because the entry is locked by design. The record has to be removed on the bench before the unit will work again.

Is the car safe to drive with the lamp on?

Assume the airbags will not fire. A car in that state should not carry passengers until the unit is reset and the circuits are proved.

Does every accident need a reset?

Only when a circuit has fired or the unit has stored a crash record. A light impact that set no record leaves a unit that codes and works as it should.

Why fit a dummy load when measuring?

A meter across an igniter can fire it. The dummy load lets the tester see the circuit without putting current through the airbag.

Related Services