1.1.6 build fails on FC30

[Udo van den Heuvel]

On 16-04-2020 00:55, Hal Murray wrote:
>> So no error messages about gps/NMEA.
> 
>> NMEA(0)                                 .GPS.            0 l   15   64 377   0.0000   0.0000   0.0019
> 
> What's the line for that in your ntp.conf?  Any fudge lines?

driftfile /var/lib/ntp/drift

nts key /etc/letsencrypt/keys/0000_key-certbot.pem
nts cert /etc/letsencrypt/csr/0000_csr-certbot.pem

restrict default nomodify nopeer noquery
restrict -6 default nomodify nopeer noquery

restrict 127.0.0.1
restrict -6 ::1

restrict 192.168.10.0 mask 255.255.255.0 nomodify

refclock nmea unit 0 mode 7 flag3 0 flag2 0 flag1 1 time1 0.00000006
time2 0.260 baud 4800

disable monitor

server 192.168.10.98 minpoll 4 iburst
server fd00:c0a8:a00:1::1

server time.cloudflare.com:1234 nts  # TLS1.3 only
server ntpmon.dcs1.biz nts
server pi4.rellim.com nts
server ntp1.glypnod.com nts
server ntp2.glypnod.com nts
server ntp.xs4all.nl
server ntp2.xs4all.nl
server ntp0.nl.net
server ntp2.nl.net
server keetweej.vanheusden.com
server ntp.nmi.nl

includefile /etc/ntp/crypto/pw

keys /etc/ntp/keys

statsdir /var/log/ntp/

logconfig =syncall -clockall


We have some `time`in place.
See the nmea refclock. Has been there for ages.

> What does stty say for the baud rate?

# stty < /dev/ttyS0
speed 4800 baud; line = 18;
intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof =
<undef>;
start = <undef>; stop = <undef>; susp = <undef>; rprnt = <undef>;
werase = <undef>; lnext = <undef>; discard = <undef>;
ignbrk -brkint -imaxbel
-opost -onlcr
-isig -iexten -echo -echoe -echok -echoctl -echoke

> What sort of GPS device ?  What baud rate is it using?

Garmin GPS18X
4800 bps.

> Try stopping ntpd and running cat /dev/whatever
> That should show some NMEA sentences.

It does, even with the ntpd running.

> The 377 reach shows that something is working but the rest of the line shows 
> that it isn't.
> 
> The NMEA driver is strange in that it tries to merge both the NMEA and PPS.  I 
> guess that's good if it works, but it makes debugging things like this 
> complicated.

I could switch to a NMEA clock sans PPS and a dedicated PPS clock?

> I run with 2 separate servers.  Here is the chunk from my ntp.conf
> 
> 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
> 
> That turns into:
> *NMEA(0)         .GPS.            0 l   31   64  377   0.0000  10.9381  27.6977
> oPPS(0)          .PPS.            0 l   30   64  377   0.0000   0.0570   0.0004

Like more or less what I understand from this part...


Udo