Re: NTPsec reports excessive jitter from GPSD/KPPS SHM

[Gary E. Miller]

Yo Nick!

On Wed, 04 Mar 2020 22:17:25 +0000
"Nick Burkitt" <address@hidden> wrote:

> Representative ntpmon output (afterPPS is marked as a falseticker):

Oddly I see that it is my mailer, and my lack of caffeine, that lost the
offset and jitter.

So, morphing your table a bit:

>       remote      offset jitter
>   SHM(0)          -33.5071 17.3123
> xSHM(1)           -122.422 15.4372
> +ha81.smatwebdes   19.3951 35.7520
> -ntp2.wiktel.com  -37.5661 32.3464
> -nu.binary.net    -35.1534 36.6477
> *ntp2.wiktel.com   -8.1684 19.2080
> +time.cloudflare  -14.3229 20.2842

Looks to me like your PPS pulse width is 100 milli seconds, and your are
triggering on the wrong edge.  If you KPPS was returning both edges, then
the gpsd KPPS code would pick the right 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

pgpfRsRVQDI0E.pgp
Description: OpenPGP digital signature