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

[Charles Muggen]

I'm sorry for the double negative.
I was in the middle of a paste.
I need to proofread my replies better.


> Sent: Monday, February 05, 2018 at 4:24 PM
> From: "Bill Unruh" 
> To: chrony-users@chrony.tuxfamily.org
> Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian 
> jessie with gps hat
>
> > now it seems to lock on PPS1, but I don't think PPS1 is not a valid source. 
> > Sorry, you double negative is completely confusing. It looks to me like 
> > pps1 is a fine source and so does chrony. What problem do you have with it? 
> > > here's the results for chronyc sources: > > 210 Number of sources = 2 > 
> > MS Name/IP address Stratum Poll Reach LastRx Last sample > 
> > ===
> >  > #? GPS 0 4 0 1192 -43.4s[ -43.7s] +/- 200ms > #* PPS1 7 4 377 20 +9ns[ 
> > +773ns] +/- 629ns > > > > > >> Sent: Monday, February 05, 2018 at 6:03 AM 
> > >> From: "Miroslav Lichvar" >> To: chrony-users@chrony.tuxfamily.org >> 
> > Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian 
> > jessie with gps hat >> >> On Fri, Feb 02, 2018 at 11:35:42PM +0100, Charles 
> > Muggen wrote: >>> # 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. delay 0.2 >>> refclock SHM 1 
> > refid PPS precision 1e-9 >> >> If you are using the SHM 1 source, which is 
> > based on PPS with gpsd, >> I'd suggest to either remove the first line or 
> > add noselect to it. >> >> You could also use the PPS device directly with 
> > SHM 0, e.g. >> >> refclock SHM 0 offset 0.5 delay 0.2 refid NMEA noselect 
> > >> refclock PPS /dev/pps0 lock NMEA refid GPS >> >>> I made a change to my 
> > /boot/config.txt >>> I had to add a line that says >>> 
> > dtoverlay=pps-gpio,gpio=4 >>> This points the PPS server to pin 4 of the 
> > GPS HAT. >>> >>> hmmm, maybe the thing is working... but should the PPS 
> > show an asterisk "*"? >> >> How is gpsd started? With a GPIO PPS, I think 
> > it needs to be started >> with both devices: serial (e.g. /dev/ttyS0) and 
> > PPS (e.g. /dev/pps0). >> >> -- >> Miroslav Lichvar >> >> -- >> To 
> > unsubscribe email chrony-users-requ...@chrony.tuxfamily.org >> with 
> > "unsubscribe" in the subject. >> For help email 
> > chrony-users-requ...@chrony.tuxfamily.org >> with "help" in the subject. >> 
> > Trouble? Email listmas...@chrony.tuxfamily.org. >> >> > > -- > To 
> > unsubscribe email chrony-users-requ...@chrony.tuxfamily.org > with 
> > "unsubscribe" in the subject. > For help email 
> > chrony-users-requ...@chrony.tuxfamily.org > with "help" in the subject. > 
> > Trouble? Email listmas...@chrony.tuxfamily.org. > -- To unsubscribe email 
> > chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the 
> > subject. For help email chrony-users-requ...@chrony.tuxfamily.org with 
> > "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.

--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Bill Unruh]

now it seems to lock on PPS1, but I don't think PPS1 is not a valid source.


Sorry, you double negative is completely confusing. It looks to me like pps1
is a fine source and so does chrony. What problem do you have with it?



here's the results for chronyc sources:

210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
#? GPS   0   4 0  1192   -43.4s[ -43.7s] +/-  200ms
#* PPS1  7   4   37720 +9ns[ +773ns] +/-  629ns






Sent: Monday, February 05, 2018 at 6:03 AM
From: "Miroslav Lichvar" 
To: chrony-users@chrony.tuxfamily.org
Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian jessie 
with gps hat

On Fri, Feb 02, 2018 at 11:35:42PM +0100, Charles Muggen wrote:

# 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. delay 0.2
refclock SHM 1 refid PPS precision 1e-9


If you are using the SHM 1 source, which is based on PPS with gpsd,
I'd suggest to either remove the first line or add noselect to it.

You could also use the PPS device directly with SHM 0, e.g.

refclock SHM 0 offset 0.5 delay 0.2 refid NMEA noselect
refclock PPS /dev/pps0 lock NMEA refid GPS


I made a change to my /boot/config.txt
I had to add a line that says
dtoverlay=pps-gpio,gpio=4
This points the PPS server to pin 4 of the GPS HAT.

hmmm, maybe the thing is working... but should the PPS show an asterisk "*"?


How is gpsd started? With a GPIO PPS, I think it needs to be started
with both devices: serial (e.g. /dev/ttyS0) and PPS (e.g. /dev/pps0).

--
Miroslav Lichvar

--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.




--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.



--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.

Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

I changed my chrony.conf file as suggested.

# 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 offset 0.5 delay 0.2 refid NMEA noselect
refclock PPS /dev/pps0 lock NMEA refid GPS

now it seems to lock on PPS1, but I don't think PPS1 is not a valid source.
here's the results for chronyc sources:

210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample   
===
#? GPS   0   4 0  1192   -43.4s[ -43.7s] +/-  200ms
#* PPS1  7   4   37720 +9ns[ +773ns] +/-  629ns





> Sent: Monday, February 05, 2018 at 6:03 AM
> From: "Miroslav Lichvar" 
> To: chrony-users@chrony.tuxfamily.org
> Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian 
> jessie with gps hat
>
> On Fri, Feb 02, 2018 at 11:35:42PM +0100, Charles Muggen wrote:
> > # 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. delay 0.2
> > refclock SHM 1 refid PPS precision 1e-9
> 
> If you are using the SHM 1 source, which is based on PPS with gpsd,
> I'd suggest to either remove the first line or add noselect to it.
> 
> You could also use the PPS device directly with SHM 0, e.g.
> 
> refclock SHM 0 offset 0.5 delay 0.2 refid NMEA noselect
> refclock PPS /dev/pps0 lock NMEA refid GPS
> 
> > I made a change to my /boot/config.txt
> > I had to add a line that says
> > dtoverlay=pps-gpio,gpio=4
> > This points the PPS server to pin 4 of the GPS HAT.
> > 
> > hmmm, maybe the thing is working... but should the PPS show an asterisk "*"?
> 
> How is gpsd started? With a GPIO PPS, I think it needs to be started
> with both devices: serial (e.g. /dev/ttyS0) and PPS (e.g. /dev/pps0).
> 
> -- 
> Miroslav Lichvar
> 
> -- 
> To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
> with "unsubscribe" in the subject.
> For help email chrony-users-requ...@chrony.tuxfamily.org 
> with "help" in the subject.
> Trouble?  Email listmas...@chrony.tuxfamily.org.
> 
> 

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Bill Unruh]

That looks much better!


William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/

On Fri, 2 Feb 2018, Charles Muggen wrote:


Let's do a test.
I found an option to "Always send e-mails as plain text (without formatting)."

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



--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.



--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.

Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

#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. delay 0.2
refclock SHM 1 refid PPS precision 1e-9

#chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample   
===
#* GPS   0   4   37717  -6540us[  -11ms] +/-  200ms
#? PPS   0   4 0 - +0ns[   +0ns] +/-0ns

#chronyc tracking
Reference ID: 47505300 (GPS)
Stratum : 1
Ref time (UTC)  : Fri Feb 02 22:19:35 2018
System time : 0.003947824 seconds slow of NTP time
Last offset : -0.004957667 seconds
RMS offset  : 0.010333695 seconds
Frequency   : 19.195 ppm slow
Residual freq   : -1.445 ppm
Skew: 25.232 ppm
Root delay  : 0.20003 seconds
Root dispersion : 0.100304745 seconds
Update interval : 16.0 seconds
Leap status : Normal

I made a change to my /boot/config.txt
I had to add a line that says
dtoverlay=pps-gpio,gpio=4
This points the PPS server to pin 4 of the GPS HAT.

hmmm, maybe the thing is working... but should the PPS show an asterisk "*"?

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

Let's do a test.
I found an option to "Always send e-mails as plain text (without formatting)."

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



-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

My GPS HAT has a fix. I am getting NMEA messages.

gpsmon /dev/serial0 shows valid NMEA messages.

 

 

 

Sent: Friday, February 02, 2018 at 12:51 PM
From: "Bill Unruh" 
To: chrony-users@chrony.tuxfamily.org
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 _|___ Advanced Research _| Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca 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.4 seconds fast of NTP time Last offset : +0.0 seconds RMS offset  : 0.0 seconds > Frequency   : 7.218 ppm fast Residual freq   : +0.000 ppm Skew    : 0.000 ppm Root delay  : > 0.0 seconds Root dispersion : 0.0 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-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email > chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email > listmas...@chrony.tuxfamily.org. >




--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

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. 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.4 seconds fast of NTP time
Last offset     : +0.0 seconds
RMS offset      : 0.0 seconds
Frequency       : 7.218 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 0.0 seconds
Root dispersion : 0.0 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" 
To: chrony-users@chrony.tuxfamily.org
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 _|___ Advanced Research _| Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca 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.4 seconds fast of NTP time Last offset : +0.0 seconds RMS offset  : 0.0 seconds > Frequency   : 7.218 ppm fast Residual freq   : +0.000 ppm Skew    : 0.000 ppm Root delay  : > 0.0 seconds Root dispersion : 0.0 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-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email > chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email > listmas...@chrony.tuxfamily.org. >




--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

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

[Bill Unruh]

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 _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
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.4 seconds fast of NTP time Last offset : +0.0 seconds RMS 
offset  : 0.0 seconds
Frequency   : 7.218 ppm fast Residual freq   : +0.000 ppm Skew    : 
0.000 ppm Root delay  :
0.0 seconds Root dispersion : 0.0 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-requ...@chrony.tuxfamily.org with 
"unsubscribe" in the subject. For help email
chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? 
Email
listmas...@chrony.tuxfamily.org.

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

[Charles Muggen]

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.4 seconds fast of NTP time
Last offset : +0.0 seconds
RMS offset  : 0.0 seconds
Frequency   : 7.218 ppm fast
Residual freq   : +0.000 ppm
Skew    : 0.000 ppm
Root delay  : 0.0 seconds
Root dispersion : 0.0 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-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.