In article AANLkTi=ju-fv8e-q4rh3p7rpdf3cqncn7dpec9zrc...@mail.gmail.com,
Chris Albertson albertson.ch...@gmail.com writes:
What I'm looking for here is advice on what to check.
Is there anything interesting in the ntp log file?
(defaults to syslog which is usually /var/log/messages)
Is there
On 2/1/2011 10:57 PM, Chris Albertson wrote:
On Tue, Feb 1, 2011 at 5:50 PM, Mike Smi...@flatsurface.com wrote:
Chris, I've seen similar when using an Atom (PPS) refclock linked to another
refclock (using the prefer keyword) which delivers time via a serial
character stream. The PPS is, as it
At 10:57 PM 2/1/2011, Chris Albertson wrote...
I could have a plumbing pproblem as the UT+ is 3rd floor and the
computer is 1st floor with 75 feet of RS232 over cat-5 between.
Has the PPS been converted to RS232, or are you simply using the TTL
level PPS signal?
The docs say it's a 5V
So many good ideas. I'll try and answer them all.
(1) cable length. At this point I don't care about delay of 75 ns.
But there might be attenuation of the signal. I've not measured it
yet but I doubt it because (a) the serial messages are working fine
and are on the same cable and (b) I'm
On 2011-02-02, Richard B. Gilbert rgilber...@comcast.net wrote:
On 2/1/2011 10:57 PM, Chris Albertson wrote:
On Tue, Feb 1, 2011 at 5:50 PM, Mike Smi...@flatsurface.com wrote:
The rule of thumb for propagation in copper cable is one nanosecond
Actually no, that is the rule for vacuum.
Mike S wrote:
Chris Albertson wrote...
I could have a plumbing pproblem as the UT+ is
3rd floor and the computer is 1st floor with 75
feet of RS232 over cat-5 between.
Has the PPS been converted to RS232, or are you simply
using the TTL level PPS signal?
The docs say it's a 5V signal,
On Wed, Feb 2, 2011 at 12:26 PM, E-Mail Sent to this address will be
added to the BlackLists Null@blacklist.anitech-systems.invalid
wrote:
Mike S wrote:
Chris Albertson wrote...
I could have a plumbing pproblem as the UT+ is
3rd floor and the computer is 1st floor with 75
feet of RS232 over
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
On 2/1/2011 12:44 AM, 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
On 2/1/2011 12:44 AM, 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
On Tue, Feb 1, 2011 at 4:29 PM, Richard B. Gilbert
rgilber...@comcast.net wrote:
The 177 suggests that NTPD was recently started
Can you suggest why the GPS is not being polled consistently?
It was running for more than 24 hours, maybe 36 hours.
During those hours it would display 377
177 may also mean that about 8 minutes ago (assuming a 64 second poll
interval) a sample was missed.
And while it can take up to a half an hour for ntpd to sync, BCP is to
use 'iburst' on the server/peer lines, and that will get ntpd sync'd in
about 11 seconds' time.
H
At 08:06 PM 2/1/2011, Chris Albertson wrote...
During those hours it would display 377 and then revert back to what
I posted.
What I'm looking for here is advice on what to check.
Chris, I've seen similar when using an Atom (PPS) refclock linked to
another refclock (using the prefer
I suspect now the PPS is failing somehow. I can see the serial data
appear in the log every second. But mixed in there is a error message
that reads ONCORE[0]: ONCORE: oncore_get_timestamp, error serial
pps. I'll likey grep the code for the error string and see what
it's doing.
I just bught
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
15 matches
Mail list logo