|Re: [chrony-users] Setting up Chrony with PPS|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Sun, Apr 10, 2016 at 07:34:53PM -0700, Deven Hickingbotham wrote:
> I thought I had chrony 2.3 running on my Raspberry Pi's, but now PPS doesn't
> seem to be working. I get the same results described below on two different
> systems running Jessie.
> Note that PPS Freq Skew and Std Dev are 2000.000 and 4000ms (and these
> values don't change on successive runs of sourcestats), so I assume I've
> screwed something up, but it is not clear to me what exactly.
Hm, did the configuration of the GPS change? Maybe it's giving fewer
NMEA sentences than before? It looks like the NMEA samples are now
~400 ms off from the expected offset and PPS can't lock to them.
You could try changing the SHM offset to 0.1 and maybe increase the
delay to 0.6 or so, but I'm not sure if that will be enough if the
NMEA offset is changing so much over time.
> 210 Number of sources = 6
> Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
> PPS 0 0 0 +0.000 2000.000 +0ns 4000ms
> NMEA 9 4 129 +11.345 48.130 -417ms 1011us
> blue.1e400.net 20 15 35m +0.169 1.225 -2053us 891us
> four10.gac.edu 21 12 42m -0.366 2.259 -3534us 1394us
> 188.8.131.52 20 12 38m +0.126 1.410 +4425us 1083us
> clock.sjc.he.net 21 10 41m -0.186 1.548 -3355us 1079us
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.