Can't get track off my garmin

Try the BaseCamp Beta 2.1.1.
There is a thread here with a link to download that.

Try the BaseCamp Beta 2.1.1.
There is a thread here with a link to download that.

Unfortunately, I still have the same issue.

Here is an image of what I am seeing.



The waypoints 001 - 004 should be part of "Current Track: 31 JAN 2010 00:12" and that track took a lot longer and covered a much greater distance then is shown by BaseCamp 2.1.1.

Your graphic does not show any map products are installed in Basecamp.

You should see something like the attached graphic in the tool bar of BaseCamp. Of course your map product might not be the same as mine.

Your graphic does not show any map products are installed in Basecamp.

You should see something like the attached graphic in the tool bar of BaseCamp. Of course your map product might not be the same as mine.

Agreed. I it doesn't show any map products. But, it can still show a map...

Why would the lack of a map product prevent the correct downloading of tracks?

Why would I not be able to use their browser plugin to upload to http://connect.garmin.com/ ?

I am personally thinking that the map product is only required when you want to create something to upload to the device and not when you just want to download something from the device. Or, am I wrong?

It looks like the tracks are being downloaded.
The basemap that is included with BaseCamp has very few features, and not so much detail either.
Since the map product is not the same that could mean the track will not display the same.

But I am not sure, seems this is a question for one of Garmin's senior support folks.

It looks like the tracks are being downloaded.
The basemap that is included with BaseCamp has very few features, and not so much detail either.
Since the map product is not the same that could mean the track will not display the same.

But I am not sure, seems this is a question for one of Garmin's senior support folks.

In the image above, BaseCamp is showing the track data as it believes exists on the device. The raw track data it is showing is clearly wrong.

I have contacted Garmin Support so hopefully I will get an answer soon.

Thank you for you assistance.

The waypoints 001 - 004 should be part of "Current Track: 31 JAN 2010 00:12" and that track took a lot longer and covered a much greater distance then is shown by BaseCamp 2.1.1.

Sorry you are experiencing issues. I've never seen a case where the active track downloaded from the device was wrong. The problem always occurs when users save the track on the device. If you did this, those tracks exist, but unfortunately because of a shortcoming in the 400 they don't automatically show. Using finder, if you look at your /Garmin/GPX on your device, there may be a number of .gpx files. You can import these manually using RoadTrip or BaseCamp and you may find your track.

I strongly encourage users not to save their tracks on the device. It is better to leave them in the "current" track. Transfer the current track to the desktop software and manipulate them there. Another side effect of saving them is all the times are stripped. This occurs on all Garmin units.

Sorry you are experiencing issues. I've never seen a case where the active track downloaded from the device was wrong. The problem always occurs when users save the track on the device. If you did this, those tracks exist, but unfortunately because of a shortcoming in the 400 they don't automatically show. Using finder, if you look at your /Garmin/GPX on your device, there may be a number of .gpx files. You can import these manually using RoadTrip or BaseCamp and you may find your track.

I strongly encourage users not to save their tracks on the device. It is better to leave them in the "current" track. Transfer the current track to the desktop software and manipulate them there. Another side effect of saving them is all the times are stripped. This occurs on all Garmin units.

Ok. Thank you for the advice.

Your suggestion of manually grabbing the .gpx track file from the 'GARMIN' volumn on my Mac worked.

I am willing to provide any assistance you might need in tracking down this bug, including running dtrace scripts, etc. Just let me know.

However, I do not see the times being stripped. Please see the attached image


Perhaps this was a bug that has now been fixed.

Success. (Well, there is still the importing directly from the device bug...but I at least have a workaround now.)

If anyone cares, my first upload is here - Carter Barron Hike