Does anybody have a sample of a NMEA device with the 1024 week bug?
trv-n at comcast.net
Wed Apr 26 05:52:46 UTC 2017
I have a device that will rollover after week 1998 (in 2018) that I
just tested with a GPS simulator set to 2 years in the future,
attached to ntpd classic with a +2 year offset in get_ostime (and
"disable ntp" in conf) and ntpcal_get_build_date() of 2016. The
512-week-around-receive-timestamp code in the driver fixed the
timecode timestamp from 1999-09-10 to the proper date.
>Gary E. Miller gem at rellim.com wrote:
>On Wed, 26 Apr 2017 01:09:14 +0000
>Mark Atwood via devel <devel at ntpsec.org> wrote:
>> How hard is it to write a fake NMEA device simulator in Python, and
>> use Linux IPC control magic to have it appear at a fake serial device?
>Not how hard, but who wants that at the top of their list. I think you
>have some free time now?
>All for an obsolete device that we do not think anyone has?
More information about the devel