NMEA driver - off by 1024 weeks but says 4096

[Mark Atwood]

I suggest running it with gpsd for a while instead of NTPsec, and see if
gpsd's logging identifies the issue.

Or if the ntpd log contains the NMEA strings, it may be possible to
reconstruct a gpsd playback file, and play it into gpsd, and see what it
says.  ESR and GEM might could help with that.

..m

On Sat, Oct 28, 2017 at 11:36 PM Hal Murray via devel <devel at ntpsec.org>
wrote:

> I'm working with an old NMEA device.  It sends things like:
>
>   $GPRMC,062409,A,3726.0822,N,12212.2630,W,000.3,190.6,150398,015.5,E*6A
> I've got a fudge time2 to fix that.  It seems to be working.
>
> I'm seeing stuff like this in the log file:
>   28 Oct 22:48:51 ntpd[2504]: NMEA(0) Changed GPS epoch warp to -4096 weeks
>
> Anybody know that chunk of code?  Is that code actually doing anything?  If
> it is doing something, why is my fudge working as I expect?
>
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-- 

Mark Atwood
http://about.me/markatwood
+1-206-604-2198 Mobile & Signal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20171031/935b5131/attachment.html>