08 Ford CVPI Three of the Emission Readiness Monitors not setting...

Status
Not open for further replies.
dogememe

dogememe

Joined
Apr 15, 2017
Messages
5,476
Location
Napa, CA.
I purchased the 2008 Crown Vic P71 with 166K miles with a P0152 and so I replaced the B2S1 oxygen sensor. It seems to have solved the problem, because after I cleared the codes it didn't come back.

I drove it several hundred miles across a week or so and the monitors weren't setting. I had a weird hesitation in the transmission and it just wasn't driving quite right. Suspected a bad MAF sensor (despite the lack of codes indicating as such), and since my 2010 Ford Escape uses the same MAF sensor, did the switcheroo and yes, the Vic's MAF sensor was definitely bad. The sensor I moved over from the Escape is fairly new - maybe 6 months old. I left it in the Vic and put a new one in the Escape. Cleared the codes by disconnecting the battery for about 30 minutes (meanwhile I did clean the throttle body, it was nasty). Now, my car shifts and drives great - my "transmission issue" is gone and it's perfect. Unfortunately, I'm having the same problem with a few of the monitors not setting (the rest set quickly no problem):

-Catalyst Mon
-Oxygen Sens Mon
-Oxygen Sens Htr

I've done all sorts of Googling and Binging and found all these different drive cycles, some of them oddly specific (drive exactly 40mph for 4 minutes) but that's pretty much impossible on public streets? I have owned over a dozen cars and never had this much trouble getting the computer ready for smog. I remember in my 07 CVPI I replaced the battery and then sold the car a while later and the monitors were all OK because I had no trouble smogging it prior to selling it.

I do have a P1233 "non-MIL" code stored in the computer. It always comes back after I clear the codes. Would this prevent the monitors from setting? I tried to so some research on the P1233 code but most people with this code experience a crank no start condition while my car starts and runs perfectly.

Thank you all for your help, it's imperative I take care of this situation because since I'm in California I can't register the car/transfer the title into my name til I can smog it.
 
Did you disconnect the battery for a while (like, go have a cup of coffee while)? That should clear any lingering codes.

The Oxygen sensor heater one is the most concerning to me, I believe that it should run that monitor pretty quickly as it's looking to make sure the oxygen sensor circuit is complete and pulling the right current. Maybe it runs when the others do.

For the catalyst and Oxygen sensor monitors to run, you have to accelerate hard (to ensure the catalysts are up to temp) and then keep going pretty fast. I've been able to get them to run consistently on a stretch of road that is dead straight and flat with a similar powertrain (4.6, 47RW in a van). Just remember not to floor it and don't lift up on the pedal for any length of time or the test will abort. I accelerate at 3/4 throttle to 50 MPH and then cruise for a mile. Works every time for mine.

From what I can tell, the P1233 is for a fuel pump driver module taking a day off. You might have a pending "side of the road" event with those, they seem unreliable. Regardless, it sounds like a "works or it doesn't" situation and shouldn't impact the emissions testing.
 
Check that there is power to the sensor heater circuit. Check that the sensor outputs are cycling on the live data.
 
Originally Posted by MichiganMadMan
Did you disconnect the battery for a while (like, go have a cup of coffee while)? That should clear any lingering codes.

The Oxygen sensor heater one is the most concerning to me, I believe that it should run that monitor pretty quickly as it's looking to make sure the oxygen sensor circuit is complete and pulling the right current. Maybe it runs when the others do.

For the catalyst and Oxygen sensor monitors to run, you have to accelerate hard (to ensure the catalysts are up to temp) and then keep going pretty fast. I've been able to get them to run consistently on a stretch of road that is dead straight and flat with a similar powertrain (4.6, 47RW in a van). Just remember not to floor it and don't lift up on the pedal for any length of time or the test will abort. I accelerate at 3/4 throttle to 50 MPH and then cruise for a mile. Works every time for mine.

From what I can tell, the P1233 is for a fuel pump driver module taking a day off. You might have a pending "side of the road" event with those, they seem unreliable. Regardless, it sounds like a "works or it doesn't" situation and shouldn't impact the emissions testing.


Previously after replacing the o2 sensor I cleared the codes using a scanner. This time, after changing the MAF sensor, I disconnected the battery for at least 30 minutes. I've done quite a bit of merging on the highway and then cruising - perhaps I have to give it more gas. I will try it again! I do generally drive somewhat assertively... today I took a 2 hour drive which included a lot of driving at about 40mph... some straight driving and some curves with braking and acceleration. I really do think it should have set by now.

As for the P1233, yeah, it's weird, if my fuel pump module was dead I wouldn't be going anywhere!
 
Last edited:
Originally Posted by spasm3
What oxygen senor did you replace? What brand did you use?


Which o2 sensor I changed is in the first line of my post... bank 2 sensor 1. I used a Bosch. I would have preferred to use an NTK, Denso, or Motorcraft, but it was the only one that I could get the same day through work. I did use a direct fit one, not a universal one.
 
Hmmm. P0152 is high voltage for B2S1. Was it getting putrid gas mileage?

The thought that is going through my head is that it was shorted to B+ somewhere in the harness, causing the ECM to see high voltage on both the sensor and heater circuit. See any pinched or narfed wiring harness?

I agree with mk378: see if the thing is cycling with the engine running, and check the heater circuit. It should be off when the key is off and be hot when you turn the key to run and stay there.
 
Originally Posted by MichiganMadMan
Hmmm. P0152 is high voltage for B2S1. Was it getting putrid gas mileage?

The thought that is going through my head is that it was shorted to B+ somewhere in the harness, causing the ECM to see high voltage on both the sensor and heater circuit. See any pinched or narfed wiring harness?

I agree with mk378: see if the thing is cycling with the engine running, and check the heater circuit. It should be off when the key is off and be hot when you turn the key to run and stay there.


I only drove it for about a day with the bad O2 sensor, so IDK about fuel economy. According to the live data on the scanner the o2 sensors are working fine. After replacement of the O2 sensor, I ended up about 15MPG, which is right in line with my two previous Vics. I'm hoping for better now that I changed the faulty MAF sensor but honestly I don't expect much more out of a V8 RWD beast given that I'm not exactly a grandma style of driver and do a lot of city driving in traffic.
 
Last edited:
Originally Posted by Chris142
The code could keep it from running its monitors.


^This.

If the Oxygen sensors aren't working 100% right, there is no way it will run the catalyst test as it needs them to determine if they are working.
 
Originally Posted by MichiganMadMan
Originally Posted by Chris142
The code could keep it from running its monitors.


^This.

If the Oxygen sensors aren't working 100% right, there is no way it will run the catalyst test as it needs them to determine if they are working.


Hmm, but my code has nothing to do with o2 sensors and is related to my fuel pump driver module. does it matter?
 
Originally Posted by clinebarger
The P1233 could be from a cut/open Fuel Pump Monitor Circuit, Being a P71......Wouldn't surprise me a bit if a wire was cut during the "decommissioning process"

Yes. They are not nice. Both my P71s had to have wiring repaired in the trunk due to cut wires. Since the FPDM is working the car is running but it doesn't 'know' what the FPDM state is. In other cases where there is a no-start with that code, well the FPDM is dead and that would be why
 
Originally Posted by Colt45ws
Originally Posted by clinebarger
The P1233 could be from a cut/open Fuel Pump Monitor Circuit, Being a P71......Wouldn't surprise me a bit if a wire was cut during the "decommissioning process"

Yes. They are not nice. Both my P71s had to have wiring repaired in the trunk due to cut wires. Since the FPDM is working the car is running but it doesn't 'know' what the FPDM state is. In other cases where there is a no-start with that code, well the FPDM is dead and that would be why

Alright, I'll look into that wiring. I also have to fix my horn since it's dead. I'm still wondering if the P1233 has anything to do with my o2 sensor monitors or not?
 
Originally Posted by dogememe
Originally Posted by Colt45ws
Originally Posted by clinebarger
The P1233 could be from a cut/open Fuel Pump Monitor Circuit, Being a P71......Wouldn't surprise me a bit if a wire was cut during the "decommissioning process"

Yes. They are not nice. Both my P71s had to have wiring repaired in the trunk due to cut wires. Since the FPDM is working the car is running but it doesn't 'know' what the FPDM state is. In other cases where there is a no-start with that code, well the FPDM is dead and that would be why

Alright, I'll look into that wiring. I also have to fix my horn since it's dead. I'm still wondering if the P1233 has anything to do with my o2 sensor monitors or not?

Looks like it. Sensors OK has a laundry list including "no system failures affecting fuel" that have to be good before it will try running the monitor.

2019-02-18 17_54_11-Pale Moon.webp
 
Last edited:
Originally Posted by dogememe
I'm still wondering if the P1233 has anything to do with my o2 sensor monitors or not?


I don't have a definitive answer to that, Maybe Colt does? GM DTC descriptions state that information while Ford doesn't......At least in my sources.
 
So it looks like the module is sending power to the fuel pump otherwise it would not be running. But the pcm is not seeing a return signal from the fpdm about fuel pressure?

Perhaps check fuel pressue, if its low in this setting , where you might expect the pcm to call for more pressure, perhaps its the fuel pump. If the fuel pressure is within whatever the spec is or higher, the FPDM is the culprit ?
 
Last edited:
Originally Posted by spasm3
So it looks like the module is sending power to the fuel pump otherwise it would not be running. But the pcm is not seeing a return signal from the fpdm about fuel pressure?

Perhaps check fuel pressue, if its low in this setting , where you might expect the pcm to call for more pressure, perhaps its the fuel pump. If the fuel pressure is within whatever the spec is or higher, the FPDM is the culprit ?

No, the FPDM is running and modulating the pump correctly, or there would be a code about fuel pressure. This is purely about the computer seeing a return signal from the FPDM which amounts to "Hey Im here and I have a valid signal; Everything is A-OK"
See my previous post.
 
Status
Not open for further replies.

Similar threads

M
2002 Sienna emission/CAT system diagnosis?
Replies
11
Views
367
MichaelRS
dnewton3
2023 ES350 multiple system errors and root cause
Replies
16
Views
482
eljefino
B
'13 Outback - Check Engine Light, Brake Light Flashing, Cruise Control Light Flashing
2
Replies
22
Views
18K
14Accent
S
When will a CEL/MIL turn off by itself?
2
Replies
20
Views
4K
The motor guy
Nick1994
AX4N, No O/D - Flashing Light
Replies
18
Views
3K
Nick1994
Back
Top Bottom