I am working on a BaseCamp issue and I needed to completely delete my CNNA 2015.10 map from the Montana device. After doing this I verified on the device that it only had the basemap installed. Using Express 3.2.17 I wanted to do a fresh install of 2015.10 on the Montana. However, GE refuses to do this saying that the device is already up to date. I have deleted the device from GE, reinstalled and restarted GE, refound the device and still GE says my empty Montana has an up to date 2015.10. Any ideas on how to convince GE that there are no maps on my Montana?
Since the Montana is not preloaded with City Navigator mapping, Garmin Express will not install the maps to the device. Express installs the map to the computer then MapInstall installs the map to the Montana or microSD/SD card. It doesn't sounds like you uninstalled the 2015.10 maps from the computer so all you need to do is use MapInstall to install the maps. See the FAQ: How do I install mapping to my device with MapInstall?
The route issue is totally separate and may in fact be an issue. I will look into this. This does not change the basics on how non-preloaded devices work. All devices that are compatible but not preloaded with City Navigator maps require a full version DVD in order to install the maps to the computer and be eligible for map updates. All full version DVD maps install to the computer first then are sent to the device or sd card by MapInstall. Basecamp does not and should not read the maps sent to the device because they are already installed on the computer. There's no reason to read the maps on the device.
In the past the Route recalculation issue occurred when a route was initial created on a prior map version. Example would be a route created on 2013.10 maps. After a couple of map updates the computer has 2015.10 and the device has 2015.10. The route created on 2013.10 maps still has some meta-data attached that says it was created under 2013.10 maps. Basecamp displays the warning and the device will recreate the route which is usually undesirable.
The resolution in the past was to recalculate the route in BaseCamp with the 2015.10 maps active then send the route to the device. You'll have to monitor the changes made after the recalculation and edit the route as needed. The way I understand it the parties involved have created new routes in 2015.10 maps but still get the route error when transferring the route to a 2015.10 device . That should not happen, so I will have to test that out.
The recalculation is a simple solution but it has to be done with the City Navigator 2015.10 maps active in BaseCamp and before the route is sent to the device. Basecamp displays maps installed on the computer as City Navigator North America. It doesn't matter if BaseCamp can see the maps on the device or not. I will test creating/sending a route in North America 2015.10 maps and get back with if I find anything.
The only time I can get BaseCamp 4.3.5 to display the error, "Routes send to device were recalculated because they were created on a map that is not installed on the device" is if I create the route on any other map or version than the one installed on the device. That is the way it is supposed to work.
If I change the active map in BaseCamp then recalculate the route, BaseCamp does not display the error when it is sent.
Thanks JAVAWA. I referenced using the Device Manager in my Basecamp thread as a way to work around my issue. In fact, it is the only way I can get Basecamp to not generate the warning message and result in a usable route on the device.
EXPRESSCUSTOMERCARE,Assume I have an existing route created on any map other than 2015.10. If I open this route with 2015.10 selected as the active map and recalculate the route should I be able to be send it to the Montana without a warning? The only way I can get this to happen is if I use JAVAWA to mark the map as visable in Basecamp. I never had to do this the prior to 2015.10.
The thing to me is with the device map visable to Basecamp I now have two 2015.10 maps in the Basecamp Maps pulldown. However, it doesn't seem to matter which is selected as the route is transferred without the warning. Without the device 2015.10 map visable to BC the warning is generated and the route is unusable. Again, this is new with 2015.10. Something has changed.
However, if everytime a map is updated I need to recreate (not recalculate) a route then I have a problem with that. So far, with my installation, a simple recalculate doesn't fix the the issue.
Interesting, I will look into why it works if BaseCamp can see the maps installed on the device through MapInstall. Since BaseCamp should not really see these something must have changed.
I was able to confirm what you are describing and the solution provided by Desktop App Developer ERACERZ. "You can turn off this warning dialog in the options. Edit->Options->Device Transfer, Select the Device from drop down menu, uncheck Always match route to the map on my device when transferring". So the message isn't caused specifically by MapInstall but is a result of changes made in BaseCamp. If the Desktop App Developers see that the changes are having a negative effect on a large number of BaseCamp users with non-preloaded devices then they may evaluate how to handle these route transfers in future releases but I suspect that's why the option to disable the message was added.
