OBD-II code · Network
U045D Invalid Data Received From Automated Driving System Control Module A
A receiving module detected implausible data from automated driving system (ADS) control module A. Trajectory plan, perception fusion or actuator commands fail plausibility checks and are rejected; automated mode degrades or hands back to the driver.
Is it safe to drive with U045D?
The car may go into limp mode (reduced power). Get it diagnosed before a long trip.
Common causes
- Most likelyModule internal fault or sensor input drift
- PossibleSoftware version mismatch after replacement
- Less likelyGateway module routing CAN messages incorrectly
Symptoms
- Multiple warning lights may illuminate
- Affected modules may go into limp mode or shut down
- Specific functions inoperative depending on module
- Diagnostic tools may show communication faults
Repair at a glance
- Difficulty
- Hard
- DIY friendly
- Best left to a mechanic
- Typical labour
- 1–6 h
- Emissions test
- Usually unaffected
- After the fix
- A drive cycle is needed before the light stays off
- Parts involved
- Ads Module A
Related codes
- U045EInvalid Data Received From Automated Driving System Control Module B
- U045AInvalid Data Received From Parking Assist Control Module A
- U045BInvalid Data Received From Anti-Lock Brake System (ABS) Control Module B
- U045CInvalid Data Received From Power Steering Control Module B
- U045FInvalid Data Received From Automated Driving System Interface Module A
- U0460Invalid Data Received From Automated Driving System Interface Module B
Code data: OBDex open dataset (CC0). Labour times are typical ranges, not a quote.