[time-nuts] leontp offset?
tshoppa at gmail.com
Sat Oct 15 05:09:10 EDT 2016
Check the Arbiter for anomalous "Cable Delay" or "Clock Offset" settings.
Maybe they accidentally got set to 9999999ns instead of zero.
Page 38 in this manual:
On Fri, Oct 14, 2016 at 8:31 PM, gmx tallahassee <gmx.tallahassee at gmail.com>
> Hi all,
> I'm checking out the leontp ntp time server (leontp.com). After a week of
> use I am getting the following ntp -q output:
> $ ntpq -pn
> remote refid st t when poll reach delay offset
> *172.17.21.11 .GPS. 1 u 13 16 377 0.137 0.077
> 0.054 <- Arbiter 1084C GPS Clock
> +172.17.21.12 .GPS. 1 u 11 16 377 0.101 0.085
> 0.174 <- Arbiter 1084C GPS Clock
> x172.17.21.233 .GPS. 1 u 11 16 377 0.071 9.760
> 0.061 <- LeoNTP
> the offset of the leontp device from the other clocks has consistently been
> in the 9.5 -10.5 range. since I'm measuring all three sources from the
> same (EL7) computer, I would expect that the offset of the leontp unit to
> converge to be in the close neighborhood of the offsets of the arbiters.
> It has not converged, instead maintaining the ~10ms offset.
> 172.17.21.11 is approx 400M away through two Cisco 3750G switches no
> 172.17.21.12 is in the same rack as the leoNTP unit and plugged into the
> same 3750G switch
> Antenna location for the .12 arbiter and the leontp is on the same rung of
> the same tower. Tower has clear horizon to horizon view. cable runs are
> the same (obviously).
> I did run with the included puck in my south facing office window (rather
> than the GPS antenna on the tower) for a couple of days when I first got
> the unit. The offset behaviour was the same.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> and follow the instructions there.
More information about the time-nuts