Basecamp and 393 maps don't match

I've got CN NA 2024.1 on both Basecamp and the 396. The 396 actually shows 2024.10 Foursquare, 2024.10 ALL Canada and Mexico and 2024.10 ALL US. I'm guessing the trailing 0 doesn't show up when looking at the map version on Basecamp as it shows 2024.10 on Express.

When sending routes from the PC to the device I get a message 'Routes sent to zumo 396 were recalculated because they were created on a map that is not installed on the device.'

As best as I can tell the routes look okay on the 396. Does anyone know what is causing this and if it will create any problems with the routes?

0 Peobody over 2 years ago

When installing maps to the PC, old ones are not removed and the new one is not automatically enabled so verify that the CN NA 2024.1 has a checkmark next to it in the Maps menu of BaseCamp.

Regarding problems with the routes, any calculation by the device has the potential of routing differently than what BaseCamp did. The only way to tell is to load the route on the device and then compare that route to what you did in BaseCamp. If you are lucky, you had enough route points to force the device to calculate the same route that BaseCamp did.

0 Littlefield over 2 years ago

Yes, the new map is checked on Basecamp. Another odd thing. When the device is plugged into Basecamp it shows there are 2 copies of CN installed on it. I may reload the map and see if it makes any difference. And do a visual comparison.

0 SUSSAMB over 2 years ago in reply to Littlefield

There will be 2 maps on your device, the map is now too large to stay within the FAT32 file limit so the NA map is now split in 2 on your device. The EU map has been split in two for many years. On your PC the FAT32 limit doesn't apply so that map is the full NA map.