Code
B1151
HUMMER
B — Body
Deployment Commanded - Frontal
Views:
UK: 9
EN: 24
RU: 15
AI status
Completed
Completed
100%
Causes
- Actual frontal crash resulting in deployment command
- Impact/crash sensor(s) detecting event above threshold
- Short, open, or intermittent wiring in SIR squib or sensor circuits
- Corrosion, water intrusion, or damaged connectors at SIR module or sensors
- Internal SIR (SDM/RCM) logic fault or internal module error
- Stored event from previous deployment that was not cleared after repairs
Symptoms
- Frontal airbag(s) deployed or evidence of deployment
- SRS/airbag warning lamp illuminated or flashing on instrument panel
- Crash data or freeze frame present in SIR/SDM module memory
- Seat belt pretensioner deployment or damaged restraint components
- Vehicle may show obvious front-end damage or occupant injury reports
- No-start or other electrical anomalies if module triggered protection modes
What to check
- Visually inspect vehicle for evidence of deployment and any crash damage
- Using a scan tool, read and record all SIR/SRD/SDM codes and freeze frame data
- Confirm whether airbags and pretensioners are deployed (do not attempt to power or test deployed squibs)
- Inspect connectors and harnesses at the SIR module and front crash sensors for corrosion, damage, or loose terminals
- Verify battery voltage and ground integrity at time of code (freeze frame), check for recent battery disconnects or low-voltage events
- Check service history for prior crash repairs and whether SIR components were replaced according to manufacturer requirements
Signal parameters
- SIR deployment command bit/state (set/cleared)
- Freeze frame vehicle speed at event (km/h or mph)
- Accelerometer/impact sensor peak G values and direction
- Battery voltage and ignition state at time of event
- Seat occupancy/weight sensor state (if applicable)
- Pretensioner activation flags
Diagnostic algorithm
- Record all DTCs and freeze frame data with an appropriate SRS-capable scan tool; do not clear codes before inspection
- Visually confirm whether airbags/pretensioners are deployed. If deployed, follow manufacturer procedure: remove and replace deployed modules, squibs, pretensioners, and any damaged components
- Inspect front impact sensors, mounting points, and wiring for physical damage or corrosion. Repair harness damage and damaged connectors per repair manual
- With ignition off and battery disabled per safety procedure, measure squib/pretensioner resistance and continuity where allowed by manufacturer; compare to spec. Do not apply power to squib circuits
- Restore power only after repairs and use scan tool to clear crash/event codes. Some modules will store a crash event that cannot be cleared until specific repairs are completed or module replacement is done
- If no physical deployment is found but B1151 is stored, perform detailed wiring harness continuity and short checks between sensors, squibs and the SIR module, paying attention to chafing points and body-to-harness areas
- If module internal fault suspected after wiring and component checks, follow manufacturer diagnostic flow for SIR/SDM replacement and programming; replace module only if required and reconfigure with scan tool
- After repairs, perform SIR self-test with scan tool and verify readiness. Confirm no additional codes and perform road test if required by procedure
Likely causes
- Vehicle experienced a collision triggering deployment
- Front impact sensor or accelerometer reported high G event
- Damaged airbag squib or pretensioner circuit (short to ground or battery)
- Corroded connector or damaged harness near module or sensor
- Previous crash repairs incomplete (deployed components not replaced or connectors left disconnected)
Fault status
Status
Stored when the SIR (airbag) module has commanded frontal airbag deployment. Indicates the module detected crash conditions or internal logic caused a deployment command; requires inspection for actual deployment and verification/repair of SIR components and wiring.
Repair difficulty: Hard
Diagnostic time: 3.0-6.0 hours
Similar codes
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
B1151
LAND ROVER
B — Body
cushion passenger seat passenger seat backrest motorista
Views:
UK: 8
EN: 20
RU: 11
AI status
Completed
Completed
100%
Causes
- Actual frontal crash resulting in deployment command
- Impact/crash sensor(s) detecting event above threshold
- Short, open, or intermittent wiring in SIR squib or sensor circuits
- Corrosion, water intrusion, or damaged connectors at SIR module or sensors
- Internal SIR (SDM/RCM) logic fault or internal module error
- Stored event from previous deployment that was not cleared after repairs
Symptoms
- Frontal airbag(s) deployed or evidence of deployment
- SRS/airbag warning lamp illuminated or flashing on instrument panel
- Crash data or freeze frame present in SIR/SDM module memory
- Seat belt pretensioner deployment or damaged restraint components
- Vehicle may show obvious front-end damage or occupant injury reports
- No-start or other electrical anomalies if module triggered protection modes
What to check
- Visually inspect vehicle for evidence of deployment and any crash damage
- Using a scan tool, read and record all SIR/SRD/SDM codes and freeze frame data
- Confirm whether airbags and pretensioners are deployed (do not attempt to power or test deployed squibs)
- Inspect connectors and harnesses at the SIR module and front crash sensors for corrosion, damage, or loose terminals
- Verify battery voltage and ground integrity at time of code (freeze frame), check for recent battery disconnects or low-voltage events
- Check service history for prior crash repairs and whether SIR components were replaced according to manufacturer requirements
Signal parameters
- SIR deployment command bit/state (set/cleared)
- Freeze frame vehicle speed at event (km/h or mph)
- Accelerometer/impact sensor peak G values and direction
- Battery voltage and ignition state at time of event
- Seat occupancy/weight sensor state (if applicable)
- Pretensioner activation flags
Diagnostic algorithm
- Record all DTCs and freeze frame data with an appropriate SRS-capable scan tool; do not clear codes before inspection
- Visually confirm whether airbags/pretensioners are deployed. If deployed, follow manufacturer procedure: remove and replace deployed modules, squibs, pretensioners, and any damaged components
- Inspect front impact sensors, mounting points, and wiring for physical damage or corrosion. Repair harness damage and damaged connectors per repair manual
- With ignition off and battery disabled per safety procedure, measure squib/pretensioner resistance and continuity where allowed by manufacturer; compare to spec. Do not apply power to squib circuits
- Restore power only after repairs and use scan tool to clear crash/event codes. Some modules will store a crash event that cannot be cleared until specific repairs are completed or module replacement is done
- If no physical deployment is found but B1151 is stored, perform detailed wiring harness continuity and short checks between sensors, squibs and the SIR module, paying attention to chafing points and body-to-harness areas
- If module internal fault suspected after wiring and component checks, follow manufacturer diagnostic flow for SIR/SDM replacement and programming; replace module only if required and reconfigure with scan tool
- After repairs, perform SIR self-test with scan tool and verify readiness. Confirm no additional codes and perform road test if required by procedure
Likely causes
- Vehicle experienced a collision triggering deployment
- Front impact sensor or accelerometer reported high G event
- Damaged airbag squib or pretensioner circuit (short to ground or battery)
- Corroded connector or damaged harness near module or sensor
- Previous crash repairs incomplete (deployed components not replaced or connectors left disconnected)
Fault status
Status
Stored when the SIR (airbag) module has commanded frontal airbag deployment. Indicates the module detected crash conditions or internal logic caused a deployment command; requires inspection for actual deployment and verification/repair of SIR components and wiring.
Repair difficulty: Hard
Diagnostic time: 3.0-6.0 hours
Similar codes
Workshop Manuals
Repair manuals for LAND ROVER
3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualYour experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email