A loose, corroded, or damaged connector at the Automated Driving System Interface Module A or at a CAN bus splice point.; Open or shorted wiring in the CAN bus circuit between the interface module and the rest of the network.; A blown fuse or poor ground connection supplying power to the interface module.; Water intrusion or corrosion in the module's connector or housing, common in areas exposed to road spray.; A failed Automated Driving System Interface Module A itself, due to internal electronics failure.; A software or calibration issue in the interface module or in a module that communicates with it.; A fault in another module on the same CAN bus that disrupts communication for all nodes.

DTC codes / U01xx · Lost communication with a control module / U015E

U015ELost Communication With Automated Driving System Interface Module A

U015E is a generic network communication code indicating that one or more control modules have stopped receiving messages from the Automated Driving System Interface Module A over the vehicle's Controller Area Network (CAN) bus. The detecting module sets this code when the expected periodic data frames from that interface module fail to arrive within a defined timeout window, which can happen because of a wiring fault, a power or ground problem, or an internal failure in the module itself.

SystemNetwork

Code typeGeneric (all makes)

SeverityMedium

Fix difficultyProfessional

AreaLost communication with a control module

Symptoms you may notice

A warning light or message on the dashboard indicating a driver-assist or automated driving system fault.
The automated driving features, such as adaptive cruise control or lane-centering assist, may become unavailable or default to a manual mode.
Other unrelated warning lights may illuminate if the failed module shares a communication bus with other systems.
Intermittent operation of driver-assist features, especially over bumps or in wet conditions, pointing to a wiring issue.
Often no symptoms besides the warning light, because the vehicle may still drive normally with the automated driving interface offline.

Common causes, most likely first

A loose, corroded, or damaged connector at the Automated Driving System Interface Module A or at a CAN bus splice point.
Open or shorted wiring in the CAN bus circuit between the interface module and the rest of the network.
A blown fuse or poor ground connection supplying power to the interface module.
Water intrusion or corrosion in the module's connector or housing, common in areas exposed to road spray.
A failed Automated Driving System Interface Module A itself, due to internal electronics failure.
A software or calibration issue in the interface module or in a module that communicates with it.
A fault in another module on the same CAN bus that disrupts communication for all nodes.

How to diagnose and fix it

Connect a scan tool and record all stored codes in every module, then clear codes and test-drive to see if U015E returns immediately or only under specific conditions.
Inspect the Automated Driving System Interface Module A for visible damage, loose connectors, and corrosion, and check that all pins are fully seated.
Check the fuse and ground circuits for the interface module using a multimeter, verifying battery voltage at the module's power pin with the key on.
Perform a CAN bus voltage and resistance test at the diagnostic connector to confirm the bus is not shorted or open, and compare readings with manufacturer specifications.
Wiggle-test the harness and connectors while watching live data for the interface module to catch intermittent faults.
If wiring and power are good, substitute a known-good module of the same part number or perform a module swap to confirm the fault follows the module.
After repair, clear codes and perform any required relearn or calibration procedures for the automated driving system, then verify communication is restored.

What a U015E really tells you

This code does not automatically mean the interface module is dead; a single chafed wire or a corroded ground can set the same communication timeout.
A weak or failing battery or charging system can cause sporadic CAN bus communication faults that mimic a failed module, so always load-test the battery first.
Other modules on the same bus can set U015E if they lose power or ground, so check for additional codes that point to a shared power or ground splice.
Aftermarket accessories wired into the CAN bus or tapping into the interface module's harness are a common cause of communication disruptions that set this code.
Some vehicles require a specific ignition cycle or sleep cycle before the interface module will rejoin the network after a repair, so a code that persists immediately after clearing may not indicate a failed repair.

Can I keep driving with U015E?

The vehicle is generally safe to drive because the automated driving features will be disabled, but you should avoid relying on any driver-assist functions until the fault is repaired. If the warning light is accompanied by other system failures or drivability issues, have the vehicle inspected promptly.

Tools that help

Tools we recommend are in the Auto Veteran shop on Amazon. As an Amazon Associate we earn from qualifying purchases.

Guidance is general and written for all OBD-II vehicles. Exact tests and values vary by model, so confirm the fault before replacing parts.