> >>> Why do you need the SHM 0? You can use SHM 1 or SOCK.Some cookbooks
(e.g.,
> https://support.ntp.org/bin/view/Support/ConfiguringSHMRefclocks ) use
both SHM 0 and SHM 1
That might had been necessary with very old versions of gpsd (IIRC it
originally required something to bring the system
On Thu, Mar 03, 2022 at 10:03:54PM -0600, Steven Sommars wrote:
> Config: Host sync'd to nearby stratum 1s. Jitter ~35 usec. gpsd 3.23
> gpspipe, gpspipe -R and ntpshmmon running simultaneously for several hours
>
> gpspipe -T '%s' --usec -r | sed 's|,.*||'
> Min Max
> (sec)(sec)
>
Config: Host sync'd to nearby stratum 1s. Jitter ~35 usec. gpsd 3.23
gpspipe, gpspipe -R and ntpshmmon running simultaneously for several hours
gpspipe -T '%s' --usec -r | sed 's|,.*||'
Min Max
(sec)(sec)
.132419 .168017 GPGBS
.132332 .167903 GPGGA
.132393 .167985 GPGSA
.389284
On Wed, Mar 02, 2022 at 10:14:48AM +0100, Gabriele Coppi wrote:
> At this point, I guess the easiest option would be to install gpsd 3.20 and
> test it again
Why do you need the SHM 0? You can use SHM 1 or SOCK. If you really
need it (e.g. for >1Hz PPS), you can set the refclock offset to 0.4
On Tue, Mar 01, 2022 at 03:09:27PM -0600, Steven Sommars wrote:
> I understand the jumps to be gpsd-related.I see identical behavior on
> one of my RPi4+ublox GPS units.
> NMEA sentence timing remains consistent. As an optimization some gpsd
> versions move the GPS into ublox binary mode
At this point, I guess the easiest option would be to install gpsd 3.20 and
test it again
Gabriele
On 1 Mar 2022, 22:10 +0100, Steven Sommars , wrote:
> Gabriele provided ntpshmmon output which I've graphed below. The host was
> roughly synchronized, then chrony was disabled for the duration
Gabriele provided ntpshmmon output which I've graphed below. The host was
roughly synchronized, then chrony was disabled for the duration of the
test. NTP1 (pps) drifted slightly (0.7 msec) during the test, but that was
too small to be visible on the scatterplot.
The notable feature is that NTP0
On Mon, Feb 28, 2022 at 1:12 PM Miroslav Lichvar
wrote:
> On Mon, Feb 28, 2022 at 10:37:09AM +0100, Gabriele Coppi wrote:
> > On Mon, Feb 28, 2022 at 8:46 AM Miroslav Lichvar
> > wrote:
> > > On Fri, Feb 25, 2022 at 12:10:40PM +0100, Gabriele Coppi wrote:
> > > > refclock SHM 0 precision 1e-1
On Mon, Feb 28, 2022 at 10:37:09AM +0100, Gabriele Coppi wrote:
> On Mon, Feb 28, 2022 at 8:46 AM Miroslav Lichvar
> wrote:
> > On Fri, Feb 25, 2022 at 12:10:40PM +0100, Gabriele Coppi wrote:
> > > refclock SHM 0 precision 1e-1 delay 0.5 refid GPS
> > > refclock SHM 1 precision 1e-7 refid PPS
> >
On Mon, Feb 28, 2022 at 8:46 AM Miroslav Lichvar
wrote:
> On Fri, Feb 25, 2022 at 12:10:40PM +0100, Gabriele Coppi wrote:
> > I am having some issues running Chrony with only GPS+PPS (coming from the
> > GPS) on RPi 4. At the startup gpsd starts running with no particular
> issue
> > and I got
On Fri, Feb 25, 2022 at 12:10:40PM +0100, Gabriele Coppi wrote:
> I am having some issues running Chrony with only GPS+PPS (coming from the
> GPS) on RPi 4. At the startup gpsd starts running with no particular issue
> and I got GPS and PPS solution with no problem checking gpsmon. I have
>
11 matches
Mail list logo
