14 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHOver Rev Report Question
Leading reported evidence
Clean report
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.
Leading evidence: 'Clean report' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Clean report' (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
Setting aside the constant tire and brake changes they change the oil once in the middle of the season.
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
Setting aside the constant tire and brake changes they change the oil once in the middle of the season.
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
On my test drive the salesman said to not worry about running the car up to redline since, and I am paraphrasing: " These cars are made to be run hard, so drive it like you stole it.".
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
On my test drive the salesman said to not worry about running the car up to redline since, and I am paraphrasing: " These cars are made to be run hard, so drive it like you stole it.".
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
On my test drive the salesman said to not worry about running the car up to redline since, and I am paraphrasing: " These cars are made to be run hard, so drive it like you stole it.".
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
On my test drive the salesman said to not worry about running the car up to redline since, and I am paraphrasing: " These cars are made to be run hard, so drive it like you stole it.".
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.
14 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 · 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: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Possibly getting close to pulling the trigger on a new 2010
Cayman S
. The dealer "punched" the warranty last week and is offering me a decent deal at14.5% discount from MSRP. The car has 953 miles on the odometer from test drives and use at a couple of local events (per Sales Manager). Due to the mileage, I requested a
DME
Over-Rev report which the dealer povided within 2 hours of my request (impressive). Can you guys help me interpret the results?
Nmax stored for range 1
34 28.28h
Nmax stored for ranges 2 thru range 6
0 0.00h
Operating hours counter (h)
35.86h
Throttle pot 1 voltage at lower stop
0.5
Throttle pot 2 voltage at lower stop
4.4
Throttle setpoint angle from throttle adap.
4.8
Thanks in advance.
That isn't an over-rev report. An over-rev report will list some rpm ranges over the red line, and a number of ignitions (hopefully) zero in each rpm range.
The report in your post does tell you that the average speed the car was driven while running was less than 30mph.
Looks clean to me. Range 1 isn't a big deal, the real trouble is when you get to Range 5 or 6
See the FAQ:
Planet-9 - FAQ: Cayman Technical Data-OverRev
I interpret it as showing 34 ignitions in Range 1 and none in 2-6 - that's hardly ever going near the redline. Seems like the previous owner barely even enjoyed the car . . .
i have problems interpretting the report. so even though the report showed that there is no ignitions from 2-6 range, but 3428 ignitions in range 1. so accordin to that faq, that car has just bumped into the red line but has not been over revved. does that mean i can assume that the car has been driven above 4k rpms and was not safely broken into during the break in period?
Well, it's really showing 34 ignitions, which occurred in the 28th hour of engine operation. The engine has run for 36 hours so far. An occasional trip to redline won't have much of an effect on break-in.
On my test drive the salesman said to not worry about running the car up to redline since, and I am paraphrasing: " These cars are made to be run hard, so drive it like you stole it.". I thought cool beans and proceeded to flog it. Since then I have come to learn there is indeed a break-in period of staying below 4200rpm for the first 2000 miles. Has anyone else run into this mindset? He gave me the keys and said to be back in a couple of hours.
Different people will have different opinions on 'break in'
Obviously a 'virgin' car that hasn't gone over 4k rpm since leaving the factory would be ideal.
I don't think you really *need* too much, but allowing some form of 'wear in' period is nice. I've heard that revving the engine without putting a heavy load on it is a 'good thing' or at least easier on the engine - but I wouldn't swear to that being accurate.
Most car salesmen I've seen are happy to drive the cars hard - is it just because they want to move them? I don't think people are likely to do much of any damage during a test drive.
A different opinion...
I just don't see that this is the report you want - how many times has it hit the rev limiter? 34 times in first gear? Is that what that means? I wonder what a Durametric code reader would pull?
Seems to me that they are trying to sell it right before 1000 miles. But this might also mean perhaps 95 test drives at 10 miles each. So it could be 95 or more times out with former or potential
Porsche
owners trying to see what is has and how it sounds opened up. I know when I test drove a
Porsche
I did things I wouldn't do with mine until it was properly broken in.
That is exactly why I didn't buy a demo model, but ordered mine. I know exactly how it was driven and broken in from the first mile.
I think another dealer might give a discount if he knows you are serious and are about to buy somewhere else. So why not try and get some discount but go for a 2011 instead - wouldn't you come out ahead?
When I took the
Porsche
Driving school 4 years ago (barber) I asked the lead instructor what they did. He said they get their new cars at the first of the year and begin running them hard right out of the box for about 210 days a year. Setting aside the constant tire and brake changes they change the oil once in the middle of the season. The cars are sold as
Porsche
certified at the end of the year. That's how I remember it anyway.
I visited the factory in Stuttgart , in 2003, all engines are red lined for several minutes before , either being shipped or installed in the car. That's SOP.
Cheers
I vote with those above who think the report means 34 ignitions (rather than "hits", miles, or whatever) in Range 1. I think this was very likely due to only one very brief touch into Range 1. Probably shouldn't even count as a red line hit. Thus, I would not be the least bit concerned about the ignitions over red-line.
Unfortunately, these reports don't show how many times the engine experienced deep throttle acceleration before completely warmed-up.
I would be more concerned with lugging the engine vs hitting redline. However, I have bought demo cars in the past with no ill effects. If you like it and the price is right and is what is needed to get into a
Cayman
then go for it.
This is a source reference. Confirm exact model applicability in the original material.