Re[2]: NTPsec reports excessive jitter from GPSD/KPPS SHM

[Nick Burkitt]

Hi Gary.

No problem, but let's get back in sync. Here's the info again. This configuration seems to be working. Am I mistaken?

With this command line:

gpsd -n /dev/ACM4 /dev/pps0

and this ntp.conf GPS/PPS configuration:

# GPS Serial data reference (NTP0)

refclock shm unit 0 refid GPS noselect

# GPS PPS reference (NTP1)

refclock shm unit 2 minpoll 3 maxpoll 3 refid PPS prefer 

I finally see ntpmon output that makes sense (to me):

     remote           refid      st t when poll reach   delay   offset   jitter

 SHM(0)          .GPS.            0 l    1   64  377      0ns -67.60ms 1.9155ms

*SHM(2)          .PPS.            0 l    1    8  377      0ns 306.33us 20.710us

-t2.time.bf1.yah 98.138.17.15     3 u    2   64  377 100.54ms 247.84us 1.7718ms

-vps5.ctyme.com  216.218.254.202  2 u    2   64  377 22.541ms -1.585ms 1.7352ms

-time.cloudflare 10.4.0.197       3 u   11   64  377 22.042ms -3.304ms 1.2201ms

+mis.wci.com     192.12.19.20     2 u   14   64  377 42.174ms -671.7us 1.4036ms

 pool.ntp.org    .POOL.          16 p    -  256    0      0ns      0ns  1.907us

-66.85.78.80     172.16.23.153    2 u   31   64  377 63.698ms -162.2us 5.8518ms

-ns1.backplanedn 173.162.192.156  2 u   30   64  377 92.035ms 6.9021ms 4.5433ms

+t2.time.gq1.yah 208.71.46.33     2 u   27   64  377 45.646ms 728.41us 1.1335ms

-static-72-87-88 128.59.0.245     2 u   28   64  363 91.383ms -2.542ms 1.2817ms

ntpd ntpsec-1.1.8+ 2020-03-04T20:55:58Z        Updated: 2020-03-09T16:22:31 (4)

 lstint avgint rstr r m v  count rport remote address

      0     61    0 . 6 2   2187 58711 localhost

      2   8342   d0 . 4 4     17   123 vps5.ctyme.com

      3   8342   d0 . 4 4     17   123 t2.time.bf1.yahoo.com

     11   7851   d0 . 4 4     18   123 time.cloudflare.com

     14   7851   d0 . 4 4     18   123 mis.wci.com

     27   7850   d0 . 4 4     18   123 t2.time.gq1.yahoo.com

     29  10265   d0 . 4 4     14   123 static-72-87-88-202.prvdri.fios.verizon.

     31   8341   d0 . 4 4     17   123 ns1.backplanedns.org

     32   7850   d0 . 4 4     18   123 66.85.78.80

Thanks,

-Nick

------ Original Message ------

From: "Gary E. Miller" <address@hidden>

To: address@hidden

Sent: 3/9/2020 11:49:44 AM

Subject: Re: NTPsec reports excessive jitter from GPSD/KPPS SHM

Yo Nick!

 

On Mon, 09 Mar 2020 18:45:14 +0000

"Nick Burkitt" <address@hidden> wrote:

 

Hi Gary.

 

>Except, you have them backwards. Your PPS is on SHM(0) and your

>GPS is on SHM(2). Assuming: gpsd -n /dev/pps0 /dev/ttyACMx

 

Why assume? I included the gpsd command line. Here it is again:

 

But not in the email that I replied to. Happens all the time that

things mutate and not reported. That is why I had to assume that you

had not changed things. And, you had changed it, and did not report it

in the email that I replied to. As I often read email order I often

miss changes like this one.

 

RGDS

GARY

---------------------------------------------------------------------------

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703

address@hidden Tel:+1 541 382 8588

 

Veritas liberabit vos. -- Quid est veritas?

"If you can't measure it, you can't improve it." - Lord Kelvin