Zumo 660 - and now for my next conundrum!

Andy B

Well-known member
UKGSer Subscriber
Joined
Apr 6, 2006
Messages
2,573
Reaction score
55
Location
Lea & Perrins country
Transferring maps from Mapsource to Zumo.

Should be easy enough I hear you say! Never had a problem with this for years! However, something elementary is going wrong and I can't work it out!:augie

I'm running Mapsource 6.16.3 on my PC and update 4.10 on the Zumo. Every time I send a map to the Zumo I get a message when I boot up the Zumo afterwards saying that the route was calculated with different map and would I like to recalculate.

I've a vague recollection of this problem with my old 550 in the dim and distant past but it's got me stumped!:confused:

Help please!!:blast
 
Andy

I'm no wizard at this stuff, but I'll have a guess.

I suspect your map version installed on the zumo (likely 2011.10 or maybe the latest 2011.40?) is not the same as the map version you're using in mapsource to create the route in the first place. Thus, where you create in mapsource using one map version and then transfer to the Zumo which is using a different map version, the unit has to re-calculate the route.

Sound plausible?

If so, just make sure that the map version you're using in map source to create the route is the same as that installed on the unit.

Hope it helps.
 
I think you are right.

What is baffling me is that I've run the updates for both the unit and mapsource and it's telling me I'm all up to date. The unit is running City Navigator Europe NT 2011.40 and Mapsource City Navigator Europe NT 2010.1 ver. 13.10. If the Mapsource software is out of date why is it not prompting me or telling me I need to update and directing me to the update?!:confused:
 
I think you are right.

What is baffling me is that I've run the updates for both the unit and mapsource and it's telling me I'm all up to date. The unit is running City Navigator Europe NT 2011.40 and Mapsource City Navigator Europe NT 2010.1 ver. 13.10. If the Mapsource software is out of date why is it not prompting me or telling me I need to update and directing me to the update?!:confused:

I may be wrong, but this is my understanding...
When MapSource tells you that the software is up to date, it is referring to the "MapSource" software, not the version of the installed map.
For example, my current version of MapSource is 6.16.3 and the installed map it is using is City Navigator Europe NT 2011.4
The installed map on my Zumo is also City Navigator Europe NT 2011.4, which means that both the PC and the Zumo are using the same map.
When you download the updated map from Garmin, you have to have your GPS unit connected via USB for Garmin to authenticate the download. I think this is what you've done...
On one of the screens during the update process, there is a box in the bottom LH corner which you must click to specify that the new maps be installed in BOTH the GPS itself AND the PC... it's very easy to miss this step and, as default, it will only update your GPS and not your PC.
In your case, connect your GPS via USB and go and repeat the update process, but this time click on this box... you can then specify that the new maps be installed on your PC only... this will update MapSource with the new map.
Once you've done it a couple of times, you won't forget :blast
Good luck :D
 
It is possible to get the message even when the maps on the PC and 660 match.

I am running identical maps on both my 660 and my PC. If I summon up an old route on my PC it will open and display in the the new map.

If I then send the route to my 660, the device will tell me that the route was created in a different map set (or some similar message) and asks if I would like to recalculate?

If I say, yes,the device goes into a deep sulk, reverts to it's factory settings and wipes my Favourites. Garmin can replicate the fault but cannot fix it :blast
 
Bang on Ballistic!:thumb

I'd missed the option to update on both. I can see why too! Not very obvious is it?!

Thanks for your help - it's downloading again now.:D
 
It is possible to get the message even when the maps on the PC and 660 match.

I am running identical maps on both my 660 and my PC. If I summon up an old route on my PC it will open and display in the the new map.

If I then send the route to my 660, the device will tell me that the route was created in a different map set (or some similar message) and asks if I would like to recalculate?

If I say, yes,the device goes into a deep sulk, reverts to it's factory settings and wipes my Favourites. Garmin can replicate the fault but cannot fix it :blast

Fortunately, I've never had this happen :JB
To be absolutely certain of it never happening again, I imagine that the cure would be to recalculate any old routes in MapSource (using the same map as is installed in your GPS) before downloading them to the GPS... a bit of a pain eh? :(
 
Wapping - my reinstall has solved the problem but when loading old routes it comes up with the same problem as you've got.

I've solved it by saving the old routes with a new name and then sent them to the Zumo and the old routes are then okay.:thumb
 
I had this on my Nav III. If you open the old route in Mapsource with the new maps, then recalculate and then save the route, then send it back to the unit that seems to fix it.
 
This is an old thread, but having come across it looking for something else entirely I might add LOL, it might be worth just adding a few points for members to keep in mind.

There are currently 2 available Garmin applications for route planning - MapSource and Basecamp. MapSource has reached the end of it's development and will no longer be supported by Garmin although it is still available for download. BaseCamp is still under development and is still in need of some improvements in order for motorcyclists to ditch MapSource completely.

When updates to maps are download BaseCamp is also downloaded and installed by default. A lot of users are not aware of this fact as it doesn't install a desktop icon.

When planning routes it is essential to always create these with both the GPS and the application (MS or BC) using the same map versions.

Now to the crux of this post. MapSource and BaseCamp use different indexing systems as indeed do Google and other map providers. This is important if you created a route in one map version (say a couple of years ago) and now want to use it in the GPS that now has installed a later map version. Recalculating the route in the GPS might appear to work but in fact it doesn't and can lead you astray unexpectedly. Also, recalculating the route with MapSource doesn't work because it is not able to recalculate the indexes......it was never designed for this.

However, all is not lost and this is where BaseCamp comes in handy and is useful for this function even if you don't want to use it yet as a replacement to MapSource.
BaseCamp is able to recalculate an old route including the indexing and will reliably produce the same route that you spend hours creating. Here's the way:-
(a) Open your old route - gdb file - in BaseCamp.
(b) Double-click on the route in the left hand panel which will open the Properties page.
(c) With the Properties tab active at the bottom right hand side of the page you will see the Recalculate tab which you should activate. The route will now be recalculated with the correct indexing.
(d) Now close this page which will return you to the BaseCamp home page.
(e) With your route active either right-click and choose Export or go to File > Export. Give your file a name and from the drop-down box either choose the gpx or gdb formats. I personally choose the same name and the gdp format (same as original) and replace the original with this now updated and recalculated route.
(f) The file is now ready to be sent to the GPS if required.

I've referred to 'indexing' several time so it might be worth a couple of lines explaining what exactly I am meaning.
When you plan a route and adjust sections of it using the rubber band method under the point where you release the mouse will either be a white box when the route is place at a junction using two differing road names i.e. a crossroads or T-junction, or a black box if you place a box anywhere else on the road i.e. not at a junction.
In the case of the former (white boxes) these will be announced by the GPS but not flagged. With the black boxes (not recommended) this creates flags and the map view of your GPS will be full of blue flags. Both white and black boxes are 'indexes' and have a definite reference in map creation software. Updated maps can, and more often than not do, have slightly different reference points and simply using the Recalculate function is unable to re-index these points to where they should be hence the possibility of your route being thrown out. An example of this could be that an index point has now moved to the opposite side of a dual carriage/motorway which unless zoomed in 100% may not be noticeable but will cause the unit to announce 'make a U-turn' at the appropriate time.
The old way (and only accurate way) was to revisit these old routes, locate the index points and drag them off position with the mouse before moving them back again. This obviously can be a lengthy process but for ride leaders an essential process because they generally retain routes for several years for use again.
BaseCamp has made this process a lot simpler and quicker. It's also an idea to use this method if someone sends you a route (gdb or gpx file) that may have been created in a map version that does not match yours.
Hope this post will have been of some use to someone? :nenau
 


Back
Top Bottom