Basecamp and Enduro3

H! it's not a problem. Enduro3 can't work with Basecamp. Instead, you can enter your GPX  files directly in the 'NEW FILES" 

Hi, 

Is there an official Garmin statement about that?

tks

Garmin officially discontinued development of BaseCamp several years ago, and it is no longer updated or supported. This means it doesn't receive updates to support newer Garmin devices or the latest operating systems on computers .

Additionally, many newer Garmin devices, particularly those released in the past few years, are not compatible with BaseCamp. These devices often require more modern software solutions for managing routes and maps . Garmin now encourages users to utilize Garmin Express and Garmin Connect for managing device settings, syncing data, and updating software. For route planning and mapping, Garmin Explore is the recommended application. Garmin Explore offers a more modern interface and better compatibility with current devices.

Well, well, well...

I have been playing a little with Explore
I'm not using the phone based version because I need a larger screen, so this is my experience with the web based version

At first glance, it is a major step back when comparing it with BaseCamp

From an architecture point of view:
- You depend on a proper internet connection (which is not necessarily the case at my place)
- You rely on CloudFlare services (which is good), except when you get "Bad gateway error code 502" which made me loose the track I was designing
- All your data is "somewhere" in the cloud without a proper control on who does what with your data
- Having a smartphone is mandatory to sync your tracks to your Enduro (when a basic, cheap USB cable could do the job)

From a functionality point of view, I could not find several essential track management functions:
- How to prevent automatically switching to the satellite view when zooming zoom under the 100m?
- How to duplicate a track?
- How to split a track?
- How to add segments to an existing track?

Explore offers indeed a more modern interface, but seems to have dropped essential functionality for track design...
At first glance, being forced to migrate from BaseCamp to Explore seems to be a real PitA...
But maybe I missed a few things ????

Hey, well until I read this post my Enduro 3 worked fine with basecanp. I have Basecamp on Windows 11 pc. No issues connecting with my Enduro 3. No different to my previous garmin products (original Epix, Fenix 6x Pro, GSMAP 67, 64,61.)
I connect the E3 via USB. Watch setting USB mode is MTP (Media transfer). Watch settings>System>Advanced>USB Mode.

In basecamp I select a track the go: Device> Send to device> Send selection to device. it works great. 
I can also go Device> Receive from Device.

Except!! Recently update E3 to 17.28. Connect just now and E3 will NOT talk to basecamp. Not happy.

Hi, mine is 12.28 too. Look at this photo.

Hi
Thanks a lot for this update
I didn't mention it, but BaseCamp is functioning perfectly with my GPSmap

My E3 watch is also on 17.28, but I'll try the MTP setting anyway tonight
BTW, I'm on Windows 11 with BaseCamp 4.7.5

OK. I found a workaround. (Including suggestions from here)

To export to the E3:
- From Basecamp.
- Select a track or folder. File> Export> Export Selection (Or folder name)
- Save to wherever you save your tracks. I have a "Tracks folder" set up. 
- Connect E3 to PC. 
- Copy your Track file from your Track Folder across to Enduro3\Internal Storage\GARMIN\NewFiles. 
- When you disconnect the watch it will copy these into it's own directory and you can see the track. 

To import to Basecamp:
- From Basecamp
- Select a directory or list in your collection.
- File>Import into[Current list]
- Navigate to Enduro3\Internal Storage\GARMIN\Actvity. 
- Select the activity you want to import. (Fit file)

That will work well enough for my needs.

Yes, that method is indeed properly described and works
It's just that it requires several export/import manipulations instead of the straightforward drag and drop which used to work previously

Put it differently: "why would you do it the simple way, when a complex end error prone method exists"!