Colorado 300

[+oikumene]

I have installed maps on my Colorado and have three sets. I would like to delete one set of maps but do not know how.

 

2) It seems that Colorado does not start a new track log after switching off and on the GPS. THe GPSMap60CSx always creates a new log after switching on the GPS.

[+Crid]

I agree with #2 being annoying. I use my GPS for mapping and the 76CSx started a new track when I turned tracking off and back on. The Colorado seems to put it all under a single track.

 

On the plus side, I gather that when you save a track the Colorado keeps all of the data, rather than stripping off the timecodes like the 76 does.

[gallet]

I have installed maps on my Colorado and have three sets. I would like to delete one set of maps but do not know how.

 

 

I suppose you mean three different maps in a single file. There can be one file on the internal memory and one on the SD card. When you plug your Co into the PC usb both drives will mount, or just 'Garmin' will mount if there's no SD card. You will need to resend a new map file but you don't really need to delete the old maps because the new file will overwrite it.

 

The file it produces is called gmapsupp.img

[bmirak]

You need to use Mapsource to manage the maps on your device.

 

In Mapsource, you must select all the different map segments you want to upload (let's say you want some from City Navigator and some from U.S. Topo.) When you are ready to upload, Mapsource bundles all these segments into one map file and sends it the device. This new file overwrites the exisitng map file on the device.

 

So, if you've got three maps on your device and you only want two, just upload the two you want using Mapsource and the third will be gone.

[+g-o-cashers]

The CO is a little funny about how/when it creates separate track logs. When you turn the Colorado off with an active destination when you turn it back on it remembers that. I've noticed under these circumstances that the Colorado will continue the same track rather than breaking it. The work around is to cancel navigation before shutting off or cancel it before the unit get satellite lock on the way back up (this is difficult sometimes if the unit is doing a warm start).

 

This doesn't entirely fix the issue however. I still see that sometimes the Colorado doesn't split tracks but I'm not sure what causes it.

 

GO$Rs

[swobrien]

The CO is a little funny about how/when it creates separate track logs. When you turn the Colorado off with an active destination when you turn it back on it remembers that. I've noticed under these circumstances that the Colorado will continue the same track rather than breaking it. The work around is to cancel navigation before shutting off or cancel it before the unit get satellite lock on the way back up (this is difficult sometimes if the unit is doing a warm start).

 

This doesn't entirely fix the issue however. I still see that sometimes the Colorado doesn't split tracks but I'm not sure what causes it.

 

GO$Rs

 

My first post I think after months of looking before buying and then keeping updated after my purchase. Thanks to everyone for all the useful info so far.

 

I have the 400t, but I think I also see some strange behavior with tracks and was wondering if it is related to this.

 

My problem is that the auto archiving of tracks never seems to work properly. For example, if I am tracking points every second, then I reach 10,000 after a few hours and it starts cycling through the log again, but not always archiving first. Is it possible that it only archives complete tracks? So, if I have switched off and on, but a new segment is not created, will it will not archive?

 

To be honest I have not been able to find the exact pattern here, as I live in New York City and don't always get a signal in my apt for testing my theories and each possible test takes hours. When out and about, I normally need my tracks (for photos) so I manually archive, but it is a pain to always remember.

 

Could it be related and has anyone seen a similar issue?

 

Apart from this, I love my little machine. I'm still on 2.4 software which I upgraded to after hearng about it on here. Not gone above yet, as no fix mentioned to this, my only issue of concern.

[+g-o-cashers]

This is probably a bug. When you have the tracklog in auto mode it doesn't generate nearly as much data (you would have to change batteries before the tracklog wrapped) so most people would never notice the issue. I believe the tracklog archive probably happens at boot time not at runtime which means if you overflow the tracklog before the next boot cycle you could lose some of your track data.

 

GO$Rs

[swobrien]

Thanks for the fast response. My other workaround was to only log every 5 or 6 seconds for a similar reason, that way I never fill up in one day and can make sure I archive at the end of the day. I think when I manually archive, it does not bother to auto archive, so I can't even perform an auto for safety and then see the results of the manual. Again, I have not really been able to confirm this yet.

 

I have not used auto mode for the capturing of tracks, so maybe I should look into this and see how it works, as it sounds like a good option and will probably save me some effort of switching the method based on what I am doing that day. What is the method for auto as I don't want to find that I have moved half a mile and there is no point logged?

 

Thanks again.

[+Red90]

Just use the auto mode for tracks set at "most often". It is quite well designed and you won't lose any accuracy.

[swobrien]

Just use the auto mode for tracks set at "most often". It is quite well designed and you won't lose any accuracy.

 

After testing loads of scenarios, the auto archiving appears to be fixed in the latest firmware, V2.54

 

It now auto archives all tracks, even if it is running constantly beyond the 10,000 limit. It seems to archive every 9800 points for me.

 

Very happy to now not worry about this and having to keep backing them up every night if on long hikes.