OBD-II code · Network
U053D Invalid Data Received From Image Processing Module C
A receiving module detected implausible data from image processing module C. Object detections, lane lines or sign recognitions fail plausibility checks against other ADAS sensors and are rejected.
Is it safe to drive with U053D?
Usually safe for short trips, but don’t ignore it: the underlying fault can get more expensive over time.
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–4 h
- Emissions test
- Usually unaffected
- After the fix
- A drive cycle is needed before the light stays off
- Parts involved
- Image Processing Module C
Related codes
- U053BInvalid Data Received From Image Processing Module A
- U053CInvalid Data Received From Image Processing Module B
- U053AInvalid Data Received From Entrapment Control Module A
- U0541Invalid Data Received From Entrapment Control Module B
- U0542Invalid Data Received From Headlamp Control Module A
- U0543Invalid Data Received From Headlamp Control Module B
Code data: OBDex open dataset (CC0). Labour times are typical ranges, not a quote.