5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault code query?
Leading reported evidence
Clean )
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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
* Incorrect signal from MAF sensor(MAF may be knackered/needing cleaned)
Leading evidence: 'Clean )' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check " light bursts into life' (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 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.
Suggestion · Original poster
Minding my own business on Wednesday in traffic when suddenly the "engine check" light bursts into life.
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.
Suggestion · Original poster
Thanks for the tip - will check the cap immediately.
Check obvious ones(air leak at cap and maf seals first)
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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.
Suggestion
Check the obvious ones(air leak at cap and MAF seals first)
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.
Suggestion
* Leak from the intake air system leaking (check the seal at the MAF also)
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.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261027T150039Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all,
Minding my own business on Wednesday in traffic when suddenly the "engine check" light bursts into life. No real change in the cars behaviour so I carefully drove to my destination (about 40 miles). The car felt right and no odd misfires, loss of power or juddering, nothing nasty at all.
Got Porsche Assist to check and they reported code P1130. They had cleared the fault and reset the light and all was well and the light hadn't come back on. So I head home, a 150 mile trip. All fine until about 10 miles from home and I got a "blip" in power and the "engine check" light flashed briefly at me (for less than a second). Felt like a momentary block in fuel, that sort of power blip.
Any ideas what this might be and can anyone tell me what the fault code P1130 relates to?
Many thanks
According to OPC that error code suggests that the car is running lean.
Most likely causes are an o2 sensor is playing up or your MAF needs looking at. However as odd as it sounds you should check that your oil filler cap is properly screwed on. apparently this is quite a common cause of the CEL coming on as it allows too much air in.
P1130 Is the Oxygen Sensing Adaptation(bank 2 I think)
Are you seeing P1128 also by chance?
P1130....hmmm could/will be one or more of the following:
* Incorrect signal from MAF sensor(MAF may be knackered/needing cleaned)
* Blocked/fouled injector(s) (possible)
* Leak from the intake air system leaking (check the seal at the MAF also)
* Low fuel pressure(unlikely) but older some 996's have faulty pumps
* A leak in the exhaust system somewhere (possible but rather unlikely unless it's been messed with recently)
Check the obvious ones(air leak at cap and MAF seals first)
If it was an air leak or MAF it would affect both banks, and as has been said, you would expect to see both P1128 and P1130 fault codes.
Check the voltage output of the oxygen sensor on bank 2. It should fluctuate rapidly between 0.04 and 0.79 volts. If it is sluggish, or out of range, it's the O2 sensor that's the problem.
This is a source reference. Confirm exact model applicability in the original material.
