Problems syncing to a reference clock - NTP

This is a discussion on Problems syncing to a reference clock - NTP ; I have an older PC running BSDI 3.01 which has an internal ISA based GPS TrueTime clock: # uname -a BSD/OS tickhaus.utoronto.ca 3.1 BSDI BSD/OS 3.1 Kernel #2: Sun Aug 8 19:31:21 CDT 1999 etc. # dmesg | grep -i ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Problems syncing to a reference clock

  1. Problems syncing to a reference clock

    I have an older PC running BSDI 3.01 which has an internal ISA based
    GPS TrueTime clock:

    # uname -a
    BSD/OS tickhaus.utoronto.ca 3.1 BSDI BSD/OS 3.1 Kernel #2: Sun Aug 8
    19:31:21 CDT 1999 etc.
    # dmesg | grep -i true
    gpspc0 at isa0 iobase 0x320: TrueTime Model 560-5500 GPS-PC Card

    I am running xntpd version 3-5 and there seems to be a problem syncing
    to the
    reference clock. The daemon can sync to other time servers.

    # xntpdc -c peers
    remote local st poll reach delay offset disp
    ================================================== =====================
    =128.100.aaa.bbb 128.100.ccc.ddd 1 64 1 0.00879 0.103917 15.8750
    =GPS_PC(0) 5.0.0.0 0 64 0 0.00000 0.000000 16.0000

    Here is what ntp.conf looks like:


    # cat /etc/ntp.conf

    server 128.100.aaa.bbb
    server 127.127.27.0

    driftfile /etc/ntp.drift

    restrict default ignore
    restrict 127.0.0.1
    restrict 127.127.27.0
    restrict 128.100.aaa.bbb



    The GPS part seems fine:

    # gpstest
    *** GPSPCSTATUS ***
    Hardware register = 0xFFFC
    Antenna OK
    Error register = 0x00
    Configuration register = 0x1107
    Sync-Gen Mode
    Sync to GPS
    Local Offset is: 00:00
    DST start day is: 00-00
    DST stop day is: 00-00
    Sync-gen Offset (prop delay) is: 0 microsecs
    Output code is: IRIG-B
    Rate output is: 1 pps
    *** GPSPCREADTIME ***
    2028:129:15:59:20.370261 Locked to GPS
    *** GPSPCSIGLEVEL ***
    SAT03 = 11.45
    SAT23 = 9.83
    SAT16 = 11.93
    SAT06 = 9.00
    SAT19 = 4.68
    SAT13 = 7.46
    *** GPSPCPOSITION ***
    Latitude: xx degrees 9 minutes 40.0 seconds N
    Longitude: yy degrees 23 minutes 53.7 seconds W
    Altitude: +00zz.1 meters


    Here is some debugging output:

    # xntpdc -c "clkbug 127.127.27.0"
    clock address: 127.127.27.0
    values: 8
    0 129 16 10
    47 0 3408134400 0
    times: 3
    0.000000 00:000:00:00:00.0003431088647.018523
    08:265:16:10:47.018
    0.000000

    # xntpdc -c "clockstats 127.127.27.0"
    ***Command `clockstats' unknown
    bash# xntpdc -c "clockstat 127.127.27.0"
    clock address: 127.127.27.0
    clock type: TrueTime GPS-PC Interface (27)
    last event: 6
    current status: 6
    number of polls: 3
    no response to poll: 0
    bad format responses: 0
    bad data responses: 3
    running time: 176
    fudge time 1: 0.000000
    fudge time 2: 0.000000
    stratum: 0
    reference ID: GPS
    fudge flags: 0x0


    Any ideas?


    ---
    Russell P. Sutherland Email: russ @ madhaus.cns.utoronto.ca
    4 Bancroft Ave., Rm. 102 Voice: +1.416.978.0470
    University of Toronto Fax: +1.416.978.6620
    Toronto, ON M5S 1C1 WWW: http://madhaus.cns.utoronto.ca/~russ
    CANADA

  2. Re: Problems syncing to a reference clock

    >>> In article , russ@madhaus.cns.utoronto.ca (Sutherland Russell) writes:

    Sutherland> I have an older PC running BSDI 3.01 which has an internal ISA
    Sutherland> based GPS TrueTime clock:

    Sutherland> # uname -a BSD/OS tickhaus.utoronto.ca 3.1 BSDI BSD/OS 3.1
    Sutherland> Kernel #2: Sun Aug 8 19:31:21 CDT 1999 etc. # dmesg | grep -i
    Sutherland> true gpspc0 at isa0 iobase 0x320: TrueTime Model 560-5500 GPS-PC
    Sutherland> Card

    Sutherland> I am running xntpd version 3-5 and there seems to be a problem
    Sutherland> syncing to the reference clock. The daemon can sync to other
    Sutherland> time servers.

    Russ,

    I see there is a TT560 reflock in the current codebase at 127.127.41.x .

    I also see the TT560 is listed as an IRIG-B refclock card.

    Did your setup work before and recently stop working?

    3.5 is kinda old - http://support.ntp.org/Dev/ReleaseTimeline .

    If you have the source code then debugging this shouldn't be too painful.
    Even so, I'd be inclined to see if a more recent release worked better for
    you.

    --
    Harlan Stenn
    http://ntpforum.isc.org - be a member!

  3. Re: Problems syncing to a reference clock

    In article ,
    Sutherland Russell wrote:
    >I have an older PC running BSDI 3.01 which has an internal ISA based
    >GPS TrueTime clock:
    >
    ># uname -a
    >BSD/OS tickhaus.utoronto.ca 3.1 BSDI BSD/OS 3.1 Kernel #2: Sun Aug 8
    >19:31:21 CDT 1999 etc.
    ># dmesg | grep -i true
    >gpspc0 at isa0 iobase 0x320: TrueTime Model 560-5500 GPS-PC Card
    >
    >I am running xntpd version 3-5 and there seems to be a problem syncing
    >to the
    >reference clock. The daemon can sync to other time servers.
    >
    ># xntpdc -c peers
    > remote local st poll reach delay offset disp
    >================================================== =====================
    >=128.100.aaa.bbb 128.100.ccc.ddd 1 64 1 0.00879 0.103917 15.8750
    >=GPS_PC(0) 5.0.0.0 0 64 0 0.00000 0.000000 16.0000
    >
    >Here is what ntp.conf looks like:
    >
    >
    ># cat /etc/ntp.conf
    >
    >server 128.100.aaa.bbb
    >server 127.127.27.0
    >
    >driftfile /etc/ntp.drift
    >
    >restrict default ignore
    >restrict 127.0.0.1
    >restrict 127.127.27.0
    >restrict 128.100.aaa.bbb
    >
    >
    >
    >The GPS part seems fine:
    >
    ># gpstest
    >*** GPSPCSTATUS ***
    >Hardware register = 0xFFFC
    >Antenna OK
    >Error register = 0x00
    >Configuration register = 0x1107
    >Sync-Gen Mode
    >Sync to GPS
    >Local Offset is: 00:00
    >DST start day is: 00-00
    >DST stop day is: 00-00
    >Sync-gen Offset (prop delay) is: 0 microsecs
    >Output code is: IRIG-B
    >Rate output is: 1 pps
    >*** GPSPCREADTIME ***
    >2028:129:15:59:20.370261 Locked to GPS
    >*** GPSPCSIGLEVEL ***
    >SAT03 = 11.45
    >SAT23 = 9.83
    >SAT16 = 11.93
    >SAT06 = 9.00
    >SAT19 = 4.68
    >SAT13 = 7.46
    >*** GPSPCPOSITION ***
    >Latitude: xx degrees 9 minutes 40.0 seconds N
    >Longitude: yy degrees 23 minutes 53.7 seconds W
    >Altitude: +00zz.1 meters
    >
    >
    >Here is some debugging output:
    >
    ># xntpdc -c "clkbug 127.127.27.0"
    >clock address: 127.127.27.0
    >values: 8
    > 0 129 16 10
    > 47 0 3408134400 0
    >times: 3
    > 0.000000 00:000:00:00:00.0003431088647.018523
    >08:265:16:10:47.018
    > 0.000000
    >
    ># xntpdc -c "clockstats 127.127.27.0"
    >***Command `clockstats' unknown
    >bash# xntpdc -c "clockstat 127.127.27.0"
    >clock address: 127.127.27.0
    >clock type: TrueTime GPS-PC Interface (27)
    >last event: 6
    >current status: 6
    >number of polls: 3
    >no response to poll: 0
    >bad format responses: 0
    >bad data responses: 3
    >running time: 176
    >fudge time 1: 0.000000
    >fudge time 2: 0.000000
    >stratum: 0
    >reference ID: GPS
    >fudge flags: 0x0
    >
    >
    >Any ideas?
    >
    >
    >---
    >Russell P. Sutherland Email: russ @ madhaus.cns.utoronto.ca
    >4 Bancroft Ave., Rm. 102 Voice: +1.416.978.0470
    >University of Toronto Fax: +1.416.978.6620
    >Toronto, ON M5S 1C1 WWW: http://madhaus.cns.utoronto.ca/~russ
    >CANADA


    Can you update this to the lastest version of ntpd?

    I still used 4.3.1 and no problems.
    --
    Member - Liberal International
    This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
    God, Queen and country! Beware Anti-Christ rising! Canada vote anything but
    Conservative on 14 OCt 2008, join us at http://www.harpocrit.ca .

+ Reply to Thread