csigona
Active member
2005.5 BRM. I'm hoping this helps someone else who has similar problems.
After leaving the battery disconnected for some weeks while I did some repairs, I put things back together and found a few new dashboard lights. They were the steering position failure light (little amber steering wheel) and the ESP failure light (little skidding car icon). I read quite a few forum threads, many of which suggested the problem is caused by a bad ground. I fiddled with various things, but got nowhere.
Just to feel like I'm bright enough to manage to fix something, I decided to forget about the lights for now and work on some trouble codes, that weren't (or so I thought) related to the steering position and ESP lights. The OBD2 said that my right rear ABS sensor failed. Sure enough it was bad, and so I replaced it. Not only did the ABS sensor code go away, the steering position light also turned off. Then I went on to another code: G65 high pressure A/C sensor was no good. I don't much care about A/C since I hardly ever use it up where I live, but I was in the mood to clear codes, and guess what. Not only did the G65 code go away, but the ESP light went out.
There was no intelligence involved, just dumb luck. How should one know that the ABS sensor affects the steering position sensor, or that G65 affects ESP? Clearly the computer believes they are related! One could make a case that the computer wants to calibrate the wheels and steering before enabling the steering position stuff, not that I really buy it, but I can't see what the high pressure A/C sensor has to do with the Electronic Stability Program (ESP). Somehow, when the computer has to recalibrate various stuff because the battery was out, things that previously didn't matter suddenly do. The ABS sensor hasn't worked for months, similarly G65, but neither affected steering or ESP until after I removed and reinstalled the battery.
The moral, at least from my viewpoint, is to keep your codes clear.
After leaving the battery disconnected for some weeks while I did some repairs, I put things back together and found a few new dashboard lights. They were the steering position failure light (little amber steering wheel) and the ESP failure light (little skidding car icon). I read quite a few forum threads, many of which suggested the problem is caused by a bad ground. I fiddled with various things, but got nowhere.
Just to feel like I'm bright enough to manage to fix something, I decided to forget about the lights for now and work on some trouble codes, that weren't (or so I thought) related to the steering position and ESP lights. The OBD2 said that my right rear ABS sensor failed. Sure enough it was bad, and so I replaced it. Not only did the ABS sensor code go away, the steering position light also turned off. Then I went on to another code: G65 high pressure A/C sensor was no good. I don't much care about A/C since I hardly ever use it up where I live, but I was in the mood to clear codes, and guess what. Not only did the G65 code go away, but the ESP light went out.
There was no intelligence involved, just dumb luck. How should one know that the ABS sensor affects the steering position sensor, or that G65 affects ESP? Clearly the computer believes they are related! One could make a case that the computer wants to calibrate the wheels and steering before enabling the steering position stuff, not that I really buy it, but I can't see what the high pressure A/C sensor has to do with the Electronic Stability Program (ESP). Somehow, when the computer has to recalibrate various stuff because the battery was out, things that previously didn't matter suddenly do. The ABS sensor hasn't worked for months, similarly G65, but neither affected steering or ESP until after I removed and reinstalled the battery.
The moral, at least from my viewpoint, is to keep your codes clear.
Last edited: