Hi all, I did a thermostat tower replacement last week, another thread. All hooked back up and restricted performance and red engine light. OBDll gives me P0332 low voltage bank 2. I erased code after cleaning connection and looking for a bare wire. No help. Figured it might be a bad ground as the leaking thermostat had a lot of antifreeze in the valley. I took the bolt off the sensor and did a bit of cleaning with a soft wire brush and re installed. I left it disconnected and started the car, shut off and plugged it back up, started the car and the restricted performance was gone but the red engine light stayed on. Did another erase on the P0332 and all was OK????
My buddy called and said restricted performance came back on the way home, but the funny thing is no problem with performance. I told him to drive it a couple of days and see what happens, in the mean time I picked up a SU7012 from Autozone. Oh, I did a hard reset to no avail. Worse part, he gave me the "I know you broke my car look".
Just weird and wonder why it almost worked??

Wayne

 

This is the main reason why I only work on my car.

With a Jaguar you have to have one of two things either the skills to do your own work or the skills to earn the money to pay some one to do the work.

 

Or the ability to learn how to do your own work.

 

Sometimes it's great to be right. I told my buddy to drive the car for a few days and see if the restricted performance and check engine light would go away on their own.
The second day the R/P went away and the third the red check engine disappeared. I was having trouble getting rid of the P0332 code. I think when I was first having trouble and disconnected the Knock Sensor, cleaning it and the surface it sets on, then I think the key trick was to leave it disconnected and starting the car and making the car try to find it, shut off and connected, code did disappear, but came back on his way home. All is well and it's been about a week
Did I figure something out or just got lucky??

Wayne

 

Probably your code reader never really cleared the code. Each item in a system has specific parameters as to what will cause a code to set (how many times did it occur, does it require it to happen during a full drive cycle or just anytime it occurs, does the engine need to be above 183.2234 degrees and at 45+ mph, blah, blah, blah) and how many non-error 'trips' are required for the ECU to clear them itself.

 

Yeah, what you said.
Just kidding, I was figuring something like that and got lucky.
Checked for leaks today and all is well.

Wayne