THe Bug:
At multiples of 63 miles the trip meters zero themselves - sort of.
(It just starts averaging from a new point, but the miles-driven-since- zeroing-trip meter read-out does not actually go to zero.)
Hypothetical example:
So, lets say you are doing great for the first 62 miles and get 55 MPG.
Then you park the car for the night, with 62 miles on the Trip meter.
The next morning (cold) you get into the car and drive off.
At first you MPG reads 55 MPG at 62 miles.
About a mile later it plumets to 20 or so.
What happened is it "zeroed" at 63 miles, so it is averaging since mile 63 not since mile zero.
It is reported to do this at multiples of 63 too, 126, 189 etc.
This is my unerstanding of what I have read.
Here is what I have seen in MY car so far:
Since learning of the problem I zeroed Trip meter A yesterday.
This morning in the middle of my commute I hit the 63 mile mark.
(My MPG was 57 MPG at 62 miles.)
At 63 miles my MPG jumped up to 60 - which makes sense considering the bug since I was going 50
MPH with a warmed up engine on a flat road.
Then the MPG jumped up and down a lot with every slight incline. (Much moreso than it would have if it was really averaging together 66 or so miles.)
When I got to work 10 miles later my TRIP A MPG meter read 67 MPG - Certainly too good to be true (unless I had zeroed the trip meter after the engine was warmed up on the freeway). (Which is exactly what the faulty gauge is doing - except it does not actually zero the "miles driven" portion - it just begins averaging from a new starting point.
This is hard to describe, and I am not 100% sure I even understand it yet.
Make sense?