This DTC indicates the Integrated Inertial Sensor (IIS) in the ESP (Electronic Stability Program) system lacks initial calibration, or the calibration data is abnormal or invalid — Atto 3
This DTC indicates the Integrated Inertial Sensor (IIS) in the ESP (Electronic Stability Program) system lacks initial calibration, or the calibration data is abnormal or invalid.
The Integrated Inertial Sensor integrates a high-precision MEMS accelerometer and gyroscope to monitor the vehicle’s longitudinal acceleration, lateral acceleration, and yaw rate in real time.
The ESP uses these core input signals for body stability control, anti-skid calculations, and Automatic Emergency Braking (AEB) decisions.
The ECU sets this DTC when it detects a significant deviation between the sensor output and the expected reference, when the calibration data area checksum validation fails, or when the installation attitude angle exceeds the permitted tolerance.
This condition forces the ESP system into a degraded mode, restricting or disabling functions such as the Anti-lock Braking System (ABS), Traction Control System (TCS), Vehicle Dynamics Control (VDC), and AUTOHOLD.
In extreme cases, this compromises driving safety.
- 1Reinstalling the ESP/IPB control unit assembly after accident repair, chassis removal and installation, or a collision altered the installation angle or levelness, causing the inertial sensor to lose its reference attitude.
- 2Severe impact to the vehicle underbody (such as bottoming out, deep pothole impact, or collision) causing a slight shift in the sensor's physical position or zero-point drift in the internal MEMS chip.
- 3Failure to perform the initial Sensor Calibration procedure after installing a new ESP hydraulic modulator assembly, or failure to keep the vehicle absolutely level during calibration.
- 4Internal fault in the integrated inertial sensor (MEMS chip aging, cold solder joint, internal IC damage) or corrupted ECU internal EEPROM data, resulting in unreadable calibration parameters or verification failure.
- 5Defective control unit software version, flashing error, or abnormal power interruption corrupting the calibration data area.
- 1Pre-inspection preparation: Park the vehicle on level ground (recommended hoist platform levelness error <0.5°) and center the steering wheel. Check the ESP/IPB control unit mounting bracket for deformation. Verify the fixing bolt torque meets specification (typically 8-12Nm). Confirm the mounting surface is free of debris and the control unit is level.
- 2Fault confirmation: Connect a dedicated diagnostic tool such as BYD VDS or Launch X-431, enter the ABS/ESP system, read and record all fault codes, and check for C00A800 and accompanying faults such as C006102 (lateral acceleration sensor) and C006202 (longitudinal acceleration sensor).
- 3Software calibration: Select 'Special Functions' → 'Inertial Sensor Calibration' (Sensor Calibration/IIS Calibration). Follow the prompts: keep the vehicle stationary, do not press the brake pedal, and do not turn the steering wheel. Execute the calibration procedure (usually 30-60 seconds) until the diagnostic tool displays 'Calibration successful'.
- 4Function verification: Clear all fault codes. Turn off the vehicle, wait 5 minutes, then power on again. Confirm C00A800 does not reappear. Perform a road test (including straight-line driving and moderate steering). Verify the ESP warning light turns off and the lateral/longitudinal acceleration values in the data stream are within a reasonable range (close to 0±0.1g when stationary, varying normally during steering).
- 5Hardware replacement: If calibration fails repeatedly, the fault recurs intermittently after calibration, or internal circuit fault codes are present, replace the ESP hydraulic modulator assembly with ECU. After replacement, perform the calibration and brake system bleeding procedures.
Seal ESP warning light stays on — calibration skipped after chassis repair
E5 sensor calibration lost after collision repair
BYD Dolphin: Intermittent multi-system warning lights illuminated — software refresh resolved it