Re: [chrony-users] Setting up Chrony with PPS

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]




William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

On Fri, 19 Feb 2016, Deven Hickingbotham wrote:



On 2/18/2016 11:36 PM, Miroslav Lichvar wrote:
The solution is to compile chrony with PPS support (using the
timepps.h header) and use the PPS refclock instead of SOCK. gpsd would
just provide the NMEA timing as a SHM refclock with noselect option,
to which the PPS refclock would be locked as shown in the example in
the chrony manual. This would also be a good opportunity to switch to
a more recent chrony release, 1.24 was actually the first release with
support for reference clocks and there were some bugs fixed since
then.

Okay, this makes sense as I had to recompile ntp to get it working with PPS.

1. Where do I find timepps.h? If I have to download it, where should it be placed?

You might already have it. Otherwise just google timepps.h
Or install pps-tools from the repository.

You can put it into /usr/include if you wish. Or in the same directory as the
chrony source files, in which case change #include <timepps.h> to #include
"timepps.h" in refclock_pps.c

Debian may well have already installed it.

..

2. Does timepps.h just have to be present or do I have to change it so it looks for GPIO 4?

Nope it just has to be present.





3. What would be the correct way to configure chrony.conf to recognize PPS?

I suggested one. If you have /dev/pps0 which you say you do,
 refclock PPS /dev/pps0

However, as I said, first you have to figure out if your pps0 is really
working. Check if it is assert or clear that gives the correct time.
What you posted on the assert looks very very suspicious.




4. Other than stopping the chrony service before installing v2.3, are there any other steps that should be taken before updating?

Thanks,

Deven


--
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/