[Top][All Lists]

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

Re: [gpsd-dev] Status driver_nmea2000.c

From: Gary E. Miller
Subject: Re: [gpsd-dev] Status driver_nmea2000.c
Date: Sun, 8 Feb 2015 15:37:01 -0800

Yo Harlan!

On Sun, 08 Feb 2015 23:29:42 +0000
Harlan Stenn <address@hidden> wrote:

> "Eric S. Raymond" writes:
> > Gary E. Miller <address@hidden>:
> > > One other item that might be easy to do.  The ntpd guys would
> > > like the TPV JSON message to have the time stamp when the TPV
> > > wass receiver.  Which is related to the gpsmon problem in #1
> > > above, but already known in gpsd. It just needs to be added to
> > > the TPV, or in another related message.
> > 
> > The PPS message already includes clock time of the last fix.
> > 
> > Given that, I'd like to understand why they think they want the
> > same stamp in the TPV before I do it. I don't see that it adds any
> > information.
> I do not know, and given the choice, I'd rather not dig in to it.
> My first inclination is to see what Pearly says.  I see that Hal has
> been curious about stuff, too.

Pearly was the one that pointed out the problem.  He has had to take
his own clock timestamp when he receives the TPV message.  That, of
course, is giving him pretty aweful data.

But I guess your take home from this is that the GPSD_JSON is a mess
right now, and not gonna get resolved soon, so you should just leave 
that driver as it has been (broken) and ship the next ntpd.

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

reply via email to

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