O2 sensor failure reported by Durametric.

OK, when I check for readiness codes using Durametric or VAG-COM I get failure of the O2 sensor : I do not know if that is just a normal reading on our cars or something specific to my car. Can someone here check their modified or even better stock car and tell me what you see? I am not sure if this would cause me to fail emissions test. Here in WA they only check readiness codes.

I haven't seen that code come up but then again I'm running a flash. Do you have the stock header and exhaust? If not I've seen several threads theorizing the the extra airflow throws the sensor out of the expected range. At least the Softronic flash broadens the error band or corrects it so that with non-stock cats, headers and exhaust you don't get the dreaded CEL come up.

Hi there. Can you check for me? I do not have a CEL, just the code. I have SRP 4.1, and stock headers. I wonder if I broke one of my O2 sensors when I was reinstalling headers.

Hello, This is only stating that the O2 sensors have not passed ready status yet and nothing more. To pass them certain conditions have to be met or a short test has to be run. Many cars can run many hours of op and not pass all the ready status. The things to look for are secondary environmental faults or CEL. Best, Scott

Thanks Scott. I posted here as your answer is likely to educate hundreds after me and save others time. Car runs smooth and great with your SRP.

I have checked. Read it out after installing the Capristo and the SRP 4.1 flash last winter and then driving for a while in the spring. What I meant by I hadn't seen that code come up. Same thing for SRP and 2.0 flash with stock exhaust back in 2008.

Sure , no problem and a good point Thanks, Scott

Just came across this exact situation this evening when looking through the Durametric DME module... started worrying about my upcoming emissions test now that I've installed my SpeedArt, SRP, and Flash. Decided to do a search on here and surprised to find exactly what I was seeing with a response from Scott. Thanks. I assume this won't impact my upcoming emissions test since I'm not throwing a CEL. I installed all of this stuff myself and am really going through the Paranoia stage right now, second guessing my work. I also installed a HIP CEC when I did the SRP and am hearing noises I never noticed before...most notably a ticking sound coming from the engine. Not sure if it just started or I just notice it now that the engine cover has been replaced. Hate to take it somewhere, but maybe I need to get someone else to verify that I didn't screw anything up. :crazy:

Mine has not gone away. Will flash to stock to see if I can get a more meaningfull code that would identify the sensor that is having the issue.

I have a similar story with my 2006 Boxster S . I run NHP catless headers (among other things) and have the FVD flash. The flash has been programmed for the lack of cats on the headers, as I requested FVD to do so when I purchased said flash. I do not have a CEL at present, nor have I ever with this combination of modifications. On the other hand, when I ask my ScanGauge II to scan for CEL codes, it indicates that my status is "Not Ready." The ScanGauge II is not sophisticated enough to indicate what precisely is "Not Ready," however. This is the case even some three months after installing the headers and flashing the DME . I do not recall having the "Not Ready" status before the flash, but my memory on this is less than perfect. The car runs flawlessly. I haven't scanned for codes in a few weeks, so on my way home from campus I will do so and check back in.

Interesting, I recently installed fabspeed catless headers and have SRP so never seen the CEL. I will try and check my codes in the next day or two to see if I'm having the same status. From what I'm gathering emissions issues arise only from fault codes/ CEL and not readiness status?

OK, this is not an error code, but an OBD2 readiness code. So do not scan for error codes, but go to the readiness screen. Its a basic, standard, every OBD2 car can be scanned for it. It means little without a Porsche code telling me what is wrong - which I do not have - but I wonder if I do not see the error as Softronic is hiding it - I do not know. Car also runs well. Having said that, I am 99% sure I will not pass emissions in WA and many other states that look to OBD2 for answers. So eventually I will need a new car or chase this down. My first step in troubleshooting is to install stock software and see what happens.

I see what you mean, CEL is an auto failure of the test, but in regards to readiness codes this article seemed to have some good info: What Actually Happens During An OBDII Emissions Inspection Specifically the 7th paragraph down: "If a car is inspected while it is not ready, the car will return ‘not ready’ to the inspection computer. On cars sold between 1996 and 2000 an emissions test is considered a fail if any 2 of the emissions systems return not ready. On later vehicles, you are only allowed one not ready."

Check your state's emission requirements....I found this on Illinois' site. "Remember, vehicles are rejected when more than two non-continuous readiness monitors are “not ready” for 1996 to 2000 model year vehicles, or when more than one non-continuous readiness monitor is “not ready” for 2001 and newer model year vehicles . Additionally, the catalyst monitor must be “ready” at the time of any re-test after a vehicle failed an initial test for any catalyst code." Which seems consistent with Blitz's post. Here is the link to the Illinois regs... Air Team - Illinois Vehicle Emission Test Program Since we only have one non-continuous readiness monitor "not ready" or failing, we would be okay (atleast in Illinois).

Nice! Now I may never get around to finding out why this readiness code never resets.

consistent for WA as well. Readiness Status

Great there are a Few of use looking forward to this answer! I have the same issue, one off.

I understand what you wrote Tomasz, as you were clear from the start. Because what I wrote in my prior post may not be clear, I will try again. In order to check the readiness state of OBD II via ScanGauge II, the SG II manual indicates that one must scan for codes. This action results in a concomitant check that all readiness " … tests have been completed since the last reset." Because I received the "Not Ready" display, " … the vehicle hasn't completed some test cycles." Unfortunately, SG II does not indicate which test cycles are incomplete. As promised, I ran the tests again today, and "Not Ready" is still displayed. Because the State of Florida does not perform emissions tests, I am not all that concerned, but I may still give FVD a call and ask if they have had feedback on their flash regarding this matter. I might feel differently if I lived in a state where rigorous emissions testing was in force.

Somewhere, someplace, I've seen what it takes to set the readiness code. Sorry, I don't recall where. It's pretty complicated. You have to go through this complicated driving sequence, starting from a cold start, without deviation. Deviate just a little and you have to start over (from a cold start again). Because of that, you'd have to do it on a deserted road someplace (e.g. park your car there overnight), just in case traffic interfered with your process. This is NOT the sequence, but it was described something like this: 1) Start from a cold start 2) Idle from 30 to 60 seconds 3) Accelerate to 20MPH, never exceeding 3,000 RPM 4) Maintain 20 MPH for 2 minutes 5) Accelerate to 40 MPH, never exceeding 4,000 RPM 5) Maintain 40 MPH for 10 minutes etc, etc. It goes on and on. Some states can issue a waiver if your readiness codes are not set. You can't go to your neighborhood smog check station, you have to go to a special one. They check that all your emissions are fine, you complain that setting the codes is near impossible (they know that), and they issue a waiver.

Maybe I missed it but I haven't seen you post an actual "P" code yet. If you have a "P" code, for example typical O2 sensor problem codes are P00130 and P0134 which are pre cat codes and P0136, P0138 are post cat codes. Once you have these you can start narrowing down the problem as it may not be the sensors are bad but something else causing the sensors to read the fuel air mix incorrectly. My pre cat codes came on recently and it turned out I had a hole in the Oil/Air seperator bellows and a broken line from a pre oxygen pump diaphragm. The problem with O2 sensor codes is because they're on doesn't mean they are the problem. There is a "tree" of tests that have to be performed on the entire intake/exhaust system to determine the issue.:cheers:

No, there is no P code. Just a readiness "Not Ready". My is NEVER ready, most cars eventually become "READY". I do not know what does this insinuate.

I do not think that would work. I have durametric that shows NO codes. I assume PS2 would do the same. Remember I have catless headers and softronic. So one of these is either causing or masking the issue or both. I am thinking of taking the car back to stock to troubleshoot then...

Hello, Before we over react or make it into something it is not, Porsche has had problems with it and took several revs to correct. The code status has been an issue even with the PIWIS tester . What does this mean? Nothing as it does not affect you in anyway.... The cars do not require all the ready status to pass OBD2 port emissions and affects the car in no way. Best, Scott

Once I realized that I decided to leave it alone and do not worry.

Update: I took my car in for the Illinois emissions test last week. The car had no CELs, but had one readiness test that had not yet cleared. The car passed the test just fine. My car has a SpeedArt Export exhaust, SRP, and Softronic Flash.