AutoDTCs – OBD-II Trouble Code LookupAutoDTCs – OBD-II Trouble Code Lookup
  • Home
  • DTC Codes
    • Powertrain (P-Codes)
    • Body (B-Codes)
    • Chassis (C-Codes)
    • Network (U-Codes)
  • Maintenance Procedures
  • About
  • Contact
  • Home
  • DTC Codes
    • Powertrain (P-Codes)
    • Body (B-Codes)
    • Chassis (C-Codes)
    • Network (U-Codes)
  • Maintenance Procedures
  • About
  • Contact
Home / Knowledge Base / Body Systems (B-Codes) / Body / Comfort & Interior / B0090 – Occupant Restraint System Circuit Fault

B0090 – Occupant Restraint System Circuit Fault

SAE B0090 is a Body Circuit Fault code associated with occupant restraint and presence-detection related signals. It indicates the vehicle body-control domain, wiring, or a related sensor circuit is reporting an abnormal, out-of-range, or implausible signal tied to occupant detection or restraint system behavior. This is a system-level descriptor only — it does not name a single failed component or precise location. Interpretation commonly varies by make, model, and year; you should confirm the fault with targeted electrical and network tests before replacing parts.

What Does B0090 Mean?

This article follows SAE J2012 formatting. SAE J2012-DA defines DTC structure and provides standardized descriptions; the SAE J2012-DA digital annex contains the published descriptive text used by scan tools. B0090 is a body (B) class code indicating a circuit or signal fault related to occupant restraint/presence functionality, reported by a body control module or restraint system controller depending on vehicle architecture.

The code shown here has no hyphen suffix and is presented without a Failure Type Byte (FTB). An FTB, if present (for example “-1A”), would act as a subtype that narrows the failure mode (intermittent, high, low, implausible, etc.). Because many manufacturers assign component responsibilities differently, B0090 does not have a single universal component-level meaning; you must confirm with measurements and network/message checks to identify whether wiring, power/ground, sensor signal, or module messaging is at fault.

Quick Reference

  • System: Body — occupant presence/restraint signal circuit
  • Severity: Usually non-drive-limiting but safety-related; can affect airbag/passenger detection features
  • Typical first tests: Scan tool freeze frame, live data, power/ground, signal continuity
  • Common sources: connector corrosion, open/shorted wiring, sensor plausibility, module message errors
  • FTB status: Code shown without FTB; an FTB would specify failure subtype
  • Diagnosis strategy: Test-driven: verify power/ground/reference, measure signals, confirm network messages

Real-World Example / Field Notes

Technicians often see B0090 set after seat removal, connector disturbance, or water ingress near seat electronics. In the shop a common pattern is an intermittent code that clears when the ignition cycles but returns after the occupant sensor harness is flexed — a classic sign pointing at wiring or connector issues rather than an immediate sensor swap. Another pattern is a steady code combined with a related network message timeout on the scan tool, suggesting either a module not communicating or low supply voltage to that node.

When a vehicle arrives with B0090 you should first capture freeze-frame and live-data entries: note timestamped voltages, signal voltages for presence sensors, and any CAN (Controller Area Network) message loss. Measure battery voltage under key-on and cranking; a low battery or poor ground can produce implausible sensor readings. Wiggle-testing connectors while watching live data can reveal intermittent opens; back-probing for reference voltage and ground while comparing to a known-good channel helps isolate wiring versus sensor issues.

On some models, service history shows recurring B0090 after aftermarket seat work or occupant sensor replacement without proper connector seating. In other cases a chassis ground rust spot under the seat produces elevated resistance that corrupts sensor reference levels. Remember: components mentioned here are one possible cause or commonly associated items — always confirm with voltage, resistance, and network message testing before deciding on repairs.

B0090 is a Body-class Diagnostic Trouble Code (DTC) that indicates a fault in the vehicle body electrical domain related to occupant restraint or associated communication circuits. Under SAE J2012-DA formatting this code is classified as a body circuit issue, but the exact component or location can vary by make, model, and year. Interpretation often depends on how the vehicle implements the Supplemental Restraint System (SRS) and its networked sensors. Confirm any theory with measured voltages, continuity checks, and bus/communication diagnostics before replacing parts or modules.

Symptoms of B0090

  • Warning lamp SRS/airbag indicator illuminated or flashing on the dash.
  • Airbag readiness system shows a stored fault and may refuse resets.
  • Occupant detection message or seatbelt buckle warning related to passenger sensing.
  • Intermittent faults that set and clear with ignition cycles or body wiring movement.
  • Communication errors logged in the vehicle network (reduced function of restraint subsystems).
  • Diagnostic tool reports implausible or out-of-range sensor data for restraint-related inputs.

Common Causes of B0090

Most Common Causes

Faulty or intermittent wiring/connectors in the occupant restraint circuit or its communication lines are frequent causes. Corrosion or loose connectors at seat harnesses, under-seat control units, or junction connectors can interrupt power, ground, or signal. A weak or missing reference voltage to a passenger presence sensor or an open/shorted sensor element can also produce this body-class fault. On many vehicles, CAN or low-speed communication interruptions to the Supplemental Restraint System control module are commonly associated.

Less Common Causes

Less commonly, internal processing or input-stage issues in a control module may be the root cause—particularly after all external wiring, power, ground, and signal tests pass. Mechanical damage from prior collisions, water ingress in seat modules, or aftermarket equipment that alters seat wiring or network topology can also lead to this code.

Diagnosis: Step-by-Step Guide

Tools: digital multimeter, 4‑wire oscilloscope or CAN bus analyzer, OBD‑II scan tool with live data and freeze frame, backprobe pins or breakout box, wiring diagrams (vehicle-specific), insulated probe set, service manual for connector locations, and basic hand tools.

  1. Read fault with a scan tool; record freeze frame and any related faults or communication errors to establish context and whether an FTB (failure type byte) is recorded—note that this code is shown here without a hyphen FTB.
  2. Verify the fault is current by clearing codes and cycling ignition; see if B0090 returns and capture live data while reoccurring.
  3. Visually inspect connectors and harnesses for the restraint/seat area and under carpets for damage, corrosion, or aftermarket splice points; tug harnesses gently while watching live data for changes.
  4. With ignition on, measure module power and ground pins for correct battery voltage and good chassis/return continuity; an SRS or restraint module without stable power/ground will set body-class faults.
  5. Backprobe the passenger presence sensor and related signal lines; confirm reference voltage (usually a key 5 V or other spec per service data) and that the sensor signal varies logically with occupancy changes.
  6. Use an oscilloscope or CAN analyzer to check network traffic on the applicable bus (Controller Area Network (CAN)) for errors, bus silence, or malformed frames; compare activity to a known-good baseline if available.
  7. Check resistance/continuity of suspect sensor circuits with power removed; look for shorts to ground or battery and for unexpected high resistance that indicates broken strands or corroded terminals.
  8. If wiring, power, ground, and communication tests pass yet fault persists, perform controlled substitution or isolate modules per service manual—only then consider possible internal processing or input-stage issue in the control module.
  9. After any repair, clear codes and confirm the fault does not return during normal operating cycles; document test values and pass/fail criteria used.

Professional tip: always verify repairs with measured, repeatable evidence—capture before-and-after live data and bus traces. Replace or program control modules only after eliminating wiring, power, ground, and communication as causes; many “module failures” are intermittent connector or network faults in disguise.

Possible Fixes & Repair Costs

Low / typical / high cost estimates depend on the verified fault discovered by testing. Always base repairs on measurement or inspection findings: wiring continuity, reference voltage, ground quality, and signal integrity. If you find a blown fuse or corroded connector with an open circuit on the tested pin, a small parts-and-labor repair is justified. If a sensor or peripheral device fails plausibility testing (stable reference but bad signal), sensor replacement may be required. If all external power, ground, wiring, and communications test good, the remaining possibility is a module-level problem such as a possible internal processing or input-stage issue, and replacement or reflash may be needed only after confirming external inputs.

  • Low: $40–$150 — fuse, terminal cleaning, connector repair, or simple wiring splice confirmed by continuity and voltage checks.
  • Typical: $150–$450 — component replacement (sensor, switch, or harness section) after resistance, voltage, and signal waveform failure on bench or in-circuit tests.
  • High: $600–$1,500+ — module replacement and programming or extensive harness repair when external tests (power, ground, signal, CAN) all pass and the module shows a possible internal processing or input-stage issue.

Cost factors: labor time, part availability, dealer versus independent pricing, diagnostic time to isolate intermittent wiring faults, and whether programming is required. Every repair should be justified by a specific test result: open, short, high resistance, implausible waveform, or confirmed module input-stage failure after external tests pass.

Can I Still Drive With B0090?

Whether you can drive depends on what the B0090 code represents in your vehicle and which system is affected. Some B-codes affect non-critical body functions and are driveable, while others can involve safety systems where driving is not recommended. Use a scan tool to read freeze frame and Mode $06 data, then perform basic power, ground, and signal checks to determine severity. If diagnostic testing shows a safety-related sensor or airbag-related input is compromised, do not drive until repaired.

What Happens If You Ignore B0090?

Ignoring B0090 can lead to loss of related body function, degraded safety features, or an illuminated warning that masks other faults. Intermittent faults may worsen, making later diagnosis harder and potentially increasing repair cost.

Need SRS wiring diagrams and connector views for this code?

SRS/airbag circuit faults require OEM connector views, harness routing diagrams, and approved test procedures. A repair manual helps you verify the exact circuit path safely before touching SRS components.

Factory repair manual access for B0090

Check repair manual access

Related Occupant Restraint Codes

Compare nearby occupant restraint trouble codes with similar definitions, fault patterns, and diagnostic paths.

  • B0019 – Occupant Restraint Airbag Circuit Fault
  • B0014 – Occupant Restraint Circuit Fault
  • B0011 – Occupant Restraint Circuit Fault
  • B0005 – Occupant Restraint Squib Circuit Integrity
  • B0001 – Occupant Restraint Circuit Fault (Airbag)
  • B0097 – Occupant Restraint Circuit Integrity

Last updated: March 1, 2026

Key Takeaways

  • SAE J2012-DA defines DTC structure; B0090 is a body-system level fault whose exact meaning can vary by vehicle.
  • Diagnosis must be test-driven: verify power, ground, and signal integrity before replacing parts.
  • Module replacement is only reasonable after all external inputs, wiring, and network tests pass.
  • Costs vary widely; small wiring fixes are inexpensive, module-level repairs are expensive and require confirmation.

Vehicles Commonly Affected by B0090

B0090 is most often reported on vehicles from manufacturers with complex body control modules and occupant-sensing systems, commonly seen on Toyota, Ford, and General Motors vehicles. These platforms use multiple sensors, seat modules, and CAN-networked body controllers, which increases the chance of a B-type body circuit code showing up for wiring, sensor, or module input-stage issues. Interpretation still varies by make/model/year, so confirm with vehicle-specific testing.

FAQ

Can I clear B0090 myself and see if it returns?

You can clear the code with an OBD-II scanner, but clearing only erases the symptom; it does not fix the cause. If the underlying electrical condition remains—open, short, high resistance, or communication error—the code will likely return and may set additional monitors. Use post-clear testing: check Mode $06, freeze frame, and perform power/ground/signal checks to confirm the fault is resolved before declaring the repair complete.

Can a loose connector cause B0090?

Yes. A loose, corroded, or partially mating connector can create intermittent open or high-resistance connections that produce a B0090. Confirm by performing wiggle tests while monitoring live data and checking for unstable voltages or changing resistance. If continuity or reference voltage drops under movement, repair or replace the connector and retest to ensure the fault does not recur before clearing the code.

Is module replacement always required for B0090?

No. Module replacement is not the first step. Only after verifying stable power, solid ground, correct reference voltages, intact wiring continuity, and proper network messages should you consider a possible internal processing or input-stage issue in the module. Replace a module only when external inputs are confirmed good and the fault persists; document the test results that justify replacement to avoid unnecessary cost.

How long will diagnosing B0090 take at a shop?

Diagnostic time varies with symptom clarity and intermittency. A straightforward wiring or connector fault may be found in one hour with targeted tests. Intermittent or network-related issues can take several hours of tracing, back-probing, and scope work. Shops will typically charge diagnostic time based on hourly rates; expect 1–4 hours for common cases, more for complex intermittent faults requiring longer observation or vehicle simulation.

What tests will a technician perform for B0090?

A technician will first read freeze frame and Mode $06 data, then test battery voltage, reference voltage, and ground at the suspect circuit. Next steps include continuity and resistance checks, back-probing for signal waveform with an oscilloscope, CAN-bus message checks if applicable, and connector inspection. Only after external inputs and network messages are confirmed good would they consider a possible internal processing or input-stage issue in the module.

All Categories
  • Steering Systems
  • Powertrain Systems (P-Codes
  • Suspension Systems
  • Body Systems (B-Codes
  • Wheels / Driveline
  • Chassis Systems (C-Codes
  • CAN Bus / Network Communication
  • Network & Integration (U-Codes
  • Control Module Communication
  • Engine & Powertrain
  • Vehicle Integration Systems
  • Fuel & Air Metering
  • Volkswagen
  • Ignition & Misfire
  • Mitsubishi
  • Emission System
  • BYD
  • Transmission
  • Toyota
  • Hybrid / EV Propulsion
  • Lexus
  • Cooling Systems
  • Mercedes-Benz
  • Body / Comfort & Interior
  • Dodge
  • Airbag / SRS
  • Kia
  • Climate Control / HVAC
  • Hyundai
  • ABS / Traction / Stability
  • Engine & Powertrain
  • Fuel & Air Metering
  • Ignition & Misfire
  • Emission System
  • Transmission
  • Hybrid / EV Propulsion
  • Cooling Systems
  • Body / Comfort & Interior
  • Airbag / SRS
  • Climate Control / HVAC
  • ABS / Traction / Stability
  • Steering Systems
  • Suspension Systems
  • Wheels / Driveline
  • CAN Bus / Network Communication
  • Control Module Communication
  • © 2026 AutoDTCs.com. Accurate OBD-II DTC Explanations for All Makes & Models. About · Contact · Privacy Policy · Disclaimer