I have a large (128 Gb I think) memory card in my Zumo 665 that is virtually empty. I use BaseCamp to transfer new trips to the 665. Once I disconnect, the 665 imports my files and then tells me that it has insufficient memory? What good does it do to get a memory card if the device cannot even use it? This seems extremely ridiculous to me. Garmin shipped the GPS with almost no storage space available. They provided for expanded storage via micro-SD, but then you can't really use it anyway? Am I doing something wrong here, or is Garmin really that inept?
Worse still, I cannot delete the internal storage on the Garmin from BaseCamp. I have to go through the labor-intensive process of deleting each trip on the Garmin one by one? Who thought that up?
You're confused about memory. If you're getting a message when dealing with routes its referring to inaccessible memory on the device itself, probably as a result of a very complicated and/or long route.
As for deleting data on the device that is due to the way that zumos, nuvis etc work and nothing to do with BaseCamp.
Note too cards must be FAT32 formatted, I suspect your card isn't if its that large.
I have other routes on the card, so I'm assuming that the formatting is correct if the 665 has been able to access those routes before? BC reports that the native storage is nearly full, despite that I've added very little to it. Am I wrong in deducing that the 665 moves the route data from the SD card to the native storage when it imports the route? If so, what good does having a SD card do for routing? The only thing it would be useful for would be music. That would make the 665's usefulness severely limited.
BTW, I would have liked to reply to you in the other thread before you closed it.
Wow, so is the updated 5xx series of motorcycle navigators saddled with the same severe storage limitations? Wish I would have known before I bought this one.
Am I wrong in deducing that the 665 moves the route data from the SD card to the native storage when it imports the route?
Probably, but some information is likely stored on the device (perhaps route title and a pointer to the location on the sd card). In addition, the route may well be loaded on the device when active.
How much memory is available on the device when viewed thru windows as an external drive? (i.e. not thru basecamp)
How many routes are on the device/sd card?
How many trip logs have been saved?
How may total points in the route that gives the memory error? (export the route as gpx and open it with excel)
All devices have limits on the number of routes, waypoints etc. allowed. In addition, there are limits on the maximum number of user points allowed in a route, the number of total points in a track and I suspect the total number of points in a route (this would include the path between user points). These all vary by device. As far as I know, all devices log data to the device memory only - nothing is written to an sd card.
Typically the design of the device will have reserved enough device memory to handle these limits. So, even if you could store 1000 routes on an sd card, the device itself will not have enough reserved memory to store the information needed for retrieval or listing the routes.
Wow, so is the updated 5xx series of motorcycle navigators saddled with the same severe storage limitations? Wish I would have known before I bought this one.
Not sure what you mean by severe storage limitations. You may need a card for future map updates, but no different to cameras, phones etc that require memory cards.
Not sure what you mean by severe storage limitations. You may need a card for future map updates, but no different to cameras, phones etc that require memory cards.
I had about 15 routes imported to the 665, none of them overly long or complicated with a bunch of waypoints (the longest was from IL to TN), and ran out of storage space. That's what I mean by severely restricted storage limits. I would have thought that I could have stored hundreds of routes, not less than 20.
Probably, but some information is likely stored on the device (perhaps route title and a pointer to the location on the sd card). In addition, the route may well be loaded on the device when active.
How much memory is available on the device when viewed thru windows as an external drive? (i.e. not thru basecamp)
How many routes are on the device/sd card?
How many trip logs have been saved?
How may total points in the route that gives the memory error? (export the route as gpx and open it with excel)
All devices have limits on the number of routes, waypoints etc. allowed. In addition, there are limits on the maximum number of user points allowed in a route, the number of total points in a track and I suspect the total number of points in a route (this would include the path between user points). These all vary by device. As far as I know, all devices log data to the device memory only - nothing is written to an sd card.
Typically the design of the device will have reserved enough device memory to handle these limits. So, even if you could store 1000 routes on an sd card, the device itself will not have enough reserved memory to store the information needed for retrieval or listing the routes.
I deleted all but one route and the addresses I had previously loaded on the device and I was left with 168 Mb free on the 3.66 Gb internal storage. I'm not sure how much space each route takes once imported to the 665, but so far experience has shown that I can load less than 20 routes before running out of space.
I know this doesn't answer your issue of the SD card not being used as effectively as it might be but you might be able to free up enough space on the Zumo to make it more useful.
Connect the device to the PC and use your file manager to view the folders on the device. Find the "Text", "Voice", and "Vehicle" folders. They are likely in the Garmin folder.
Delete any languages you are not using from the Text and Voice folders. For the languages you keep make sure you also keep the .sum files, too.
Delete any Vehicle icon files you don't want.
I've done that on one of my Nuvis and it bought me a fair bit of space.
