On Mon, 30 Oct 2017, Hal Murray via devel wrote:
> fallenpega...@gmail.com said:
> > 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 pl
fallenpega...@gmail.com said:
> 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.
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.
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 war
