SOLVED: Warning lights - please help!
- Thread starter David
- Start date
I don’t think the crank position sensor is “hard topped”, I think the connector has been dislodged.
The error code I found: “2A94 crankshaft sensor, SIGNAL”
I’d interpreted that as the ECU doesn’t acknowledge it is even plugged in.
Am I right in thinking that if it had failed it’d still be closing the circuit, and the ECU would instead know it was there and not working?
I’m feeling optimistic...
There are 6 crankshaft codes:
2A94 crankshaft sensor, signal
2A95 crankshaft sensor, synchronisation
2A96 crankshaft sensor, tooth failure
2A97 crankshaft sensor, gap failure
2A98 crankshaft - inlet camshaft, correlation
2A99 crankshaft - outlet camshaft, correlation
...I reckon if it was büggered, it’d throw the sync code.
Hopefully I’ll get a chance tomorrow to check the connection. Hoping I can reach it from under the car.
Last edited:
I changed the one on my Z3 from underneath David, albeit on a ramp. May be easier on your engine type. Hope it's the fix you need mate.
Tony.
Tony.
I have just removed 10 off topic/pointless posts. Please don't clutter up threads with off topic banter posts while people are trying to offer serious assistance - plenty of other general threads available for you to do that in.
Last edited:
From those codes on that list, I would say signal and sync.. so you might be on the right path. Might be worth disconnecting the sensor and then reading the code to see if it gives the same.
SOLVED!!!
This morning, before I attempted jacking the car up, I tried going in blind and reaching my hand under the starter motor from above the engine.
I felt around a bit (hello sailor!) and found what I thought must’ve been the crankshaft sensor connector. Gave it the lightest of pulls and it fell out of place, without any resistance.
Plugged the connector back in, and gave it another tug (ooh aah!) and it did not budge.
Turned the key, and hey presto, the car started on the button, without any warning lights, and with power steering back.
A big thank you to everyone that helped, for their guidance and advice. Contrary to the opinion of a select minority, I do know what I’m up to, and I’m learning even more everyday thanks to this great forum.
...How much do you reckon a mechanic would have charged me by the time they solved that one?
Celebratory test drive time I think!
David
Glad its all sorted.... and the is what the forum is about.. bouncing thoughts and ideas and a lesson... We never stop learning....
Good old fashioned debugging and you solved the problem 
Got to remember that the warning lights are frequently latched. It's quite possible that one fault condition then triggers the next and so on. It's equally possible that the code is written that one thing has to be cleared or ok before the code to clear the next is accessible and it's possibly deliberate to protect (even quite unrelated) systems. Just the one problem can cascade as the code executes and gives false indications and disables other subsystems. The computer says no!
Reinstate the correct inputs and everything springs into life again. Just a case of finding that one input causing the problem.
Got to remember that the warning lights are frequently latched. It's quite possible that one fault condition then triggers the next and so on. It's equally possible that the code is written that one thing has to be cleared or ok before the code to clear the next is accessible and it's possibly deliberate to protect (even quite unrelated) systems. Just the one problem can cascade as the code executes and gives false indications and disables other subsystems. The computer says no!
Reinstate the correct inputs and everything springs into life again. Just a case of finding that one input causing the problem.
Indeed. My observation was with the benefit of hindsight. Tony did all the hard thinking
Last edited by a moderator:
Those were just thanks for the congratulations.
@t-tony most certainly deserves and has received a thank you from me.