Airbag Light Five Minutes In — Airbags Off for the Rest of the Drive

The Challenge

An SRS lamp isn't a live sensor reading. It is the restraints control module latching a failed self-test on a firing circuit — and the system fails safe by taking the affected restraint stage offline. The "warning light" and the "non-functioning airbag" are the same fault: while the lamp is lit, at least one stage is silently inoperative, and the lamp is the only warning the driver ever gets. It is also a UK MOT failure, which is what brings most of these cars into the workshop.

The trap is that three very different faults produce the identical lamp: a low or drifting 12V supply logging spurious codes across modules, a lost-comm fault (the U0151 family — power, ground or CAN to the restraints module, nothing to do with the airbags), or a genuine break in a squib circuit — clock spring, under-seat connector, occupancy mat, pretensioner, impact sensor. Replacing parts before splitting those three is how airbag jobs go wrong. And there is a hard safety rule underneath it all: never probe a squib circuit with a powered multimeter — meter current can fire the charge.

What the Onset Timing Already Proves

The five-minute delay is the unusual part of this complaint, and it does real diagnostic work before a scanner is plugged in. The lamp passes its key-on prove-out — lights with ignition, goes out — so the bulb and cluster work, and the RCM's ignition-on self-test passes. Whatever is wrong is not wrong at key-on. The RCM then monitors the firing loops continuously, so a lamp at minute five means a circuit that is healthy cold and fails warm and under way: a marginal circuit, its resistance drifting with heat and vibration — not the clean break that latches the lamp straight after prove-out.

Two more things follow. The lamp appears at a standstill with the engine running, so the fault does not need the car moving — that points away from purely movement-gated causes (steering input working a clock spring, seat travel working an under-seat connector) and keeps thermal drift and charging-system voltage drift firmly on the table: an alternator wandering out of the 13.8–14.8 V band minutes into a run is a classic delayed-lamp cause. And a plain clear-and-key-cycle cannot be trusted as a fix — any repair has to survive running past the onset window. The five-minute figure, annoying as a symptom, is a gift as a test protocol: the fault reproduces on demand.

Structuring the Diagnostic

What the timing cannot do is name the circuit — supply, comms and squib faults can all present this way. That split is what the EvmetricsOBD Workshop Templates structure: the Airbag / SRS template works supply, then comms, then squib circuits, with the safety gate built in before any component is unplugged — and with the onset timing captured as evidence rather than an anecdote.

The Split Ahead

The next session on the car is defined. First the supply: rested battery voltage, then the control-module voltage (PID 0142) logged through minute five and beyond with the engine running — the delayed onset makes the charging system the prime cheap suspect, and it costs nothing to test (contrast the diesel crank-no-start case, where a browning-out bus produced phantom faults across unrelated modules; voltage decides whether any code can be trusted at all).

Then the restraints module directly. A generic Mode 03 scan often comes back quiet for SRS faults — restraint codes are B-codes living in the restraints module, not emissions codes in the engine ECU — so the scan asks the module itself: on JLR, UDS to the RCM (header 737) and the occupant module (OMM, header 752). The U0151 family would send the job to RCM power, ground and CAN; a B-code naming a deployment loop sends it to that circuit's connectors and harness — behind the safety gate of battery off, capacitor wait, and no powered meter near a firing loop. EvmetricsOBD's offline DTC database carries the generic SAE restraint B-codes, so whatever the module reports resolves to a name on the spot.