BaseCamp 4.4.2 Is Now Available

Thing is: you state a situation I (and others) do not recognize at all.

a. working with the zumo660, with recalculation off the unit will not recalculate. There used to be one exception: in older firmware-versions it would recalculate once you drive in the opposite direction of the route (or the unit THINKS you do; e.g. in hairpin situations). The zumo550 still has that behaviour; in the 660 is was solved via firmware-update. This is the only explanation I can think of. You might want to check if you have the most recent firmware in your Zumo.

Not true! My riding partner has the 665 and his unit was doing the exact same thing with the routes, but not necessarily at the exact same time. We both have the latest firmware. Garmin support stated this was a known issue but that they were no longer updating the units firmware so it could remain compatible with Basecamp. I was instructed to use Mapsource.

b. essentially, working with a zumo 660 there is no relevant technical difference between a route from basecamp or mapsource; there are minor differences but they will not affect recalculation behaviour.

There might be other aspects causing your problem. You might want to check your unit using the JDM tool. http://www.javawa.nl/jdm_en.html

Again, not correct if you want to believe what Garmin is telling me. They are telling me to use Mapsource to avoid this behavior.

Yes, currently we are recommending Zumo 600 series owners use MapSource for route planning.

Yes, currently we are recommending Zumo 600 series owners use MapSource for route planning.

1. Is the reason that the 600 series units seem to be affected more than the 550 because the 600's deviation distance from route that triggers a recalc smaller than the 550?
2. Is it fair to say that as soon as this problem is fixed (you had earlier said a fix is being tested), then BaseCamp will return to being the recommended route planner for all devices?

1. Is the reason that the 600 series units seem to be affected more than the 550 because the 600's deviation distance from route that triggers a recalc smaller than the 550?

This makes no sense! Why is it recalculating without prompting? I can ride completely off the route, like to a gas station, and the unit will prompt me for a recalc. I just ignore it and the gps continues navigate when I get back on the route. But if I'm riding on the route and it thinks I've deviated a little it just recalcs without asking??

2. Is it fair to say that as soon as this problem is fixed (you had earlier said a fix is being tested), then BaseCamp will return to being the recommended route planner for all devices?

If I remember correctly, Garmin has stated this is an incompatibility with Basecamp and the firmware in the 660s. There is no plan to upgrade the firmware in the 660s anymore. Therefore there is no fix coming. They have fixed some firmware incompatibilities in the past by, not by updating the firmware, but by compensating for the issues in Basecamp. I don't believe they want to, or can, fix this one in that manner. They haven't fixed it after being told about this last summer. What makes you think they are going to fix it now?

Adam, I can certainly sympathize with your frustration and anger. You've already stayed with Garmin long after many would have set their device on a track rail like an old penny... None the less, I'd like to hear JM's comments on my questions, ideally with some further amplification, since this is a very serious issue.

Adam, I can certainly sympathize with your frustration and anger. You've already stayed with Garmin long after many would have set their device on a track rail like an old penny... None the less, I'd like to hear JM's comments on my questions, ideally with some further amplification, since this is a very serious issue.

I hope you get a satisfactory answer to your question.... :)

Meanwhile back from a short test-ride. Could now reproduce but did see some odd behaviour I would have to dive into. Tested with BC 4.4.2. and CN Eu 2014.40

Two questions:
a. do you have the City Navigator map on internal memory or on SD?
b. with 'device transfer' setting: do you have 'match route to the map' selected?

If both are 'yes' I think the route is recalculated on the basemap, leading tot dramatic results. I would advise to try again with at least one of the two changed.

Also; please try to convert the route to the track and then send it to the 660 and import the triplog. At least the last method should solve the problem.

@ JM47048: since which BC-version does Garmin advise to use mapsource instead of basecamp?

The maps are loaded into internal memory. The 'always match route...' is checked.

@ JM47048: since which BC-version does Garmin advise to use mapsource instead of basecamp?

I believe around the time 4.2 came out.