OBD-II trouble code
U0460: Invalid Data Received From Automated Driving System Interface Module 'B'
A module is receiving messages from the automated driving system (ADS) interface module 'B', but the data inside them is implausible or out of range. The link is alive; the content is wrong. Automated and hands-free driving features are disabled as a precaution — you drive manually until it's fixed.
Quick facts
- System
- Network
- Category
- Network Communication
- Severity
- Medium severity
- Drivable
- Usually safe to drive short-term
- Repair cost range
- $100 – $1,400
- DIY difficulty
- Shop recommended
What does U0460 mean?
The automated driving system (ADS) interface module bridges the ADS controller's driving decisions and the vehicle systems that carry them out, relaying and time-aligning data between the automation, the actuators (steering, braking, propulsion), and the sensor networks. Vehicles that use two interface modules for capacity or redundancy designate the second one 'B'. U0460 sets when a receiving module is still hearing from ADS interface module 'B', but the data in its messages is invalid — out of range, implausible, or in conflict with what other modules report. The module is transmitting; its content simply can't be trusted. That is what separates U0460 from a lost-communication code, where interface module 'B' would have gone completely silent.
Automation that touches steering and braking is designed to fail conservative, so when the network can't trust interface module 'B', the vehicle disables its automated and hands-free driving features and returns full control to the driver with a takeover warning. On a redundant architecture, losing confidence in the second interface path can disable the whole feature even if the primary path is healthy, because the system won't run without all of its trusted links. The car stays fully driveable under manual control — engine, transmission, brakes, and steering are unaffected — but you are responsible for all of the driving until the fault clears.
Like its 'A' counterpart, the interface module is largely a relay, so U0460 is frequently a secondary code: implausible values can originate upstream in a sensor or controller and pass through. Read companion codes first — a camera, radar, steering, brake, or ADS controller code often names the real fault. The remaining causes are the usual invalid-data set: low system voltage or a poor ground; corroded or damaged connectors; chafed or damaged high-speed bus wiring between networks; an interrupted or mismatched software update; a module replaced without configuration; and, once those are ruled out, an internal module fault. If both interface modules 'A' and 'B' set invalid-data codes at once, a shared power, ground, or bus cause is the priority.
Common causes
- Upstream sensor or controller fault passing implausible data through the interface
- Low system voltage, a weak battery, or a poor ground at the module
- Corroded, loose, or damaged connectors at the module
- Chafed or damaged high-speed bus wiring between networks
- Interrupted, mismatched, or corrupted ADS software update
- ADS interface module 'B' replaced without correct configuration
- Electrical noise or a marginal gateway corrupting relayed messages
- Internal ADS interface module 'B' fault
Symptoms
- Automated / hands-free driving features unavailable with a warning message
- Takeover request handing control back to the driver
- Driver-assistance warning light or 'service driver assist' message
- Multiple companion ADS, camera, radar, or chassis codes stored alongside U0460
- No change in how the vehicle starts, runs, or drives under manual control
Diagnostic steps
- 1.Read all stored codes first — U0460 is often a secondary code, so a companion sensor, chassis, or ADS code usually names the real fault.
- 2.Note whether U045F ('A') is also set; if both are, prioritize a shared power, ground, or bus cause.
- 3.Address upstream faults (camera, radar, steering, brake, ADS controller) before focusing on the interface module.
- 4.Load-test the battery and verify charging voltage and the module's grounds.
- 5.Inspect connectors and high-speed bus/gateway wiring for corrosion, looseness, and chafing.
- 6.Confirm the last software update completed and check for available updates.
- 7.If upstream data, wiring, and software check out, suspect an internal module fault and verify with service data.
Repair cost
$100 – $1,400
Cost depends on the cause. Because U0460 is often secondary, fixing the upstream fault frequently clears it. A software update/reflash is often $100-$300. Repairing a connector, ground, or wiring/gateway fault is typically $100-$450. Reprogramming or configuring the module after a replacement is usually $100-$300. ADS interface module replacement with programming is the higher end at roughly $700-$1,400. Diagnose and fix the source of the invalid data before replacing the interface module.
Estimate your repair
Run the numbers for your vehicle
Open the Repair Cost Estimator with module communication / can bus diagnosis preselected. Adjust labor rate and vehicle category to fit your situation.
DIY vs shop
Leave this one to a qualified shop. It typically involves emissions-critical components, refrigerant handling, or other work that requires manufacturer-grade tooling, training, or certification. DIY attempts often produce a more expensive problem than the original code.