View Poll Results: Do you have the HCH 62 Mile bug ???
My HCH has the 62 Mile Bug.
19
44.19%
My HCH doesn't have it.
16
37.21%
I don't own an HCH 2006
8
18.60%
Voters: 43. You may not vote on this poll
The 62 Mile bug (100 Km)
#3
Re: The 62 Mile bug (100 Km)
Originally Posted by kenny
Would posting VINs also be useful?
I've just been watching too much Fox and CNN... is there a privacy or fraud issue ?
#4
Re: The 62 Mile bug (100 Km)
Are you only asking about HCH2, or also polling those of us with HCH1? My HCH1 does not, but from lurking around this forum it sounds like some HCH1's do have it... So would you like me to answer >No, or would you like me to answer >Don't have a 2006 HCH ?
#5
Re: The 62 Mile bug (100 Km)
There is. Only post the last six digits - that gives everyone the build number, and keeps the rest of the info (somewhat) secure - after all, I can reconstruct a HCH-2 VIN just shy of the check digit, just based on what I know about the models / option (w/ or w/o navi). For the check digit, there are tools available that would give me that, as well.
For those who post - cars for the Canadian market will have the first digit as an '8' - ie; 8xxxxx USDM models will have leading zeros up until the build sequence # - mine is '008661', for example.
If someone were to know your real name, and where you lived, they could acquire a new key, and your car could be stolen. Those are hypotheticals, but it could happen. That's why you often see people block out their license plates when they post pictures of them on the web. Google is a powerful tool - and the bad guys know how to use it, too.
There have been people who have had their cars stolen in the past, simply from people copying the visible VIN from the windshield. Supposedly, dealers have become more diligent about actually verifying that the person requesting the new key is actually the rightful owner. But why tempt fate ?
I've had a car stolen (not this way). It's not fun.
BTW - my car #8661 does *not* have the bug. Someone posted their vehicle #12xxx did seem to have it, but I'm guessing their display change was legitimate, from the way they described it, and they don't really have it (or at least, haven't definitively determined it yet).
The really valid check is at the multiples - 124mi, 186mi, 248mi, 310mi, 372mi, 434mi, 496mi
If you see a drastic change - not a tenth, but several integers worth of difference at one or more of those intervals - you've got the bug. It takes a lot to move the averaging display as you get farther and farther into a tank (assuming you haven't reset it since the tank started).
BTW - I thought 100km was 63mi, not 62 ? However, if you look at the display at 62, you're going to notice soon after if it does have the bug, so not a big issue.
For those who post - cars for the Canadian market will have the first digit as an '8' - ie; 8xxxxx USDM models will have leading zeros up until the build sequence # - mine is '008661', for example.
If someone were to know your real name, and where you lived, they could acquire a new key, and your car could be stolen. Those are hypotheticals, but it could happen. That's why you often see people block out their license plates when they post pictures of them on the web. Google is a powerful tool - and the bad guys know how to use it, too.
There have been people who have had their cars stolen in the past, simply from people copying the visible VIN from the windshield. Supposedly, dealers have become more diligent about actually verifying that the person requesting the new key is actually the rightful owner. But why tempt fate ?
I've had a car stolen (not this way). It's not fun.
BTW - my car #8661 does *not* have the bug. Someone posted their vehicle #12xxx did seem to have it, but I'm guessing their display change was legitimate, from the way they described it, and they don't really have it (or at least, haven't definitively determined it yet).
The really valid check is at the multiples - 124mi, 186mi, 248mi, 310mi, 372mi, 434mi, 496mi
If you see a drastic change - not a tenth, but several integers worth of difference at one or more of those intervals - you've got the bug. It takes a lot to move the averaging display as you get farther and farther into a tank (assuming you haven't reset it since the tank started).
BTW - I thought 100km was 63mi, not 62 ? However, if you look at the display at 62, you're going to notice soon after if it does have the bug, so not a big issue.
Last edited by GreenAndBlue; 03-30-2006 at 05:56 PM. Reason: Clarify US vs. CDN build numbers
#6
Re: The 62 Mile bug (100 Km)
Originally Posted by Adelwyn
Are you only asking about HCH2, or also polling those of us with HCH1? My HCH1 does not, but from lurking around this forum it sounds like some HCH1's do have it... So would you like me to answer >No, or would you like me to answer >Don't have a 2006 HCH ?
I am sorry I didn't know there was an issue with the HCH-I, maybe someone else can start a separate survey. Thanks.
Last edited by Katz6768; 03-30-2006 at 03:29 PM.
#7
Re: The 62 Mile bug (100 Km)
Originally Posted by GreenAndBlue
There is. Only post the last six digits - that gives everyone the build number, and keeps the rest of the info (somewhat) secure ...
Originally Posted by GreenAndBlue
BTW - I thought 100km was 63mi, not 62 ? However, if you look at the display at 62, you're going to notice soon after if it does have the bug, so not a big issue.
100 Km = 62.1371 miles.
#8
Re: The 62 Mile bug (100 Km)
My car has the bug but it doesn't happen all the time. It seems that it only occurs or is noticable when I am in city driving or in stop and go traffic. On the highway I never notice it. My build # is 000384.
#10
Re: The 62 Mile bug (100 Km)
Originally Posted by Adam_HybridCivic
My car has the bug but it doesn't happen all the time. It seems that it only occurs or is noticable when I am in city driving or in stop and go traffic. On the highway I never notice it. My build # is 000384.