Data Synchronization between Head and Field PLCs with Storage of the Process Values in CSV Files

Transcription

1 Application Description 03/2014 Data Synchronization between Head and Field PLCs with Storage of the Process Values in CSV Files SIMATIC STEP 7 (TIA Portal), WinAC RTX, WinAC ODK

2 Warranty and Liability Warranty and Liability 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 customerspecific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we 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 the contents of the other documents have priority. 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 ). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of Siemens Industry Sector. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, stateoftheart industrial security concept. Thirdparty products that may be in use should also be considered. For more information about industrial security, visit To stay informed about product updates as they occur, sign up for a productspecific newsletter. For more information, visit Entry ID: , V1.0, 03/2014 2

3 Table of Contents Table of Contents Warranty and Liability Task Solution Overview Hardware and software components Components used Sample files and projects Functionality of the Application General overview The blocks of the STEP 7 program "Archive_Data" function block "SysDateTimeToInt" function block "Global_Data" data block Installation Installation of the hardware Installation of the software Startup of the SIMATIC Components IP addresses used Loading the PLCs Operation of the Application Creating an executable file from the C# program Starting archiving Establishing a connection with the shared memory of the WinAC Defining the archive file name and starting Stopping archiving Adding More Field PLCs Changes in the new field PLC Changes in the head PLC Changing the shared memory access Addresses used Changes in the STEP 7 program Changes in the C# program Screenshot of STEP 7 program expansion Screenshot of C# program expansion References History Entry ID: , V1.0, 03/2014 3

4 1 Task 1 Task Introduction Process value exchange between a head PLC and several field PLCs requires performant cyclic communication. This communication is for the head PLC to collect all process values of the field devices and archive them as CSV files. Overview of the automation task The figure below provides an overview of the automation task. Figure 11 Head PLC Archiving in CSV files Description of the automation task Field PLC 1 Field PLC 2 Field PLC n The head PLC is supposed to process the process values from the field PLCs in the following steps: Collect process values by means of cyclic communication between head and field PLCs Bundle process values Archive process values in CSV files Requirements for the automation task The following requirements are imposed on the automation solution: Optimal and performant utilization of the available connection resources of the head or field PLC. Easy adaptation to variable quantity structures (process values and number of field PLCs). Applicable to IPCs with WinAC as head PLC and S71200/1500 as field PLCs. Process data archiving in a cycle of 1 second minimum. Process value archiving in CSV files. Entry ID: , V1.0, 03/2014 4

5 2 Solution 2.1 Overview 2 Solution 2.1 Overview Schematic overview Figure 21 The figure below gives a schematic overview of the most important components of the solution: Head PLC IPC427D + WinAC RTX WinAC ODK Shared Memory Extention (SMX) Storage of process values in CSV files Field PLC S71500 Field PLC S71200 Setup This application example demonstrates the use of a communication block and data archiving using WinAC ODK. A SIMATIC IPC with WinAC RTX is used as head PLC. A CPU S71500 and two CPU S71200 are used as field PLCs. Data archiving is realized via the shared memory extension (SMX) interface of WinAC ODK. A C# program reads the process values from the shared memory and archives them in CSV files. Entry ID: , V1.0, 03/2014 5

6 2 Solution 2.1 Overview Description The foundation stone of this application is a communication block for data synchronization between several field PLCs and one head PLC. For the complete description of the communication block, please refer to the following entry: This application example only describes the archiving of the collected process values. For the complete description of the communication between head and field PLCs, please refer to the abovenamed entry. The task of the "Archive_Data" function block in the head PLC is to automatically bundle the process values of the field PLCs and provide them to the Windows operating system via the SMX interface. A C# program reads the process values from the shared memory and stores them in CSV files. The process values are written to the shared memory by the STEP 7 program once per second. The C# program autonomously recognizes when new process values are written to the shared memory by the STEP 7 program. In this case, the process values are archived line by line in CSV files. The C# program provides a graphical user interface. Here, archiving can be started and monitored. Figure 22: C# program, graphical user interface Advantages The solution presented here offers you the following advantages: Quick and easy setup of a communication solution Flexible expandability of the field PLCs Consistent archiving of process data Easy archiving operability due to supplied wizard user interface Delimitation This application does not include information on basic STEP 7 programming basic information on Industrial Ethernet and CPUCPU communication Basic knowledge of these topics is therefore assumed. Entry ID: , V1.0, 03/2014 6

7 2 Solution 2.2 Hardware and software components 2.2 Hardware and software components Components used The application was set up with the following components: Hardware components Table 21 Component No. Article number Note IPC 427D 1 6AG4140xxxxxxxx Head PLC CPU 15163PN/DP 1 6ES7 5163AN000AB0 Field PLC 1 CPU 1214C DC/DC/DC 1 6ES7 2141AE300XB0 Field PLC 2 CPU 1212C DC/DC/DC 1 6ES7 2121AD310XB0 Field PLC 3 SCALANCE X GK52080BA102AA3 SIMATIC FIELD PG 1 6ES For loading the head and field PLCs Software components Table 22 Component No. Article number Note STEP 7 Professional V12 SP1 UP3 1 6ES78220A WinAC ODK ES78061CC030BA0 Microsoft Visual Studio WinAC RTX 2010 SP1 1 6ES76710RC080YA Sample files and projects The following list contains all files and projects used in this example. Table 23 Component _CODE_TIA_v10.zip _CODE_visual_studio_v10.zip Note contains the STEP 7 project contains the Visual Studio project Entry ID: , V1.0, 03/2014 7

8 3 Functionality of the Application 3.1 General overview 3 Functionality of the Application 3.1 General overview The figure below shows the functionality of the STEP 7 and C# program. Figure 31 STEP 7 program C# program Start/Stop Archive_Data Start/Stop C_Prog_ready FALSE New Data counter incremented No TRUE Yes Communication with field PLCs Set Error_Bit Reset CProg_ready Write data to shared memory Increment New_Data counter Increment Error_Counter counter Read new data from shared memory Write data to CSV file *Called every second (OB 35) Set C_Prog_ready * Default setting in this application 100ms* cycle time STEP 7 program The "Archive_Data" block is called every second by means of a time interrupt. With the help of the "C_Prog_ready" tag, the status of the C# program is checked. When the C# program is ready for new data, communication with the field PLCs is started. Then, the data are written to the shared memory and the counter "New_Data" is incremented. This is necessary in order that the C# program recognizes whether new data are available. If the "C_Prog_ready" tag is set to "False" when the "Archive_Data" block is called, error handling is started (see chapter "Archive_Data" function block). Entry ID: , V1.0, 03/2014 8

9 3 Functionality of the Application 3.1 General overview C# program The C# program checks whether the "New_Data" counter has been incremented. If this is not the case, it awaits the next scanning cycle. If new data are available, these are processed. The "C_Prog_ready" tag is set to "False". This is necessary to signal to the STEP 7 program that the C# program is just processing data. (Handshake) Afterwards, the data are read from the shared memory and written to CSV files. Then, the "C_Prog_ready" tag is set to "True". This indicates that the C# program is ready for new data. Data exchange via shared memory Figure 32 STEP 7 program WinAC ODK Shared Memory Extention C# program write Output Area (4kByte) Counter_New_Data Processdata read Note read Input Area (4kByte) C_Prog_ready For data exchange between the STEP 7 program and the C# program, the shared memory interface of WinAC ODK is used. 4 kbytes of data are available each for input and output. write For further information on WinAC ODK, please refer to: Archiving in CSV files The C# program reads the data from the shared memory and archives them in CSV files. These CSV files constitute a cyclic buffer. This buffer consists of several CSV files which are changed as soon as a file contains 65,000 lines. When the maximum capacity of the last file has been reached, the first one is overwritten again. The names of the CSV files are expanded by the extension "_X", where X stands for the number of the current file to be written. Entry ID: , V1.0, 03/2014 9

10 3 Functionality of the Application 3.2 The blocks of the STEP 7 program 3.2 The blocks of the STEP 7 program Figure 33 The figure below shows the interaction of the existing application (see entry ID ) and the application described herein: DATASYNC_HEAD idb idb idb DATASYNC_HEAD DATASYNC_HEAD TCON TRCV TSEND TSEND TDISCON OB 1 IP_ADDRESS DB_MANAGE DB_STATE OB 35 (1 sec.) DB_RCV_DATA Read process values Archive_Data DB_SND_DATA Data synchronization application (entry ID ) SysDateTimeToInt Global_Data This application "Archive_Data" function block Task Query whether the C# program is ready for data archiving Start communication between head and field PLCs Read data from "DB_RCV_Data" data block Save data to shared memory Entry ID: , V1.0, 03/

11 3 Functionality of the Application 3.2 The blocks of the STEP 7 program Reaction to error In the event of an error, the following operations are executed during operation: Set "Error_Bit" tag Increment "Error_Counter" counter The following error might occur: Error acknowledgement C program has not finished data readout If a positive edge is pending at the "Reset_Error" input, "Error_Bit" is set to "False" and "Error_Counter" is reset to "0". Interfaces The formal parameters of the function block have the following meaning: Figure 34 "Archive_Data" function block Table 31 Formal parameter Type Data type Meaning Reset_Error Input Bool Acknowledges the error "Error_Bit" is reset "Error_Counter" is set to 0 Error_Bit Bool Is set in the event of an error Error_Counter Output INT Counts the number of errors during operation Entry ID: , V1.0, 03/

12 3 Functionality of the Application 3.2 The blocks of the STEP 7 program "SysDateTimeToInt" function block Task In order that date and system time can be written to the shared memory, the data type must first be converted from "Date_And_Time" into "INT". This is executed by the "SysDateTimeToInt" function block. Query of date and system time Splitup of date and system time into "INT" values Return of the "INT" values Interfaces Table 32 Formal parameter Type Data type Meaning Year_YYYY INT Current year (four digits) Year_YY INT Current year (two digits) Month INT Current month Day Output INT Current day Hour INT Current hour Minute INT Current minute Second INT Current second "Global_Data" data block Task Table 33 The "Global_Data" data block serves for data management of the process values required for archiving. It contains the following tags: Tag Data type Meaning Reset_Error BOOL Acknowledges the error "Error_Bit" is reset "Error_Counter" is set to 0 Error_Bit BOOL Is set in the event of an error Error_Counter INT Counts the number of errors during operation Increment INT Counter that is incremented in the case of new process values Cur_Date_Time STRUCT Contains the date and time as INT values Entry ID: , V1.0, 03/

13 4 Installation 4.1 Installation of the hardware 4 Installation 4.1 Installation of the hardware The figure below shows the hardware configuration and the IP addresses used in this application. Figure 41 IPC427D SIMATIC Field PG CPU 1214C SCALANCE X208 CPU 1212C CPU 1516C Connect a head PLC (here: IPC427D), the field PLCs (here: S71200/1500), and the SCALANCE X208 each to a 24 V power supply. Connect all devices with the SCALANCE X208 by means of a standard Ethernet cable. Note The installation guidelines for these components must always be observed. Entry ID: , V1.0, 03/

14 4 Installation 4.2 Installation of the software 4.2 Installation of the software Installation of the basic software: Install the following software on the programming device: Table Install STEP 7 V12 Professional SP1 Update 2 2. Install WinAC ODK V4.2 SP1 Manual: Manual: Install Microsoft Visual Studio 2010 Table 42 Install the following software on the execution system (here: IPC427D). 1. Install WinAC RTX 2010 Update 3 on a PC system Application software Table 43 Unzip the following files on your PG/PC. Manual: Update: 1. Unzip the files "WinAC_Data_Concentrator.zip" and "Visual_Studio_WinAC_Data_Concentrator.zip". Entry ID: , V1.0, 03/

15 5 Startup of the SIMATIC Components 5.1 IP addresses used 5 Startup of the SIMATIC Components 5.1 IP addresses used Table 51 The following IP addresses are used in this application: IP address Component Field PLC Field PLC Field PLC Head PLC IPC SIMATIC Field PG The subnet mask is always Changing the IP addresses of the PLCs Table 52 The SIMATIC components are addressed in the TIA portal by means of the online function "Assign IP address". 1. Start the TIA portal and open the project "WinAC_Data_Concentrator". 2. Open the project view of the TIA portal. 3. Doubleclick "Online & diagnostics" under "HEAD WinAC RTX Software PLC". 4. Select "Assign IP address" under "Functions". Click the "Accessible devices" button. Entry ID: , V1.0, 03/

16 5 Startup of the SIMATIC Components 5.2 Loading the PLCs 5. Select the SIMATIC Field PG interface. The search for accessible devices is carried out automatically. The result is shown in a list. Identify the PLC you use as "HEAD" PLC via the MAC address and click "Apply". 6. Assign the IP address stored in the project to this device with "Assign IP address". The "HEAD" PLC now owns the IP address stored in the project. 7. Change the IP addresses of the field PLCs in the same way. 5.2 Loading the PLCs In the following, the PLCs are loaded with the hardware configuration and user program. Note For further information, please refer to the entry "How is a project downloaded in the CPU in STEP 7 (TIA portal)?" Entry ID: , V1.0, 03/

17 5 Startup of the SIMATIC Components 5.2 Loading the PLCs Table Select the first field PLC. Then load the device configuration and program to the field PLC with the respective symbol in the toolbar. 2. The project is compiled. Click the "Load" button. 3. Activate "Start all" to start the module. Exit the loading operation with "Finish". 4. Proceed in the same way for the two other field PLCs and the head PLC. Entry ID: , V1.0, 03/

18 6 Operation of the Application 5.2 Loading the PLCs 6 Operation of the Application In order to archive the data arising during communication between the head and field PLCs, they must be read out of the shared memory of the WinAC with the C# program ("WinAC_Data_Concentrator.exe"). Description of the wizard page Figure Table 61 No. Remarks 1 Opens a dialog box for connection with the WinAC RTX 2 Input field for defining the file names 3 Shows the currently selected storage path 4 Opens a dialog box for defining the storage path for the files 5 Starts data archiving 6 Stops data archiving 7 Shows the name of the file that is currently written 8 Shows the data records that are currently written Entry ID: , V1.0, 03/

19 6 Operation of the Application 6.1 Creating an executable file from the C# program 6.1 Creating an executable file from the C# program Table Open the supplied Visual Studio 2010 project: "WinAC_Data_Concentrator.sln". 2. Select "Release" under "Solution Configuration". 3. Click "Build Build Solution" in the menu list. The executable file is created and saved to the project folder. 4. Navigate to the project folder of the Visual Studio project. Open the "bin" folder with a doubleclick and in there the "Release" folder. 5. Copy the file to the target system using WinAC RTX (here: IPC427D). 6. Start the "WinAC_Data_Concentrator.exe" on the target system (here: IPC427D). Entry ID: , V1.0, 03/

20 6 Operation of the Application 6.2 Starting archiving 6.2 Starting archiving Establishing a connection with the shared memory of the WinAC Table Click "SMX Open" in the menu list. A dialog box opens. 2. Enter the name of the WinAC. In this application, the name is "WinAC RTX Software PLC". Confirm with "OK". Note: You can find the name of the PLC in the project tree under "HEAD". 3. In the case of an invalid entry, an error message is output. Entry ID: , V1.0, 03/

21 6 Operation of the Application 6.2 Starting archiving Defining the archive file name and starting Table Enter the desired file name for your archive in the "File Name" field on the user interface. The file extension ".csv" is then attached automatically. 2. Select the storage path to which the archive files are to be saved. Click the "..." button for that and select the folder. Confirm with the "OK" button. The default path is "C:\Temp". 3. Start archiving with the "Start Data logging" button. Entry ID: , V1.0, 03/

22 6 Operation of the Application 6.3 Stopping archiving 4. If the start was successful, the name of the currently written file is displayed at "Cur. File" and the current data at "Cur Data". 5. In the case of invalid entries, an error message box opens. 6.3 Stopping archiving Table While data archiving is running, the "Stop Data logging" button is enabled. You can stop archiving by clicking this button. 2. Click "SMX Close" in the menu bar to cut the connection with the shared memory of the WinAC. Entry ID: , V1.0, 03/

23 6 Operation of the Application 6.3 Stopping archiving 3. Click "File Exit" in the menu bar to completely end the program. Entry ID: , V1.0, 03/

24 7 Adding More Field PLCs 7.1 Changes in the new field PLC 7 Adding More Field PLCs To expand the application, you can create up to 32 field PLCs in the project. How to add a new PLC is described here by taking the example of a CPU 1215C. 7.1 Changes in the new field PLC Perform the following steps to add a new SIMATIC S7 1200/1500 CPU: Table Click "Add new device". 2. Select the desired CPU and confirm with "OK" The CPU is added. 3. Assign a unique IP address as described in chapter 5.1 IP addresses used. For example, Entry ID: , V1.0, 03/

25 7 Adding More Field PLCs 7.1 Changes in the new field PLC 4. Change to a different field PLC. Copy the files in the "Program blocks" folder with a rightclick and "Copy". 5. Return to the new CPU. Select the "Program blocks" folder with a rightclick and then click "Paste". Entry ID: , V1.0, 03/

26 7 Adding More Field PLCs 7.2 Changes in the head PLC 6. If the "Program blocks" folder already contains files, a prompt appears, asking whether these are to be overwritten. Confirm with "OK". 7. Execute steps 4 and 5 for the "PLC Data Types" folder. Note When changing the receive and send structures, make sure that the send structure of the head PLC corresponds exactly to the receive structure of the field PLC. 7.2 Changes in the head PLC The following supplements are required in the head PLC (here: IPC 427D) to include the new CPU in the communication: "DB_IPADDRESS" data block Table Open the "DB_IPADDRESS" data block under "Program blocks". 2. Copy the structure "IP_Address_01". Entry ID: , V1.0, 03/

27 7 Adding More Field PLCs 7.2 Changes in the head PLC 3. Paste the structure in the bottom list. Assign the name "IP_Address_04". 4. Open the structure and enter the IP address of the new CPU. "DB_MANAGE" data block Table Open the "DB_MANAGE" data block under "Program blocks". 2. Enter the number of field PLCs at "Nr_of_Substations". In this example, it is 4 field PLCs. 3. Select the "REQ_3" tag and rightclick. Select "Add row". Entry ID: , V1.0, 03/

28 7 Adding More Field PLCs 7.2 Changes in the head PLC 4. Create the new "REQ_4" tag. Data blocks "DB_SEND_DATA" and "DB_RCV_DATA" Table Open the "DB_SEND_DATA" data block under "Program blocks". 2. Copy the structure "Receive_Structure_01". 3. Paste the structure at the bottom and assign the name "ReceiveStructure_04". 4. Open the "DB_RCV_DATA" data block and execute steps "DB_STATE" data block Table Open the "DB_STATE" data block under "Program blocks". 2. Copy the "Sub_01" tag. Entry ID: , V1.0, 03/

29 7 Adding More Field PLCs 7.2 Changes in the head PLC 3. Paste the tag at the bottom of the table and assign the name "Sub_04". "Do_Communication" function block Table Open the "Do_Communication" function block with a doubleclick. 2. Select network 3 with a rightclick. Select "Insert network". A new network is inserted. 3. Drag and drop the "DATASYNC_HEAD" function block to the new network. The "Call options" window opens in which you have a new data block created. Assign the name "IDB_04_DATASYNC" and confirm with the "OK" button. Entry ID: , V1.0, 03/

30 7 Adding More Field PLCs 7.2 Changes in the head PLC 4. Interconnect the block as shown in the following figure. For further information about block interconnection, please refer to the following application documentation: mens.com/ww/view/en/ Copy the network "start impulse for partner 3" and paste it at the bottom of the block. 6. Change parameter "IN1" to "IDB_04_DATASYNC.Step" and the output parameter to "DB_MANAGE.REQ_4". "Archive_Data" function block Table Open the "Archive_Data" function block under "Program blocks". 2. Place the cursor in the line with the comment "Start impulse for Communication". Entry ID: , V1.0, 03/

31 7 Adding More Field PLCs 7.3 Changing the shared memory access 3. Set the "REQ_4" tag in the "DB_MANAGE" data block to Load the project to the new field PLC and to the head PLC as described in chapter 5.2 Loading the PLCs. After having executed this step, communication to the new CPU is established. The communication data are stored cyclically every second in the "DB_RECV_DATA" data block. 7.3 Changing the shared memory access In order to archive the process data of the newly added CPU, these data must also be written to the shared memory. The commands for that must be added in the STEP 7 program in the head PLC and in the C# program Addresses used Table 78 In the shared memory, the following addresses have been assigned so far: STEP 7 program C# program Usage From From 0 Data exchange station 1 From From 616 Data exchange station 2 From From 1616 Data exchange station 3 From From 3616 Data exchange date and time New_Data C_Prog_ready Note The addresses for "New_Data" and "C_Prig_ready" are located at the end of the shared memory area. When adding new PLCs, make sure that these two bytes are not changed. In this example, the shared memory addresses from (and 2626 respectively) are used for the new PLC. Entry ID: , V1.0, 03/

32 7 Adding More Field PLCs 7.3 Changing the shared memory access Changes in the STEP 7 program In order to archive the process data of the newly added PLC, you must expand the code in the "Archive_Data" function block as follows: Table Open the "Archive_Data" function block under "Program blocks". 2. Place the cursor in the line with the comment "Write Info from Communicationpartner 2". 3. Copy the lines that execute the shared memory access of station 2 (comment: "End Communication Partner 2"). 4. Place the cursor in the line with the comment "End Communication Partner 3". 5. Paste the text. 6. Adjust the commands to the new PLC. See screenshot in chapter Screenshot of STEP 7 program expansion Start address for station 4 = The process data source is "DB_RCV_DATA". ReceiveStructure04. Entry ID: , V1.0, 03/

33 7 Adding More Field PLCs 7.3 Changing the shared memory access Changes in the C# program Table 710 In order to read and archive the process data of the newly added PLCs from the shared memory, you must make the following changes in the C# program: 1. Open the "MainWindow.cs" file in the Visual Studio project. 2. Go to the "#region Variable Definition" area. 3. Add the following new tags. 4. Place the cursor in the "void read_smx( )" function. 5. Copy the commands between "#region SMX READER Partner 2" and "#endregion Partner 2". 6. Place the cursor below the command "#region SMX READER Partner 3". 7. Paste the text. 8. Adjust the commands to the address range of the new PLC ( ). See screenshot in chapter Screenshot of C# program expansion Save the return values of the SMX functions to the tags created in step Place the cursor in the line with the comment "Write Information in CSV Output Stream". 10. Copy the "csv_writer_writeline( )" line of station 3. Entry ID: , V1.0, 03/

34 7 Adding More Field PLCs 7.3 Changing the shared memory access 11. Paste the line directly below and change the tag names to the ones created in step Place the cursor in the line with the comment "Information for Wizard Page". Expand the output by the tags created in step Then create a new executable file as described in 6.1 Creating an executable file from the C# program. Entry ID: , V1.0, 03/

35 7 Adding More Field PLCs 7.3 Changing the shared memory access Screenshot of STEP 7 program expansion The following figure shows the complete code required for a newly added PLC in the STEP 7 program: Figure 71 Entry ID: , V1.0, 03/

36 7 Adding More Field PLCs 7.3 Changing the shared memory access Screenshot of C# program expansion The following figure shows the complete code required for a newly added PLC in the C# program: Figure 72 Entry ID: , V1.0, 03/

37 8 References 8 References Table 81 Subject \1\ Siemens Industry Online Support \2\ Download page of the entry \3\ Application entry page Data synchronization Title \4\ WinAC ODK manual History Table 91 Version Date Modifications V1.0 03/2014 First version Entry ID: , V1.0, 03/