Anybody experienced steering angle sensor failing twice?

[bmw540san]

Po had it replaced at the dealer in 2010 with 60k on clock.

Now at 106K I'm getting random well know trifecta of lights ( ABS / BRAKE / DSC) which quickly goes away after doing the re-calibration with full left and right steering wheel movement cycle.

No codes found with my AutoEnginuity which is way superior to generic scan tool and it does have enhanced mode to deal with Airbag and ABS codes.

I can get the new genuine BMW sensor for $130 shipped (really good price) but I'd hate to replace good sensor.

I did all the other usual checking: voltage issues, speed sensors etc...

Having 2 older E39's with ASC that don't have this sensor and considering I've had the X5 for 2 years now, I'm not really experienced much with DSC and steering angle sensor.

Any thoughts?

Thanks.

[g300d]

SAS is not the only cause of the trifecta.

I would suggest getting it scanned with BMW software to start narrowing it down.

Edit: When I had to do the SAS in the 4.6, it threw an SAS code and trifecta did not disappear when turning lock to lock. That how I recall people having SAS problems describing them as well. Yours situation sounds different?

[bmw540san]

Originally Posted by g300d

SAS is not the only cause of the trifecta.

I would suggest getting it scanned with BMW software to start narrowing it down.

Edit: When I had to do the SAS in the 4.6, it threw an SAS code and trifecta did not disappear when turning lock to lock. That how I recall people having SAS problems describing them as well. Yours situation sounds different?

Yes, it's different.
While AutoEnginuity is not GT1, DIS or some high end aftermarket scan tools, it does have capabilities to read stored codes for powertrain, ABS, Airbag etc... even without CEL or lights present on dash.
I'm just going from assumption that full right and full left cycle are the way to re-calibrate the SAS and it turns off the lights in my case.
If it was something such as speed sensor or DSC module, I've always found stored codes in DME with AutoEnginuity.
On the other hand, SAS are known to go bad but twice in relatively short lifespan?

[Fifty150hs]

Originally Posted by bmw540san

Yes, it's different.
While AutoEnginuity is not GT1, DIS or some high end aftermarket scan tools, it does have capabilities to read stored codes for powertrain, ABS, Airbag etc... even without CEL or lights present on dash.
I'm just going from assumption that full right and full left cycle are the way to re-calibrate the SAS and it turns off the lights in my case.
If it was something such as speed sensor or DSC module, I've always found stored codes in DME with AutoEnginuity.
On the other hand, SAS are known to go bad but twice in relatively short lifespan?

just had to replace my SAS. Only light I got was the DSC warning light. Read the codes and it indicated a bad SAS. Cleared the code and did the lock to lock re-calibration and DSC light went out. As soon as I started to drive it came back on. Checked again and it was throwing the SAS code again. Replaced the SAS. If you do you have to take it to someone with a BMW computer as it has to be programmed.

[g300d]

To add to the above, INPA I believe can show the actual values and computed angle the sensor is showing, in real time. That would help a lot in determining if the sensor is bad.

[Fifty150hs]

Originally Posted by g300d

To add to the above, INPA I believe can show the actual values and computed angle the sensor is showing, in real time. That would help a lot in determining if the sensor is bad.

Checked that also. When the sensor is bad it doesn't show anything.

[bmw540san]

Good to know as well. Thanks guys.