|
From: | Nick Burkitt |
Subject: | Re[2]: NTPsec reports excessive jitter from GPSD/KPPS SHM |
Date: | Sun, 08 Mar 2020 01:49:00 +0000 |
User-agent: | eM_Client/7.2.37929.0 |
Hi Gary. Thanks - does the order matter? I've been using gpsd -n /dev/pps0 /dev/ttyACM4 and seeing those large PPS jitter numbers in NTPsec When I try gpsd -n /dev/ttyACM4 /dev/pps0 NTPsec doesn't seem to be able to find SHM(1) at all
remote refid st t when poll reach delay offset jitter SHM(0) .GPS. 0 l 8 64 377 0.0000 -65.3223 1.4824 SHM(1) .PPS. 0 l - 8 0 0.0000 0.0000 0.0019 +gatekeeper.tss. 216.218.254.202 2 u 27 64 377 42.5804 1.7949 0.8879 -ntp1.nbg1.squar 193.171.23.163 2 u 32 64 377 174.9244 6.6212 1.1147 *chl.la 216.218.192.202 2 u 11 64 377 29.7299 2.6507 2.8947 -vf2.bbnx.net 253.109.221.150 2 u 18 64 373 103.4807 -3.8824 21.8616 pool.ntp.org .POOL. 16 p - 256 0 0.0000 0.0000 0.0019 -134.209.141.224 127.67.113.92 2 u 18 64 377 24.9198 -0.2233 0.7348 +paladin.latt.ne 204.123.2.72 2 u 22 64 377 21.7663 -0.2696 1.1303 -pegasus.latt.ne 128.227.205.3 2 u 16 64 163 84.8570 -0.5848 1.3430 ntp1.ams1.squar 193.79.237.14 2 u 79 64 42 179.8666 13.4722 1.7658 ntpd ntpsec-1.1.8+ 2020-03-04T20:55:58Z Updated: 2020-03-08T01:46:24 (4) lstint avgint rstr r m v count rport remote address 0 32083 0 . 6 2 2073 44435 localhost 12 4431795 d0 . 4 4 16 123 chl.la 17 98 d0 . 4 4 5 123 pegasus.latt.net 19 4431795 d0 . 4 4 16 123 vf2.bbnx.net 19 4154808 d0 . 4 4 17 123 134.209.141.224 23 4154808 d0 . 4 4 17 123 paladin.latt.net 28 4154807 d0 . 4 4 17 123 gatekeeper.tss.net 33 4748351 d0 . 4 4 15 123 ntp1.nbg1.squareflow.xyz 80 136 d0 . 4 4 3 123 ntp1.ams1.squareflow.xyz -Nick ------ Original Message ------
From: "Gary E. Miller" <address@hidden>
To: address@hidden
Sent: 3/7/2020 5:01:30 PM
Subject: Re: NTPsec reports excessive jitter from GPSD/KPPS SHM
|
[Prev in Thread] | Current Thread | [Next in Thread] |