markhait

I went out today to do a couple caches since doing a hard boot yesterday and it looked like it was doing OK until I got to my 2nd cache. On the map it showed the cache on my side of the street, but the compass heading showed straight ahead and another 188'. I hesitated, but went across the street anyway and it wouldn't count down anymore, but then the compass needle swung around and pointed in the direction I just came from. I went back across the street and got to within 45' and then it just sat there not going up or down. While I was fooling with it, my son found the cache and it was about 15' away. I understand the margin or error with a GPS, but what drives me nuts is when it won't update either smaller or larger. I've had it at 2' and walked another 50' and it still said 2'. I mean come on now! A 64st with maps is like $500 and this is the best I can expect? I bought the 64st because it is rated as one of the best/most accurate GPS's with excellent satellite reception. I'll be warning everyone now to stay away!

I just did a hard reset and it seems to have worked. Sucks because my found geocaches are gone, but since I just started and only have 10 found, I guess that's not going to be too much work setting them back to found. I'll try again tomorrow after work and see what happens. I guess since I know where 10 caches are at, it should make easy work to see if the GPS is working. Wish me luck and thanks for your help!

^^^This^^^ Nope...not locked on road. This thing is just messed up! I spent 10 minutes with Garmin on the phone and tried the usual.....correct version, waas turned on etc....just came back from a geocache and it seemed like I could get close to the correct location, but could not zero in on it. Once I found one, I marked it with a waypoint and headed off to the next. On our way back, I tried going to my way point, but when I got there it said that I need to go another 138'! I tried the exact same thing at home, but this time when I got to my way point it said that I needed to go another .13 miles! I turned it off and tried again and it got me to within 13'. Walked across the yard, marked another way point and then tried to go back to the first one. The way point page said that I was 147' away....probably correct, then I switched to the map screen and it said I needed to go .13 miles! I give up! I guess I'll be on the phone with Garmin tomorrow too!

I bought a Garmin 64st and am having tons of problems with it...maybe its me? I bought it specifically for geocaching because of its good reviews and connectivity to satellites. Once I pick a cache and get real close to it, it seems to stop working. It will either say 0 feet to destination or 2 feet or even sometimes 20 feet. As I begin to walk around it won't count up or down...maybe a foot or two, but that's it. In almost every situation of late, I had clear view of the sky, full lock on and the accuracy was stated at 10 feet. This was same in both the compass screen and the trip screen. The reason I know something is wrong is because when I switch to the map screen, it will say I'm like 50' or more away. From there I keep switching between screens and have even turned it off and rebooted it and even ended the navigation to the cache. Eventually through all this, it finally starts to work. On a cache today, it took me over 300' away from it's actual location before it started to work through switching screens and re-booting. With the maps and everything this unit cost me well over $500 and I hate it as of today!....I want to call Garmin and scream at them! Is there something I'm doing wrong? This is my first handheld GPS that I've owned and I admit that I'm not a seasoned pro, but this sounds like it's broken! Please help!!!

Just started using my new GPSMAP 64st for geocaching. I setup, received and unzipped a Pocket Query from Geocaching and the GPS won't read it. If I download individual geocaches they show up fine on the GPS. I put the Pocket Query in the exact same folder as all the individual GPX files that showed up. I don't understand what I'm doing wrong or is this just a glitz on Garmin's side? Thanks for your help!