ADAS Error Codes Explained

What Is a Diagnostic Trouble Code?

A DTC is a standardised alphanumeric code stored in a vehicle's Electronic Control Unit when a sensor, actuator or communication line falls outside its expected parameters. Codes follow the SAE J2012 standard: the first character indicates the system (C = chassis, B = body, P = powertrain, U = network), followed by a four-digit number for the specific fault.

For ADAS systems, the most relevant prefixes are C (chassis - covers radar alignment and steering-integrated safety features), B (body - covers camera modules and sensor housings) and U (network - covers CAN bus communication failures between ADAS modules). A basic OBD-II reader will not access most ADAS modules. Professional scan tools are required to read the full fault code set from chassis, body and network control units.

Radar Fault Codes

C110300 - Radar sensor alignment fault. This is the single most common ADAS code in our customer data. It appears across the entire Volkswagen Group range - VW, Audi, Skoda, SEAT and Cupra. The radar module's internal self-check has detected that its beam is no longer pointing along the vehicle centreline. Common triggers: bumper removal or respray, front-end collision, grille replacement, parking sensor work that required bumper removal. Resolution requires static radar calibration using OEM-grade equipment to re-establish correct aim angles.

C110400 - Radar calibrated but system not functioning. A specific VW Group code where the calibration procedure completed successfully but the system still doesn't work. From our case data on VW Golf models, this code often indicates the radar passed its calibration test but another condition is preventing the system from activating - a wheel alignment issue, a CAN bus fault from an unrelated module, or firmware that needs updating before the calibrated data can be used by the ADAS controller.

C1A76 - Blind spot radar sensor fault (rear quarter). Common after rear-quarter bodywork, towbar fitting or trailer socket installation. Blind spot sensors embed in the rear bumper and are sensitive to mounting angle changes. Calibration involves setting the vehicle on a level surface and running the manufacturer's alignment routine through diagnostic software.

P2583-76 - Bosch millimetre-wave radar misalignment. A cross-make code that appears on vehicles using Bosch radar hardware. Seen in our data on Ford, VW Group and Hyundai vehicles. The Bosch radar runs its own internal alignment check independent of the vehicle manufacturer's diagnostics. This code means the radar hardware itself has detected a misalignment that needs correction through the Bosch calibration routine within the OEM software.

C10C700 - Front radar maladjusted. A Mercedes-Benz specific code for the Distronic front radar. Requires XENTRY diagnostic software for full access - aftermarket tools can read this code but cannot run the Mercedes radar calibration procedure without XENTRY or Autel Remote Expert.

Camera Error Codes

B1240 - Forward camera misalignment. The most common camera code after windscreen replacement. The camera mount moved when the glass was changed. Even if the camera was physically reattached in the same position, microscopic differences in glass thickness, curvature and adhesive bond angle shift the reference frame. Static calibration with manufacturer-approved targets is mandatory.

B220600 - Camera VIN coding fault. Seen on Mercedes vehicles. The camera module stores the vehicle's VIN as part of its configuration data. After replacement or in some cases after a software reset, the VIN coding needs to be re-established through XENTRY before the camera will function. This is not a calibration issue - it's a programming issue that must be resolved before calibration can proceed.

B2A60-54 - Static camera aiming incomplete. A cross-make code indicating the static calibration procedure was started but not completed successfully. Common causes: target positioning error, workshop lighting interference, vehicle not on a level surface, or the procedure was interrupted by low battery voltage. The calibration needs to be restarted from scratch in correct conditions.

Dashboard messages that appear alongside these codes vary by manufacturer. Volkswagen Group displays "Front Assist not available." Toyota shows "Pre-Collision System Malfunction." Ford shows "Co-Pilot360 Unavailable." These messages are the customer-facing indication of the underlying fault codes. The messages will not clear until the root cause is resolved and the system passes its self-check.

CAN Bus and Communication Fault Codes

U1000 - CAN bus communication fault (general). The CAN bus is the internal network that connects all electronic modules in the vehicle. U1000 means one or more modules are not communicating as expected. Causes include a blown fuse, corroded wiring connector, a faulty module or electromagnetic interference introduced during a repair. When multiple ADAS warnings appear simultaneously, a U-series code is almost always the root cause.

U0140 - Lost communication with body control module. When ADAS features depend on signals from the BCM - vehicle speed, steering angle, ignition state - a U0140 code can trigger multiple ADAS warnings at once. This is frequently misdiagnosed as a calibration issue. It is a network fault that must be resolved before any calibration is attempted.

In one documented case, a 2023 Hyundai Santa Fe came in after a front-end collision with five simultaneous ADAS faults. The body shop had replaced the bumper and cleared all codes. But a MAP sensor connector knocked loose in the impact was sending intermittent bad data across the CAN bus. That single loose connector cascaded to ABS, ESC, both blind spot modules and the automatic emergency braking system. Five ADAS faults from one engine management sensor that nobody checked.

Rule: when multiple ADAS codes appear at the same time, investigate U-series network codes first. Attempting calibration before network faults are resolved will produce failed calibrations and may generate additional fault codes.

The Toyota No-Code Problem

Toyota and Lexus vehicles present a unique diagnostic challenge. On 2024+ models, the pre-collision system can display a malfunction warning with zero DTCs stored in any module. A full health check using Toyota GTS+ may show no stored or pending codes. The system detects degraded sensor performance through its real-time monitoring without the degradation being severe enough to set a traditional fault code.

The root cause is often Records of Behavior (ROB) data. Toyota stores calibration history and sensor performance logs in the ADAS control module. This ROB data can block a new calibration from completing even when no DTCs exist. Any technician calibrating a Toyota must clear ROB data before starting the procedure. This is unique to Toyota and not documented in most aftermarket tool workflows.

Manufacturer-Specific Diagnostic Requirements

BMW, Mercedes-Benz and Volvo use proprietary code prefixes readable only with manufacturer-specific diagnostic tools. An independent garage using a generic scanner may see a reduced code set or no codes at all, even when faults are present.

Nissan locks out Autel - the most widely used aftermarket diagnostic tool - on 2024+ vehicles. Consult 4 with R2R authentication is required, with login needed at every step: VIN scan, module scan, activations and parameters.

GM blocks counterfeit MDI2 diagnostic interfaces but aftermarket J2534 devices are unaffected. If a GM diagnostic session fails, the interface itself may be the issue rather than the vehicle.

Stellantis vehicles require wiTECH 2.0 with an MDP pod. Using unauthorised diagnostic tools on Stellantis can permanently brick the instrument cluster. One confirmed case involved an AJ Diagnostics box on a 2021 Jeep Grand Cherokee that killed the cluster entirely, requiring full replacement at dealer cost.

The Correct Diagnostic Process

1. Full system scan. Not just the engine management - all available modules including chassis, body and network. This identifies the complete fault code set across every ADAS module.
2. Review freeze frame data. Freeze frame shows the conditions present when the fault was first stored: speed, steering angle, temperature. This distinguishes a genuine calibration fault from a transient electrical issue.
3. Physical inspection. A code alone does not confirm physical damage. The sensor may be dirty, the bracket loose, or a connector intermittently poor. Inspect before condemning.
4. Resolve network faults first. If U-series codes are present, fix the communication issue before attempting any sensor calibration.
5. Calibrate. Once physical causes are resolved, run the OEM calibration procedure for each affected sensor.
6. Verify. Post-scan to confirm all codes are cleared, followed by a verification drive to confirm the system passes its self-test and no new codes are stored.

Clearing codes without addressing the root cause will result in the same codes returning. ADAS fault codes do not clear permanently through code deletion alone. The system must pass its internal diagnostic checks before the warning light extinguishes. Submit your registration and we run a full diagnostic to identify exactly which codes are stored and what resolution they need. See our pricing guide for costs by service type, or read our warning lights guide to match your dashboard message to the likely fault code.