Help with DME report
#2
Rennlist Member
630 total hours is low - I'm assuming low mileage car?
1 Over-Rev in Range # 4 & 1 in Range #5 no big deal since it happened 149 hours agoColor 92U the best Arctic Silver
How did the PPI go?
1 Over-Rev in Range # 4 & 1 in Range #5 no big deal since it happened 149 hours agoColor 92U the best Arctic Silver
How did the PPI go?
The following users liked this post:
FlatsixS (08-26-2023)
The following users liked this post:
grgallo (08-28-2023)
#4
RL Community Team
Rennlist Member
Rennlist Member
Average mph is about 35 which is normal if not a bit low - points to more around town driving than highway use.
You're good to go from a DME perspective.
#5
Rennlist Member
Not quite. There was an overev event at 149.5 hours but the car has 630 hours on it now so that actually happened 480 hours ago. You can also ignore the single overrevs - they're software glitches...so it was a range 2 or maybe kissed range 3 but it was so long ago it doesn't matter.
Average mph is about 35 which is normal if not a bit low - points to more around town driving than highway use.
You're good to go from a DME perspective.
Average mph is about 35 which is normal if not a bit low - points to more around town driving than highway use.
You're good to go from a DME perspective.
#6
Track Day
Thread Starter
Petza, I know the owner, old guy, never tracked never redlined, could all this be just a software glitch like you say?
He states he never redlined the car or even went over 6k.
Sure would be nice to see when it comes out of the factory what the DME says right away.
He states he never redlined the car or even went over 6k.
Sure would be nice to see when it comes out of the factory what the DME says right away.
#7
RL Community Team
Rennlist Member
Rennlist Member
Trending Topics
#8
RL Community Team
Rennlist Member
Rennlist Member
With 123 in range 1 and 10 in range 2, that's a legitimate overev event that went through range one kind of slowly and touched into range 2 for just a bit.
Last edited by Petza914; 08-26-2023 at 03:28 PM.
#11
Rennlist Member
It has also been explained changing a battery on rare occasion cause the over rev blip. Is this correct?
#14
RL Community Team
Rennlist Member
Rennlist Member
Do I think this engine may have an issue from what's logged here - No, I don't because the Range 3s and 4s were so long ago.
#15
This engine has been driven fairly hard or regularly on a track. It has seen at least 4 separate overrev events - one at 1,148 hours (range 4), one at 2,091 hours (range 3), one at 2,415 hours (range 2), and most recently at 2,430 hours (Range 1). The total hours on the engine is 2,461 so the last overrev event was only 31 hours ago, but it was also only a Range 1, which isn't concerning and there was a range 2 46 hours ago which is why I say this engine was fairly regularly bumped up against the rev limiter because between the Range 1, 2, and 3 overrevs, there's a total of about 1,900 of them. The way the DME log works is it only captures the hour reading of the most recent one in that range, but to get to 1,900 counts there are multiple instances logged. You can ignore the Range 5s and 6s with a single overrev in each (not possible). Is 1,900 a ton of them - no, there are DMEs of track cars where the counter is maxed out (happens around 15,000 or something like that), but it was spun up more often than I do my own cars. The potential risk is was the engine fully warmed up when these occurred, was the owner keeping up with oil changes so the engine was well-protected during these higher RPM events - that's the stuff only they know.
Do I think this engine may have an issue from what's logged here - No, I don't because the Range 3s and 4s were so long ago.
Do I think this engine may have an issue from what's logged here - No, I don't because the Range 3s and 4s were so long ago.