GreyGoose
Well-known member
I thought i better update this thread with something i just heard from garmin (after a nice long 60 minute holding period) and got the following information (note: note sure if its valid or not):
Through many of our discussions, we realized that routes can get altered during the transfer from mapsource to your garmin. Some devices seem to be more prone to this than others. I started doing a deep dive into this when i got my zumo 660 and saw that one of the firmware upgrades included the following text:
"Corrected to allowed routes to be imported from matching maps on MapSource without recalculation"
I was considering upgrading the firmware until i heard of an issue that causes the device to shutdown. So i wanted one of the updates, but didnt want the bug to come with it. so i kept wondering what prompted this bug fix. Here is what i found out:
When transferring custom routes into your zumo (or other device) with firmware 3.50, if you have any preferences enabled (i.e. avoid highways, u turns, etc), the device will recalculate your route during the transfer. if you were to then disable those preferences before using the route, you will probably end out with something very different than what you intended. Thats the bug that was fixed in 3.80. The 3.80 firmware will now take your route as its shown in mapsource and download it into the device "as is" no matter what preferences you have set. The preferences can then be put into action when the route is loaded. So those of us that want to wait on upgrading our firmware from 3.50 to 3.80 because of the shutdown issue but were concerned about the import issue, should turn off all preferences before transfering the custom route from mapsource into the device. The preferences can still be applied to the route after their enabled, but the route will come into the device without change. I would use this procedure for all garmin products before transferring to the device.
Thats the story i'm getting from garmin and i'm told to take what there support says with a boulder of salt. IF anyone see's anything different, let us know. I aint upgrading untill that shutdown issue is resolved.
GreyGoose
Through many of our discussions, we realized that routes can get altered during the transfer from mapsource to your garmin. Some devices seem to be more prone to this than others. I started doing a deep dive into this when i got my zumo 660 and saw that one of the firmware upgrades included the following text:
"Corrected to allowed routes to be imported from matching maps on MapSource without recalculation"
I was considering upgrading the firmware until i heard of an issue that causes the device to shutdown. So i wanted one of the updates, but didnt want the bug to come with it. so i kept wondering what prompted this bug fix. Here is what i found out:
When transferring custom routes into your zumo (or other device) with firmware 3.50, if you have any preferences enabled (i.e. avoid highways, u turns, etc), the device will recalculate your route during the transfer. if you were to then disable those preferences before using the route, you will probably end out with something very different than what you intended. Thats the bug that was fixed in 3.80. The 3.80 firmware will now take your route as its shown in mapsource and download it into the device "as is" no matter what preferences you have set. The preferences can then be put into action when the route is loaded. So those of us that want to wait on upgrading our firmware from 3.50 to 3.80 because of the shutdown issue but were concerned about the import issue, should turn off all preferences before transfering the custom route from mapsource into the device. The preferences can still be applied to the route after their enabled, but the route will come into the device without change. I would use this procedure for all garmin products before transferring to the device.
Thats the story i'm getting from garmin and i'm told to take what there support says with a boulder of salt. IF anyone see's anything different, let us know. I aint upgrading untill that shutdown issue is resolved.
GreyGoose
Last edited by a moderator: