Re: NTP via tcp NMEA feed

[Gary E. Miller]

Yo Nick!

On Wed, 19 Oct 2022 11:01:14 +0100
Nick Taylor <nicktaylor@dataskill.uk> wrote:

> gpsd is obviously seeing time OK and can be seen using cgps but no
> feed in ntpshmmon :(

I see it is running the new code, the SHM is activated for the
tcp://


gpsd:PROG: NTP:SHM: ntpshm_link_activate(tcp://10.186.165.121:50012), 
sourcetype 7 fd 7
gpsd:PROG: NTP:SHM: ntpshm_alloc(tcp://10.186.165.121:50012), sourcetype 7 
shm_clock using SHM(0)
gpsd:INFO: SHM: ntpshm_link_activate(tcp://10.186.165.121:50012): NTP activated 

It clearly has a good fix, and the right time:

gpsd:CLIENT: => client(0) len 390: 
{"class":"TPV","device":"tcp://10.186.165.121: 
50012","status":2,"mode":3,"time":"2022-10-19T09:44:44.000Z","ept":0.005,"lat":32
 
.646786667,"lon":-108.373716667,"altHAE":1620.4000,"altMSL":1645.0000,"alt":1645.
  
0000,"track":84.5000,"magtrack":93.8000,"magvar":9.3,"speed":9.672,"climb":-1.000
 ,"geoidSep":-24.600,"eph":4.750}

But maybe this SKY is confusing things?
time:

{"class":"SKY","device":"tcp://10.186.165.121:50012","hdop":1.00}

But it does pass the >3 sats used test:

{"class":"SKY","device":"tcp://10.186.165.121:50012","gdop":2.44,"hdop":1.00,"pdop":1.30,"tdop":1.27,"xdop":0.71,"ydop":0.75,"vdop":0.90,"nSat":10,"uSat":8,

Maybe a problem with the received message order??

I'll just pushed some log changes to git that may, or may not, shed
some light here.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpVq8mz1o2GP.pgp
Description: OpenPGP digital signature