15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH'Check engine drive to workshop'
Reported or suspected cause
exhaust oxygen sensor (lambda)
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
I've had the same issue, and it turned out to be an exhaust oxygen sensor (lambda).
Leading evidence: 'exhaust oxygen sensor (lambda)' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'exhaust oxygen sensor (lambda)' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check engine' (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 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
Probably the coil pack, especially with the systems you describe and the wet weather.
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
Personally, I would take it literally and drive to a workshop to check the engine.
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.
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
They reset the warning all free of charge, and told me not to be concerned about it.
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.
15 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: 20261027T031046Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
The car felt lumpy at tickover yesterday and this morning. When I parked it the above warning came up.
Can anyone explain what it means as the words engine and drive in the same sentence are making me nervous. :?
Could be a number of things, faulty MAF, Lambda sensors, split coil pack... All with through a CEL. Get a diagnostic reader plugged in and read the fault code...
:thumb:
Presume Cayman and Boxster warnings point to the same issues?
So a trip to OPC then.
It started the morning I turned it over at 0300am when the temp was 6d/g. Never felt it rocking on tickover. Felt better when warmed up as it did yesterday after 15 mile drive. But still slightly rough on tickover today and that's when I noticed the orange warning.
Only feed it Shell red top to doubt it's fuel issues.
I've had the same issue, and it turned out to be an exhaust oxygen sensor (lambda). The MAF would really affect performance across the range, and a faulty coil pack would make for rough rev's through the range too.
They're about £100, but a pig to fit, as they're an alloy thread going into steel exhaust, and the threads strip really easily.
Just spoke to OPC Byfleet and the guy reckons they have had 10 or so similar issues this week so we will plug her in at 4 o'clock and see what happens. He thinks it's the coil, which in his view, is / are located in a vulnerable situation. (Once they have it plugged in I think it may be me in the vulnerable situation .......)
Thanks for the help
Find out which one has gone, and change it yourself 4WD - not a hard job, just need to jack the back end up a bit and be a bit patient.
They're less than £25 each from GSF carparts.
I had the same message appear on the dash just this Friday lunchtime. I was driving on the B30 near Ulm in Germany when it appeared.
I mmediately drove to the nearest Porsche Garage and they plugged in the computer.
It turns out that in the last year there have been 4 cases of the Lambda sensors giving readings that were out of the normal range. They reset the warning all free of charge, and told me not to be concerned about it.
