d4b97f497c
The logic for the Automotive Profile added a message interval update mechanism that triggers whenever the servo enters the "stable locked" state. This SERVO_LOCKED_STABLE state is active when the configuration option servo_offset_threshold is non-zero and servo_offset_threshold criteria is satisfied. However, in general, the state of the servo can and should be independent of any profile specific optional behavior. In particular, the "stable locked" state will be used in the future to trigger other kinds useful logic. For example, an upcoming write phase mode feature would like to take advantage of the SERVO_LOCKED_STABLE state to trigger its activation. This patch introduces a proper configuration option to enable transmission of the message interval request that is specific to the Automotive Profile. Signed-off-by: Vincent Cheng <vincent.cheng.xh@renesas.com> Signed-off-by: Richard Cochran <richardcochran@gmail.com>
39 lines
887 B
INI
39 lines
887 B
INI
#
|
|
# Automotive Profile example configuration for slaves containing those
|
|
# attributes which differ from the defaults. See the file, default.cfg, for
|
|
# the complete list of available options.
|
|
#
|
|
[global]
|
|
#
|
|
# Options carried over from gPTP.
|
|
#
|
|
gmCapable 1
|
|
priority1 248
|
|
priority2 248
|
|
logSyncInterval -3
|
|
syncReceiptTimeout 3
|
|
neighborPropDelayThresh 800
|
|
min_neighbor_prop_delay -20000000
|
|
assume_two_step 1
|
|
path_trace_enabled 1
|
|
follow_up_info 1
|
|
transportSpecific 0x1
|
|
ptp_dst_mac 01:80:C2:00:00:0E
|
|
network_transport L2
|
|
delay_mechanism P2P
|
|
#
|
|
# Automotive Profile specific options
|
|
#
|
|
BMCA noop
|
|
slaveOnly 1
|
|
inhibit_announce 1
|
|
asCapable true
|
|
ignore_source_id 1
|
|
# Required to quickly correct Time Jumps in master
|
|
step_threshold 1
|
|
operLogSyncInterval 0
|
|
operLogPdelayReqInterval 2
|
|
msg_interval_request 1
|
|
servo_offset_threshold 30
|
|
servo_num_offset_values 10
|