Incorrect Average Speed Limit Warnings on TT 1000 Live

BenM · Occasional Visitor Joined: May 05, 2006 Posts: 8

Has anyone else experienced an issue with the TomTom supplied Average Speed Limit Warnings? I am using a Tomtom 1000 Live with NC 11.041 and yesterday I drove through 6 sets of average speed limits, two on the north eastern part of the M25 and 4 going up the M1. At each one my TomTom would show the correct reduced speed limit of 50 mph in a red circle at the bottom left of the screen, but only for about 2 seconds. It would then flick to 70 despite still being in the 50 mph speed limit zone. This is irratating and confusing as you then don't receive a warning if you stray over 50 mph.

Any feedback will be much appreciated as it will provide ammo for me when I report it to TomTom.

Thanks

HenryMitchell · Posted: Mon Mar 12, 2012 10:48 pm Post subject:

I get the same thing on the M25 J27-J30 section...
_________________
Device: GO 600, Live connected via iPhone 5.
App: 13.030.1412491.111 (0) (2042, 31/10/2013)
OS: 1392579
Map: Europe v920.5244 (11/2013)

Andy_P · Posted: Tue Mar 13, 2012 11:34 am Post subject:

BenM... can you check your Navcore version? Did you mean v11.031?

I THINK what is happening here is that the "Camera speed limit" indicator roundel on the TomTom is working like it does for a normal fixed camera... i.e. it appears for a few seconds before the camera and then disappears.

And then it is going back to the normal "road speed limit" indication.

You can tell the difference because the "Camera speed" is shown in a slightly larger roundel.

So if the road speed is still set (in the map data) to 70, then the reduced speed limit is only getting shown while you are near a camera.

Sounds like a bug, I'll get it reported (if no-one else has already).
_________________
"Settling in nicely" ;-)

BenM · Occasional Visitor Joined: May 05, 2006 Posts: 8

Thank you both for your replies.

Andy_P that sounds exactly right, I seem to remember it would temporarily flick back to showing 50 when nearing the average speed cameras. Unfortunately I won't be in a position to test this for a while.

I will confirm the version of my firmware but I will reporting this to TomTom myself. The more the merrier....

HenryMitchell · Posted: Wed Mar 14, 2012 12:44 am Post subject:

M8TJT · Posted: Wed Mar 14, 2012 9:23 am Post subject:

My guess at the cause of this this would be, in the case where it is wrong, they have not changed the underlying road speed limit data to the new lower speed limit. In the case of where it is right, they have done this. It will probably be right when the authorities have installed some specs to enforce an existing speed limit, such as 30MPH where TT had it right before the specs installation.

HenryMitchell · Posted: Wed Mar 14, 2012 9:36 am Post subject:

I've just been through the M25 J30-J28 roadworks this morning as usual and paid careful attention to what it did.

This zone is a 70mph motorway but with a temporary 50mph limit for the duration of the roadworks. The speed limit is shown in the bottom left section of the screen as 70mph all the way through the zone.

As I approach the first camera the large roundel appears showing the 50mph limit and the overspeed warnings correspond to that limit. It stays like this all the way through the zone until a few hundred metres before the last camera when the roundel changes to show 70mph, then I got a warning that I was reaching the last camera, and then all the warnings disappeared as expected as I passed it.

A similar thing happens when going through the same zone in the opposite direction but the incorrect 70mph roundel appears at least twice (I'll check later).
_________________
Device: GO 600, Live connected via iPhone 5.
App: 13.030.1412491.111 (0) (2042, 31/10/2013)
OS: 1392579
Map: Europe v920.5244 (11/2013)

BenM · Occasional Visitor Joined: May 05, 2006 Posts: 8

I STILL haven't had a chance to confirm the version of the navcore on my TT but I posted this issue on the official TomTom 1000 forum and somebody has replied saying that TT are aware of the problem and it will be resolved in the next firmware release.

	PocketGPS
	Web