PGE Tuning Lab

Audi airbag lamp with crash data in the module

An airbag lamp that stays on after a repair usually means the module still holds the crash record from the event that fired it. The A4 and the A6 keep that record inside the airbag unit, and clearing the fault memory does not remove it. Read the module before you order a part, and measure its feeds before you open it.

A lamp that stays on after the repair

The airbags and the belts have been replaced, the battery is connected, and the lamp comes on at key on and stays on. The tester clears the memory and the lamp returns at the next key cycle. That pattern tells you the unit holds a record the tester cannot erase, and it is the most common reason a repaired car returns with the same lamp. Compare the date on the module label with the date of the repair, because a unit that was never removed cannot have been reset.

Ask what was replaced and whether the module was reused. A car with new airbags and the original module shows the lamp until the unit is reset, while a car with a unit from another car may carry a coding that does not belong to this one and sets a lamp of its own.

Reading the airbag address

Read the airbag address and save the full memory before you clear anything, because the entries name the loop that deployed and the moment it was recorded. Note the part number and the coding from the identification page, since a unit prepared for this car is matched to that coding. Photograph the label on the module before it comes out of the car. Keep that photograph with the job sheet, because the coding is written from it when a replacement is prepared in advance.

Compare the stored entries with the parts that were changed. An entry that names a loop you have already replaced points at the record inside the unit, and an entry that names a loop you have not touched points at the harness or at the igniter on that side of the car.

Crash data inside the module

The module keeps a crash record in its memory and sets a flag that holds the lamp on for as long as the record stays there. A tester that clears the fault memory removes the entry and leaves the flag, which is why the lamp comes back. The flag is cleared on the bench by reading the memory and writing that block back in its pre crash state. Some units keep the record in more than one block, so the whole memory is read and compared before anything is written.

Do that work with the unit on the bench and the airbags disconnected, since the module is armed whenever it has a supply. Work on a grounded mat with the unit sitting in a plastic tray, and never probe the igniter pins of the module while it is powered up.

Supplies and ground at the module

Measure the permanent feed and the ignition feed at the module connector with the plug fitted, and load each one with a bulb. A module that sees eleven volts at key on and drops away during a start can set a supply entry of its own, and that entry reads like a crash record to anyone who does not check the value. Read both feeds once more with the engine cranking, because the dip at that moment is exactly what sets such an entry on a car with a tired battery.

Measure the ground pins to the battery post on the millivolt range, then clean the stud and repeat the reading on the same pins. A ground drop above about fifty millivolts upsets the module and produces a lamp that comes on after a bump in the road, which the driver reports as an intermittent fault on a car with nothing wrong inside it.

The loops and the harness

With the battery disconnected and the module plug off, measure each igniter circuit on the harness side from pin to pin and from each pin to ground. You are looking for a short to ground and for a circuit that reads open. A circuit that reads a few ohms through the igniter is normal, and that value is compared across the loops. Write the value for every loop on the sheet, since the comparison across loops is what makes one odd reading mean something.

Do not put a meter across an igniter itself, because the meter current is a risk and the number tells you very little. Read the loop resistance from the module through the tester instead, where the unit measures it with its own small current and reports the value on the data page for each loop.

The seat and belt circuits

Read the entries for the seat occupation sensor and the belt tensioners as well, because a lamp that comes on with no crash record is often one of those circuits. Move the seat through its full travel and watch the value, since a broken wire in the seat loom shows itself at one end of that travel. Look for a bent pin in the connector under the seat. Check the belt buckle switch on both sides, because a buckle that reads closed with the belt out sets the same lamp.

A tensioner that has fired has to be replaced, and the module keeps the lamp on until it reads a good loop on that side. Fit the new part before you clear anything, because a clear on a loop that is still open is wasted work and the lamp returns at the first key cycle.

What confirms the module

The module is the fault when the crash record survives a clear and the wiring has been checked at every loop, with the feeds holding under load and a low ground drop. Those results together leave the wiring out of the picture. Write each value on the sheet as you take it, because a second unit is prepared from those numbers.

A unit that has been reset and still sets a loop entry has a fault on that loop, and the harness on that side is measured again. The record and the loop fault look the same on the cluster, and only the data page separates them for the reader.

Handback and the lamp check

Fit the module, connect the battery and cycle the ignition three times, watching the lamp at each key on. The lamp should come on for its check and then go out. Clear the memory once more and read it again afterwards, because a unit that was reset correctly has nothing left to store.

Write the part number, the coding and the reset result on the sheet. Ask the customer to return if the lamp comes on after a week, since a seat connector that was disturbed during the repair will show itself around then and it is a short visit.

Photograph the module label and the coding before the unit leaves the car, because a unit prepared from the wrong coding sets a lamp of its own and the photograph saves a second visit. Clear the memory only after every loop has been checked, since a clear on a car with an open loop hides the entry from the next reader. Tell the customer that the lamp comes on for a check at key on, because a driver who expects it to stay dark will report a fault that is not there.

What is measured on an A4 or an A6 with the airbag lamp on
SymptomLikely causeWhat is measured
Lamp returns after a clearCrash record inside the moduleStored memory saved before the clear
Lamp on after a startSupply falls during crankingBoth feeds at the plug under a bulb load
Entry names one loopHarness or igniter on that sideCircuit to ground on the harness side
Lamp on over bumpsGround drop at the moduleMillivolt drop to the battery post

Frequently Asked Questions

Does clearing the fault memory turn the airbag lamp off?

It removes the entry and leaves the crash flag in place, so the lamp returns at the next key cycle. The unit is reset on the bench before the lamp stays out.

Is it safe to measure the airbag wiring with a multimeter?

Measure the harness side with the module unplugged and the battery disconnected, and never put a meter across an igniter. The loop values are read from the module through the tester.

Can a module from another A4 be fitted?

Only with the coding and the matching data written for this car, and with the crash record cleared first. A unit carrying another coding sets a lamp of its own.

Why does the lamp come on a week after the repair?

A seat or belt connector disturbed during the work shows itself after some driving. The value is read while the seat moves through its travel, and the connector is checked at the same time.

Related Services