OBD-II code · Network
U0405 Invalid Data Received from Cruise Control Module
The Cruise Control Module is present on the data bus but the values it reports are implausible — out of range, frozen, or failing the checksum or rolling-count check. The receiving modules reject the data. Cruise control is disabled. Causes include a faulty sensor feeding the module, internal computation errors, a software or calibration mismatch after a repair, or bus interference corrupting the frames.
Is it safe to drive with U0405?
Usually safe to drive in the short term. Get it diagnosed when convenient, sooner if the car drives differently.
Common causes
- PossibleCruise module internal fault
- PossibleCAN corruption causing checksum errors
- 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
- Medium
- DIY friendly
- Best left to a mechanic
- Typical labour
- 1–4 h
- Emissions test
- Usually unaffected
- Parts involved
- Cruise Control Module, Can Bus Wiring
Related codes
- U0402Invalid Data Received from TCM
- U0403Invalid Data Received from Transfer Case Control Module
- U0404Invalid Data Received from Gear Shift Control Module
- U0406Invalid Data Received from Cruise Control Front Distance Range Sensor
- U0407Invalid Data Received from Steering Angle Sensor Module
- U0408Invalid Data Received from Vehicle Immobilizer Control Module
Code data: OBDex open dataset (CC0). Labour times are typical ranges, not a quote.