On Mon, 30 Jan 2006, Nelson Minar <[EMAIL PROTECTED]> wrote:
Chris Hastie wrote:
I must say, things don't look great:
ntpq -p ntp1.npl.co.uk
remote refid st t when poll reach delay
offset jitter
============================================================================== LOCAL(0) .GPS. 0 - - 64 0 0.000 0.000
0.000
*139.143.49.13 .1PPS. 1 - 52 64 357 9.230
-8.911 4.270
+139.143.49.18 .1PPS. 1 - 21 64 377 9.231
-8.447 1.395
Huh, that's not what I'm seeing. Maybe they just changed it? This is
from the US:
$ ntpdate -q ntp1.npl.co.uk
server 139.143.5.57, stratum 2, offset 0.003235, delay 0.14064
$ ntpq -p ntp1.npl.co.uk
remote refid st t when poll reach delay offset
jitter
==============================================================================
LOCAL(0) .GPS. 0 - - 64 0 0.000 0.000
0.000
*139.143.49.13 .1PPS. 1 - 56 64 377 9.230 -1.772
1.760
+139.143.49.18 .1PPS. 1 - 29 64 377 9.230 -3.201
1.161
Well exactly. Earlier this afternoon I tried and the reach was at 0 and
nothing
synced. A minute later it had synced and the offset was very respectable, but
it quickly slipped away. I'm now seeing
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .GPS. 0 - - 64 0 0.000 0.000 0.000
*139.143.49.13 .1PPS. 1 - 54 64 377 9.230 -7.856 3.844
+139.143.49.18 .1PPS. 1 - 22 64 377 9.228 -7.256 2.515
so it looks like it's see-sawing all over the place. Whoever said if NPL can't
get it right who can may have been misplaced in their faith, by the look of
things! I think I'll stick with my MSF receiver as my preferred way to
get time
from NPL.
--
Chris Hastie
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
