SiliconFiend

If you want to use the Invisible Shield, you might want to go with a case like this instead. I have one for my Vista HCx and it's nice. They also make them for other models if you want something different (search Amazon for "Foarm"). It comes with two screen protectors that look like they're the same material as the Invisible Shield, but they're small--only the size of the case opening, instead of covering the entire area. If you use the neoprene case that has the plastic window, it will stick to the Invisible Shield. Plus, it's just harder to see through 2 screen protectors.

I noticed it was easy to see in the summer. Now that winter has come (to the northern hemisphere), with overcast skies, it usually requires the backlight on more than you would normally need. It's great in full sun, though, and at night I need only one or two clicks on the backlight (5-10%) to see it clearly.

Yes, but with the GPX file support, that's almost a moot point. If you're that into caching, you'll likely be a premium member and will be using GSAK to manage your GPX files. True, we don't yet know for sure how many caches it will hold, but it's probably more a function of memory than of some artificial limit. For "normal" usage of waypoints (to mark something of interest to you, one point at a time), 1000 is a lot. That depends on where you live. 1,000 unfound waypoints fill a radius of under 20 miles from my home. Not enough for me! I'd really like 10,000. That would get me the whole state of NJ, all of Long Island and NYC, plus some upstate NY and the closest 500 caches in Pennsylvania and leave me with ~2000 open waypoints. This would be ideal for me. But with the new way that the Colorado handles geocaches, I'd be able to accomplish this easily. Right? You're missing my point. As geocachers, we've come to expect geocache=waypoint. But that's not the original purpose of a waypoint (before geocaching), and with the Colorado, that seems to be no longer true (they're treated specially from the GPX files, not just a waypoint with a special icon as with the legacy Garmin implementation). So, given sufficient memory and absent artificial limits, there's no reason you couldn't have your 10k caches. So I reiterate, based on those facts, 1000 "normal" waypoints (actual waypoints, not caches) should be plenty for nearly all users.

Calibrate the compass when you change the batteries or it starts to go wonky.

Yes, but with the GPX file support, that's almost a moot point. If you're that into caching, you'll likely be a premium member and will be using GSAK to manage your GPX files. True, we don't yet know for sure how many caches it will hold, but it's probably more a function of memory than of some artificial limit. For "normal" usage of waypoints (to mark something of interest to you, one point at a time), 1000 is a lot.

Oops, I just saw that you mentioned you had a Vista C, not a Cx or HCx. Well, something to think about if you're considering upgrading.

OK. so I was on the right track (so to speak) in thinking it was change of direction that would trigger a recording, as it seemed to me that recording changes would be the most efficient in terms of points. However, as the reporting has a 2D bearing which often appeared to be the same for successive (and often short) legs, I was thinking my theory didn't fit the data I was seeing. However, it may have been that there was a sufficient change altitude or speed that was causing the recording of the point. That makes sense. It's perhaps worth explaining why I am so interested in how the tracking is being done. We went on a month's holiday recently driving from Brisbane to Perth and back (about 12000 km) and we were using the Garmin to record waypoints and tracks in the hope we could automatically (or at least semi-automatically) geo-locate our photos. Now in the 2 years we've owned the Garmin, we've never had a problem with recording track data. All the track data we've ever recorded was still fitting in the memory, but with the benefit of hindsight, it was a large number of fairly short trips. So we set off to Perth with the tracking on, assuming we'd have a month of track data on our return. Sadly we found we had about 4 days of track data because the Garmin didn't have sufficient memory and was overwriting. So, I'm now very motivated to try to work out the best settings for trackings to make the most efficient use of the memory to avoid this problem in future (I'd rather not have to cart a laptop around just to upload track info). But of course the solution might lie in getting a camera with a builtin GPS (still a bit of an expensive option but probably the preferred option in terms of what we are actually trying to achieve) or getting another GPS with more track memory. Thanks for everyone's thoughts. Kerry If your model has a microSD slot, you can (and should) set it up to record the tracklogs to the card. You'll get one GPX file per day, and they aren't overwritten.

Hello! I found out about this project called OpenStreetMap.org, seems like they have some kind of support to Garmin as well (see wiki.openstreetmap.org). Haven't tried to upload those to my GPSr yet, since it seems to be lacking the maps to my area (so I started creating some tracks there). I don't know how's the coverage in your area, but it doesn't cost anything to try it out, and if you get interested you can participate yourself in creating the maps. Best regards, Timo I'm glad word is getting out about OpenStreetMap (OSM). I've been involved with that project for a few months now. It seems like the best chance of getting wide coverage of detailed trail maps which can be auto-routed. Lack of good trail coverage (free or commercial) has been a point of frustration for me. As you found, there's currently a program (mkgmap) which creates Garmin IMG files from OSM data. My plan is to create auto-routing Garmin maps from OSM data (via cGPSMapper). OpenStreetMap is currently importing US map data from the US Census (over 80% complete). The coverage is good but the accuracy is bad. The streets need to be realigned to reflect reality. I'd encourage cachers to check it out and consider contributing some time to improving the map. In addition to "Cache in, trash out", you could "Cache & Map"

I did my tests just in Demo mode, leaving the GPS receiver on. Auto would use your current satellite fix and would only be available if the GPSr was on. I'm not sure what you mean by your last point, though. With the route method, I created a route with two waypoints (which would be your two caches in this case). Then I used Demo mode and the map to tell it I was nearby the first waypoint. Then I went to the route I created and selected Navigate. I was trying to test routing (and I presume you are as well), so I chose Follow Road. Hope this helps.

Go to Demo Mode, then go to the Satellite screen, press the Menu button, tell it New Location, and Use Map. Then you can pick the location where you want to position yourself to start navigating. I'm trying that, but it's not particularly user-friendly. My route goes between two geocaches. I'm trying to find one of them on the map, but unfortunately I have two problems: (1) there are a ton of geocaches here, so it's not easy to find the one I randomly picked as the starting location just by panning and zooming, and (2) unlike the regular map, the one that is displayed for setting the new location doesn't show the lat/long of the cursor when you're panning around. Well, you could select a spot that's near the start point, then create a route between the two waypoints that you want to navigate between. When you select Navigate on that route, it should navigate you from your current location to the first point, then navigate to the next point, which is the part you care about.

Go to Demo Mode, then go to the Satellite screen, press the Menu button, tell it New Location, and Use Map. Then you can pick the location where you want to position yourself to start navigating.

I think you're confused. The version 2.5 you're referring to (and which has been discussed in other threads) is a GPS chipset firmware update, which is certainly software.

Did you read the post I made further up with the Garmin specs? GPS may be inaccurate for distance / odometer, however, they are very accurate for velocity. Yes, its true that co-ordinate position is generally only good to 3m (10ft) and yes its also true that GPS calculates velocity by calculating the time between 2 co-ordinates. However, as I understand it, whilst the GPS points are inaccurate, the error in the co-ordinate position is very repeatable. This why GPSs are so good at measuring velocity. It doesn't matter that the GPS is 3m (10ft) off in its co-ordinates as long as the next point is off by the same amount in the same direction. This is how Garmin are able to claim 0.18km/h (0.11mph) speed accuracy. No, GPS calculates velocity from doppler shift, not from the difference between two points. If you don't believe me, I posted a few months ago with links providing evidence for this.

You'll have to decide if that's really important to you. The Vista HCx has great reception--hard to see a need for an external antenna. This is true, but it's also quite a bit dimmer, due to the fluorescent backlight instead of the HCx's LED backlight. Also the HCx has a slight edge in resolution. You're the first person I've heard say that (and I've read a lot of comparisons). If you're talking about the older model of Vistas (C or Cx), I can see that, but the HCx is plenty quick. Oh, brother... Making up for some "shortcomings", are we?

Source? Are you saying that one could not load a GPX file from GSAK (in which, for instance, I combine various PQs, use corrected coordinates, etc.)? If so, that's a dealbreaker. Even if it does require a new format (probably not), you can bet the software tool authors will support that new format quickly. It shouldn't be a "dealbreaker" for you. I wonder if testing for the Colorados had anything to do with the sporadic "send to GPS" problems on geocaching.com recently... Kinda stupid to do testing like that on your production site, though.

I can't say I'm surprised, but it does suck. From what I've heard, the most common problem with radar is misidentification (pulling over the wrong car for speeding). The GPS evidence would seem to provide at least reasonable doubt that the car was correctly identified as the speeder. I commute through that area, and my wife just got a speeding ticket there on Monday (grumble punk motorcycle cop ). I had my GPS with us, but obviously it wouldn't have helped (she actually was speeding but just for an instant).

There may be something wrong with your unit. If it were integer hours off, it would likely be a timezone thing, but it doesn't sound like it. If there's one thing that GPS receivers know, it's the correct time. The satellites tell the receivers what time it is so that the receivers can use triangulation to know where they're at. I'd suggest putting it in clear view of satellites for a half hour or so and see if it sorts itself out.

Search this forum for the solution. It's a GSAK setting that has to be changed. Thanks for the suggestion, but GSAK is set to send 14 characters. GSAK sends all 14 to my 76CSx but only 10 to the vista HCx (same settings in GSAK). Or that might be better worded that the Vista HCx seems to truncate it at 10 even if more characters are sent. It has me stumped!! Here's the post: http://forums.Groundspeak.com/GC/index.php...=175943&hl= I guess it's really a GPBabel setting, not a GSAK setting, but they're related. Sorry, I'm not a GSAK user (I have a toddler; not enough time to do caching to need special tools).

I don't think that applies to the track log, only the odometer. I get a cluster of track log points even when I'm sitting still. However, it's possible it could affect the frequency of logging based on the auto->least/less/more/most setting.

Search this forum for the solution. It's a GSAK setting that has to be changed.

I seen a post back in April on aother site where this case was made in black. Are there color choices for this case or the standard "Artic White" that I see on Amazon? I got a Foarm case for Christmas for my Vista HCx. I'm planning to write up a full review with pictures, but in short, I like it. Apparently it only comes in white, though, which is unfortunate. I like the black look better.

The backlight used to come on initially when you first powered up the unit. Seems like a weird reason for churning a firmware revision, but I'm sure there's some good engineering reason behind it (I hope for their sake, anyway!). I wish it would preserve the backlight setting between power cycles, too, without having to click the power button twice to get it back to my "user" setting.

The panhandlers must be sharing tips. I saw a variation on that sign at the 49ers game yesterday.

I've experienced this with my Vista Cx also. I believe the difference is this: If you are currently 'navigating' to a to a cache or other destination, and use the arrow to highlight another cache, it will attempt to grab that cache and move it. If you are not currently navigating to anything, and use the arrow to highlight a cache, it will give you the information for that cache the opportunity to 'go to' it. If I've got this wrong, I'm sure somebody will clarify. Check my post #16 above.

If you have no maps enabled, then it's using the basemap resolution, which is horrible and that's why the circle is so large (because the poor map quantization means it can't display your location on the map you any more precisely than "somewhere within the circle"). When you have routable maps installed, the circle radius pretty much matches your reported accuracy.