OBD-II trouble code
U0328: Software Incompatibility With Steering Angle Sensor Module
A calibration mismatch on the sensor that reports where the steering wheel is. What makes this one distinct is the zero point: the sensor counts angle relative to a stored straight-ahead reference, and a mismatch that invalidates that reference gives every system downstream a confident, wrong answer.
Quick facts
- System
- Network
- Category
- Network Communication
- Severity
- Medium severity
- Drivable
- Usually safe to drive short-term
- Repair cost range
- $120 – $550
- DIY difficulty
- Shop recommended
Browse every code in U0300–U0354, or start from the full code library.
What does U0328 mean?
U0328 is set when a module on the network finds that the steering angle sensor module is running a calibration that does not belong to the matched set the vehicle expects. Communication is working. What is wrong is which software the sensor is executing, and on this particular sensor that has an unusual consequence.
The steering angle sensor does not directly know where straight ahead is. It reports rotation, and the meaning of that rotation depends entirely on a stored zero point the vehicle learned during calibration. Everything downstream — stability control, the electric power steering assist curve, lane keeping, adaptive headlamps — is doing arithmetic against that reference. When the module's software is replaced or mismatched, the zero can be invalidated or reinterpreted, and the result is not a missing signal. It is a plausible signal that is wrong by a constant amount.
That produces a complaint people do not associate with an electronic fault at all. If the car believes the wheel is held a few degrees to the left while it is actually pointing straight, stability control sees a vehicle that ought to be turning and is not, and on some systems it responds by applying a small amount of brake to one wheel. The driver reports a car that pulls, or that feels like it is dragging a brake, or that steers heavier one way than the other because the assist curve is being read at the wrong point. Wheel alignment gets checked, the brakes get checked, and the fault is in a calibration file.
This module also has a service history that no other member of this code group shares. It is normally part of the clockspring stack behind the steering wheel, which means it is disturbed by airbag work, column repairs, wheel changes and anything that requires the wheel to come off. A steering angle software or calibration fault very often traces back to a job that had nothing to do with electronics, and asking what was last done to the steering column is a faster route to the answer than reading part numbers.
There is a cost consequence worth flagging before authorising work. On vehicles with camera or radar driver assistance, the aim of those sensors is calibrated with reference to steering angle zero. Changing this module's software and resetting its reference can invalidate a previously correct camera calibration, so the job may need an ADAS recalibration afterwards — which frequently costs more than the reprogramming that caused it. Find out whether that applies before quoting, not after.
Common causes
- Steering angle sensor or clockspring assembly replaced without VIN-specific programming
- Zero point reset skipped after column, airbag or steering wheel work
- Stability control module updated while the steering angle sensor calibration was left behind
- Used sensor installed still carrying another vehicle's learned reference
- Reflash interrupted or performed with a file for a different steering system variant
- Calibration performed with the wheels not actually centred, storing a wrong zero
- Software applied for a vehicle with different steering ratio or assist hardware
Symptoms
- Vehicle pulling or feeling as though a brake is dragging on a straight road
- Steering assist noticeably heavier turning one way than the other
- Stability or traction control warning lamp illuminated
- Lane keeping, lane departure warning or adaptive cruise unavailable
- Adaptive headlamps aiming to one side when travelling straight
- Fault appearing after airbag, clockspring or steering column work
- Steering itself feeling mechanically normal despite the warnings
Diagnostic steps
- 1.Ask what was last done to the steering column, airbag or steering wheel, because this module sits in the clockspring stack and is disturbed by work that has nothing to do with electronics.
- 2.Read the reported steering angle with the vehicle standing still and the wheels physically straight — a non-zero value there is the fault in its clearest form.
- 3.Check the reported angle against the actual wheel position at full lock in both directions to detect a scaled rather than merely offset reading.
- 4.Read the module's calibration part number and compare it against the approved set for the VIN and the steering variant fitted.
- 5.Note whether the complaint is a pull or an uneven assist weight, since those are what an offset zero feels like from the driver's seat.
- 6.Reprogram to the matching calibration, then perform the zero point reset with the wheels genuinely centred rather than approximately so.
- 7.Establish whether the vehicle has camera or radar driver assistance, because resetting steering angle zero can invalidate a previously correct ADAS aim.
- 8.Road test on a straight, level road and confirm both that the code stays away and that the pull or assist imbalance has gone.
Repair cost
$120 – $550
Reprogramming and resetting the steering angle sensor is $120 to $300, rising to $300 to $550 where the calibration is dealer-only or the clockspring assembly itself is replaced. The item that catches people out is what follows: on vehicles with camera or radar driver assistance, changing this module's reference can require a full ADAS recalibration afterwards, and at $250 to $700 that is frequently the larger half of the bill. Establish whether it applies before agreeing a price.
Estimate your repair
Run the numbers for your vehicle
Open the Repair Cost Estimator with module communication / can bus diagnosis preselected. Adjust labor rate and vehicle category to fit your situation.
DIY vs shop
Leave this one to a qualified shop. The barrier here is module programming, security access, and bus-level diagnosis that need manufacturer-grade scan tools and the credentials to use them. DIY attempts often produce a more expensive problem than the original code.