You can configure an M580 controller as an NTP server or an NTP client in the Control Expert NTP tab.
When the controller firmware version is:
Earlier than V4.01, the SNTP protocol is employed and you can configure the controller as:
NTP client
NTP server
Both NTP client and server
V4.01 or any subsequent supporting version(s), the NTPv4 protocol is employed and you can configure the controller as:
NTP server only
NTP server and client
To begin, open the controller configuration tabs in Control Expert.
NTP Service Features
The NTP service has these features:
A periodic time correction is obtained from the reference-standard time server.
There is an automatic switchover to a backup (secondary) time server if an error is detected with the normal time server system.
Controller projects use a function block to read the accurate clock, allowing project events or variables to be time stamped. (Refer to the System Time Stamping User Guide for detailed information about timestamping performance.)
When the M580 controller is configured as either an NTP server or as an NTP client, the BM•CRA312•0 (e)X80 EIO adapter modules are NTP clients of the controller:
When only BM•CRA31200 modules are configured as NTP clients, the accuracy of this server allows time discrimination of 20 ms.
All BM•CRA31200 modules in the network have the same client configuration.
NTP Client Mode
When the controller is configured as an NTP client, the network time service (SNTP or NTPv4) synchronizes the clock in the M580 controller to that of the time server. The synchronized value is used to update the clock in the controller. Typical time service configurations utilize redundant servers and diverse network paths to achieve high accuracy and reliability.
When the controller firmware version is:
Earlier than V4.01, you can specify a primary and secondary NTP server.
V4.01 and any subsequent supporting version(s), you can identify up to 8 NTP servers, and specify the preferred server.
To establish the accurate Ethernet system network time, the system performs the following at power up:
requires the controller to boot
uses the controller to obtain the time from the NTP server
requires a predefined interval until time is accurate; your configuration determines how long before time is accurate
may require several updates to achieve peak accuracy
Once an accurate time is received, the service sets the status in the associated time service register.
The time service clock value starts at 0 until fully updated from the controller.
Model |
Starting Date |
|---|---|
Modicon M580 with Control Expert |
January 1st 1980 00:00:00.00 |
Stop or run controller:
Stop and run have no effect on the accuracy of the clock.
Stop and run have no effect on the update of the clock.
A transition from one mode to the other has no effect on the accuracy of the Ethernet system network time.
Download application:
The status clock value associated with the time service register in the M580 controller is reinitialized after an application is downloaded or after an NTP server swap. The time is accurate after two polling periods.
NTP Server Mode
When the controller is configured as an NTP server, it can synchronize client clocks (such as a BM•CRA31200 (e)X80 EIO adapter module). The controller's internal clock is then used as reference clock for NTP services.
NTP Parameters for a Controller with Firmware earlier than V4.01
Use the pull-down menu in the field to configure the controller as an or an :
Value |
Comment |
|---|---|
|
default: Both the NTP server and the NTP client services of the controller are disabled. |
|
The controller functions as the NTP client. In this case, configure the NTP Server Configuration parameters. NOTE: Enable the NTP client here to automatically
enable the NTP client service on all BM•CRA312•0 adapter modules.
|
|
The Ethernet I/O scanner controller acts as an NTP server. NOTE: Enable the NTP client
here to automatically enable the NTP client service on all BM•CRA312•0 adapter modules and to configure the BM•CRA312•0 to use the controller as the NTP server.
|
Assign values to these parameters in the field:
Parameter |
Comment |
|---|---|
|
the IP address of the NTP server, from which the controller first requests a time value |
|
the IP address of the backup NTP server, from which the controller requests a time value after not receiving a response from the primary NTP server |
|
The time (in seconds) between updates from the NTP server. Smaller values typically result in better accuracy. NOTE: This parameter applies only to
the SNTP protocol and to controllers using a firmware version earlier
than V4.01.
|
NTP Parameters for a Controller with Firmware V4.01
Use the following settings to configure the NTP protocol for controller with firmware V4.01 or any subsequent supporting version(s):
Parameter |
Description |
|---|---|
Server Only / Client Server |
Specify the NTP role of the controller: server only, or both client and server. |
Stratum |
The relative position of the server in the NTP network. This represents the distance of the controller (in its role as NTP server) from the reference clock.
When the controller is operating as:
|
Server IPv4 address1 |
The IP addresses of reference NTP servers used by the controller. Minimum of 4; maximum of 8. |
Used as preferred1 |
Indicates the NTP server in the list to be used by the controller. |
Quality threshold (ms)1 |
Threshold for NTP accuracy. Setting range 0...1000.
The Quality threshold setting is compared to the DDT value NTP_WITHIN. If the Quality threshold is ≥ NTP_WITHIN, the NTP_QUALITY_WARNING DDT item is set to true (1) and the event is recorded in syslog. |
1. If Server Only is selected, these parameters are disabled. |
|

