Nuvi trips are invisible in BaseCamp

Former Member over 10 years ago

I have several trips saved in my nuvi. None of them are visible in BaseCamp. Why is that?

I can understand that BC will not edit data stored in the nuvi but I find it odd that trips are not even seen by BC.

It appears nuvi trips are stored in xxx.trip files... are there any alternative ways to see them in BC? outside BC? some import/export trick?

Thanks

0 SUSSAMB over 10 years ago

They show in BC for me and always have done. Is your nuvi set to mass storage mode? Mine is and I've never hooked it up to BC in mtp mode so maybe in that mode trips aren't visible?

With my nuvi connected I simply select Internal Storage and all my data shows in BC.

0 Former Member over 10 years ago

Yes, my nuvi is in mass storage mode and I, like you, see the routes in Internal Storage, but those routes are simple route files (.gpx), not trips.

Trips, as the ones auto imported by the nuvi from route files sent from BC, or created directly by the user in the nuvi's Trip Planner, are invisible.

To see what I mean: create a simple two waypoint trip in the nuvi trip planner and save it, then try to see that trip in BC. In my case that trip is invisible in BC.

Thanks for the assistance.

0 SUSSAMB over 10 years ago

What device do you have?

It works for me but some devices won't send trips to Basecamp, see Note 1 here

https://support.garmin.com/support/searchSupport/case.faces?caseId=%7B65814150-50b3-11dc-4ec8-000000000000%7D

0 Former Member over 10 years ago

That's it, you nailed it, thank you.

My nuvi (3590) is in the list of devices with invisible trips. :mad:

What a bummer, BC trips do not transfer well to my nuvi and my nuvi trips can't be seen by BC, so in effect BC is useless to me as a trip planning tool. Nice one, Garmin.

0 SUSSAMB over 10 years ago

Trips should transfer OK though?

0 Former Member over 10 years ago

They transfer OK, in the sense that the gpx file created by BaseCamp contains all the info for the route and the corresponding waypoints all the info for the stops. But that's as far as it goes in terms of "OK". The data is there, but the nuvi ignores most of it.

When the BC trip (gpx file) is received by the nuvi the device creates a nuvi trip which ignores most of the info passed to it and simply creates a dumb sequence of stops. Prectically all the trip information is lost.

What's the point of spending hours and hours in BC creating a trip with departures, layovers, comments, etc if the only data that makes it to the device is a dumb "A to B to C" list with none of the additional data you put in BC?

0 Former Member over 10 years ago

Although my Nuvi 56 firmware and device CN map are a generation ahead of BC due to a half completed upgrade a couple of nights ago, I did manage to create a Trip with Layovers by hours and minutes, if not days, in the Nuvi 56. Then I "round tripped" the Trip file through BC and back to this newer Nuvi, with intermediate parking of the gpx file in an unrelated Folder on the computer C drive. Oh yes, the Trip received a renaming while in BC for reference purposes.

All the Stops and Stop Duration layover times seem to remain the same back in the Nuvi, although arrival times can vary with recalculation due to various route road profiling differences. Upon further review, it seems that there are still some shape points in there that are not considered to be worthy of fully editable time hacks or layover Duration times by the Nuvi.

FWIW, this Nuvi 56 is not currently playing well with either Windows 7 Explorer or BC when hooked up to the USB port, but I am not going to try fix the device driver issue until after my next trip in a couple of weeks.