|Subject:||Re: gpsd + chrony + pps|
|Date:||Sat, 13 Jun 2020 09:31:22 +0200|
|User-agent:||Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0|
armbian (debian buster based)
For reference:1. What OS brand & version are you using?
2. Are you running this on a RPi, or a x86 computer?
Orange pi zero (arm). PPS is on gpio.
I just set this up last week with a serial/pps line + intel computer + gpsd- (3.20 / master) + chrony (2.11). So, it definitely _CAN_ be done, but the setup can be finicky.
It's a very different setup, your timepulse is on the tty
I found the chrony.pps0.sock trick here:
(beaglebone and timepulse on gpio)
On Fri, Jun 12, 2020 at 6:03 AM Stéphane Péneau <firstname.lastname@example.org> wrote:
I've made many tests to use the timepulse output on my U-blox ZED-F9P
with gpsd and chrony to get an accurate time.
I've never had a working solution if I try to use a socket like
But if I replace 'ttyXX' with my 'pps', it works.
refclock SOCK /var/run/chrony.pps0.sock refid PPS2 lock GNSS <== OK
refclock SOCK /var/run/chrony.ttyACM0.sock refid PPS2 lock GNSS <== NOK
Is there a mistake in the documentation ?
|[Prev in Thread]||Current Thread||[Next in Thread]|