SD-card not vissible in Basecamp

Hi,

I have a Zumo 350 with an extra SD-card installed.

In the past, when I connected the device to my laptop, both the internal memory and the SD-card was shown in Basecamp, and I could
select either location to send routes, maps,....
Lately only the internal memory location is shown in Basecamp.

The SD-cards is available when using Windows file explorer, and works fine under Windows.
Also the device can read the SD-card, as the maps which are installed on the card are available on the Zumo.

I tried reformating the card, but this did not help (as expected).

Any other ideas (besides reinstalling Basecamp, which I want to avoid)

0 SUSSAMB over 9 years ago

Sorry, I'm clearly missing something here ... I still don't understand what you mean when you refer to "locked lifetime map control" :confused:

0 Former Member over 9 years ago

Sorry, I'm clearly missing something here ... I still don't understand what you mean when you refer to "locked lifetime map control" :confused:

Well, it sort of like moderator powers.

As to my BaseCamp operation, it seemed prudent to boot up the Nuvi 56 through B/C one more time before responding. So, with B/C running an OSM map of US-CA, which included adjacent areas of US-NV, I unplugged the Nuvi 56 from the external Li-ion battery pack and plugged it into a laptop USB port. The usual and customary Windows list box popped up with its usual default options. I closed the Win list box by clicking on the -x- in the upper right corner and clicked on the B/C icon in the lower Windows tool tray. A B/C map of Reno, NV, USA popped up with some routing to various McDonald's and other POI coordinates.

Lo and behold, B/C "Trip to McDonald's6-Day 2" could now be deported to the SD card by the Send To method. CN North America NT 2015.40 had now been displayed without any map selection on my part. It must be magic, or some sort of hacker intervention. Or something.

On a related subject, the reason for the seemingly random number "6" suffix for this particular McDonald's location has nothing to do with the map POI database, but results from the relative distance and sequencing of a focus point search of POIs using B/C. The suffix on the created waypoint could be any number from "1" to the limits of the POI search in the upper right corner of B/C. These semi-random renamings of database POIs may be a cause of seemingly unexplainable routing anomalies in Nuvi devices in Reno area reported by another user.

In short, Send to SD card is currently working, but I would not necessarily use that feature in the first place as it is no great burden to drop a file off in My Documents before copying it to the USB connected Nuvi with Windows Explorer.