U0126 – Lost communication with steering angle sensor (SAS) module

U0126 means one or more control modules stopped receiving steering angle sensor (SAS) data over the vehicle network. You may notice stability control or steering-related warnings and changes in traction control behavior. The vehicle can also disable features that depend on steering angle input. According to factory diagnostic data, this code indicates “Lost communication with steering angle sensor (SAS) module.” This definition stays intentionally general by SAE design. Your job in diagnosis is to prove whether the SAS module went offline, lost power/ground, or the network path to it failed.

U0126 Quick Answer

U0126 points to a network communication loss with the steering angle sensor (SAS) module. Start by confirming the SAS module appears on a full network scan, then check its power, ground, and network wiring before condemning any module.

What Does U0126 Mean?

The official U0126 meaning is “Lost communication with steering angle sensor (SAS) module.” In plain terms, another module expected steering angle data but did not get it. That missing data can disable ESC/traction functions or steering assistance features, depending on the vehicle. The code does not prove the SAS module failed. It only proves the vehicle network did not deliver valid SAS communication when required.

Technically, a receiving module monitors network message presence and validity for the SAS module. When those messages stop, arrive corrupted, or the SAS node drops off the bus, the module sets U0126 and may log related U-codes. This matters because the root cause can sit anywhere in the communication chain. Power loss at the SAS, a ground voltage drop, a shorted CAN/LIN circuit, or a gateway issue can all create the same “lost communication” result.

Theory of Operation

Under normal conditions, the SAS module measures steering wheel angle and steering rate. It broadcasts that data on the vehicle network to other modules. Common listeners include the ABS/ESC module, power steering, and ADAS functions. Those modules use steering angle to calculate yaw control, traction interventions, and steering assist targets. The network carries the message through the bus or through a gateway, depending on vehicle architecture.

U0126 sets when the listening module stops seeing the expected SAS communication for a calibrated time window. Several failures can cause that dropout. Loss of B+ or ground at the SAS stops all messages instantly. A high-resistance ground can allow the module to “boot” but crash under load. Network faults can also isolate the SAS while other modules still communicate, which makes this code tricky without a full module list scan and targeted voltage-drop tests.

Symptoms

U0126 symptoms usually show up as stability/steering feature warnings and scan tool communication issues.

• Scan tool behavior: SAS module missing from the ECU list, “no communication,” or intermittent dropout during a network scan
• ESC/traction warning: stability control light on, traction control off message, or ESC unavailable
• Steering warning: EPS warning light or reduced steering assist on some platforms
• ABS/ESC codes stored: companion U-codes in ABS/ESC or gateway modules related to missing steering angle
• ADAS feature disabled: lane-keep assist, park assist, or collision features limited due to missing steering input
• Erratic stability intervention: unexpected traction control behavior if steering angle data drops in and out
• Calibration unavailable: steering angle calibration routine fails because the tool cannot talk to the SAS module

Common Causes

• SAS module power feed lost (blown fuse or open in B+ circuit): The SAS module drops off the network when it loses battery or ignition power, so other modules log U0126.
• High-resistance or open SAS ground: A weak ground can let the module boot or wake intermittently, then reset under load and stop communicating.
• Open or high resistance in CAN wiring to the SAS: A break in CAN+ or CAN- near the clock spring, column, or harness joint prevents messages from reaching the rest of the network.
• CAN wiring short to power or short to ground: A short forces the bus voltage out of its normal bias range and blocks valid data from all nodes on that bus segment.
• Connector fault at SAS, clock spring area, or intermediate junction: Spread terminals, fretting, or moisture raises contact resistance and causes intermittent module dropouts.
• Network gateway or bus segment issue (module not on the same network you are scanning): Some vehicles route SAS data through a gateway, so a gateway power loss or internal fault can mimic “lost comm” with the SAS.
• Recent steering column, rack, or airbag/clock spring service error: Pinched wiring, an unseated connector, or a damaged clock spring path can interrupt SAS power or CAN circuits.
• Low system voltage or unstable charging voltage: A weak battery or charging issue can cause multiple modules to reset, and U0126 appears as a symptom of network instability.

Diagnosis Steps

Tools you need include a capable scan tool with full network scan, a DVOM, wiring diagrams, and basic back-probing tools. Have a battery charger or maintainer ready. For CAN checks, use an ohmmeter with the battery disconnected. A terminal tension kit and contact cleaner help confirm connector faults without guessing.

1. Run a full vehicle scan and record all DTCs, including pending and history codes. Save freeze frame data for U0126 and any related U-codes. For this communication loss, focus on ignition state, vehicle speed, system voltage, and which modules also reported network faults.
2. Use the scan tool’s network topology or module list. Confirm whether the steering angle sensor (SAS) module appears online. If the tool cannot “see” the SAS at all, treat it as an offline module issue first. If it appears online but sets U0126, suspect intermittent power, ground, or bus disturbance.
3. Decide urgency using pending vs confirmed status. Many network faults act like Type B logic on some platforms, so a pending U0126 may need a second trip to confirm. A hard communication loss usually returns immediately at key-on. Clear codes and cycle the key once to see what returns without a drive.
4. Check fuses and power distribution that feed the SAS and any related gateway. Do this before probing the module. Verify the fuse has power on both sides with the circuit loaded, not just with an ohmmeter.
5. Verify SAS power and ground with voltage-drop tests under load. Back-probe the SAS connector and command the vehicle awake (key ON, engine off). Load the circuit if possible by turning on headlights or using scan tool functions. Measure ground drop from SAS ground pin to battery negative while the module should be operating. Accept less than 0.1 V drop.
6. Inspect the SAS connector, steering column harness routing, and any junction connectors. Look for pulled pins, corrosion, pushed-out terminals, and harness rub points near the column tilt mechanism. Pay extra attention if the vehicle recently had column, clock spring, rack, or airbag work.
7. Check for CAN bus integrity at an accessible point near the SAS or gateway. Key OFF, battery disconnected, and wait for modules to sleep. Measure resistance between CAN+ and CAN- at the connector. A healthy network typically reads about 60 ohms. Readings near 120 ohms or OL point to an open or missing termination. Very low resistance suggests a short.
8. Check CAN bias voltage with ignition ON. Communication line bias voltage only exists when the network is powered. Measure CAN+ to ground and CAN- to ground. A healthy high-speed CAN bus typically sits near 2.5 V on both lines at rest. A line stuck near 0 V or near system voltage indicates a short or a pulled bus.
9. If the bus checks good at the DLC but not at the SAS connector, isolate the harness section. Unplug modules on that branch one at a time as the diagram allows, then recheck resistance and bias. This identifies a shorted module or a harness segment fault without parts guessing.
10. Use a scan tool snapshot during a controlled test if the concern is intermittent. Freeze frame shows conditions when the code set. A snapshot lets you capture live bus status, system voltage, and module online/offline transitions during a wiggle test or road test.
11. After repairs, clear codes and repeat a full network scan. Confirm the SAS appears consistently online. Road test with steering inputs and verify no U0126 returns as pending or confirmed.

Professional tip: If U0126 sets with multiple other U-codes, stabilize battery voltage first and retest. Low voltage resets modules and creates “lost communication” codes that vanish after a charging system fix.

Possible Fixes

• Restore SAS power feed: Replace the correct fuse only after you find and correct the short or overload, then verify voltage at the SAS under load.
• Repair ground connection issues: Clean and tighten the ground point, repair damaged wiring, and confirm less than 0.1 V drop with the module operating.
• Repair CAN harness faults: Fix opens, shorts, or rubbed-through sections near the steering column, clock spring area, or harness junctions, then recheck 60-ohm bus resistance.
• Service connector and terminal fit: Correct spread terminals, remove corrosion, and ensure connectors fully and lock, especially at the SAS and intermediate connectors.
• Correct installation errors after steering column or airbag service: Reroute harnesses, relieve pinched sections, and confirm clock spring and related connectors match the wiring diagram path.
• Replace the SAS module only after circuit and network tests pass: If power, ground, and CAN integrity test good and the module still drops offline, replacement or programming may correct the confirmed fault.

Can I Still Drive With U0126?

You can often drive with a U0126 code, but you should treat it as a safety-related fault. When the vehicle loses communication with the steering angle sensor (SAS) module, systems that rely on steering angle can degrade or shut off. Expect stability control and traction control to disable on many vehicles. Electric power steering may change its assist strategy on some platforms. ADAS features that use steering angle inputs, like lane keep assist, may also stop working. If the steering feels heavy, inconsistent, or the stability light stays on, limit driving and avoid wet or icy roads. If multiple network codes appear at once, or the cluster shows “Service Stabilitrak/ESC/Power Steering,” diagnose it before daily use.

How Serious Is This Code?

U0126 ranges from an inconvenience to a real safety concern. It stays minor when the only symptom is an illuminated warning light and no change in steering feel. The risk climbs when ESC/traction control disables, because the car can understeer or oversteer more easily during a skid. Severity also increases if the network drops out intermittently, since steering-related features can come and go while driving. If the vehicle uses steering angle for ADAS functions, you must not trust lane-centering or lane-keep behavior until you restore communication and confirm correct steering angle data. After any SAS module, clock spring, steering column, or alignment-related repair, many vehicles require a steering angle reset or calibration before the system operates safely.

Common Misdiagnoses

Technicians often replace the steering angle sensor or clock spring too early. U0126 is a communication loss code, not a “bad sensor signal” code. A dead module, a dropped power or ground, or a network wiring fault can all look identical to the scan tool. Another common miss involves skipping a full network scan. If several modules show “U-codes,” the real problem may sit on the shared CAN bus or in a splice pack. People also clear codes repeatedly without checking which modules go offline first. That habit hides an intermittent connection issue. Avoid wasted spending by proving module power, ground integrity with voltage-drop under load, and CAN bus integrity before any parts decisions.

Most Likely Fix

The most common confirmed repair direction for U0126 involves restoring the SAS module’s ability to communicate, not automatically replacing it. . The second frequent direction involves a CAN wiring issue near the steering column area, a harness rub-through, or a disturbed splice after prior steering or dash work. If you restore power/ground and network integrity yet the scan tool still cannot communicate with the SAS module, then module failure or required setup becomes a reasonable next test path.

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: April 7, 2026