25 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHI?m guessing these are good numbers. What do you think
Leading reported evidence
Use valet parking only
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
so i guess the OP used the valet parking only once
I?m guessing these are good numbers. What do you think
Read full discussion summary
Leading evidence: 'Use valet parking only' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Run ) since your last range 1 ignition detection' (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
Another way to put it - it has been 88.7 engine operating hours (engine is running,) since your last Range 1 ignition detection.
I?m guessing these are good numbers. What do you think
Use durametric
Suggestion or failed attempt
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 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 · Original poster
There is a video posted recently that someone provided when I asked about using a Durametric.
I?m guessing these are good numbers. What do you think
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.
25 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: 20261027T044418Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
They look good. The max deviation between both banks should be no more than 6 degrees (though I think FSI/Jake Raby says any more than 4 degrees should be concerning)�
There is a video posted recently that someone provided when I asked about using a Durametric. Search Durametric on here. I�d post but I�m not that technologically savvy.
The first number is the # of ignitions in that range, and the second number is the operating hour at which that Range 1 ignition was detected
So it reads:
(Ignition in RPM Range #1 Count)
2,530
/ (Occurred at)
2531.2
hours
You have a total of 2619.9 hrs of runtime on the car or operating hours.
On range 1: you�ve had 2,530 overrevs interrupted by the ECU. The last one happened at the 2531 hour mark.
😉
And I'll add, yes, you have 1 ignition in Range 2 which everyone says is a "no no", but I'll repeat more-or-less what my mechanic told me when he was looking at my sheet; it happened more than 2000 hours ago so don't worry about it!
That�s what I thought but it just seems way to high. I hardly ever get over 5k. I wish I had kept the reading from when I bought it. Something seems out of whack. Is there any other way to trip it?
Thanks for responding.
Range 1s are high on most 996 but not so much on range 2., but its so long ago I wouldn�t worry about� if it damaged the car you�d know about it. Probably either a missed downshift or someone punching it in first gear and not shifting quick enough to 2nd.
[Image-only post; no author-written text. Original image references:]
https://cimg5.ibsrv.net/gimg/rennlist.com-vbulletin/1129x781/over_revs_e1606212261995_f8d4ebad30c4be459191d57ecf42636bf72df649.jpg
Someone correct my math if I'm wrong!
At 7400RPM, that's 123RPS
With a 4-stroke motor, that would equal 30.75 ignitions per cylinder in that 1 second.
6 cylinders would mean 184.5 ignitions per second.
So 2530 range 1 ignitions would equal 13.7 seconds of rev limit(or more) over the 2619.9 hours of driving.
I'm no math wizard, so someone tell me if I have it correct.
Car has just under 77k.
im not saying it�s bad, I�m just trying to get what it means.
2530/2531.2
One means last time it happened, what�s the other number?
If your all wondering, I am able to hold a job.😀
the 1st # 2530 = number of events, there r 6 events per revolution.
The 2nd # 2531.2h = the period of time the last event happend based on your total amount of hours on the car
the issue u have is the numbers are similar but this is a coinsedence
Another way to put it - it has been 88.7 engine operating hours (engine is running,) since your last Range 1 ignition detection.
The last time your car detected a Range 1 was at 2,531.2 hours of operation and your car currently has 2,619.9 hours of operation logged on the computer.
So to clarify what Tex is saying - if you were to hypothetically go out and redline your car right now for 1 second, your updated Range 1 count should look like this:
Number of Ignitions in Range 1: 2715 /
2619.9
Operating Hours Counter: 2619.9
This is because in 1 second you will add about 185 ignitions in Range 1 but you will not add any appreciable engine operating time for the ECU to add to your tally, so it will simply update itself to reflect the current operating time. i.e. "This just happened"
This is a source reference. Confirm exact model applicability in the original material.
