Frank Kardel <kardel%netbsd.org@localhost> writes: > From your billboards I see a systematic offset of 650ms. This > driver needs to know the time offset at the end of the line. > See file:///usr/share/doc/html/ntp/drivers/driver20.html > time 2 - Specifies the serial end of line time offset calibration > factor, in seconds and fraction, with default 0.0.) > > So you might want to try to fudge time2 to 0.650 in your case. (I hope > I analyzed the code correctly) Are you suggesting that the NMEA data is delayed by 650 ms, and then the check that the pps is close enough to NMEA is failing, and thus the refclock driver is using the NMEA offsets instead?
Description: PGP signature