Hi Jason,
Not sure if you have checked this, but I have found that I can see
100us or more of delta if the dedicated clock has not done a position
average run, or has bad position information set.
So if you trust your 4501s to be providing the better time, you might
want to look for other settings in the TS2100s in addition to cable
delays.
--
Russell
At 11:05 AM -0500 2010/11/01, Jason Rabel wrote:
I hope this doesn't get mangled too much via email... Below is an
output of "ntpq -p" on one machine.
remote refid st t when poll reach delay offset jitter
==============================================================================
*NET4501-1 .GPS. 1 u 36 64 377 0.724 0.022 0.100
+NET4501-2 .GPS. 1 u 22 64 377 0.801 0.038 0.132
+PRAECIS .GPS. 1 u 14 64 377 0.740 0.097 0.034
-TS2100-1 .GPS. 1 u 50 64 377 4.995 -0.362 0.030
-TS2100-2 .GPS. 1 u 17 64 377 4.966 -0.331 0.035
My two TS2100's always seem to be slightly "off" compared to my
other time servers... Even after I've had to power cycle all my
equipment. Four of the five devices are currently on the same GPS
antenna and have more or less the same length of cable. Same four
go to the same switch and such.
Does a negative offset mean it is in the future? If so, I'm guessing
I need to dig and find an offset for cable delay (or similar)
in the TS2100? I seem to recall that the standard package came with
50' or 150' of cable, but even that pre-factored delay wouldn't
equate to ~300-400us would it?
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
