BC Bug: "Cannot calculate the route. No roads near the destination" Error.

Former Member
Former Member
I'm told over at the Zumo Forums that someone at Garmin might monitor for issues and bugs, so here's one. This is with Basecamp 4.2.5 and the Zumo 660.

Updated to the latest North America map, NT 2014.40, and it looks like Garmin still hasn't fixed the "Cannot calculate the route. No roads near the destination" error. I re-check my custom route and all via and way points are on legitimate roads. It's an annoying bug since forces one to select the custom route again and start from scratch.

Anyone else having this problem?
  • I assume you're talking about a message you're getting in Basecamp? Which map do you have selected?
  • Former Member
    0 Former Member
    I use Basecamp with the newest map 2014.40 to create the route. The message appears on the Zumo 660 during the trip. The route is aborted when the error message occurs.
  • Ah OK, I understand now, it's a Zumo and not a Basecamp error. Is your zumo running the latest software?

    When you say you use the 2014.40 map that is both on the Zumo and in Basecamp?

    If you have never done so since installing a software and/or map update I'd try a master reset to see if that clears it.
  • Former Member
    0 Former Member
    I just wanted to follow up that even after the master reset, the Zumo 660 still reports this error. It seems to happen most commonly if I deviate from the programmed route for a bit. After the message, the route stops and I need to re-start it. Then it returns to normal ... for a while.

    Singlespeeder
  • Former Member
    0 Former Member
    I am now having this problem was it ever resolved ?
  • I started having the same problem after installing CNNA 2015.10 on Basecamp 4.3.4 and a Montana 600 with 5.9 firmware. I reported this in several threads and was rewarded with a yawn.
    I finally found a solution that works for me but it's something I shouln't need to do and didn't need to do until very recently. Using JaVaWa Device Manager I made the map installed on the Montana to be visable to BaseCamp.
    Now BaseCamp shows two copies of 2015.10 in the map products list. Selecting either of the two maps works fine with no routing errors. If I remove the Montana's map from BC visibility then the error returns.

    The difference for me is that on BC 4.3.4 (and maybe 4.3.3) there is an option under Device Transfer to "Always map the route to the map installed on my device when transfering". If this option is checked AND the Montana's map is NOT visable to BC I get a warning message whenever I transfer a route. The message is something like "The route was recalculated because it doesn't match the map installed on your device. But I have a full 2015.10 installed via Garmin Express on both the PC and device. If I ignore the message and transfer anyway the Montana will bark about needing to recalculate and then cough up the "Cannot calculate the route. No roads near the destination"

    Using the same waypoints transfered from BC to the Montana I can create the same route on the device with no problems. It's only when BC get involved that things fall apart.

    The Montana has the maps installed on a SD card with 12 GB free and the Montana has about 3 GB free so space should not be an issue. I have tried moving the map from the SD card to the Montana internal with no change.
    Maybe if enough users report this issue Garmin may take an interest and at least explain what BC is looking at to think that the maps are not the same.
  • Former Member
    0 Former Member
    Problem still not fixed

    The problem is still not fixed: I have a ZUMO 660.

    The map I have installed on both Basecamp 4.6.2 and the Zumo is the City Navigator North America NT 2017.2
  • This is a Zumo device issue and not BaseCamp. Please contact product support.