YASKAWA VIPA System SLIO Manual page 75

Hide thumbs Also See for VIPA System SLIO:
Table of Contents

Advertisement

VIPA System SLIO
4.7.1.1.1
Time-of-day synchronization
NTP method
4.7.1.2
Configuration via additional CP
Proceeding
HB300 | CPU | 013-CCF0R00 | en | 19-30
Hardware configuration - Ethernet PG/OP channel > Take IP address parameters in project
In the NTP mode (Network Time Protocol) the module sends as client time-of-day queries
at regular intervals to all configured NTP servers within the sub net. You can define up to
4 NTP server. Based on the response from the servers, the most reliable and most exact
time-of-day is determined. Here the time with the lowest stratum is used. Stratum 0 is the
time standard (atomic clock). Stratum 1 are directly linked to this NTP server. Using the
NTP method, clocks can be synchronized over subnet boundaries. The configuration of
the NTP servers is carried out in the Siemens SIMATIC Manager via the CP, which is
already configured.
1.
Open the Properties dialog by double-clicking 'PN-IO' .
2.
Select the tab 'Time-of-day synchronization' .
3.
Activate the NTP method by enabling 'Activate NTP time-of-day synchronization' .
4.
Click at [Add] and add the corresponding NTP server.
5.
Set the 'Update interval' you want. Within this interval, the time of the module is
synchronized once.
6.
Close the dialog with [OK].
7.
Save and transfer your project to the CPU.
ð After transmission, the NTP time is requested by each configured time server
and the best response for the time synchronization is used.
Please note that although the time zone is evaluated, an automatic
changeover from winter to summer time is not supported. Industrial sys-
tems with time-of-day synchronization should always be set in accord-
ance to the winter time.
With the FC 61 you can determine the local time in the CPU. More infor-
mation about the usage of this block may be found in the manual
"SPEED7 Operation List" from VIPA.
This is the conventional variant for configuration and is supported by all firmware ver-
sions. If possible, always use the configuration via the internal interface, otherwise the fol-
lowing disadvantages result:
n
Address overlaps are not recognized in the Siemens SIMATIC Manager.
n
For PROFINET devices only the address range 0 ... 1023 is available.
n
The addresses of the PROFINET devices are not checked with the address range of
the CPU by the Siemens SIMATIC Manager for address overlaps.
Deployment CPU 013-CCF0R00
75

Advertisement

Table of Contents
loading

Table of Contents