Re: gpsd losing connection to ublox

[Niall Parker]

On 2021-11-10 2:07 p.m., Gary E. Miller wrote:
> Can you be more specific on "latest"?  Latest is:
>
> # gpsd -V
> gpsd: 3.23.2~dev (revision release-3.23.1-122-g3d860d8d1)

I didn't recognize gpsd was so active ! ... must pull more often, now 
trying release-3.23.1-124-g17aa9ebce

> gpsmon is not a tool to debug NTP.  What does ntpshmmon show?
ntpshmmon: version 3.23.2~dev
#      Name  Seen@                 Clock Real                 L Prc
sample NTP2  1636605083.112353126  1636605083.000066187 
1636605083.000000000 0 -20
sample NTP0  1636605083.147133927  1636605083.146458406 
1636605083.000116578 0  -1
sample NTP2  1636605084.000978656  1636605084.000090685 
1636605084.000000000 0 -20
sample NTP0  1636605084.143911825  1636605084.143802864 
1636605084.000116260 0  -1
sample NTP2  1636605085.001452757  1636605085.000101585 
1636605085.000000000 0 -20
sample NTP0  1636605085.143553699  1636605085.142538848 
1636605085.000115941 0  -1
sample NTP2  1636605086.000505798  1636605086.000067973 
1636605086.000000000 0 -20
sample NTP0  1636605086.147479651  1636605086.146820897 
1636605086.000115623 0  -1
sample NTP2  1636605087.001192574  1636605087.000098523 
1636605087.000000000 0 -20
sample NTP0  1636605087.144117840  1636605087.143413358 
1636605087.000115305 0  -1
sample NTP2  1636605088.000981813  1636605088.000090611 
1636605088.000000000 0 -20
sample NTP0  1636605088.142028769  1636605088.140983678 
1636605088.000114986 0  -1
sample NTP2  1636605089.000490666  1636605089.000066441 
1636605089.000000000 0 -20

... this gave me the clue it wasn't NTP1 I needed but rather NTP2, 
adjusting that in ntp.conf and finally it was able to reach the PPS signal.

Found a note in https://gpsd.io/gpsd-time-service-howto.html this might 
be the case for some GPS HATs, should have read it more carefully ! ;)

Now that PPS is getting through I can follow the tuning procedure in the 
howto, give it some time get some stats.

Thanks again !

            ... Niall