U0122 – Lost Communication With Vehicle Dynamics Control Module

Last updated: April 7, 2026

U0122 means the car lost communication with the Vehicle Dynamics Control Module, so stability and traction functions may reduce or shut off. Most drivers notice ABS/traction/stability warnings and a change in how the vehicle handles on slick roads. According to manufacturer factory diagnostic data, this code indicates a network communication loss with the Vehicle Dynamics Control Module, not a confirmed failed module. The key point is “lost communication.” Something prevented other modules from receiving valid messages. That “something” can be power, ground, wiring, network faults, or an internal module issue. Diagnosis must prove which one.

🔍Look up your vehicle's recalls, specs & safety ratings — free VIN decoder with NHTSA data

U0122 Quick Answer

U0122 points to a network communication loss with the Vehicle Dynamics Control Module. Start by confirming the module shows “no communication” on a full network scan, then verify its power and grounds under load before chasing CAN wiring.

What Does U0122 Mean?

U0122 means one or more control modules on the vehicle network stopped receiving messages from the Vehicle Dynamics Control Module. In plain terms, the car can’t “hear” the stability/traction controller. When that happens, the vehicle usually disables or limits stability control, traction control, and sometimes ABS-related features. The DTC does not prove the dynamics module failed. It only proves a communication problem exists somewhere in the path.

Technically, modules set U0122 when expected network messages from the Vehicle Dynamics Control Module time out or fail plausibility checks. The setting module tracks message presence, not component health. That distinction matters. A blown fuse feeding the dynamics module can set the same U0122 as a CAN bus short, a backed-out connector terminal, or a gateway issue.

Theory of Operation

Under normal operation, the Vehicle Dynamics Control Module shares critical data over the network. It broadcasts stability and traction status, brake intervention requests, wheel speed-related data, and system state. Other modules use those messages for torque reduction, cruise control logic, and warning lamp control. The network may be CAN, or a mixed network with a gateway translating data. SAE U-codes stay general on purpose, so the exact network path varies by make and model.

U0122 sets when the network stops delivering that module’s messages. Loss can come from a powered-down module, a weak ground that drops out under load, or a bus fault that blocks traffic. An open in CAN-H or CAN-L can isolate the module from the bus. A short to power, short to ground, or water intrusion can corrupt the entire network. Some vehicles also route that module through a gateway. A gateway fault can make a healthy module “disappear” on the scan tool.

Symptoms

U0122 symptoms usually relate to stability/traction availability and scan tool communication behavior.

• Scan tool behavior: Vehicle Dynamics Control Module does not respond, shows “no communication,” or drops offline during a network scan.
• ABS/ESC/traction warnings: ABS, ESC, traction control, or brake warning lamps illuminate and may stay on.
• Stability control disabled: The dash may display “Stability Control Off/Service ESC” and the system may not intervene.
• Traction control limited: Wheel spin control may reduce or stop functioning, especially on wet or icy surfaces.
• Cruise control changes: Cruise may cancel or refuse to set because it depends on stability inputs.
• Powertrain behavior: Some vehicles reduce engine torque or enter a limited mode due to missing dynamics data.
• Intermittent faults: Warning lamps may come and go with bumps, rain, or temperature changes.

Common Causes

• Vehicle Dynamics Control Module (VDC) power feed loss: A blown fuse, open relay contact, or high-resistance power splice can shut the VDC module down so it stops transmitting network messages.
• VDC module ground path voltage drop: Corrosion or a loose ground lug can pass a continuity test but drop voltage under load, which resets the module and triggers U0122.
• CAN bus open on CAN+ or CAN- near the VDC module: A broken conductor or backed-out terminal prevents the VDC module’s messages from reaching other modules on the network.
• CAN bus short to ground or short to power: A chafed harness can pull the network bias voltage down or up, which blocks communication and sets a lost communication code.
• Poor terminal tension or water intrusion at the VDC connector: Intermittent contact changes bus impedance and causes repeated dropouts that other modules interpret as a lost module.
• Network junction/connector fault (splice pack, gateway, or junction block): A compromised junction can isolate the VDC module from the rest of the CAN network even though the module still powers up.
• Low system voltage during crank or charging system fault: A weak battery or alternator issue can dip voltage enough to reboot the VDC module, then other modules log U0122.
• VDC module internal fault: If power, ground, and CAN circuits test good, the module may stop transmitting due to an internal hardware or software failure.

Diagnosis Steps

Tools you need include a scan tool with full network scan capability, a DVOM, and a wiring diagram for the VDC module power/ground and CAN circuits. Use back-probes or breakout leads to avoid terminal damage. A battery charger helps during testing. If you have it, an oscilloscope speeds up CAN diagnostics.

1. Confirm U0122 and record all DTCs from every module. Save freeze frame data and note ignition state, vehicle speed, battery voltage, and any ABS/ESC-related codes that appeared first.
2. Run a network scan and check whether the scan tool can communicate with the Vehicle Dynamics Control Module. If the module does not appear, treat this as a hard communication loss and focus on power/ground and bus integrity first.
3. Check whether U0122 is pending or confirmed/stored. A pending U0122 can point to an intermittent dropout. A confirmed code often returns quickly after key-on if the fault remains.
4. Inspect fuses, relays, and power distribution that feed the VDC module before you take any connector measurements. Load-test the suspect fuse circuits with a test light or by commanding the system on, not by visual inspection alone.
5. Verify VDC module power and ground with voltage-drop tests under load. With the circuit operating, measure ground drop from the VDC ground pin to battery negative. Keep it under 0.1 V. Then measure power-side drop from battery positive to the VDC power pin while the module powers up.
6. Inspect the VDC connector and harness routing. Look for water tracks, green corrosion, spread terminals, and rub-through near suspension towers, inner fenders, and underbody clips. Repair harness damage before deeper network testing.
7. Check CAN bus resistance with ignition OFF and battery disconnected. Measure between CAN+ and CAN- at an accessible module connector or DLC when appropriate. A healthy bus reads about 60 ohms. A reading near 120 ohms or OL points to an open or missing termination.
8. Check CAN bias voltage with ignition ON. Measure CAN+ to ground and CAN- to ground at the VDC connector or another accessible point. A healthy network typically sits near 2.5 V on both lines. Do not use ignition-off readings as a reference because bias voltage disappears when the network sleeps.
9. If resistance or bias looks wrong, isolate the fault by unplugging modules or junction connectors one at a time, following the wiring diagram. Recheck resistance each time. When the reading returns to normal, you found the branch with the short or open.
10. When the scan tool can see the VDC module again, clear codes and perform a road test. Use a scan tool snapshot to capture live data during the event if the concern is intermittent. Remember the difference: freeze frame shows conditions when U0122 set, while a snapshot captures the dropout as it happens.
11. Confirm the repair by repeating a full network scan and ensuring U0122 stays cleared after multiple key cycles. Verify the ABS/ESC system performs self-checks and no related communication codes return.

Professional tip: If the VDC module disappears only during crank, watch battery voltage and ground drop during cranking. Many U0122 comebacks trace to a marginal battery cable or ground that passes static checks but fails under starter load.

Possible Fixes

• Repair the VDC module power supply fault (blown fuse cause, relay contact issue, open feed wire, or damaged splice) after confirming the voltage drop under load.
• Clean, tighten, and repair the VDC ground connection, then retest with a loaded voltage-drop measurement to verify less than 0.1 V drop.
• Repair an open, short to ground, or short to power on the CAN+ / CAN- circuits, including chafed wiring and backed-out terminals.
• Service connector issues at the VDC module (water intrusion cleanup, terminal tension repair, connector body replacement) and apply proper sealing where required.
• Repair a faulty network junction, splice pack, or gateway path that isolates the VDC module from the rest of the bus.
• After you verify power, ground, and CAN integrity, perform OEM-directed VDC module programming or replace the module only if tests prove it stops communicating.

Can I Still Drive With U0122?

You can sometimes drive with a U0122 code, but you should treat it as a safety-related fault until proven otherwise. The Vehicle Dynamics Control Module supports stability control and traction control on many vehicles. When other modules lose communication with it, the vehicle may disable those features or run in a reduced strategy. Expect ABS/ESC/traction warning lamps, and expect longer stopping distances on slick roads. Avoid towing, spirited driving, and wet or icy conditions. If the brake warning lamp also stays on, or the brake pedal feel changes, stop driving and inspect the base brake system first. If the engine runs rough or the transmission shifts harshly at the same time, you may have a wider network issue that can strand you.

How Serious Is This Code?

U0122 ranges from an inconvenience to a real safety concern, depending on what drops offline. If only the stability control functions go unavailable, you may notice no change in normal dry driving. Safety risk rises fast on low-traction surfaces and during emergency maneuvers. If the dynamics module also shares wheel-speed or yaw data across the network, other systems can degrade too. Some vehicles limit cruise control, hill start assist, or torque management when U0122 sets. Ignoring the code can hide an intermittent power, ground, or network fault that later takes down more modules. Treat repeated or confirmed U0122 as urgent, and prove power, ground, and network integrity before any module replacement.

Common Misdiagnoses

Technicians often replace the Vehicle Dynamics Control Module because the scan tool shows “lost communication.” That wastes money when the real problem sits in the basics. A weak module power feed, a loose ground eyelet, or water in the connector can drop the module offline for milliseconds and set U0122. Another common miss involves the CAN bus. A shorted aftermarket radio harness, a pinched CAN pair near a battery tray, or corrosion at a splice pack can block messages and make the dynamics module look dead. Shops also skip a full network scan. If multiple U-codes appear across modules, you must diagnose the shared network or power supply first. Always confirm whether you can talk to the dynamics module directly before calling it failed.

Most Likely Fix

The most common confirmed repair direction for U0122 is restoring reliable power and ground to the Vehicle Dynamics Control Module. That includes cleaning and tightening grounds, repairing spread terminals, and fixing water intrusion at the module connector. The next frequent direction involves correcting CAN network integrity issues near the module. Look for rubbed-through wiring, poor repairs, or corrosion at splice points. After repairs, clear codes and road-test under similar conditions that set the fault. Enable criteria vary by vehicle, so use service information to confirm what drive cycle proves the network stays stable.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.