"Excessive" over-revs
Three Wheelin'
Joined: Jun 2012
Posts: 1,587
Likes: 50
From: MN
Car 2 range 1 has maxed out the overrev counter at 65536 decimal. It's stored as a 16-bit number 0xffff in hex which is 65535 max. The +1 difference is an implementation issues. New range 1 overrevs get the hour logged but the counter no lomger increases. Bottom line the are many more range 1, overrevs than logged.
Range 1 is not necessarily bad, just be aware this car has spent a lot of time at the rev limiter, more than recorded.
Range 1 is not necessarily bad, just be aware this car has spent a lot of time at the rev limiter, more than recorded.
Thread Starter
Racer
Joined: Dec 2013
Posts: 463
Likes: 89
From: Atlanta
Originally Posted by semicycler
Car 2 range 1 has maxed out the overrev counter at 65536 decimal. It's stored as a 16-bit number 0xffff in hex which is 65535 max. The +1 difference is an implementation issues. New range 1 overrevs get the hour logged but the counter no lomger increases. Bottom line the are many more range 1, overrevs than logged.
Range 1 is not necessarily bad, just be aware this car has spent a lot of time at the rev limiter, more than recorded.
Range 1 is not necessarily bad, just be aware this car has spent a lot of time at the rev limiter, more than recorded.
This is kind of is a cross post back to my "2006 S aero in Charlotte area" car post. I won't even mention the 20+ error codes recorded on the durametric short test.
