[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GPS/PPM very large offset
From: |
Mike Simpson |
Subject: |
Re: GPS/PPM very large offset |
Date: |
Fri, 6 Nov 2020 23:51:38 +0000 |
Big. Sometimes 3s, sometimes 4s. B&A complaining of 5s.
On my Pi when it was happening I noticed that the time offset field of cgps
would jump about rapidly from 0.2s-0.4s to 3.something and ntpsec would state
that both pps and gps were 3 seconds off.
Removing GLONASS kept the cgps time offset at 0.something and corrected the
time seen by ntpsec.
Second time this has come up on the list with the ublox8.
> On 6 Nov 2020, at 23:38, Greg Troxel <gdt@lexort.com> wrote:
>
>
> Mike Simpson <mikie.simpson@gmail.com> writes:
>
>> It’s glonass
>> They run such a big offset that they are unusable for time.
>>
>> ubxtool -d GLONASS
>>
>> Need to do this every time after Pi reboot or presumably cold restart of the
>> GPS.
>
> What do you mean by big? Do you mean something like 41 ns?
>
> Or do you mean 5s? If so, surely 5s is not an error, and there is some
> alternate time scale and there should be translations.
>
- GPS/PPM very large offset, B&A Consultants, 2020/11/06
- Re: GPS/PPM very large offset, Gary E. Miller, 2020/11/06
- Re: GPS/PPM very large offset, B&A Consultants, 2020/11/06
- Re: GPS/PPM very large offset, Gary E. Miller, 2020/11/06
- Re: GPS/PPM very large offset, Mike Simpson, 2020/11/06
- Re: GPS/PPM very large offset, Greg Troxel, 2020/11/06
- Re: GPS/PPM very large offset,
Mike Simpson <=
- Re: GPS/PPM very large offset, Gary E. Miller, 2020/11/06
- Re: GPS/PPM very large offset, Greg Troxel, 2020/11/06
- Re: GPS/PPM very large offset, B&A Consultants, 2020/11/08
- Re: GPS/PPM very large offset, Håkan T Johansson, 2020/11/08
- Re: GPS/PPM very large offset, B&A Consultants, 2020/11/08
- Re: GPS/PPM very large offset, David J Taylor, 2020/11/08