U0405

Code

Generic U — Network/User

Invalid Data Received From Cruise Control Module

Brand: Generic

Type: U — Network/User

Views: UK: 37 EN: 139 RU: 68

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Faulty cruise control module (internal fault or corrupted firmware)
Intermittent or open/shorted wiring or connector between cruise module and vehicle bus(s)
Corroded/damaged connectors or poor ground at cruise or receiving module
CAN/LIN bus fault (short to voltage/ground, high resistance, missing termination)
Other module sending incorrect/garbled messages
Incorrect or incomplete module programming/calibration (software mismatch)

Symptoms

MIL (Check Engine) or warning lamp illuminated
Cruise control disabled or inoperative
Intermittent loss of cruise control or erratic activation behavior
Other systems that depend on cruise data (speed-related functions) may show faults or operate incorrectly
Stored U0405 and possibly related communication U-codes (U0100, U0121, etc.)

What to check

Connect a OEM-capable scan tool and read all stored U-codes and related freeze frame data
Check for other active/inactive communication DTCs (U0100, U0073, U0121, etc.)
Verify vehicle battery voltage stable and proper module supply/ground voltages
Visually inspect cruise control module connector and wiring for corrosion, damage, or water intrusion
Inspect CAN/LIN bus wiring routing for chafing, pinched sections or recent repairs
Use oscilloscope or CAN bus monitor to check message traffic, error frames and physical layer signals on CAN_H/CAN_L

Signal parameters

CAN physical idle voltages: both CAN_H and CAN_L near midpoint (~2.5 V) when recessive; dominant state typically shows CAN_H ≈ 3.5 V and CAN_L ≈ 1.5 V (differential ≈2 V)
Typical CAN message frequency: cruise-related messages commonly 1–10 Hz (check OEM spec)
Message contents to check: speed, set/resume flags, enable/disable status, checksum or CRC field
Supply voltage to module: nominal battery voltage (11–14.5 V with engine running)
Ground resistance: low (

Diagnostic algorithm

Retrieve all DTCs and freeze frame with a capable scan tool. Note time/states when U0405 set.
Check battery voltage and module power/ground circuits. Repair any low voltage or bad ground first.
Perform visual inspection of cruise control module connector and harness. Repair corroded pins, broken wires or water damage.
Use a scan tool to attempt live data from the cruise control module. If module does not respond, suspect loss of communication or module failure.
Monitor CAN bus traffic with a scope or CAN sniffer. Confirm cruise control messages are present, check message rate, integrity (CRC/checksum), and look for bus error frames.
Measure static and dynamic voltages on CAN_H and CAN_L at the cruise module and at the receiving module. Compare to spec and to each other to find shorts/open circuits.
Backprobe and wiggle suspected wiring while monitoring communications to reproduce intermittent faults.
Isolate sections of the bus if multiple modules share it — disconnect nodes (per OEM procedure) to identify the faulty device or wiring segment.
If wiring and bus are good and the module is reachable but sending invalid payloads, check for available software updates or reflash per manufacturer procedure.
If module fails self-tests or continues to send invalid data after correct power, ground, wiring and reflash, replace module and re-test. Clear codes and perform a test drive to confirm repair.

Likely causes

Damaged CAN_H or CAN_L wiring near cruise control module
Poor/cracked connector pins at cruise control or receiving module
Failed cruise control module after power surge or water ingress
Bus termination resistor missing or shorted causing communication errors
Module firmware mismatch after partial reflash or using wrong calibration

Fault status

⚠️ Status

Invalid data received from Cruise Control Module — receiving module flagged message as malformed, checksum/CRC failure, out-of-range field, or unexpected CAN/LIN payload. MIL may be illuminated and cruise control disabled.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 1.0-3.0 hours