Vibramhead

I completely agree. I've used TopoFusion for several years, and just bought a 62s and started tinkering with custom maps. TopoFusion is by far the easiest means of making a custom map. It automatically georeferences it, and gives you a choice of many different map layers, e.g., aerial photos, open streetmap, landownership, USGS topos, MyTopo, etc. TF also does a nice job of matching up your photos with GPS tracks on a map, even if your photos don't include location data.

I already own the Garmin Topo US 2008 DVD, for my 60Cx, and I'm thinking of buying the Garmin 62s and loading topos onto it. Is there any reason to pay more and buy the 62st? Are the topos on the 62st any better than Topo US 2008? Thanks for any input.

Here's a neat little new site called GPSfly. You upload a gpx or kml track file to it, and it takes you flying along it in a Google Earth window in your browser. The site's pretty new, and needs better organization, but it's an easy way to share your hikes with friends. At this point, it doesn't appear to allow downloading of other folks' gpx files, but they're apparently planning on upgrading it.

The device you're thinking of is the Spot Messenger. It costs $150, plus a $100/yr subscription fee. For an extra $50/yr, it has a tracking function that sends a location signal every 10 minutes that appears on a website. I have one and used it recently on a hike around Mt Rainier. It worked pretty well, except in heavy tree cover.

My relatively new 60Cx odometer usually understates the mileage by 10% or so, although sometimes it overstates it. This seems to occur mostly on forested hikes. The odd thing is that, when I download the track to my computer, the track mileage is accurate. I had the same experience with my old 60CSx.

Here's a set of free Oregon 24K Garmin-compatible maps you can download: http://www.aracnet.com/~seagull/ORTopo/index.html. They only cover the Portland metro area and part of the north coast, but they'll give you an idea of whether the added contour resolution is worth it. I've tried them, and have generally found that the 100K resolution of US Topo is adequate for hiking, and makes for a less cluttered screen.

You might want to look specifically at the new Sanyo 2700 MAh, model HR-3U. They use some kind of proprietary chemistry that is supposed to substantially reduce drain while inactive. I've been using them in my 60csx for a couple of months, and consistently get 18-20 hours per charge, even when I haven't charged them recently. I got mine from Thomas Distributing: http://www.thomas-distributing.com/index.htm.

I got Garmin to send me their 3.0 "beta" firmware a couple of weeks ago, and I've done a couple of test hikes and walks around town. So far, it looks like the odometer & track log are matching up more closely: the difference seems to range from 1% to 3%. These hikes have been 4 to 8 miles. If this holds for longer hikes, I'll say the problem is fixed.

I am not sure what you are talking about. I have tracks saved to the microSD card and can access them with my GPSr. I don't understand this either. I saved 2 tracks yesterday to my card and I can still delete them without going into USB mass storage mode. I don't know about deleting them, but I can't read them off the card with the GPSr. Garmin apparently confirms this: Thank You for contacting Garmin International! I am happy to help you with this. The data card acts as a mass storage device when you load the latest version of the software. Those files should be accessed from your computer looking for the drive that is the storage device. When this is called up you should see the files for the track logs. There is a file on this drive that allows you to see the tracks in mapsource. These tracks that are stored on the data card are not accesable by the GPS as tracks. If you have any additional comments or questions, please do not hesitate to contact us via email or at the number listed below. Best Regards, Bob Betlach Product Support Specialist Garmin International

I believe someone posted that if you enable saving your track to the microSD card that doesn't happen. Feel free to test and report back. I haven't tested this with my old CS, but did the CS have this issue as well, the discrepancy between the track log distance and the trip computer distance? The bizarre thing about saving the track to the microSD card is that you can't use the GPSr to read a track stored there. You can only download a track from the card to a PC. Consequently, you can't determine when you're out on the trail how long a track on the microSD card is. Here's what Garmin tech support said: Thank You for contacting Garmin International! You may have noticed that the latest firmware updates to our X-series units have added USB Mass Storage support. I have some tips as to what this means and how it may be useful: *To clarify, this does not allow you to access the internal memory of the GPS unit. This will allow you to access the Micro SD card on the unit as a drive on the PC. To activate Mass Storage mode (with the latest firmware version installed on the unit): 1. Go to the Main Menu 2. Select Setup 3. Select Interface 4. There will be a button on the bottom of the screen labeled USB Mass Storage - highlight this and press enter. 5. If the unit is already plugged into the computer, you will be in Mass Storage Mode - If not, plug the unit into the computer at this point. 6. To remove the unit from the computer after you are done, you will want to find the Safely Remove Hardware icon in the System Tray of Windows (Bottom-right corner, near the time), click on the icon, and choose Safely Remove USB Mass Storage Device - Drive(X:). What you can do with this feature: 1. You can check the format (File System) of the data card in the unit. a. Open My Computer, right-click on the drive assigned to the unit in Mass Storage Mode and choose properties. b. The File System will be listed towards the top of this window *note: our units work best with FAT File System - if it says FAT32 here, you will want to re-format the card. 2. You can re-format the card. a. Open My Computer, right-click on the drive assigned to the unit in Mass Storage Mode and choose format.... b. In the Format window, you will want to use the drop-down menu to choose the File System to FAT (not FAT32). c. Click Start to format the card. 3. You can retrieve tracklogs you have saved to the data card. a. The ability to save an active track to the data card was added during the last firmware update. (Tracks > Setup > Data Card Setup) b. If you have a saved track log, you can open My Computer and double click on the drive assigned to the unit in Mass Storage Mode. c. This will open a window allowing you to view the contents of the card - you should see any supplemental maps, saved track logs, and any other files that may be on the data card

Mine doesn't do this, and it's updated to 2.90/2/60.

I've been using the 60csx for 6 months, mostly for hikes in the woods, and I've consistently had the same problem. The trip odometer always reads less than the actual distance walked, as measured by the track log. I've tested this on measured trails (i.e., ones marked every quarter mile) and the odometer is always short, while the track log is usually right on target. I've complained to Garmin about this several times, with no result so far. On the phone, tech support have been clueless, and via email, they haven't even bothered responding. At least you got some kind of explanation, though I agree a thoroughly unsatisfactory one. I've found that the only way to figure out how far I've walked, prior to getting home and downloading the track, is to save the track log onto the GPSr, which will then give you a track length. One problem with this is that if your track log is more than 500 points, the save function will strip out some of the points, which will effectly straighten some of the turns, shortening it a bit. So, a 30-mile walk became a 28-mile track after saving. As long as you don't delete the active log, you can at least get an accurate mileage once you get home. On the other hand, I haven't had this problem when paddling on open water. It's not clear to me whether this is because I'm generally moving in a relatively straight line, or because I always have a clear view of the sky when I'm on the water. I've also tested it a couple of times in a car, and the trip computer seems pretty accurate there. But I didn't buy this unit for driving; I bought it for hiking. So, I'm not very satisfied.

I agree with you on tech support. They've seemed clueless the two times I've called them with problems with my 60CSx, and they've failed to respond at all to a couple of emails. I have to wonder whether Garmin being based in Kansas has something to do with it. Kansas isn't exactly known for its hiking opportunities, so how much time does a Kansas-based tech support person actually spend outdoors using something like the 60CSx?

If I were you, I wouldn't trade up. I've had the 60Csx for 6 months now, and have decided I'd prefer the 60Cx. The barometric altimeter on the Csx generally gives a less accurate reading than the "GPS elevation" that the Cx uses. It's been as much as 300 feet off. As for the compass, I have to recalibrate it every time I turn the unit on, which is annoying. I don't really need a compass for my use, which is hiking, but if I did, I'd just use a cheap magnetic pocket compass instead.. Another problem with the 60Csx is that the odometer is chronically inaccurate for hikes on forest trails. It generally reads 10 to 40 percent less than the actual mileage. It doesn't seem to have this problem when I'm in areas open to the sky, like when I'm paddling my kayak on rivers. I can't say whether the 60Cx would be any better; I suspect it's a problem with any unit using the SiRF chip.

I've had the 60CSx for 6 months, and I've had several problems with it. I use it for hiking, not geocaching. The main problem is that the odometer is chronically inaccurate; it always indicates less than the actual mileage walked. The error ranges from 5% to 25%. What's odd is that the recorded tracks are accurate, i.e., I'll take a 10-mile hike, the odometer will read 8 miles, but when I download the track into Mapsource or another program, the track length will be 10 miles. I've also tested it against measured courses, and it always comes up short. It seems to be more accurate in open country, or on the road, than on the winding, forested trails where I usually go. Then there are the screwy altimeter readings: sudden jumps to 10K or drops to -500. Even without the odd jumps, the altimeter just isn't accurate; the GPS elevation reading is almost always closer to the actual elevation, while the barometric reading can be off by 300 ft. Then there's the compass requiring constant recalibration. I don't really need a compass, but if I did, it'd be easier to just pull out my trusty $20 Silva, which I carry anyway, because nobody should rely on an electronic device as the sole navigation aid in the wilderness. I'm surprised that others have raved about Garmin's tech support. The 2 times I've spoken with them, they've seemed clueless. And they haven't even bothered to respond to several emails. So, I've finally asked them to send me a replacement, and to make it a 60Cx, rather than the CSx. In its favor, I will say that it almost always gets and keeps a reliable location fix, even in heavy tree cover, which is where I do most of my hiking. In this way, it's far superior to the Legend I used to have, which was useless for forest hikes.

I've had this happen with my 60csx a few times. The only way to get the elevation to register again is to turn the unit off and on again. Then there's the elevation recorded in the track suddenly jumping several thousand feet. I've emailed Garmin tech support about these issues twice, once a month ago and once 2 weeks ago, and they have yet to reply. So far, I can't say I'm very impressed with Garmin support. Another bug I've emailed Garmin about, with no reply, is the tendency of the trip odometer to register about 5 to 10 percent less distance than is shown on the track line when downloaded. Doesn't inspire much confidence in the unit's ability to give you an accurate reading of how far you've gone. The unit does, however, reliably keep a solid location lock, even under tree cover, and that's its saving grace.

I agree. I have the csx, and the altimeter isn't worth the trouble of regular recalibration. When I step out my door, at 500 ft, the csx barometric altimeter typically reads 100 to 150 feet too high. The gps elevation (to which you have the option of calibrating it) is always more accurate, usually within 20 ft. It'd be nice if Garmin offered the option of turning off the barometric altimeter and just getting the gps elevation, but they don't. actually, there is such a feature on the CSX. On the satellite page hit MENU then select GPS elevation. Thanks!

I agree. I have the csx, and the altimeter isn't worth the trouble of regular recalibration. When I step out my door, at 500 ft, the csx barometric altimeter typically reads 100 to 150 feet too high. The gps elevation (to which you have the option of calibrating it) is always more accurate, usually within 20 ft. It'd be nice if Garmin offered the option of turning off the barometric altimeter and just getting the gps elevation, but they don't.

I've had the 60csx for about 6 weeks now. Its reception is much better than my old Legend. The Legend often couldn't get a lock in moderate tree cover, but the csx always gets and keeps a lock no matter what the cover. (I'm in the Pacific Northwest, so we have lots of big trees.) In fact, I can carry the csx in my jacket pocket, zipped up, and it still keeps a lock just fine. This alone made it worth the price. The Legend was basically useless for forest hikes. But I do have a few complaints. First, the trip odometer seems to under-report the mileage by 5 to 8 percent. I just took a 24 mile walk today, and the odometer read 21.9. I know it was a 24 mile walk, because when I downloaded the track into Mapsource, the "track properties" said 24 miles. I also clocked the GPS against a measured mile at one point, and it was about 8 percent short. It's done this several times. I emailed Garmin about this 3 weeks ago, but got no response. Also, the barometric altimeter is not very reliable. Sometimes, it just shuts down (stops displaying any elevation), and will only restart by turning the unit off and on again. Also, sometimes, it records elevations that are way off, e.g., sudden jumps of 9000 feet, or sudden drops to 1000 feet below sea level. Other users have reported this. And again, Garmin tech support hasn't responded to my email about this. I think the GPS elevation is actually more reliably accurate than the barometric elevation, especially since the csx usually has a lock on at least 7 sats, so I think I'd be happier with the 60Cx, and would have saved $50.

You can get one, if you're willing to spring $600. It's called a personal locator beacon (PLB), and it will transmit a location signal based on a GPS fix. The frequency is monitored by rescue folks around the world. For emergencies only, of course. Check here for the REI page: http://rei.com/online/store/ProductDisplay...ory_rn=40002203 And here for a review: http://www.equipped.org/406_beacon_test2_toc.htm And of course, I agree that NOBODY CAN TRACK YOU WITH YOUR STANDARD GPSr, any more than they can track you when you're using the FM radio in your car. That's just stupid.

I have a similar problem with my 60csx: I take a hike, then download the track when I get home. It shows the correct elevation for much of the hike, but then inexplicably jumps 9000 feet, or drops way below sea level. Another odd thing that shows up in the trackline, coinciding with the elevation jumps, is that the frequency of trackpoint recording suddenly goes from 1 every 8-10 seconds to 1 per second. This is when I have the recording frequency set to "more often." Another problem I've had is the altimeter just shutting down completely while in use. The only way to get it to work is to turn the unit off, then on.

I have a 60csx, but I think I'd get a 60cx if I had it to do over again, because the barometric altimeter & compass aren't that useful. The altimeter is downright unreliable; it sometimes shuts down completely, or gives crazy readings. Perhaps Garmin will come up with a firmware fix. On the other hand, I like the big color screen, and the Sirf chip reception is amazing. It does great in heavy tree cover. Tall buildings (i.e., anything over about 4 stories) seem to throw off the accuracy quite a bit, though. But I didn't buy it for urban use, really. Anyway, as another poster said, any of the x models will have Sirf, so the Vista cx should have similar sensitivity, and it would have the advantage of being more compact.

I have the same problem with my 60csx. It seems like I have to calibrate it every time I start it. If I don't, the heading will be off by a good 10 or 20 degrees. In fact, I don't even bother with the compass now. I might as well have bought the 60Cx

I have a 512MB card in my 60csx and it works fine, so far.

Thanks. I've emailed them about this and am awaiting a reply. I'll post it here when I get it.