Configuration Guide#

This guide describes the configuration of the S-CORE time module components.

TimeSlave Daemon (time_slave)#

The behavior of the TimeSlave is controlled by the GptpEngineOptions structure. Currently, only a subset of these options can be overridden at runtime via command-line arguments. For all other options, the hard-coded default values are used.

Command-Line Arguments#

The following argument is available to configure the TimeSlave at runtime:

Argument	Overrides	Description
`-i, --interface <name>`	`iface_name`	Mandatory Runtime Parameter. Specifies the Ethernet network interface. Although the internal default is “emac0”, this must be set correctly at runtime to match the target hardware.

Default Configuration (GptpEngineOptions)#

The following table lists all available options and their default values as defined in the source code. Currently, only iface_name can be changed without recompiling the application.

Table 13 GptpEngineOptions Default Values#
Option	Default Value	Description
`iface_name`	`"emac0"`	The network interface to use for gPTP traffic.
`pdelay_interval_ms`	`1000`	The interval in milliseconds for sending Peer-Delay measurement requests.
`pdelay_warmup_ms`	`2000`	The initial delay in milliseconds before the first Peer-Delay request is sent.
`sync_timeout_ms`	`3300`	The time in milliseconds without receiving a PTP Sync message before a timeout is declared and the clock is considered unreliable.
`jump_future_threshold_ns`	`500'000'000`	The threshold in nanoseconds (500 ms) for detecting a significant forward time jump.
`domain_number`	`0`	The gPTP domain number. The TimeSlave will only interact with a PTP master in the same domain.
`phc_config`	`disabled`	Configuration for hardware clock (PHC) adjustments. Disabled by default.

Example Invocation#

# Start the TimeSlave, overriding the default interface name "emac0"
./time_slave --interface eth1

Attention

The command-line parsing is currently incomplete. To change parameters other than the interface name, you must modify the default values in the GptpEngineOptions structure and recompile the application. A comprehensive configuration mechanism (e.g., via a JSON file) is planned for future versions.

TimeDaemon (time_daemon) & Client Applications#

The TimeDaemon process and all client applications using the score::time library currently operate without any external configuration. They rely on the default, built-in settings for IPC communication.