Route millage goes mad when I send route to Zumo

[dave hendy]

I am using a Zumo 550 with city naigator 2010.1 and mapsource 6.15.6 I have done 26 routes for a trip in just over a week. My Zumo is on version 4.70. I started to transver them last night only to find the first route of 299 miles on mapsource goes to over 1200 miles on the Zumo. I have since loaded 9 more routes and 4 more have done a similar thing The routes look fine on the PC with millages and times what I would expect so I don't know what is going wrong? I am transvering the routes 1 at a time. Has anyone got any sugestions?

Dave

 

[peterh]

I have the same issue, same versions of s/w. I have reported it to Garmin who have passed to the US for investigation with two sample files as evidence. Callender to Ullapool, either 229 miles (Mapsource) or 2299 miles (Zumo).

This does not always happen but I have found a fix for those times it does. Clunky, but it works. Send the file from Mapsource and import to the Zumo. Then send the same file back to Mapsource and recalculate, then send it back again to the Zumo and import. Voila!

 

[dave hendy]

I have the same issue, same versions of s/w. I have reported it to Garmin who have passed to the US for investigation with two sample files as evidence. Callender to Ullapool, either 229 miles (Mapsource) or 2299 miles (Zumo).

This does not always happen but I have found a fix for those times it does. Clunky, but it works. Send the file from Mapsource and import to the Zumo. Then send the same file back to Mapsource and recalculate, then send it back again to the Zumo and import. Voila!

Sorry you have the problem as well, but glad it's not just me! Let me know if you get any reply from Garmin and I will try what you sugest. Just tried what you said it actually made it worse?

 

[peterh]

Had a quick look at the Zumo Forum and found a relevant post. Have a look here
http://www.zumoforums.com/index.php?topic=9377.0

Can't remember if you need to register first, but in case you need to but do not want to, here is something that might help:

In that case it's almost certain that the problem routes were built with 6.15.3 - what you describe was a major bug in that version and you'll find discussion of it under 'Bugbusters'.

Find one of the routes that is giving problems, delete from the Zumo and then re-calculate that route in the current Mapsource and re-import it to the Zumo - you'll probably find that it's now fine.

 

[dave hendy]

Sorry you have the problem as well, but glad it's not just me! Let me know if you get any reply from Garmin and I will try what you sugest. Just tried what you said it actually made it worse?

Forgot to say when I recalculated on the PC as it was worse I didn't bother to resend it, should I have? Or should it have been OK when mapsourse recalculated it?

I have just recalculated a couple of the effected routes and re-sent them to the Zumo and these seem to be OK. I will try the others tomorrow!

 

[peterh]

In my case (yours may be different) importing a barking mad file from the Zumo (which was originally a sane file created in Mapsource) and recalculating in Mapsource cleared the problem. Once more I had a sane file which I sent back to the Zumo and once more I imported it, this time getting a sensible answer on the Zumo.

It doesn't make any sense, but for me, it worked.

 

[dave hendy]

All the faulty routes have now been recalculated and sent to the Zumo OK I am now re-doing the routes that seemed to go last night to be on the save side I am always amazed how quickly you get help on these forums, many thanks