Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by jmundinger

  1. I'm curious whether there is information at Delta's website that specifically says that it is permissible to use a GPSr while in flight. The last time I flew (Northwest), I didn't see any specific reference to a GPSr and concluded that it was in the category of "all other electronic devices" that were prohibited to use.
  2. If you are on a commercial flight, are you sure that it is lawful to turn the GPSr on after the cabin door has closed?
  3. In those applications, I agree with those who suggest that it doesn't matter. true v. magnetic north is relevant if you are doing something related to orienteering and using the gps in conjunction with a map and a compass. Even in those applications, I think it is still a matter of personal preference. But, in either case, if you are going to use the gps for that kind of application, you should understand the concept of declination and know the declination angle for the area in which you are working - which you can get from either a topo map or from the gps.
  4. One suggestion - go to the garmin website and download the pdf file for the user's manual for the VistaC - it is an older version of the HCx. That manual has a more complete explanation of the various functions.
  5. Open the file that you want to save in MapSource and then view it in GE. You then have the option to save that file in GE.
  6. Thanks for the explanation. I haven't tried it, but I don't think the Vista HCx has the option of doing what you just described, i.e. averaging the waypoint after the waypoint has been created - I think the average function only works when the waypoint is first created and before it is saved, and, thus, my confusion. It sounds as though the PN-20 has that capability. Oooops. I just learned something new about my GPSr - it does have the capability of averaging a waypoint after the waypoint has been created - it's a function on the menu for the waypoint.
  7. I'm missing something here. Just how do you go about "fine tuning" a waypoint after it is created? What is the sequence? My basic approach, when hiding a cache, is to create one averaged waypoint at the cache site, walk a few feet away from the hiding spot, return and create a second averaged waypoint. Time permitting, I might do a third. Then, I plot all three in USAPhotoMaps and pick the waypoint that looks to be the best.
  8. Change the set up on your compass page from a "course pointer" to a "bearing pointer"
  9. The owner's manual for my Vista HCx says that I can expect less than 10 meter accuracy 95% of the time and less than 3 meter accuracy 95% of the time when WAAS is enabled. But, the accuracy information also includes a footnote that indicates that the accuracy can degrade when the Department of Defense has activated its selective availability system. Also, remember that when you are looking for a cache, your are dealing with the error in your unit as well as the error of the unit of the person who hid the cache. My suggestion would be to search for a couple of benchmarks - the coordinates for those should have a smaller margin of error than the average cache. I am not familiar with the emap. But, if you are consistently within 15 feet, that's probably all that you can reasonably expect from a consumer grade gpsr.
  10. MapSource allows you to transfer data back and forth between your computer and your GPS. If you have GoogleEarth loaded on your computer, you can also view data displayed in MapSource in GoogleEarth. Under most situations it is helpful to have basic map information about the location of the cache - which you can view from the description of the cache. You don't really need the map to locate caches once your search actually begins.
  11. I tried mine on a short hike to a chache this afternoon. It was uphill the whole way from the parking spot to the cache and I intentionally walked slowly during portions of the hike just to check the Trip Computer. I noticed that it was recording down to 0.4 mph. I didn't try walking any slower than that. When I stopped it went to zero but immediately started recording my speed again as soon as I started walking (something it did not always do before the chipset update). It appears that the odometer is now registering just a bit high. Here is the hike, as registered by the trip computer and the track log.
  12. Topo (MapSource) has the option of viewing in GoogleEarth. Set the route in Topo and then select "view in GoogleEarth" from the View menu. This routine requires that you also have GoogleEarth installed on your computer.
  13. I have not had a chance yet to take the unit on a long walk. But, my initial impression is that the trip computer is more functional than it was prior to the update. Two things I noticed immediately is 1) that the odometer registers slow speeds and 2) that the odometer no longer hangs up on 0 while the unit is moving, i.e. it might drop to 0 while moving slowly but, if moving, it quickly returns to registering the speed.
  14. I sent Garmin an email with a request for the software. I received a polite response, including a copy of the update and a request to provide Garmin with feedback on whether the update to the chipset corrects the trip computer issue. I had a couple of issues getting the software installed because I am not that computer literate. The attachment was a compressed file which, when unzipped, included the current version of the UpDater and a .rgn file. When I tried to run UpDater, I got an error message which I finally figured out meant that I had to run UpDater from the C:\ prompt. I wasn't sure how to do that. But, after looking at the Command Prompt screen, I moved the UpDater and the .rgn file to the folder referenced on the screen and then typed in UpDater space and the name of the .rgn file and UpDater opened up and, from there, I just had to follow instructions on the screen. My GPSr hung up on "transferring data" after UpDater indicated that the operation had been successful but, when I rebooted it, things seemed to be normal. Now, I will have to test the unit on a few walks.
  15. It just removes/reinstalls the system software. It doesn't change any of your settings and it does not affect any data (waypoints etc.) that you have stored in the unit. It won't disturb stored maps and you don't have to remove your microSD.
  16. Have you tried either re-installing the software or installing the current update (2.5)?
  17. I'd be more inclined to trust the gps than your vehicle's speedometer. I have an eTrex, a Legend C and a Vista HCX. The discrepancy between the speedomoter and the GPSr, at highway speed, varies between vehicles, but is pretty much the same, regardless of which unit I have in the vehicle.
  18. It isn't, unless you prefer caches involve a bit of a hike to locate. In my case, caching is not the primary reason that I own a GPS or the reason why I purchased one with the capability of the Vista HCX.
  19. 1 - Approx. Date Of Purchase? July 24, 2007 2 - Purchase Location? Offroute 3 - Unit Software Version? 2.40 4 - GPS SW Version? 2.30 5 - Unit ID? 3348872*** 6 - Have you updated the firmware yourself? Yes 7 - Have you noticed the Trip Computer bug firsthand? Yes 8 - Does your typical usage depend on the Trip Computer function? Yes 9 - Have you contacted Garmin about the issue? Yes
  20. Thanks for sharing that. If that is the case, then my rationale for claiming a defect in the earlier versions (relative to the later versions) would not apply.
  21. Shunra - thanks for your reply. Your post described the problem that many of us have experienced with the trip computer. It also includes a problem with the odometer - on of the functions on the trip computer page - because when the unit is not registering the rate of travel, it also is not registering distance traveled (although it is still noting the change in your location on the track log). To find the version of the software that you are running, go to the main menu and select setup. On the setup menu, select system. On that page, push the menu button (lower button on the left side as you are looking at the unit). On the popup menu, use the rocker key to scroll down to Software Version and then push enter. The next popup will display the Software Version (should read 2.40) and the GPS SW Version. If you have the older model, that number will probably be 2.30. If you have the newer version, that number will be 2.40. If you have GPS SW Version 2.40, it suggests that the trip computer issue has not been resolved with the new chipset. By the way, if the numbers that you have differ from those (lower), it means you have an older model and have not updated the software to the current version - which you can do by running WebUpdater.
  22. I'd be very curious to know from those who have the Vista HCX with the newer chipset, whether the trip computer (speedometer and odometer) function correctly on those units.
  23. If we were talking about just a software issue, I'd agree with you. However, if it took a hardware issue to correct the problem - a problem that prevents the unit from performing as described in the operating manual that came with the device - I think Garmin would be on shakier ground. That would especially be the case if the correction were made while existing units were still under warranty.
  24. The units came with warranties - but, I admit, I have not read mine carefully. If the new chipset was used to correct a flaw in the original chipset, the original units were defective when they left the factory. If that is the scenario - I have not yet confirmed that is the case - Garmin has a legal obligation, within the terms of the warranty, to correct the problem.
  • Create New...