Rennlist

Finding and Conquering the Dreaded SAI Leaks P0491/P0492

Add to repair workspace

New repair projectOpen repair workspace

Original source

2 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis

THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHFinding and Conquering the Dreaded SAI Leaks P0491/P0492

Leading reported evidence

Use old, small, very basic code reader first)

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
I will connect my Durametric next (I used my old, small, very basic code reader first).
Original post Read captured discussion
Finding and Conquering the Dreaded SAI Leaks P0491/P0492

Read full discussion summary

Leading evidence: 'Use old, small, very basic code reader first)' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Use old, small, very basic code reader first)' (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.

Read captured replies

1 matching discussions · 2 captured posts examined · 0 partial discussions

Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Use old, small, very basic code reader first)

No successful repair reported for this finding.

0
Reported fixes: 0
Unsuccessful attempts: 1
Discussions

Read evidence and context

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
I will connect my Durametric next (I used my old, small, very basic code reader first).
Original post Read captured discussion
Finding and Conquering the Dreaded SAI Leaks P0491/P0492

Coverage and how to read this overview

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.

2 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: 20261026T105141Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

Happy Saturday all, I'm back with another video. This time I'm getting secondary air injection leak errors, P0491 or P0492, in my rebuilt 4.0 996 Cabriolet. Thanks to the advice and guidance I got from Rennlist, I was able to deal with this nagging issue and will show you how easy it is to diagnose it yourself. Enjoy! You Tube

POST 2Original post

Good stuff. My GT3 just threw the P0491 code, so this is a nice "maybe here's the problem" video. I will connect my Durametric next (I used my old, small, very basic code reader first).

This is a source reference. Confirm exact model applicability in the original material.