Your normal brakes still stop the car, so short, careful trips are possible, but ABS and stability control are disabled and a wheel can lock on wet or loose surfaces. Since the whole brake module has gone quiet on the network, have it diagnosed soon. U0129 is a network (U-code) fault that sets when a module on the data bus stops receiving the periodic message it expects from the Brake System Control Module — the ABS/electronic stability controller, often called the EBCM. The '"A" missing message' wording means the primary brake module's regularly broadcast frame simply stopped arriving, so the monitoring module reports lost communication with it.
What U0129 means
On a modern vehicle the brake control module (the ABS/traction/stability controller) sits on the high-speed CAN bus and continuously broadcasts data other controllers depend on — most importantly wheel-speed and vehicle-speed information, plus ABS/stability status. Modules such as the engine controller, transmission controller, instrument cluster, forward-facing camera and driver-assist controllers all listen for that message. With the ignition on and system voltage in the normal 10-16 V range, each listening module expects the brake module's frame to repeat every few tens of milliseconds; if the expected message goes absent for roughly two to five seconds, the module stores U0129. It is a message-presence fault, not a diagnosis of an internal brake circuit: the brake module may have lost power or ground, dropped off the bus because of open or shorted CAN wiring, been pulled offline by another failed node, or failed internally. This is distinct from U0418 (implausible data from the brake module), where the frame still arrives but its contents are out of range, and from a C-code such as C0050/C0051, which points to a fault inside the brake system itself rather than a broken conversation on the bus.
Symptoms
- ABS, traction control (TCS) and stability control (ESC/StabiliTrak/ESP) warning lights illuminated together
- Anti-lock and stability functions dead — the pedal no longer pulses/cycles during a hard stop
- 'Service Brake System' / 'Service Electronic Stability Control' or similar messages in the driver display
- Speedometer or vehicle-speed-dependent features glitch or drop out, since many modules take speed from the brake module's broadcast
- Multiple lost-communication U-codes stored across several modules at once (cluster, PCM, camera, etc.)
- Cruise control, hill-start assist or ADAS features (auto-braking, lane keeping) disabled or unavailable
Common causes
- Loss of switched power or a poor/corroded ground at the brake control module, so it cannot transmit
- Open, shorted, or corroded CAN bus wiring between the brake module and the rest of the network
- Blown fuse feeding the ABS/brake control module, taking it fully off the bus
- A failed brake control module (EBCM) that has stopped broadcasting its message
- A different dead or shorted node on the same CAN bus dragging the whole network down and silencing the brake module's frame
- Loose, backed-out, or water-intruded connector at the brake module or a bus splice
- Low system voltage or a weak battery/charging fault causing modules to briefly drop off the bus
- Recent module replacement or battery work leaving the brake module or a gateway unconfigured for the vehicle
Severity & driving advice
Severity: Moderate — Base hydraulic brakes still work, but ABS, traction and stability control are offline and speed-dependent features may drop out until communication is restored.
Can I drive? Your normal brakes still stop the car, so short, careful trips are possible, but ABS and stability control are disabled and a wheel can lock on wet or loose surfaces. Since the whole brake module has gone quiet on the network, have it diagnosed soon.
Diagnostic approach
- Confirm battery voltage, then verify the code is active — Charge the battery first — low voltage on its own triggers bus dropouts and false lost-communication codes. Turn the ignition on and scan all modules. If U0129 is active now, chase a 'no response from the brake module' condition; if it is only stored history, treat it as an intermittent event that has since recovered.
- Run the communication pre-diagnostic and read every module — Scan the whole network, not just one controller. Resolve any battery-voltage, ignition run/start, or 'bus off' codes first, because those cause secondary lost-communication codes like U0129. Note whether only one module reports U0129 or several do — a single reporting module points toward the brake module or its branch, while many modules losing the brake message points to a shared bus or gateway problem.
- Verify power and ground at the brake control module — Back-probe the EBCM/brake module connector: confirm battery/switched B+ on the power pins (near system voltage, roughly 12-14 V running) and a clean ground with under about 0.1 V drop to chassis. Check the ABS/brake module fuse(s). No power or a bad ground silences the module on the bus even though the module and CAN wiring may be fine.
- Test the CAN bus wiring to the brake module — With the key off, check the CAN twisted pair between the brake module and the network for opens, shorts to power or ground, and shorts across the two lines. A healthy high-speed CAN pair measures about 60 Ω across the two bus wires at rest (two 120 Ω terminators in parallel); a reading near 120 Ω suggests a broken bus wire, and a very low or open reading points to a short or a lost termination. Inspect the module and splice connectors for corrosion and backed-out terminals.
- Isolate a node that is pulling the bus down — If several modules report lost communication with the brake module (or with each other), disconnect suspect controllers one at a time — or look for one module shorting the bus — and watch whether communication returns. A single failed node can collapse the whole bus and make the brake module appear silent even though it is healthy.
- Confirm configuration, then evaluate the brake module — Verify the brake module and any gateway are configured/flashed correctly for the vehicle, especially after module replacement or battery work. Only once power, ground, bus wiring, and configuration all check out should the brake control module itself be condemned and replaced, then clear the codes and road-test above walking speed so every module re-establishes communication and the ABS/stability lights extinguish.
FAQ
Does U0129 mean my brake control module (ABS module) is bad?
Not necessarily. U0129 only means another module stopped receiving the brake module's expected message. That can happen because of missing power, a bad ground, damaged CAN wiring, a blown fuse, another failed node dragging the bus down, or a configuration error. The brake module is condemned only after those are ruled out.
What is the difference between U0129 (missing message) and U0418 (implausible data)?
U0129 is a lost-communication code — the brake module's message stopped arriving on the bus at all. U0418 means the message still arrives but its contents are out of range or contradict other data. Missing message points at power, ground, wiring, or a dead module, while implausible data points at what the brake module is sending or a sensor feeding it.
Is U0129 a communication fault or an actual brake fault?
It is a communication fault. U0129 lives on the data-bus side and reports that the brake module went silent. An internal brake problem — a wheel-speed sensor, pump, or valve issue — sets a C-code inside the brake module instead. If you see both, fix the brake module's own C-codes and its power/ground first, since they can knock it off the bus.
Can low battery voltage cause U0129?
Yes. Modules only monitor for the code within a normal voltage window of roughly 10-16 V. A weak battery, failing charging system, or a heavy voltage drop can make the brake module briefly drop off the bus and set U0129, so a full charge and a charging-system check should come before deeper diagnosis.
Why did U0129 appear along with several other lost-communication codes?
Because many controllers listen to the brake module, one bus or power problem can make all of them report it missing at once. When U0129 shows up beside other U-codes, suspect shared CAN wiring, a gateway, a common power/ground, or one dead node collapsing the bus rather than assuming each module failed separately.
Will U0129 clear on its own after I fix the problem?
Once the underlying power, ground, wiring, or module issue is repaired and codes are cleared with a scan tool, the network re-establishes communication on the next key cycle and drive. If the brake module now reports normally, the ABS, traction and stability lights go out; if U0129 keeps returning active, a real fault is still present.