Re: Using gpsd
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <jorhdt4wne4dv5ogzuuzjlqwyhhzhdxaxuz2jrsv2wq5zrpiag@k3w5k66w4mht> |
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-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]