10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHList of Porsche OBD 2 Codes
Reported or suspected cause
still there
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause · Original poster
He replaced the MAF sensor(thank god I didn't have to pay for it) and the problem was still there.
Leading evidence: 'still there' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'still there' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Repair job - ouch' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
He replaced the MAF sensor(thank god I didn't have to pay for it) and the problem was still there.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
If you had both P1128 and P1130 I would also suspect the MAF or oil separator.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
10 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T075545Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My CEL light came on the other day. I have an OBD 2 scanner which allows me to read out the codes and reset the CEL. The OBD2 scanner is a PC based unit from
www.obd-2.com
. The problem is that the code it is reading out this time is not one of the standard codes pointing to one of the sensors. It is listed as a manufacturers proprietary code. It reads out a code number but where can I get a list of porsche specific codes and what they mean?
The code I'm getting is PI130ND. It takes several days after resetting to come on again. Sometimes it does go off by itself after being on for several days. Any ideas would be appreciated.
The year of your car would be helpful since 996's have had 3 different DMEs (DME 5.2.2, DME 7.2 and DME 7.8). The code fault analysis varies somewhat depending on the DME version.
DME 7.2 - Boxster (986), S MY01-02; Carrera (996) 4, 4S MY99-01; Carrera (996) MY00-01
P1130 - Oxygen Sensing Adaptation, Idle Range, Bank 2 � Above Limit
Air leaks ahead of the oxygen sensors can lead to a fault in adaptation.
Bank two (Cylinders 4 - 6) is the passenger side of the engine.
Any changes to the air intake lately?
Could be an air leak in the intake, or exhaust.
If you had both P1128 and P1130 I would also suspect the MAF or oil separator.
Thanks for the tips, I checked my service manuals last night and I do indeed have a DME 7.2 system in my C4. I believe I had this same code for the left side of the engine a few years ago when it was under warranty. The technician said it could be a induction leak or a MAF sensor. He replaced the MAF sensor(thank god I didn't have to pay for it) and the problem was still there. They eventually found the leak to be a cracked hose. I'm glad it isn't a camshaft timing actuator. I had one of those go bad last summer. That was a $2000 repair job - ouch.
I'll have to take a close look at the induction system. Couldn't it also be a bad oxygen sensor?
Thanks,
Greg Wroclawski
MY 99 C4
GreggT,
You mentioned that "member-subscribers to renntech.org have access to the code lists (along with TSBs, etc)". Can you tell me where/how to access them?
Thanks.
Thanks for the list.
@Cups Rennlist - Renntech.org is a great resource for technical information and it's well worth becoming a contributing member. I just renewed my membership.
This is a source reference. Confirm exact model applicability in the original material.
