I know this is the secondary Oxygen sensor.

Here's my question about this though.

I have a catted (spun metal cat) ZZP downpipe. It's been on for 20-25k miles.
Do you think that finally caused it to throw a code or is the sensor likely to be actually bad. I'm leaning towards that the sensor is actually bad because it sounds to me like it's not heating properly.

Oh.... and anyone know the price of these off hand?

 

I threw it about 100 miles after putting their catted pipe on, got it deleted from Vince when I got tuned

need to get him to delete P2096, it comes up every month or so, not near as frequent as the other did...

 

The sensor i wanna say is $140 or right around there. I could be wrong but thats the number that pops into my head from what the dealer told me. One dealer wouldnt fix it under warranty and another did so i ended up paying nothing

 

Tune it out, there is nothing wrong with the sensor, I used to pop it once in a while since I'm catless. I disabled all the secondary 02 codes.

 

I would replace the sensor. It's ok if you delete P0420 and P013E, but not this one. You need a working O2 sensor back there for DFCO so you don't screw up some of your fuel trims.

 

You'll have to explain that to me, sorry. DFCO cuts the fuel and lambda reads 1.99 on the primary 02 that controls the lambda in the ecu. If the torque management injector table is set to 15's in the right hand column, DFCO works fine. 0's everywhere else.

 

I was under the impression that for DFCO to work, the rear O2 needs to be working.

 

As far as I know, the rear 02 does no control, only alarms on cat emission issues. Just going off what I have read over the last two years here and on HPTuners. With the 02 codes disabled I still see lambda setpoints up to 1.04 and actual reads 1.99 so I have to believe DFCO is still working.

I know when I had the DFCO disabled with all 0's in the inj table mentioned earlier I would set a CEL on long DFCO's almost daily. It wouldn't cut fuel completely then.

I did just look and I do not have P141 disabled though, that means I never got the error in 1.5 years.

You may be correct on it's function.