12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHNumber of Ignitions, range 1 - range 2
Leading reported evidence
Check 3 996 c2s
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've checked 3 996 C2s that all had over 60k miles and several track events for over revs with the durometric.
Leading evidence: 'Check 3 996 c2s' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check 3 996 c2s' (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 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've inspected several 996s (and 1 GT3) with my Durametric...
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 may be accelerating hard enough in 1st to use momentum to add *some* range 2s.
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.
12 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: 20261026T155324Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Can someone give a difinative answer on this?
I'm looking at a car. I had the Porsche dealer run the codes today.
It came back with 6,217 Range 1 ignitions last range one was at 720.8 hours
0 range 2 ignitions
Total engine hours are 724.7
Does this mean the car has be started 6,217 times or that the rev limiter has been hit 6,217 times?
Thanks!
Neither...it means there have been 6217 ignitions while at the rpm limit for type 1's (like 6750 depending on the car and the ECU). The last one was about four operating hours ago. recognize that @6750rpm = ~112.5rps and there are 3 ignitions per rev (6cylinders/3)...so it hit the rev limiter for all of about 18 seconds....
Range 2 is the dangerous range - it's good it's 0
Range 1 is lightly over the limit. 6,217 is the number of sparks over the red line I believe, divide by 6. Somewhere on Renntech is a formula to figure it out. Your Range 1 is a little high for the hours you have listed.
Right - the "ignitions" are the # of spark firings. 3x for every crankshaft revolution (all 6 for 2 revolutions). At 7,500 RPM, you can rack up those type 1 ignitions pretty quickly!
That # is perfectly acceptable.
Right - type one are ignition cycles when the rev limiter is engaged to limit a further RPM increase. Type 2 are ignition cycles where the redline has been exceeded due to mechanical factors (like a missed shift on the track - from 4th, you upshift into 3rd instead of 5th).
Type 2s can cause the internal components to be subjected to excessive stress.
I've checked 3 996 C2s that all had over 60k miles and several track events for over revs with the durometric. All had many thousands of range 1 and no range 2. With my previous C2, I tried running to redline, holding it there for a few seconds, as well as wheel spin to redline, none of these added any range 2s. The discussion on 6speed is centered around the twin turbos, which is not the car in question here. They may be accelerating hard enough in 1st to use momentum to add *some* range 2s. A few range 2s wouldn't scare me from a car either, a bad over rev would add more than a handful, and going a few hundred rpm above redline once is not going to break anything either...
I've inspected several 996s (and 1 GT3) with my Durametric... and I've seen some cars with both type 1s and type 2, I've seen cars, like mine, with type 1s, but zero type 2s, and I've seen cars with LOTS of type 1s.
I've hit the rev limiter on the track several times, but never missed a shift (and never spun the wheels at redline) - and yet, have not logged a type 2...
Reviving this old post on revving (get it) because of something I learned on a Flat6 video. My Durametric showed 2 range 2 ignitions. From the formula above that equals 0.006 seconds. Made no sense. Flat6 video demonstrating Durametic said a number like mine it just a ghost in the machine.
