Garmin GPSmap 60CSx not seen in BaseCamp

So, you can access the SD card in the 60csx, but only to send maps. All other data types must be transferred (to the device) via serial (non mass storage mode) data protocol, which BaseCamp does not support. MapSource does support this form of data transfer, and is the only software Garmin intended to be used with the 60csx.

I have windows 7 64 bit and Basecamp is communicating nicely with my 60Csx via a USB cable. That's not to say there isn't some functionality lost that I have not noticed. It is only mildly inconvenient for me because the maps no longer live on my PC. But I'm find with that. I can visit mapping websites that function just fine for me.

My original post that questioned how to access the card has been resolved.

:)

That's not to say there isn't some functionality lost that I have not noticed.

I prefer using MapSource 6.16.3 with all my devices but do use BaseCamp on occasions.

That said BC should transfer user data (waypoint/routes/tracks) just as MS does. Of course you won't be able to view any maps on the units microSD card in BC at the same time since the unit has to be in mass storage mode to do that.

Now MS has the ability to transfer maps to devices. BC doesn't and uses the bundled program MapInstall. With the 60C/76C 'x' models maps have to be written to the card (vs the unit). Putting your device into mass storage mode simply converts it to a large, expensive and slow card reader. You're actually better off putting the card in a real card reader when transferring maps (and any other large files).

BABJ615 is correct in that the 60C/76C were designed when (and later came bundled with) MapSource was the Garmin software to use. You can use that (as I do) or use BaseCamp if you prefer. Your choice.

The bottom line is that the current version of BaseCamp supports the Garmin USB protocol (but not the RS-232 serial one). Older devices that use that protocol (60C/76C, some older eTrex modes, the Quest and later StreetPilot's) vs mass-storage mode will work with BC. Whether one wants to or not is a matter of opinion.

I prefer using MapSource 6.16.3 with all my devices but do use BaseCamp on occasions.

That said BC should transfer user data (waypoint/routes/tracks) just as MS does.

Just for clarification, MapSource and BaseCamp can send waypoints tracks and routes to your 60csx, the manner in which they do so is important to understand.

The older non mass storage GPSr (such as the 60csx) store all waypoints, tracks, routes etc in a single GPX database ("Current.gpx') on the device. Newer GPSr (mass storage devices like the Colorado and newer) store tracks, waypoints and routes (etc) independently of each other, and use the 'Current.gpx' file for you current track log recording only.

MapSource writes sent waypoints, tracks and routes (etc) to a 'Temp.gpx' file on your GPSr, and during the next boot process your GPSr adds the contents of the 'Temp.gpx' file to the internal database ('Current.gpx'), then clears the 'Temp.gpx' file from the device. MapSource will not read any other files present on any device, so if you are trying to read a newer device, you will only see the data in the 'Current.gpx' file. Also, MapSource only writes to the 'Temp.gpx' file, so if you send data to a newer device with MapSource, all sent data will be combined into a single GPX file named 'Temp.gpx', which the GPSr may rename during the next boot process.

Of course you won't be able to view any maps on the units microSD card in BC at the same time since the unit has to be in mass storage mode to do that.

Now MS has the ability to transfer maps to devices. BC doesn't and uses the bundled program MapInstall. With the 60C/76C 'x' models maps have to be written to the card (vs the unit). Putting your device into mass storage mode simply converts it to a large, expensive and slow card reader. You're actually better off putting the card in a real card reader when transferring maps (and any other large files).

Yes, all Garmin GPSr are painfully slow card readers.

BABJ615 is correct in that the 60C/76C were designed when (and later came bundled with) MapSource was the Garmin software to use. You can use that (as I do) or use BaseCamp if you prefer. Your choice.

The bottom line is that the current version of BaseCamp supports the Garmin USB protocol (but not the RS-232 serial one). Older devices that use that protocol (60C/76C, some older eTrex modes, the Quest and later StreetPilot's) vs mass-storage mode will work with BC. Whether one wants to or not is a matter of opinion.

Personal preference indeed! And once the user fully understands the pros and cons of each, they can make a better decision.

The older non mass storage GPSr (such as the 60csx) store all waypoints, tracks, routes etc in a single GPX file ('Current.gpx') on the device.

I'm curious to know how you know this. On such devices the user has no direct access to internal storage. I'm sure a filesystem is used and there may indeed be a current.gpx file in there but how do you see it? User data is accessed. indirectly, via the serial or USB protocol.

PS: I just did a dump of the 60Cx/60CSx/76Cx/76CSx firmware image (029201000400.rgn) file and it doesn't contain any reference to "current.gpx" or any other GPX file. The file is not compressed and one can see the embedded text strings clearly.

PPS: What I did find is text that relates to writing track log GPX files to the SD card (a feature of these models).

I'm curious to know how you know this. On such devices the user has no direct access to internal storage. I'm sure a filesystem is used and there may indeed be a current.gpx file in there but how do you see it? User data is accessed. indirectly, via the serial or USB protocol.

Independent testing and research.

In review, I left out some important details in my previous post, and I have edited it to be more complete and accurate.

PS: I just did a dump of the 60Cx/60CSx/76Cx/76CSx firmware image (029201000400.rgn) file and it doesn't contain any reference to "current.gpx" or any other GPX file. The file is not compressed and one can see the embedded text strings clearly.

Connect a newer mass storage GPSr to your computer, and send several waypoints, tracks, and routes to the GPSr using MapSource.

Find the newly created 'Temp.gpx' file in the \Garmin\GPX\ directory, and copy it to the \Garmin\GPX\Current\ directory.

Delete the existing 'Current.gpx' file.

Now, clear those waypoints, tracks and routes from MapSource, and then ask MapSource to import all tracks, waypoints and routes from the connected device. It will find your GPSr, but will not find any data to import, regardless of any GPX files in the \Garmin\GPX\ directory.

Rename the 'Temp.gpx' file on your GPSr to 'Current.gpx', and again ask MapSource to import all tracks, waypoints and routes from the connected device. The data you sent originally will now be imported into MapSource.

This test confirms that MapSource only writes to the 'Temp.gpx' file and only reads from the GPSr 'Current.gpx' file. It is no stretch of the imagination to conclude that the 'Temp.gpx' data is assimilated into the 'Current.gpx' data each time the unit is powered on.

PPS: What I did find is text that relates to writing track log GPX files to the SD card (a feature of these models).

Yep. Older 'x' units had that option due to extremely limited internal memory capacities.

I think you have it around the wrong way. On the Zumo range of receivers and on my Nuvi 1490, the "temp.gpx" file is created by Mapsource or Basecamp in order to transfer data to the device. Mapsource creates a new file each time, but Basecamp appends new transferred data to the file.

The "current.gpx" file is created by the device when it is connected to a computer and is used as a means of transferring a copy of the internal data in the device memory to either Mapsource or Basecamp. If you modify this file it will have no effect on the contents of the device memory.

I think you have it around the wrong way. On the Zumo range of receivers and on my Nuvi 1490, the "temp.gpx" file is created by Mapsource or Basecamp in order to transfer data to the device. Mapsource creates a new file each time, but Basecamp appends new transferred data to the file.

The "current.gpx" file is created by the device when it is connected to a computer and is used as a means of transferring a copy of the internal data in the device memory to either Mapsource or Basecamp. If you modify this file it will have no effect on the contents of the device memory.

This may all be correct for the nuvi and zumo units, but is not true for Garmin 'On The Trail' GPSr.