Yes, you are right added 'fudge time2 -0.5'
[root@NTP ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*GPS_NMEA(0) .GPS. 0 l 16 16 377 0.000 -0.304 0.035
+admin.non-stop. 203.35.x.x 2 u 50 64 377 0.336 -17.013 0.124
130.220.30.32 .STEP. 16 u - 1024 0 0.000 0.000 0.000
chronos.ise.can .STEP. 16 u - 1024 0 0.000 0.000 0.000
-ns1.unico.com.a 203.23.237.200 3 u 13 64 377 27.789 -24.321 4.624
+ntp.hiltech.com 149.20.64.28 2 u 61 64 377 74.266 -13.340 1.541
How do I check if ntpd is using PPS pulse?
I still have to check the PPS pulse with a scope .
Mark
-----Original Message-----
From: Dave Hart [mailto:[email protected]]
Sent: Saturday, 4 February 2012 4:00 PM
To: Mark C. Stephens
Cc: [email protected]
Subject: Re: [ntp:questions] timing issue with a HP 58534A
On Sat, Feb 4, 2012 at 03:04, Mark C. Stephens <[email protected]> wrote:
> I put that in because without noselect I get this:
>
> [root@NTP ~]# ntpq -p
> remote refid st t when poll reach delay offset
> jitter
> ======================================================================
> ========
> xGPS_NMEA(0) .GPS. 0 l 4 16 377 0.000 0.931
> 0.012 xtime.non-stop.c 210.9.x.x 2 u 61 64 377 0.340
> -496.02 0.236
>
> [root@NTP ~]# cat /etc/ntp.conf
> #
> #keysdir /etc/ntp
> keys /etc/ntp/keys
> trustedkey 1
> requestkey 1
> controlkey 1
>
>
> # GPS NMEA
> server 127.127.20.0 mode 16 minpoll 4 maxpoll 4 fudge 127.127.20.0
> flag1 1 # time2 -0.400
>
> # GPS PPS
> #server 127.127.22.0 minpoll 4 maxpoll 4 prefer #fudge 127.127.22.0
> flag3 1
>
> #Inhouse reference
> server 192.168.5.8 iburst maxpoll 9
>
> logconfig =allall
> driftfile /etc/ntp/drift
> enable stats
> statsdir /var/ntp/stats
> statistics loopstats peerstats clockstats
>
> Both are now false tickers. Could it be this GPS gumming up the works?
It appears despite my claim, fudge time2 -0.525 or so is needed for NMEA to
properly associate the PPS with the correct second. Moreover, you're running
into the "man with two watches never knows what time it is" problem -- there's
no tiebreaker if there's disagreement. Add more network sources, and/or
"noselect" all sources except NMEA, at least until you get NMEA behaving well.
Cheers,
Dave Hart
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
