3 ms·

It's something that's inherent in the GPS standard, which was developed considerably before Y2K, and it's something that's very very easy to correct for. Are y

It's something that's inherent in the GPS standard, which was developed considerably before Y2K, and it's something that's very very easy to correct for. Are you surprised that people are still designing hardware where the time rolls over to 00:00 every 24 hours?

mkl 4y ago
The signal is 10-bit, but it seems silly to make the receiving device 10-bit and suffer this problem when correcting for it is easy. OP says it wasn't always corrected for, even by people with the lesson of Y2K behind them, which is what surprises me.
- nullc 4y ago
  Every one of the devices failing at this particular date have been 'corrected' for it: They are shifting the wrap point based on their manufacturing date. The natural wrap point isn't now-- the second natural wrap was in 2018. Correcting for it more elaborately than that is challenging, in particular if you depend on remembering the number of wraps a replacement part pulled off the shelf will return wrong dates when the original was fine, also if you remember then a false (or spoofed) signal can put the device in a bricked state. Most GPS receivers (including most of the ones listed here) can be temporarily fixed by setting the date manually. But their interfaces may be inaccessible in the devices they're installed in and the fix will be lost after restart. The L1C/L2C/L5 gps signals use a 13 bit week number. Hardware for the new signals was first deployed with the IIR-M satellites in 2005 with L2C support, which were delayed from something like 1997... but no broadcasting of L2C started until 2014. Right now very few receivers support the new signals.
relaxing 4y ago
Luckily the 24 hour clock comes with a rollover counter, which may be confusingly named something like “day.” Consult accompanying documentation for details. If your hardware vendor did not include a “day” counter, you may need to implement in wetware.
- Gordonjcp 4y ago
  But then that rolls over every seven "days" incrementing the "week" counter, and then either 28, 29, 30, or 31 days in a bizarre pattern incrementing the "month" counter. Then - get this - every 365.25 days it increments the "year" counter, which is just so spectacularly half-assed. Three hundred and sixy-five *and a quarter* days. WTAF.
  - quickthrower2 4y ago
    You could store the number of milliseconds since an arbitrary date in Greenwich UK, and provide methods to get the time, but even this has problems. The units could be defined by atomic vibrations or by the spinning of a large celestial object but these don’t agree. What is more the large celestial object (and others nearby) distorts space and time adding to the issue of where the time is (see my past submission on Barycentric Time)
- quickthrower2 4y ago
  My device doesn’t have a day counter but it makes a hell of a buzz in the morning to wake me up and runs off stored mechanical energy

mkl 4y ago

The signal is 10-bit, but it seems silly to make the receiving device 10-bit and suffer this problem when correcting for it is easy. OP says it wasn't always corrected for, even by people with the lesson of Y2K behind them, which is what surprises me.

nullc 4y ago
Every one of the devices failing at this particular date have been 'corrected' for it: They are shifting the wrap point based on their manufacturing date. The natural wrap point isn't now-- the second natural wrap was in 2018. Correcting for it more elaborately than that is challenging, in particular if you depend on remembering the number of wraps a replacement part pulled off the shelf will return wrong dates when the original was fine, also if you remember then a false (or spoofed) signal can put the device in a bricked state. Most GPS receivers (including most of the ones listed here) can be temporarily fixed by setting the date manually. But their interfaces may be inaccessible in the devices they're installed in and the fix will be lost after restart. The L1C/L2C/L5 gps signals use a 13 bit week number. Hardware for the new signals was first deployed with the IIR-M satellites in 2005 with L2C support, which were delayed from something like 1997... but no broadcasting of L2C started until 2014. Right now very few receivers support the new signals.

relaxing 4y ago

Luckily the 24 hour clock comes with a rollover counter, which may be confusingly named something like “day.” Consult accompanying documentation for details. If your hardware vendor did not include a “day” counter, you may need to implement in wetware.

Gordonjcp 4y ago
But then that rolls over every seven "days" incrementing the "week" counter, and then either 28, 29, 30, or 31 days in a bizarre pattern incrementing the "month" counter. Then - get this - every 365.25 days it increments the "year" counter, which is just so spectacularly half-assed. Three hundred and sixy-five *and a quarter* days. WTAF.
- quickthrower2 4y ago
  You could store the number of milliseconds since an arbitrary date in Greenwich UK, and provide methods to get the time, but even this has problems. The units could be defined by atomic vibrations or by the spinning of a large celestial object but these don’t agree. What is more the large celestial object (and others nearby) distorts space and time adding to the issue of where the time is (see my past submission on Barycentric Time)
quickthrower2 4y ago
My device doesn’t have a day counter but it makes a hell of a buzz in the morning to wake me up and runs off stored mechanical energy