[Top][All Lists]

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

Re: M8T time offset

From: Denny Page
Subject: Re: M8T time offset
Date: Tue, 21 Jan 2020 17:37:56 -0800

Hi Gary,

Okay, I’ve re-tested with 3.19 and 3.20. I do see the issue with 3.19, I have not seen it with 3.20. With regard to head, I think I had the wrong repo—I still had rather than I’m not able to build the current master from gitlab due to an odd scons error so I haven’t tested with it yet.

Another abnormality… in gpsmon with 3.19 I see the current PPS offset in the PPS field. With 3.20, I see “N/A” in the PPS field.


On Jan 21, 2020, at 13:24, Denny Page <address@hidden> wrote:

I can test again with head. It’s been a few of weeks since I did it. Head and 3.20 are identical, yes?

I wish I had better detail records. I’ve been waiting to perform a config reset and cold start until I could finish several long term surveys.


On Jan 21, 2020, at 13:06, Gary E. Miller <address@hidden> wrote:

Yo Denny!

On Tue, 21 Jan 2020 12:31:36 -0800
Denny Page <address@hidden> wrote:

So, I___ve been seeing a bit of a weird problem. I have an M8T that I___m
using with gpsd. The behavior I see is that gpsd oscillates every 30
minutes or so between reporting time correctly, and reporting time
off by 1 second.

What version of gpsd?  Something like you report was seen in gpsd
versions before 3.20.

I am using gpsd 3.19, although I have tested with current head (3.20)
and see the same behavior.

That is odd, I have not seen it in months.  reports of similar behavior stops
a few months ago.

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

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

reply via email to

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