ADAS Error Codes Explained
When an ADAS fault is stored by your vehicle's control module, it's recorded as a Diagnostic Trouble Code. Understanding which codes require calibration vs part replacement vs network repair saves time and money. This guide covers the codes US technicians see most often, with real diagnostic cases and the resolution path for each.
How ADAS Diagnostic Codes Work
A DTC is a standardized alphanumeric code stored in an Electronic Control Unit when a sensor or communication line falls outside parameters. Codes follow SAE J2012: the first character indicates the system (C = chassis, B = body, P = powertrain, U = network), followed by a four-digit fault number.
For ADAS, the relevant prefixes are C (radar alignment, steering-integrated safety), B (camera modules, sensor housings), and U (CAN bus communication between ADAS modules). A basic OBD-II reader won't access most ADAS modules. Professional scan tools are needed to read the full code set from chassis, body and network controllers.
Radar Fault Codes
C110300 - Radar sensor alignment fault. The most common ADAS code on VW Group vehicles (VW, Audi). The radar's internal self-check detected its beam is no longer pointing along the vehicle centerline. Triggers: bumper work, front-end collision, grille replacement. Fix: static radar calibration with OEM equipment.
C110400 - Radar calibrated but system not functioning. VW Group code where calibration completed but the system won't activate. From US case data, this often indicates the radar passed calibration but another condition prevents activation - a wheel alignment issue, CAN bus fault, or firmware needing an update before the calibrated data can be used.
P2583-76 - Bosch millimeter-wave radar misalignment. Cross-make code on vehicles using Bosch radar hardware. Seen on Ford, VW Group and Hyundai vehicles. The Bosch radar runs its own alignment check independent of the vehicle manufacturer's diagnostics.
C1A76 - Blind spot radar sensor fault. Common after rear-quarter body work, trailer hitch installation or rear-end collision. BSM sensors in the rear bumper are sensitive to mounting angle changes. On GM EVs (Cadillac Lyriq, Hummer EV), the right BSM communicates through the left module - if left is damaged, both appear dead.
Camera Error Codes
B1240 - Forward camera misalignment. Most common camera code after windshield replacement. The camera moved when glass was changed. Static calibration with manufacturer-approved targets is mandatory. Even if the camera was reattached in the same spot, microscopic glass differences shift the reference frame.
B2A60-54 - Static camera aiming incomplete. Cross-make code indicating calibration started but didn't complete. Causes: target positioning error, lighting interference, vehicle not level, or battery voltage dropped mid-procedure. Restart from scratch in correct conditions.
Dashboard messages behind these codes vary by make. Toyota shows "Pre-Collision System Malfunction." Ford shows "Co-Pilot360 Unavailable." Chevy shows "Forward Collision Alert Unavailable." These messages clear when the underlying code is resolved and the system passes its self-check.
CAN Bus and Communication Codes
U1000 - CAN bus communication fault. The CAN bus connects all electronic modules. U1000 means modules aren't communicating correctly. Causes: blown fuse, corroded connector, faulty module, interference from a repair. When multiple ADAS warnings appear at once, a U-series code is almost always the root cause.
U0140 - Lost communication with body control module. ADAS features depend on BCM signals (vehicle speed, steering angle). U0140 triggers multiple ADAS warnings simultaneously. Often misdiagnosed as a calibration issue - it's a network fault that must be fixed before any calibration.
In a 2023 Hyundai Santa Fe case, a MAP sensor knocked loose during a collision sent intermittent bad data across the CAN bus. ABS, ESC, both blind spot sensors and AEB all faulted - five ADAS warnings from one engine management sensor. The body shop never checked it because it wasn't in the "collision zone." This is why full-system scans matter.
Rule: when multiple ADAS codes appear together, resolve U-series network codes first. Calibrating sensors before fixing the network produces failed calibrations and can generate additional codes.
The Toyota No-Code Problem
2024+ Toyota and Lexus vehicles can show "Pre-Collision System Malfunction" with zero DTCs. Even GTS+ may show a clean scan. The system detects degraded performance through real-time monitoring without setting a code. The root cause is often Records of Behavior (ROB) data that must be cleared before calibration. See our Toyota pre-collision guide for the full diagnostic approach.
Manufacturer-Specific Tool Requirements
Nissan 2024+: Autel locked out. Consult 4 with R2R authentication required at every diagnostic step. This affects the most popular aftermarket tool in the US market.
Mercedes: XENTRY mandatory for Distronic and newer systems. $40,000+ initial investment. Autel Remote Expert is an alternative at lower cost but doesn't cover all procedures.
Stellantis (Jeep, Ram, Chrysler, Dodge): wiTECH 2.0 with MDP pod only. Unauthorized diagnostic tools have been confirmed to permanently brick instrument clusters. One documented case on a 2021 Jeep Grand Cherokee destroyed the cluster.
GM: Blocks counterfeit MDI2 interfaces. Aftermarket J2534 devices (Cardaq Plus 3, Bosch J-Box) work fine. VIP architecture on newer models may need manual VIN entry.
BMW: ISTA+ via bmwtechinfo.com at $32/day. Slow service reported by US technicians.
The Correct Diagnostic Process
- Full system scan - all modules: chassis, body, network. Not just engine management.
- Review freeze frame data - conditions when the fault first stored (speed, steering angle, temperature).
- Physical inspection - dirty sensor, loose bracket, intermittent connector. A code doesn't confirm physical damage.
- Resolve network faults first - fix U-series codes before any sensor calibration.
- Calibrate - OEM procedure for each affected sensor.
- Verify - post-scan plus verification drive to confirm the system passes its self-test.
Clearing codes without fixing the cause means the same codes return within minutes. ADAS systems self-check continuously. Submit your VIN for a full diagnostic. See our cost guide for pricing or warning lights guide to match your dashboard message to the likely code.
ADAS Error Codes Explained — Common Questions
Answers to frequently asked questions on this topic
A basic OBD-II reader can clear engine codes but most ADAS modules sit in separate chassis or body ECUs needing a professional scan tool. Even if you clear the code, it returns if the cause isn't fixed.