Re: gpsd + chrony + pps

[Dan Williams]

> Not knowing chronyd well, I'm unclear what that says.

Yea, it's a bit clearer with the full output from 'chronyc sources' -- i.e. the column headers:

> MS Name/IP address         Stratum Poll Reach LastRx Last sample
> ===============================================================================
> #? GNSS                          0   4   377    17    +64ms[  +64ms] +/-  200ms
> #* PPS                           0   4   377    14   +363ns[ +506ns] +/- 1790ns

From the man pages, (https://chrony.tuxfamily.org/doc/3.4/chronyc.html), the output can be deciphered that the above two sources are actually flowing time updates into chronyc -- Success!

> How about the output of this, as root:
>        # ntpshmmon

Does that command actually show the changes in `/var/run/chrony.pps0.sock` ?   I was under the impression that is a different mechanism than the shared memory api?

Daniel Williams  |  Software Engineer

dwilliams@nextdroid.com

On Thu, Jun 18, 2020 at 1:15 PM Gary E. Miller <gem@rellim.com> wrote:

Yo Stéphane!

On Thu, 18 Jun 2020 11:11:26 +0200
Stéphane Péneau <stephane.peneau@wanadoo.fr> wrote:

> > What steps have you progressed through, to verify that the PPS
> > signal is being received by the OS?
>
> refclock SOCK /var/run/chrony.pps0.sock refid PPS2 lock GNSS
>
> It works :

Not knowing chronyd well, I'm unclear what that says.  It could just
be the NMEA time.

How about the output of this, as root:
        # ntpshmmon

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin