gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] Unexpected behavior


From: Nick Burkitt
Subject: Re: [gpsd-users] Unexpected behavior
Date: Tue, 19 Sep 2017 16:52:22 -0700

Hi Gary.

 

Thanks for the reply. For some reason, I’m not getting email from the list, hence the delay. :-/ But…

 

> > The expected duration is, of course, 100 ms, and every second KPPS

> > cycle report matches that expectation. But in between the expected

> > duration reports are reports claiming a 900 ms duration,

 

> Well, 100ms + 900ms is 1 second.  That is 100% expected and proper.

 

With effort, I was able to perform that calculation also. I had more trouble figuring out how the 11 second cycle fit into the 1 second PPS period. But it’s never wise to read too much into other people’s log messages. I’ll take your word that the 10-second delays are not significant.

 

> > and then the

> > TIOCMIWAIT warnings, which suggest that GPSD is using user-space PPS

> > instead of KPPS.

 

> Of course, gpsd auto configures.  Not a problem.

 

If it auto-configures to use user-space PPS, that’s a problem. It’s smarter than that, though, right?

 

> Looks perfect to me.  But the way to really know is to feed NTPsec

> from gpsd and see what ntpmon thinks of your data.

 

>-- many hours and much swearing later --<

 

Both gpsd and ntpd (NTPsec) are running, and, possibly, talking to each other. I can use gpsmon to watch GPS output, and ntpmon to watch, um, some information from NTPsec. Nothing in either output suggests (to me) that they think of each other at all, let alone what opinions they may harbor.

 

ntpmon -n says:

 

     remote           refid      st t when poll reach   delay   offset   jitter

+74.120.81.219   45.56.123.24     3 u   66   64  377  52.6010   1.8384  10.1963

*50.116.52.97    192.5.41.209     2 u   58   64  377  79.1755   0.4626   1.9507

-66.228.59.187   35.73.197.144    2 u   67   64  177  82.4018   4.9234   2.9133

+108.61.56.35    18.26.4.105      2 u   51   64  377  77.8942  -2.4250   1.7669

ntpd ntpsec-0.9.7+1381 2017-09-19T09:55:20-0400Updated: 2017-09-19T23:13:42 (32)

lstint avgint rstr r m v  count rport remote address

      0   2.75    0 . 6 2    404 41935 ::1

     51     57   d0 . 4 4     26   123 108.61.56.35

     58     57   d0 . 4 4     26   123 50.116.52.97

     66     57   d0 . 4 4     26   123 74.120.81.219

     67     61   d0 . 4 4     24   123 66.228.59.187

 

Is ntpd’s PPS happiness encoded in there somewhere?

 

Thanks again,

 

-Nick

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]