Dirtleg
BoostCreep
Background. My 2007 GT has been sitting for most of the last 2 years. I had been fighting a driveline issue which is now fixed thankfully.
About a week before I figured out the driveline issue my check engine light came on. I didn't check it at the time as I was wrapped up on my other issues and I wasn't driving the car.
Fast forward to yesterday I finally pulled the codes and it was a P0345 and P0349. I swapped the sensors side to side, cleared the codes and started the car. Same issue. Problem stayed on the same bank and did not follow the sensor.
At this point I caught on about the alternator issue, and seeing as how I was still running the original alternator, went ahead and installed a rebuilt one today.
Well that didn't solve the issue either.
Next check will be wiring harness. But before I go there I wanted to mention what seems to me like odd behavior for this issue.
Example 1. When I clear the codes, I get a fault code as soon as I start the car. This is normal and would indicate that the sensor wasn't reporting on start up. It does not throw a code prior to engaging the ignition switch.
Example 2. If I turn on the ignition and there is already a fault in the system the check engine light blinks before starting the car if the ignition is left in the on position. Again seems to be normal behavior for this issue.
Example 3. If there is a code when I power on the ignition but clear it before starting the car, I do not get a code on startup or an extended drive (60 miles no code) but it will come back after the next time the key is cycled off and the car is started. This seems odd to me as the fault is not happening on startup like it does in the first example but is waiting for a power cycle.
It seems that if the sensor were not reading on startup, which if I understand correctly, is about the only time this sensor is used, it would throw the code again when starting the engine. The only thing I can think of that would cause it to ignore the sensor in this situation were if it only did the sensor check at key on. But if that were the case why would it wait until the engine was cranked to throw the code?
Also is there another common issue that can cause these diagnostic faults that I haven't clued into yet?
Thanks for reading.
About a week before I figured out the driveline issue my check engine light came on. I didn't check it at the time as I was wrapped up on my other issues and I wasn't driving the car.
Fast forward to yesterday I finally pulled the codes and it was a P0345 and P0349. I swapped the sensors side to side, cleared the codes and started the car. Same issue. Problem stayed on the same bank and did not follow the sensor.
At this point I caught on about the alternator issue, and seeing as how I was still running the original alternator, went ahead and installed a rebuilt one today.
Well that didn't solve the issue either.
Next check will be wiring harness. But before I go there I wanted to mention what seems to me like odd behavior for this issue.
Example 1. When I clear the codes, I get a fault code as soon as I start the car. This is normal and would indicate that the sensor wasn't reporting on start up. It does not throw a code prior to engaging the ignition switch.
Example 2. If I turn on the ignition and there is already a fault in the system the check engine light blinks before starting the car if the ignition is left in the on position. Again seems to be normal behavior for this issue.
Example 3. If there is a code when I power on the ignition but clear it before starting the car, I do not get a code on startup or an extended drive (60 miles no code) but it will come back after the next time the key is cycled off and the car is started. This seems odd to me as the fault is not happening on startup like it does in the first example but is waiting for a power cycle.
It seems that if the sensor were not reading on startup, which if I understand correctly, is about the only time this sensor is used, it would throw the code again when starting the engine. The only thing I can think of that would cause it to ignore the sensor in this situation were if it only did the sensor check at key on. But if that were the case why would it wait until the engine was cranked to throw the code?
Also is there another common issue that can cause these diagnostic faults that I haven't clued into yet?
Thanks for reading.
Last edited: