What is the 62 mile bug? - Page 2 - GreenHybrid

Sledge · #11 (**permalink**) 04-04-2006, 11:27 AM

Quote:

Originally Posted by Tim

Don't know how much this has to do with it, but computers think/speak in binary - 1's and 0's. You can count from 0 to 63 using 6 bits, that is 000000 thru 111111. To get 64, you need a seventh bit (1000000). Often times when computers do goofy things related to math, it happens on the factors of 2 (1, 2, 4, 8, 16, 32, 64...). If the computer - due to a programming error - is only reading the first 6 bits of the mileage data, it would go 0 - 63 then recycle. It could be some other combination as I'm not sure how they'd handle the decimal.

If this is true then the HCH2 is suffering from the same type of problem as the Y2K bug

I do NOT want a car programmed in COBOL!

zadscmc · #12 (**permalink**) 04-04-2006, 11:53 AM

Shift to the LEFT
Shift to the RIGHT
UPSI 1
UPSI 2
BYTE, BYTE, BYTE

toast64 · #13 (**permalink**) 04-04-2006, 04:11 PM

Well, I believe I finally have conclusive evidence that it is indeed a 100 km bug....

Today on the way home from work I was at about 175 miles on trip A (62 x 3 = 186).

So, I switched my display to read in metric (km and l/100km - rather strange watching the instantaneous meter read the other way!). Switching to metric made it easy to see what would happen at exactly 300.0 km.

I watched the l/100km gauge for 11 miles. It didn't move much, which is to be expected. The entire way home it stayed right at 4.9 l/100km, only occasionally dipping to 4.8.

I knew that if it was a 100 km bug, and if I accelerated hard at 300.0 km, I would minimize the time it took for the gauge to register after reset and hopefully catch it in the act.

At 298.5 km I pulled into a medium sized parking lot. I cruised the lot until the gauge read 300.0 km, and I stopped. Still read 4.9 l/km, as it had pretty much the entire 11 miles previous.

I then accelerated hard for .3 km, letting up only long enough to make the turns.

The gauge hesitated at 4.9 l/100km for roughly .1 km (I assume while the reset was taking place and gas/km were accumulating to something that would register), then climbed from 4.9 to 5.2 to 5.5 l/100km while I traveled from 300.1 to 300.3 km.

I think this nails it. It is a 100km bug, or a 62.13712 mile bug if you prefer.

Anyone see any flaws in the test?

ElanC · #14 (**permalink**) 04-04-2006, 05:24 PM

I called my nearest Honda dealership's service department today and scheduled an appointment for Friday. I told them I had a problem with the gauge cluster as described in Product Update 06-013 (thanks to whoever posted that info here). The service consultant said, yes, it says you need a software update. No problem. We'll take care of it for you.

I'll report back on Friday, or as soon as I get a chance to verify that it's fixed.