On 28/10/2012 20:50, A C wrote:
[]
If your PPS signal is on /dev/pps0 as you describe, add the ATOM driver
(number 22) in addition to your SHM (gpsd) driver and it will be fine:
This is exactly how I have my own server running (but not on an R-pi).
PPS comes in via one port, gpsd SHM comes in from another port and two
drivers (22 and 28) take care of gluing them together.
[]
server 127.127.22.0 minpoll 4 maxpoll 4
A C thanks for your reply. I added the 127.127.22.0 server and
removed the 127.127.28.1 server, but I don't see any line relating to
the ATOM driver in the ntpq -p output. Should I? Perhaps the "*" will
simply turn to a "o" after enough time? Makes me wonder whether my NTP
has been compiled with ATOM support - I'm using the one which comes with
the current Linux for the Raspberry Pi.
server 127.127.28.0 minpoll 4 maxpoll 4
fudge 127.127.28.0 time1 +0.350 refid GPS stratum 15
server 127.127.22.0 minpoll 4 maxpoll 4
fudge 127.127.22.0 refid PPS
server 192.168.0.3 minpoll 5 maxpoll 5 iburst prefer
server 192.168.0.2 minpoll 5 maxpoll 5 iburst
server 192.168.0.7 minpoll 5 maxpoll 5 iburst
pool uk.pool.ntp.org minpoll 10 iburst
C:\Users\David>ntpq -p 192.168.0.14
remote refid st t when poll reach delay offset
jitter
==============================================================================
xSHM(0) .GPS. 15 l 8 16 377 0.000 11.801
5.676
*pixie .PPS. 1 u 21 32 377 0.505 -3.762
1.053
+FEENIX .PPS. 1 u 19 32 377 0.532 -3.063
0.701
+Stamsund .PPS. 1 u 23 32 377 0.542 -3.183
0.628
-dns0.rmplc.co.u 193.62.22.74 2 u 252 1024 1 20.971 0.201
5.270
server1.terrybu .INIT. 16 u - 1024 0 0.000 0.000
0.000
xpanzer.charliec 252.102.21.12 4 u 250 1024 1 111.728 16.757
6.968
time.videxio.ne .INIT. 16 u - 1024 0 0.000 0.000
0.000
--
Cheers,
David
Web: http://www.satsignal.eu
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
