8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHEmission sensor
Reported or suspected cause
lambda sensor has gone bad
Suggestion or failed attempt
No successful repair reported for this finding.
0
Identified cause
1
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 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
Most likely a lambda sensor has gone bad, but you need to get a diagnostic check done to see which one, or if it is something else.
Leading evidence: 'lambda sensor has gone bad' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'lambda sensor has gone bad' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check done' (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
Most likely a lambda sensor has gone bad, but you need to get a diagnostic check done to see which one, or if it is something else.
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
Can you recommend a reasonably priced kit for diag on the 996 TT.
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
Would just like someting that would tell me any fault codes, maybe help with getting the air out of the system after changing a rad etc.
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
On a Turbo, any cheapie handheld OBD2 code reader/scanner will read engine fault codes and reset a cheeck engine light.
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.
8 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: 20261026T222516Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all.
Does anyone know the cause of an emission warning light that came on yesterday while I was out cruising, and if so, do you know how to fix it.
Thanks in anticipation.
Dave the gas.
Hi Richard
Can you recommend a reasonably priced kit for diag on the 996 TT. Would just like someting that would tell me any fault codes, maybe help with getting the air out of the system after changing a rad etc. I am used to doing my own maintainence but the 996 seems to need one to be able to check if any probs exist.
Hi Eddie
On a Turbo, any cheapie handheld OBD2 code reader/scanner will read engine fault codes and reset a cheeck engine light. It won't read any of the other control modules on the car though. For that, you would need a Durametric scanner, or a Porsche tester. The Durametric is by far and away the best DIY tool designed specifically for Porsches. The latest version 6 of the tester will even do some basic coding, and has the facility for brake bleeding on the 9x6 cars.
Bleeding a Turbo cooling system can only be done with a Porsche tester at the moment, but Durametric are continuously adding facilities to the new system, so I expect that they will be introducing it fairly soon. Their suppost is very good, so if you are interested in one, try contacting them to see if/when they have it planned. You can buy the system from them direct at www.durametric.com or from the UK distributor at http://www.hickleys.com . By the time you have added import duty and VAT there isn't much difference than buying direct.
I have no affilliation with Durametric. I have one of the older Professional models which works very well, and I keep in the car.
