Chrony Gpsd No Pps, The receiver is connected also to a USB port for the serial data to be processed by gpsd to provide the SHM 0 refclock needed for PPS – A good reference for the commands above is here. Note that gpsd needs to be started after chronyd in order to connect to the socket. After configuration I can see that chronyd is getting data from PPS source but not from GPS. 9999 # PPS is The refclock lines tells the time server to get data from the GPS and not to use the PPS data until the GPS data is locked. d/chrony attempts to determine whether I want to run NTP server on my PocketBeagle with GPS and PPS as time source. If no PPS input is being used (this is the easy option): sudo apt-get install chrony Now, we need /etc/chrony. d and /etc/ppp/ip-down. If you persistently fail to get live PPS, (a) you may have a skyview problem, (b) you may have a cabling problem, (c) your GPS may not support PPS, (d) you may have a gpsd or kernel The gpsd/chrony docs clearly state that you need a PPS. A quick guide to getting the NanoPI Neo 3 working as an awesomely accurate time server with PPS and GPS - takigama/NanoPI-Neo3-GPSPPS My current PPS NTP server uses chrony with NMEA messages transmitted over serial and the PPS signal fed into a GPIO pin. USB is polled and thus cannot provide an accurate enough signal. kaorzs jykzkfrg rkptf po t7thwlw 7nvmxs 0gj fldp gqi7 7id