gps004

The basemap interest is close to 0. Go and buy it where you want.

Main menu / Setup / System / Menu Key / Software Version

I had this the very first time I used my Vista. I made a hike and I noticed a great difference (around 100m) in altitude between the beginning and the end (same place). At that time I was not aware of the other problem and I considered I made something wrong. Later I had twice (and not anymore since a few weeks now ) the other problem and I fixed it switching the unit off and on. I think there must be a link somewhere. I only used 2.60 so I have no comparison with older versions.

Had the problem twice and I always used waas. Not seen the problem since weeks now. Don't know why and I don't remember having changed anything that could to explain this.

I have personally visited a lot that forum and found the information was great. That forum saved me from buying a triton 500. Thanks to them I bought a Garmin Vista HCx. I cannot be more grateful for that. Now concerning the banishment without previous warning in the post and the deletion of the posted information, I find is a kind of censure you find in some part of the world but that should not happen in our countries. There have maybe been some background communication but the reason should have been stated in the original post as an information for all members.

Are we the only few ones to have this problem ? I am wondering now if this is a firmware or a hardware problem. Is it confirmed it appeared after the last GPS firmware upgrade ? I installed 2.60 when I bought it so I do not have a comparison for my Vista..

If you suspect it is off more than in the past, try powering it off and on. Do you see a difference ? In my case difference was around 100m. Fixed after the operation.

Etrex Vista HCX. At least 1 month old

I have a Vista HCX since one month (First GPS) and I have the same problem. I thought I did something wrong until I read this post. This weekend, when I looked at the screen and saw the track was being logged around 100m from where I was I powered it off and on and immediately the track restarted where I really was. There is a gap of 100 in the middle of my track. The operation took 15 seconds so I don't think anything changed in the reception conditions. I don't know why it happened but the track logging was OK for around 2 hours. I have also seen that the track diverged progressively and not in one sudden move of 100m.This was a street and so easy to detect precisely on the map). It took around 100m to get 100m off, almost like a diagonal in a square. It stayed off constantly by 100m until I switched it off. The rest of the day was OK with no more divergence.