Chris Albertson wrote:
I just set up a new Linux based stratum 1 server using a Motorola
Oncore UT ref. clock. Seems to mostly be working except for a
periodic anomaly Look at this output from ntpq:
chris@atom:~$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
oGPS_ONCORE(0) .GPS. 0 l 6 16 177 0.000 1.401 377.675
+dp.cx 128.227.205.3 2 u 39 64 377 86.133 -4.062 0.423
+64.73.32.134 129.6.15.28 2 u 50 64 377 75.212 1.608 0.804
The I do nothing but wait and try again and get this
==============================================================================
*GPS_ONCORE(0) .GPS. 0 l 64 16 360 0.000 0.816 0.115
+dp.cx 128.227.205.3 2 u 16 64 377 85.835 -3.523 0.642
-64.73.32.134 129.6.15.28 2 u 24 64 377 73.538 1.635 0.869
This is really bad reach, I'm guessing the top result is from just after
recovering the connection.
Some times the offset and jitter will be as low as 0.004 and 0.002
This is the normal status for an Oncore, anything above 10 us is a bad sign.
In the clockstats file it looks OK I see many lines that, I think say
the GPS sees 5 to 8 satellites with good signal
For the same time period as the loss of reach?
55593 20317.217 127.127.30.0 3505527516.999033699 2011 32 5 38 37 36
rstat 08 dop 0.0 nsat 12,7 traim 1,0,0 sigma 44 neg-sawtooth -30
sat 88088878
55593 20318.217 127.127.30.0 3505527517.999037365 2011 32 5 38 38 37
rstat 08 dop 0.0 nsat 12,7 traim 1,0,0 sigma 44 neg-sawtooth -41
sat 88088878
Have you put your Oncore into Zero-D mode yet?
If you do that, maybe after a day or two of position averaging, your
reach should stay 377 as long as at least one sat is visible!
Terje
--
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
