what wrong with my nmea gps receiver? - NTP

This is a discussion on what wrong with my nmea gps receiver? - NTP ; Sun solaris 10 x86 with ntp 3-5.93e /etc/inet/ntp.conf server 127.127.20.0 mode 1 prefer fudge 127.127.20.0 time1 0.000 flag3 1 stratum 0 driftfile /var/ntp/ntp.drift statsdir /var/ntp/ntpstats/ -bash-3.00# ntpq ntpq> cl status=0606 clk_badtime, last_clk_badtime device="NMEA GPS Clock", timecode=, poll=5, noreply=0, badformat=0, baddata=2, ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: what wrong with my nmea gps receiver?

  1. what wrong with my nmea gps receiver?

    Sun solaris 10 x86 with ntp 3-5.93e

    /etc/inet/ntp.conf
    server 127.127.20.0 mode 1 prefer
    fudge 127.127.20.0 time1 0.000 flag3 1 stratum 0
    driftfile /var/ntp/ntp.drift
    statsdir /var/ntp/ntpstats/

    -bash-3.00# ntpq
    ntpq> cl
    status=0606 clk_badtime, last_clk_badtime
    device="NMEA GPS Clock", timecode=, poll=5, noreply=0, badformat=0,
    baddata=2, fudgetime1=0.000, stratum=0, refid=GPS, flags=4
    ntpq> pe
    remote refid st t when poll reach delay offset
    disp
    ================================================== ============================
    GPS_NMEA(0) .GPS. 0 l 183 64 34 0.00 239.739
    3892.88
    ntpq> clockvar
    status=0606 clk_badtime, last_clk_badtime
    device="NMEA GPS Clock", timecode=, poll=5, noreply=0, badformat=0,
    baddata=2, fudgetime1=0.000, stratum=0, refid=GPS, flags=4
    ntpq> rv
    status=c011 sync_alarm, sync_unspec, 1 event, event_restart
    system="SunOS", leap=11, stratum=16, rootdelay=0.00,
    rootdispersion=0.00, peer=0, refid=0.0.0.0,
    reftime=00000000.00000000 Thu, Feb 7 2036 14:28:16.000, poll=4,
    clock=c8b87199.c298c000 Mon, Sep 18 2006 9:15:05.760, phase=0.000,
    freq=0.00, error=0.00
    ntpq> ntpversion
    NTP version being claimed is 3
    ntpq> version
    ntpq 3-5.93e Mon Sep 20 15:45:42 PDT 1999 (1)

    #/usr/lib/inet/xntpd -d

    refclock_gtlin: fd 5 time 3367530857.567885 timecode 46
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    nmea: timecode 46 $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    refclock_gtlin: fd 5 time 3367530857.567885 timecode 0
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    refclock_gtlin: fd 5 time 3367530857.732772 timecode 68
    $GPGSV,2,1,08,22,68,196,00,30,63,108,00,14,58,349, 34,05,37,053,37*7F
    nmea: timecode 68
    $GPGSV,2,1,08,22,68,196,00,30,63,108,00,14,58,349, 34,05,37,053,37*7F
    refclock_gtlin: fd 5 time 3367530857.732772 timecode 0
    $GPGSV,2,1,08,22,68,196,00,30,63,108,00,14,58,349, 34,05,37,053,37*7F
    refclock_gtlin: fd 5 time 3367530857.897665 timecode 68
    $GPGSV,2,2,08,18,32,159,00,25,27,260,00,01,23,307, 41,06,06,139,00*78
    nmea: timecode 68
    $GPGSV,2,2,08,18,32,159,00,25,27,260,00,01,23,307, 41,06,06,139,00*78
    refclock_gtlin: fd 5 time 3367530857.897665 timecode 0
    $GPGSV,2,2,08,18,32,159,00,25,27,260,00,01,23,307, 41,06,06,139,00*78
    refclock_gtlin: fd 5 time 3367530858.044246 timecode 67
    $GPRMC,011418.061,A,3200.8362,N,11849.8242,E,27.62 ,3.58,180906,,*37
    nmea: timecode 67
    $GPRMC,011418.061,A,3200.8362,N,11849.8242,E,27.62 ,3.58,180906,,*37
    refclock_gtlin: fd 5 time 3367530858.055433 timecode 0
    $GPRMC,011418.061,A,3200.8362,N,11849.8242,E,27.62 ,3.58,180906,,*37
    refclock_gtlin: fd 5 time 3367530858.457633 timecode 78
    $GPGGA,011419.061,3200.8461,N,11849.8249,E,1,03,50 .0,-57.4,M,5.3,M,0.0,0000*6A
    nmea: timecode 78
    $GPGGA,011419.061,3200.8461,N,11849.8249,E,1,03,50 .0,-57.4,M,5.3,M,0.0,0000*6A
    refclock_gtlin: fd 5 time 3367530858.457633 timecode 0
    $GPGGA,011419.061,3200.8461,N,11849.8249,E,1,03,50 .0,-57.4,M,5.3,M,0.0,0000*6A
    refclock_gtlin: fd 5 time 3367530858.567543 timecode 46
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    nmea: timecode 46 $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    refclock_gtlin: fd 5 time 3367530858.567543 timecode 0
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.0*00
    refclock_gtlin: fd 5 time 3367530858.734488 timecode 67
    $GPRMC,011419.061,A,3200.8461,N,11849.8249,E,27.16 ,3.58,180906,,*3A
    nmea: timecode 67
    $GPRMC,011419.061,A,3200.8461,N,11849.8249,E,27.16 ,3.58,180906,,*3A
    refclock_gtlin: fd 5 time 3367530858.734488 timecode 0
    $GPRMC,011419.061,A,3200.8461,N,11849.8249,E,27.16 ,3.58,180906,,*3A
    refclock_gtlin: fd 5 time 3367530859.458294 timecode 78
    $GPGGA,011420.061,3200.8536,N,11849.8255,E,1,03,50 .0,-57.0,M,5.3,M,0.0,0000*6A
    nmea: timecode 78
    $GPGGA,011420.061,3200.8536,N,11849.8255,E,1,03,50 .0,-57.0,M,5.3,M,0.0,0000*6A
    refclock_gtlin: fd 5 time 3367530859.458294 timecode 0
    $GPGGA,011420.061,3200.8536,N,11849.8255,E,1,03,50 .0,-57.0,M,5.3,M,0.0,0000*6A
    refclock_gtlin: fd 5 time 3367530859.568202 timecode 46
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.1*01
    nmea: timecode 46 $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.1*01
    refclock_gtlin: fd 5 time 3367530859.568202 timecode 0
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.1*01
    refclock_gtlin: fd 5 time 3367530859.735147 timecode 67
    $GPRMC,011420.061,A,3200.8536,N,11849.8255,E,26.72 ,3.58,180906,,*3D
    nmea: timecode 67
    $GPRMC,011420.061,A,3200.8536,N,11849.8255,E,26.72 ,3.58,180906,,*3D
    refclock_gtlin: fd 5 time 3367530859.735147 timecode 0
    $GPRMC,011420.061,A,3200.8536,N,11849.8255,E,26.72 ,3.58,180906,,*3D
    refclock_gtlin: fd 5 time 3367530860.458143 timecode 78
    $GPGGA,011421.061,3200.8610,N,11849.8260,E,1,03,50 .0,-56.6,M,5.3,M,0.0,0000*6D
    nmea: timecode 78
    $GPGGA,011421.061,3200.8610,N,11849.8260,E,1,03,50 .0,-56.6,M,5.3,M,0.0,0000*6D
    refclock_gtlin: fd 5 time 3367530860.458143 timecode 0
    $GPGGA,011421.061,3200.8610,N,11849.8260,E,1,03,50 .0,-56.6,M,5.3,M,0.0,0000*6D
    refclock_gtlin: fd 5 time 3367530860.568055 timecode 46
    $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.1*01
    nmea: timecode 46 $GPGSA,A,2,01,14,05,,,,,,,,,,50.0,50.0,20.1*01

    thanks!!


  2. Re: what wrong with my nmea gps receiver?

    >>> In article <1158584487.147442.324640@h48g2000cwc.googlegroups. com>, xvenw@163.com writes:

    xvenw> Sun solaris 10 x86 with ntp 3-5.93e

    If your 3-5.93e is 'stock', it is seriously old.

    Please try again with a current release of ntp.

    H

  3. Re: what wrong with my nmea gps receiver?

    Harlan Stenn wrote:

    >>>>In article <1158584487.147442.324640@h48g2000cwc.googlegroups. com>, xvenw@163.com writes:

    >
    >
    > xvenw> Sun solaris 10 x86 with ntp 3-5.93e
    >
    > If your 3-5.93e is 'stock', it is seriously old.
    >
    > Please try again with a current release of ntp.
    >
    > H


    Harlan,

    3-5.93e is what ships with Solaris 8, 9, and 10 (don't know about
    earlier versions). I guess Sun is waiting for V4 to be "standardized"
    or something. Many other vendors also ship this antique!

  4. Re: what wrong with my nmea gps receiver?


    Harlan Stenn 写道:

    > >>> In article <1158584487.147442.324640@h48g2000cwc.googlegroups. com>, xvenw@163.com writes:

    >
    > xvenw> Sun solaris 10 x86 with ntp 3-5.93e
    >
    > If your 3-5.93e is 'stock', it is seriously old.
    >
    > Please try again with a current release of ntp.
    >
    > H


    I have tested with ntp 4.2,it work very well. Thanks.^_^


+ Reply to Thread