Lost Communication Codes for Brake, Steering and Stability Modules
Lost communication codes such as U0122, U0123, U0125, U0126, U0128, U0129, U0131 and U0212 indicate that a reporting module did not receive expected CAN network messages from another control unit. They commonly involve vehicle dynamics, yaw rate, accelerometer, steering angle, park brake, brake control, power steering and steering column modules. Heavy steering can appear, yet the code is evidence to interpret, not proof a part failed.
Verify the Code Meaning and Identify the Module Reporting It
A lost communication code is stored when a reporting module detects that expected network messages did not arrive on the CAN network. That finding does not identify a failed part. The missing traffic may involve module power and ground, a connector, a communication circuit or the module that should have transmitted. A U0122 code commonly identifies lost communication with the vehicle dynamics control module, but the exact designation still depends on the vehicle's year, model and equipment.
Confirm the exact code, any suffix and the manufacturer's diagnostic information before interpreting module names or network behavior. Manufacturer-dependent codes require vehicle-specific confirmation. Record which module stored each result and whether the scan tool labels it current, stored or intermittent. Those status labels describe how the tool last observed the condition; they do not prove the fault is gone, still present or confined to one control unit. A stored or intermittent label can remain after messages resume.
U0123, U0125 and U0126: Motion and Steering Angle Messages
A U0123 code commonly indicates lost communication with the yaw rate sensor module, a U0125 code with the multi-axis acceleration sensor module, and a U0126 code with the steering angle sensor module. Those labels still need vehicle-specific verification, because some designs combine motion sensing while others use separate modules. Yaw rate, multi-axis acceleration and steering angle information help stability and traction functions judge vehicle motion relative to driver input.
Stability or traction warnings and unavailable assistance functions may appear when those messages are missing, yet symptoms cannot identify the failed network component. A communication code does not independently prove sensor failure, an incorrect sensor reading or a need for calibration. The reporting module only recorded that expected traffic did not arrive. Wiring, power, ground or the transmitting module can produce the same result, so further testing is required before any sensor replacement or alignment work is considered.
U0128 and U0129: Park Brake and Brake Control Communication
After verifying the vehicle's definitions, a U0128 code commonly indicates lost communication with the park brake control module, and a U0129 code with the brake system control module. Parking brake messages, brake warnings or unavailable functions may appear when those modules are not exchanging expected CAN network traffic. Fail-safe responses vary by design, so the code cannot promise a particular warning pattern or remaining brake function.
A communication code establishes that expected messages were missing; it does not establish braking safety or prove a hydraulic, mechanical or actuator fault. Distinguishing a network issue from a brake system problem requires dedicated brake system testing beyond the stored U code. If a parking brake will not release or will not hold, seek professional assistance rather than attempting a bypass or forced release. Those actions can leave the vehicle uncontrolled or the parking brake inoperative, and they are not a diagnostic substitute for confirming module communication.
U0131 and U0212: Power Steering and Steering Column Communication
U0131 commonly identifies lost communication with the power steering control module, and U0212 with the steering column control module, using verified vehicle-specific terminology. Reduced steering assistance, heavy steering or a steering warning can accompany a U0131 code, yet the result cannot confirm whether power, ground, a communication circuit or the module itself interrupted the messages. Sudden steering-effort changes call for professional assessment, not column disassembly or an assumed replacement.
Symptoms accompanying U0212 depend on the functions assigned to the steering column control module in that vehicle. Column-related features such as lock control, position sensing or associated driver-interface functions may be affected on some designs and left unchanged on others. Because those assignments vary, a U0212 finding should be read against manufacturer information rather than a generic list of steering complaints. The code documents missing expected messages, not a confirmed column fault, so diagnosis still starts with communication, power and ground rather than assuming the column hardware has failed.
Warning Signs That Require Stopping and Getting Assistance
Controls that still feel normal do not confirm that brake, steering or stability assistance remains available. Lost communication can leave a function reduced even when pedal feel, steering weight or motion has not changed in an obvious way. If braking changes, steering becomes difficult or control feels uncertain, stop safely and arrange assistance. Driving on to see whether a warning stays on or a code returns is not a reliable check of remaining capability.
Treat a red brake warning or an instruction to stop according to the owner's manual. A code description cannot declare the vehicle safe, and manufacturer-dependent messages should be followed as written rather than reinterpreted from a generic U-code list. Deliberate road tests, abrupt steering inputs and attempts to trigger stability intervention are inappropriate owner checks. Those maneuvers can demand the very assistance that may be unavailable, and they do not isolate whether the yaw rate, acceleration, steering angle or brake modules are actually communicating.
Safe Observations and the Shared Diagnostic Approach
Record warning messages, when symptoms began, whether they recur, and any recent battery discharge, jump-starting or electrical work. Timing can be useful context, but it is not proof of causation. Preserve the original scan report before clearing codes or disconnecting the battery, because lost evidence can hinder diagnosis. A later full-system scan that no longer shows a U0131, U0212 or related result does not explain what the reporting module originally saw, and intermittent lost communication can disappear after a power cycle without the circuit being repaired.
An appropriate full-system scan is needed to identify reporting modules, unreachable modules and accompanying voltage or network codes. A basic engine-code reader may provide incomplete coverage of brake, steering and stability controllers. Professional checks then follow the vehicle's network layout, module power and grounds, communication circuits and relevant connectors. Those inspections look for shared supply or bus problems that can silence more than one module. Probing shortcuts, jumper wires and bypasses are not owner procedures; they can damage control units and they do not replace a structured network diagnosis.
How Testing Confirms the Cause and Verifies the Repair
Several communication codes may reflect a shared supply or network problem and do not establish several failed modules. If U0122, U0123, U0125 and U0126 appear together, the pattern can point to a common CAN network or power issue affecting vehicle dynamics and motion-sensor traffic rather than four independent failures. Successful communication during a workshop visit does not rule out an intermittent fault. Recorded conditions, freeze-frame data when available and the original scan report help guide further testing when messages have returned by the time the vehicle is inspected.
Module replacement, programming or calibration should wait for evidence that the module, rather than its supply or communication path, is at fault, and those procedures follow manufacturer requirements. Repair verification depends on restored module communication, a follow-up scan and qualified checks of affected functions. Clearing codes alone does not confirm a repair, because a silenced transmitter can look quiet until the condition returns.