On Mar 29, 5:12 am, mi...@udel.edu (David Mills) wrote:
John,
The intended design to detect and suppress bad reference/PPS clocks is
at least two additional sources, that do not have to be reference
clocks. If the reference/PPS clock sails to the sunset, the selection
algorithm will vote it
On Mar 29, 8:25 pm, Unruh unruh-s...@physics.ubc.ca wrote:
Eg, no fudge1, do not trust it without a peer to number the seconds, fudge1 0
trust it forever, fudge1 86400
trust it for a day, etc.
In all cases do not trust it until the system clock has been brought within
.25
sec, say, by
On Mar 26, 5:46 am, Unruh unruh-s...@physics.ubc.ca wrote:
So, I have PPS running the shm refclock, with the seconds supplied by the
local clock (ie the reading from the system clock) and the usec from the
PPS signal. Since I do not expect the local clock to suddenly shift by a
second, its
.
Dave
alkope...@googlemail.com wrote:
On Mar 24, 10:29 pm, mi...@udel.edu (David Mills) wrote:
alkopedia,
Your PPS signal is working, but not necesarily discipining thekernel. I
can't help you with Linux.
Dave
Thanks for your help anyway. The PPS is working, that's right. But let
me
On Mar 26, 12:48 am, Unruh unruh-s...@physics.ubc.ca wrote:
However if the only concern was losing PPS discipline due to prefer peer
problems, then I agree this is tangential.
Yes, it was ;-)
I think he's monitoring the self-reported offsets between the NTP
disciplined clock and the local
On Mar 23, 5:00 am, Dave Hart daveh...@gmail.com wrote:
Dr. Mills,
Thank you for your confirmation. The original poster should be
satisfied, assuming their kernel time is being disciplined directly by
their cesium standard.
What do I have to do to use the kernel discipline?
At the moment
Hi
My setup is as follows:
Server A --- GPS
|
|
Server B --- HP cesium frequency normal
Server A gets it's timestamps from GPS.
Server B gets it's timestamps from Server A and PPS from the HP
cesium. Server A is marked as prefer because otherwise PPS won't work.
My problem is:
If Server A
Hi
Where can I find a detailed description of all these values provided
by ntpq -c rv?
What do you think which values are important for logging and graphical
display to see problems fast? Here is an example
http://www.wraith.sf.ca.us/ntp/rrd/index.html but I'm not sure what is
important because I
On Jan 13, 9:29 pm, David Woolley
da...@ex.djwhome.demon.co.uk.invalid wrote:
You should be very wary of any frequently written file on flash RAM.
Even if you constantly write with maximum speed to the SD card it will
take around 2 years until the minimum write cycle count is reached.
On Jan 11, 6:52 pm, Unruh unruh-s...@physics.ubc.ca wrote:
And alter your script so that it does not try to write any file on today or
earlier. Or test to see if peerstats and peerstats.20090201 are the same
file (same inode with ls -li)
This is a good idea. I have changed my script and it
On Jan 10, 8:23 pm, Unruh unruh-s...@physics.ubc.ca wrote:
What version of ntp are you running? I have 4.2.4p4 and it creates a new
set of statistics files every day, saving the old ones in the form
/var/log/ntp/peerstats.20090101 /var/log/ntp/peerstats.20090106
As far as I can tell ntp
On Jan 9, 11:19 am, alkope...@googlemail.com
alkope...@googlemail.com wrote:
Thanks. Now I have in my ntp.conf:
# statistics
statistics clockstats cryptostats loopstats peerstats rawstats
sysstats
filegen clockstats file clockstats type day enable
filegen cryptostats file cryptostats type
On Jan 9, 3:10 am, Richard B. Gilbert rgilber...@comcast.net
wrote:
This is the (AFAIK) documented and supported method of getting NTP to
start a new file every day.
Eventually, you will have remove the old files or buy a new disk drive! ;-)
You put it in your NTP.CONF file.
Thanks. Now I
Hello
I'm using a script that moves the ntp stats (cryptostats.20090107,
loopstats.20090107, ...) files from the ntp server to a fileserver at
00:40 AM. It works fine, except for the cryptostats.mmdd file. It
seems the ntpd has this file still opened and when I move it away it
will produce a
On 8 Jan., 15:42, Richard B. Gilbert rgilber...@comcast.net wrote:
Is that 00:40 AM local time? Or UTC?
Have you tried using:
It's UTC and ntpd is version 4.2.4p5
filegen cryptostats file cryptostats type day enable ??
What do you mean?
___
On Dec 18, 7:56 pm, Unruh unruh-s...@physics.ubc.ca wrote:
That you PPS has an offset of 20-40usec does
surprize me. It should be much better than that (2-4ms is more typical)
Running time was not long enough at that point. In the last 12 hours I
have these values:
Min: -4 us, Max: +6.9 us,
On Dec 18, 10:08 am, Martin Burnicki martin.burni...@meinberg.de
wrote:
Hi,
The PCI511 card decodes the AM signal from DCF77 only. Due to the
characteristics of the AM signal the accuracy of the PCI511 card is only in
the range of a few milliseconds, while the GPS card provides an accuracy
On Dec 18, 12:47 pm, alkope...@googlemail.com
alkope...@googlemail.com wrote:
I did not wonder about the offset between gps
and pps
Should be:
I did not wonder about the offset between gps and dcf :-)
___
questions mailing list
questions
On Dec 17, 6:57 pm, ober...@es.net (Kevin Oberman) wrote:
The time to process the time string from the clock is long and fairly
slow. The PPS is short and fast. As the documentation states, the PPS
signal trains the clock.
OK, my first example has an error. Of course I need the same fudge at
Hi
One of my ntp servers (moni0) uses another ntp server (gps) as time
source. The gps server gets it's time by gps ;-)
As you can see in this graph the offset is quite constant:
http://img-up.net/img/gps-jitter0PsFiy.png
But I wonder why it shows such big jitter values? I thought jitter is
only
Hi
I have 2 ntp servers running Linux with LinuxPPS patch. Number one
uses a Meinberg PCI511 v1.00 as time source, number two uses a
Meinberg GPS170PCI v1.10.
On both machines ntp is configured to use the Meinberg refclock
(127.127.8.0) and furthermore the Meinberg PPS outputs are connected
to the
21 matches
Mail list logo
