Another O2 thread
#1
Another O2 thread
About a month ago, my car displayed a P1647 code. Therefore I replaced the sensor (last week) with a Denso sensor from NAPA. The next day, the code cleared on its own (Tuesday). I drove back and forth to work the rest of the week without issue. On Friday night, when I left the house to run an errand the MIL came on again. I checked codes and now I have P1646 and P1647!!!
I figured I might have the new unit die faster than normal since it was a cheapo replacement, but the likely hood of the brand new Bank two sensor and the old bank one sensor failing at the exact same time is preposterous.
Has anyone else seen such a thing? Is one of the fabled 'hard PCM' resets (ground to positive for 30 seconds) in order here?
Thanks in advance!
I figured I might have the new unit die faster than normal since it was a cheapo replacement, but the likely hood of the brand new Bank two sensor and the old bank one sensor failing at the exact same time is preposterous.
Has anyone else seen such a thing? Is one of the fabled 'hard PCM' resets (ground to positive for 30 seconds) in order here?
Thanks in advance!
#2
#3
After the PCM reset the P1647 never came back. The only errors was P1000 and P1646. That evening I picked up a new O2 sensor and placed it in the Bank 1 sensor 1 location. I cleared the codes. The P1000 hung around as pending.
The next day I drove to work and back and never got the MIL to come on again. Out of fear of generating another CAN error, I did not plug my scan tool into the car again. I pulled into the local garage and got a sticker after passing OBDII testing.
Lesson learned. If the car is throwing codes like crazy, reset the PCM with the discharge method. THEN run and recheck. Some of the codes are wrong and will mislead you.
For reference my scanner is an Autel MS-509
Thanks,
Craig
The next day I drove to work and back and never got the MIL to come on again. Out of fear of generating another CAN error, I did not plug my scan tool into the car again. I pulled into the local garage and got a sticker after passing OBDII testing.
Lesson learned. If the car is throwing codes like crazy, reset the PCM with the discharge method. THEN run and recheck. Some of the codes are wrong and will mislead you.
For reference my scanner is an Autel MS-509
Thanks,
Craig
#4
Hey p1000 will never clear it's a cycle issue that ford recalled the DMV will not fail you for - but P1647 I have that code popping up I understand you replace the sencers can you give us the instruction on how you replaced it - I'm in the process of replacing mine but before I do want to do it right - thanks
#5
Are you getting the banks around the wrong way?
I've just delt with this issue where previous owner had 1646 fault and he replaced what he thought as bank 1 but he replaced bank 2.
P1646 is bank 1 which is the sensor in the manifold at the back of the engine (bulkhead)
I would assume P1647 is bank 2 which is in the manifold at front of car (radiator)
From previous experience of other cars mainly fords the P1000 code means the car needs to be driven for a while so that all sensor checks can be done around the engine after codes have been cleared and your trying to read the codes to soon after clearing previous codes.
I'm sure someone will correct me if i wrong
I hope this helps
I've just delt with this issue where previous owner had 1646 fault and he replaced what he thought as bank 1 but he replaced bank 2.
P1646 is bank 1 which is the sensor in the manifold at the back of the engine (bulkhead)
I would assume P1647 is bank 2 which is in the manifold at front of car (radiator)
From previous experience of other cars mainly fords the P1000 code means the car needs to be driven for a while so that all sensor checks can be done around the engine after codes have been cleared and your trying to read the codes to soon after clearing previous codes.
I'm sure someone will correct me if i wrong
I hope this helps
Thread
Thread Starter
Forum
Replies
Last Post
Marka
S-Type / S type R Supercharged V8 ( X200 )
22
09-11-2016 12:09 AM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)