Re: [Linuxptp-users] Output of ptp4l

[Adrian K. <ad...@dr...>]

On Wed, May 15, 2013 at 08:34:43PM +0000, Keller, Jacob E wrote:

> The numbers you are seeing are...
> 
> ptp4l[1821233.508]: Clock identifier per the PTP standard.
> 
> master offset 93511: The calculated offset from master measured in
> nanoseconds.
> 
> s2: The state of the P/I servo, there are 3 states, 0, 1, 2 with the
> following meanings.
> 
> 0: initial state, servo is unlocked, meaning measurements being
>    calculated but not actually applying adjustment.
> 1: second state: used when the clock will be jumped.
> 2: third state: servo is locked to master, and is being adjusted
> 
> adj  +10006: The frequency adjustment measured in parts per  billion
> (might be parts per million for SW, I don't actually know for sure)
> This is a measurement of percent-like adjustment in the frequency, so
> in this case it means the frequency of the SW clock has been increased
> by ten thousand parts per billion. This means for every 1 billion
> seconds of nominal time, 10006 seconds in addition will have
> accumulated.
> 
> path delay      53481: The measurement in nanoseconds of the delay
> between this node and the master node (or the peer if using peer
> delay)

How about copy&pasting this to README.org?


I can propose a patch to the devel ML. While at it, I'd probably add an
example section to ptp4l.8 showing gPTP.cfg. It's easier to see how a
proper config file should look like than to work oneself through a
paraphrased description of the config format.


Just my €0.02

-- 
mail: ad...@th...  	http://adi.thur.de	PGP/GPG: key via keyserver