17 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHRange 2 Overrev's
Leading reported evidence
Check wow
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.
Leading evidence: 'Check wow' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check wow' (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
When an engine is replaced whatever data stored in the DME remains.
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
When my DME in my 1997 Boxster was replaced 3 years ago the DME started with zero engine operating hours, and zero range X revs.
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
Could it also be that the engine was replaced due to the overrev's but since the ECU was not it still holds the codes?
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 guys must have missed a downshift or spun out the car and ran in reverse with the engine running forward, I guess.
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.
17 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: 20261026T163944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I had a PPI done on a car (2003 C4S), and it was reported that it had 282 "range 2" overrevs. It has 66K miles on it.
Does that seem like a lot? From what I understand, that means that the spark plugs fired 282 times when the engine was overrev'd, probably from a missed shift. The place that did the PPI said that if the valves were damaged, that there would have been other signs that they would have noticed.
I'm sure that the PPI advisor is correct, but I just wanted to get a second opinion.
Thanks for your help.
P.S. I did search on the topic, but I couldn't get the forum to search for "range 2" together instead of posts with range or 2 that might be separated.
You need to ask how long ago was the last range 2. It is expressed in terms of engine operating hours since the last incident, versus current engine operating hours.
Could it also be that the engine was replaced due to the overrev's but since the ECU was not it still holds the codes? If so, then maybe it is not an issue? Just a thought...
David
As I understand it, range 2 overrevs are directly related to a single revolution. That is, one revolution would result in 6 stage 2 overrevs. So, based on this, 282 stage 2 revs would be about 47 revolutions of the engine. Assuming redline is at 7500, thre are around 125 revolutions per second. Thus 282 stage 2 revs is about 1/3 of a second in that overrev range.
Some P-tech guru correct this if it is way off, so we don't promulgate wacky info.
-td
When an engine is replaced whatever data stored in the DME remains. The DME is not replaced or zeroed out due to an engine replacement.
The opposite is also true. When my DME in my 1997 Boxster was replaced 3 years ago the DME started with zero engine operating hours, and zero range X revs.
The sheet says:
Number of ignitions, range 1
3658 1588.0h
Number of ignitions, range 2
282 1587.8h
Operating hours counter
1590.0
So, range 1 seems fairly low for a car with 66K (but I am only comparing that to examples that I could find on the internet).
Thanks again for the advice.
I found this on another forum:
Number of ignitions, range 1-RPM Range 7,300-7,500
Number of ignitions, range 2-RPM Range 7,500-7,700
Number of ignitions, range 3-RPM Range 7,700-7,900
Number of ignitions, range 4-RPM Range 7,900-8,400 (Some damage)
Number of ignitions, range 5-RPM Range 8,400-9,500 (Damage)
Number of ignitions, range 6-RPM Range 9,500-11,000 (Damage)
-td
I decided to not worry about the overrev's. I spoke with two Porsche mechanics (not associated with the dealer) and both of them said they wouldn't worry about it. The car is not from a Porsche dealer.
So, thank you again.
Unless something else comes up, I should soon be the new owner of a 2003 C4S. I'll post pics as soon as I get it.
This is a source reference. Confirm exact model applicability in the original material.
