Please tell CS that BC is compatible with zumo 660

This is a bit...troubling. You appear to be saying the Zumo 665 I bought last year is now a legacy device and my choices for developing routes are to use discontinued Mapsource which has a tendency to crash with newer maps or Basecamp which may download routes the 665 can't work with. Is that correct?

Kevin

Well 'legacy' isn't the same as 'unsupported'. There was an update released for the 13xx and 14xx series quite a few years after they were first available, but none for the last 2 years as the software is now extremely stable. Map releases continue to work and Garmin still supports many devices older than that range.

What the issue is with some routes on the Zumo 66x series I have no idea, but from the posts above it seems to be an issue with most of the Zumo range so I suspect it's not something the BC developers can correct. If they can I'm sure they'll chime in :)

As a ardent believer in Consumer Self-help, if I had purchased a zumo66x recently and read this I would be returning the device.

So would I :)

It was May last year that it was purchased so it's over a year old and I doubt I'd have a leg to stand on unfortunately, particularly as it was bought in the US and I'm in the UK (the 665 isn't available in the UK). I suspect Garmin would say it still functions as a satellite navigation system and any issues relate to navigation software that was not purchased as part of the system and in fact was not purchased at all; I'd have no argument.

I buy Garmin units as opposed to another manufacturer's units because of the ability to plan routes on my PC and download them to Garmin devices so I'll confess to being somewhat 'disappointed', not least because I have two 660s and a 665.

I recognise I'm a niche user - I use the software for planning long distance motorcycle rides and rallies - and I really wish Garmin had some competition in this area but they don't and I doubt anyone's going to come riding in on their white horse to provide some unfortunately.

Kevin

I think you're right. And as I pointed out I'm pretty sure this is a device issue and not within the gift of the BaseCamp developers to solve. I'd like confirmation of that though since IF it is a BaseCamp issue it needs to be flagged for resolution.

<snip> Given that the 66x is considered a legacy device, there are no more firmware updates slated for it (that I know of). <snip>

I'm sorry to come back with this but I'm confused. The 660LM is listed as a current device for sale on the Garmin UK web site. How then can it be a 'legacy device'?

Kevin

I'm sorry to come back with this but I'm confused. The 660LM is listed as a current device for sale on the Garmin UK web site. How then can it be a 'legacy device'?

Kevin

I'm sorry too. And, having just tried it, I can confirm that upgrading to BC 4.3.4 has screwed up the ability to reliably copy routes to my NAV IV. It's the only thing that's changed on my system, and a route previously copied successfully has now gone berserk. Garmin has just recently released new maps for Europe NT - I'll try loading those onto both Mac and NAV IV to see if that fixes the issue.

I'm sorry too. And, having just tried it, I can confirm that upgrading to BC 4.3.4 has screwed up the ability to reliably copy routes to my NAV IV. It's the only thing that's changed on my system, and a route previously copied successfully has now gone berserk. Garmin has just recently released new maps for Europe NT - I'll try loading those onto both Mac and NAV IV to see if that fixes the issue.

Switch of the settings in the Device Transfer settings, found in the preferences of BaseCamp (Mac and Windows). This is a common problem with the new BC versions! Map names are now different between Device and computer, very handy, but not in combination with these options (especially the 3th one).

The new functionality is added to v4.3.4 BaseCamp, switched on by default, one line in a release note and we are on our own. Perfect to addition from Garmin for there customers, but the communication about it is piep piep pieper the piep worthless :cool: Switched off by default was a much better choice.

Thank you Marco. That solved a route transfer issue I was having with my Zumo 590.