[ntp:questions] My Palisade Issues resolved + Checking Stability and accuracy :)

Chris H ntp at archnetnz.com
Mon Sep 27 21:58:02 UTC 2010


Hello, 
For anyone who has been following my questions, my palisade issues seem
to have been corrected now.

Just had to make a bit of a patch to the refclock_palisade.c driver, and
send a character to the device, for hardware polling.. 
We suspect that perhaps my RS422 to RS232 adaptors might not set RTS or
CTS high without data being present... 

Here is my ntpq info -=- could anyone please have a bit of a look at the
following and tell me if my ref_clock is working, and how accurate it
it.. and now how I can tell how 'stable' the clock is.

If I have not given you enough info please just let me know what you
need, and I will be more than happy to supply :)

ntpq> cv
assID=0 status=0000 clk_okay, last_clk_okay,
device="Trimble Palisade GPS", timecode="2010 270 21:51:59.428172",
poll=2787, noreply=0, badformat=0, baddata=0, fudgetime1=0.000,
stratum=0, refid=GPS, flags=0
ntpq> 

ntpq> rl
assID=0 status=0444 leap_none, sync_uhf_clock, 4 events,
event_peer/strat_chg,
version="ntpd 4.2.4p8 at 1.1612-o Sat Sep 25 09:09:32 UTC 2010 (5)",
processor="i686", system="Linux/2.6.35-19-generic", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdispersion=1.304, peer=22353,
refid=GPS, reftime=d04b90c2.78d743cb  Tue, Sep 28 2010 10:53:06.472,
poll=5, clock=d04b90c4.a6ec8d02  Tue, Sep 28 2010 10:53:08.652, state=4,
offset=-0.084, frequency=15.280, jitter=0.729, noise=0.489,
stability=0.022, tai=0
ntpq> 

ntpq> rv
assID=0 status=0444 leap_none, sync_uhf_clock, 4 events,
event_peer/strat_chg,
version="ntpd 4.2.4p8 at 1.1612-o Sat Sep 25 09:09:32 UTC 2010 (5)",
processor="i686", system="Linux/2.6.35-19-generic", leap=00, stratum=1,
precision=-19, rootdelay=0.000, rootdispersion=1.514, peer=22353,
refid=GPS, reftime=d04b90c2.78d743cb  Tue, Sep 28 2010 10:53:06.472,
poll=5, clock=d04b90d2.b5417013  Tue, Sep 28 2010 10:53:22.708, state=4,
offset=-0.084, frequency=15.280, jitter=0.729, noise=0.489,
stability=0.022, tai=0
ntpq> 


ntpq> peers
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
-warrane.connect 192.94.41.130    3 u   35   64  377   34.511    1.586
0.602
-caffeine.cc.com 203.209.212.98   3 u   30   64  377   64.355   -7.665
4.964
-pond.thecave.ws 18.26.4.105      2 u   27   64  377   85.675   -2.443
0.314
xns.creativecont 121.0.0.41       3 u   39   64  377   51.255  -23.593
13.578
-tur-dmz2.massey 131.203.16.10    2 u   28   64  377   15.298    0.769
0.500
+msltime.irl.cri .ATOM.           1 u   43   64  377   18.728   -1.113
0.389
+msltime2.irl.cr .ATOM.           1 u    5   64  377   18.158   -0.950
0.599
*GPS_PALISADE(0) .GPS.            0 l   13   16  377    0.000    0.306
0.056
ntpq> 


ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 22346  9314   yes   yes  none   outlyer   reachable  1
  2 22347  9314   yes   yes  none   outlyer   reachable  1
  3 22348  9314   yes   yes  none   outlyer   reachable  1
  4 22349  9114   yes   yes  none falsetick   reachable  1
  5 22350  9314   yes   yes  none   outlyer   reachable  1
  6 22351  9414   yes   yes  none  candidat   reachable  1
  7 22352  9414   yes   yes  none  candidat   reachable  1
  8 22353  9614   yes   yes  none  sys.peer   reachable  1
ntpq> 









More information about the questions mailing list