An example QNX-based host Ntp Platform Service Editor is shown in Figure 126. This is the default view for the RFC-1305 compliant NtpPlatformService on any QNX-based JACE.
This dialog provides access to some of the key settings of the NTP daemon (ntpd) of the QNX OS running on the host JACE platform.
As in all Ntp Platform Service Editors, there are two main areas: Settings at top, Time Servers at bottom. Also, starting in AX-3.6, the NtpPlatformServiceQnx has an available “Sync Now” action. For more details, see Sync Now action.
Settings in the Ntp Platform Service Editor QNX include the following properties:
Enabled
If true, the host will use NTP to sync its clock with time values retrieved from other servers.
Sync Local Clock to NTP
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
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.
Use Local Clock as Backup
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, andthus not result in more polling.
Generate NTP Statistics
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 ->. Keep in mind that the ntpd is a QNX process; thus NiagaraAX has no control over what it reports.
Each entry in the time servers list in the Ntp Platform Service Editor QNX specifies a server to which the host’s clock will be sync’ed when the service is Enabled (true), and “Sync Local Clock to NTP” is also true. These servers are not used if either of these properties are false.
Controls below the list allow you to add
and delete
servers, as well as reorder up
or down
(to establish priority order, highest at top). Fields for each time server includes the following:
Address
Fully qualified domain name, IP address, or host files alias for the NTP time server.
Peer Mode
Peer mode to use with the server, as either server or peer (symmetricActive).
Burst
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
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
Minimum poll interval for NTP messages, from 4 to 16. Note 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
Maximum poll interval for NTP messages, from 10 to 17. Note 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).
In addition to the “Poll” action present on any NtpPlatformService, starting in AX-3.6 the NtpPlatformServiceQnx component has an additional “Sync Now” action.
As shown in Figure 127, this action produces a popup Sync Now dialog, which is blank.
To use, type in the fully qualified domain name of a public NTP server (as shown above), or else the IP address of any accessible NTP server, and then click .
To verify, look for a related entry in the station’s spy “platform diagnostics” log. Do this in Workbench by right-clicking the station, then selecting ->-> or from the Workbench File menu, -> (Ctrl-L) and enter:
ip:JACE_IP_address│fox:│spy:/platform diagnostics/log
Copyright © 2000-2014 Tridium Inc. All rights reserved.