GPSD/JSON driver

[Gary E. Miller]

Yo Hal!

On Thu, 05 May 2016 10:53:02 -0700
Hal Murray <hmurray at megapathdsl.net> wrote:

> gem at rellim.com said:
> > 46    GPSD NG client protocol
> > I suggest avoiding #46.   
> 
> Why?
> 
> I thought the party line was that json was the preferred way to talk
> to gpsd.

The JSON protocol is a good one, it is what the 46 refclock then does
with the data.  Specifically, by default, it stirs in the NMEA and PPS
times, coming up with composite jitter/dispersion numbers that jump by
several orders of magnitude when GPS signals are acquired and lost.

The ntpd PLLs take days to settles and jarring changes from minute to
minute on the 46 cause ntpd to mark the JSON time as a false ticker.

Unuseable in its default configuration.  We can't inflict bad
defaults on users.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160505/dbfbecb1/attachment.bin>