ADAS Error Codes Explained

What Is a Diagnostic Trouble Code (DTC)?

A DTC is a standardised alphanumeric code stored in a vehicle's Electronic Control Unit (ECU) 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 indicating 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 professional scan tool is required to read these codes; a basic OBD-II reader will not access all ADAS modules.

Common Radar Fault Codes

C1101 — Radar sensor alignment fault. This code indicates the radar module's internal self-check has detected that its beam is no longer pointing along the vehicle's centreline. Common triggers include a front bumper impact (even a minor one), bumper removal during bodywork, or sensor bracket damage. Resolution requires professional radar calibration using OEM-grade equipment to re-establish the correct horizontal and vertical aim angles.

C1234 / C1A67 — Radar signal blockage or obstruction. These codes appear when the radar cannot transmit or receive signals at expected strength. Causes include mud, ice, snow, or a damaged radar cover (radome). After clearing the physical obstruction, a short calibration drive is usually needed to confirm the system is operating within specification. If the radome is cracked or discoloured, it must be replaced before calibration.

C1A76 — Blind spot radar sensor fault (rear quarter). This code is common after rear-quarter bodywork, tow bar fitting, or trailer socket installation. The blind spot sensors are embedded in the rear bumper and are highly sensitive to mounting angle changes. Calibration involves setting the vehicle on a level surface and running the manufacturer's alignment routine via diagnostic software.

Common Camera Error Codes

B1240 — Forward camera misalignment. This is the most frequently seen ADAS code after windscreen replacement. The camera module mounts directly to the windscreen and must be re-calibrated every time the glass is changed. Even if the camera is physically re-attached in the same position, microscopic differences in glass thickness, curvature, and the adhesive bond angle mean the reference frame shifts. Static calibration with manufacturer-approved targets is mandatory.

B1B02 — Camera module internal fault or image degradation. This code can indicate a dirty or fogged lens, a failing camera module, or software that cannot process the image data it is receiving. First step is cleaning the lens. If the code persists, the camera module may need replacement followed by calibration. Some manufacturers bundle B1B02 with a required software update.

UK dashboard messages such as 'Front Assist not available' (Volkswagen Group), 'Camera view obstructed' (Toyota Safety Sense), and 'Lane Assist Unavailable' (Ford Co-Pilot360) are the customer-facing indication of underlying B-series camera fault codes. These 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 (Controller Area Network) bus is the internal network that allows ADAS modules to share data with each other and with the main ECU. U1000 means one or more modules are not communicating as expected. Causes include a blown fuse, corroded wiring connector, a faulty module, or interference introduced during a repair.

U0140 — Lost communication with body control module. When ADAS features depend on signals from the BCM (such as vehicle speed or steering angle), a U0140 code can trigger multiple ADAS warnings simultaneously. This is often misdiagnosed as a calibration issue — it is actually a network fault that must be resolved before calibration is attempted.

When multiple ADAS codes appear at the same time, always investigate U-series network codes first. Attempting calibration before network faults are resolved will produce failed calibrations and risk generating additional fault codes.

Manufacturer-Specific Code Behaviour

Not all ADAS fault codes use the generic SAE format. BMW, Mercedes-Benz, and Volvo use proprietary code prefixes that are only readable with manufacturer-specific diagnostic tools (BMW ISTA, Mercedes XENTRY, Volvo VIDA). An independent garage using a generic scanner may see a reduced code set or no codes at all, even when a fault is present.

Volkswagen Group vehicles (VW, Audi, SEAT, Skoda) use VAG-COM codes alongside generic DTCs. Toyota Safety Sense faults are logged in a dedicated TSS module that requires Toyota Techstream or an equivalent professional scanner. If your vehicle is showing ADAS warning lights but a high-street scanner finds nothing, the codes are likely stored in a manufacturer-specific module that requires specialist equipment.

The Correct Diagnostic and Resolution Process

Step one is a full system scan using appropriate diagnostic equipment — not just the engine management system, but all available modules including chassis, body, and network. Step two is reviewing freeze frame data, which shows the exact conditions present when the fault was first stored (speed, steering angle, temperature). This helps distinguish a genuine calibration fault from a transient electrical issue.

Step three is a physical inspection of all sensors and their mounting points. A code alone does not confirm physical damage — the sensor may be dirty, the bracket may be loose, or a connector may be intermittently poor. Step four, once physical causes are ruled out or resolved, is calibration. Step five is clearing the codes and performing a verification drive to confirm the system passes its self-test and no new codes are stored.

It is important to note that 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 will extinguish.