8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHRange 2 - Thoughts
Reported or suspected cause
single missed shift
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.
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
The above with the preliminary cold start and idling as the engine warms up and as you listen for any scary noises has the engine running around an hour.
Leading evidence: 'single missed shift' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'single missed shift' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Run around an hour' (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
The above with the preliminary cold start and idling as the engine warms up and as you listen for any scary noises has the engine running around an hour.
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
My senior Porsche techs told me they like to see at least an hour's run time after the over rev event with the engine manifesting no untoward behavior.
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
Have you subjected the car to a test ride then test drive?
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
Have you subjected the car to a test ride then test drive?
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Run around an hour
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
The above with the preliminary cold start and idling as the engine warms up and as you listen for any scary noises has the engine running around an hour.
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
My senior Porsche techs told me they like to see at least an hour's run time after the over rev event with the engine manifesting no untoward behavior.
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.
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: 20261026T120458Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Seeking to own my first. DME says 2 ignitions in range 2 for this 2003 C2. 40Kmiles
It only reports on range 1 and 2.
What's the RPM to enter range 2.
Should I have any concerns?
Apologies to be asking what I assume is a previously covered topic,
Nav
My info:
996 Carrera
Range 1: > 7300 and < 7900
Range 2: > 7900
What is the total engine runtime and what are the time stamps for the last over rev events?
My senior Porsche techs told me they like to see at least an hour's run time after the over rev event with the engine manifesting no untoward behavior.
I'd add with the CEL dark, no pending DTCs, and all the readiness monitors set to complete.
Others like to see more time.
Have you subjected the car to a test ride then test drive? This has the seller driving the car over a 15 mile route that allows him to demo the car as you intend to use it then afterwards at the starting point you get behind the wheel and drive the car over the same route and drive the car the same way.
The above with the preliminary cold start and idling as the engine warms up and as you listen for any scary noises has the engine running around an hour.
Two instances of range 2 ignitions?
I'd hardly worry about that. Probably a single missed shift.
If the count was in the hundreds, it would be obvious flogging.
It's irrelevant then. I have 810 range 2 on my track car, 120 of which I was responsible for. Not a single issue from it. My range 1 are 65535 which is the max number it will report.
My DD on the other hand has 0 range 2 and minimal range 1.
Same here and agreed 2 R2s 1,000h ago isn't something I'd worry much about. Probably more risk in old peripherals like the water pump, chain tensioners, aos, coolant lines/tank, etc.
This is a source reference. Confirm exact model applicability in the original material.
