I've been searching this site for answers to the problems I've been having regarding the transfer of data (routes and waypoints) from Basecamp to my new Nuvi 2595. So far, I've seen some discussion of it, and in trying to add to one discussion, the site apparently didn't know what to do with my comment and it went into the bit bucket in the sky.
Here is what is happening:
When connecting my 2595 to my Win 7/64 laptop and booting up Basecamp, I immediately see the routes and waypoints that I have in Basecamp, and until a few days ago (when there was an update to my device) I could also see the routes and waypoints that I had downloaded from BC to the 2595. Now, however, when I connect the 2595 to BC, the routes on the device do not show up in BC. All of the waypoints that I transferred to the device from BC do show up.
I totally wiped my 2595 clean with a reset procedure, then reloaded the routes and waypoints. This seemed to work, and while the device was still connected to the laptop, I could see all of the files that I had transferred from BC to the 2595. But when I disconnected the device, and then reconnected it, the routes were no longer visible. One other thing -- after I transferred the routes from BC and disconnected the device, I set up a new route on the device itself using the trip app. When I reconnected the device to BC this route (trip) was the only one that showed up in BC as belonging on the 2595. (The routes that have been transferred to the device from BC are all on the device -- they just won't show up in BC when the device is reconnected.)
I've seen discussions of the .gpx files somehow being linked to these issues. There are only two .gpx files now on my device: current.gpx, which is 209kb in size, and temp.gpx, which is 7.53mb in size. Looking at the temp.gpx file using a text editor, it appears that this is my waypoints file and it also appears to hold all of my trips. There are no other .gpx files on the device that I can find. (INLINE UPDATE: Okay, I just made a copy of the temp.gpx file and renamed it to waypoints.gpx. BC now sees all of the routes on the device as well as the waypoints that were already there.)
A couple of questions:
1. Why would routes transferred to the device from BC be visible on the device's internal memory (viewing from the BC desktop) immediately after transferring them, but not visible after disconnecting the device and then reconnecting it to BC? (It seems I answered this question through my little experiment -- because the waypoints.gpx file no longer exists, but something called temp.gpx has taken its place.)
2. Some routes, when transferred to the device from BC, have all via and waypoints intact within the route on the device. But some routes (and sometimes much simpler routes) don't? Case in point: I've planned a trip with a start and finish point, with three waypoints between, selected from the lodging waypoints in BC. On the transferred route within the device only one of these motel waypoints shows up, the other two don't. I can restore these waypoints to the route directly on the device, since those waypoints have actually been saved. But this is just weird.
Any suggestions, comments, bug fixes?