Thanks for verifying the serial rate configured in the mode number in
ntp.conf matches the rate the GPS is actually using, we can scratch
that possibility off the list of potential causes.

Please bring this up on questions@ (or on the newsgroup
comp.protocols.time.ntp if you prefer usenet, the two are gatewayed
together).

Please don't bother showing ntpdc -c kerninfo output when ntpd's not
synched.  Without a * or o in the first column of the peers billboard,
kernel loop discipline details are entirely irrelevant.  What is
relevant and missing from your NOTES below is the version of ntpd in
use, which is part of ntpq -crv output.  ntpq -ccv output might be
useful as well.

Cheers,
Dave Hart

On Mon, Feb 20, 2012 at 04:55, AlbyVA <[email protected]> wrote:
>
>
>  Well, it looks like bps rates aren't the issue. I got the port set for 9600
> and
> ntp.conf listing (mode 16) and still no dice.
>
> NOTES:
> ------------
>
> # ntp.conf entry
> #
> #
> server 127.127.20.0 minpoll 4   mode 16         prefer
> #
> #
>
>
>
> godzilla# stty -a -f /dev/cuau0
> speed 9600 baud; 0 rows; 0 columns;
> lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
>  -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
>  -extproc
> iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk
>  brkint -inpck -ignpar -parmrk
> oflags: opost onlcr -ocrnl tab0 -onocr -onlret
> cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
>  -dtrflow -mdmbuf
> cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
>  eol2 = <undef>; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U;
>  lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q;
>  status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;
> godzilla#
>
>
> godzilla#
> godzilla# cu -l /dev/cuau0 -s 9600
> Connected
> $GPGGA,045400.000,3903.1320,N,07729.1216,W,1,6,2.57,59.6,M,-33.4,M,,*58
> $GPGSA,A,3,19,13,06,03,23,07,,,,,,,3.50,2.57,2.38*04
> $GPGSV,3,1,12,19,75,077,20,07,70,314,16,03,40,050,33,13,37,217,29*7A
> $GPGSV,3,2,12,11,34,159,,08,32,315,,06,27,048,26,16,19,075,*79
> $GPGSV,3,3,12,48,17,246,,23,16,192,15,01,13,164,,28,10,273,*75
> $GPRMC,045400.000,A,3903.1320,N,07729.1216,W,0.58,124.13,200212,,,A*74
> $GPGGA,045401.000,3903.1317,N,07729.1216,W,1,6,2.57,59.7,M,-33.4,M,,*5C
> $GPGSA,A,3,19,13,06,03,23,07,,,,,,,3.50,2.57,2.38*04
> $GPGSV,3,1,12,19,75,077,20,07,70,314,15,03,40,050,33,13,37,217,29*79
> $GPGSV,3,2,12,11,34,159,,08,32,315,,06,27,048,26,16,19,075,*79
> $GPGSV,3,3,12,48,17,246,,23,16,192,15,01,13,164,,28,10,273,*75
> $GPRMC,045401.000,A,3903.1317,N,07729.1216,W,0.58,124.07,200212,,,A*74
>
>
> godzilla#
> godzilla# /etc/rc.d/ntpd start
> Starting ntpd.
>
> godzilla# ntpq -p
>      remote           refid      st t when poll reach   delay   offset
> jitter
> ==============================================================================
>  GPS_NMEA(0)     .GPS.            0 l    -   16    0    0.000    0.000
> 0.002
> godzilla#
> godzilla#
> godzilla# ntpdc -c kerninfo
>
> pll offset:           0 s
> pll frequency:        -12.503 ppm
> maximum error:        0.021516 s
> estimated error:      1.6e-05 s
> status:               2340  unsync ppssignal ppsjitter nano
>
> pll time constant:    0
> precision:            1e-09 s
> frequency tolerance:  496 ppm
> pps frequency:        -12.503 ppm
> pps stability:        0.000 ppm
> pps jitter:           0 s
> calibration interval: 4 s
> calibration cycles:   0
> jitter exceeded:      0
> stability exceeded:   0
> calibration errors:   0
> godzilla#
> godzilla#
>
>
> -Alby
>
>
>
>
>
>
>
>
> On Sun, Feb 19, 2012 at 11:18 PM, Dave Hart <[email protected]> wrote:
>>
>> On Mon, Feb 20, 2012 at 02:51, AlbyVA <[email protected]> wrote:
>> >  Now I know I can see data from /dev/cuau0 (a /dev/gps0 link points to
>> > /dev/cuau0) when I cat the port.
>> > But when I start up the NTP daemon, I get nothing.
>>
>> Perhaps cat and ntpd are reading the port at different speeds?
>> Double-check the mode value for 127.127.20.0 in ntp.conf specifies the
>> same rate the GPS is sending.
>>
>> BTW, the questions@ list is a better fit for this discussion.
>>
>> Cheers,
>> Dave Hart
>
>
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to