apersson850

From a geocaching point of view, the new Colorado has significantly more to offer than the 60 CSx.

If you mean the ability to define a new waypoint, on the Colorado itself, by specifying the coordinates, then that has been possible since the beginning.

I thought along the same line. If I have a weekend on my own, while working in the US, I may want to try some local caches. Then I go home, do some more, and then upload the log file to Groundspeak. At that time, I have caches found (hopefully) in different time zones, so to log them with times that are meaningful to other people, who look at the logs, or looked for the cache on the same day, the local times has to be applied.

I've actually been at a cache, where the clue included the elevation of the cache. Which was prudent, as it was placed very close to an almost vertical incline, so both the summit and foot of the incline was within the inaccuracy of the GPS. Without the elevation figure, it would be impossible to say if you should look around at the bottom or the top - or walk on the wall like a fly, looking mid way!

I bet. Round and nice. Good for chewing on. I've tried caching with the Colorado twice now, once with 2.30 and once with 2.40. The interface has improved significantly, but as others say, there are still unnecessary limitations. Like that on the Colorado, it's impossible to build a route which passes through a couple of geocaches. The route manager can search for everything else, but not geocaches! To make this happen, you either have to think about this at home, and build the route in Mapsource, or you have to pan around the map, hover on each cache, mark as a waypoint as well, then return to the route manager and make the route through these waypoints instead. Doable, but meaningless maneouvers to accomplish something that should have been a no-brainer.

Learn the elevation of your home turf. Often you start off from there, don't you?

There's a default time zone setting in your geocaching member profile as well. But as you may be caching elsewhere than in your home time zone, using the time zone setting that was current in the GPS, when the cache was logged, seems to be the smartest thing. Which means this can't be done at the web site, unless the Colorado stores the time zone setting as well. I've been so trigger happy, that I've logged the same day as I found the caches. Hence, I've not seen if it's using another date than the one logged in the file.

Did you have the magnetic compass enabled? You don't have to delete the found cache list file, if you don't want to, as the web site will keep track of which are new. But if you want to, I see no more convenient way than doing it with the computer connected. If it wasn't a joke, but you actually are afraid that you'll delete something else, then I don't really know what to say... Save the beer until you are ready, maybe??

I've never seen any hard facts, but it's "known" that the old style receivers, like what you have in a GPSmap 60CS, uses around 20000 correlators, while the SiRFstar III and similar use about 200000 correlators. That's what makes them able to track in much worse situations. As a general rule, older units didn't wander that much, because at these conditions, where modern GPS units do seem to ramble around, the old ones simply said "Lost satellite reception".

They have some settings, where you can select different units for distance and elevation, but as speed is distance over time, I don't think anyone at Garmin anticipated that anyone using km for distance wouldn't also use km/h for speed.

Yes, that must be it. Had it been a 400, it would have been worse, since then it could have been some of the pre-installed maps.

That wouldn't be difficult to find out, as they are simple gpx files. Can be read with any text editor.

It seems reasonable that the caches disappear if you remove the GPX file. Otherwise we would need a separate "Delete caches" command, when they've been pre-processed and stored in some internal database. When first making a route, then looking up a cache, does it not then provide a route (straight line, but still a route) to that cache on the overview map? Which then explains why the original route disappeared. You replaced it with a new one, even if that wasn't your intention, just something that happens then.

"Naval Colors" can be selected from the setup menu.

As far as I understand, the Colorado can show cadence and/or heart rate in a data field. Period. But I don't have any suitable such sensor, as I have the older style Forerunner 301. The sensor supplied with a Forerunner 305 is compatible with the Colorado, but that doesn't help me.

I have once seen a brief "Battery low" warning, which immediately went away. Only once.

You may find the total cost of buying a Colorado 400 (or 300 + Topo maps on DVD) + City Navigator on DVD to be higher than the Colorado with Topo + a small nüvi with the City Navigator maps pre-loaded. You'll not get the CN maps in your computer that way, but you get a better car navigator than the Colorado. You can exchange the Colorado for a 60 CSx i the paragraph above; it still has the same validity.

I haven't checked autozoom with off-road routes good enough to have any opinion about that. I've been out driving with the Colorado, v 2.40, and autozoom does work when following that kind of routes, and also when not following any route at all. I'll see what happens to me when following an off-road route as well.

Makes two of us. In this particular case, I've had quite a detailed discussion with a technician at Garmin about this problem, so I know a bit more than most of you about it. That's why I'm counteracting at least some of the large amount of misinformation that's floating around here. I tried yesterday evening to set an alarm in the morning. I kept air pressure logging off, so not to have the possible effect of that to make things different. Then I waited for the alarm in the morning. I had it set so it should go off five minutes after my regular alarm clock, as not to miss it. It turned out that 19 minutes after the set time, the alarm triggered. Looking at the clock in the Colorado, it was then 19 (no wonder) minutes behind. I selected the "snooze" option, which advances the alarm time by ten minutes. Ten minutes later, nothing was heard from the Colorado. Checking again, it turned out that it had received enough satellites to compute a position, and thus also advanced the time by the missing 19 minutes. As the snooze was ten minutes away, and when the position was established probably even less, the clock just passed by that time, without triggering the alarm.

If you don't think it's wrong, then you are wrong. These GPS units for sure use the time they can calculate from the satellite information, once a position has been established. This is all included in the PVT calculations (Position - Velocity - Time). However, to facilitate quick startup, they also keep an ordinary quartz-controlled clock running when powered down. This clock is powered by the normal batteries in your GPS. If you remove them, the clock is powered by a backup energy source. In the case of the Colorado, this is a so called supercap. There is no doubt whatsoever that the Colorado should be able to display the correct time and date, when you turn it on, even if you don't have any position calculated yet. The difference between the 60 CS and the 60 CSx is not that the clock isn't running when the later is off, it's that the clock chip used can't issue the proper interrupt required to make the GPS power itself on, after a certain interval.

Well, my guess here is that the barometric plot is updated every 15 minutes. There's a chip inside that actually does keep track of the time. That chip initiates a wake-up, when it's time to record the pressure. At each such occasion, no pressure is actually recorded (on my unit, at least), but the Colorado's idea of the current time is advanced by 15 minutes. Not recording is a bug, of course, but turning on four times per hour would then imply that the clock isn't more off than that. I'll have to try the GPS off/on trick as well.

I tired this feature yesterday. It worked perfectly. I would have liked it to enter the time found as well, though. Into the web site log, I mean. But the time zone fuzz may make that more difficult than one could expect.

http://forums.Groundspeak.com/GC/index.php?showtopic=185887

But only for that single occasion, right? The next time you have the same problem back, don't you?

I've reported that map selections aren't retained in profiles. If the clock isn't running, having a complete almanac is of limited use. I tired the automatic cache logging yesterday. It works.