Controller TimeServers Settings

Controller TimeServers Settings

This view configures NTP (Network Time Protocol) properties in a controller platform.

Figure 348. NTP view in a controller station

To access this view, click Controller Setup > Miscellaneous > TimeServers Settings

Settings properties

Property	Value	Description
Enabled	`true` (default) or `false`	If `true`, the host will use NTP to sync its clock with time values retrieved from other servers.
Sync Local Clock to NTP	`true` (default) or `false`	If `true`, this enables the host to adjust its local clock by means of NTP. If disabled (`false`), the local clock free-runs at its intrinsic time and frequency offset. This flag is useful in case the local clock is controlled by some other device or protocol and NTP is used only to provide synchronization (as server) to other clients. In this case, the local clock driver can be used to provide this function and also certain time variables for error estimates and leap-indicators.
Sync Time At Boot	`true` or `false` (default)	Default is `false`. If true, when the controller boots, before the stations starts or the ntpd starts, it executes the ntpdate command. This updates the system local time.
Use Local Clock as Backup	`true` or `false` (default)	If `true`, should the specified NTP server(s) become unavailable at the time of a poll, the time used is provided by the system clock. This prevents the timing of the polling algorithm in the ntpd (which is executed at specified/changing intervals) from being reset. A `true` value does not result in any change to the NTP daemon’s polling interval (frequency). In fact, by using the local system clock the NTP-calculated polling time would remain the same, and thus not result in more polling.
Generate NTP Statistics	`true` or `false` (default)	If `true`, the NtpPlatformService reports whatever information it can about its operation. To access these statistics with the station opened in Workbench, right-click the NtpPlatformServiceQnx and select Views SpyRemote. Keep in mind that the ntpd is a QNX process; thus Niagara has no control over what it reports.

Time Servers properties

These properties become available when you click the Add button.

Property	Value	Description
Address	server domain name	Fully qualified domain name, IP address, or host files alias for the NTP time server.
Peer Mode	drop-down list	Defines the type of server: `Server` indicates that the contoller platform is in a subordinate role to the server with regard to time synchronization. `Peer` indicates that the platform functions as an equal with the server with regard to time synchronization.
Burst	Drop-down list, `true` or `false` (default)	`false` by default. If `true`, when server is reachable, upon each poll a burst of eight packets are sent, instead of the usual one packet. Spacing between the first and second packets is about 16 seconds to allow a modem call to complete, while spacing between remaining packets is about 2 seconds.
Preferred	Drop-down list, `true` or `false` (default)	If `true`, designates a server as preferred over others for synchronization. Note also that priority order (top highest, bottom lowest) is also evaluated if multiple servers are entered.
Min. Poll Interval	seconds (defaults to 6)	Minimum poll interval for NTP messages, from 4 to 16. Note that units are in “log-base-two seconds,” or 2 to the power of n seconds (NTP convention), meaning from 2 to the 4th (16 seconds) to 2 to the 16th (65,536 seconds).
Max. Poll Interval	seconds (defaults to 10)	Maximum poll interval for NTP messages, from 10 to 17. Note that units are in “log-base-two seconds,” or 2 to the power of n seconds (NTP convention), meaning from 2 to the 10th (1,024 seconds) to 2 to the 17th (131,072 seconds).