Problem migrating from legacy to ntpsec

[Hal Murray]

Is there anything interesting in the log file?

> The relevant lines from ntp.conf are:
> server 127.127.20.0 mode 16 minpoll 4 iburst
> fudge 127.127.20.0 time1 -0.0007 flag1 1 flag2 0 flag3 1 refid PPS 

Turning on flag 1 does the PPS processing in the NMEA driver.  That merges 
the data from 2 drivers into one which makes it harder to debug things 
like this.

I use two separate drivers:

server 127.127.20.0 path /dev/ttyS0 prefer mode 0x10001
fudge  127.127.20.0 flag1 0             # disable PPS
fudge  127.127.20.0 time2 0.167         # offset for NMEA signal

server 127.127.22.0 ppspath /dev/pps0   # PPS signal, needs prefer
fudge  127.127.22.0 flag2 0             # Rising edge

That will put things like this in clockstats (if you have it enabled):
60559 76229.866 127.127.22.0 47838 64 0 0 0
60559 76266.866 127.127.20.0 $GPRMC,211106,A,3726.0746,N,12212.2511,W,
   000.0,138.7,210105,015.0,E*6F  64 64 0 0 0 0


Your ntpq output shows an offset of -96.9056
You might need something like:
  tos mindist 0.075     # default is 0.001 (1 ms)
Adjust the 0.075 to be big enough to cover the offset from your NMEA 
signal to the PPS.  (or fudge the NMEA to be close enough)

> Also, is it a true statement that all I have to do to change to the new
> naming scheme is to change 127.127.20.0 to nmea? 

It might need (0) to tell it which NMEA line to use.  It may need NMEA in 
upper case.  What ntpq -p shows should work.  (I haven't bothered to 
change.  The old 127.127 stuff is unlikely to stop working.)

-- 
These are my opinions.  I hate spam.