B1785: Front Left Occupant Collision Record

Stored crash data

What B1785 means

The occupant classification system weighs and tracks what is in the seat so the module can decide how, or whether, to fire the airbag for that position. Its sensors sit under the seat cushion and feed a small ECU. When the front left sensor reports a load event that matches a collision, the module writes B1785 as a record of that event rather than as a live circuit reading.

There are two very different reasons this code appears. One is a real impact, where the record belongs there and the restraint system needs a full inspection before anything is cleared. The other is a sensor that was shocked or overloaded without a crash, such as a heavy object dropped into the seat or seat removal handled roughly, which is why the definition allows a zero point calibration to clear it when no collision took place.

Common causes

• An actual collision that loaded the front left seat sensor hard enough to log the event
• A heavy object dropped onto the driver seat cushion with the ignition on
• Seat removal or installation that flexed or torqued the sensor mounts
• Aftermarket seat covers, seat heaters, or cushions that preload the classification sensor
• A sensor or its ECU that drifted out of calibration and read the load as impact
• A previous repair that skipped the zero point calibration after seat work

Crash data or hardware fault?

This one lives with the crash data codes because it is a stored event, not a resistance reading that comes and goes. The module wrote it once and holds it. The definition on this code carves out one exception: when no collision happened, a zero point calibration performed on the vehicle can clear it. After a real deployment, the crash record in the module needs a reset before the system will arm again.

Does our reset clear it?

If the vehicle was in a crash and the module is holding deployment data along with B1785, our mail in reset is what returns the module to a ready state after the physical repairs are done. If no collision took place, start with the zero point calibration on the vehicle, since that is the intended path for this code and it costs nothing but time. Never clear a genuine crash record without replacing what deployed.

Which makes throw it

Lexus and Toyota both use B1785 with the same meaning, tied to the occupant classification system used in their front passenger and driver seating positions. The calibration procedure differs a little by model, so follow the service information for the specific chassis.

What to do next

First decide whether this vehicle has actually been hit, because everything downstream depends on that answer. Check for deployed airbags, a locked seat belt retractor, and body damage on the left side. With no collision history, empty the seat completely and run the zero point calibration. If the code returns after a clean calibration, the sensor or the classification ECU is the suspect, and if there was a deployment, mail us the module for a reset once the replacement parts are in. Related codes: B1695, B1787, B1670.