4x4 light on. 5F0E code. Steering angle sensor or Yaw Sensor?

[andrewwynn]

The rebuild kit is not exactly cheap

https://www.ebay.com/itm/113538959838

But the genuine BMW part is $330 or so from fcpeuro.

I saw a bunch of knock off SAS for less than the repair kit but they would also need coding.

I've also seen just bushes but for e65, for about $10-15. Not sure if they would work.

That said if you are getting good readings from SAS you need to find the spot in the software to read yaw sensor.

The bigger problem is that quote often the problem is internal to the abs module. The bond wires from the PCB to the connector break and then you get indication that the sensor is bad.

One more thing: when SAS goes bad it usually means it's got "scratchy spots" not that it stops reading, so if you can graph the real-time data and sweep through the rotation to confirm it's smooth the entire way no spikes, that can help eliminate the SAS from the equation.

I don't know if the yaw sensor needs coding but my understanding is the SAS does.

[RocketyMan]

Originally Posted by Kraut74

This is not the first time working on BMW's. I also have an M5 and family has other X5's.....So you are going to have to take my word for it.

This is the first time I have been stuck trying to figure out a code and I don't want to buy parts for the sake of buying parts

Well if youre familiar with BMWs then I would be using INPA instead of ISTA as ISTA is rather clunky. It's nice, but clunky.

To andrew's point, you need to be actually reading what the DSC is interpreting the data is. INPA does not have graphing capability in terms of plotting, but it does have bar graphs for typical ranges. The reason why andrew suggests this as you can have sensors fail within range and do funky things because the DSC has those printed bond wires that can and do go bad.

I've used ISTA a couple times and have got it to do some service routines as it is possible.


Here is just an example of a DSC and the values it's reporting using INPA. Clear, concise, and no fluff.


Good luck. And let us know what you find.

[Kraut74]

Originally Posted by RocketyMan

Well if youre familiar with BMWs then I would be using INPA instead of ISTA as ISTA is rather clunky. It's nice, but clunky.

To andrew's point, you need to be actually reading what the DSC is interpreting the data is. INPA does not have graphing capability in terms of plotting, but it does have bar graphs for typical ranges. The reason why andrew suggests this as you can have sensors fail within range and do funky things because the DSC has those printed bond wires that can and do go bad.

I've used ISTA a couple times and have got it to do some service routines as it is possible.


Here is just an example of a DSC and the values it's reporting using INPA. Clear, concise, and no fluff.


Good luck. And let us know what you find.

I have INPA on the computer as well (I believe it's INPA. Only used it for programming my M5). I just use ISTA for basic diagnostics and such. I will run INPA this weekend

[RocketyMan]

Originally Posted by Kraut74

I have INPA on the computer as well (I believe it's INPA. Only used it for programming my M5). I just use ISTA for basic diagnostics and such. I will run INPA this weekend

That's good! Connect your laptop and literally HOP in and see what the accelerometers report.

[Kraut74]

Originally Posted by RocketyMan

That's good! Connect your laptop and literally HOP in and see what the accelerometers report.

Dedicated desktop. Only garage diagnostics

[andrewwynn]

I recommend having foxwell scanner for live readings and graphing. Even if you already have computer it’s nowhere near as nice to compare a graph of vanos angle request vs. actual for example. Also for road trips having 2nd level scanner to read transmission codes etc can be priceless.