NTPsec flags my GPS as a falseticker

[Hal Murray]

users at ntpsec.org said:
> 2020-03-19T02:39:11 ntpd[19607]: CONFIG: configpeers: Ignoring duplicate '127.127.28.2'
> 2020-03-19T02:39:11 ntpd[19607]: CONFIG: configpeers: Ignoring duplicate '127.127.28.0' 

Something fishy there.  I'd fix that just to make sure you are using the 
correct lines from the config file.


> refclock shm unit 2 refid PPS minpoll 3 maxpoll 3 prefer flag4 1
> refclock shm unit 0 refid GPS minpoll 3 maxpoll 4 time1 0.080 flag4 1

The combination of 0 and 2 is a bit strange.  The usual pairing is 0 and 1 for 
the first GPS device and 2 and 3 for the second GPS device.

-----------

I'm not a gpsd wizard.  If you don't need it for some other reason, try using 
the NMEA and PPS drivers.  This works for me on a Raspberry Pi.

# PPS via GPIO, Adafruit GPS card with ???? NMEA driver: GPRMC, 9600, stats
server 127.127.20.0 prefer path /dev/ttyAMA0  mode 0x010011
fudge  127.127.20.0 flag1 0            # disable PPS
fudge  127.127.20.0 time2 0.600        # Fixup offset
server 127.127.22.0                    # PPS signal, needs prefer
fudge  127.127.22.0 flag2 0            # Rising edge

     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
*NMEA(0)         .GPS.            0 l   59   64  377   0.0000 -31.9530  35.5048
oPPS(0)          .PPS.            0 l   58   64  377   0.0000  -0.1953   1.6976



-- 
These are my opinions.  I hate spam.