Re: [gpsd-dev] GPSd on FreeBSD

[O'Connor, Daniel]

> On 10 Sep 2019, at 13:55, Gary E. Miller <address@hidden> wrote:
>>>> 
>>>> I think NTP must be using PPS otherwise the jitter would be much
>>>> higher.  
>>> 
>>> Your ntpmon showed that you were NOT using the local time from
>>> gpsd!  
>> 
>> Yes, as above.
> 
> The ntpmon showed your system was not using local NTP either.  So you
> still have not shown your PPS works with NTP.

This output:
    remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
o127.127.20.0    .GPS.            0 l    6   16  377    0.000   -0.018   0.002
-10.0.2.1        214.52.129.40    3 u   33   64  377    0.229   -1.949   0.044
0.au.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.002
1.au.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.002
2.au.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.002
+220.233.156.30  .PPS.            1 u    9   64  377   28.999    0.900   0.166
+220.158.215.20  202.46.178.18    2 u   36   64  377   78.438   -0.451   0.086
-13.239.25.115   .GPS.            1 u   25   64  377   30.705   -1.130   0.493
+27.124.125.252  27.124.125.250   3 u   31   64  377   33.795    0.369   0.220
-103.126.53.123  223.252.32.9     2 u   21   64  373   31.275   -1.001   0.114[

Indicates PPS is being used. The 'o' tally code is:
o  pps.peer
The peer has been declared the system peer and lends its variables to thesystem 
variables. However, the actual system synchronization is derived from a 
pulse-per-second (PPS) signal, either indirectly via the PPS reference clock 
driver or directly via kernel interface.

>>>> given it should be using the kernel for PPS edge capture I think it
>>>> wouldn't have an effect.  
>>> 
>>> Well, the logging demonstrated it was NOT using KPPS.  Nor
>>> TIOMCIWAIT PPS.  So no PPS at all.  
>> 
>> You seem to be missing the point that it is trying to do
>> time_pps_create on a file descriptor set to -2 which is not a valid
>> FD.
> 
> You are missing the point the -2 is not an FD, it is an error code from
> an eariler failure.

I can't find any earlier failure though..

I put the whole log file at http://www.dons.net.au/~darius/gpsd.log if you want 
to check it out.

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum