Yes the cats CAN produce this code......

I never did with mine but I have heard about it in the past and it was a simple fix.They made an o2 extension....hang tight and I will try and find it!
Northvan997S knows what I am trying to say.
I think it has something to do with the fact that the exhaust is flowing by so fast(free'r flowing) that the o2 has a hard time getting its reading.....

Gone to find a link....be right back!

Stacy

 

OK I found it.....I am not saying that this is the problem forsure but if it is....easy/cheap fix...

http://shop.fvd.de/us/en/Porsche-0/9...Extension.html

Stacy

PS Worked for NORTHVAN997S

 

Will a PIWIS (or equivalent) diagnose a code - down to the specific O2 sensor - if that is the issue? I've given Alex (Sharkie) a buzz (PM) and may try to head down to his place.
And yes, it is frustrating. I'm willing to accept that it was 'pilot error' (well, installer error) and a test, a little bolt tightening and a reset will fix it. If so, mea culpa and lesson learned. Surely there are enough variables here (headers, gaskets, cat and muffler couplings, O2 sensors wire rerouting and install, new cats) that there could easily be some error along the paths. I only wish the CEL was not so general. A hint would be useful.
But if not, well...

 

Stacy,
Thank you. I've seen these advertised before, and I hope I don't need them. Was told the unit would work as-is. As I just noted, I'm willing to accept that the likely issue is 'installer error'. Would you happen to know if the car will pass emission with these things installed? I presume that the O2 sensors serve a useful purpose of participating in the feedback loop to keep the mixture adjusted properly.
Thanks again.

 

I doubt that this could be the issue, but because the plumbing of the x-pipe is different than the standard cats, I was wondering if could have mixed the order of the O2 sensors. That is, I've plumbed the sensors with the blue wire (on both sides) to be just after the headers, before the cat. And the sensor(s) with the black wire to be after the cats.
I assume that if I got this wrong, the CEL would have fired immediately on startup but it's worth checking. Also, the wire lead lengths of the sensors likely not permit getting these crossed. But I guess it's worth a check.
Would anyone be willing to go out to their car and take a look?
Also, would a leak - either at the header/cats or cats/mufflers cause a CEL? The car sounds a little 'breathy', especially when cold, but I felt around (as much as I could with the engine running) and couldn't detect anything. Anyone have a technique for sussing out a leak?

BTW, I assume the car is still drive-able? No risk?

 

It would be better to know what the code is. When you "stretched the O2 wires, how much did you stretch them. The wiires are as important as the sensor itself as it is through the wire that the sensor breaths.

 

You're probably right. I did try to take care to ensure that the connectors on both ends remained intact, and made sure the thermal sheath over the wire near the sensor was fastened properly.
I guess I'll let it sit, until someone can look at it. Dang.

 

After going over ever little piece yesterday and having the evening to mull, I took out my fine tooth comb this morning and found the issue.
Seems like the (EVOMS CAI) airbox had just barely come free at the hose/throttle body connector. No doubt my error when I replaced the airbox, having removed it to get to the O2 sensor wires.
So I buttoned it up and disconnected the -ive (!) battery cable to reset the CEL (thank you Alex - I didn't know that was possible) andit all seems to be working. No beeps, lights, or 'take car to workshop'. Of course, on CEL-happy cars like ours, I won't be fully convinced for days. But this was clearly causal, which is very good news.
I'd want to thank Stacy, 1999Porsche911, utkinpol, Alex (Fabspeed) who called me to help out, Alex (Sharkworks) for being so helpful. It's great to know that I'm not alone when testing my limited skills.
V

 

Makes sense - it was MAF sensor related CEL then.

Still it would be convenient if you could find somebody nearby, some shop or tuning guy who can read those codes.
I bet it should be somebody with durametric cable close to you in the Bay area. It is much better to know what car was talking about.

BTW, what about those OBD2 readers at autozone stores - can they read Porsche CEL codes?

 

Yes, I'm going to go get something to make all this clearer 'next time'. The Durametric seems like the best, but pricey. There are the standard, cryptic but inexpensive ones at the local auto parts store, and then there's the Rev iPhone application (needs an ODB port to wi-fi sender).
Any recommendations out there?

 

There's a Durametric posted locally on craigslist that you may want to check out: http://sfbay.craigslist.org/pen/pts/1389105325.html

Andre

 

Thank you Andre. I jumped on it as soon as I saw your note. But it's now listed as 'sold' and I haven't heard from the seller.

 

Verde, I googled it for a minute and ordered from here:

http://www.obd2tech.com//33-porsche-...c-scanner.html

I called that guy and essentially it is a durametric cable, at least software you get is durametric. Should do the trick I guess. He told me that if it will not work or I will not like it he will allow to return it but so far everybody who got it liked it and it works fine. Your car seems to be covered there as well if you still have 2005.

 

Yes, I saw that one. Decided it was in the 'too good to be true' category and ended up ordering a Durametric enthusiast last night. The price was not much less than the pre-owned one.
On the one you ordered, keep me posted. I wonder if Durametric knows about it? Could it be a hacked security version of a copy of their stuff?

 

Will let you know. Cable may either work or not work, there is no 3rd option there.