16 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHow to read overrev report?
Reported or suspected cause
error blip more than anything else
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
I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
Leading evidence: 'error blip more than anything else' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'error blip more than anything else' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace like opening a window' (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
I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
Reset service lights was one reason, the other being able
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
I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
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
When I saw the zeros for ranges 2-6 I wondered if I ran the test wrong.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Replace like opening a window
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
I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
Reset service lights was one reason, the other being able
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
I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
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.
16 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 · 2 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T072535Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi, I got a
DME
overrev report for my new
Cayman S
and am struggling to learn how to read it. I was wondering if anyone had any resources, or could help me understand this?
Number of ignitions, range 1 (h)
51594, 1507.8
h
Number of ignitions, range 2 (h)
3585, 1481.7
h
Number of ignitions, range 3 (h)
630, 1387.7
h
Number of ignitions, range 4 (h)
118, 1197.0
h
Number of ignitions, range 5 (h)
6, 1036.4
h
Number of ignitions, range 6 (h)
0, 0.0
h
For reference:
Operating hours: 1512.5
Miles: 44014
Do you think it was tracked much?
Ah okay, based on this, I see that the left value is the total number of ignitions over time, and the right value is the "hour index" for when it happened. Meaning e.g. it was overreved in range 1 recently, but hasn't reached range 4-5 in the last ~300 hours.
How to read over rev report? - 6SpeedOnline - Porsche Forum and Luxury Car Resource
997 Turbo / GT2 - How to read over rev report? - Can any one explain how to read the report and what is in the range of acceptable. Thanks
www.6speedonline.com
What is the rpm range for each range on a 2006 Cayman S?
Range 1 - 7200-7500 (7300 - 7500 for
911
)
Range 2 - 7500-7700
Range 3 - 7700-7900
Range 4 - 7900-8400
Range 5 - 8400-9500
Range 6 - 9500 and up. This occurs when the engine is mechanically overreved by shifting into a lower gear and mechanically exceeding the rev-limiter.
http://www.durametric.com/troubleshooting-Porsche-9x7.aspx
Okay I guess I eventually found everything I needed on my own lol.
Number of ignitions / 3 = number of engine revolutions
Number of revolutions / by rev limiter = minutes spent at limiter
Minutes spent at limiter x 60 = seconds spent at limiter.
Porsche rev range activity | engine over revs explained by 911virgin
Understanding Porsche rev range activity. A detailed guide from Porsche specialist dealer 911virgin based in Uxbridge, West London
911virgin.com
So, number of seconds spent in each range:
Range 1 (s)
140.39
Range 2 (s)
9.43
Range 3 (s)
1.62
Range 4 (s)
0.29
Range 5 (s)
0.01
Range 6 (s)
0.00
A previous owner must have missed a gear and caught it within 2 seconds.
Generally, range 4 or higher is where you start worrying. However, the overrevs in this range were both a long time ago and limited in time, so I'd say there's not much risk of issues from this report.
For reference, I had some range 6 on my car, but they were 800 hours prior, so people said to not worry about it. My car has been running great for 3 years now... knock on wood!
I bought a
ThinkDiag
for my new (to me) 2009
Cayman S
. I plan on doing most of the maintenance myself, so resetting service lights was one reason, the other being able to code changes like opening a window when I open the rear hatch.
Anyway, I ran the
DME
Over Rev report and like most, am not sure what I'm seeing and would like some confirmation. It appears to be a very good report. Almost to the point that I wonder if I did something wrong. I haven't figured out how to export yet, so here's some screenshots. What say you?
Overrev report is easy to read. Basically, you only have 263 ignitions in range 1, and the last one happened at 2838h of the engine life. There is a value somewhere else that tells you what the current time (age) is... and you use that to compare with the above time to know how long ago that was, approximately.
If you had higher ranges, there would be more to dive into, but range 1 is basically when you just approach or bounce off the rev limiter. In other words, it's not a big deal to have those, so don't worry about them. The rest of yours are 0, so it's never gone past that.
Is this a manual trans car? If so, it wasn't "money-shifted" ever (ie, downshifted with too much speed for the gear). A
PDK
may show numbers like this as well, since it will never allow a "money shift".
In the end, nothing to worry about here.
Thanks for taking a look and replying. When I saw the zeros for ranges 2-6 I wondered if I ran the test wrong.
The car is a 6MT and I've only had it for about a month. In that short time I have not "money-shifted ". Good to know in its 15 year life it doesn't appear to have been abused (at least by overreving).
When I bought my car, it had like 61 ignitions in range 6. But they were over 800 hours before I saw the car, and it ran great and the PPI showed it was great as well. So, just because you have higher items doesn't NECESSARILY mean that the car is toast. It only takes one money-shift to do that, after all.
My car now has another 30k miles on it, and is still running great. No oil consumption either.
IMO the only reason the overrev report would be a problem is if you sell the car. Honestly, this is my favorite car EVER. I have NO desire to sell it, so I don't care what my overrev shows, nor have I bothered with
PPF
... I plan to keep this car forever!
Hello Everyone, New here. Looking to purchase an '05 987
Boxster S
. Had a PPI done, and got the
DME
report. Pretty excited but having some doubts reading the report. Any help would be appreciated!
Range 1 3669 1050.7
Range 2 108 1014.1
Range 3 1 48.3
Range 4 1 48.3
Range 5 1 48.3
Range 6 1 48.3
Operating Hours 1101.00
Looks like it had one big zing for a fraction of a second. That is # of ignitions....so divide by 3 for rotations. 15 rotations at over redline. A non issue.
Or is that 1 ignition at hour 48.3???
Thanks.. yea. Looks like it read 1 Ignition at hour 48.3 on all ranges above 3, which is weird... should that not be progressive? the Range 1 and 2 seems about 50+ hours prior...
Agreed, 1 ignition at 48.3h... probably an error blip more than anything else.
My car had real values at range 6 when I bought it, and it has been running great for the past few years without issue... I wouldn't worry about it.
This is a source reference. Confirm exact model applicability in the original material.