Anyone notice GPS Rollover Problem?

[Bill (Smithville NJ)]

April 6 has come and gone with only minor GPS data rollover problems - at least on the newer units.

Just for curiosity, I powered up my MIO C310 handheld GPS. This is a nice little unit that I purchased back in 2000. Haven't used it for a few years since the latest car had a GPS built-in and the cell phones work so well for navigating.

After a few minutes, it acquired enough satellites to display what it thinks is the date. I was expecting it to be 1999.

But was really surprised when it showed January 1, 1601.

Did anyone here get similar errors on their old GPS units?

Bill
Smithville, NJ

[SammysHP]

Yes, I have date issues on my Garmin Legend HCx.

[DA74254]

I haven't checked my own oldest yet; a Garmin eTrex Legend from 2003. I'm currently at work (seaman) and eager to check when I return home in abt a fortnight

Alas, Garmin claims it should work correctly positionwise but the date and time may be incorrect.

[smp]

My Garmin Nuvi 2555 got a small software update a couple of days ago.
I assume it had something to do with avoiding/solving this issue.

smp

[Bill (Smithville NJ)]

I just powered up the second Mio C310 (I had originally bought three of them).

It also shows January 1, 1601.

I wonder why it rolled over to 1601 instead of 1999.

Did anyone else get a bad date other than 1999?

73
Bill Smithville, NJ

[EugeneNine]

ǝɹǝɥ ɯǝlqoɹd ɹǝʌolloɹ ou

[Steve Keeley]

I just fired up my Garmin E-trex Summit from 2000. (I can't remember the last time I had it turned on.) After letting it find 4 satellites I checked the date and it read 11-APR-19.

[Sylvain Cote]

ArsTechnica Article
GPS’ UTC clock, used for more than navigation, is about to reset. There might be some surprises.

USA NCCIC/NCC GPS Warning Document
MEMORANDUM FOR U.S. OWNERS AND OPERATORS USING GPS TO OBTAIN UTC TIME

[Maximilian Hohmann]

Hello!

I haven't had any problems with any GPS device so far. Luckily, because the business jet I fly for a living is nearly 20 years old.

But these guys here seem to have some serious problems (our friend Geoff here flies that type, I hope he is not left stranded somewhere!):

http://newsinflight.com/2019/04/08/15-bo...ver-issue/

Regards
Max

[Zaphod]

(04-09-2019 04:07 PM)Bill (Smithville NJ) Wrote:  But was really surprised when it showed January 1, 1601.

January 1 1601 is the date from which ANSI dates are counted.

Quote:ANSI Date
ANSI dates are counted from 1601-01-01 and were adopted by the American National Standards Institute for use with COBOL and other computer languages. This epoch is the beginning of the last 400-year cycle by which leap-years are calculated in the Gregorian calendar. The last year of this cycle is the only one divisible by 100 that is a leap-year, which was the year 2000, and which was followed by a new 400-year cycle beginning with 2001. 32-bit versions of the Microsoft Windows operating system count units of one hundred nanoseconds from this epoch.

[Jlouis]

(04-09-2019 04:07 PM)Bill (Smithville NJ) Wrote:  But was really surprised when it showed January 1, 1601.

Bill
Smithville, NJ

Hmmm, now I have sure that Colombo and Cabral had a GPS back then and what they discovered was not an accident...

[Bill (Smithville NJ)]

(04-12-2019 07:54 PM)Zaphod Wrote:  

(04-09-2019 04:07 PM)Bill (Smithville NJ) Wrote:  But was really surprised when it showed January 1, 1601.

January 1 1601 is the date from which ANSI dates are counted.

Thanks for pointing that out. I never knew that ANSI had a date epoch.
I knew Unix had a date epoch of Jan 1, 1970, but never really thought about what windows used.

So far, my Mio GPS units are the only ones that I have seen using 1601. All my friends units have all come up with1999.

I learn something new every time I come to this forum.

Bill
Smithville, NJ