Professional Documents
Culture Documents
Industry Automation and Drive Technologies Service & Support Portal This article is taken from the Service Portal of Siemens AG, Industry Automation and Drive Technologies. The following link takes you directly to the download page of this document: http://support.automation.siemens.com/WW/view/en/61627479
Copyright
Task Solution Creating and Adapting the PCS 7 Project Configuring with AdvES
1 2 3 4 5 6 7
SIMATIC PCS 7 Performance Mass Data Engineering with PCS 7 AdvES on a Practical Example
Siemens AG 2013 All rights reserved
Application Description
Copyright
Copyright
Preface
Preface
Objective of this application This application describes the functionality of a PCS 7 Advanced Engineering System V8.0 (AdvES) based on a practical example. Furthermore, the advantages of AdvES in comparison to the import/export wizard are explained. Main topics of this application The following core points are discussed in this application: Describing AdvES and its advantages Configuring an example project using AdvES
Validity Valid from SIMATIC PCS 7 V8.0 SP1 (incl. option package PCS 7 Advanced Engineering System V8.0 SP1)
Copyright
Table of Contents
Table of Contents
Warranty and Liability .............................................................................................. 4 Preface ...................................................................................................................... 5 Table of Contents ..................................................................................................... 6 1 2 Task................................................................................................................. 7 Solution........................................................................................................... 8 2.1 2.2 2.3 2.4 3 3.1 3.2 3.3 3.4 3.5 3.6
Siemens AG 2013 All rights reserved
PCS 7 Advanced Engineering System ............................................... 8 AdvES advantages .......................................................................... 10 AdvES Principle of Operation........................................................... 12 Required engineering components................................................... 15 Required prerequisites of the PCS 7 project..................................... 17 Creating a project ............................................................................ 18 Deriving a CMT from Advanced Process Library (APL) .................... 23 Changes in the CMT and the technological connections................... 26 Configuring optional blocks of the "ValveAnalog" CMT ..................... 30 Configuring messages ..................................................................... 31 Data import from PCS 7 to AdvES ................................................... 33 Assigning mapping labels for the technological I/Os of a CMT.......... 39 Assigning the mapping labels .......................................................... 42 Creating variants and copy templates in AdvES ............................... 46 Creating individual mapping labels ................................................... 49 Transferring mapping labels............................................................. 53 Data import of external data ............................................................. 55 Creating the configurator for importing ............................................. 58 Importing Data ................................................................................. 71 Specifying control modules .............................................................. 75 Configuring connections .................................................................. 80 Determine connections at the CMTs ................................................ 80 Execute interconnections for the CM instances ................................ 82 Assigning hardware ......................................................................... 84 Consistency check ........................................................................... 91 Exporting data to PCS 7 .................................................................. 94 Other useful functions in AdvES..................................................... 103 Report folder.................................................................................. 103 Control module (CM) test sheets.................................................... 105 Procedure ...................................................................................... 105 Table views ................................................................................... 107 Project properties .......................................................................... 110
Configuring with AdvES ............................................................................... 33 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.3 4.3.1 4.3.2 4.4 4.5 4.5.1 4.5.2 4.6 4.7 4.8 4.9 4.9.1 4.9.2 4.9.3 4.9.4
Copyright
5 6 7
1 Task
Task
Different planning and engineering tools will be used for planning and realizing a process control system. Most of the time the software data cannot be easily used in another software, since they use different data formats. Handling these different data formats is time consuming and resource intensive.
Introduction
Copyright
Description of the automation task The following requirements must be met in order to improve the current process of engineering and save costs and resources: One-time entry and reuse of data. Support of data exchange between different tools. System support in case of modifications. Detection and documentation of data changes at the interfaces.
2 Solution
2
2.1
Solution
PCS 7 Advanced Engineering System
SIMATIC PCS 7 Advanced Engineering System (AdvES) expands the functionality of the system configuration. It serves as a link between standard engineering tools from the SIMATIC PCS 7 Engineering Toolset (CFC, HW config, technological hierarchy (Plant Hierarchy)) and basic and detail planning tools, e.g. EPlan, ELCAD, or SmartPlant.
Properties AdvES is a SIMATIC PCS 7 optional package. AdvES prepares data for use in the PCS 7 ES. AdvES is an application for importing data. Data can be imported into AdvES from process tag and signal lists and can be transferred to PCS 7 ES. After a first assignment, AdvES will detect the control module types (CMTs) and automatically generate the control modules (CMs). In this context, technological hierarchy, signal, and parameter settings can automatically be taken over from the process tag and signal lists. Hardware (decentralized periphery including channel assignment) can be generated from the signal lists. Object-dependent mass data processing and queries are possible.
Figure 2-1: Engineering with AdvES
Copyright
Note
2 Solution
Range of functions of AdvES Generating CMs from process tag and signal lists Creating hardware configurations from signal lists (including symbol table) Using CMs from PCS 7 (e.g. Basic Control Module - library and customerspecific libraries) Defining variants through optional blocks Mass data processing of control modules, signals, parameters, and messages Checking data consistency and plausibility Generating the PCS 7 automation data Using messages to control modules
Figure 2-2: Overview of AdvES functionality
Copyright
2 Solution
2.2
AdvES advantages
Reduction of configuration and start-up times Easier qualification through standardized interfaces Less coordination efforts with the systems planner Technological engineering in Advanced ES without PCS 7 system knowledge Changes to process tags can be exchanged bidirectionally
General information
Increase in quality Fault prevention through standardized interfaces Verifiability of plausibility and data consistency Secured return of automation changes to systems planning Change management for supplied planning data
Saving the expenditures for creating and maintaining separate tools and solutions
Advantages of AdvES over the import/export wizard The following table shows the advantages of AdvES over the import/export wizard:
Table 2-1: Comparison of AdvES and import/export wizard Import/export wizard PCS 7 Advanced Engineering System
Copyright
10
2 Solution
Import/export wizard
Copyright
11
2 Solution
2.3
General overview
Note
Note
Copyright
Note
The AdvES database is not identical with the PCS 7 database. It will not be archived together with the PCS 7 multi-project. The AdvES database must be secured separately. This procedure is described in detail in chapter 2.5 of the Process Control System PCS 7 Advanced Engineering System manual.
12
2 Solution
Every AdvES project includes many objects of these types; each of these must adhere to a certain structure: TH folders can be found underneath the object node or underneath other TH folders. CMs are inside TH folders. CM parameters are placed underneath CMs. Signal parameters are placed underneath signals. Signals are placed underneath CMs.
Copyright
13
2 Solution
Overview of the AdvES workflow The figure below shows the AdvES principle of operation:
Copyright
14
2 Solution
2.4
6ES7658-1GX08-2YA5
Updating the SIMATIC PCS 7 V8.0 Advanced Engineering System software or V8.0 update 1 to V8.0 SP1:
Copyright
Sample files and projects The following list contains all files that are used in this example.
Table 2-3: Supplied project files Component DEMO_AdvES.zip Note This zipped file includes a PCS 7 library with 4 CMTs and one Excel signal list This document.
61627479_Application_AdvES_en.pdf
Note
The types used in the examples must be checked for use outside of this application.
15
2 Solution
Example project The ZIP file includes a library with 4 CMTs from the basic control module library and a signal list for the example project. The signal list includes information for 170 CMs, TH, hardware, signals and parameters. The following steps must be taken to import, generate, and export this data to PCS 7 through AdvES:
Table 2-4: Configuration steps in AdvES Chapter 3 4.1 4.2 4.3 4.4 4.5
Siemens AG 2013 All rights reserved
Action Creating and Adapting the PCS 7 Project Data import from PCS 7 to AdvES Assigning mapping labels for the technological I/Os of a CMT Data import of external data Specifying control modules Configuring connections Assigning hardware Consistency check Exporting data to PCS 7 Other useful functions in AdvES
Copyright
16
3
3.1
Copyright
17
3.2
Procedure
Creating a project
1. Open the SIMATIC Manager. 2. Create a new multi-project with a sub-project using the 'New project' Wizard. File > New Project Wizard...
Figure 3-2: Creating a multi-project
The PCS 7 Wizard: New Project opens. 3. Click on the Next button.
Figure 3-3: PCS 7 Wizard: New Project dialog
Copyright
18
4. Select a "AS 417-4" CPU with a matching bundle. 5. Select "0" for the "number of communication modules" of the CP-443-5 in the drop-down menu. 6. Click on the Next button.
Figure 3-4: PCS 7 Wizard: New Project dialog
7. Select 1 for the number of levels for the technological hierarchy. OS objects for PCS 7 OS, SIMATIC BATCH, route control and open PCS 7 are not required.
Figure 3-5: PCS 7 Wizard: New Project dialog
Copyright
8. Click on the Next button. Assign a suitable name for the project, e.g. AdvES_example. 9. Then click on the Finish button. A new PCS 7 multi-project is generated.
19
10. When you have created the project, change the name of the AS to AS1 and the Process cell(1) technical hierarchy folder to Process cell.
Siemens AG 2013 All rights reserved
11. Delete the plans SFC(1) and CFC(1) in the Process cell technological hierarchy folder.
Figure 3-7: Deleting the plans
Copyright
12. Open NetPro in the toolbar of the SIMATIC Manager and delete the MPI bus there.
Figure 3-8: "NetPro
20
14. Drag the included CMTs ("AMON_Std", "CTRL_Std", "MOT_1sp_2fb_1cm" and "MOT_2sp") into the master data library of your project.
Figure 3-10: Accepting the control module types
Copyright
Note
As of V8.0, PCS7 provides you with a new type concept which, together with PCS 7 Advanced Engineering (AdvES), allows for improved mass data engineering as well as for changes to control module types already instantiated. For details on the new type concept, please refer to chapter Handling of control module types in the SIMATIC Process Control System PCS 7 CFC for SIMATIC S7 (V8.0) function manual.
21
The default functions are automatically created when you are dragging the CMTs into the project.
Copyright
22
3.3
Procedure
2. Select the ValveAnalog process tag type, open the context menu and click Process Tag > Create/Change Process Tag Type...: The Create/Change Process Tag Type... dialog box opens. 3. Click on the Next button.
Figure 3-13: Adapting the "ValveAnalog" type
Copyright
23
6. Delete any external interconnections in the chart of the type. 7. Select the Process tag types folder in the master data library of your multiproject and open the context menu. 8. In the context menu, select Control Modules > Create control module type from process tag type.... A selection dialog box opens.
Figure 3-15: Converting process tag types into CMTs
Copyright
24
Figure 3-16: Selection dialog for converting process tag types into CMTs.
The CMT will now be created in the master data library. 9. Delete the "ValveAnalog" process tag type and assign the name "ValveAnalog" to the "ValveAnalog(1)" CMT.
Siemens AG 2013 All rights reserved
Copyright
25
3.4
Procedure
4. If this is not the case, right-click into the field of the Assignment column and the Name row. The "Plan ValveAnalog" button will open. Click on the button and you will have assigned a plan to the name.
Figure 3-19: Assigning the control module name
Copyright
NOTICE
If this assignment does not exist, the chart names of the instances will not be created correctly in the process of creation.
26
5. Select the "ValveAnalog" object and open the object by right clicking the context menu of the object. 6. Click on the Insert new object > Control module entry. A new object named Control unit is created. In the next step, instantiate the object with the FbkOpen input driver block.
Figure 3-20: Technological connections
7. Select the Control module object. The attributes of the object are opened. 8. Drag the "FbkOpen" block into the field of the "assignment" column and the "assigned block" row via drag & drop. 9. Assign the name FbkOpen for this object.
Figure 3-21: Instantiating the "FbkOpen" object
Copyright
27
10. Select the PV_In input of the FbkOpen block and drag it onto the FbkOpen object. A Signal type control tag is automatically created. 11. Adjust the name of the control tag.
Figure 3-22: Defining CMT connecting points
Note
You can also create objects via drag & drop. For this purpose you have to select the respective block and drag it via drag & drop to the respective object.
Copyright
28
12. Please perform these steps also for the following blocks.
Table 3-1: Blocks that must be instantiated Block FbkClose Output ValveAnalog PV_In (Signal) PV_Out (Signal) MV_Ext (Parameter) Input/Output
Note
If the Select Structure Element dialog opens up during the assignment of a parameter, you have the following options:
1. 2. Select a complete structure Select an individual structure member if you do not use the complete structure
1.
2.
Copyright
29
3.5
Procedure 1. Enable the Optional attribute in the attributes of the FbkOpen and FbkClose blocks. Chapter 4.2.1 of the application example shows you how you can form different variants of the ValveLean type in this way.
Figure 3-24: "Optional" block attribute
Copyright
Note
The optional blocks, for example, can be disabled in an instance of the type and can be enabled in another instance. The huge advantage is that you no longer require many different process tag types, for a valve for example. A universal control module type which contains and can reproduce all variants of a valve is sufficient.
30
3.6
Configuring messages
The block at which you wish to configure the messages must support the messaging function.
Requirements
Procedure 1. Open the Technological connections of the ValveAnalog control module type. 2. Right click on the ValveAnalog object. A context menu opens. 3. Click on Insert new object > Message.
Figure 3-25: Creating the message object
Copyright
4. Select the ValveAnalog block and using drag & drop, move it into the field for assigning the message (Column: Assignment row: Assigned message) and select the SIG1 message identifier (possible message identifiers: SIG1 ...SIG8).
Figure 3-26: Configuring messages
31
Note
"MsgEvID2" messages cannot be configured in this way. For blocks containing more than one Alarm_8P, hence also an MsgEvID2, you need to proceed as follows:
1. 2. Switch the connections "MsgEvID1" and "MsgEvID2" visible. Select the MsgEvID2 connection and use drag & drop to move it onto the object of the appropriate block. A message with the assignment to the message-capable block is automatically generated. Select the desired message identifier.
3.
Copyright
32
4.1
Copyright
Procedure 1. Select your sub-project and right click to open the context menu. 2. Click on "Open project in AdvancedES" to open AdvES.
Figure 4-2: Opening AdvES
33
Note
The "Open project in AdvancedES" item will only be shown with correct installation and can only be selected with a valid license. Standard templates will be transferred when an AdvES project is opened for the first time, the opening process will therefore take a little longer. The progress of copying will be displayed.
AdvES will open with an empty project, i.e. no data will be available in the three tabs of the navigation area, only the name of the project.
Figure 4-3: AdvES dialog
Copyright
34
4. Select the "Import from PCS 7" tab. 5. Enable all selectable filter options. For the first import of PCS 7 data or after hardware changes (or changes to the control module types) it is mandatory to enable the filters for control module types and the hardware. 6. Click on the "Import" button to start importing.
Figure 4-5: Filter selection dialog for data import
Note
After that, AdvES will automatically check for differences between the PCS 7 project and the AdvES project. The result of the comparison will be displayed in the "Data transfer - Generate/import" window. 7. Click on the button to start the import to AdvES.
Copyright
35
Note
The found.
button will only be enabled if differences between the two projects are
Note
Enable the "delete at target" function if you wish to delete obsolete data in the AdvES project. Only the changes will be imported. Example You have already imported control module types and a hardware configuration into the AdvES project. Then you delete a control module type in the master data library and change the name of the PROFIBUS master system in the hardware config. With the Delete at target function, the new name of the PROFIBUS master system will be adopted when importing, and the old control module type will be removed from the AdvES project. Without the delete at target function, an additional PROFIBUS master system is created and the data of the already existing PROFIBUS master system remains in COMOS.
Note
8. After the import, you will be shown a log for the import process, acknowledge the dialog with OK.
Figure 4-7: Dialog box for the import process
Copyright
9. The Data transfer dialog box opens. Here you have the option of comparing the AdvES project with the PCS 7 project. 10. Click on the "Yes" button to start the data synchronization. After synchronization, check whether all data were correctly transferred to AdvES.
36
11. Click on the Close button to close the import dialog box. Subsequently, the data is adopted in AdvES and displayed in the automation view. You will see a generation log with errors, warnings and messages.
Figure 4-10: Generation log after data import
Copyright
37
12. Click on the button to confirm the "PCS 7 Import" menu item. This enables the next menu item "Assign signals/parameters".
Figure 4-11: Confirming the "PCS 7 Import" step
Copyright
38
4.2
Note
The mapping labels for 2 areas are assigned on a separate basis in AdvES. On one hand for the data from PCS 7 and on the other hand for the external data from the Excel lists. The identifiers are a link between PCS 7 and AdvES as well as between AdvES and Excel tables. They enable the file import and fulfill the function of maintaining the structure during import, i.e. the assignment of signals and parameters to the CMTs.
Figure 4-12: Project step in the overall workflow
Copyright
39
Example Looking for example at the ValveAnalog CMT from the example project. The CMT has an input signal for the feedback open and closed and an analog output signal for the current position of the valve (see Figure 4-13). The signal name is made up of the block name and the input name in the control module type.
Figure 4-13: Technological connections of the "ValveAnalog" CMT
Copyright
The same information for the signals of a valve is also included in the signal list of the example project (see Figure 4-14).
Figure 4-14: Excerpt of a signal list
In AdvES, the labels "FBO", "FBC", and "OUTOC" are assigned as mapping labels for the signals from the control module type and from the Excel list. This way AdvES can link the information from the "ValveAnalog" CMT with the information from the Excel list (see Figure 4-15).
40
You will find a detailed description of how to assign the mapping labels in chapters 4.2.1, 4.2.3 and 4.3.1.
Siemens AG 2013 All rights reserved
Note
The mapping labels only have to be assigned once. If the same master data library is used in a different AdvES project, which means the mapping labels have already been assigned, the mapping labels can be imported from that project (see chapter 4.2.3).
Copyright
41
4.2.1
Introduction In this section you will learn how to assign mapping labels to the technological connections (signals and parameters) of the CMTs imported into AdvES (see Figure 4-16).
Figure 4-16: Assigning signals and parameters
Copyright
In the AdvES work area all CMTs in the project are displayed with the corresponding status for assignment. In this example the "AMON_Std", "CTRL_Std", "MOT_1sp_2fb_1cm", "MOT_2sp", and "ValveAnalog" CMTs are displayed. Possible statuses:
Red no mapping label assigned yet Yellow mapping labels incomplete Green mapping labels complete
Note
42
2. Click a CMT, e.g. AMON_Std. You will receive a list of all technological connections (signals and parameters) of the type. Here you can assign the mapping labels. 3. Click the icon in the Mapping label" column. A dropdown selection menu is opened with a list of the mapping labels for parameters or signals stored in AdvES. 4. As shown in the following diagram, assign the mapping labels to the signals of the "AMON_Std" type.
Figure 4-19: Mapping labels of the "AMON_Std" CMT
Copyright
Note
After you assigned a label, the status of the type will change to "yellow". After you assigned the mapping labels for all signals, the status will change to "green".
43
Copyright
Note
If you assign a mapping label to a connection for the first time, it will be applied to all equal connections in the CMTs. These connections will then be marked blue, as shown in Figure 4-22. If you change existing mapping labels you can choose whether the mapping label will also be changed for the connections with the same name of all CMTS. Alternatively, you can define exceptions via the "Only for this connector" button. These will then be marked red.
44
6. In the next step, as shown in the following diagram, assign the mapping labels to the signals of the "ValveAnalog" type.
Figure 4-23: Mapping labels for the "ValveAnalog" CMT
Copyright
45
4.2.2
Procedure
1. Open the Variants tab. If the status of all CMTs is green than the Variants tab is enabled. 2. Click the "ValveAnalog" entry. 3. Click on "Click here to add a new variant".
Figure 4-24: Creating variants of the "ValveAnalog" type
Note
4. Enter the name "Valve_FBC". 5. Disable the option for the "FbkOpen" block. 6. Create another variant for the "ValveAnalog" CMT:
Table 4-1: Variants of the type "ValveAnalog" Variant 2 Name Valve_no_FB FbkOpen disable FbkClose disable
Copyright
46
Note
The blocks "FbkOpen" and "FbkClose" are included in the "ValveAnalog" basic type.
This way you created, as described in chapter 3.5, two variants from one "ValveAnalog" CMT. 7. After you assigned all signals and parameters of the types, click the "Generate" button in order to create the copy templates of the CMTs. Loss of the assignments When generating the copy templates, the selection of the mapping labels is not saved in this dialog. To save, click the OK button or Apply.
Figure 4-26: Generating copy templates
Copyright
NOTICE
47
You need the copy templates in order to specify the process tags later on (see chapter 4.4).
Result
Figure 4-28: Assignments for data from PCS 7
Copyright
48
4.2.3
Note
Procedure 1. Click the button in the header bar next to the Menu. A drop-down menu will open. 2. Click the Manage mapping labels menu entry.
Figure 4-29: Creating mapping labels
Copyright
The Manage mapping labels dialog box opens. The editing mask is divided into three areas: parameter, signal and signal parameters. If you would like to, for example, create a new mapping label for a parameter, you have to proceed as follows:
Figure 4-30: Manage mapping labels dialog
49
3. Click the Parameter tab. 4. Click the Add new element button . A new empty row is recreated. It is stored under the User defined status.
Figure 4-31: Creating mapping labels for parameters
5. Here, you assign the new name and the description of the new mapping labels. 6. The mapping labels have to be switched visible, so that they can be used as mapping labels. 7. Subsequently, click the "Apply" button. 8. Click the Manage mapping labels dialog box. Only once the Manage mapping labels dialog has been closed, are newly created mapping labels read out and can be used for assignments.
Figure 4-32: Creating mapping labels for parameters
Copyright
Note
50
9. If you have created a mapping label, assigned it and created the copy template, the mapping label status in User-defined mapping label will change. You can therefore no longer delete the mapping labels via the button.
Copyright
10. If you are replacing the mapping label you have created by another one and you are creating the copy template again, your mapping label created by you is no longer used and this is displayed under the user defined status. You can therefore delete the mapping label again.
51
Note
When you enable the Show predefined labels option box, all default mapping labels are displayed. You cannot edit or delete them. They can only be switched visible or invisible. This has the advantage that only all relevant default mapping labels are visible and that they are displayed in the dropdown selection menu.
Copyright
52
4.2.4
Note
Procedure 1. Click the button in the header bar next to the Menu. A drop-down menu will open. 2. Click the Transfer mapping labels menu entry. In the working area, an overview of all AdvES projects is opened.
Siemens AG 2013 All rights reserved
Copyright
3. Select the project from which you wish to transfer the mapping labels. 4. Subsequently, click the transfer "Apply mapping labels" button. The mapping labels are applied in your current project.
53
Note
NOTICE
Subsequently check the mapping labels and, if required, correct them. Variants will not be transferred here. New variants must be generated for the project.
Copyright
5. After assigning all mappings, generate the CMTS copy templates, as described in chapter 4.2.2.
54
4.3
Copyright
Requirements for importing Excel lists must meet the following requirement to ensure the correct transfer of information from Excel and generation of data in AdvES: Each column must be clearly defined (identical information in one column). The sequence of entry of the columns with the respective information into the Excel list is not specified. A configurator selects the columns and assigns them correctly (see chapter 4.3.1 "Creating the configurator for importing").
55
Types of Excel lists AdvES can process two types of Excel lists: Process tag list The process tag list includes all process tags with name and associated detailed information. Signal list (used in this application example) The signal list includes all signals with name and associated detailed information. In the table below the list types are clearly illustrated. In this table it is shown what information has to be included in the lists in order to generate the respective data. The following table shows which information must or can be available in a process tag or signal list (Excel list).
1. 2. 3. The column "mapping target" and "mapping class" indicates the assignment you have to select in the configurator for the respective information. The "must/can" column shows which information is optional or mandatory for the respective list type. The column "when" shows the list types. It specifies which information must be available to achieve the corresponding target, e.g. importing data for generating signals and hardware. The following applies to the technological hierarchy levels: Whether and how the technological hierarchy is used here depends on the level on which the signal data or process tag data is imported to AdvEs. The TH must be gapless from the used import level on.
Note
4.
Copyright
56
Copyright
57
4.3.1
Procedure 1. Click on the "Import signal/process tag list" button in the workflow bar.
Figure 4-40: "Import signal/process tag list" menu
The "PCS 7 Import/Export" dialog box will open, with the "Import" tab open. 2. Click on the "Configuration" tab to create a new configurator.
Siemens AG 2013 All rights reserved
3. Click on the "New..." button to create a new configuration object. 4. Assign a suitable name.
Figure 4-41: Creating a new Excel configurator
Copyright
58
5. Then select the Excel list for the example project and click on the Load button.
Figure 4-42: Loading the Excel list
Note
Siemens AG 2013 All rights reserved
The selected Excel file will be opened. It is a signal list with hardware information.
Copyright
59
6. Check the Excel list for relevant information Note Take the list from Figure 4-39 and compare which information is available in the signal list. Please note the following:
Which data is relevant and to be imported? Which import type can be used and is the required information available?
In this example, we are looking at a signal list with hardware information, i.e. you can generate the control modules (CMs) with the TH, the corresponding signal interconnections, and the corresponding hardware (DP slaves) from this list. 7. Select the Excel worksheet ("signal_list_example") and the Excel start row from which the configurator will read out the data later on. 8. Select line "2" as the Excel start row. 9. Using drag & drop, move the hierarchy folder of level 1 to the "Import target" field.
Siemens AG 2013 All rights reserved
Copyright
10. Define the significance of the columns in the signal list in AdvES. There are two variants according to which you can approach: 1st variant You can transfer all Excel columns to the configurator, via the "transfer all Excel columns" function. Since the list includes a lot of information which is not required, the second variant is recommended. 2nd variant You can add the Excel columns individually to the configurator via Add column definition and via drag & drop from the Excel list to the configurator. This step is required for AdvES to be able to read in the data and to correctly assign it.
60
Example:
Table 4-2: Assigning columns Column AJ M B Unit CMT Function Controller Name Significance in AdvES project TH1 Process tag function Name of station (AS)
11. Select a cell in the "AJ" column and place the cursor on the frame of the cell until the cursor changes its icon. This will work on one of the side edges of the cell, but not on the corners. 12. With the mouse button pressed down drag the cell to AdvES. A column object is generated. 13. Enter line 1 as header row. For all other column objects, the name entered in row one is used.
Figure 4-45: Generating a column object
Note
Copyright
61
Content Includes the letter of the Excel column Includes the cell value of the "Excel start row" that you defined in the configuration Defining a category of mapping labels. Mapping labels can be: Technological hierarchy Process tag Control module attribute Control module parameter Signal Signal attribute Signal parameter
Data
Includes the first three values of the Excel column from the defined "Excel start row"
After you inserted the column into the configuration and thus communicated it to AdvES, you now have to map it, so that AdvES can detect which information is read and can process it correctly. 14. Assign the mapping class for TH, use Figure 4-39 for this purpose. 15. Click the arrow field of the mapping class in the column definition. 16. A menu with the selectable definitions will open. 17. Select the entry "Technological hierarchy".
Figure 4-46: Assigning the mapping class
Copyright
62
18. After assigning the mapping class you now need to assign the associated mapping target (see Figure 4-39). Depending on the selection of the assignment class, other assignments are offered in the dropdown menu. Select TH level 2.
Figure 4-47: Assigning the mapping target
Copyright
63
19. Repeat this procedure also for the following required columns.
Table 4-4: Configuring the column objects Column L Name Control Module Name Mapping class Process tag Mapping target 02 (Control module AdvES) (splitting... see paragraph below "Splitting and assigning information from Excel lists") Function of the control module PCS 7 control module name (splitting... see paragraph below "Splitting and assigning information from Excel lists") Station name Variable mapping (see paragraph below "Assigning the mapping labels for signal names of the Excel list") (splitting... see paragraph below "Splitting and assigning information from Excel lists") Address DP slave order number HW signal type Channel PCS 7 signal name Signal module number Station name Slot Subnet
M L
B K
D H I F K Y B E C
Station Address DP-IM MLFB I/O Type Channel Signal Name I/O Module MLFB Controller Slot Bus
Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute
Copyright
64
Splitting and assigning information from Excel lists AdvES provides the option of splitting information in Excel columns. Using the "splitting" button you can split the content of a cell and assign different mapping classes and mapping targets to the contents. This example shows you how to separate and assign the information for the mapping class "process tag" in column "J". Procedure 1. Click on the column definition for mapping class "process tag". 2. In the properties view of the column click on the "Splitting" button.
Figure 4-48: Splitting a column object
Copyright
3. Then click the button. The "Splitting" dialog box will open. There you can define the criteria for splitting. 4. Use the following options for splitting: Split character From the back: with a space character
65
5. After splitting, a second box will open which is referenced to the same column.
Figure 4-50: Splitting the "L" column
Copyright
66
6. Hide the left splitting of column L. Click the Hide button (see Figure 4-50). 7. Assign "process tag" as the mapping class and "02 (control module AdvES)" as the mapping target.
Figure 4-51: Assigning the mapping target for column "L"
Copyright
Note
Splittings can also be disabled via the "Hide" button. The hidden content will not be used and will not be imported to AdvES.
67
Assigning the mapping labels for signal names of the Excel list (Variable mapping) When assigning the mapping labels for signals you perform a variable assignment. For the signals found in the Excel list, the corresponding NAMUR labels will be assigned.
Procedure 1. Assign the appropriate NAMUR ID in the column definition of the Signal mapping class (column I). Click on the button in order to transfer the signal names to the assignment field. Execute this step for all names.
Figure 4-52: Assigning the corresponding NAMUR IDs for the signal names
Copyright
68
2. The mappings for the "Technological connections" of the CMTs were assigned in chapter 4.2.1. Assign the mapping labels of the associated "Technological connections" to the corresponding signal names of the Excel signal list. This creates a link (as described in chapter 4.2) between PCS 7, AdvES, and the Excel list.
Figure 4-53: Assigning the corresponding mapping labels
This ensures that the structure of the data during the import from Excel is maintained, i.e. the assignment of signals and parameters to the CMTs. For a later export of the data from AdvES to PCS 7, for example, the signal input of the respective CM instance is assigned to the appropriate signal.
Figure 4-54: Mapping labels for SIMATIC PCS 7 and Excel
Copyright
69
Result
Figure 4-55: Configurator part 1
Column AJ L
Mapping target 02 (hierarchy file level 2) 02 (control module AdvES) (splitting... see paragraph above "Splitting and assigning information from Excel lists")
M L
Function of the control module PCS 7 control module name (splitting... see paragraph above "Splitting and assigning information from Excel lists")
Copyright
B K
Station name Variable mapping (see paragraph above "Assigning the mapping labels for signal names of the Excel list") (splitting... see paragraph above "Splitting and assigning information from Excel lists") Address DP slave order number HW signal type Channel PCS 7 signal name Signal module number Station name Slot Subnet
D H I F K Y B E C
Station Address DP-IM MLFB I/O Type Channel Signal Name I/O Module MLFB Controller Slot Bus
Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute Signal attribute
70
4.3.2
Importing Data
Prerequisite for importing data from a signal or process tag list is a corresponding list with a matching configurator.
Procedure 1. After creating the configurator, open the import dialog box. 2. Fill in the fields according to the table below: Import type: Configuration: Edit: Create:
Siemens AG 2013 All rights reserved
Note
Here you select whether the list to be imported is a process tag or a signal list. Here you select an existing configurator. Here you change an existing configurator (e.g. after you changed the Excel list). Here you create a new configurator. Here you select the Excel file from which to import the data. When the checkbox is disabled the data to be imported is instantly integrated into the AdvES project. If the checkbox is enabled, the data to be imported is not instantly transferred to the AdvES project but is first of all saved in a working layer. This is to prevent faulty imports from being immediately transferred into the AdvES project and destroying it.
Copyright
Import target:
Here you define the import target from the "Project" tab via drag & drop.
3. Enable the Import new working layer checkbox with a mouse click. 4. Then click on the "Import" button to import the signal list data to AdvES.
71
Figure 4-57: Import dialog box for importing from the Excel list
During import a continuous protocol will be output. It includes information on the progress of the import and potential errors. Each empty cell in a column to be read out causes a warning message. In this example, a warning message will appear that there is no content in the cells of the columns for Subnet, DP slave order number and Signal module order number. This was done deliberately in this example, to show you how to add this data in AdvES (see chapter 4.6).
Note
Siemens AG 2013 All rights reserved
Copyright
72
Note
By enabling the Import new working layer checkbox, AdvES will work with the working layer when importing external data. Imported data will not be transferred into the AdvES project immediately, but will be stored in a working layer first. This is to prevent faulty imports from being immediately transferred into the project and destroying it.
The data imported to AdvES is made available in a working layer. Before you proceed you can determine whether to use or discard the imported data (in case of a faulty import). The "project" tab in the navigation area shows the status of the objects after import as follows:
Figure 4-60: Imported data from the Excel list
Copyright
73
As soon as the import is confirmed, the control buttons in the header bar are blocked and the buttons for releasing or discarding the import are enabled.
Siemens AG 2013 All rights reserved
Note
The release, accepts the changes fully in the project. Discarding deletes the changes from the signal or process tag lists last imported. An import can only be performed after the previous import has been released or discarded. 7. Release the import if it was performed correctly.
Copyright
Note
Clicking on the "Release import" button will fully transfer the imported data from the working layer into the AdvES project and it can be further processed. With the Discard import button, the imported data in the working layer is deleted and is not accepted in the AdvES project.
74
4.4
Procedure 1. Click on the "Specify control modules" button in the AdvES header bar.
Figure 4-64: "Specifying control modules" menu
Copyright
75
2. Using drag & drop, move the project node into the "Start object" field. All control modules under the object node will be displayed.
Figure 4-65: Dialog box for specifying the control modules
Copyright
3. Open the "Copy templates" tab in the navigation area. This is where you find the copy template of the imported CMTs from the master data library. Prerequisite is that you have correctly executed the steps described in chapter 4.2. 4. Perform the assignment for each function type once. Drag the respective copy template via drag & drop to the respective function type.
Table 4-7: Specifying Control Modules No. 1 2 3 4 5 6 7 Function of the control module M IC V V_C V_OC I MSF CTRL_Std Valve_no_FB Valve_FBC ValveAnalog AMON_Std MOT_2sp Copy template MOT_1sp_2fb_1cm
76
Note
Copyright
Open the "Copy templates" tab in the navigation area. From there you can assign a copy template to each CM using drag & drop. This procedure is more efficient and is used in this example.
77
After you performed the mapping for each function type once, you assign the missing mappings automatically via the button on the right. This initiates the assignment of the CMTs to the remaining CMs according to their function.
Figure 4-67: Automatic assignment of the CMs
Copyright
icon in the
6. Click on "Execute (all)" in the drop-down menu. The assignments will be executed and their status checked.
Figure 4-68: "Execute (all)" menu
78
7. As soon as the status of all mappings is green you can close the dialog box.
Figure 4-69: Specifying of all CMs completed
Copyright
79
4.5
Configuring connections
You can configure cross-chart interconnections in AdvES (connections between control modules). In this example the CMs of the CTRL_Std controller type are to be interconnected with the appropriate analog valves. Two work steps are required in AdvEs to configure interconnections: 1. You determine which signals of the control module types are to be always interconnected (chapter 4.5.1). 2. You determine for which control module instances this option of interconnection shall be used (chapter 4.5.2).
4.5.1
Procedure
Copyright
The "Connect types" dialog box will open. Define the predecessor and successor control module. In this example, we want the "CTRL_Std" type to control the types "ValveAnalog", "ValveFBC", and "Valve_no_FB", which means the "CTRL_Std" type is the predecessor control module and the "ValveAnalog" type and its variants is the successor control module. 2. Drag the CTRL_Std copy template via drag & drop into the field for the predecessor control module and the ValveAnalog copy template into the field for the successor control module. All signals of the selected control module types are displayed. 3. Using drag & drop, connect the "MV" output of the predecessor control module ("CTRL_Std") with the "MV_Ext" input of the successor control module ("ValveAnalog", "Valve_FBC, and "Valve_no_FB").
80
Copyright
4. Click on the "Apply" button and then "OK" to close the dialog box. You can only interconnect input signals that are not connected to hardware channels and that are not listed in the icon table.
Note
81
4.5.2
Procedure
2. Drag the project node into the "Start object" field. 3. Drag the respective IC-CM into the Interconnected predecessor cell of the appropriate V-CM from the Acid Sel and Gas Rel hierarchy folder in the navigations area (via drag & drop).
Siemens AG 2013 All rights reserved
This is how you specify which CMs are to adopt the defined interconnections (see chapter 4.5.1).
Figure 4-74: Definition of connections for the individual IC CMs to the V-CMs
Copyright
82
4. After you assigned the associated CTRL CMs to each of the Valve CMs, click on the > "Execute (all)" button.
Figure 4-75: "Execute (all)" menu
5. When the status of all connected V CMs is green, click on the "close" button.
Figure 4-76: Connection definitions
Copyright
83
4.6
Assigning hardware
Apart from the import of the hardware information from the external signal list, you can also process the hardware assignment in AdvES manually. Since there is no information regarding the respective order numbers for the DP slaves and the I/O modules in the signal list of the example project, you have to assign them manually in AdvES. Furthermore, you have to change the data for the subnet.
Procedure 1. Click on the "Assign hardware" button in the AdvES workflow bar.
Figure 4-77: "Assign hardware" menu
The dialog box for the hardware assignment will open in the work space.
Siemens AG 2013 All rights reserved
2. Specify your project as start object. All signals available under the object nodes will be displayed. The hardware catalog is located on the right side of the dialog box. From this catalog, you can specify the respective DP slave type and the I/O module type. 3. Using drag & drop, insert a DP slave type and a module type from the hardware catalog for each HW signal type, Execute it in accordance with Table 4-8. The DP slave type and the I/O module type needs to be assigned to a hardware signal type once only.
Figure 4-78: Single assignment of the I/O module type and DP slave type
Copyright
84
Note
With the filter functions in the column heads, you can make the assignments faster and more efficiently. You can, for example, filter for hardware signals which you would like to assign to the hardware and do not have to look in the list fist.
HW signal type AI 2x0/4-20mA HART AI 4xRTD AO 2x0/4-20mA HART DI 16x24VDC DI 4xNAMUR DO 8xRelais
DP slave type IM 153-2 HF 6ES7 153-2BA02-0XB0 IM 153-2 HF 6ES7 153-2BA02-0XB0 IM 153-2 HF 6ES7 153-2BA02-0XB0 IM 153-2 HF 6ES7 153-2BA02-0XB0 IM 153-2 HF 6ES7 153-2BA02-0XB0 IM 153-2 HF 6ES7 153-2BA02-0XB0
I/O module type 2AE, 0/4-20mA HART, EX 6ES7 331-7TB00-0AB0 8AE thermo, 4AE PT100, EX 6ES7 331-7SF00-0AB0 2AE, 0/4-20mA HART, EX 6ES7 332-5TB00-0AB0 16DE, DC 24V 6ES7 321-1BH01-0AA0 4DE, DC 24V, EX 6ES7 321-7RD00-0AB0 8DA, Relais, DC 24V, AC 120/230V, 5A 6ES7 322-5HF00-0AB0
Copyright
85
. Here you can check 4. Subsequently, click the "Open selection list" button whether your assignments to the respective hardware signal types have been correctly recorded by AdvES.
Figure 4-79: Overview of the assignments
Note
There will be no verification between HW signal type and I/O module type. The hardware is assigned individually for each signal. Make sure that the signals to be connected with the same module are connected with the same module type. 5. You can automatically assign the hardware (HW) to the remaining signals of the same hardware signal type. To do this, click the Map HW (all) button.
Figure 4-80: Assigning hardware automatically
Copyright
86
6. Subsequently click the Refresh button so that you can see if the hardware data was correctly assigned. 7. Click "Apply" and then "OK".
Figure 4-81: Automatically assigned hardware
8. Open the AdvES menu in the header bar and click on the "Table view signal list PLC" entry.
Figure 4-82: Opening the "Table view signal list PLC"
Copyright
You have assigned a name for the PROFIBUS master system in your PCS 7 project. Since this information is not available in the example signal list and therefore not in AdvES, you need to enter it into the PLC view manually.
87
9. Drag your project node into the "Start object" field. The signals existing under the start object in the AdvES project are displayed as a table with the properties belonging to the signals: Signal name Signal description Station name Signal parameter Hardware assignment Bus addresses Module slot Channel assignment Existing signals can be checked and changed here.
Figure 4-83: Structure of the table
Copyright
11. Select the first cell in the "Subnet" column and press "Ctrl" and "A" at the same time. All cells in the column will be selected. 12. Right click on the selection. A context menu opens. 13. Click the "Edit" entry. An entry field opens.
88
14. Enter the name of your PROFIBUS master system into the input field.
Figure 4-86: Assigning the name for the subnet
Copyright
NOTICE
If you click the OK button, the following dialogs will appear. Click the No and Cancel button otherwise you will change the AdvES database.
89
Copyright
90
4.7
Consistency check
Automatic consistency checks are performed during data transfers. In case of errors the transmission will be canceled. Advanced ES also provides the option of manually initiating a consistency check at any time. You can check the following objects: Technological hierarchy Process tags Signals Parameters
Copyright
The window for the consistency check will open in the work space. 3. Drag your project node into the "Start object" field via drag & drop. The consistency check is initiated. After the check, you will be shown a log with the respective status of the objects in the work area.
91
Copyright
Note
Every non-connected parameter / signal creates an inconsistency warning. In this example such warnings are also created, since not all parameters and signals are connected.
92
Note
Status 1 State complete Description AdvES object is consistent and complete. Data can be transferred to PCS 7. A warning may indicate an error or a deliberate deviation from the standard, created by the user. An error occurred, preventing the generation to PCS 7.
Inconsistency warning
Inconsistency error
In case of errors or warnings you can double-click on the corresponding row to go to the object concerned 4. If no errors occurred during the consistency check, you can export the data.
Siemens AG 2013 All rights reserved Copyright
93
4.8
Copyright
Procedure 1. Click on the "PCS 7 export" button in the workflow bar to execute the export.
Figure 4-92: "PCS 7 Export" menu
In the work area the PCS 7 Import/Export tab is opened. In the opened dialog the Import from PCS 7 tab is preselected. 2. Click on the "Export to PCS 7" tab. 3. Enable the export option selections for technological hierarchy, control modules, and hardware in the export dialog.
94
4. Click on the Export button. The data to be exported is generated. A protocol is generated and displayed during the process.
Figure 4-94: Protocol
Copyright
Note
During this process, warnings will be generated since not all the signals of the example are connected.
95
Note
If an error occurs during generation, you cannot proceed with the next steps. The errors must be corrected before any further processing. Perform a consistency check to analyze the errors in more detail (see chapter 4.7). Warnings will not block the export.
5. If the data was generated without errors, the Data transfer - Generate/import window opens and a comparison between the AdvES project data and the PCS 7 project data is automatically triggered. The differences between the PCS 7 project and the AdvES project are marked in color.
Figure 4-95: Comparison dialog
Copyright
6. Click on the button to trigger the object export. This transfers the technological hierarchy and the hardware. The dialog box for the data comparison opens. 7. Click on the OK button.
96
8. Click on the Yes button to update the project data once more.
Figure 4-97: Dialog box for updating the projects (AdvES - PCS 7)
9. Click on the
Copyright
97
10. The dialog box for data comparison will open again. 11. Click on the "Yes" button to compare and update the project data once more.
Figure 4-99: Dialog box for updating the projects (AdvES - PCS 7)
Copyright
12. Close the window. The data selected for transfer (TH, CFC, hardware, messages and interconnections) is now available in the PCS 7 project.
98
Copyright
99
Copyright
100
Interconnections generated from the AdvES data between the B-101-IC control module and the B-101-V control module.
Figure 4-105: Interconnection between control modules B-101-IC and B-101-V
Copyright
101
Copyright
102
4.9
4.9.1
Note
Procedure 1. Open the context menu of a TH folder by right clicking in the project view.
Siemens AG 2013 All rights reserved
2. Navigate to: New > RP Report folder and click RP Report folder.
Figure 4-108: Creating report folder
Copyright
103
3. By right clicking the report folder, you can create the respective report design template there.
Figure 4-109: Creating the report design templates
Copyright
104
4.9.2
Procedure 1. Open the project view in the navigation area of AdvES. 2. Navigate to the desired control module. 3. Open the control module by right clicking the context menu. Via this menu you can now create a CM test sheet.
Figure 4-110: Creating an CM test sheet
Copyright
105
Copyright
Note
Alternatively, you can also create the CM test sheets for several control modules via the process tag list table view or via the report folder.
106
4.9.3
Table views
In AdvES you can also process mass data. Different table views are available for this purpose.
Procedure The following applies to all table views: 1. The different table views can be selected via the dropdown menu in the AdvES header. Click the button next to the Menu. 2. The drop-down menu will open. Via this, different table views can be selected.
Figure 4-113: Table views
Copyright
Functions in the tables In the header bar of a table view you can refresh all contents with a button.
Figure 4-114: Refreshing the contents
107
In the header of a table view there is a button for exporting the contents. Exception: Table view connections. By clicking the triangle you can select the export format and at the same time trigger the export. Microsoft Excel is preset by default.
Figure 4-115: Exporting the contents
a.) By writing directly into a field. b.) Several fields can also be selected (e.g. by Ctrl + A). By right clicking one of the selected fields a context menu opens. Editing (F2) can uniformly change the content of the selected cells (see chapter 4.6). c.) A text can be transferred to another field by right clicking a cell (context menu opens) and clicking Copy texts, then right clicking on a different cell and Paste texts. If the text is to be transferred to several fields, the text is to be copied first, then the fields are selected and opened for editing (see b) and the text can be inserted with Ctrl + V. By placing the cursor in the header of a column, two selection buttons become visible. With the left one you can sort the rows alphabetically.
Figure 4-116: Alphabetical sorting
Copyright
108
With the right one you can create a filtered view of the data. The filter value is selected in the check box (left) and executed with the flash button (see chapter 4.6).
Figure 4-117: Sorting according to contents
Copyright
109
4.9.4
Project properties
In AdvES from version 8.0 SP1 you have the option to define project properties.
Procedure 1. Click the button in the header bar next to the Menu.
A drop-down menu will open. 2. Click the Project properties menu entry.
Figure 4-118
Copyright
3. The "Attribute" dialog box will open. Here, you can enter general information on the project that will be used in other places, for example, in reports or test sheets.
Figure 4-119
110
5 Conclusion
Conclusion
This application has shown that Advanced ES provides a solution for more efficient engineering and optimized data processing in order to improve the engineering process so far. This becomes apparent by the use of a new type concept which represents a great advantage compared to IEA. Furthermore, Advanced ES is an approach to replace previous heterogeneous tools for project realization by a homogenous software option package. The great advantage here is that documentation, support as well as further development of the tool is guaranteed.
Copyright
111
6 Further Links
Further Links
Table 6-1: Internet links Topic 1 SIMATIC PCS 7 Process Control System; Advanced Engineering System SIMATIC PCS 7 CFC Process Control System for SIMATIC S7 (V8.0) Siemens Whitepaper Fast Track Engineering Entry ID: 57414032
http://support.automation.siemens.com/WW/view/en/57414032
Title
German:
http://www.automation.siemens.com/mcms/process-controlsystems/SiteCollectionDocuments/efiles/pcs7/support/marktstudien/W P_Fast-Track-Engineering_DE.pdf
English:
Siemens AG 2013 All rights reserved
http://www.automation.siemens.com/mcms/process-controlsystems/SiteCollectionDocuments/efiles/pcs7/support/marktstudien/W P_Fast-Track-Engineering_EN.pdf
FAQ: How can you export and then re-import PCS 7 Advanced ES project data? Application: "Integrated Engineering with COMOS and SIMATIC PCS 7 in a practical example" Online entry: Service Pack 1 for SIMATIC PCS 7 V8.0 (EU) available
Copyright
Online entry: SIMATIC PCS 7 Advanced Engineering System V8.0 Service Pack 1 available
112
7 History
History
Table 7-1: Document versions Version V1.0 V2.0 Date 06.2012 07.2013 First version Creating PCS 7 project, configuring messages in CMT, creating individual mapping labels, chapter 4.9 "Other useful functions in AdvES, refreshing texts and images. Modifications
Copyright
113