U0122 – Lost Communication With Vehicle Dynamics Control Module

U0122 means your vehicle lost communication with the Vehicle Dynamics Control Module, which can disable or limit stability control and traction control. You may notice ABS, traction, or stability warnings and a different brake or handling feel. According to factory diagnostic data, this code indicates that one or more other modules stopped receiving expected network messages from the Vehicle Dynamics Control Module for a calibrated time. The code does not prove the module failed. It points to a network communication loss that you must confirm with power, ground, and CAN circuit testing before any parts decisions.

U0122 Quick Answer

U0122 code points to a communication loss with the Vehicle Dynamics Control Module. Start by verifying the module appears on the scan tool network list, then check its fuses, powers, grounds, and the CAN wiring at its connector.

What Does U0122 Mean?

U0122 is defined as “Lost Communication With Vehicle Dynamics Control Module.” In plain terms, another control module on the vehicle network expected to “hear” from the dynamics control module and did not. When that happens, the vehicle often turns off or limits stability control and traction functions because the network can’t coordinate braking and torque requests reliably.

Technically, the setting module monitors network traffic and expects periodic messages from the Vehicle Dynamics Control Module. When those messages stop or become invalid, it logs U0122 and may flag the dynamics module as “not responding” on a network scan. This matters because the code only tells you the communication failed. You still must determine whether the cause sits in power/ground, the network wiring, a connector issue, or the module itself.

Theory of Operation

Under normal conditions, the Vehicle Dynamics Control Module shares data with the ABS/brake system, powertrain control, and sometimes steering modules. It broadcasts network messages that report wheel speed processing, yaw or lateral calculations, and stability intervention status. Other modules use that data to coordinate torque reduction, brake pressure commands, and warning lamp logic.

U0122 sets when the network stops delivering those messages. A loss of module power, a weak ground, or a corroded connector can make the module reboot or go silent. A shorted or open CAN circuit can also block traffic and cause multiple modules to “drop off” the network. Because SAE U-codes stay intentionally general, you must identify which bus segment and which node failed using a full module scan and circuit checks at the dynamics module.

Symptoms

U0122 symptoms usually show up as stability and traction features turning off, often with multiple warning lamps.

• Scan tool: Vehicle Dynamics Control Module missing from the ECU list, not responding to ping, or dropping out intermittently during a network scan
• Warning lights: ABS, traction control, stability control, or brake warning lamps on, sometimes together
• Driver message: “Stability control off,” “Service traction,” or similar message after startup or during a turn
• Handling change: traction control does not intervene on slippery acceleration or during aggressive cornering
• Brake feel: ABS function may feel reduced or inconsistent, especially on loose surfaces
• Multiple codes: other modules may store additional U-codes that reference lost communication or network faults

Common Causes

• Power feed interruption to the Vehicle Dynamics Control Module: A blown fuse, failing relay, or loose power distribution connection makes the module drop offline and triggers U0122 in other modules.
• High-resistance ground at the dynamics module: Corrosion or a loose ground eyelet lets the module boot intermittently, so it stops sending network messages and sets a communication loss DTC.
• Open or short in the network twisted pair near the module: Harness rub-through, pin fit issues, or a stretched section can open the bus or short CAN circuits, which prevents message traffic from reaching the dynamics module.
• Connector water intrusion at the dynamics module or junction: Moisture bridges terminals and changes impedance, so the bus becomes noisy and the module fails to maintain communication.
• Aftermarket device or improper wiring repair loading the network: Splices for remote starts, alarms, radios, or trailer wiring can distort the bus and block the dynamics module’s messages.
• Network junction or gateway fault affecting the module’s bus segment: A failing splice pack, star connector, or gateway module can isolate the dynamics module even when its own power and ground stay intact.
• Low system voltage or charging system event during startup: A weak battery, voltage dip, or alternator over/undercharge can reset the dynamics module and create a U0122 during high electrical load.
• Vehicle Dynamics Control Module internal fault (rare): Internal logic or transceiver failure can stop communication, but you must prove power, ground, and bus integrity first.

Diagnosis Steps

Use a scan tool that can perform a full network scan, read freeze-frame, and show module status. Have a DVOM for voltage-drop testing and wiring diagrams for power, ground, and network routing. A backprobe kit helps at sealed connectors. If available, use an oscilloscope to evaluate bus signal quality during a wiggle test.

1. Confirm U0122 and note whether it shows as pending, confirmed, or history. Record freeze-frame data and focus on ignition state, vehicle speed, battery voltage, and any companion U-codes. Check which module stored U0122, since that identifies the “complaining” module. Save a report of all DTCs from every module.
2. Run a network scan and verify whether the Vehicle Dynamics Control Module appears and responds. If the scan tool cannot communicate with it, treat the issue as power/ground, connector, or bus access first. If it does appear, compare which modules still log U0122 and look for a gateway or segment issue.
3. Check related fuses, relays, and power distribution feeds before probing the module connector. Load-test suspect fuses with a test light or by measuring voltage drop across the fuse while the circuit is active. Do not trust a visual fuse check.
4. Verify the module’s power and ground under load at the connector. Command functions that wake the network if needed, then measure voltage drop from battery positive to the module B+ pin while operating. Next, measure ground voltage drop from the module ground pin to battery negative with the circuit operating, and keep it under 0.1V.
5. Inspect the Vehicle Dynamics Control Module connector and nearby harness routing. Look for water tracks, green corrosion, backed-out pins, and terminal spread. Follow the harness to the nearest junction, splice pack, or body pass-through and inspect for chafing.
6. With ignition ON, check network line bias at the module connector or at the nearest accessible junction. Communication line bias only exists with the network awake, so ignition-OFF readings do not help. If the scan tool shows the module offline, measure on both bus lines to confirm the network has normal bias and no hard short.
7. Perform circuit integrity tests on the network pair between the module and the next junction point. Isolate the circuit per service information, then check for opens, short-to-ground, and short-to-power. Use resistance checks only with power removed, and avoid forcing terminals with meter probes.
8. Wiggle test the harness and connector while monitoring module presence on the scan tool. If the fault acts intermittent, capture a scan tool snapshot during a road test or vibration event. Freeze-frame shows conditions when the DTC set, while a snapshot captures the moment the failure occurs during diagnosis.
9. If the module communicates intermittently, verify related sensor inputs and network wake-up signals that keep it online. Check for companion ABS/traction/stability related codes in other modules that may point to a shared power feed or shared ground point. Confirm no aftermarket accessories share the same power or ground path.
10. After repairs, clear codes and rerun a full network scan. Road test under similar freeze-frame conditions and confirm the module stays online. Recheck for pending codes, since some monitors need two trips to mature from pending to confirmed.

Professional tip: When U0122 sets, prove the basics with a loaded power and ground test first. A module can show 12V on a meter with no load and still reset under demand. Voltage-drop testing catches the hidden resistance that communication diagnostics often miss.

Possible Fixes

• Repair power feed or ground issues to the Vehicle Dynamics Control Module, including corroded ground eyelets and loose power distribution connections.
• Repair harness damage, poor splices, or terminal problems on the network twisted pair near the module and at junction points.
• Clean, dry, and restore connector integrity after water intrusion, then apply proper terminal tension and sealing practices.
• Remove or correct aftermarket wiring that loads the network or introduces poor splice connections.
• Restore charging system health or battery condition if low voltage events coincide with the freeze-frame data.
• Reprogram or replace the Vehicle Dynamics Control Module only after you verify power, ground, and network integrity.

Can I Still Drive With U0122?

You can often drive with a U0122 code, but you should treat it as a stability and braking support risk. When the Vehicle Dynamics Control Module drops off the network, the vehicle may disable ABS, traction control, and stability control functions. Some vehicles keep base hydraulic braking, but they remove electronic assist features. Drive only if the brake pedal feels normal and warning lights stay stable. Avoid hard braking, towing, slippery roads, and aggressive maneuvers. If you see a red brake warning, the pedal goes soft, or the dash shows multiple network warnings, stop driving and tow it. An intermittent U0122 that comes and goes with bumps also points to a wiring or connector issue that can worsen quickly.

How Serious Is This Code?

U0122 ranges from an inconvenience to a real safety concern, depending on what shuts down with the lost communication. If the module only loses data briefly, you may only see a traction control or stability warning and no drivability change. When the loss stays active, many vehicles disable ABS, ESC, and traction control. That increases stopping distance on slick pavement and reduces control during a skid. You should treat any brake or stability warning as time-sensitive. Network faults can also trigger secondary codes in the ECM, BCM, or instrument cluster. Those extra codes do not confirm those modules failed. They often report the same missing messages.

Common Misdiagnoses

Technicians often replace the Vehicle Dynamics Control Module because the scan tool cannot talk to it. That skips the most common root causes. Power or ground loss at the module will make it “disappear” from the network. A single high-resistance ground can mimic a dead module, especially when you load the circuit with the key on. Another common mistake involves chasing wheel speed sensor codes first. Those sensors do not usually cause U0122 by themselves. U0122 points to a network-level communication loss, not a single sensor input fault. Shops also misread “U-codes” as proof of a bad CAN bus. In reality, one backed-out terminal, water intrusion in a connector, or a rubbed-through harness near the ABS pump can take the module offline.

Most Likely Fix

The most frequent U0122 repair path starts with restoring clean power and ground to the Vehicle Dynamics Control Module and repairing any connector damage at that module. Corrosion at the module connector, loose terminals, and poor grounds near the chassis are common patterns. The next most common direction involves locating an open or short in the network wiring between the dynamics module and the rest of the bus. Confirm the module’s power, ground, and network integrity with voltage-drop tests under load before you consider module replacement. After repairs, road test long enough to prove the fault does not return. Enable conditions vary by vehicle, so verify with service information and a full network scan.

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.

Last updated: March 31, 2026