Message when sending route to Montana

Bumping this in the hopes a Garmin developer will chime in. Does anyone know exactly what is meant by this message banner that is displayed just below the menu bar:
"Route(s) sent to Montana 600 (Unit ID nnnnnnnnnn)(N:) were recalculated because they were created on a map that is not installed on that device."
The meaning is acutally obvious but it shouldn't be happening.

I have City Navigator North America NT 2015.10 installed as the only map on the Montana and it is selected in Setup->Maps.
I have City Navigator North America NT 2015.10 installed on the PC and it is selected on the map pulldown on Basecamp 4.3.3.

What more can I do or need to install to get this thing to not give me an error message when doing a simple copy of a two waypoint route from BC to my Montana?
I know that I can disable this error message by deselecting an option in Device Transfer options to not match routes to the map installed on the device but why should I need to do this if the same maps are installed on both the device and the PC?

I'm having the exact same issue on my 62s, and it's driving me nuts!

I called Garmin earlier in the week. We messed with some device settings - verified I was using the same map in BC as on the device, verified the routing was the same as in BC (in my case "hiking") - and they had me delete and recreate the routes I was trying to load (via BC, not via the device). A bit of a pain in the bum, but it did the trick. I created a few additional routes over the next couple of days, and had no trouble loading them to my device. Now, I'm getting the error again! I've changed no settings since then.

FWIW, my maps package is the 24k Topo Northwest set.

What gives, Garmin?

So you have the same map installed on the Montana and one on the PC is that correct? As in if you disconnect your device from the computer, you still have access to the 2015.10 map?

I am curious to know if you are able to get expected results if you use the map on the device itself, and not the one that is installed on your PC. If this works, this is indeed a bug and I will write a case for that. Let me know the outcome of that and I will investigate.

Thanks again for the feedback.

I do have 2015.10 installed on both the PC and the device. When I disconnect the device I still have the 2015.10 map available in Basecamp. I'm not sure how to perform your test of using only the map on the device without deleting the maps on the PC. Let me know how to do that and I'll try. I have a route that I created some time ago with an older map version but even if I recalculate using 2015.10 I get this warning message. Is this perhaps something to do with waypoints created on an older map version? I can change activity profile to direct and not get the message. All other profiles display the message.
Do you know what exactly is being compared to cause this message to be displayed.
I can send you the .gpx of this particular route if you wish. It's about 500K.
As another note I do have several older CNNT maps installed on the PC; 2008, 2014.3, 2014.4 and 2015.10. 2015.10 is selected in the drop down list.

I'll try to add some additional information about this issue. Using JaVaWa device manager I made the 2015.10 map on the device visable to BC. Upon restarting BC I now had two instances of 2015.10 in the map dropdown. Now no matter which 2015.10 I select I no longer get the warning message: Route(s) sent to Montana 600 (Unit ID nnnnnnnnnn)(N was recalculated because they were created on a map that is not installed on that device.". I'm assuming that one of the 2015.10s in the dropdown is the BC copy and the other is the device.
I just changed the device copy back to be not visable to BC and indeed there is now only one 2015.10 in the dropdown. However, when I try to copy the previous route to the device the warning message is back.

I should also add that if I ignore the warning and try to use the route on the device it is not usable. The device complains that it needs to recalculate and when it tries that it complains that there are no routable roads.

Another point is that I can create the same route on the device using the same waypoints with no routing problem. The problem seems to occur if the route is sent to BC and then back to the device.

In all previous versions of BC and CNNT I did not need to have the device map visable to BC. Is this now required?

Same problem with Montana 600 and CN North America NT 2014.14 maps installed on PC and Montana. Any fixes?

So far not much interest from Garmin. I just did a BC 4.3.5 install with CNNT 2015.10 on a brand new Toshiba Win 8/64 laptop using Garmin Express to install the map on the PC. Using the same Montana 600 I get the same "problem". I don't know if it's just a Montana thing or something else. I guess as long as I have a workaround Garmin will considered it's fixed.

In all previous versions of BC and CNNT I did not need to have the device map visable to BC. Is this now required?

Are you sure? If BC couldn't see the map how would it know it was installed? It would seem logical that you'd get the error you mention, since Basecamp would think that the routes were created on a map that isn't on the device :confused:

Yes, pretty sure. In the past I have loaded the same map on both the device and BC either with mapinstall or more recently GE. At that time BC would only show a single entry for the map in the map selection pulldown. This setup always worked.

Since 2015.10 I have needed to use JaVaWa device manage to make the map on the device visable to BC. With this done I now see two entries for the 2015.10 map in the map selection pulldown. Now, regardless of which 2015.10 map is selected I no longer get the warning message. I never had to do this before and I never had two entries for the same map displayed in BC before.

In any case, if this is now required then Garmin Express should make the device map visable to BC when installing the map. I have completely cleared all maps from the deivce and installed 2015.10 via GE but the maps are not marked as "visable" to BC after installation. I need to use the JaVaWa device manage to change that setting.

So I'm not sure what is correct or wrong but something changed in the latest map release. Or at least it has changed for me.

Currently this is the designed behavior, although obviously it isn't ideal.

You probably sent the maps to the Montana using MapInstall. BaseCamp doesn't see maps that were transferred with MapInstall, so from BaseCamp's perspective that Montana doesn't have the CityNav 2015.10 maps.

You can turn off this warning dialog in the options. Edit->Options->Device Transfer, uncheck "Always match route to the map on my device when transferring".