RCIM User’s Guide
2
-
20
#
/usr/sbin/ntpq -np
remote refid
st
t
when
poll
reach
delay
offset
jitter
========================================================================================
xns2.medbanner.c
192.43.244.18
2
u
33
64
377
72.443
-2.897
11.235
+toshi.keneli.or .GPS.
1
u
43 64 377 27.915
0.938 2.075
-216.56.81.86 193.131.101.50
3
u
33
64
377
49.388
-0.579
2.710
+new.localdomain .GPS.
1
u
42 64 377 0.182 0.010 0.020
*GENERIC(0) .GPS.
0
l
46
64
377
0.000
0.000
0.001
The output shows how the system time compares to other time sources. This includes the
GPS receiver and other time servers.
The column labeled
remote
is the hostname of the timeserver. The system
new.localdomain
is a local network time server;
GENERIC(0)
is the GPS attached to
the RCIM. The other lines are time servers assigned by pool.ntp.org. The first column
indicates which servers are being selected for synchronization. The '*' in front of
GENERIC(0)
indicates that the RCIM GPS receiver is being used as the system peer.
The columns
delay
,
offset
, and
jitter
are all times in milliseconds. The offset is
the difference between the local system time and the time source. In this case we are
synchronized to the GPS receiver to microsecond accuracy.
The
delay
field is the measured network delay to exchange the time with the remote
server.
The
jitter
measures the difference between offset values from the same source.
The
refid
indicates where the remote system gets its time.
The
st
column is the stratum number. A stratum zero system should have a direct
connection to an authoritative source.
The
poll
column shows how frequently this server is being polled. The
when
column is
the time in seconds since the last poll.
The
reach
column is a bitmap in octal which shows if recent polls have been successful.
The value 377 would indicate that the last 8 polls suceeded.
Another indicator is through the
ntpq
clockvar
command:
#
/usr/sbin/ntpq
ntpq>
clockvar
assID=0 status=0003 clk_okay, last_clk_fault,
device="Trimble GPS (TSIP) receiver", timecode="\x10\xff\x02\x10",
poll=52, noreply=0, badformat=0, baddata=0, fudgetime1=20.000,
stratum=0, refid=GPS, flags=4,
refclock_ppstime="c66be732.00000000 Tue, Jun 28 2005 15:11:46.000",
refclock_time="c66be734.03ffffff Tue, Jun 28 2005 15:11:48.015",
refclock_status="TIME CODE; PPS; POSITION; (LEAP INDICATION; PPS SIGNAL; POSITION)",
refclock_format="Trimble TSIP",
refclock_states="*NOMINAL: 00:54:26 (98.04%); NO RESPONSE: 00:00:02 (0.06%); FAULT:
00:01:03 (1.89%); running time: 00:55:31",
trimble_tracking_status[08]="ch=4, acq=ACQ, eph=19, signal_level= 6.40, elevation= 9.12,
azimuth= 34.35, collecting data",
trimble_satview="mode: 2D-AUTO, PDOP 8.96, HDOP 8.91, VDOP 1.00, TDOP 2.90, 3 satellites
Summary of Contents for RCIM
Page 1: ...Real Time Clock and Interrupt Module RCIM User s Guide 0898007 1000 March 2021...
Page 10: ...RCIM User s Guide 1 4...
Page 32: ...RCIM User s Guide 2 22...
Page 80: ...RCIM User s Guide A 28...
Page 102: ...RCIM User s Guide C 2...