P0332 code on just bought F-Pace
Hello all,
The wife and I drove to Houston to pick up what appeared to be a fairly pristine 2017 F-Pace. Of course, after barely getting 5 miles down the road, the CEL light comes on. We take it back to the dealership, and they read out the code, and it's P0332 (Knock Sensor 2 Circuit Low Input Bank 2). The battery was actually low, so they replaced it, since I remembered when my XF battery would occasionally get low, I'd sometimes get weird codes. On the drive home to Austin, the CEL lit up again, but no noticeable performance issue. I read the code out today, and it's the same one.
Wondering if anyone else has thrown this code, and if it could possibly be due to the gas having sat in the car for some time. Saw some other folks on the FPaceforum.com (which I was unaware of until today. Is it affiliated with this site?) indicate the F-Pace seems sensitive to gas. Would appreciate any info you can provide.
The wife and I drove to Houston to pick up what appeared to be a fairly pristine 2017 F-Pace. Of course, after barely getting 5 miles down the road, the CEL light comes on. We take it back to the dealership, and they read out the code, and it's P0332 (Knock Sensor 2 Circuit Low Input Bank 2). The battery was actually low, so they replaced it, since I remembered when my XF battery would occasionally get low, I'd sometimes get weird codes. On the drive home to Austin, the CEL lit up again, but no noticeable performance issue. I read the code out today, and it's the same one.
Wondering if anyone else has thrown this code, and if it could possibly be due to the gas having sat in the car for some time. Saw some other folks on the FPaceforum.com (which I was unaware of until today. Is it affiliated with this site?) indicate the F-Pace seems sensitive to gas. Would appreciate any info you can provide.
The F-Pace uses "extended" error codes which require JLR Pathfinder diagnostics to read with absolute accuracy. There are three extended codes listed for P0322 but the possible causes in the Workshop Manual decode are the same for all of them! It shows water in the connector or a failed sensor.
A replacement battery in the first instance was a good call and you should ensure this is fully charged. Even one supplied as "charged" should be trickle charged overnight before fitting.
Fuel could also be the cause. The smaller 25t that I have can set a code for variable timing solenoid which is fuel related. A Technical Bulletin allowed replacement under warranty but this does not fix it and it can return after a refuel. The knock sensor on the 35t could be a similar issue.
I'd fully charge the battery, run the fuel tank low and fill with fresh (the drive home looks to be only around 260 miles?) then clear codes. See if it comes back again before throwing new parts at it.
Graham
A replacement battery in the first instance was a good call and you should ensure this is fully charged. Even one supplied as "charged" should be trickle charged overnight before fitting.
Fuel could also be the cause. The smaller 25t that I have can set a code for variable timing solenoid which is fuel related. A Technical Bulletin allowed replacement under warranty but this does not fix it and it can return after a refuel. The knock sensor on the 35t could be a similar issue.
I'd fully charge the battery, run the fuel tank low and fill with fresh (the drive home looks to be only around 260 miles?) then clear codes. See if it comes back again before throwing new parts at it.
Graham
Thread
Thread Starter
Forum
Replies
Last Post
Austin7
F-Pace (X761) / C-X17
0
Mar 27, 2017 08:31 AM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)









