Re: ntpviz showing odd repeating offset for SHM(0) from gpsd

[Martin Boissonneault]

Oops, I goofed.

The GNSS configuration can be taken with ubxtool -P CONFIG if my memory is good.

Martin Boissonneault
Sent from my phone

> On May 9, 2020, at 10:41, Martin Boissonneault <address@hidden> wrote:
> 
> Hi Arne,
> From what I see of your SHM(0), the time strings look barely early. It's not 
> clear from the information you posted what the problem is, except it appears 
> you are jumping by one second on the SHM(1). Am I correct?
> 
> Is the GNSS the only time source used? The ntp.conf file would be useful to 
> figure this problem out. 
> 
> Also, the GNSS configuration would be useful, new parameters where added to
> 
> Martin 
> 
> 
> 
> Martin Boissonneault
> Sent from my phone
> 
>> On May 9, 2020, at 07:11, shouldbe q931 <address@hidden> wrote:
>> 
>> so now it gets curiouser
>> 
>> As can be clearely seen, the flip flop offset has gone from SHM(0),
>> 
>> https://pasteboard.co/J7yTyFQ.png
>> 
>> However there is now different issue
>> 
>> https://pasteboard.co/J7yVa8A.png
>> 
>> Cheers
>> 
>> Arne
>> 
>> 
>>>> On Fri, May 8, 2020 at 10:41 PM shouldbe q931 <address@hidden> wrote:
>>> 
>>> Hi Martin,
>>> 
>>>> On Fri, May 8, 2020 at 4:23 PM Martin Boissonneault
>>>> <address@hidden> wrote:
>>>> 
>>>> Hi Arne,
>>>> 
>>>> My U-blox MAX-M8Q does the same. The message timing has that varying 
>>>> offset, but it has no real consequences as SHM1 is the one that carries 
>>>> the PPS. I would, however, recommend you apply an offset to keep the delay 
>>>> positive or it could mess the decoding.
>>>> 
>>> 
>>> Yes, I'm quite aware that it isn't an "issue" (-:
>>> 
>>> 
>>>> Otherwise, it's normal.
>>> 
>>> I have a "few" uBlox receivers (including a MAX-M8Q on an Uputonics
>>> "hat") , and I have not seen this on any of the others, none of the
>>> other gpsd installs were on the same (exact) version.
>>> 
>>> I've updated to git head, and the "flip flop" offset no longer appears
>>> to be happening.
>>> 
>>> Cheers
>>> 
>>> Arne
>>> 
>>>> 
>>>> Martin
>>>> 
>>>> Martin Boissonneault
>>>> Sent from my phone
>>>> 
>>>>> On May 8, 2020, at 07:00, shouldbe q931 <address@hidden> wrote:
>>>>> 
>>>>> As a picture is allegedly worth a thousand words, I've included two 
>>>>> pictures
>>>>> 
>>>>> daily view
>>>>> https://pasteboard.co/J7p9VU5.png
>>>>> 
>>>>> weekly view
>>>>> https://pasteboard.co/J7paicZ.png
>>>>> 
>>>>> As none of the other server offsets show this, I have presumed that
>>>>> the repeating offset is not happening on the ntpsec side.
>>>>> 
>>>>> gpsd: 3.19-dev (revision 3.19-dev-2019-04-22T13:57:37.400598)
>>>>> ntpd ntpsec-1.1.3+ 2019-04-22T13:02:45Z (git rev 5b9324c)
>>>>> 
>>>>> Running in a rPi raspbian stretch
>>>>> 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
>>>>> 
>>>>> gpsd is started with
>>>>> /usr/local/sbin/gpsd -P /var/run/gpsd.pid -n  /dev/gpsd0
>>>>> 
>>>>> UBX-MON-VER:
>>>>> swVersion 1.00 (59842)
>>>>> hwVersion 00070000
>>>>> extension: PROTVER 14.00
>>>>> extension: GPS;SBAS;GLO;QZSS
>>>>> 
>>>>> Although the rPi also runs dump109-fa (an ADS-B receiver), I'm fairly
>>>>> sure that this is not related.
>>>>> 
>>>>> Cheers
>>>>> 
>>>>> Arne
>>>>> 
>>