5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault code help?
Leading reported evidence
Check " light bursts into life
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 · Original poster
Minding my own business on Wednesday in traffic when suddenly the "engine check" light bursts into life.
Leading evidence: 'Check " light bursts into life' (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
Get a diagnostic check done, and get them to read out the output voltage from the sensor.
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
If the sensor is reading correctly, check the fault areas listed above.
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.
Porsche Club GB: 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: 20261026T124918Z · 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
P1130
Oxygen Sensing Adaptation Area 2 (Cylinders 4 - 6) "" Rich Threshold
Fault conditions
Fuel/air mixture is so lean that sensing has
reached its rich threshold.
Fault area
"" Intake air system leaking.
"" Fuel pressure too low.
"" Volume supply of fuel pump too low.
"" Fuel injectors fouled.
Most likely you have a faulty lambda (oxygen) sensor on bank 2. Get a diagnostic check done, and get them to read out the output voltage from the sensor. The voltage should fluctuate rapidly between 0.04 and 0.79 volts. If the output is out of that range, or sluggish, then the sensor is faulty. If the sensor is reading correctly, check the fault areas listed above.
Hi Gizmo
P1130 - Oxygen Sensing Adaptation Area 2 (Cylinders 4 - 6) - Rich Threshold.
Which I think means your engine will run lean but I'm sure Richard will have more detail for you.
RB.
Thanks chaps - nothing too major then.
Seems that it would explain the momentary lack of power too if it is a fuel related issue.
Will pop it down to the OPC over the weekend and get them to plug it in.
This is a source reference. Confirm exact model applicability in the original material.
