If true, the host will use NTP to sync its clock with time values retrieved from other servers.

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.

Default is false. If true, when the JACE boots, before the stations starts or the ntpd starts, it executes the ntpdate command. This updates the system local time.

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

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.