Richard Cochran
2013-05-17 05:39:48 UTC
Here is what I came up with after the recent discussion about adapting
the servo to the sync interval. I gave this some light testing,
including changing the sync on the fly. Comments are welcome.
Thanks,
Richard
Richard Cochran (6):
Use a consistent frequency estimation interval in the PI controller.
Let the clock servo know the expected sync interval.
Add a table of PI constants, with one entry per sync interval.
Provide a method to install a user constant into the table.
Add a configuration option for changing the table of PI constants.
Remove the legacy PI constant configuration options.
clock.c | 2 +
config.c | 14 ++----
config.h | 2 -
default.cfg | 7 ++-
gPTP.cfg | 2 -
phc2sys.c | 12 +++---
pi.c | 129 +++++++++++++++++++++++++++++++++++++++++++++++-------
pi.h | 21 ++++-----
ptp4l.c | 2 -
servo.c | 5 ++
servo.h | 7 +++
servo_private.h | 2 +
12 files changed, 153 insertions(+), 52 deletions(-)
the servo to the sync interval. I gave this some light testing,
including changing the sync on the fly. Comments are welcome.
Thanks,
Richard
Richard Cochran (6):
Use a consistent frequency estimation interval in the PI controller.
Let the clock servo know the expected sync interval.
Add a table of PI constants, with one entry per sync interval.
Provide a method to install a user constant into the table.
Add a configuration option for changing the table of PI constants.
Remove the legacy PI constant configuration options.
clock.c | 2 +
config.c | 14 ++----
config.h | 2 -
default.cfg | 7 ++-
gPTP.cfg | 2 -
phc2sys.c | 12 +++---
pi.c | 129 +++++++++++++++++++++++++++++++++++++++++++++++-------
pi.h | 21 ++++-----
ptp4l.c | 2 -
servo.c | 5 ++
servo.h | 7 +++
servo_private.h | 2 +
12 files changed, 153 insertions(+), 52 deletions(-)
--
1.7.2.5
1.7.2.5