Planet-9

Timing chain stretch - How to definitively diagnose?

Add to repair workspace

New repair projectOpen repair workspace

Original source

1 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis

THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHTiming chain stretch - How to definitively diagnose?

Leading reported evidence

Check timing by popping off the green plugs etc

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 have not yet physically checked the timing by popping off the green plugs etc but I plan on doing this in the
Original post Read captured discussion
Timing chain stretch - How to definitively diagnose?

Read full discussion summary

Leading evidence: 'Check timing by popping off the green plugs etc' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check timing by popping off the green plugs etc' (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 · 1 captured posts examined · 1 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.

Check timing by popping off the green plugs etc

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 have not yet physically checked the timing by popping off the green plugs etc but I plan on doing this in the
Original post Read captured discussion
Timing chain stretch - How to definitively diagnose?

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.

1 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

Planet-9: 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: 20261027T051247Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1Original post

2006, Boxster S 3.2L, 140k miles. So, I have been told by the dealer that the cause of my misfire codes, mostly on bank 2 on decel and also my bank 1 cam deviation (as read on my iCarsoft POR2.0 unit, does not throw code or CEL) is "possibly" due to timing chain stretch. Is there a way to diagnose whether they are or not before I go and drop the engine and do this? I have not yet physically checked the timing by popping off the green plugs etc but I plan on doing this in the next couple of weeks. Thanks, Julian

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