[Top][All Lists]

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

Re: [gpsd-users] Garmin 18X-5Hz

From: Gary E. Miller
Subject: Re: [gpsd-users] Garmin 18X-5Hz
Date: Mon, 15 Aug 2016 18:11:15 -0700

Yo Alexander!

On Mon, 15 Aug 2016 18:02:21 -0700
Alexander Carver <address@hidden> wrote:

> > What is your setup: exact configuration files please.  
> I don't have any of the setup anymore and I wasn't originally planning
> on reporting it so I didn't generate plots or collect data
> permanently. I did a test, didn't like the results, then changed the
> configurations of the hardware and software until I got something
> that worked.  This set of threads piqued my interest.

Well, then hard to improve it now.

> Maybe if I have some tuits available again I can set things back up to
> collect data especially  if there's been any change to SHM code in
> gpsd and/or ntpd.  However, on some of the older systems it takes me
> much longer to get around to setting up because I have to make a
> makefile for gpsd since the scons code it uses requires a much newer
> version of python than is available for those machines.

Well, ntpd has forked, and there has been a lot of work on gpsd for PPS.

Any data more than 6 months old is no longer useable.

> > Odd, what versions of gpsd and ntpd?  
> ntpd was 4.2.2 or thereabouts, gpsd was around 3.13 I think (mid 2015)

ntpd (classic) is now 4.2.8
ntpd (sec) is now 0.9.40dev.
gpsd is now 3.16

Anything a year old is obsolete for new development.

> > The gpsd-users list is for how to get gpsd/ntpd to play well
> > together. Driver 22 is known to be an inferior solution.  Driver
> > 28, SHM(), for now is the superior solution.  At least until you
> > can provide hard data, and hard configurations to prove otherwise.  
> True it's for gpsd but my experience is gpsd not playing nicely with
> ntpd and the fault is lying with gpsd because ntpd plays nicely with
> the GPS receiver on its own.  In the absence of a functional pairing
> of gpsd-ntpd the use of Driver 22 is my only solution.

I've had gpsd running with ntpd for a decade.  Many different
platforms, no credible bug reports.

We know driver 22 has more problems than driver 28, so next time
try to get 28 to work.  Not the least of which is marginal validity
checking of the PPS time.

> > I'm not saying there are not problems withh the SHM() driver, some
> > were discussed today on #ntpsec.  At least on NTPsec progress is
> > being made. With 7 months without an NTP classic commit you are
> > stuck with old grotty code.  
> I have to take grotty code when it's the code that actually works.

Well, easy to complain when you got no data, no working setup, and are
doing nothing to fix that. i can't argue against ghosts.  When you
actually want to fix it, come back here.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

Attachment: pgpsig340cUgL.pgp
Description: OpenPGP digital signature

reply via email to

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