| Re: [chrony-users] Re: Using gpsd |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
That would surprize me very much, unless you are doing a very slow polling of
the gps pps. .125 sec sound like the original IBMPC I bought in 1980.
Maybe if you told us the hardware you are using and the OS you are using
someone could help more. Now if it is not PPS but is rather reading the NMEA,
then a slow baud rate could give you that, since the sentences can be about
that long at 600Bd. Also, you really only need the NMEA for the first few
seconds until the system knows the seconds.
On Tue, 19 Mar 2024, infection.many550@xxxxxxxxxxx wrote:
[CAUTION: Non-UBC Email]
On Tue, Mar 19, 2024 at 05:29:40PM -0700, Bill Unruh wrote:
refclock PPS /dev/pps0 lock NMEA refid GPS
refclock SOCK /var/run/chrony.clk.ttyS0.sock offset 0.5 delay 0.1 refid NMEA noselect
That says that the system is .5 sec out? Hard to believe. Maybe you
are using the wrong part of the pulse (clear rather than assert?)
FWIW, I'm testing a daemon that reads an *i2c* gps device and feeds to
chrony, and I need to bias it by about 0.250s -- I think it is just
that slow to read the bytes from i2c. But I'm still looking for a
foolish logic error like you suggest.
--
Ian
--
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.