On 3/8/22, Richard Cochran <richardcoch...@gmail.com> wrote: > On Tue, Mar 08, 2022 at 04:17:29PM +0100, Martin Pecka wrote: >> I've implemented this management option to ease monitoring whether the >> time >> sync is stable or not. Doing it via log parsing doesn't really seem >> practical for me. > > The servo state is an internal variable has no relevance to outside > observers. It does not track whether the servo is actually stable in > the controls theory sense.
I would have liked to have this some years ago, because the LXI specification requires that the clock state appears on the the "Sync Configuration" web page: https://www.lxistandard.org/members/Adopted%20Specifications/Latest%20Version%20of%20Standards_/LXI%20Standard%201.5%20Specifications/LXI%20Device%20Specification%20v1_5_01.pdf?page=50 At the time, we had our own in-house implementation of ptp, and I think I wrote out state changes to a fifo or a file or something. But I also remember adding some vendor specific management messages. The memory fades.... Oh, and here is the LXI 1588 profile if you are interested: https://www.lxistandard.org/Documents/About/LXI%20IEEE%201588%20Profile%201%200_%201%20Dec%2008.pdf -Dale _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
