Re: [gpsd-users] About date and time validity

[Gary E. Miller]

Yo Massimiliano!

On Sun, 23 Dec 2018 12:15:58 +0100
Massimiliano Fago <address@hidden> wrote:

> sorry for delay. Yes, I do not see NTP1 record, but when i run pptest
> I found one source and I think that the hardware is ok. It is correct?
> 
> address@hidden:/home/pi# ppstest /dev/pps0
> trying PPS source "/dev/pps0"
> found PPS source "/dev/pps0"
> ok, found 1 source(s), now start fetching data...
> source 0 - assert 1545563231.009011405, sequence: 2433 - clear
> 0.000000000, sequence: 0
> source 0 - assert 1545563232.009020271, sequence: 2434 - clear
> 0.000000000, sequence: 0

That looks good.  You have a good KPPS signal for gpsd to use.

> after I start gpsd with this command:
> 
> ./gpsd -D 5 -N -n /dev/ttyAMA0 /dev/pps0

You started with "-D 5" for debug info.  What does it say?

It should look like this:

# gpsd -D 5 -N -n /dev/ttyAMA0 /dev/pps0 |& fgrep PPS
gpsd:PROG: PPS:/dev/ttyAMA0 chrony socket /var/run/chrony.ttyAMA0.sock doesn't 
exist
gpsd:INFO: KPPS:/dev/pps0 RFC2783 path:/dev/pps0, fd is 6
gpsd:INFO: KPPS:/dev/pps0 pps_caps 0x1151
gpsd:INFO: KPPS:/dev/pps0 have PPS_CANWAIT
gpsd:WARN: KPPS:/dev/pps0 missing PPS_CAPTURECLEAR, pulse may be offset
gpsd:INFO: KPPS:/dev/pps0 kernel PPS will be used
gpsd:PROG: PPS:/dev/pps0 thread launched
gpsd:INFO: PPS:/dev/ttyAMA0 ntpshm_link_activate: 1
gpsd:PROG: switch_driver(PPS) called...
gpsd:PROG: selecting PPS driver...
gpsd:PROG: PPS:/dev/pps0 chrony socket /var/run/chrony.pps0.sock doesn't exist
gpsd:INFO: KPPS:/dev/pps0 RFC2783 path:/dev/pps0, fd is 7
gpsd:INFO: KPPS:/dev/pps0 pps_caps 0x1151
gpsd:INFO: KPPS:/dev/pps0 have PPS_CANWAIT
gpsd:WARN: KPPS:/dev/pps0 missing PPS_CAPTURECLEAR, pulse may be offset
gpsd:INFO: KPPS:/dev/pps0 kernel PPS will be used
gpsd:PROG: PPS:/dev/pps0 thread launched
gpsd:INFO: PPS:/dev/pps0 ntpshm_link_activate: 0
gpsd:PROG: KPPS:/dev/pps0 gps_fd:-2 not a tty, can not use TIOMCIWAIT
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/pps0 kernel PPS timeout Interrupted system call
gpsd:PROG: KPPS:/dev/pps0 assert  1545596148.999999243, sequence: 4900210, 
clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle: 1545596148999999, duration:       0 @  
1545596148.999999243
gpsd:PROG: PPS:/dev/pps0 Assert cycle: 1545596148999999, duration:       0 @  
1545596148.999999243
gpsd:PROG: PPS:/dev/pps0 Assert ignored missing last_fixtime
gpsd:PROG: KPPS:/dev/pps0 assert  1545596148.999999243, sequence: 4900210, 
clear   0.000000000, sequence: 0 - using: assert
gpsd:PROG: KPPS:/dev/pps0 Assert cycle: 1545596148999999, duration:       0 @  
1545596148.999999243
gpsd:PROG: PPS:/dev/pps0 Assert cycle: 1545596148999999, duration:       0 @  
1545596148.999999243
gpsd:PROG: PPS:/dev/pps0 Assert ignored missing last_fixtime

> In my /etc/ntp.conf file I have the following rows:

> # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
> 
> driftfile /var/lib/ntp/ntp.drift
> 
> # Enable this if you want statistics to be logged.
> statsdir /var/log/ntpstats/
> 
> statistics loopstats peerstats clockstats sysstats
> filegen loopstats file loopstats type day enable
> filegen peerstats file peerstats type day enable
> filegen clockstats file clockstats type day enable
> filegen sysstats file sysstats type day enable
> 
> # GPS PPS reference
> server 127.127.28.2 prefer
> fudge  127.127.28.2 refid PPS
> 
> # get time from SHM from gpsd; this seems working
> server 127.127.28.0
> fudge  127.127.28.0 refid GPS
> 
> # By default, exchange time with everybody, but don't allow
> configuration. restrict -4 default kod notrap nomodify nopeer noquery
> limited restrict -6 default kod notrap nomodify nopeer noquery limited
> 
> # Local users may interrogate the ntp server more closely.
> restrict 127.0.0.1
> 
> # Needed for adding pool entries
> restrict source notrap nomodify noquery
> 
> # Clients from this (example!) subnet have unlimited access, but only
> if # cryptographically authenticated.
> #restrict 192.168.123.0 mask 255.255.255.0 notrust

Looks good to me.  But since you problem was before ntpd and ntpshmmon I
would not expect this problem is in ntp.conf.

> dear Gary, we wish you a merry Christmas

It snowed here last night.  Melted today, but maybe I'll have a white
Christmas.  I hope yours is also merry.


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

pgpkVqMgXvZ9L.pgp
Description: OpenPGP digital signature