2018-04-17 11:08 GMT+02:00 Miroslav Lichvar :
> > >
> > But PPS by itself can't provide datetime, only second synchronization.
> > What would happen if I don't let chrony select GPS clock? Would it know
> > what time is it?
>
> Yes. That's what the lock option is for. It allows a refclock to
> pro
On Tue, Apr 17, 2018 at 10:20:04AM +0200, Alvaro Gamez wrote:
> 2018-04-17 9:00 GMT+02:00 Miroslav Lichvar :
> > You might want to add the noselect option to the GPS refclock
> > directive to not consider it for selection at all. Otherwise, it would
> > be good to at least increase its distance wit
2018-04-17 9:00 GMT+02:00 Miroslav Lichvar :
> On Tue, Apr 17, 2018 at 08:28:43AM +0200, Alvaro Gamez wrote:
> > #- GPS 0 4 37728+11ms[ +11ms] +/-
> > 9045us
> > #* PPS 0 4 37727 +109us[ +105us] +/-
> > 388us
> >
> > Why is
On Tue, Apr 17, 2018 at 08:28:43AM +0200, Alvaro Gamez wrote:
> #- GPS 0 4 37728+11ms[ +11ms] +/-
> 9045us
> #* PPS 0 4 37727 +109us[ +105us] +/-
> 388us
>
> Why is GPS marked as not combined, though?
Because its distance
2018-04-17 1:23 GMT+02:00 Simon Haines :
> Also note that gpsd can sometimes erroneously create a second PPS source,
> thinking that the GPS device is connected with the serial line discipline
> exposing the PPS on a serial port pin. You can cross-check with ppstest,
> but your kernel debug seems
Also note that gpsd can sometimes erroneously create a second PPS source,
thinking that the GPS device is connected with the serial line discipline
exposing the PPS on a serial port pin. You can cross-check with ppstest,
but your kernel debug seems to suggest that the source is indeed pps0.
Simon.
On Mon, Apr 16, 2018 at 09:01:11AM +0200, Alvaro Gamez wrote:
> I've tried your configuration (main difference was only the offset values).
> It sometimes seems to work, but not always.
>
> Here's a series of 'sources' requests output:
> #* GPS 0 47718+90ms[
Hi!
I've tried your configuration (main difference was only the offset values).
It sometimes seems to work, but not always.
Here's a series of 'sources' requests output:
#* GPS 0 47718+90ms[ +306ms] +/-
6773us
#? PPS 0 4 6
Here is the configuration I use for a device that is not network-connected,
and uses GPS+PPS to derive accurate time. Note the offset for the GPS clock
so that the PPS signal can be aligned to the correct GPS time message.
refclock PPS /dev/pps0 poll 4 refid PPS lock GPS
refclock SHM 0 poll 4 offs
On Fri, Apr 13, 2018 at 12:29:56PM +0200, Alvaro Gamez wrote:
> I'm trying to make chrony sync against a GPS and PPS signal, but it seems
> like the PPS is being ignored.
>
> I run gpsd attached to the serial console which has the GPS connected, and
> for PPS I want to use chrony, so this is the c
Hi!
I'm trying to make chrony sync against a GPS and PPS signal, but it seems
like the PPS is being ignored.
I run gpsd attached to the serial console which has the GPS connected, and
for PPS I want to use chrony, so this is the configuration I've set:
# cat chrony.conf
refclock SHM 0 refid GPS
11 matches
Mail list logo
