Re: [chrony-users] getting chrony to work with gpsd on raspbian jessie with gps hat

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

> now it seems to lock on PPS1, but I don't think PPS1 is not a valid source.

Sorry, you double negative is completely confusing. It looks to me like pps1
is a fine source and so does chrony. What problem do you have with it?


> here's the results for chronyc sources:
>
> 210 Number of sources = 2
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
> ===============================================================================
> #? GPS                           0   4     0  1192   -43.4s[ -43.7s] +/-  200ms
> #* PPS1                          7   4   377    20     +9ns[ +773ns] +/-  629ns
>
>
>
>
>
> > Sent: Monday, February 05, 2018 at 6:03 AM
> > From: "Miroslav Lichvar" <mlichvar@xxxxxxxxxx>
> > To: chrony-users@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [chrony-users] getting chrony to work with gpsd on raspbian jessie with gps hat
> >
> > On Fri, Feb 02, 2018 at 11:35:42PM +0100, Charles Muggen wrote:
> > > # set larger delay to allow the NMEA source to overlap with
> > > # the other sources and avoid the falseticker status
> > > refclock SHM 0 refid GPS precision 1e-1 offset 0.9999 delay 0.2
> > > refclock SHM 1 refid PPS precision 1e-9
> >
> > If you are using the SHM 1 source, which is based on PPS with gpsd,
> > I'd suggest to either remove the first line or add noselect to it.
> >
> > You could also use the PPS device directly with SHM 0, e.g.
> >
> > refclock SHM 0 offset 0.5 delay 0.2 refid NMEA noselect
> > refclock PPS /dev/pps0 lock NMEA refid GPS
> >
> > > I made a change to my /boot/config.txt
> > > I had to add a line that says
> > >     dtoverlay=pps-gpio,gpio=4
> > > This points the PPS server to pin 4 of the GPS HAT.
> > >
> > > hmmm, maybe the thing is working... but should the PPS show an asterisk "*"?
> >
> > How is gpsd started? With a GPIO PPS, I think it needs to be started
> > with both devices: serial (e.g. /dev/ttyS0) and PPS (e.g. /dev/pps0).
> >
> > --
> > Miroslav Lichvar
> >
> > --
> > To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> > with "unsubscribe" in the subject.
> > For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> > with "help" in the subject.
> > Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.

--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.