BaseCamp Upload to BMW Navigator lV (Zumo 660) Route Corruption Problem

Former Member
Former Member
My BaseCamp and other software/firmware is fully up to date.
If I create a Route in BaseCamp I don't have a problem. Mileage, time etc all correct
It all goes wrong when I upload it to my device which is a BMW Navigator IV motorcycle unit but essentially it's a Zumo 660
Examining the BaseCamp created route on the device it is totally corrupt. Miles, time etc completely different and Waypoints are created on the device that
do not exist in the same place on BaseCamp.
The uploaded Route then just connects Straight Line routes between these Waypoints
This problem is driving me mad. I've tried everything I know to cure it for days now but nomatter what I try I get the same result. Very frustrating
I hope it's something silly that I'm overlooking. Can anyone point me in the right direction please?
  • Former Member
    0 Former Member over 10 years ago
    BaseCamp 4.4.2 (Mac & PC) has issues with routes. That may be the cause of your problems (not sure).

    v4.4.2 Routing Issues

    Garmin is aware of the issue and is working on an update.
  • Are you using the same maps on both?

    Note that I believe there is an issue with transferring routes to one particular zumo model, but I can't recall if it's the 660 or not
  • Former Member
    0 Former Member over 10 years ago
    Note that I believe there is an issue with transferring routes to one particular zumo model, but I can't recall if it's the 660 or not


    You're probably thinking of this

    Garmin CSR is recommending Zumo 550/66X users go back to MapSource???

    I've seen other posts about it too.

    Of course that doesn't help Mac users (MapSource in a Windows program).
  • You're probably thinking of this

    Garmin CSR is recommending Zumo 550/66X users go back to MapSource???


    Yes :)
  • "Garmin CSR is recommending Zumo 550/66X users go back to MapSource???"

    Is it being suggested that Basecamp and the ZUMO 660/BMW Navigator IV are not compatible? Wait a minute! This doesn't make sense, but maybe I'm not following the Tread correctly.

    I've been using various Garmin GPS's for the past 14-15 years and until recently they were all relatively easy to learn. On the other hand, I find the Zumo 660/BMW Navigator IV and Basecamp very difficult to learn, let alone master.
  • Former Member
    0 Former Member over 10 years ago
    Is it being suggested that Basecamp and the ZUMO 660/BMW Navigator IV are not compatible?


    Yes, that's exactly what's being said.

    Others have had the same reaction as you. As I said above there are a few posts about it (I forget where).
  • Former Member
    0 Former Member over 10 years ago
    You might want to read this thread as well.

    Please tell CS that BC is compatible with zumo 660

    BTW I don't have a dog in this hunt. I mostly use MapSource not BaseCamp, don't own a Zumo, nor do I ride motorcycles.
  • Former Member
    0 Former Member over 10 years ago
    Thanks for your help.

    At least I know it's not me being obtuse - I can be :)
    This is a serious shortcoming. Hope Garmin come up with a fix before my next big trip

    BaseCamp 4.4.2 (Mac & PC) has issues with routes. That may be the cause of your problems (not sure).

    v4.4.2 Routing Issues

    Garmin is aware of the issue and is working on an update.
  • Former Member
    0 Former Member over 10 years ago
    Yes. Latest maps being used - CN Europe NT 2015.20 - same on both Zumo device and BaseCamp.
    On a route well known to me ( for testing purposes ) the stats are spot-on in BaseCamp. When looking at the uploaded route on the Zumo device it's "all over the place".
    Wrong mileage, wrong time and caused by Straight Line Routes (ie not following roads ) being linked back and forth between WayPoints, which themselves are not in the same place as
    the WayPoints on BaseCamp. For example, in the middle of fields. Everything is set up correctly for Motorcycle and excludes the obvious such as Tracks. It's bizarre
    Thanks for your response. Any idea on when we may get an update from Garmin to fix this?