jsl7687

I ran across this post through a Google search and thought I would share my experience. Unfortunately it looks like my Vista Cx unit has been affected by this rollover (i.e. my GPS has been y2k'd!). The time of day (if you don't consider DST) and navigation appear to work normally, but the date will be off. My unit will show a date 1024, 2048, or 3072 weeks into the future depending on what the previous state of the GPS was on last shutdown. When it hits 4096 weeks, it doesn't actually show this date but instead the unit does a complete cold start and will eventually show the correct time/date once a GPS lock is achieved. For example, here is the cyclic pattern I've seen with my unit after doing some experimenting this weekend on 2019-04-13: State 1) Date: 2020-07-22, Time: ~5 hours off (DST off). I’m considering this the beginning of the cycle. Every time the GPS starts in this state, it is a complete cold start, regardless if there was a GPS lock before a restart. After the unit searches for satellites and gets a lock, the date and time are updated to the correct date/time. …restart… State 2) Date 2038-11-27, Time: correct (DST off). Hot start - quick lock on GPS. This date is 1024 weeks into the future. The date is never updated even after a good soak with a GPS lock. …restart… State 3) Date 2078-02-26, Time: correct (DST off). Hot start - quick lock on GPS. This date is 3072 weeks into the future (3 x 1024). The date is never updated even after a good soak with a GPS lock. …restart… …cycle repeats… State 1) Date: 2020-07-22, Time: ~5 hours off (DST off). Cold start. Date/time corrected after lock. I can repeat this cycle many times and get the same result. For some reason I don't get the 2048 date (2058-07-13) during this exercise, but I have seen it pop up occasionally when I first noticed the issue. I did this exercise with back to back shutdown/restarts, so perhaps something else happens when the GPS is off for a longer period of time. My concern when I first saw the issue is that I wouldn't be able to save my track logs with accurate time/date information (I'm not a geocacher, but regularly reference my old track logs for planning hiking/skiing/mountaineering trips); however, now that I know the error is predictable I can simply modify the gpx file by subtracting some multiple of 1024 weeks from the date and then correcting the time for DST if necessary. It's an extra step in the process but it will work for now, at least until I talk myself into buying another GPS.