Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
PPS_SYNC and NTP refclocks
Is anyone successfully running a stratum 1 server using NetBSD current?
Having successfully run a stratum 1 server in $DAYJOB 6 years ago on NetBSD 4
using Trimble GPS hardware, I thought I would try using a more modern release
and a recently acquired Oncore GPS receiver. I hooked up the hardware to an
old Pentium 4 PC running a recent snapshot (6.99.10/i386). GPS attached to
/dev/tty00 via a level converter with PPS on DCD
/dev/tty00 syslinked to /dev/oncore.serial.0 & /dev/oncore.pps.0
Generic kernel compiled with additional PPS_SYNC option
/etc/ntp.oncore.0 =>
MODE 1
LAT 53 25 33.01
LONG 3 2 32.78
HT 109.41M
TRAIM NO
HARDPPS
SHMEM /var/log/ntpstats/ONCORE.0
/etc/ntp.conf =>
pidfile /var/run/ntpd.pid
driftfile /var/db/ntp.drift
logconfig -syncstatus
tos minsane 2
statistics loopstats
statsdir /var/log/ntpstats/
filegen peerstats file peers type day link enable
filegen loopstats file loops type day link enable
server 127.127.30.0
server nero.grnet.gr
server hora.roa.es
server ntp0.fau.de
server ntp2.oma.be
server canon.inria.fr
Bringing up ntp, the refclock is found and is being read, but the pps doesn't
seem to be working. There is definately a pulse on DCD.
Aug 7 23:04:29 dev ntpd[105]: ntpd 4.2.6p5-o Wed Feb 1 07:49:06 UTC 2012
(import)
Aug 7 23:04:29 dev ntpd[754]: proto: precision = 2.514 usec
Aug 7 23:04:29 dev ntpd[754]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen and drop on 1 v6wildcard :: UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen normally on 2 fxp0
fe80::203:47ff:fee6:2e17 UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen normally on 3 fxp0 192.168.0.3 UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen normally on 4 lo0 127.0.0.1 UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen normally on 5 lo0 ::1 UDP 123
Aug 7 23:04:29 dev ntpd[754]: Listen normally on 6 lo0 fe80::1 UDP 123
Aug 7 23:04:29 dev ntpd[754]: peers refreshed
Aug 7 23:04:29 dev ntpd[754]: Listening on routing socket on fd #27 for
interface updates
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: ONCORE DRIVER -- CONFIGURING
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: state = ONCORE_NO_IDEA
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: Input mode = 1
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: Initializing timing to Assert.
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: HARDPPS Set.
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: SHMEM (size = 3628) is CONFIGURED
and available as /var/log/ntpstats/ONCORE.0
Aug 7 23:04:29 dev ntpd[754]: ONCORE[0]: state = ONCORE_CHECK_ID
Aug 7 23:04:35 dev ntpd[754]: ONCORE[0]: Oncore: Resend @@Cj
Aug 7 23:04:35 dev ntpd[754]: ONCORE[0]: Oncore: Resend @@Cj
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: @@Cj
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: COPYRIGHT 1991-1996 MOTOROLA INC.
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: SFTW P/N # 98-P36847P
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: SOFTWARE VER # 1
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: SOFTWARE REV # 7
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: SOFTWARE DATE AUG 20 1997
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: MODEL # R1121N1145
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: HWDR P/N # 1
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: SERIAL # R013RV
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: MANUFACTUR DATE 7G23
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]:
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: This looks like an Oncore GT with
version 1.7 firmware.
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: Channels = 8, TRAIM = OFF
Aug 7 23:04:52 dev ntpd[754]: ONCORE[0]: state = ONCORE_CHECK_CHAN
Aug 7 23:04:57 dev ntpd[754]: ONCORE[0]: Input says chan = -1
Aug 7 23:04:57 dev ntpd[754]: ONCORE[0]: Model # says chan = 8
Aug 7 23:04:57 dev ntpd[754]: ONCORE[0]: Testing says chan = 8
Aug 7 23:04:57 dev ntpd[754]: ONCORE[0]: Using chan = 8
Aug 7 23:04:57 dev ntpd[754]: ONCORE[0]: state = ONCORE_HAVE_CHAN
Aug 7 23:04:58 dev ntpd[754]: ONCORE[0]: state = ONCORE_TEST_SENT
Aug 7 23:05:08 dev ntpd[754]: ONCORE[0]: GPS antenna: OK
Aug 7 23:05:08 dev ntpd[754]: ONCORE[0]: state = ONCORE_INIT
Aug 7 23:05:09 dev ntpd[754]: ONCORE[0]: Setting Posn from input data
Aug 7 23:05:09 dev ntpd[754]: ONCORE[0]: state = ONCORE_ALMANAC
Aug 7 23:05:12 dev ntpd[754]: ONCORE[0]: Posn:
Aug 7 23:05:12 dev ntpd[754]: ONCORE[0]: Lat = N 53.4258361deg, Long = E
3.0424389deg, Alt = 109.41m (358.96ft) GPS
Aug 7 23:05:12 dev ntpd[754]: ONCORE[0]: Lat = N 53deg 25.5502m, Long = E
3deg 2.54633m, Alt = 109.41m ( 358.96ft) GPS
Aug 7 23:05:12 dev ntpd[754]: ONCORE[0]: Lat = N 53deg 25m 33.01s, Long = E
3deg 2m 32.78s, Alt = 109.41m ( 358.96ft) GPS
Aug 7 23:05:12 dev ntpd[754]: ONCORE[0]: Cable delay is set to 0 ns
Aug 7 23:05:14 dev ntpd[754]: ONCORE[0]: Have now loaded an ALMANAC
Aug 7 23:05:14 dev ntpd[754]: ONCORE[0]: state = ONCORE_RUN
Aug 7 23:05:14 dev ntpd[754]: ONCORE[0]: SSstate = ONCORE_SS_DONE
Aug 7 23:05:15 dev ntpd[754]: ONCORE[0]: ONCORE: Detected TRAIM, TRAIM = ON
Aug 7 23:05:15 dev ntpd[754]: ONCORE[0]: Input says TRAIM = 0
Aug 7 23:05:15 dev ntpd[754]: ONCORE[0]: Model # says TRAIM = 0
Aug 7 23:05:15 dev ntpd[754]: ONCORE[0]: Testing says TRAIM = 1
Aug 7 23:05:15 dev ntpd[754]: ONCORE[0]: Using TRAIM = 0
Aug 7 23:05:16 dev ntpd[754]: ONCORE[0]: 3553365898.121663721 2012 220 22 5
16 58 rstat 08 dop 0.0 nsat 0,4 traim 0,x,x sigma xx neg-sawtooth xxx sat
85780000
Aug 7 23:05:18 dev ntpd[754]: ONCORE[0]: 3553365918.050198554 2012 220 22 5
18 18 rstat 08 dop 0.0 nsat 0,4 traim 0,x,x sigma xx neg-sawtooth xxx sat
85780000
Aug 7 23:05:19 dev ntpd[754]: ONCORE[0]: ONCORE: oncore_get_timestamp, error
serial pps
Aug 7 23:05:20 dev ntpd[754]: ONCORE[0]: 3553365920.050234931 2012 220 22 5
20 20 rstat 08 dop 0.0 nsat 10,4 traim 0,x,x sigma xx neg-sawtooth xxx sat
85783000
Aug 7 23:05:21 dev ntpd[754]: ONCORE[0]: ONCORE: oncore_get_timestamp, error
serial pps
Aug 7 23:05:24 dev syslogd[216]: last message repeated 2 times
...
Keeping the same hardware I swapped the disk caddy and loaded FreeBSD 9, same
version of ntp, same ntp.conf, ntp.oncore.0 etc. That seemed to come up
without any issues and although the loopstats don't look wonderful it does
seem to handling the pulses. dmesg similar to above without the 'error serial
pps' messages.
Any clues?
Cheers,
Dave
--
=====================================================================
Phone: 07805784357
Open Source O/S: www.netbsd.org
Caving: http://www.wirralcavinggroup.org.uk
=====================================================================
Home |
Main Index |
Thread Index |
Old Index