On 2013-08-25, Ron Hahn (EI2JP) <[email protected]> wrote: > Hello, > > I am trying to get an Oncore GPS board to PPS a FreeBSD 8.3 > installation. Originally I was using a Sure GPS board and now I want > the better Oncore board to be working. From the log output below I am > talking to the Oncore board but it is not in particular listening: > > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: ONCORE DRIVER -- CONFIGURING > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: state = ONCORE_NO_IDEA > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: Input mode = 2 > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: Initializing timing to Assert. > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: HARDPPS Set. > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: SHMEM (size = 3628) is > CONFIGURED and available as /var/log/ntpstats/oncore.0 > 25 Aug 22:52:51 ntpd[22820]: ONCORE[0]: state = ONCORE_CHECK_ID > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: Oncore: Resend @@Cj > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: @@Cj > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: COPYRIGHT 1991-1997 MOTOROLA INC. > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SFTW P/N # 98-P36848P > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE VER # 2 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE REV # 2 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SOFTWARE DATE APR 24 1998 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: MODEL # R5122U1112 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: HWDR P/N # 5 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: SERIAL # R02YWM > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: MANUFACTUR DATE 8G25 > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: This looks like an Oncore UT > with version 2.2 firmware. > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: Channels = 8, TRAIM = ON > 25 Aug 22:52:52 ntpd[22820]: ONCORE[0]: state = ONCORE_CHECK_CHAN > 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Input says chan = -1 > 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Model # says chan = 8 > 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Testing says chan = 8 > 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: Using chan = 8 > 25 Aug 22:52:57 ntpd[22820]: ONCORE[0]: state = ONCORE_HAVE_CHAN > 25 Aug 22:52:58 ntpd[22820]: ONCORE[0]: state = ONCORE_TEST_SENT > 25 Aug 22:53:05 ntpd[22820]: ONCORE[0]: GPS antenna: OK > 25 Aug 22:53:05 ntpd[22820]: ONCORE[0]: state = ONCORE_INIT > 25 Aug 22:53:08 ntpd[22820]: ONCORE[0]: Setting Posn from input data > 25 Aug 22:53:08 ntpd[22820]: ONCORE[0]: state = ONCORE_ALMANAC >......... > 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: Initiating hardware 3D site survey > 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: SSstate = ONCORE_SS_HW > 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: PPS Offset is set to 0 ns > 25 Aug 22:53:13 ntpd[22820]: ONCORE[0]: Satellite mask angle is 0 degrees > 25 Aug 22:53:19 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, > error serial pps > 25 Aug 22:53:19 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, > error serial pps > 25 Aug 22:53:20 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, > error serial pps > 25 Aug 22:53:21 ntpd[22820]: ONCORE[0]: ONCORE: oncore_get_timestamp, > error serial pps > ---< cut here>--- > > ..and the PPS signal is not being heard either, so it is appearing: > > Can anyone explain to me what is going wrong? I have googled this error > for many times now and have not received an answer. > It looks like the you got the Motorola Oncore serial side working on your FreeBSD installation. Have you made the devfs.conf entries to link the pps and serial signal to the correct hardware port? Is your hardware port 'real'? Things don't work well with virtual serial ports and USB to serial converters.
This is the contents of my /etc/devfs.conf: link cuad1 oncore.serial.0 link cuad1 oncore.pps.0 The .pps. tag in your ntpq billboard doesn't show with this driver, you only get one common .gps. for both signals. The driver gets both pps and serial data from your serial port and uses both in the time solution. Your kernel also requires rebuildingwith the addition of: # Enable support for the kernel PLL to use an external PPS signal, # under supervision of [x]ntpd(8) # More info in ntpd documentation: http://www.eecis.udel.edu/~ntp options PPS_SYNC When it all works, the ntpdc will show: ntpdc -c sysi system peer: GPS_ONCORE(0) system peer mode: client leap indicator: 00 stratum: 1 precision: -22 root distance: 0.00000 s root dispersion: 0.00034 s reference ID: [GPS] reference time: d5c724b8.37c4ecad Tue, Aug 27 2013 9:14:32.217 system flags: auth monitor ntp kernel stats pps jitter: 0.000000 s stability: 0.000 ppm broadcastdelay: 0.000000 s authdelay: 0.000000 s and ntpdc -c kern pll offset: 6.69e-07 s pll frequency: 14.076 ppm maximum error: 0.006233 s estimated error: 1e-06 s status: 2107 pll ppsfreq ppstime ppssignal nano pll time constant: 4 precision: 1e-09 s frequency tolerance: 496 ppm pps frequency: 14.076 ppm pps stability: 0.010 ppm pps jitter: 2.502e-06 s calibration interval: 256 s calibration cycles: 2239 jitter exceeded: 223 stability exceeded: 0 calibration errors: 3 Does your system show that pps is in the kernel? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
