Ralph,
On Tue, Feb 12, 2013 at 6:04 AM, Ralph Aichinger <ra...@pangea.at> wrote:
> Does this look sane to you for a Raspberry Pi with a
> Sure Electronics board and PPS enabled? It looks fine to me,
> I just want to confirm that people more experienced than me
> see it the same way.
>
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> +217.19.37.26 .ATOM. 1 u 11 64 377 19.983 1.585 0.956
> *ts1.univie.ac.a .PPS. 1 u 14 64 377 13.653 2.661 1.955
> -212.33.33.36 131.188.3.220 2 u 14 64 377 8.071 -2.072 1.823
> +ts2.univie.ac.a .PPS. 1 u 19 64 377 13.749 1.864 2.282
> oGPS_NMEA(0) .GPS. 0 l 3 16 377 0.000 -0.005 0.001
>
I would expect to see a PPS line if you have PPS up and working
correctly, this is what I see on my RPi.
remote refid st t when poll reach delay offset jitter
==============================================================================
*GPS_NMEA(0) .GPS. 0 l 5 8 377 0.000 -97.821 35.442
oPPS(0) .PPS. 0 l 14 16 377 0.000 -0.003 0.002
+nist1-la.ustimi .ACTS. 1 u 18 64 377 34.135 11.500 1.210
+nist1-lv.ustimi .ACTS. 1 u 21 64 377 32.048 -3.096 1.236
+nist1-sj.ustimi .ACTS. 1 u 57 64 377 42.007 7.540 0.772
+clock.team-cymr 204.123.2.72 2 u 22 64 377 70.763 5.496 0.946
+linode.aput.net 10.0.0.250 3 u 56 64 377 23.727 1.156 1.104
+ntp0.cis.strath 140.203.204.77 2 u 42 64 377 171.100 2.239 2.041
+ns3.customer-re 192.53.103.108 2 u 40 64 377 187.250 15.373 0.418
> In
>
> root@pi:/home/ralph# ntpq -c rv localhost
> associd=0 status=0415 leap_none, sync_uhf_radio, 1 event, clock_sync,
> version="ntpd 4.2.6p5@1.2349 Tue Feb 12 11:35:08 UTC 2013 (1)",
> processor="armv6l", system="Linux/3.6.11", leap=00, stratum=1,
> precision=-20, rootdelay=0.000, rootdisp=0.388, refid=GPS,
> reftime=d4c4c966.1eca9efd Tue, Feb 12 2013 15:00:06.120,
> clock=d4c4c970.3c484545 Tue, Feb 12 2013 15:00:16.235, peer=58223, tc=4,
> mintc=3, offset=-0.005, frequency=-21.037, sys_jitter=0.001,
> clk_jitter=0.001, clk_wander=0.001
>
>
This is mine:
associd=0 status=0115 leap_none, sync_pps, 1 event, clock_sync,
version="ntpd 4.2.7p347@1.2483 Sat Jan 12 07:12:20 UTC 2013 (1)",
processor="armv6l", system="Linux/3.6.1+", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdisp=500.045, refid=PPS,
reftime=d4c4e26b.6e1eaad0 Tue, Feb 12 2013 7:46:51.430,
clock=d4c4e26e.efc5983d Tue, Feb 12 2013 7:46:54.936, peer=3436, tc=4,
mintc=3, offset=-0.002504, frequency=23.052, sys_jitter=0.001907,
clk_jitter=0.000, clk_wander=0.001
> I do not see any "kern", as described by some tutorials. Should I
> worry about that? Cf. eg.:
>
> http://www.satsignal.eu/ntp/Raspberry-Pi-NTP.html
>
>
>
> The relevant section of /etc/ntpd.conf is:
>
> server bevtime1.metrologie.at iburst
> server ts1.univie.ac.at iburst
> server ntp.liwest.at iburst
> server ts2.univie.ac.at iburst
>
> server 127.127.20.0 mode 24 minpoll 4 maxpoll 4
> fudge 127.127.20.0 time2 0.384 flag1 1
>
You seem to be missing your PPS driver and should have something
similar to this.
server 127.127.20.0 mode 16 minpoll 3 iburst prefer
fudge 127.127.20.0 flag1 0 time2 0.400
server 127.127.22.0 minpoll 4 maxpoll 4
fudge 127.127.22.0 flag3 1 flag4 1
make sure you are loading the pps_gpio module for your PPS to work.
> TIA
> /ralph
>
> _______________________________________________
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
James
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
