25 not 24

[Agent777]

I'm trying to enter the speed limit on a street @ 25mph thru mapshare. The tomtom (GO 730) keeps showing 24. I have tried changing it to 30 and back to 25 and it still shows 24. I have set speed limits on other streets in the hood at 25 and they have all worked. Any suggestions? Oh, I have tried the pin reset. Thanks.

 

[dhn]

I'm trying to enter the speed limit on a street @ 25mph thru mapshare. The tomtom (GO 730) keeps showing 24. I have tried changing it to 30 and back to 25 and it still shows 24. I have set speed limits on other streets in the hood at 25 and they have all worked. Any suggestions? Oh, I have tried the pin reset. Thanks.

Others have noted this too. Suspicion is the firmware converts the speed entered to metric and back again for some reason and the conversion algorythm isn't quite correct.

You'll notice the problem with some other speeds too.

 

[johnling]

I'm trying to enter the speed limit on a street @ 25mph thru mapshare. The tomtom (GO 730) keeps showing 24. I have tried changing it to 30 and back to 25 and it still shows 24. I have set speed limits on other streets in the hood at 25 and they have all worked. Any suggestions? Oh, I have tried the pin reset. Thanks.

This is intentional behavior. When the unit is set to "warn if speeding" it will alert you at 29 MPH with the ?bong? just before you hit 30 MPH. Less than 5 MPH deviations in speed are supposed to be allowed by law enforcement.

 

[Michael Quinlan]

This is intentional behavior. When the unit is set to "warn if speeding" it will alert you at 29 MPH with the “bong” just before you hit 30 MPH. Less than 5 MPH deviations in speed are supposed to be allowed by law enforcement.

So you're saying that TomTom's speeding alert is triggered at 5 MPH over the speed limit, and instead of changing that to 4 MPH they are intentionally storing incorrect speed limit data that is 1 MPH less than the actual limit? I've heard of TomTom doing some crazy things, but incorrectly storing millions of numbers instead of changing just one??

 

[Ricochet]

This is intentional behavior. When the unit is set to "warn if speeding" it will alert you at 29 MPH with the ?bong? just before you hit 30 MPH. Less than 5 MPH deviations in speed are supposed to be allowed by law enforcement.

That's ludicrous!

The observed reductions aren't consistent across all speeds: entered values of 25, 30, & 45 mph, all drop by 1 to: 24, 29, & 44 mph, whereas, 55 mph stays 55 mph. Additionally, every pre-loaded roadspeed I've encountered has been spot on with the actual posted limits & never reduced by one.

As for the 'warn if speeding' feature, my ONE 3rd "allows" me 3-4 mph of leeway above the road's set speed before it turns Red & starts chanting, "Slowdown!" (or whatever wave I've chosen).

So, if the displayed road speed is "29" it turns red at approx. "33/29" or higher. If the speed is 55, it turns at "58/55." If I slow down to "32" or "57" in the above examples, the display ceases to be red & the warnings stop. I observe this 3+ mph behavior during my daily commute and while making deliveries through residential areas. My cruise-control habits depend on it.


dhn's "metric re-conversion" theory is much more plausible.

R?

 

[nicholb]

If it was a metric conversion I don't see how it is happening. For Example:

35mph = 56.33kph

If you round that to 56 and convert back you get 34.80 mph which rounds to 35mph. They could be truncating instead of rounding which would result in 34, but we should also see a problem with 55mph.

55mph = 88.51kph
88 kph = 54.68 mph = 54 mph if we truncate both the kph and mph results.
89kph = 55.30 mph = 55mph if we round.

So rounding should make both numbers correct, and truncating the fraction should make both incorrect. There must be some other reason the lower speed limits are off by 1 mph.