Mark C. Stephens wrote:
This is what I had with no time1:
remote refid st t when poll reach delay offset jitter
==============================================================================
oPPS(0) .PPS. 0 l 13 16 377 0.000 -0.007 0.005
*GPS_PALISADE(0) .GPS. 0 l 12 16 377 0.000 0.008 0.003
And this is what I get with time1 of 0.015
remote refid st t when poll reach delay offset jitter
==============================================================================
oPPS(0) .PPS. 0 l 10 16 377 0.000 0.012 0.005
*GPS_PALISADE(0) .GPS. 0 l 10 16 377 0.000 15.031 0.008
Seems I have put myself out 15 ms by adding time1 0.015
Also in my ntp.conf I have:
saveconfigdir /etc/ntpd
however if I do a ntpq -c saveconfig
it comes back asking for a filename.
Have I not compiled saveconfig mechanism in or something?
-----Original Message-----
From: questions-bounces+marks=non-stop.com...@lists.ntp.org
[mailto:questions-bounces+marks=non-stop.com...@lists.ntp.org] On Behalf Of
E-Mail Sent to this address will be added to the BlackLists
Sent: Friday, 16 August 2013 1:43 PM
To: questions@lists.ntp.org
Subject: Re: Acutime Gold
Mark C. Stephens wrote:
If I have palisade prefer PPS comes up fine within a minute or so.
When I tried making pps prefer it got an x beside the PPS.
I waited for an hour or 2 but it was still marked bad.
Not sure what's going on there..
this is the relevant part of the config:
# PPS
server 127.127.22.0 minpoll 4 maxpoll 4 # prefer # noselect fudge
127.127.22.0 flag2 0 flag3 1 flag4 0 # time1 0.000016
# palisade on ttyS0
server 127.127.29.0 minpoll 4 maxpoll 4 prefer fudge 127.127.29.0
flag2 0 # time1 0.000015
fudge 127.127.29.0 time1 0.015 # milli-seconds, not micro-seconds
As you can see I have tried different time1 for both clocks.
You don't need to get a very accurate time from the GPS as the
PPS when present sets the offset. Some GPS are a disaster when
used to set a clock and several of my devices have variations
of > +/- 50 ms. Your GPS_PALISADE is very accurate by comparison.
eg.
fudge 127.127.28.0 stratum 4 time1 0.024 refid MSFa
fudge 127.127.20.2 stratum 6 time2 0.417 refid GPSb
Note that I don't really want either to be used for offset as
neither is as good as internet time.
If you really want to fudge out the time offset of GPS_PALISADE
you would need 0.000008 (s) or better run peer_summary for a
while so you can get an average in case that value varies.
David
I am not familiar with the mindist option.
tos mindist 0.020
--
E-Mail Sent to this address <blackl...@anitech-systems.com>
will be added to the BlackLists.
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
