This DTC indicates that the airbag control unit (SRS ECU) has detected a collision event meeting the deployment threshold, permanently written the crash data to the ECU internal non-volatile memory (NVRAM), and activated the crash lock protection mechanism — Seal U
This DTC indicates that the airbag control unit (SRS ECU) has detected a collision event meeting the deployment threshold, permanently written the crash data to the ECU internal non-volatile memory (NVRAM), and activated the crash lock protection mechanism.
In this state, the SRS system enters safe mode, disables further airbag deployment to prevent secondary injury, and illuminates the warning lamp continuously.
A genuine collision event (deployed or recorded without deployment) can trigger this lock.
Crash sensor faults, wiring harness short/open circuits, ECU algorithm miscalculations, or power supply system anomalies can also generate a false record.
Once locked, standard DTC clearing cannot erase the code.
Reset the data using dedicated diagnostic equipment, or replace the ECU.
- 1The vehicle experienced an actual collision (regardless of airbag deployment). The SRS ECU recorded longitudinal/lateral acceleration sensor data and locked the system.
- 2Internal short circuit, open circuit, or signal drift in the front impact sensor, side impact sensor, or central sensor causes the ECU to receive an abnormal acceleration signal.
- 3Damage to the SRS ECU internal memory chip, a software bug, or power supply fluctuations (such as voltage spikes when jump-starting a discharged battery) causing erroneous data writes to the data area.
- 4Working directly on the airbag wiring harness during repairs without disconnecting the battery, or water ingress or oxidation in the yellow connector (airbag-specific) causing abnormal resistance, resulting in a false collision detection.
- 5Failure to replace the locked SRS ECU during accident repairs (some BYD models use a single-use ECU requiring replacement after recording a collision).
- 1Use a dedicated BYD diagnostic tool (VDS2000/3000 or ED400) to access the SRS system. Read the complete fault codes, Freeze Frame data, and Crash Record. Confirm the trigger time, triggered sensor location, and collision severity value (Delta-V).
- 2Check the vehicle repair history against the freeze frame time. Visually inspect the front and rear longitudinal rails, crash beams, B-pillars, and sills for signs of sheet metal repair to confirm whether the event was a genuine collision or a false alarm.
- 3Disconnect the 12V battery negative terminal for 3 minutes. Check all yellow SRS harness connectors (especially the floor harness and sensor connectors) for water ingress or oxidation. Measure the crash sensor resistance (Normal: 2.0–3.0 kΩ; Abnormal: <1 kΩ [short circuit] or >10 kΩ [open circuit]).
- 4If confirmed as a false alarm with no hardware damage: Use the diagnostic tool to perform the 'Crash Data Clear' function and enter the BYD manufacturer-authorized password. If the ECU does not support clearing or clearing fails, replace the SRS ECU with a new unit (part number must match vehicle configuration).
- 5If an actual collision occurred: replace all deployed airbag modules, seat belt pretensioners, and crash sensors, and install a new SRS ECU (do not reuse a locked ECU).
- 6After hardware replacement, perform ECU coding, sensor calibration, and a system self-check. Conduct a road test to confirm DTC B17A200 does not return and the airbag warning light is off.
BYD Qin Pro DM: SRS light stays on after accident repair
Water ingress caused sensor short circuit and false locking.
Collision record locked after battery replacement
SRS ECU internal damage; replacement required