New user - wrestling with BaseBamp

Recently started using the GPSMAP62s and enjoying it except for some hardware/firmware issues but that is a different issue. Here is are several initial issues with Basecamp. Some may have been brought up by other users.

-BaseCamp displays "non-GPS" usb devices (Windows ReadyBoost, other USB drives, etc.) - any way to supress that?
-The device "sees" a track/route but, BaseCamp does not. That track is visible via Windows explorer.
-I can send an item to the SD card in the device but, once there, it may not be renamed, moved, deleted as I am able to do when it is on the device. I can use Windows Explorer to do that however.
-This HAS been discussed, how about a way to globally/individually turn off/on tracks, routes, waypoints without having to send it to a collection?
-The info balloons that pop up when you select a route, etc...any way to supress them or have them pop up somewhere besides on the map?

Hope this isn't too much in one chunk.
Thanks, John

There is currently no way to suppress non-Gps devices unfortunately. Maybe this will be added in a future version.

Where is the file located that you can see with windows explorer and what kind of file is it?

That is working as intended, deleting data is only supported on devices that support user data sync (the device checks which files are present and adjusts its database according to the data in those files). The 62 supports it, the SD card does not.

Noted. :)

Not currently.

Thanks FALAGAR for the response.
The file that I can see with Explorer and the GPSMAP 62s sees is a .gpx file. It is located on the SDHC card at N:\Garmin\GPX. In fact, now that I look further, NO gpx file on the SD card is displayed in Base Camp. Interestingly, BaseCamp does display BirdsEye and Custom Maps on the same SD card in folders N:\Garmin\BirdsEye and N:Garmin\CustomMaps!

The tracks, routes and waypoints on the SD card, although visible and functional in the GPS are not displayed in BaseCamp. If I move the same files to the GPSMAP 62s, they are visible in BaseCamp.

Don't know if this is related, BaseCamp displays a route on the GPSMAP that has no name (not noname but a blank name field). The properties show a number of via points and is actually my commute route no longer needed. This route is NOT visible on the device in Windows. If I delete it, I get the "can't be undone" bla, bla, bla message but, it reapears next time I connect the device and open BaseCamp. If I send the route to the SD card, it shows up in the GPX folder as "userdata.gpx". It still persists on reappearing after being deleted. It does not appear on the GPSMAP 62s and not in Windows...only BaseCamp
John

The behavior with the SD card is as expected (by me, not you :) ). Currently, BaseCamp does not "know" the SD card is part of your 62, and therefore I believe we only read a userdata.gpx file from the SD card's 'Garmin' folder, and ignore everything else.

In the future, we will make sure to recognize the SD card as part of the GPS, and then we will hopefully be able to read other files from the card as well. As it is right now, we recommend to store only map data on the SD card, other stuff is better put on the GPS.

The issue with the no name route is probably not related. It has to be somewhere on the device though, or we would not display it in BaseCamp. Is there a current.gpx file in the 62's Garmin folder or a subfolder?

The behavior of the SD card I find interesting...BaseCamp "sees" City Navigator 2012, .IMG files from GPS File Depot, and all of the .JNX and .KMZ files but NOT the .GPX files?. Curious.

As for the route with no name, I discovered it is contained within the "current.gpx" track file. I can see the waypoints when looking at the file with Notepad. If I delete the file, when the 62s created a new one, the "route" is back in the new one!

Every day since I discovered this, the information is carried over to the new current.gpx file. If I look at the current track with the 62s, the "route" is not seen. If I clear the route, the new current.gpx file has the "route" again. This round of testing was done with ALL routes, waypoints and archive tracks deleted.

Yeah. We currently do not read any gpx file but userdata.gpx. A future release (not 3.2.1) will correct this.

The route with no name, I do think BaseCamp is just doing what the device advertises. If the device writes out a current.gpx file with that route in there, that's what we display.

The route with no name pops up again, just like days before after renaming, editing, deleting it in BaseCamp.

Not going to be concerned any longer...just got a RMA for a warranty exchange (2 issues in additon to this one) so this mystery is soon on its way to Kansas Dororthy.