Re: [chrony-users] getting chrony to work with gpsd on raspbian jessie with gps hat

["Charles Muggen" <BeamPower@xxxxxxxx>]

sorry about the line breaks...

is this better?

 

chrony.conf

 

driftfile /var/lib/chrony/chrony.drift

log tracking measurements statistics
logdir /var/log/chrony

# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0

dumponexit
dumpdir /var/lib/chrony

local stratum 8
manual
smoothtime 400 0.01
makestep .1 -1

allow
logchange 0.5
rtcsync

# set larger delay to allow the NMEA source to overlap with
# the other sources and avoid the falseticker status
refclock SHM 0 refid GPS precision 1e-1 offset 0.9999 delay 0.2
refclock PPS /dev/pps0 lock NMEA

 

chrony sources

 

210 Number of sources = 2
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#? GPS                           0   4     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   4     0     -     +0ns[   +0ns] +/-    0ns

 

chrony tracking

 

Reference ID    : 7F7F0101 ()
Stratum         : 8
Ref time (UTC)  : Fri Feb 02 17:23:28 2018
System time     : 0.000000004 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 7.218 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 0.000000000 seconds
Root dispersion : 0.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Normal

 

systemctl status chronyd

 

● chronyd.service - NTP client/server
   Loaded: loaded (/lib/systemd/system/chronyd.service; enabled)
   Active: active (running) since Fri 2018-02-02 00:18:07 UTC; 17h ago
     Docs: man:chronyd(8)
           man:chrony.conf(5)
 Main PID: 961 (chronyd)
   CGroup: /system.slice/chronyd.service
           └─961 /usr/local/sbin/chronyd

 

 

 

Sent: Friday, February 02, 2018 at 12:51 PM
From: "Bill Unruh" <unruh@xxxxxxxxxxxxxx>
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian jessie with gps hat

You line breaks are a mess. You gps is not getting any data, and thus pps cannot work. Your system needs to get the approximate time ( to better than 1/4 of a second) from somewhere else than PPS, since PPS give no information about the actual time. Just when the turn of the second occurs. What is your chrony.conf file? How have you connected up gpsd? Is it seeing the gps source? William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273 Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology |____ unruh@xxxxxxxxxxxxxx Canada V6T 1Z1 ____|____ and Gravity ______|_ www.theory.physics.ubc.ca/ On Fri, 2 Feb 2018, Charles Muggen wrote: > I have a Raspberry Pi Model 2 running Raspbian Jessie. Attached to the Raspberry Pi is a GPS HAT from Adafruit. I > think I have all the libs installed to get this to work, but for some reason I am getting question marks "?" when I > run chronyc sources. > The goal is to get accurate time with no internet connection. The only time source is the GPS HAT. > Status printouts below. > Any hints/suggestions on getting this to work are greatly appreciated. > Thank you. >   > chronyc sources > 210 Number of sources = 2 MS Name/IP address         Stratum Poll Reach LastRx Last sample                > =============================================================================== #? GPS                           > 0   4     0     -     +0ns[   +0ns] +/-    0ns #? PPS                           0   4     0     -     +0ns[   +0ns] > +/-    0ns >   > chronyc tracking > Reference ID    : 7F7F0101 () Stratum         : 8 Ref time (UTC)  : Fri Feb 02 17:23:28 2018 System time     : > 0.000000004 seconds fast of NTP time Last offset     : +0.000000000 seconds RMS offset      : 0.000000000 seconds > Frequency       : 7.218 ppm fast Residual freq   : +0.000 ppm Skew            : 0.000 ppm Root delay      : > 0.000000000 seconds Root dispersion : 0.000000000 seconds Update interval : 0.0 seconds Leap status     : Normal >   > systemctl status chronyd > ● chronyd.service - NTP client/server    Loaded: loaded (/lib/systemd/system/chronyd.service; enabled)    Active: > active (running) since Fri 2018-02-02 00:18:07 UTC; 17h ago      Docs: man:chronyd(8)            man:chrony.conf(5) >  Main PID: 961 (chronyd)    CGroup: /system.slice/chronyd.service            └─961 /usr/local/sbin/chronyd >   >   > -- To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject. For help email > chrony-users-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject. Trouble? Email > listmaster@xxxxxxxxxxxxxxxxxxxx. >

--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.