"Excessive" over-revs
#16
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
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.
#17
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
Sounds like he needed to get rid of the car quick. Perhaps before the accident report get's logged by CarFax. Cudos for doing your research and knowing when to walk. You'll find a better car.
#18
Racer
Thread Starter
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
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.