How to read over rev report?
#31
Burning Brakes
Let me explain....too many nice cars are missed because of these reports.
This report is Porsche's way to not warranty issues. Blame it on the over rev report
This report is Porsche's way to not warranty issues. Blame it on the over rev report
#32
Track Day
thanks for the response! So that report looks reasonable for a 2007 997TT with 30k miles. Not driven too hard? tracked? the 12 over revs at 5 look like 400 hours ago. Trying to decide today :/
#33
Drifting
I don't see the total operating hours, but since they have to be at least 851, that means that last "bad" overrevs are at least 300 (range 4) and 400 (range 5) hours old. If the car runs fine and passes your PPI, you'll have nothing to worry about. (Except maybe for weenies hassling you at resale down the line - some people will automatically exclude any car with range 3+, regardless of how perfect and mechanically sound the vehicle is otherwise.)
#34
Track Day
I don't see the total operating hours, but since they have to be at least 851, that means that last "bad" overrevs are at least 300 (range 4) and 400 (range 5) hours old. If the car runs fine and passes your PPI, you'll have nothing to worry about. (Except maybe for weenies hassling you at resale down the line - some people will automatically exclude any car with range 3+, regardless of how perfect and mechanically sound the vehicle is otherwise.)
#37
Rennlist Member
A perfect report. It needs to be driven harder.
The following users liked this post:
Robocop305 (08-19-2021)
#39
Advanced
Hi, what is the protocol to read these values ?
Can this be read with OBD2 tool?
I have the Kiwi3 OBD2 tool, on which I can program code to read from the car.
I have regular OBD2 commands for now, but I would be interested on reading and writing more Porsche specific data.
Can this be read with OBD2 tool?
I have the Kiwi3 OBD2 tool, on which I can program code to read from the car.
I have regular OBD2 commands for now, but I would be interested on reading and writing more Porsche specific data.
There are 6 different messages, 1 for each rev range. The response is 2 bytes for the ignition count, and then 4 bytes for the time of last incident, (in tenths of seconds, divide by 36000 to get hours)...
I know this cos I just worked them out tonight on my 997.2 C2S!
BTW I have 717 ignitions in Range 1, nothing else, When I bought the car 2.5 years ago it only had 427. Naughty me.
#40
I dont know if I'm more impressed you pulled the byte codes and read the values yourself, or disappointed you did it in response to a 5+ year old question.
#41
Advanced
Heh. I am doing it cos I'm writing an OBD2 app. While writing this app via standard OBD2, I found that my Porsche 997.2 does not respond to Engine Oil Temp over the standard OBD PID.
So for kicks I am trying to work out some of the Porsche custom messages to see how viable that is as an option.
So for kicks I am trying to work out some of the Porsche custom messages to see how viable that is as an option.