Configuration Instruction

Transcription

1 Configuration Instruction SIMATIC PCS 7 SIMATIC IT Integration PCS 7 / SIMATIC IT Integration Pack 2007 Time Synchronization

2 Warranty, liability and support Note The application examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to pro-vide support for typical applications. You are responsible in ensuring that the de-scribed products are correctly used. These application examples do not relieve you of the responsibility in safely and professionally using, installing, operating and servicing equipment. When using these application examples, you recognize that Siemens cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these application examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications - e.g. Catalogs - then the contents of the other documents have priority. Warranty, liability and support We do not accept any liability for the information contained in this document. Any claims against us - based on whatever legal reason - resulting from the use of the examples, information, programs, engineering and performance data etc., described in this application example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health The above provisions does not imply a change in the burden of proof to your detriment. Copyright 2008 Siemens A&D. It is not permissible to transfer or copy these application examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following address: mailto:online-support.automation@siemens.com V /40

3 Table of Content Table of Content Table of Content Introduction Test environment Equipment for the Windows active directory domain Installed software... 6 Operating systems... 6 SIMATIC software Time master and time client overview Time synchronization of the domain controllers Settings on the time master domain controller Settings on the time master client domain controller Time synchronization of the domain computers SIMATIC PCS 7 OS Server SIMATIC PCS 7 OS Multiclient SIMATIC BATCH Server and SIMATIC Engineering System General Information about DCF Installation of DCF77 Client Creating a matching user account for the DCF Service settings for DCF77 Client Configuring the DCF77 Client SIMATIC IT Server with OS Multiclient installed with DCF77 for the Foundation server Time synchronization of the SIMATIC AS Settings on the Engineering System Settings on the SIMATIC PCS 7 OS Servers References Abbreviations V /40

4 Introduction 1 Introduction Time synchronization is very important. In a plant, which is using SIMATIC software, time is used for synchronizing, tracing, documenting and archiving processes and values. Therefore it is mandatory to have the same time on every computer. The time between the terminal bus (computers) and process bus (AS s) must also be synchronized. CAUTION It is necessary to plan and configure time synchronization for your plant including all SIMATIC computers and all AS s (CPU). 1.1 Test environment The following schema shows the test environment which is used to set up the time synchronization in a domain in an overview: Figure 1-1: Schema of the Windows active directory domain computers A private IP address band is used with fixed IP addresses. V /40

5 Introduction Equipment for the Windows active directory domain 2 Windows active directory domain controllers (DNS, WINS) 2 SIMATIC PCS 7 OS Servers (redundant) 2 SIMATIC BATCH Servers (redundant) 1 SIMATIC PCS 7 Engineering System (ES) 2 SIMATIC PCS 7 OS Multiclient + SIMATIC BATCH Client 1 SIMATIC IT Production Modeler 1 SIMATIC IT Historian + PPA DB 1 SIMATIC IT Report Manager/ CAB engineering 1 SIMATIC IT components software + SITMesDB 1 SIMATIC AS CPU 417 with a CP V /40

6 Introduction Installed software Operating systems The used operating systems for the domain computers can be found in the following table. Table 1-1 Server Client Station Domain Controller Installation Windows 2003 MUI (Multilanguage User Interface) with SP2 Internet Explorer V6.0 SP2 ( ) Image software Windows XP SP2 Image software Windows 2003 MUI (Multilanguage User Interface) with SP2 Internet Explorer V6.0 SP2 ( ) SIMATIC software SIMATIC software and its required software packages (e.g. message queuing, SQL Server 2005 with SPx,..) are installed as needed. The installed software for SIMATIC PCS 7 and SIMATIC IT is the released Integration Pack 2007 on top of the released SIMATIC Versions. Table 1-2 Product SIMATIC PCS 7 SIMATIC IT V7.0 SP1 Version Microsoft SQL 2005 SP1 HF PCS 7 / SIMATIC IT Integration Pack 2007 Part1 Updates SIMATIC PCS 7 V6.3 SP1 Microsoft SQL 2005 SP2 PCS 7 / SIMATIC IT Integration Pack 2007 Part2 Updates SIMATIC IT A detailed list of the installed SIMATIC software can be found in the attachment A of the document SIMATIC software in a domain. V /40

7 Introduction 1.2 Time master and time client overview The following picture gives an overview of the used tools for time synchronizing the test environment. Figure 1-2: Schema of the Time synchronization Domain controller The domain controllers (in our case two) will serve as time master in the domain. They are synchronized with the build in Windows NTP (network time protocol). One DC is the time master while the second one is the time master client. SIMATIC PCS 7 OS Server SIMATIC PCS 7 OS Multiclient The SIMATIC PCS 7 OS Servers will be used to synchronize directly with the domain controllers using the build in OS Time Synchronization tool. The same tool is used for the SIMATIC PCS 7 OS Multiclient computers. They will synchronize directly with the attached SIMATIC PCS 7 OS Servers as there time masters. Other SIMATIC PCS 7 computers SIMATIC PCS 7 computers which have no SIMATIC PCS 7 OS Multiclient installed (e.g. SIMATIC BATCH server, SIMATIC ES, pure SIMATIC V /40

8 Introduction BATCH clients) use a 3rd party tool called DCF77 service to synchronize with a SIMATIC PCS 7 OS Server. SIMATIC IT Foundation Server The SIMATIC IT Foundation Server will use the 3rd party tool called DCF77 service to synchronize with a SIMATIC PCS 7 OS Server. The Foundation Server synchronizes the other SIMATIC IT computers over the build in time alignment function in the System Configuration editor tab Foundation Servers inside the management console. SIMATIC AS The SIMATIC AS will use time synchronization within settings made in SIMATIC PCS 7 STEP7 and the SIMATIC PCS 7 OS Server project. NOTE The time synchronization described in this document is an example. There exist other possibilities of applying time synchronization in an environment. Which possibility you choose does not matter as long as you think about the topic time synchronization and apply it to your environment. V /40

9 Time synchronization of the domain controllers 2 Time synchronization of the domain controllers As the domain controllers are used as time master in the environment you should make sure that the domain controllers in your environment are time aligned. Just imagine what happens, if one domain controller fails and the other takes over the time mastership and the times of these domain controllers would be different. Clearly the time must be aligned. To do this we use the Windows NTP (network time protocol) for synchronizing the domain controllers. We are not synchronizing our domain time to an outside UTC time source. There exists e.g. the possibility to synchronize the domain time over external devices DCF77 GPS Siclock Windows time synchronization using NTP The NTP is a protocol that can be used for synchronizing times of computers. NTP Explanation NTP is used for synchronizing clocks of computers. NTP is using UDP port 123 and is one of the oldest protocols still in use. Inside Windows 2003 the W32time service can be used to synchronize times between computers. Inside the Microsoft support pages you will find some addition hints to this topic. The W32Time service is an integrated service in Microsoft Windows 2000/2003. The W32Time service synchronizes an authoritative time server with an outside time source. The authoritative time server is a domain controller that uses the W32Time service to make sure that the computer date and time settings are correctly synchronized throughout an organization. With the settings described in the document under the Microsoft support page it is possible to set one domain controller as the base time while the second one uses the provided time. V /40

10 Time synchronization of the domain controllers 2.1 Settings on the time master domain controller [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config] "AnnounceFlags"=dword: a [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Param eters] "ServiceMain"="SvchostEntry_W32Time" "ServiceDll"=hex(2):43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,00,53,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,33,00,\ 32,00,74,00,69,00,6d,00,65,00,2e,00,64,00,6c,00,6c,00,00,00 "NtpServer"="time.windows.com,0x1" "Type"="NoSync" The setting AnnounceFlags indicates that this computer is using an internal clock rather than an external time source. The Type NoSync indicates that this Server does not synchronize with an external time source. Due to this the original setup setting NtpServer which is referenced to an external time source can be still in the registry. Figure 2-1: Registry setting of the time master domain controller V /40

11 Time synchronization of the domain controllers 2.2 Settings on the time master client domain controller [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Param eters] "ServiceMain"="SvchostEntry_W32Time" "ServiceDll"=hex(2):43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,00,53,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,33,00,\ 32,00,74,00,69,00,6d,00,65,00,2e,00,64,00,6c,00,6c,00,00,00 "NtpServer"="AD1.adcgoa.com,0x1" "Type"="Ntp" The Type Ntp indicates that this Server is synchronizing with an external time source. Due to the setting in the NtpServer, where the master domain controller is referenced, this domain controller is using the time provided from the master Server by using the NTP (network time protocol). Figure 2-2: Registry setting of the second domain controller CAUTION Please note that a change to the registry can lead to an unstable system. Changes in the registry happen on your own responsibility. Please make sure that you document your changes and have only authorized personal working in the registry. V /40

12 3 Time synchronization of the domain computers There exist several possibilities to setup time synchronization for the domain computers. In this document one possible way is described. For other possibilities of setting up time synchronization please refer to the references provided at the end of this document. 3.1 SIMATIC PCS 7 OS Server In the test domain are two redundant SIMATIC PCS 7 OS Servers. These Servers have a key role for the time synchronization as these Servers are directly synchronized with the domain controllers. The other SIMATIC computers receive their time from the SIMATIC PCS 7 OS Servers. Settings in the Time synchronization editor To synchronize the SIMATIC PCS 7 OS Servers with the domain controllers use the Editor Time Synchronization inside the WinCC explorer on the Engineering System. Due to marking the check box Synchronization via Terminal Bus (Slave) and using the option Use the time from a specific computer the software allows you to browse for computers on the network with help of the browsing buttons ".".The domain controllers in our environment are called AD1 and AD2 as you can see in in the following figure. Figure 3-1 Time synchronization V /40

13 3.2 SIMATIC PCS 7 OS Multiclient To synchronize a SIMATIC PCS 7 OS Multiclient you can also use the editor Time Synchronization inside the WinCC explorer (like on the Servers). Simply mark the check box Synchronization via Terminal Bus (Slave) and by using the option Use the time from a connected WinCC Server your Multiclient will be synchronized with the SIMATIC PCS 7 OS Server which is synchronized with the domain controllers. Figure 3-2 Setting of the time synchronization V /40

14 3.3 SIMATIC BATCH Server and SIMATIC Engineering System The time synchronization on a computer without a SIMATIC PCS 7 OS is a little bit different because you cannot use the editor Time synchronization. On the PCS 7 DVD PCS 7 V7.0 SP1 is an additional tool called DCF77 in the path Additional_Products\DCF77Client_V1.22 which you can use to synchronize your time. The DCF77 Client program is an additional tool for synchronizing the time of computers. In the following chapters the installation and maintaining of this tool is described. Figure 3-3 Installation path of the DCF77 software 3.4 General Information about DCF77 DCF77 is a long wave time signal and standard-frequency radio station. Its primary and backup transmitter are located in Mainflingen, about 25 km south-east of Frankfurt, Germany. DCF77 has been in service as a standard-frequency station since 1959; date and time information was added in The 77.5 khz carrier signal is generated from local atomic clocks that are linked with the German master clocks in Braunschweig. With a relativelyhigh power of 50 kw, the station can be received in large parts of Europe, as far as 2000 km from Frankfurt depending on signal propagation and local interference. DCF77 is standing for D=Deutschland (Germany) V /40

15 C=long wave signal F=Frankfurt 77=frequency: 77.5 khz Installation of DCF77 Client NOTE There exist some restrictions with the tool DCF77. These can be found in the DCF77_english.wri in the setup folder. While installing the software on a Windows 2003 Server SP1 or XP SP2 system you will receive a failure message which states you cannot use this software on this operating system. Ignore this message and install the software. You find information to this topic also mentioned in the SIMATIC PCS 7 Readme. After starting the setup.exe the following message must be ignored. Figure 3-4 Installing DCF77 Press the Yes button. V /40

16 Figure 3-5 Installing DCF77 Continue with Next. Figure 3-6 Installing DCF77 Change the standard destination path if you like and / or continue with Next. V /40

17 Figure 3-7 Installing DCF77 Continue with OK. Figure 3-8 Installing DCF77 Continue with YES. V /40

18 Figure 3-9 Installing DCF77 Continue with Next. Figure 3-10 Installing DCF77 Continue with Next. V /40

19 Figure 3-11 Installing DCF77 Confirm the message with OK. Figure 3-12 Installing DCF77 Press OK to restart your system Creating a matching user account for the DCF77 The following instruction is a workaround for computers with Windows Server 2003 SP2 or XP Professional SP2. You have to add a local power user (e.g. DCF77 ) for every computer using the DCF77 Client (in our system the SIMATIC PCS 7 BATCH Servers, SIMATIC Engineering System, SIMATIC PCS 7 OS Servers and also the SIMATIC IT Foundation servers). The procedure corresponds to the description from the installation DVD Additional_Products\DCF77Client_V1.22\ DCF77_english.wri. Open the user administration in the computer management via the menu command Start > Control Panel > Administrative Tools > Computer Management > Local Users and Groups > Users. V /40

20 Figure 3-13 Configuring DCF77 Add a new user, for example DCF77, with an identical password on every computer. Figure 3-14 Configuring DCF77 The user must be at least a power user! V /40

21 Figure 3-15 Configuring DCF77 The power user requires additional write permission for the Windows event log. Add the user with full access permission in the registry. Start > Run > regedit HKLM\System\CurrentControlSet\Services\Eventlog Click on the Permissions item in the context menu to open the permission dialog. Figure 3-16 Configuring DCF77 Give the local power user (in our case the DCF77 ) rights for writing to the event log. V /40

22 Figure 3-17 Configuring DCF Service settings for DCF77 Client Open the Windows services over Start > Control Panel > Administrative Tools > Services. Here open the Properties Dialog of the "DCF77 Zeitsignal- Empfangsdienst". V /40

23 Figure 3-18 Configuring DCF77 Figure 3-19 Configuring DCF77 Switch into the "Log On" tab and under "This account:" - enter the user you have created. In our case this is the DCF77 Power user (described in 3.4.2). Close the dialog with OK. V /40

24 Figure 3-20 Configuring DCF77 Confirm the following two messages with OK. Figure 3-21 Configuring DCF77 Figure 3-22 Configuring DCF77 Stop and restart the service as requested from the software. V /40

25 3.4.4 Configuring the DCF77 Client After installing and configuring the local power user you can change and control the settings for the DCF77 Client as followed. Start the DCF77 service via Start > Control Panel > DCF-77. Figure 3-23 Configuring DCF77 V /40

26 The configuration of the DCF77 Service can be done as followed. Figure 3-24 DCF77 Client configuration Port (Browse the computer you want to use as master computer for the time) As you can see the DCF77 Client software on these computers is configured to talk with the local power user DCF77 to the OS03. Due to this configuration you have the computers which are using the DCF77 Client synchronized to the domain controllers over the synchronization with the OS03 Server. NOTE Please note that on the SIMATIC BATCH and the engineering stations, where the DCF77 Client service is used, you have no redundant time synchronization. If in this case the OS03 Server is not available. You have no time alignment for the computers which use the DCF77 Client. First Update after (After which time starts the time synchronization?) Interval (How often will the time synchronization happen?) Maximum deviation (What time shift is allowed to the time master inserted in the port?) V /40

27 Checking the event viewer You can open the event viewer via Start > Control Panel > Administrative Tools > Event Viewer. Figure 3-25: A lot of information is entered in the event log when checking every check box NOTE If you check all checkboxes for the event log Time, All valid telegrams and Quality changes you will have a lot of messages in your event log (see Figure 3-24). V /40

28 The following figure shows an example for an event log message: Figure 3-26 Example for an event log message when checkbox Time is marked There is a difference of 16 (a=-41 x 100 ns, elapsed=0) ms between your system time and correct time. If you uncheck the checkbox "time" inside the DCF77 service event log options, you will not have this message anymore but you are missing also the following messages: The time signal is good and stable (again). Service V1.22 (Lizenz-Nr ) started, Signal via NetRemoteTOD("\\OS03"). You still receive the message: The system time was set (256 ms). V /40

29 NOTE Make sure you test the event log messages and make sure they meet your goals and expectations. 3.5 SIMATIC IT Server with OS Multiclient installed NOTE If there is a SIMATIC PCS 7 OS Multiclient installed on the HISTORIAN computer (like in the last integrated version of V6.1 SP1 HF4) or another SIMATIC IT computer, it is possible to use the internal time synchronization of the SIMATIC PCS 7 OS Multiclient. The settings would be the same as shown in 3.2. With the new integrated version V6.3 SP1 HF2 + Integration Pack 2007 we are using the SPOSA station instead of a locally installed SIMATIC PCS 7 OS Multiclient on the HISTORIAN machine. We cannot use the internal time synchronization of the local Multiclient anymore. If you installed on the Foundation Server a SIMATIC PCS 7 OS Multiclient which is not started, you have no time synchronization aligned to the domain controllers for the SIMATIC IT network. Only internal all computers in the SIMATIC IT network will be aligned. As of Version V6.3 SP1 HF2 of SIMATIC IT we are using the SPOSA station of SIMATIC PCS 7 on the HISTORIAN instead of the local Multiclient. Therefore we cannot use the internal Time synchronization of WinCC anymore like we did this in the last Integration Pack with DCF77 for the Foundation server We can install the DCF77 software on the SIMATIC IT Historian, which is also our SIMATIC IT Foundation server. The usage of the DCF is shown in 3.4. Due to this configuration all SIMATIC IT computers are time aligned over the Foundation server SITHIST with the SIMATIC PCS 7 environment. NOTE As of Version V6.3 SP1 HF2 + Integration Pack 2007 of SIMATIC IT we are using the DCF77 client software for the Time synchronization for the Foundation servers of SIMATIC IT to time align the SIMATIC IT environment with the SIMATIC PCS 7 environment. V /40

30 The configuration of the Foundation server is done in the SIMATIC IT Management console in the System configuration. This can be done via Configuration > System > Register Foundation Servers or before starting your project from the Plant Management console using Tools > System Configuration > Register Foundation Servers : Figure 3-27 SITHIST is foundation server and is used to time align all computers in the SIT network Due to the setting time alignment over the Foundation Servers all SIMATIC IT computers in the network are aligned to the common domain time as the DCF77 gets the actual time from the SIMATIC PCS 7 OS server which is time aligned with the domain servers. NOTE The time alignment of the SIMATIC IT computers over the Foundation Servers is only functional when the SIMATIC IT management console is started and running. The configuration of the Network can be done from the Plant Management console before starting your plant using V /40

31 Tools > Network Configuration or from the SIMATIC IT Management console using Configuration > Network Configuration. Figure 3-28 SIMATIC IT network configuration This opens the Network Configuration Dialog. Figure 3-29 SIMATIC IT network configuration V /40

32 If you want to add a new SIMATIC IT computer, choose the User Unit Operator Workstation. Figure 3-30 SIMATIC IT network configuration Configure the data for the IP Address Figure 3-31 SIMATIC IT network configuration V /40

33 ...click Finish and you have added the next workstation. Figure 3-32 SIMATIC IT network configuration V /40

34 Time synchronization of the SIMATIC AS 4 Time synchronization of the SIMATIC AS After synchronizing the computers in the environment it makes no sense using a SIMATIC AS which would have another time as the SIMATIC computers. Therefore you need to synchronize the time of your SIMATIC AS in your test environment to the master time in your domain. 4.1 Settings on the Engineering System To insert the time synchronization for the AS you have to do some steps in the project on the Engineering System. Open the HW Config of the CPU and switch into the tab Diagnostics/Clock. Check the Synchronization type "In the PLC" to As slave. Figure 4-1 Hardware Configuration of the CPU V /40

35 Time synchronization of the SIMATIC AS Open afterwards the properties of the CP443-1 and activate the option Activate SIMATIC time-of-day synchronization in the corresponding tab. Figure 4-2 Hardware Configuration of the CP V /40

36 Time synchronization of the SIMATIC AS Open the HW Config of the OS Server and there the properties dialog of the CP1613. Activate the settings for the Time-of-Day Synchronization in the tab Options. Figure 4-3 Hardware Configuration of the CP1613 V /40

37 Time synchronization of the SIMATIC AS Open the Time Synchronization editor inside the SIMATIC PCS 7 OS Server project. Insert the setting CP1613 (ISO) for the Synchronization via System Bus (Master, Slave) as Master for the Access point 1. Figure 4-4 Time Synchronization for the CP1613 V /40

38 Time synchronization of the SIMATIC AS 4.2 Settings on the SIMATIC PCS 7 OS Servers After downloading the HW Config and Net Pro settings for the SIMATIC PCS 7 OS Servers you can check on the Servers the settings for the CP1613 card as followed: Start > All Programs > SIMATIC > SIMATIC NET > Configuration Console Figure 4-5 Time of day function of the CP1613 card is activated Make sure that the "Time-of-day adjustment" is activated. NOTE You need Administrator rights to change anything by hand (not recommended) in the configuration console of the CP1613. You should download and handle everything from the engineering station and should not configure these settings by hand on the SIMATIC PCS 7 OS Servers. V /40

39 References 5 References The following documents, help files and FAQ where used in setting up the test environment. SIMATIC PCS 7 time synchronization (English) (German) SIMATIC PCS 7 engineering handbook: OS (English) (German) SIMATIC PCS 7 engineering handbook: ES (English) (German) Security Handbook (English) SICLOCK, DCF77, GPS World Wide Web: Service and Support Automation and Drives V /40

40 Abbreviations 6 Abbreviations In this manual are used several abbreviations. Please find here the corresponding complete name. Table 6-1 Abbreviation AD AS CAB CP DB DHCP DNS ES FAQ HF HMI IP MUI NTP OS SIT SQL SP UDP UTC WINS Complete name Active Directory Automation Station Client Application Builder Communication Processor Data Base Dynamic Host Configuration Protocol Domain Name Service Engineering System Frequent Asked Question Hot Fix Human Machine Interface Internet Protocol Multilanguage User Interface Network Time Protocol Operator Station SIMATIC IT Structured Query Language Service Pack User Datagram Protocol Coordinated Universal Time Windows Internet Naming Service V /40