U0129 – Lost communication with brake system control module “A” missing message

Last updated: April 11, 2026

U0129 means one or more modules on the vehicle network stopped receiving the expected message from the brake system control module “A.” In plain English, the car may turn on ABS, traction control, or stability control warnings, and some brake assist features may stop working. According to factory diagnostic conventions used across many brands, this code does not prove the brake control module failed. It means communication dropped out or a required message went missing. The U0129 code points to a network problem area first, so you need to verify module power, ground, connector condition, and network integrity before replacing any control unit.

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

U0129 Quick Answer

U0129 points to lost network communication with the brake system control module “A.” Check for scan tool communication with the ABS/brake module first, then verify its power, grounds, and network wiring before condemning the module.

What Does U0129 Mean?

The official U0129 meaning is lost communication with brake system control module “A” missing message. In practice, another module expected brake system data and did not receive it. That missing data can disable ABS, traction control, stability control, brake assist, cruise control, or other functions that rely on brake module information. The exact module assignment for “A” can vary by manufacturer, so verify the module identity in vehicle-specific service information.

Technically, a controller on the network monitors for scheduled messages from the brake system control module. When that message does not arrive within the expected communication window, it sets U0129. This code often appears with SAE J2012DA fault subtype -87, which identifies a missing message condition. That wording matters. The module did not simply see bad brake performance. It detected absent network data, so diagnosis must focus on communication presence, module power and ground, and bus integrity before any part replacement.

Theory of Operation

Under normal conditions, the brake system control module exchanges data continuously with other controllers over the vehicle network. Depending on the platform, that module may manage ABS, traction control, electronic stability control, brake pressure information, wheel speed reporting, or brake switch status routing. Other modules use those messages for torque reduction, transmission strategy, adaptive cruise, hill assist, and warning lamp decisions. The network only works when every active module has clean power, strong grounds, intact connectors, and a healthy communication circuit.

U0129 sets when the expected brake module message disappears. That can happen because the brake control module loses battery feed, loses ignition feed, or loses ground. Corrosion in the connector can raise resistance and interrupt communication. A shorted or open network circuit can block message traffic even when the module still has power. In some cases, the module stays online only intermittently, which creates a missing message pattern instead of a total hard failure. That is why a full network scan matters before any repair decision.

Symptoms

U0129 symptoms usually center on warning lamps, disabled brake-related features, and scan tool communication problems.

• Scan tool dropout: The brake or ABS module may not appear on the module list, or it may fail to respond during a network scan.
• ABS warning: The ABS light often turns on because other modules cannot confirm brake system status.
• Traction or stability warning: Traction control and ESC lights may illuminate, and those functions may disable.
• Brake assist changes: Electronic brake assist, hill hold, or related brake support functions may stop operating.
• Cruise control disabled: Some vehicles shut off cruise or adaptive cruise when brake network data goes missing.
• Multiple communication codes: Other modules may store related U-codes because they also lost brake module data.
• Intermittent warning behavior: Lamps may come and go with bumps, moisture, steering movement, or temperature changes if the fault is connection-related.

Common Causes

• Brake system control module power loss: A blown fuse, weak feed, or failed power distribution path can shut the brake control module down and stop its network messages.
• High-resistance or open module ground: Corrosion or a loose ground eyelet can let the module wake up poorly or reset, which creates a missing-message U0129 code.
• CAN bus open circuit near the ABS/brake module: An open in CAN high or CAN low prevents the brake module from sharing data with other controllers.
• CAN bus short to ground, battery, or between circuits: A shorted network pair can collapse bus communication and make multiple modules report lost communication with the brake controller.
• Water intrusion at the brake module connector: Moisture inside the connector creates corrosion and terminal spread, which raises resistance and interrupts power, ground, or CAN signals.
• Harness damage near the hydraulic unit or frame rail: Vibration, road debris, or prior repair work can chafe the harness and break the communication or feed circuits.
• Network-wide bus fault from another module: A different controller can short the CAN network and make the brake system control module appear offline even when it is healthy.
• Low system voltage during cranking or charging faults: Battery or charging problems can make the brake module reboot or drop off the bus long enough to set a missing-message fault.
• Brake system control module internal failure: Internal circuit faults can stop message transmission, but you must prove power, ground, and network integrity first.

Diagnosis Steps

You need a full-function scan tool that can run a network scan, a wiring diagram, a DVOM, and ideally a lab scope. A fused test light helps load-test power and ground circuits. For U0129, review freeze frame data for vehicle speed, ignition state, battery voltage, and related DTCs. Freeze frame shows when the fault set. A scan tool snapshot captures an intermittent dropout during your road test.

1. Confirm U0129 with a complete vehicle scan. Record whether the code is pending, confirmed, or history. Save freeze frame data, especially ignition state, vehicle speed, battery voltage, and all related network, ABS, steering, and powertrain codes. If the brake system control module does not appear on the network scan, treat that as a primary clue.
2. Check the fuse map and power distribution first. Verify every fuse and relay that feeds the brake system control module. On a communication code, also note whether the module appears on the scan tool network list before you touch the connector. A hard fault often returns at key-on.
3. Verify module power and ground under load. Backprobe the brake control module feed and ground circuits with the circuit operating. Use voltage-drop testing, not continuity alone. Ground drop should stay below 0.1 volt under load. A high-resistance ground can pass a continuity test and still kill communication.
4. Inspect the brake module connector, nearby harness, and grounding points. Look for water entry, green corrosion, backed-out pins, terminal spread, harness rub-through, and damage near the hydraulic unit, frame rail, or battery area. Wiggle the harness while you watch scan tool module presence.
5. With the ignition ON, check CAN circuit bias voltage to ground at an accessible connector. On a healthy high-speed CAN network, both CAN+ and CAN- usually sit near 2.5 volts. Ignition-off readings do not count here because the bus bias exists only when the network is powered.
6. Turn the ignition OFF and disconnect the battery before resistance checks. Measure resistance between CAN+ and CAN- at an accessible module connector. A healthy terminated bus reads about 60 ohms. Around 120 ohms or OL points to an open or missing termination. Very low resistance points to a shorted bus.
7. If bus readings look wrong, isolate the faulted network segment. Disconnect suspect modules one at a time, following service information, and recheck resistance and module presence. A different controller can pull the bus down and create U0129 even though the brake module itself works.
8. If bus integrity looks normal, reconnect the battery and command a fresh network scan. Try to establish direct communication with the brake system control module. If communication fails but power, ground, and CAN circuits test correctly at the module connector, the suspected trouble area moves closer to the module itself.
9. Check for intermittent behavior with a road test if the code remains pending or history only. Use a scan tool snapshot to capture module dropout, ignition status, battery voltage, and vehicle speed at the moment communication fails. That helps separate a wiring movement fault from a hard module outage.
10. After repairs, clear all codes and repeat the network scan. Confirm the brake module appears normally, no related U-codes reset, and warning lamps stay off through a complete key cycle and road test.

Professional tip: U0129 often tempts people to condemn the ABS or brake control module too early. Do not skip a loaded ground test and CAN resistance check. I see more corroded connectors, fuse feed issues, and network faults than true module failures. If several U-codes set together, find the module that disappears first or pulls the bus down.

Possible Fixes

• Repair the brake module power feed: Replace the blown fuse, repair the relay or feed circuit, and correct the reason the power supply failed.
• Restore a clean, low-resistance ground: Clean and tighten the ground point, repair damaged ground wiring, and verify less than 0.1 volt drop under load.
• Repair CAN bus wiring: Fix opens, shorts, or rubbed-through CAN high and CAN low circuits, then confirm proper 60-ohm bus resistance and normal bias voltage.
• Replace damaged terminals or connectors: Correct terminal spread, corrosion, or water-damaged connector bodies at the brake module or related junction points.
• Correct a network-wide module fault: Repair or replace the controller that is pulling the CAN network down if testing proves another module caused the communication loss.
• Replace and program the brake system control module: Do this only after you verify good power, ground, connector integrity, and CAN network operation at the module.

Can I Still Drive With U0129?

You can sometimes drive with a U0129 code, but you should treat it as a brake system safety fault until testing proves otherwise. This code means another module stopped receiving the expected message from the brake system control module “A.” On many vehicles, that module manages ABS, traction control, stability control, and brake force logic. The engine may still run normally, but the vehicle can lose anti-lock braking and stability intervention. Warning lamps often turn on, and some vehicles disable cruise control, hill start assist, or collision support features that rely on brake data. If the brake pedal feels normal and only warning lights are on, the vehicle may remain movable for short trips to a repair facility. Do not ignore it. If the pedal feels unusual, the red brake light is on, or multiple chassis systems drop offline, stop driving and inspect it immediately.

How Serious Is This Code?

U0129 ranges from inconvenient to serious, depending on what the lost message affects on that vehicle. In the mild case, the car only loses ABS and traction control support, and basic hydraulic braking still works. In the serious case, the network fault blocks stability control, brake assist, adaptive cruise interaction, and other systems that need live brake module data. That raises risk during panic stops, slippery roads, towing, or evasive maneuvers. The code itself does not prove the brake control module failed. A weak power feed, poor ground, corroded connector, or CAN wiring fault can create the same missing-message condition. Because this fault involves the brake electronics network, you should rank it high priority. Driving longer without diagnosis can leave you with reduced safety features and can complicate diagnosis if the fault becomes intermittent.

Common Misdiagnoses

Technicians often replace the ABS or brake control module too early when they see U0129. That wastes money and often does not fix the car. The smarter path starts with a full network scan. Check whether the scan tool can talk to the brake system control module directly. If communication still works, the issue may be intermittent, stored history, or another module setting U0129 because it briefly lost the message. Another common mistake is skipping power and ground voltage-drop tests under load. A module can have battery voltage on a meter and still fail when current demand rises. Shops also miss water intrusion at the hydraulic unit connector, splice pack corrosion, and CAN bus damage near the battery tray or left front frame area. Always confirm module presence, power, ground, and network integrity before condemning hardware.

Most Likely Fix

The most common U0129 repair direction is restoring brake module power, ground, or CAN communication rather than replacing the module first. . If the scan tool cannot establish communication with the brake system control module and the module fails power, ground, or bus checks, repair that circuit issue first. If all inputs and network lines test correctly, then module replacement or reprogramming becomes a valid next step. After repair, clear codes, perform a full network rescan, and drive the vehicle through several key cycles and normal road-speed events. Enable criteria vary by platform, so use service information to confirm when the communication monitor runs.

Repair Costs

Repair cost depends on whether the root cause is a wheel speed sensor, wiring, connector condition, or the hydraulic control unit. Start with electrical checks before replacing brake system components.