Plant Automation Accelerator 2.0

Transcription

1 Security information 1 Preface 2 Objectives and performance scope of the data interface 3 Operating Manual Overview of data exchange with PCS 7 4 Requirements in PCS 7 5 Preparations 6 Management of control module types 7 Management of enumerations 8 "Type configurator" plugin 9 Using "Excel import" 10 Engineering in PAA 11 Editing large quantities of connections 12 Linking attributes from PAA and PCS 7 13 Export from PAA to PCS 7 14 Import from PCS 7 to PAA 15 Working with reports 16 01/2018 A5E AA Reference 17

2 Legal information Warning notice system This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION indicates that minor personal injury can result if proper precautions are not taken. NOTICE indicates that property damage can result if proper precautions are not taken. If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage. Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems. Proper use of Siemens products Note the following: Trademarks WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed. All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner. Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions. Siemens AG Division Process Industries and Drives Postfach NÜRNBERG GERMANY A5E AA P 04/2018 Subject to change Copyright Siemens AG All rights reserved

3 Table of contents 1 Security information Preface Objectives and performance scope of the data interface Overview of data exchange with PCS Requirements in PCS Preparations Creating a new engineering project Opening a planning project Creating the DCS structure Standard ISA 88 in the unit structure Management of control module types Structure of control module types Importing control module types Managing variants using optional blocks Synchronizing CM variants Creating a control module type Creating control variables Transfering LowScale/HighScale/Unit between PAA and PCS Creating messages Creating control modules Creating a CM in the DCS structure Creating aggregated CMTs Working with negations Using references Management of enumerations Creating enumeration types Using enumerations "Type configurator" plugin Objective of the type configurator Opening the "Type configurator" plugin Creating a global command and status library...43 Operating Manual, 01/2018, A5E AA 3

4 Table of contents 9.4 Large-scale operations Aggregated CMTs Variant overview Graphical properties Creating functions Configuring messages Using "Excel import" Engineering in PAA Transfer of logic blocks Adapting the assignment of the right-hand mouse button Functional characteristics of the hardware objects Information on identifying hardware components Available HW modules GSD GSD information Objective and performance scope of the interface Importing GSD files Assigning GSD objects Hardware engineering in the Navigator Creating the new physical structure via Right mouse click PROFINET and PROFIBUS Configuring a SIMATIC station Configuring the central processing unit (CPU) Creating an interface module as distributed I/O Equipping interface modules with I/O modules Configuring IO modules Creating the bus modules Creating a redundant SIMATIC station Creating a redundant I/O Using the DP/PA coupler Editing hardware engineering via engineering tasks Assigning a field bus to a DP slave via a task Assigning redundant fieldbus via engineering task Hardware engineering with the configuration tool Opening the configuration tool Creating hardware with the configuration tool Creating hardware including spare I/O channels Hardware including spare I/O space for modules is created Creating redundant signal modules Creating redundant stations Creating licenses HW configuration tool Configuring AS Bundle using HW configuration tool Configuring ET 200 stations using HW configuration tool Operating Manual, 01/2018, A5E AA

5 Table of contents Configuring WS Bundle using HW configuration tool Configuring PCS 7 Box using HW configuration tool Extended hardware parameters Software engineering in the Navigator Notes on the plant hierarchy Working with channel requests Optional: Creating and configuring process tags Optional: Linking hardware and software: Implementing channels Editing software engineering using engineering tasks Engineering tasks Displaying the "SW interface" tab and creating tasks Assigning a control module type to the DCS structure Assigning a control module type to a function Assigning control module types to the DCS structure in bulk "Assembly updater" plugin Update type usages Updating usages / instances Legend Variant administration Using symbol tables Symbol table Importing symbolic addresses into a symbol table Refreshing the symbol table Engineering in the function diagram Editing control modules on the function diagram Editing the logic on function diagrams Example for interlock logic on function diagrams Specifying the measuring ranges Moving the PH Editing large quantities of connections Linking attributes from PAA and PCS Configuring the mapping table of the signal designations Using the navigation assistant Example of an assignment Adopting a mapping table as a template Export from PAA to PCS Selective transfer Transfer of the S7 unit Exporting digitally signed XML files: Exporting a PAA project Exporting the technological hierarchy Exporting instances Operating Manual, 01/2018, A5E AA 5

6 Table of contents 14.7 Exporting types Exporting the hardware configuration Exporting ET 200 I/O modules from PAA to PCS Exporting ET 200PA SMART modules from PAA to PCS Exporting ET 200iSP modules from PAA to PCS Import from PCS 7 to PAA IO channel implementation Hardware transfer Attributes of CM Managing PCS 7 libraries in COMOS Importing digitally signed XML files Importing a PCS 7 project Importing the technological hierarchy Effects of importing the plant hierarchy Importing control modules Importing the hardware configuration Importing ET 200SP HA from PCS Importing ET 200M from PCS 7 to PAA Importing ET 200PA SMART from PCS 7 to PAA Importing ET 200iSP from PCS Working with reports Signal connections on Function diagram Assembly plan I/O report Bill of materials Configuration plan Configurable symbols Computer data sheet Reference Information in the "Data transfer - Generate/import" dialog Navigator "Import / Export PCS 7" plugin Calling the "Import / Export PCS 7" plugin "Import" tab "Export" tab Reference to the mapping table Operating Manual, 01/2018, A5E AA

7 Table of contents 17.5 Reference to the navigation assistant "Type configurator" reference plugin Excel import" reference plugin Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7" Glossary Operating Manual, 01/2018, A5E AA 7

8 Table of contents 8 Operating Manual, 01/2018, A5E AA

9 Security information 1 Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines, and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions constitute one element of such a concept. Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place. For additional information on industrial security measures that may be implemented, please visit: Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under Operating Manual, 01/2018, A5E AA 9

10 Security information 10 Operating Manual, 01/2018, A5E AA

11 Preface 2 Introduction to SIMATIC PCS 7 PAA (Plant Automation Accelerator) PAA is an COMOS integrated engineering solution for PCS 7 projects, which has the following benefits: Shorter project times - More efficient PCS 7 engineering with higher quality Lower project costs - Holistic object oriented data model which allows technical engineering with lower expert knowledge. Lower maintenance costs during plant operation - An up to date plant documentation with change management for the complete PCS 7 project Purpose of this documentation The Operating manual is aimed at the people who operate and monitor PAA in an engineering system. This manual guides you through basic features of PAA. You will also get to know the elementary configuration steps and in the process, you will develop an understanding on how PAA works. Prerequisites General knowledge in the area of automation engineering, basic knowledge of SIMATIC PCS 7, COMOS and PAA is required to understand this documentation. Guide The PAA documentation also includes references to the SIMATIC PCS 7 documentation. This enables you to quickly access the required documentation. Accessing PAA documentation The relevant versions of the documentation for PAA is available on the internet pages of the PAA ( For information on COMOS, you can refer to COMOS Overview ( support.industry.siemens.com/cs/ww/en/view/ ). For information on PCS 7, you can refer to PCS 7 ( Conventions In this document, all the instructions are given using their full menu commands. You can also access virtually all functions through the shortcut context menu or by double-clicking. Operating Manual, 01/2018, A5E AA 11

12 Preface 12 Operating Manual, 01/2018, A5E AA

13 Objectives and performance scope of the data interface 3 Objective The plugins in the menu "Plugins > Automation > PCS 7 interface" offer a bidirectional interface to exchange engineering data with SIMATIC PCS 7. Following initialization of the SIMATIC PCS 7 Plant Automation Accelerator (PAA) project and the PCS 7 project, you can work in either of the two programs. The objective is a "digital plant" through integrated engineering with PAA and SIMATIC PCS 7. In the digital plant, plant planners and plant operators work on the same database and thus generate uniform engineering. Performance scope of the interface Bidirectional import/export of Control Module Types (CMTs) Bidirectional import/export of control modules and parameters, messages and signals Update of instances of control modules Bidirectional import/export of signal connections Implementation of channels and signals Block logic in function diagrams Bidirectional import/export of hardware including symbol tables Bidirectional import/export of redundant CPU hardware including symbol tables Bidirectional import/export of hierarchy folders Bidirectional import/export of interlock logic Renamed objects Renamed objects are recognized once again during data exchange and are compared during data comparison. Renaming is detected for the following objects: Unit hierarchy nodes Control module types (CMT) Control module (CM) Functions Signal parameter (CV) Enumeration Operating Manual, 01/2018, A5E AA 13

14 Objectives and performance scope of the data interface Enumeration value Hardware: Station, slave (central, slave) Subnetwork, bus (global subnet) Exceptions The following graphic data is ignored after the import in PAA: No import of the graphical arrangements of the hardware configuration in HW Config of STEP 7. No import of the graphical display of CFC and function diagrams. Plugins The following plugins are available to you in the menu "Plugins > Automation > PCS 7 interface": Name Icon Usage "Import / Export PCS 7" "Type configurator" "Connection manager" "Assembly Updater" "Excel import" "Types re-assignment" "HW configuration tool" See also chapters Import from PCS 7 to PAA (Page 125) and Export from PAA to PCS 7 (Page 115). See also chapters Management of control module types (Page 25) and "Type configurator" plugin (Page 43). See also chapter Editing large quantities of connections (Page 107). See also chapter Update type usages (Page 96). See also chapter Using "Excel import" (Page 49). See also chapter Synchronizing CM variants (Page 30) See also chapter HW configuration tool (Page 78) 14 Operating Manual, 01/2018, A5E AA

15 Overview of data exchange with PCS 7 4 Bidirectional data exchange During data exchange between PAA and PCS 7, data can be transferred and synchronized bidirectionally. For transfer and synchronization, there are the following options: Direct data exchange: if PAA and PCS 7 are installed on the same PC. As such, the types and instances of control modules from PAA and PCS 7 can be read out and contrasted via the import service of the Automation Interface (AI). Indirect data exchange via an XML file: if PAA and PCS 7 are installed on different PCs. For indirect data exchange, first export the data to an XML file via the plugin "Import / Export PCS 7" from PAA or the SIMATIC Manager. Then import the XML file that was generated by PAA or PCS 7 and proceed in the reverse order in SIMATIC Manager or PAA. Synchronization is also performed during an import. Then the alterations to the target can be deleted or applied. Note Security when performing data exchange via XML format Access to the transfer medium/transfer directory: When using the indirect data exchange via XML format between PAA and SIMATIC PCS 7, ensure that the transfer medium or the transfer directory of the XML files is only accessible to authorized persons. Digitally signed XML files: To describe the origin and integrity of the XML data, you can sign the XML file digitally during the data exchange in XML format. This corresponds to the requirements of the PCS 7 security concept. By checking the digital signature, you ensure that the XML file on the transfer medium has not been modified. The digital signature on the XML file is deactivated by default. Activating the digital signature is recommended. See also chapter Exporting digitally signed XML files: (Page 117). Note Note on file-based data exchange When using file-based data exchange, ensure that the sources for an import are trusted. Check that the files and data carriers are free from viruses and apply the usual security measures. To protect your data, make sure that the data carriers or folders are accessible to authorized persons only. Operating Manual, 01/2018, A5E AA 15

16 Overview of data exchange with PCS 7 Perform at least the following sequences to exchange engineering data between PAA and SIMATIC PCS 7: 16 Operating Manual, 01/2018, A5E AA

17 Overview of data exchange with PCS 7 Preparation 1. Prepare PCS 7 See chapter Requirements in PCS 7 (Page 19). 2. Preparing PAA Preparing the PAA engineering project See chapter Opening a planning project (Page 22). Creating the DCS structure See chapter Creating the DCS structure (Page 22). 3. Managing control module types in PAA Importing control module types in PAA See chapter Importing control module types (Page 28). Configure a mapping table for the control module types See chapter Configuring the mapping table of the signal designations (Page 109). Creating control module types in PAA See chapter Creating a control module type (Page 30). Engineering in PAA 1. Hardware engineering in the "Locations" tab See chapter Hardware engineering in the Navigator (Page 58). Configure the control cabinet Create and configure the station Set up and configure central and distributed I/O 2. Software engineering (DCS structure) in the "Units" tab See chapter Software engineering in the Navigator (Page 89). Signal engineering Implement channels See chapter Optional: Linking hardware and software: Implementing channels (Page 92). See chapter Working with channel requests (Page 90). This step links the hardware engineering and the software engineering. 3. Assigning control modules Editing software engineering using engineering tasks (Page 92) 4. Create or update symbol table See chapter Using symbol tables (Page 99). 5. Create interlock logic on function diagrams See chapter Engineering in the function diagram (Page 101). Operating Manual, 01/2018, A5E AA 17

18 Overview of data exchange with PCS 7 Finishing processes 1. Linking PAA attributes and PCS 7 attributes where applicable See chapter Linking attributes from PAA and PCS 7 (Page 109). 2. Exporting from PAA to PCS 7 See chapter Export from PAA to PCS 7 (Page 115). 3. Importing import from PCS 7 to PAA See chapter Import from PCS 7 to PAA (Page 125). Note Assigning exported objects When you export objects from PAA to PCS 7, perform the assignment in PCS 7 subsequently, if necessary. 18 Operating Manual, 01/2018, A5E AA

19 Requirements in PCS 7 5 Requirements for control module types In order to work with control modules in PAA, the following conditions must be met: The PCS 7 project is part of a multiproject The multiproject contains a master data library Master data library contains CMT Requirements for messages The following conditions must be met before you can import messages from a PCS 7 project: The message must be assigned to the block of a control module in PCS 7. The message must be assigned to the block of a control module or the block variable of a control module at the plant interface in PCS 7. Requirements for optional blocks (variants of control module types) The following conditions must be met before you can import optional blocks from a PCS 7 project: The block must be optionally assigned to a control module in PCS 7. The block must be assigned to a plant connection at the plant interface in PCS 7. The "Optional" option for this block must be activated. See also Preparations (Page 21) Operating Manual, 01/2018, A5E AA 19

20 Requirements in PCS 7 20 Operating Manual, 01/2018, A5E AA

21 Preparations Creating a new engineering project Procedure 1. Select the "File > Open project" command in the menu bar. The "Open project" tab opens. The table is based on a query. The query functions are available in the context menu of the column headers; for example, filtering and sorting functions. You can save these settings in your user settings. 2. At the top of the tab, select a project type from the following options: Option "Engineering" "Base objects" "Templates" Project type Engineering projects Base projects Template projects "System" System projects You will see all projects of the selected project type for which you have read rights. To open the shortcut menu, right-click in the table area. You usually create a new project of the "Engineering" type. 3. Select the "New > Project" command in the shortcut menu. The new project is created and the project properties open. 4. Enter a "Name" and a "Description" for the project in the "Project" category. By default, the "Type" of the project matches the option selected in the "Open project" tab. 5. Click the "..." button next to "Project structure". The "Select project structure for <project name>" window opens. 6. Select the node "X01 > X30 Project presetting, SIMATIC PCS 7 Plant Automation Accelerator" here. 7. Confirm your selection with "OK". You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Administration of projects and working layers". Operating Manual, 01/2018, A5E AA 21

22 Preparations 6.3 Creating the DCS structure 6.2 Opening a planning project Procedure 1. Select the "File > Open project" command in the menu bar. 2. Select a project. If the project has working layers, these are displayed toward the bottom of the tab. 3. Click the "Open" button. The project is loaded. If you are working with working layers, the released area of the project will be loaded. You can find more information on this topic in the "COMOS Platform Operation" manual, keyword "Working with projects". 6.3 Creating the DCS structure Introduction The plant hierarchy consists of hierarchy folders which can contain additional hierarchy folders, CFC/SFC charts, pictures, reports and additional documents. It represents the functional, hierarchical structure of the unit, regardless of the assignment to automation systems or operator control and monitoring systems. You can find more information on this topic in the PCS 7 documentation. Requirement The project presetting for SIMATIC PCS 7 is set in the product properties. See also chapter Creating a new engineering project (Page 21). Procedure 1. Select the "New > DCS structure" command from the context menu of the project node. The "DCS structure" node is created below the project in the Navigator. 2. Select the "TH hierarchy folder" command in the context menu of the "DCS structure" node. 3. Select the "TH hierarchy folder" command in the context menu of the "TH01 Hierarchy folder" node. 4. Create the required number of folders for each hierarchy level. The hierarchy can have up to eight levels. The command is grayed out in the context menu after the eighth level. 22 Operating Manual, 01/2018, A5E AA

23 Preparations 6.4 Standard ISA 88 in the unit structure Using the pipe sign " " A pipe sign " " can be entered in the name of a PAA object of the plant hierarchy. A pipe sign in the name has an undesirable effect on the creation of a SystemFullName. A SystemFullName is created from the name of the owner and its own name, whereby the components of the name are separated by a pipe sign " ". When there is a pipe sign in an object's name, the plant hierarchy determined based on the SystemFullName cannot be created correctly. Do not use the pipe sign " " in an object name. When names are created in scripts and for imports, do not use a pipe sign " ". 6.4 Standard ISA 88 in the unit structure Requirement The "DCS structure" node exists in the Navigator. A plant hierarchy has been created. See also chapter Creating the DCS structure (Page 22). Procedure 1. Open the first level of the plant hierarchy in the properties of a folder. 2. Select the "Attributes > Automation Interface" tab. 3. In the "S88 type definition" list, select the entry Process cell". 4. Confirm your entries. The icon and the description of the object change in the Navigator. 5. Open the second level of the plant hierarchy in the properties of a folder. 6. Select the "Attributes > Automation Interface" tab. 7. In the "S88 type definition" list, select the entry "Unit". 8. Confirm your entries. The icon and the description of the object change in the Navigator. 9. Open the 3rd level of plant hierarchy in the properties of a folder. 10.Select the "Attributes > Automation Interface" tab. 11.In the "S88 type definition" list, select the entry "EMOD". 12.Confirm your entries. The icon and the description of the object change in the Navigator. Operating Manual, 01/2018, A5E AA 23

24 Preparations 6.4 Standard ISA 88 in the unit structure 24 Operating Manual, 01/2018, A5E AA

25 Management of control module types Structure of control module types Requirement The planning project is open. See chapter Opening a planning project (Page 22). Operating Manual, 01/2018, A5E AA 25

26 Management of control module types 7.1 Structure of control module types Structure Permanent folder templates (PAA & COMOS) General collecting folder for all templates of the PCS 7 interface A collecting folder for enumerations types A collecting folder for templates (For example, CMTs or Functions) A collecting folder for Control modules and Variants A Collection folder for CMT group and variants, (For example Valve with feedback and Valve without feedback) CMT template Function diagram Control module type (CMT) Block of the control module type Command Message Messages have the following properties: They describe events for control modules. They are classified by the attributes "Message class", "Priority" and "Origin". They have a freely available "Event" field to describe the event. They have a freely available "Info text" field. Parameter or block variable of the control module Status Mapping table for linking PAA-specific attributes from DCS world with COMOS-specific attributes from Unit world 26 Operating Manual, 01/2018, A5E AA

27 Management of control module types 7.1 Structure of control module types Parameter or block variable of the control module Signal Channel request for the signal Optional blocks (variants) Optional blocks are used to define the minimum size and the maximum size of a control module type. The difference between these two states is mapped by the optional blocks. The objective is to define a control module type so that it can be used as a template for the various control modules that are similar in function. When creating the templates, decide which optional blocks to use. The blocks available for a control module can no longer be changed. The optional blocks are managed and identified as follows: <Project> 7 > Template-Container > CMTs > Control module type> > <Version of the control module type> The variables, together with all of the other control modules, are located in the Template- Container" node under CMT folder. Block (SubCM) in a version of the control module type: "Automation Interface" tab, "Optional" attribute is activated See also Importing control module types (Page 28) Managing variants using optional blocks (Page 29) Operating Manual, 01/2018, A5E AA 27

28 Management of control module types 7.2 Importing control module types 7.2 Importing control module types Requirement The project is open. See chapter Opening a planning project (Page 22). The structure of control module types is clear. See chapter Structure of control module types (Page 25). Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. The "Import / Export PCS 7" plugin opens. 2. Select the "Import" tab. See also chapter "Import" tab (Page 145). 3. Select the file type of the import file: The "PCS 7 project" option: s7p The "XML file" option: xml Recommendation: When you export an XML file, also activate the "XML signature" option. The import expects that a signed XML file is to be transferred. See also chapter Importing digitally signed XML files (Page 126). 4. In the "PCS 7 project path / XML path" list, select the source project for the import. 5. Select the "Library > CM types" option in the "Filter" control group. The "Confirm import of control module library" message is displayed. 6. Deactivate all other options in the "Filter" group. 7. Click on the "Import" button. The "Data transfer - Generate/import" dialog opens. See chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 8. Click on the "Import objects from B to A" button in the "Data transfer - generate/import" dialog. Result The library with the control module types is imported into the PAA project and displayed in the "Units" tab as follows: Node "@Template 7 > Template-Container > CMTs > <Name CMT> Type/Variants collection" You then have the option of editing the imported control module types and exporting the changes to PCS 7. The control module is automatically placed on the function diagram, which is created in node. 28 Operating Manual, 01/2018, A5E AA

29 Management of control module types 7.3 Managing variants using optional blocks 7.3 Managing variants using optional blocks Requirements Control module types with subordinate control modules have been created. The subordinate control modules are marked as optional. See also chapter Creating control modules (Page 33) and chapter Importing control module types (Page 28). The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). Target Generating versions for templates from which the control modules are derived. Creating templates with variants 1. Select the control module type in the "Type library" column. 2. Open the shortcut menu and select the New variant" command. When the shortcut menu command is disabled, you have not defined optional modules at the CMT or you have already created all possible variants. 3. Expand the structure below the control module types. 4. Select the newly created version. 5. Select the underlying control modules that this version should contain in the "Type structure" column. 6. Confirm your entries. Result The control module type versions are created in the "Units" tab: 7 > Template-Container > CMTs > <CMT> Type/variants collection > <CMT_Var1 >" Note Automatic changes to variants Structural changes to control module types are automatically written to the variants. See also Engineering in PAA (Page 51) Operating Manual, 01/2018, A5E AA 29

30 Management of control module types 7.5 Creating a control module type 7.4 Synchronizing CM variants Objective: Import an instance from PCS 7 to PAA for which no suitable variant exists in PAA Variant is generated in the PAA library Naming: NameMaster#No Instance is created in PAA / existing instance is updated General If this is a new CM for PAA, it is displayed in green and imported directly without deleting the old CM. In order to avoid data loss, click "Delete at Target" to start the import, and a new working layer is created. To open the user interface, open the plugin "Type re-assignment". You can work by using drag&drop. Procedure 1. Drag a type from the navigator, "@Template" folder, into the field "Type selection > Types". 2. Drag a PH from the navigator, "DCS Structure" folder, into the "Start object" field. 3. "Find" 4. Drag a new type from the navigator, "@Template" folder, into the "New CMT" column. 5. Execute: Instances gain or lose SubCMs due to their status in comparison to the type to which they were assigned. The log window is updated with all the information about the types that have been assigned. 6. When the Function diagram is opened, all the lost connections are shown, and the CMs have correct types assigned with correct sub-control module and correct variant settings. 7.5 Creating a control module type Requirement The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). 30 Operating Manual, 01/2018, A5E AA

31 Management of control module types 7.6 Creating control variables Procedure 1. Select the "Insert new object > Control module type" command in the menu bar of the plugin. The shell for a control module type is created in the "Type library" column. The name of the newly created shell is "CMT_<consecutive number>". If no project has been created yet, a project is created. Any existing CMTs are listed. 2. Define the details of the control module type in the "Type attributes" column. If you have created a new control module type, the "Name" field is selected automatically. 3. Right-click on the shell of the CMT in the "Type structure" column and select the "Insert new object > <desired object>" command in the context menu. 4. Save your entries. Result The control module type is created in the "Templates" node and is displayed in the "Type configurator" plugin. The control module type is only a shell. In PCS 7, you assign the connections and messages of the component to this control module type. Note Editing control module types Edit control module types only via the "Type configurator" plugin. Changes in the navigator are not applied in the plugin. See also Management of control module types (Page 25) 7.6 Creating control variables Requirements You use control variables for configuring parameters and for external interconnections. The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). A control module has been created. See also chapter Creating a control module type (Page 30). Operating Manual, 01/2018, A5E AA 31

32 Management of control module types 7.8 Creating messages Procedure 1. Right-click on a control module in the "Type structure" column and select the "Insert new object > <Parameters>" command in the shortcut menu. 2. Define the details of the control variables in the "Type attributes" column. 3. Save your entries. Note User can only select valid values when creating a BOOL data type parameter for IN and INOUT "IOType". Text 0 / Text 1 The attributes are, for example, used in WinCC, in order to define interlock messages. If you create a parameter of the BOOL data type, the attributes Text 0 and Text 1 are available to you. If you select another data type, the Text 0/Text 1 attributes cannot be edited. You can still edit the combo box value. If there is no Text 0, Text 1 and enumeration then true/false selection is shown. If user changes data type to BOOL then the value is not changed, but the combo box list with true/false is available. To edit the attributes later, open the parameter properties from the Navigator. Select the "Attributes > Automation Interface" tab. It is possible to edit both the attributes. If you wish to define the attribute Text 0 or Text 1 to a type (CMT), they are also displayed on the instances. 7.7 Transfering LowScale/HighScale/Unit between PAA and PCS 7 Procedure Transfer the LowScale / HighScale / Unit values from the Unit tree via DCS tree into CM in PCS 7. LowScale/HighScale/Unit are located at a Signal below the CM. 7.8 Creating messages Introduction A control module can distribute messages. These are reported in the visualization system, for example WinCC. 32 Operating Manual, 01/2018, A5E AA

33 Management of control module types 7.9 Creating control modules Requirements The "Type configurator" plugin is open. See also section Opening the "Type configurator" plugin (Page 43). A control module has been created. See also section Creating a control module type (Page 30). Procedure 1. Right-click on a control module in the "Type structure" column and select the "Insert new object > Message" command in the context menu. 2. Define the details of the message in the "Type attributes" column. 3. Save your entries. Result The message has been created. When you transfer the messages to PCS 7, you configure the block allocation and the message identifier later in PCS Creating control modules Requirement The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). You have created a control module type. See also chapter Creating a control module type (Page 30). Procedure 1. Select the control module type in the "Type structure" column. 2. Open the context menu and select the "Insert new object > Control module" command. 3. Define the details of the control module in the "Type attributes" column. 4. To label the control module as optional, activate the "Optional" option in the "Type attributes" column. See also chapter Managing variants using optional blocks (Page 29). 5. Create the desired objects underneath the control module. To create messages, commands, and statuses, proceed as described for the control modules. See also chapter Management of control module types (Page 25). 6. Save your entries. Operating Manual, 01/2018, A5E AA 33

34 Management of control module types 7.10 Creating a CM in the DCS structure Note Editing control module types Edit control module types only via the "Type configurator" plugin. Changes in the navigator are not applied in the plugin. See also "Type configurator" reference plugin (Page 150) 7.10 Creating a CM in the DCS structure Requirement The DCS structure has been created. See also chapter Creating the DCS structure (Page 22). Procedure 1. Open the properties of the CMT template in the DCS structure you want to link. 2. Select the "Tasks > SW interface" tab. 3. Check if the "Copy in template" task is displayed and create it, if needed, using the shortcut menu command "New > Copy in template". 4. Navigate to the CMT template. 5. Drag&drop the CMT template from the Navigator into the "CM/EM type" column in the "SW interface" tab of the hierarchy folder. 6. Click the "Execute (selected)" button in the menu bar of the tab. 7. Confirm your entries. 8. Repeat the above steps for each additional CMT template that you want to link to the DCS structure. You have the option of linking the CMT templates to the DCS structure in bulk. Linking a CM with position using a unit pointer 1. Select the CM. 2. Open the properties of the CM. 34 Operating Manual, 01/2018, A5E AA

35 Management of control module types 7.11 Creating aggregated CMTs 3. Select the "General" tab. 4. Drag&drop the desired position from the unit structure into the "Unit" field. Note Setting unit pointers in bulk A query is prepared under the "DCS structure" node which you can use to set the unit pointers in bulk. See also chapter Configuring the mapping table of the signal designations (Page 109) Creating aggregated CMTs Introduction The aggregated CMT consists of individual control module types that are combined to build a CMT combination for a closed-loop control, for example. These can then be used in the project and do not have to be built individually. Requirement Multiple CMTs are created. See also chapter Creating a control module type (Page 30). Type configurator plugin is opened. Procedure 1. Select the "Insert new object > Aggregated CMT" command in the "Type library" coloumn of the "Type configurator" plugin. The shell for an aggregated CMT is created in the "Type structure " column. The name of the newly created shell is "Aggregated CMT_<consecutive number>". The "Aggregated CMT template" object and below it a function diagram are created in the "Type structure" column. 2. Define the details of the aggregated CMT in the "Type attributes" column. If you have created a new aggregated CMT, the "Name" field is selected automatically. 3. Repeat steps 2 and 3 for all Aggregated CMTs that you want to add to the CMTs. Operating Manual, 01/2018, A5E AA 35

36 Management of control module types 7.12 Working with negations 4. Optional: Open the function diagram below the "Aggregated CMT template" object. Place the CMTs from the collection on the function diagram and connect the CMTs to each other. You have the option to place functions on the function diagram. Note 5. Optional: No exchange with PCS 7 Aggregated CMTs do not participate in data exchange with PCS 7 and are not exported. To transfer the aggregated CMT template to PCS 7, use the object in the DCS structure via the "Copy template" task in the properties of the folder in the DCS structure. See also chapter Creating a CM in the DCS structure (Page 34). Note Updating the collection If you make changes to a CMT in PCS 7 or in the "Type configurator" plugin and this CMT is part of the collection, update the CMTs afterwards using the "Assembly updater" plugin. The instances of CMTs are also updated within this context. See also chapter Update type usages (Page 96) Working with negations Note Negation in PCS 7 is only possible at inputs Negations in PCS 7 are only available at interconnected inputs. The "Negation" attribute is only possible for the "BOOL" data type input parameter and is deactivated for output parameters. For input parameters, the "Negation" attribute is based on parameter switching or the signal. In PAA, negations can be used at inputs and outputs. The negations at the outputs cannot be exported to PCS 7. As such, in the function diagram properties, in the tab "Attribute > System data" in the control group "Settings", the "Mode function diagram" list, in which you can adjust as to whether you wish to work according to the PCS 7 specifications. Requirement A function diagram is open. In the function diagram properties, the entry "PCS 7" is selected in the tab "Attributes > System data" in the control group "Settings" in the list "Mode function diagram". Types have been placed on the function diagram and are connected. 36 Operating Manual, 01/2018, A5E AA

37 Management of control module types 7.12 Working with negations Procedure 1. Select the connection at a type input. 2. The connection is displayed in magenta. 3. Select the "Settings > Signal is negated" entry in the context menu. 4. Confirm your entries. Example See also Using references (Page 38) Operating Manual, 01/2018, A5E AA 37

38 Management of control module types 7.13 Using references 7.13 Using references Definition The reference in PAA corresponds to the reference to a parameter of a control variable in PCS 7. To prepare connections to other blocks, textual references are used. These can be connections that are planned for the future or connections to blocks that must be removed for editing. We distinguish between the following types of references: Global variable reference Connection to data blocks Block variable reference Connections to CFC block connections, that are not defined in the "Type configurator" plugin or in the technological editor for the exchange between PAA and PCS 7 Textual reference Connection to control variables, that are not defined in the "Type configurator" plugin or in the technological editor for the exchange between PAA and PCS 7 Requirement A function plan is open for editing. A block is placed, whose parameter you wish to link to the parameters of another block. Procedure 1. Drag&drop the reference from the toolbar onto the function diagram. The reference object is created in the Navigator below the function plan. 2. Connect the reference to the input parameter of the placed object. 3. To mark the reference, click once on the symbol of the placed reference. The selected reference is highlighted in magenta. 4. To define the type of reference, in the context menu, select the command "Reference type > <requested type>". A textual reference is created by default. 38 Operating Manual, 01/2018, A5E AA

39 Management of control module types 7.13 Using references 5. To input the path of the block that you wish to reference, select one of the following options here: To accept the absolute path in a control variable present in PAA, select a control variable in the navigator and pull the symbol of the reference to the function plan via Drag&Drop. Adjust the path so that it corresponds to the desired reference: Example for the syntax of a textual reference with unit hierarchy: PCS 7 Project name \Hierarchy path\cm.cv Example for the syntax of a global variable reference with unit hierarchy: Name of the global DB.ElementName Example for the syntax of a block variable reference with unit hierarchy: PCS 7 Project name\\hierarchy path\\blockname.blockvariable To enter the path of the reference manually, click twice in a row on the descriptive text in the symbol of the placed reference. The text field is activated for editing. Enter the path. You can enter a relative or an absolute path. As such the syntax from PCS 7 applies: (Plan\block.connection) with TH-path (if available). Further information on this topic can be found in the "CFC for SIMATIC S7 (V9.0)", keyword "Reference at the parameter of a control variable" manual. 6. To close a reference, select the symbol of the reference and in the context menu, select the command "Close reference". If PAA finds the referenced block and the reference can be closed, a connection is made from the textual reference. 7. Confirm your entries. Importing textual references If you import the textual references from PCS 7 and have already placed the corresponding block on a function plan, the textual references are also displayed on the function plan following reengineering. In the Navigator, the textual references are underneath the function plan. Operating Manual, 01/2018, A5E AA 39

40 Management of control module types 7.13 Using references 40 Operating Manual, 01/2018, A5E AA

41 Management of enumerations Creating enumeration types Note Working with central enumeration types If you wish to work with a central enumeration library, create this in the base project. Export the enumeration types by means of the XML export and then import these into your engineering project. You can define further enumeration types in the engineering project. Requirement The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). Procedure 1. Select the "Insert new object > Enumeration" command in the menu bar of the plugin. The shell for an enumeration is created in the "Type library" column. The name of the newly created shell is "Enumeration_<consecutive number>". The enumeration is displayed in the "Type structure" column. If no project has been created yet, a project is created. Any existing enumerations are listed. 2. Define the details of the enumeration type in the "Type attributes" column. If you have created a new enumeration type, the "Name" field is selected automatically. 3. Right-click on the enumeration in the "Type structure" column and select the "Insert new object > Value" command in the context menu. 4. Save your entries. Result The enumeration type is saved in the node "@Template 7 > Shared declarations> Enumeration types". To then be able to use the enumerations on other types, the enumeration types are also stored in the "Y10 > M40> A10 > Y10M40N00012 Enumeration types" standard table. See also chapter Using enumerations (Page 42). Operating Manual, 01/2018, A5E AA 41

42 Management of enumerations 8.2 Using enumerations 8.2 Using enumerations Requirement You have created at least one enumeration type. See also chapter Creating enumeration types (Page 41). You have created one CMT with a parameter and wish to use an enumeration here. See also chapter Creating a control module type (Page 30). Parameter and/or setpoint have the data type INT, DINT, BOOL, BYTE, WORD or DWORD. The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). Procedure 1. Select the CMT on which you wish to use the enumeration in the "Type library" column. Select the desired parameter in the "Type structure" column. 2. Select the field "Enumeration" in the "Type attributes" column. 3. Select an enumeration from the list. 4. Select the field "Value" in the "Type attribute" column. 5. Select a value from the list. 6. Confirm your entries. Editing the use 1. To change the usage of an enumeration on a parameter, open the parameter properties. 2. Select the "Attributes > Automation Interface" tab. 3. Edit the attributes "Enumeration" and "Value". 4. Confirm your entries. 42 Operating Manual, 01/2018, A5E AA

43 "Type configurator" plugin Objective of the type configurator The type configurator is used for the large-scale creation of CMT as well as variant handling. 9.2 Opening the "Type configurator" plugin Requirements An engineering project project is open. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Type configurator" command. 9.3 Creating a global command and status library Introduction The command and status library provides you with the most common commands and statuses for equipment modules. You can expand the library in the base objects. Requirement The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). Procedure Click the "Create command and status library" button in the menu bar of the plugin. Result Two new folders "Commands" and "Statuses" are created in the "Templates" node. In the "Commands" folder some command objects are created and in the "Statuses" folder some status objects are created. You have the option to use these commands and statuses, for example, in a step sequence. See also chapter "Type configurator" reference plugin (Page 150). Operating Manual, 01/2018, A5E AA 43

44 "Type configurator" plugin 9.5 Aggregated CMTs 9.4 Large-scale operations Objective Creation of N elements from the following list: Control module Parameter Signal Message Status Command or values at CMT Function or enumeration Procedure 1. Select an element in the "Type library column" of the type configurator 2. Right-click the element or a subelement in the Type structure column and select "Create N" 3. Select the desired object type 4. Enter a number. In addition, you have the option of copying and removing via multiple selection. 9.5 Aggregated CMTs Aggregated CMTs can be created within the type configurator. Procedure Note User actions in the navigator in folder result in data inconsistency Objects under folder may not be modified in the Navigator. These manipulated CMTs generate inconsistent CMTs under the aggregated CMTs. This inconsistency cannot be repaired by the type configurator. An inconsistent state is indicated by the fact that the type configurator is no longer initialized. Undo the actions that you carried out in the navigator 1. Click "Insert new object" in the "Type library" column and select the desired type 2. Use drag&drop to assign the CMT to the aggregated CMT (drag from the "Type library" column into the "Type structure" column) The name can be adapted at copied CMTs 44 Operating Manual, 01/2018, A5E AA

45 "Type configurator" plugin 9.8 Creating functions 9.6 Variant overview You have the possibility to obtain a graphical overview of all the variants of a CMT. Proceed as follows to do this: 1. Open the "Type configurator" plugin 2. Open the "Variant overview" 9.7 Graphical properties The representation of the graphical properties on the Function diagram can be adapted for the following objects: CMT Functions Procedure 1. Open the "Type configurator" plugin. 2. Open the "Graphical properties" button. You can select all the types of an object type or of a specific instance in the "Type library". 3. The adaptations only affect the selection. 9.8 Creating functions Introduction Functions can be used on the function plan like standard logic blocks. If you wish to work with functions on the function plan, drag&drop these from the "@Template" node to the function plan. Note Task objects belonging to the functions When you place a function on the function plan, a task object is automatically created in the Navigator. These tasks are included in the evaluation for queries. Requirement The type configurator plugin is open. See also chapter Opening the "Type configurator" plugin (Page 43). Operating Manual, 01/2018, A5E AA 45

46 "Type configurator" plugin 9.9 Configuring messages Using predefined function blocks 1. Click the "Functions" button in the menu bar of the plugin. The "Functions" column is displayed. 2. Select the desired functions. 3. Click the "Generate functions" button. The selected functions are created in the > PCS 7 > Template-Container > Functions" node and displayed in the column "Type library" of the plugin. 4. Select a function in the "Type library" column. 5. Select a parameter in the "Type structure" column. 6. Edit the properties of the parameter in the "Type attributes" column. The Text 0/Text 1 attributes are only available on the BOOL type parameters. 7. Confirm your entries. 8. Repeat steps 4 to 7 for all the parameters to be edited. Creating new function blocks 1. Select the "Insert new object > Function" command in the menu bar of the plugin. The function is created in the "Type library" column. The name of the newly created function is "Function_<consecutive number>". The function is displayed in the "Type structure" column. 2. Select the function in the "Type structure" column. 3. Select the "Insert new object > Parameter" command from the shortcut menu. 4. Edit the properties of the parameter in the "Type attributes" column. The Text 0/Text 1 attributes are only available on the BOOL type parameters. 5. Confirm your entries. 6. Repeat steps 3 to 5 for all the parameters to be created. See also "Type configurator" reference plugin (Page 150) 9.9 Configuring messages You can configure the message types. The associated data can be found in the database as follows: Name of the message type Y10 M40 A10 Y10M40N00005 Name of the message class Y10 M40 A10 Y10M40N00015 Abbreviation for group display Y10 M40 A10 Y10M40N Operating Manual, 01/2018, A5E AA

47 "Type configurator" plugin 9.9 Configuring messages In addition, five new attributes are available for messages. These are available at the Y Messages" object on the "Automation Interface" tab: Single acknowledgement Trigger action Batch ID OS area With acknowledgment Procedure 1. Click the "Configure message system" button in the type configurator 2. Edit the data in the table You can edit several cells of a column simultaneously by using multiple selection Data transfer The "Message classes" check box has been added to the data transfer dialog. The message classes are displayed and also transferred after the check box has been activated. Operating Manual, 01/2018, A5E AA 47

48 "Type configurator" plugin 9.9 Configuring messages 48 Operating Manual, 01/2018, A5E AA

49 Using "Excel import" 10 Introduction You can use the "Excel Import" plugin to import the plant hierarchies, CMTs and signals. The import of hardware is optional. Note Hardware import If you do not import the hardware, the signals on the IO channels will not be implemented. Requirement The Signallist.xls file exists and is complete. The BCM.Lib.xls file exists and is complete. Alternatively, you can use your own Lib files. Use the query provided to collect the CMT signals. Note Editing Excel lists When editing Excel lists, take care not to delete or rename any columns. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Excel Import" command. The Excel import" plugin opens. 2. Click the "..." button next to the field Select Excel import file. A window opens. 3. Select the signal list. By default, the list is located in the folder "C:\ProgramData\Siemens\PCS 7 Plant Automation Accelerator\Excel" after installation. Only use the signal list provided. 4. Confirm your entries. 5. Select the Signal list entry from the "Excel worksheet" list. 6. Enter the row from which the Excel worksheet should be read into the Start row field. 7. Click the "..." button next to the Select library file" field. A window opens. 8. Select the required library. By default, the list is located in the folder "C:\ProgramData\Siemens\PCS 7 Plant Automation Accelerator\Excel" after installation. Operating Manual, 01/2018, A5E AA 49

50 Using "Excel import" 9. Confirm your entries. 10.Use drag&drop to move the object from the Navigator to the "Start object" field under which you want to save the imported objects. For example, the object DCS structure". 11.Click on the "Import" button. Result The CMTs, hardware and signals stated in the signal list are created. See also Excel import" reference plugin. (Page 152) 50 Operating Manual, 01/2018, A5E AA

51 Engineering in PAA Transfer of logic blocks Note Data loss when using standard logic blocks - defective data transfer The logic blocks used in COMOS are no longer used in PAA. The logic blocks available on the Function diagram can therefore be not used. Instead, use the following procedure via functions. When importing a standard function from PCS 7 to PAA for which there is no function type in the PAA library, the function type is created automatically and saved in the library. The instance is then created with the automatically created function type. This scenario contains CM when importing from PCS 7 to PAA with logic blocks. List of objects: "ABS", "ADD", "AND", "DIV", "EQ", "GE", "GT", "LE", "LT", "MUL", "NAND", "NE", "NEG", "NOR", "NOT", "OR", "SQRT", "SUB", "XOR" Procedure 1. The logic blocks can be imported from PCS 7 into PAA without explicitly creating function types. The function type is created automatically and saved in the library. 2. After the import, a function type is created in the "Type Configurator" and can be repeatedly used. 3. The function is placed under the CM. 4. When exporting out of PAA, the functions are already under the CM. Only the functions under the "@Template" folder are supported Adapting the assignment of the right-hand mouse button 1. Click "Open project" 2. Select your project, right-click "Properties > Edit " 3. Select "Customer settings > Select version PAA" 4. Deselect / select the required options. Result During project design in the project the right-hand mouse button shows all the objects of the selected versions. Operating Manual, 01/2018, A5E AA 51

52 Engineering in PAA 11.4 Information on identifying hardware components 11.3 Functional characteristics of the hardware objects My Documentation Manager provides you with an Excel list in which you can see the application cases on which the individual hardware base objects are modeled. For example, whether it is exchanged via the AI or whether it is placed in the cabinet design. For more information on hardware objects, refer to the "Manufacturer_devices_PA_Accelerator*.xlsx" list in the PAA Setup. Available HW modules For more information on available HW modules, refer to the "Manufacturer_devices_PA_Accelerator*.xlsx" list in the PAA Setup. See also Excel list of the hardware objects ( Information on identifying hardware components Objective All hardware components that are imported or exported through the PCS 7 interface must receive a unique description both in PAA and in PCS 7. The data can only be assigned automatically during import or export if they have unique descriptions. A comparison of the identification fields of PAA and PCS 7 The hardware components are identified using the "Name" and "Article number" fields. In PAA, the properties "Name" and "Article number" are generated according to rules that differ from PCS 7. PAA rule PCS 7 rule (as per HW Config) Name Sequential number Number according to slot rules. Article number Randomly selectable article number Slot number of the module in the rack or distributed I/ O. See the description on "Basics of slot rules in PCS 7" below. Machine-readable serial number (MLFB) of the manufacturer. Example: "6ES XT05-0AB0" The objects are initially created based on the PAA rules in PAA. To export objects to PCS 7, they must first be renamed in accordance with the PCS 7 rules. 52 Operating Manual, 01/2018, A5E AA

53 Engineering in PAA 11.4 Information on identifying hardware components Basics of slot rules in PCS 7 Both the slot rules of the rack and the connection rules of the bus system are important for the identification of a hardware component in PCS 7. As a general rule, SIMATIC controls are structured as follows: Structure of the rack according to the slot rules of HW Config: Bus address The power supply, the CPU and the input/output modules are plugged into the rack. The bus address must be entered in the PAA object and be unique on the bus. Example: A "1" is entered for the power supply. Connections according to the connection rules of the bus system: Addresses of inputs and outputs The bus system is connected to the CPU or a communication processor (CP). The addresses are managed in blocks of 8 and written with the notation "Byte.BIT". The value ranges from 0 to 7. The y position is incremented first, then the x position. Example: The addresses for a digital input module with 24 inputs range from I0.0 to I2.7. Note Special rule for UR2H racks With UR2H racks, all modules on the entire station are placed on one rack. This UR2H rack is only divided into two areas electrically; the slots themselves provide space for two CPUs. For this reason, the UR2H racks are not transferred to PAA as two racks with slots 1 to 9, but as one rack with slots 1 to 18. This means that the first half of the slots are intended for the first CPU, and the second half for the second CPU. Accordingly, you have to match the slot numbers yourself with the UR2H racks. Standard check when exporting from PAA to PCS 7 When exporting the hardware configuration: The configured components are identified using the "Name" and "Article number" attributes. Note Checking the slot rules of HW Config The content of the "Name" attribute is initially checked in the Automation Interface. In the event of an error, the following message appears: "The value of the "Name" attribute violates a slot rule of HW Config." Standard check when importing from PCS 7 to PAA When re-engineering, the hardware configuration applies to the import: The configured components are identified using the "Article number" attribute and assigned to the base objects in PAA. See also Overview of data exchange with PCS 7 (Page 15) Operating Manual, 01/2018, A5E AA 53

54 Engineering in PAA 11.6 GSD 11.5 Available HW modules Reference For more information on available HW modules, refer to the "Manufacturer_devices_PA_Accelerator*.xlsx" list in the PAA Setup GSD GSD information The transfer of GSD information is possible The following application cases are possible with PAA: Device with the associated GSD information is placed and assigned parameters; is transferred After the export to PCS 7, the device has to be placed and assigned parameters in the HW configuration Objective and performance scope of the interface Objective You have the possibility of importing GSD files and automatically creating a base object structure under a desired node from this interpretable device description. The created structure describes the possible slots and module configurations of the devices as a COMOS base object structure with elements per slot and module. When the elements and slots have been assigned, you can create the specific device structure in the Navigator under the device by using the context menu. Note GSDML not supported The GSDML format is not supported. Performance scope of the interface Finding suitable devices for the functional requirements Providing information on the properties of the selected measuring device Setting parameters and configuration for a device Documenting the selected properties of a device 54 Operating Manual, 01/2018, A5E AA

55 Engineering in PAA 11.6 GSD Deciding which signals are made available by a modular device Deciding which manufacturer device is used and direct access to the correct GSD file Providing the information on the configuration of the modular devices in the plant documentation Defining and documenting the I/O assignment of a modular device Providing the information on the implementation of the devices in the DCS system Plugins The following plugins are available to you in the menu "Plugins > Automation > GSD interface": Plugin Description "Import GSD files" See also chapter Importing GSD files (Page 55). "Assign GSDs" See also chapter Assigning GSD objects (Page 56) Importing GSD files Introduction The data is imported into the project that is open when the plugin is started. If an engineering project is open, the data is created as local base objects and can only be used in this project. If you want to use the data in more than one project, open the base project before you open the plugin. Requirement The project into which the data is to be imported is open. The GSD files are stored locally or you have the access data for Web access at hand. Procedure 1. If you do not want to import the data into an existing node in the base objects, create the node. 2. Select the "Plugins > Automation > GSD interface > Import GSD files" command from the menu bar. The plugin opens. The "Select target" tab is enabled. 3. Select the node in the displayed base object structure under which the data is to be imported. 4. Click "Next". 5. Select the desired source for the import. 6. Click "Next". Operating Manual, 01/2018, A5E AA 55

56 Engineering in PAA 11.6 GSD 7. Select one of the following options: To import GSD files from the Internet, enter your access data. Click the "Add URLs..." button. Copy the desired URLs to the "Add URLs" window. Confirm your entries. To import GSD files that are stored locally, click the "Add files..." button. Select the desired file. Click "Open". Repeat the last two steps for each additional file that you want to import. 8. Click the "Import" button. Result The files are imported and the objects are created under the specified base object nodes Assigning GSD objects Introduction You have the possibility of creating objects from the "Plants" tab in the Navigator as an Implementation on the "Locations" tab. You can make the imported GSD objects available as elements at the implementation. Requirement GSD data has been imported. See also chapter Importing GSD files (Page 55). Objects with the attribute "PMD.PMD_ACF864_001_000" or "Y30T00001.GSDFile" are available in the plant structure. Objects with this attribute are available, for example, on the "Base objects" tab under the nodes > A20 > A10 > A20 > A10 > A10 > A20 > A10 > A40 > A10 Interface modules" and > M41 > B20 PIA LCM device requirements". Only these objects are evaluated. Procedure 1. Select the "Plugins > Automation > GSD interface > Assign GSDs" command from the menu bar. The plugin opens. The most recent selection of the start object and destination is saved and automatically set. 2. Drag&drop the base object under which the GSD structure lies into the "GSD source" field. 3. In order to find the assignable objects, click the "Find assignable devices" button in the menu bar of the plugin. All the field devices found under the start object are listed. The "Unit object" column shows the objects which has one of the required attributes. If an implementation already exists for the plant object, the row in the table is write-protected. 56 Operating Manual, 01/2018, A5E AA

57 Engineering in PAA 11.6 GSD 4. Deselect the objects in the first Objects column that you want to assign at a later point. 5. If a GSD base object structure exists, you can select the uppermost node of the base object structure in the "GSD file" column. 6. Click the "Assign" button. Result The field devices are assigned to the GSD objects on the "Locations" tab in the Navigator. If the GSD object was not already placed on the "Locations" tab, it is placed and implemented automatically. If the attribute GSD download path (GSDUri) exists and no GSD base object is found, two buttons are displayed. Using these buttons, you call the "Import" plugin or open the Website for downloading the files. So you can use direct information from PIA LCP and must not search for it. Operating Manual, 01/2018, A5E AA 57

58 Engineering in PAA 11.7 Hardware engineering in the Navigator 11.7 Hardware engineering in the Navigator Creating the new physical structure via Right mouse click Procedure 1. Select the "New > desired objects" from the context menu of the profile rail as shown in the image below. Note The right mouse structure is only located under the rail/rack, not at the terminal modules or interface module. 2. Call a script via right mouse at the slave object and create additional objects. "Create bus modules" is added to the menu at the slave. Note If script is executed, the additional objects are created in the correct structure. 58 Operating Manual, 01/2018, A5E AA

59 Engineering in PAA 11.7 Hardware engineering in the Navigator The structure will be identical to the structure in the cabinet. Note If there is space between the slots (e.g slot 4 and next module slot 7), then empty bus modules are created between the modules. Operating Manual, 01/2018, A5E AA 59

60 Engineering in PAA 11.7 Hardware engineering in the Navigator PROFINET and PROFIBUS You have the option of using both PROFIBUS and PROFINET. Only PROFINET is mentioned in the examples in the following sections. Notes on PROFINET Just like with PROFIBUS, the bus nodes are connected to their master with the "Assign fieldbus" and "Assign to redundant fieldbus" tasks. In addition to the functional assignment, you have the option to perform an MRP configuration. To do this, use the following attributes in the "Attributes > Automation Interface" tab: "MRP domain" "MRP role" "MRP diagnosis" To use the MRP protocol, make the connections of the manufacturer devices in the desired order. 60 Operating Manual, 01/2018, A5E AA

61 Engineering in PAA 11.7 Hardware engineering in the Navigator Example The following example shows the associated connections of the manufacturer devices in PAA. Operating Manual, 01/2018, A5E AA 61

62 Engineering in PAA 11.7 Hardware engineering in the Navigator 62 Operating Manual, 01/2018, A5E AA

63 Engineering in PAA 11.7 Hardware engineering in the Navigator The example looks like this in the Topology editor of PCS 7: Configuring a SIMATIC station Requirement The "Locations" tab is displayed in the Navigator. A plant has been created. Creating a SIMATIC station 1. Select the object "Plant > Building > Floor, level > Room, Control center". 2. Select the "New > Cabinet" command from the context menu of the room. The cabinet is created below the room. 3. Select the "New > Station > <required station>" command in the context menu of the cabinet. The station is created below the cabinet. Operating Manual, 01/2018, A5E AA 63

64 Engineering in PAA 11.7 Hardware engineering in the Navigator Equipping a SIMATIC station with hardware 1. Select the station in the Navigator. 2. Select the "New > > Rack <required rack>" command in the shortcut menu of the station. The rack is used to mount the assemblies. 3. Select the required power supply under "New > Power supply" in the shortcut menu of the rack. 4. Select a central processing unit (CPU) under "New > Central processing units" in the shortcut menu of the rack. Each central processing unit is equipped with at least one submodule. The submodule is created automatically in addition. See also chapter Configuring the central processing unit (CPU) (Page 64). Depending on the central processing unit: Create further modules under the CPU if required; for example, an interface module for a bus system. 5. Select an input module from one of the following folders under "New" in the shortcut menu of the rack: "Digital electronic modules" "Analog modules" "Communication" "Function modules" 6. Select an output module corresponding to the input module from one of the following folders under "New" in the shortcut menu of the rack: "Digital electronic modules" "Analog modules" "Communication" "Function modules" 7. If necessary, assign the rack to the location where it should be assembled. See also Equipping interface modules with I/O modules (Page 66) Configuring the central processing unit (CPU) Requirement A SIMATIC station has been created and equipped with hardware. In the rack, at least one central processing unit (CPU) is created. See chapter Configuring a SIMATIC station (Page 63). The "Locations" tab is displayed in the Navigator. 64 Operating Manual, 01/2018, A5E AA

65 Engineering in PAA 11.7 Hardware engineering in the Navigator Procedure 1. Select the central processing unit (CPU) in the Navigator. 2. Open the properties of the central processing unit (CPU). 3. In the "Name" field, enter the value in accordance with the slot number of the CPU in the rack. The slot number of the CPU depends on the number of power supply slots. If the power supply uses only one slot, enter the value "2", else, if the power supply uses two slots, enter the value "3". See also Information on identifying hardware components (Page 52) Creating an interface module as distributed I/O (Page 65) Creating an interface module as distributed I/O Requirement A SIMATIC station with a CPU and bus system has been created. See chapter Configuring a SIMATIC station (Page 63). The "Locations" tab is displayed in the Navigator. Procedure 1. Select the "Plant" engineering object. 2. Select the "New > Field location" command from the context menu of the object. The field location is created below the object. 3. Select the "New > Decentralized periphery > <desired object>" command from the context menu of the field location. For example, select "New > Decentral periphery > ET200M". See also Equipping interface modules with I/O modules (Page 66) Assigning a field bus to a DP slave via a task (Page 71) Operating Manual, 01/2018, A5E AA 65

66 Engineering in PAA 11.7 Hardware engineering in the Navigator Equipping interface modules with I/O modules Requirement The interface modules have been created as distributed I/O. See chapter Creating an interface module as distributed I/O (Page 65). The "Locations" tab is displayed in the Navigator. Procedure 1. In the Navigator, select the interface module of the distributed I/O. For example: "Plant > Field location > (Interface module)" 2. Select "New > Mounting rails > <desired mounting rails>" in the shortcut menu of the interface module. 3. Select the required power supply under "New > Power supply" in the shortcut menu of the mounting rail. 4. Select the required module under "New > Interface modules" in the shortcut menu of the mounting rail. 5. Select an input module from one of the following folders under "New" in the shortcut menu of the rack: "Digital electronic modules" "Analog modules" "Communication" "Function modules" To do this, select a module marked with "I". 6. Select an output module corresponding to the input module from one of the following folders under "New" in the shortcut menu of the interface module: "Digital electronic modules" "Analog modules" "Communication" "Function modules" Then, select a module marked with "O" that is suitable for the input module. See also Configuring IO modules (Page 67) 66 Operating Manual, 01/2018, A5E AA

67 Engineering in PAA 11.7 Hardware engineering in the Navigator Configuring IO modules Requirement The central processing unit (CPU) is configured See chapter Configuring the central processing unit (CPU) (Page 64). The interface modules of the distributed I/O are equipped with IO modules. See chapter Equipping interface modules with I/O modules (Page 66). The "Locations" tab is displayed in the Navigator. Procedure 1. In the Navigator, select the module below the interface module. 2. Open the properties of the module. 3. In the "Name" field, enter the value in accordance with the slot number in the interface module. A value of "1" or higher is entered for most configurations. Example: The input module receives the name "1". The output module receives the name "2". This has the result that the names of the signal modules correspond to the respective slot number in the interface module. See also Information on identifying hardware components (Page 52) Creating the bus modules Bus modules The Bus modules will be created automatically when I/O modules are configured using the "HW configuration tool" plugin. When you configure the I/O modules manually, you have to create the bus modules via the short cut menu "Create bus modules" under the module after configuring the Rack and power supply Creating a redundant SIMATIC station Requirement The "Locations" tab is displayed in the Navigator. A plant has been created. Operating Manual, 01/2018, A5E AA 67

68 Engineering in PAA 11.7 Hardware engineering in the Navigator Creating a SIMATIC station 1. Select the object "Plant > Building > Floor, level > Room, Control center". 2. Select the "New > Cabinet" command from the context menu of the room. The cabinet is created below the room. 3. Select a station in the context menu of the cabinet that has been prepared for redundant hardware. Example: "New > DCS > SIMATIC 400H Station". The station is created below the cabinet. Equipping the SIMATIC station with redundant hardware 1. Select the "New > > Rack <required rack>" command in the shortcut menu of the station. The rack is used to mount the assemblies. Example: Select a rack of the UR2 type: "Rack, UR2" Note Special rule for UR2-H racks With UR2-H racks, all modules on the entire station are placed on one rack. This UR2-H rack is only divided into two areas electrically; the slots themselves provide space for two CPUs. For this reason, the UR2-H racks are not transferred to PAA as two racks with slots 1 to 9, but as one rack with slots 1 to 18. This means that the first half of the slots are intended for the first CPU, and the second half for the second CPU. Accordingly, you have to match the slot numbers yourself with the UR2-H racks. 2. Select a power supply under "New > Power supply" in the shortcut menu of the rack. 3. Select a central processing unit (CPU) under "New > Central processing units" in the shortcut menu of the rack. 4. Select a synchronization module under "New > Sync modules since V6" in the shortcut menu of the CPU. The "Name" field of the synchronization modules contains the number of the slot occupied by the synchronization module in the CPU. 5. Select an input module from one of the following folders under "New" in the shortcut menu of the rack: For this, select a module marked with "I" from one of the following folders: "Digital electronic modules" "Analog modules" "Communication" "Function modules" 68 Operating Manual, 01/2018, A5E AA

69 Engineering in PAA 11.7 Hardware engineering in the Navigator 6. Select an output module corresponding to the input module from one of the following folders under "New" in the shortcut menu of the rack: Then select a module marked with "O" that is suitable for the input module from one of the following folders: "Digital electronic modules" "Analog modules" "Communication" "Function modules" 7. If necessary, assign the rack to the location where it should be assembled. 8. Create the second rack. Proceed as described for the first rack. See also Management of control module types (Page 25) Creating a redundant I/O (Page 69) Creating a redundant I/O Requirement Two SIMATIC stations are created for redundant hardware. See chapter Creating a redundant SIMATIC station (Page 67). The "Locations" tab is displayed in the Navigator. Creating a decentralized periphery (DP slave) 1. Select the "Plant" engineering object. 2. Select the "New > Field location" command from the context menu of the object. 3. Select the "New > Decentralized periphery > ET 200M" command from the shortcut menu of the field location. 4. Select "New > Mounting rails > <desired mounting rails>" in the shortcut menu of the interface module. 5. Select "New > Interface modules > <Interface module of the type "IM HF">" in the shortcut menu of the mounting rail. 6. Create a module underneath the interface module. 7. Create a second interface module of the "IM HF" type. Operating Manual, 01/2018, A5E AA 69

70 Engineering in PAA 11.7 Hardware engineering in the Navigator 8. Create a module underneath the interface module. Note Input/output modules Use only analog or digital input/output modules with identical order numbers. 9. Confirm your entries. 10.Open the "Attributes > Automation Interface" tab in the properties of the first module. 11.Drag the second module from the Navigator to the "Redundant partner" field. 12.Confirm your entries. Result The second module is automatically linked and the redundant partner is registered in its properties in the "Attributes > Automation Interface" tab. See also Assigning redundant fieldbus via engineering task (Page 72) Using the DP/PA coupler Introduction The DP/PA coupler is used to achieve a better separation of tasks, as it establishes smaller subnets inside the fieldbus system. Procedure 1. Create a station as master, 2. Create all required objects, including an interface module, under the station. 3. To create a slave, use a gateway such as a a DP/PA link. You can select the following command from the context menu of the cabinet: "New > Gateway - Devices > DP/PA link" 4. Insert a mounting rail below the DP/PA link. 5. Insert an interface module of the PAYLINK type below the mounting rail. For example "PAYLINK: 6ES BA82-0XB0 IM153-2 HF". 6. Open the "Tasks" tab in the properties of the interface module. 7. Drag the PROFIBUS of the master to the "Target object" field of the "Assign fieldbus" task. 8. Execute the task. 9. Create a new I/O device from the ET 200 group. 70 Operating Manual, 01/2018, A5E AA

71 Engineering in PAA 11.8 Editing hardware engineering via engineering tasks 10.Open the "Tasks" tab in the properties of the ET Drag the DP/PA link fieldbus to the "Target object" field of the "Assign fieldbus" task. 12.Execute the task. Result PAA does not distinguish between a CPU or CP and a slave (gateway) as BUS master. During generation, the attribute "YLinkMode" is created at the BUS master and determines which BUS object will be used. Note Only use one bus system Two bus objects exist when you work with the DP/PA coupler: one Profibus DP and one Profibus PA. Only use one of the BUS systems Editing hardware engineering via engineering tasks Assigning a field bus to a DP slave via a task Requirement The hardware engineering has been performed in the Navigator. A SIMATIC station has been created and equipped with hardware. An interface module of the distributed I/O is equipped with I/O modules. See chapter Hardware engineering in the Navigator (Page 58). The "Locations" tab is displayed in the Navigator. You can find more information on this topic in the "EI&C Operation" manual, keyword "Using engineering tasks". Assigning a bus To assign the interface module of the distributed I/O to a bus, follow these steps: 1. Select the interface module in the Navigator. 2. Open the properties of the interface module. 3. Select the "Tasks > Bus system" tab. 4. Check to see if the engineering task "Assign fieldbus" is available. Create the engineering task "Assign fieldbus" using the context menu if it is not available. 5. Select the SIMATIC station in the Navigator. Operating Manual, 01/2018, A5E AA 71

72 Engineering in PAA 11.8 Editing hardware engineering via engineering tasks 6. Expand the structure under the SIMATIC station until the bus is visible. The structure is determined in the following step: See also chapter Configuring a SIMATIC station (Page 63). 7. Drag&drop the "PROFIBUS" object or a similar object to the "Assign fieldbus" line in the "Target object" column. 8. Click the "Execute" button in the menu bar of the "Tasks > Bus system" tab. See also Assigning redundant fieldbus via engineering task (Page 72) Software engineering in the Navigator (Page 89) Assigning redundant fieldbus via engineering task Requirement The hardware engineering has been performed in the Navigator. A station has been created for redundant hardware and equipped with hardware. The redundant interface modules of the distributed I/O are equipped with I/O modules. See chapter Hardware engineering in the Navigator (Page 58). A fieldbus has been assigned via an engineering task. See also chapter Assigning a field bus to a DP slave via a task (Page 71). The "Locations" tab is displayed in the Navigator. You can find more information on this topic in the "EI&C Operation" manual, keyword "Using engineering tasks". Overview The first subsystem of the station is connected to one of the two PROFIBUS DP interfaces via a DP master interface with the engineering task "Assign fieldbus". The second subsystem of the station is connected to the second PROFIBUS DP interface with the engineering task "Assign redundant fieldbus". Procedure 1. Select the first interface module in the Navigator. 2. Open the properties of the interface module. 3. Select the "Tasks > Bus system" tab. 4. Check whether the task "Assign fieldbus" is available. Create the task "Assign fieldbus" using the context menu if it is not available. 72 Operating Manual, 01/2018, A5E AA

73 Engineering in PAA 11.9 Hardware engineering with the configuration tool 5. Check to see if the engineering task "Assign redundant fieldbus" is available. Create the engineering task "Assign to redundant fieldbus" using the context menu if it is not available. 6. Select the station in the Navigator. 7. Expand the structure below the station until the first bus is displayed. 8. Drag&drop the "PROFIBUS" object or a similar object from the Navigator to the "Target object" column in the "Assign fieldbus" row. 9. Expand the structure below the station until the redundant bus is displayed. 10.Drag&drop the "PROFIBUS" object or a similar object from the Navigator to the "Target object" column in the "Assign redundant fieldbus" row. 11.Click the "Execute" button in the "Tasks > Bus system" tab. 12.Confirm your entries. Note For redundant ET 200SP HA excecute all the four assigned fieldbuses. See also Software engineering in the Navigator (Page 89) 11.9 Hardware engineering with the configuration tool Opening the configuration tool In PAA 2.0, the configuration tool is revised and a new tool is developed under "Plugins > Automation > PCS 7 interface > "HW configuration tool". However, the old "Config HW configuration tool" is also availble for the user. You use the configuration tool to compile available, released hardware configurations. All necessary components are generated at the same time. The applied rules are compatible with PCS 7 V9.0. See also chapter HW configuration tool (Page 78). Requirement The project presetting for PCS 7 is set in the product properties. See also chapter Creating a new engineering project (Page 21). The "Locations" tab is selected in the Navigator. Operating Manual, 01/2018, A5E AA 73

74 Engineering in PAA 11.9 Hardware engineering with the configuration tool Procedure 1. Right-click on the project node and select the "New > Config HW configuration tool" command in the shortcut menu. The node for the configuration tool is created in the Navigator. 2. Double-click the node of the configuration tool. The configuration tool is open Creating hardware with the configuration tool Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). Procedure 1. Select the required tab. For example, the "AS bundle" tab. 2. Set a location in the "Target node" field. 3. Select the "Version" from the "Version" drop down list 4. Select the required hardware. Recommendation: When selecting the hardware, proceed from top to bottom on the tab because the list entries will change depending on the already selected hardware. 5. Click on the "Create configuration" button. 6. Subsequently you find the HW under the location structure in the selected target node. 7. In addition the corresponding MLFB is generated and entered as the "MLFB" line under the "Description". The MLFB is then also available at the "Object > "Attributes" tab > > "Order data" tab > Article number" Result The hardware including the required components is created in the Navigator under the location defined as target object. During the creation of the hardware, rules that are compatible with PCS 7 HW Config are applied. Note No check for manually created hardware Manually created hardware objects are not checked by the rules of the configuration tool. 74 Operating Manual, 01/2018, A5E AA

75 Engineering in PAA 11.9 Hardware engineering with the configuration tool Information about the database The same XML file that is used at the generation of the AS station in the PCS7 is used. This file is used as the data source for generating the contents of the table Creating hardware including spare I/O channels Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). Procedure 1. Select the required tab. For example, the "I/O ET 200M" tab. 2. Set a location in the "Target object" field. 3. In the "Standard I/Os" control group, select the "Channels" entry from the "Quantity" list. 4. Select the required hardware in the "General" control group. 5. Enter the required reserves in percentage in the "General" control group in the "Spare I/O channel" field. Result The hardware including the required components is created in the Navigator under the location defined as target object. The "Redundancy" value is entered in the properties of the channel on the "Attributes > Address" tab in the "Symbol address" field. During the creation of the hardware, rules that are compatible with PCS 7 HW Config are applied Hardware including spare I/O space for modules is created Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). Procedure 1. Select the "Attributes > I/O ET <required tab>" tab. For example, the "Attributes > I/O ET 200M" tab. 2. Set a location in the "Target object" field. 3. In the "Standard I/Os" control group, select the "Modules" entry from the "Quantity" list. Operating Manual, 01/2018, A5E AA 75

76 Engineering in PAA 11.9 Hardware engineering with the configuration tool 4. Select the required hardware in the "General" control group. 5. Enter the required reserves as percentage in the "General" control group in the Spare I/O space" field. Result The hardware including the required components is created in the Navigator under the location defined as target object. The value in the "Spare I/O channel" field is automatically set to "0" in the "General" control group. During the creation of the hardware, rules that are compatible with PCS 7 HW Config are applied Creating redundant signal modules Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). Procedure 1. Select the required tab. For example, the "I/O ET 200M" tab. 2. Set a location in the "Target object" field. 3. Select signal modules with the property "Redundant design possibe". 4. Select the option "Yes" for the signal in the "Redundancy" column. Result The hardware including the required components is created in the Navigator under the location defined as target object. The "Redundant partner" is entered in the properties of the signal module on the "Attributes >Automation Interface" tab in the "Redundant partner" field. During the creation of the hardware, rules that are compatible with PCS 7 HW Config are applied Creating redundant stations Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). 76 Operating Manual, 01/2018, A5E AA

77 Engineering in PAA 11.9 Hardware engineering with the configuration tool Procedure 1. Select the "WS bundle" tab. 2. Set a location in the "Target object" field. 3. Select the option "Redundancy". 4. Select the required hardware. Recommendation: When selecting the hardware, proceed from top to bottom on the tab because the list entries will change depending on the already selected hardware. 5. In the "Workstation:" control group, select the "Server" or "Single station" or "Client" entry from the "WS type" list". Result The hardware including the required components is created in the Navigator under the location defined as target object. A master with the description "<Name>_A" and a slave with the description "<Name>_B" is created in the Navigator. The "Redundancy" control group is filled out in the properties of the stations on the "Attributes > Computer Information" tab according to the role of the object, and the redundant partner is entered. During the creation of the hardware, rules that are compatible with PCS 7 HW Config are applied Creating licenses Requirement The configuration tool is open. See also chapter Opening the configuration tool (Page 73). Procedure 1. Select the "Attributes > WS bundle" tab. 2. Set a location in the "Target object" field. 3. Select the required options in the "Licenses" control group. Note "Preselection" control group You can only select one of the two options "Standard" or "Download" in the "Preselection" control group. 4. Click on the button "Create configuration". Result When you have created the configuration, a "Licenses" folder is created below each station in the Navigator. Operating Manual, 01/2018, A5E AA 77

78 Engineering in PAA 11.9 Hardware engineering with the configuration tool HW configuration tool Introduction You can use the "HW configuration tool" plugin to configure different I/O modules like ET 200M, ET 200iSP, ET 200PA SMART, ET 200SP HA, AS Bundle, WS bundle, and PCS 7 BOX via the Plugins menu or via the icon on the toolbar as shown in the figure below. This tool is used in bulk engineering. 78 Operating Manual, 01/2018, A5E AA

79 Engineering in PAA 11.9 Hardware engineering with the configuration tool Requirement The required PCS 7 version is selected using the "Select version" in the "Customer settings" categories of the properties windows of the project. Note Only the modules of the selected PCS 7 version will be available. Procedure The procedure below describes the HW configuration tool in general. In the menu bar, select the "Plugins > Automation > PCS 7 interface > "HW configuration tool" command or click the icon on the toolbar. The HW configuration tool" plugin opens. Select the required I/O module to be configured from the available tabs in the "HW configuration tool" window. Drag&drop the target object from the Navigator to the "Target object" field in the "Set location as owner" area. Select the required interface modules and other components related to the particular module in the "General" area. Note To create a redundant Power supply or Interface modules, check the "Redundant" option in the corresponding fields. Selection of Rack, Power supply, and Interface modules are mandatory to enable the Create button. Operating Manual, 01/2018, A5E AA 79

80 Engineering in PAA 11.9 Hardware engineering with the configuration tool Do all the required I/O configuration in the "I/O configuration" area depending on the I/O to be configured. Note A module can only be selected once. Common I/O settings Standard I/O settings Failsafe settings Click on the "Create" button. After the slave is created a message with the amount of created stations or errors or warnings are shown in the status window at the bottom. Note If the "Create" button is pressed a second time a new station is created. WS Bundle and PCS 7 Box has online configurator and overview page opens in Industry Mall and therefore internet connection is required. WS Bundle or PCS 7 Box can be re-configured after creating in the tool by the menu in the tree structure. Result The configured I/O modules are created under the selected target object. 80 Operating Manual, 01/2018, A5E AA

81 Engineering in PAA 11.9 Hardware engineering with the configuration tool Configuring AS Bundle using HW configuration tool Procedure The HW configuration tool is used to configure the AS Bundle and described as below: 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > "HW configuration tool" command or click the icon on the toolbar. The HW configuration tool" plugin opens. 2. Select the AS Bundle tab. 3. Drag&drop the target object from the Navigator to the "Target node" field in the "Set location as owner" area. Operating Manual, 01/2018, A5E AA 81

82 Engineering in PAA 11.9 Hardware engineering with the configuration tool 4. Select the required Version, AS type and Quantity in the "Set location as owner" area. Note Selection of System expansion card and PROFIBUS connection is mandatory to enable the Create button. 5. Select the required bundle from the catalog. Note The red coloured row cannot be selected as it is not available in the used database. 6. Click on the "Create" button. Note If the "Create" button is pressed a second time a new station is created. Result The configured AS Bundles are created under the selected target object Configuring ET 200 stations using HW configuration tool Requirement The required PCS 7 version is selected using the "Select version" in the "Customer settings" categories of the properties windows of the project. Note Only the modules of the selected PCS 7 version will be available. 82 Operating Manual, 01/2018, A5E AA

83 Engineering in PAA 11.9 Hardware engineering with the configuration tool Procedure The HW configuration tool is used to configure the ET 200 family I/O modules and described as below: 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > "HW configuration tool" command or click the icon on the toolbar. The HW configuration tool" plugin opens. 2. Select the required I/O module to be configured from the available tabs in the "HW configuration tool" window. 3. Drag&drop the target object from the Navigator to the "Target object" field in the "Set location as owner" area. 4. Select the required interface modules and other components related to the particular module in the "General" area. Note To create a redundant Power supply or Interface modules, check the "Redundant" option in the corresponding fields. Selection of Rack, Power supply, Interface modules, Bus Adapter and MLFB - Description are mandatory in specific I/O modules to enable the Create button. Operating Manual, 01/2018, A5E AA 83

84 Engineering in PAA 11.9 Hardware engineering with the configuration tool 5. Do all the required I/O configuration in the "I/O configuration" area depending on the I/O module to be configured. Note A module can only be selected once. Common I/O settings (All I/O modules) Standard I/O settings (ET 200M, ET 200iSP, ET 200SP HA) Failsafe settings (ET 200M, ET 200iSP, ET 200SP HA) ET 200PA SMART and ET 200M I/O configuration (ET 200PA SMART) 6. Click on the "Create" button. After the slave is created a message with the amount of created stations or errors or warnings are shown in the status window at the bottom. Note If the "Create" button is pressed a second time a new station is created. Result The configured I/O modules are created under the selected target object. 84 Operating Manual, 01/2018, A5E AA

85 Engineering in PAA 11.9 Hardware engineering with the configuration tool Configuring WS Bundle using HW configuration tool Procedure The HW configuration tool is used to configure the WS Bundle and described as below: 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > "HW configuration tool" command or click the icon on the toolbar. The HW configuration tool" plugin opens. 2. Select the WS Bundle tab. 3. Drag&drop the target object from the Navigator to the "Target Object" field in the "Set location as owner" area. 4. Select the Industrial PC and Quantity in the "Select configuration" area. 5. Click the "Start SIMATIC WS Bundle online configurator" button to do online configuration. Note The system should be connected to the internet to do online configuration using "Start SIMATIC WS Bundle online configurator". Operating Manual, 01/2018, A5E AA 85

86 Engineering in PAA 11.9 Hardware engineering with the configuration tool 6. Select all other required components from the "Additional items" area. 7. Click on the "Create" button. Note If the "Create" button is pressed a second time a new station is created. Note Select "New >Update Configuration" from the context menu of the created WS Bundle hardware to update the configuration. Result The configured WS Bundles are created under the selected target object Configuring PCS 7 Box using HW configuration tool Procedure The HW configuration tool is used to configure the WS Bundle and described as below: 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > "HW configuration tool" command or click the icon on the toolbar. The HW configuration tool" plugin opens. 2. Select the PCS 7 Box tab. 3. Drag&drop the target object from the Navigator to the "Target Object" field in the "Set location as owner" area. 4. Click the "Start SIMATIC PCS 7 Box online configurator" button to do online configuration. Note The system should be connected to the internet to do online configuration using "Start SIMATIC PCS 7 Box online configurator". 86 Operating Manual, 01/2018, A5E AA

87 Engineering in PAA 11.9 Hardware engineering with the configuration tool 5. The configuration web page opens as shown in the image below, do the required configuration and click the "Result" tab to see the configuration details. 6. Click on the "To the product list" button, the web page closes and your configuration is saved. 7. Select all other required components from the "Additional items" area. 8. Click on the "Create" button. Note If the "Create" button is pressed a second time a new station is created. Operating Manual, 01/2018, A5E AA 87

88 Engineering in PAA Extended hardware parameters Note Select "New >Update Configuration" from the context menu of the created PCS 7 Box hardware to update the configuration. Result The configured PCS 7 Box is created under the selected target object Extended hardware parameters Configuration The hardware configuration and the advanced hardware parameters are transferred via the Automation Interface. The data exchange of the advanced hardware parameters can be activated/deactivated, if e.g., for performance reasons, not all advanced hardware parameters are meant to form part of the data exchange. There are two options to control the exchange of advanced hardware parameters: In PAA you can decide whether the advanced hardware parameters are to be used during the transfer while importing/exporting. To do so, in the "Import/Export PCS 7" plugin, activate or deactivate the option "Project > Hardware > Extended parameters" in the "Filter" control group. See also chapter Exporting the hardware configuration (Page 121) and chapter Importing the hardware configuration (Page 130). In the XML control file "AIaS7ExtHWParameter.xml" define which hardware parameters form part of the data exchange. This file is in the "Program Files (x86)\siemens\step7\s7data\ais7ad" directory. In this XML file, an entry is available for each hardware parameter that begins with the expression "<HWParameter name". In this entry there is the expression "used", via which the data exchange of this hardware parameter is controlled. If the expression is "used="1"", the data exchange of this hardware parameter is activated. If the expression is "used="0"", the data exchange of this hardware parameter is deactivated. Note Functional scope In PAA, the extended hardware parameters are only available to the assemblies supplied in the database. This is visible in PAA in the "Automation extended" tab. In addition, no extended parameters are supported at F-blocks. 88 Operating Manual, 01/2018, A5E AA

89 Engineering in PAA Software engineering in the Navigator Note Standard values in the export When using the advanced hardware parameters, the standard values are not transferred. If you wish to use the standard values from PCS 7, carry out an import from PCS 7. Note No automatic consistency check of the hardware configuration In PAA, no consistency check of the set HW parameters is carried out. This has the result that configurations can be transferred which are inconsistent in SIMATIC HW Config. Note Inconsistencies during channel assignment In PAA, the limits for channel 0 (channel groups 0-1) are correct in channel 0. For channel 2 (channel groups 2-3), contrary to the assignment in PCS 7, the limits in PAA are on channel 1. The limits on channel 1 are transferred to PCS 7 for channel 2 (channel group 2-3) Software engineering in the Navigator Notes on the plant hierarchy Requirement The project presetting for PCS 7 is used. See chapter Opening a planning project (Page 22). The DCS structure has been created. See chapter Creating the DCS structure (Page 22). Operating Manual, 01/2018, A5E AA 89

90 Engineering in PAA Software engineering in the Navigator PAA structure in comparison to plant hierarchy in PCS 7 The plant hierarchy in PCS 7 can include up to 8 levels. A 4-level plant hierarchy is used in this example: Plant Part of the plant hierarchy. Unit Part of the plant hierarchy. Subunit Part of the plant hierarchy. Folder COMOS-specific structural element. Position Part of the plant hierarchy. COMOS process tag See also Optional: Creating and configuring process tags (Page 91) Working with channel requests Requirement Hardware engineering has been performed. See also chapter Editing hardware engineering via engineering tasks (Page 71). The DCS structure has been created. See also chapter Creating the DCS structure (Page 22). At least one instance of a control module has been created in the DCS structure. The instance of the control module contains a signal. If you have already created the signals with the "Excel Import" plugin, the signals are already linked. 90 Operating Manual, 01/2018, A5E AA

91 Engineering in PAA Software engineering in the Navigator Procedure 1. Select the instance of the control module in the DCS structure in the Navigator. 2. Navigate beneath the signal under the instance of the process tag to the channel request. 3. Open the properties of the channel request. 4. Implement the channel request to the I/O channel Optional: Creating and configuring process tags Requirement The plant hierarchy is known. See chapter Notes on the plant hierarchy (Page 89). The "Units" tab is open in the Navigator. Creating and configuring process tags You can find additional information on creating and configuring process tags in the "EI&C Operation" manual, keyword "Basic Engineering". Specifically, the following steps are necessary: 1. Select the "A50 EI&C" folder. 2. Create a position. 3. Create process tag. 4. Do not use a function template. 5. Select the "A20 Signal engineering" folder below the function. 6. Create signals. 7. Create the channel request "Channel requests for control" for each signal. This channel request is used to link the signal to the DP slave. See also Optional: Linking hardware and software: Implementing channels (Page 92) Operating Manual, 01/2018, A5E AA 91

92 Engineering in PAA Editing software engineering using engineering tasks Optional: Linking hardware and software: Implementing channels Requirement Hardware engineering has been performed. See chapter Editing hardware engineering via engineering tasks (Page 71). The process tags have been created and configured. See chapter Optional: Creating and configuring process tags (Page 91). Procedure 1. Select the signal in the "A50 EI&C > A20 Signal engineering" folder in the "Units" tab in the Navigator. 2. Open the properties of the signal. 3. Select the "Locations" tab in the Navigator. 4. Select an I/O module under the decentralized periphery. 5. Drag a channel of the interface module from the Navigator and drop it into the "Implementation" field in the channel request properties. 6. Confirm your entries. Implementing channels in bulk If you want to implement the channels in bulk, use the "Excel Import" plugin. See also chapter Using "Excel import" (Page 49). See also Editing software engineering using engineering tasks (Page 92) Editing software engineering using engineering tasks Engineering tasks Objective With the help of an engineering task, a control module is generated from a template and created below a position as follows. You can find more information on this topic in the "EI&C Operation" manual, keyword "Using engineering tasks". 92 Operating Manual, 01/2018, A5E AA

93 Engineering in PAA Editing software engineering using engineering tasks See also Displaying the "SW interface" tab and creating tasks (Page 93) Displaying the "SW interface" tab and creating tasks Requirement Software engineering has been performed. See chapter Software engineering in the Navigator (Page 89). The "Units" tab is open in the Navigator. Displaying the "SW interface" tab 1. Select a folder of the DCS structure in the "Units" tab in the Navigator. 2. Open the properties of the folder. 3. Select the "Tasks" tab. 4. If the "SW interface" tab is not available, close the folder properties window. 5. Select "New > "CMT template" in the folder context menu. 6. Open the properties of the folder. The "SW interface" tab opens. Checking and creating tasks 1. Select the "Tasks > SW interface" tab. 2. Check whether the following engineering task is available: "Assigned station" 3. Create missing task using the "New" context menu. See also Assigning a control module type to the DCS structure (Page 94) Assigning a control module type to a function (Page 95) Engineering tasks (Page 92) Operating Manual, 01/2018, A5E AA 93

94 Engineering in PAA Editing software engineering using engineering tasks Assigning a control module type to the DCS structure Requirement Hardware engineering has been performed. See chapter Editing hardware engineering via engineering tasks (Page 71). The "SW interface" tab of a folder in the DCS structure is displayed and the tasks have been created. See chapter Displaying the "SW interface" tab and creating tasks (Page 93). The "Units" tab is open in the Navigator. Configuring and executing a task 1. Select the "Templates" node in the Navigator. 2. Select the following object: "@Template 7 > Template-Container > CMTs Control module types". 3. Select the template of a control module in the "CMTs" folder. 4. Drag&drop the template from the Navigator to the "Target object" field in the "Copy in control module" line. 5. Click the arrow of the "Execute" button in the menu bar of the "SW interface" tab. 6. Select the "Execute (selected)" entry. 7. Confirm your entries. Executed tasks are marked with a green signal light in the "Status" column. Result The inserted control module is displayed below the folder of the DCS structure in the Navigator structure. See also chapter Notes on the plant hierarchy (Page 89). There is a mapping table below the inserted control module. See also chapter Configuring the mapping table of the signal designations (Page 109). See also Assigning a control module type to a function (Page 95) 94 Operating Manual, 01/2018, A5E AA

95 Engineering in PAA Editing software engineering using engineering tasks Assigning a control module type to a function Requirement Hardware engineering has been performed. See chapter Editing hardware engineering via engineering tasks (Page 71). The "SW interface" tab of a function is displayed and the tasks have been created. See chapter Displaying the "SW interface" tab and creating tasks (Page 93). The "Units" tab is open in the Navigator. Procedure 1. Assign the control module to a function. See also chapter Assigning a control module type to the DCS structure (Page 94). 2. Confirm your entries. Executed tasks are marked with a green signal light in the "Status" column. Result The inserted control module is displayed below the function in the Navigator structure. See also the overview in Notes on the plant hierarchy (Page 89). There is a mapping table below the inserted control module. The mapping table is edited by the administrator. See also chapter Configuring the mapping table of the signal designations (Page 109) Assigning control module types to the DCS structure in bulk Requirement Hardware engineering has been performed. See chapter Editing hardware engineering via engineering tasks (Page 71). The "Units" tab is open in the Navigator. Bulk processing of tasks 1. Select one of the folders of the plant hierarchy in the DCS structure. 2. Open the properties of the folder. 3. Select the "Tasks" tab. 4. Make sure that the "SW interface" tab is displayed and the tasks have been created. See chapter Displaying the "SW interface" tab and creating tasks (Page 93). 5. Select the "SW interface" tab and proceed as described here: Assigning a control module type to the DCS structure (Page 94) The task includes all control module types below the selected folder. Operating Manual, 01/2018, A5E AA 95

96 Engineering in PAA "Assembly updater" plugin "Assembly updater" plugin Update type usages Introduction With the "Assembly Updater" plugin, you apply changes to types to the already created instances of control modules and functions. You can save the changes in a working layer. You can overwrite existing engineering information. You have the option to set a version at the template. Requirement You have already created instances of control modules and functions. Attributes which are to be matched are defined in the "Property mapping PCS 7" standard table. See also chapter Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7" (Page 152). Procedure 1. Select the "Plugins > Automation > Assembly updater" command in the menu bar. 2. Set the desired start object below which the updated template of the type is located. You may use the project node here. 3. Drag&drop the changed type from the "Templates" node in the navigator to the "Refreshed template" field. 4. Select the entry "Structure and property verification", to check all structures and properties of the template object. 5. Click the "Update" button in the menu bar of the plugin. A tree with the template is displayed in the "Structural differences" control group. Nothing is displayed here when you run a version check. 6. Select an entry in the table for the "Usages in projects" control group. The template tree in the "Structural differences" control group is colored. The colors indicate how the selected usage deviates from the template. The color requirements of the legend apply here. Objects that have not been changed in the usage are not displayed in the template tree. To display them, select the "Show unchanged objects" option. 7. Click the "Update" button to apply the displayed type changes to the instances. A dialog opens. 96 Operating Manual, 01/2018, A5E AA

97 Engineering in PAA "Assembly updater" plugin 8. Optional: Choose one of the following options: Enable the "Create working layer" option and assign a name to the working layer to save the changes in a new working layer. Enable the "Overwrite engineering information with the template data" option to overwrite the existing engineering information at the instances. To overwrite the existing mapping tables at the instances with the mapping table of the type, select the "Overwrite mapping table" option. When you run a version check, the version of the template is written to the instance during the update. 9. Confirm your entries. Updating a subordinate control module To apply changes to a subordinate control module to the instances of an equipment module (type), proceed as follows: 1. Open the plugin. 2. Set the "Templates" node as the start object. 3. Drag&drop the changed subordinate control module from the "Templates" node in the navigator to the "Refreshed template" field. 4. Update the use of the subordinate control module as described above. 5. Confirm your entries. 6. Set the project node as the start object. 7. Drag&drop the updated control module (type) from the "Templates" node in the navigator to the "Refreshed template" field. 8. Update the instances of the control module (type) as described above Updating usages / instances Initial situation A template that is used in your engineering project has been changed. Aim The usages derived from the template should incorporate the changes. Important data for the configuration from the old objects can be retained or overwritten in the engineering project. You can first carry out the resulting changes in a working layer to better check the effects. Requirements You have read rights in the "@Template" node. Operating Manual, 01/2018, A5E AA 97

98 Engineering in PAA "Assembly updater" plugin Procedure 1. Select the "Plugins > Automation > Templates > Assembly updater" command in the menu bar: 2. In the node, navigate to the template object - the object under which the template is located. 3. Set the desired start object under which the search for the usages is to be carried out. You may use the project node here. 4. Drag the template object into the "Template" field. The current version of the template is displayed in the "Template version" row. Changes that are relevant for the updating of the instances are evaluated and displayed automatically. The owner of the engineering task who generated the instance is displayed for each instance. Information such as the working layer in which the instance was generated and the version of the instance are also displayed. All the differences of the instance to the original version (current - 1) of the template are listed below the instance. 5. Select one of the following options from the list: To display all the changes select the entry "Display all changes". To display only those changes through which conflicts were triggered select the entry "Display changes that require action". 6. Click the "Update" button. 7. Select one of the following options: Individually select the changes that you want to keep for each instance. To undo the selection for an instance click the "Reset instance" button. Existing changes are evaluated again. You can correct the selection. To undo the selection for all the instances click the "Apply default decisions again to all differences" button in the menu bar of the plugin. 8. Confirm your entries. Changing rules for the matching You can change the rules for the matching of the templates with the instances. You can find additional information on this topic in the "Administration" manual, keyword "Specifying rules for standard actions" Legend Main statement Color Gray Black Blue Meaning No changes Changed subobjects Changed 98 Operating Manual, 01/2018, A5E AA

99 Engineering in PAA Using symbol tables Color Green Red Meaning Not available on instance Not available in the template Variant administration The update of variants has been added and works via the Assembly updater. After the Assembly updater has been terminated, the graphical representation of the CMs is updated correspondingly when the Function diagram is opened. Technically speaking, the matching of CMT and variant functions as follows: All those at the variant are added to the CMT if they do not yet exist Existing objects remain and also retain added values unless the variant brings other values with. In this case the values are overwritten Objects at the CMT that no longer exist at the variant are deleted All the added functions in the variant are added to the instances. When some functions are deleted in the type, they are also deleted in the instances. Note Non-updated objects at the CMT Values of signals and parameters as well as comments are not updated In the case of a conflict, types overwrite the status of the instance Using symbol tables Symbol table Change options It is now possible to make the following changes: Selection of the displayed PH in the symbol name Manual entry of status, symbol (Y00A00505), address (Y00A00182), data type (Y00A00517), comment ((Y00A00011)) and signal designator ((Y00A00566)) Linking of symbols with hardware signals Generation of default parameters for prefixes and suffixes Operating Manual, 01/2018, A5E AA 99

100 Engineering in PAA Using symbol tables Updating Manual updating of the symbol table is required due to the new naming mechanism. This is not done automatically in order to increase the performance. Exporting the hardware information Through a query, it is possible to export and print the list of the symbols including their hardware information. Synchronizing the attributes When the symbol names are edited in the symbol table, the data is transferred to the IO channel if the IO channel is implemented. When the comment is edited in the symbol table, the data is transferred to the real channel, to the request channel object and to the signal description. When the data in the Symbol or Comment column is deleted, the inherited data is displayed by the channel request if the IO channel is implemented. If the IO channel was not implemented, deleting will only empty the field Importing symbolic addresses into a symbol table You can also import the symbolic addresses from a symbol table stored in the file system to the symbol table. Procedure 1. Select the "Symbol table > Import symbol table" command in the context menu of the symbol table. 2. In the file system you select the symbol table from which you want to import the symbolic addresses. See also Refreshing the symbol table (Page 100) Refreshing the symbol table Procedure To refresh all symbolic addresses in the symbol table, select the command "Symbol table > Refresh symbol table" from the shortcut menu of the symbol table below the station. 100 Operating Manual, 01/2018, A5E AA

101 Engineering in PAA Engineering in the function diagram Result The symbolic addresses are written into the symbol table Engineering in the function diagram Editing control modules on the function diagram Requirement The function diagram is open. The control module was automatically placed on the function block diagram during the import or during the creation of the "Type configurator" plugin. See chapter Importing control modules (Page 129) and chapter Creating control modules (Page 33). Procedure 1. Select one of the following options: If you are working with the DCS structure, select a signal below the control module. If you are working with the unit structure, select a position below a process tag. Open the folder "A20 Signal engineering" under the process tag. Select a signal in the "A20 Signal engineering" folder. 2. Drag&drop the signal to the function diagram. The signal has been implemented on the channels in a previous step. See chapter Optional: Linking hardware and software: Implementing channels (Page 92). If the data type of the signal does not match the data type of the block connector, a connection is not established. You can find additional information on this topic in the "Logical" manual, keywords "Connection types for block connections" and "Allowed connection type combinations". Operating Manual, 01/2018, A5E AA 101

102 Engineering in PAA Engineering in the function diagram 3. Place generic blocks on the function diagram. You can find more information on this topic in the "Logical" manual, keyword "Connecting blocks". The generic blocks OR, AND and XOR are available in the menu of the function diagram. You have the option of using other blocks and integrating them into the menu. For example, NOT. You can find the base objects at: > M40 > A50 > A10 > A10 > A10 > A10 > A10 > A40 Bit-wise". 4. Connect the objects on the function diagram. Note Connecting signals directly with the block Always connect the hardware signal directly to the input of the placed block. Only this type of connection configuration can be exported to PCS 7. The following procedures are not supported: Connecting a hardware signal to a generic block and then connecting the generic block to the block. Result The placed objects can be exported. See chapter Export from PAA to PCS 7 (Page 115). See also Editing the logic on function diagrams (Page 102) Editing the logic on function diagrams Requirements A control module has been edited on a function diagram. See also chapter Editing control modules on the function diagram (Page 101). Use of blocks You can use the following generic blocks: AND OR XOR NOT 102 Operating Manual, 01/2018, A5E AA

103 Engineering in PAA Engineering in the function diagram You have the option of using other blocks. To do this, the blocks must be defined as a standard function in PCS 7. Note the following: The name of the standard function in PCS 7 corresponds to the block label in PAA. The name of the block connections in PCS 7 corresponds to the label of the block connections in PAA. See also Example for interlock logic on function diagrams (Page 103) Example for interlock logic on function diagrams Requirements An interlock logic has been created in function diagrams. See section Editing the logic on function diagrams (Page 102). Operating Manual, 01/2018, A5E AA 103

104 Engineering in PAA Specifying the measuring ranges Example Semi-open connection with link across documents and reference information Memorize: Create connections across several diagrams by using these options / commands Disconnect & Connect with Specifying the measuring ranges Signals The tab of the CM signal becomes a new "Measuring range" attribute. 104 Operating Manual, 01/2018, A5E AA

105 Engineering in PAA Moving the PH When a unit is set, the measuring range can be specified through the mapping table from the measuring function. See "Attributes > Automation Interface < Signal configuration > Measuring range". Database name Y00A00404 Parameter It is also possible to specify a unit for a parameter. If the value and the device are transferred from PCS 7, you have to make sure that the change in the unit does not change the transferred value. See "Parameter configuration > Measuring range" Moving the PH Moving of objects and hierarchies such as PH, CMT is now synchronized precisely between PCS 7 and PAA. This does not result in the PH being marked as "new" in the data transfer dialog. In PAA: The elements can be moved using drag&drop. In PCS 7: Example Existing CM instance is connected with the associated CM instance in a PAA project Moving the CM instance in PCS 7 to a different location (drag&drop with Shift key) Note: The other location can also be another project in PCS 7. In this case, the data transfer shows the object as deleted from the source project in PCS 7 (as long as data transfer for a complete multiproject is not available) The user triggers a transfer of the data to PAA. This results in a moved CM instance in PAA, whereby all the subordinate objects in this CM instance are also moved The data transfer dialog does not show new or deleted objects, but only moved objects. This also applies conversely from PAA to PCS 7 Operating Manual, 01/2018, A5E AA 105

106 Engineering in PAA Moving the PH 106 Operating Manual, 01/2018, A5E AA

107 Editing large quantities of connections 12 Introduction In order to create large quantities of connections or references, use the "Connection manager" plugin. See also chapter Using references (Page 38). Requirement You have created CMs or functions with control variables, on which there are inputs and outputs. The CMs or functions are placed on a function plan. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Connection Manager" command. The "Connection manager" plugin opens. 2. In the menu bar of the plugin, in the "Connection type" list, select the desired entry. "Textual reference" is selected here as default. 3. Optional: In the menu bar of the plugin, filter according to inputs or outputs. 4. Pull the desired object into the "Start object" field, for example the plant. The evaluation starts automatically. All control variables available under the start object are listed, according to the filter settings. 5. In order to link a listed input or output with another, using Drag&Drop, pull the desired input or output from the navigator into the "Target" column. You have the option of pulling multiple objects from the navigator the multiple inputs and outputs, as listed. If an object from the navigator has the incorrect data type, you will not be able to drop the object. 6. Optional: To assign an output to multiple links, pull the object from the navigator into the "Add" column of the output. The additional link will be created in a new column. 7. Confirm your entries. Operating Manual, 01/2018, A5E AA 107

108 Editing large quantities of connections 108 Operating Manual, 01/2018, A5E AA

109 Linking attributes from PAA and PCS Configuring the mapping table of the signal designations Requirement Management of control modules types has been carried out. The templates of the control module types have been created. See chapter Management of control module types (Page 25). A control module has been inserted. The "Units" tab is open in the Navigator. Objective You edit the mapping table in the engineering data. To do this, edit the mapping table at a CM as an example. Afterwards, save the mapping table in the templates. It is then available for all CMs of this type. Calling a mapping table 1. Select the "Units" tab in the Navigator. 2. In the DSC structure, navigate to the inserted control module below a folder. 3. Open the properties of the control module. 4. Select the "Attributes > Automation Interface" tab. 5. Click the "Open mapping table" button. Step 1: Collecting PCS 7 attributes 1. Keep the mapping table open. 2. Expand the structure below the control module used in the previous step. Only attributes are allowed that are located below the control module, and for which the mapping table was opened. For the example in this documentation, use the following attributes: Control module, "Automation Interface tab: "Name" Signal under the control module, tab "Automation Interface": "Signal name" Operating Manual, 01/2018, A5E AA 109

110 Linking attributes from PAA and PCS Configuring the mapping table of the signal designations 3. Drag&drop this attribute from the Navigator into the "Attribute" column. 4. For each attribute used, double-click in the "Link type" column and select the "Full dynamic" list entry. The "Full dynamic" option ensures that all properties of the linked attribute are synchronized. Step 2: Assigning PAA attributes 1. Keep the mapping table open. 2. Select a process tag below the same position as in the previous step. A link exists through the unit pointer. An example of an assignment is available in chapter Example of an assignment (Page 112). 3. Drag&drop this attribute from the Navigator into the "Source object" column. 4. Double-click in the "Property" column and select "DisplayValue" to display the value. 5. Check the transferred property in the "Value" column. 6. To store the assignments, click the "Apply" button. Optional: Assigning PAA attributes using the navigation assistant Alternatively, you can select the source object in the navigation assistant. See chapter Using the navigation assistant (Page 111). 110 Operating Manual, 01/2018, A5E AA

111 Linking attributes from PAA and PCS Using the navigation assistant See also Adopting a mapping table as a template (Page 112) Reference to the mapping table (Page 148) 13.2 Using the navigation assistant Requirement The mapping table of the signal designations is open. See chapter Configuring the mapping table of the signal designations (Page 109). Procedure You use the navigation assistant if you do not know the position of the source object in the unit tree. 1. Open the properties of a control module. 2. Select the "Attributes > Automation Interface" tab. 3. Click the "Open mapping table" button. 4. In the mapping table, double-click in the required cell of the "Source object" column. The navigation assistant opens. The currently selected control module is entered as the start object. 5. To define the target object step-by-step, follow these steps: Double-click on an entry in the "Object" column in the right table. The selected object is transferred to the "Step" column of the left table. To create another step below the last step, mark the last step in the left table and doubleclick on the required object in the right table. To remove a step from the left table, select the "Remove row" command in the context menu of the row to be deleted. 6. Confirm your entries. You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Calculation type: Navigation library extended". See also Example of an assignment (Page 112) Reference to the navigation assistant (Page 149) Operating Manual, 01/2018, A5E AA 111

112 Linking attributes from PAA and PCS Adopting a mapping table as a template 13.3 Example of an assignment Requirement The mapping table of the signal designations is open. See chapter Configuring the mapping table of the signal designations (Page 109). Procedure The following mapping applies based on the example in this documentation: PCS 7 attribute, "Y30T00001 Automation Interface" tab Name of the signal: Attribute "Name Signal name" Name of the control module: Attribute "Name Name" PAA attribute Process tag, "A20 Signal engineering" folder, properties of the signal: "Y00T00027 Signal data" tab, "Y00A00555 Signal description" attribute Linked through unit pointer Item: "Y30T00001 Automation Interface" tab, "Name Hierarchy name" attribute Linked through unit pointer See also Adopting a mapping table as a template (Page 112) 13.4 Adopting a mapping table as a template Requirement The mapping table of the signal designations is configured. See chapter Configuring the mapping table of the signal designations (Page 109). The "Units" tab is open in the Navigator. Objective The mapping table is saved in the templates and is then available for all control modules of this type. Calling a mapping table 1. In the unit structure, navigate to the inserted control module below a position. 2. In the properties of the control module, select the "Attributes > Automation Interface" tab. 112 Operating Manual, 01/2018, A5E AA

113 Linking attributes from PAA and PCS Adopting a mapping table as a template 3. Click the "Open mapping table" button. 4. Edit the mapping table according to these instructions: Reference to the mapping table (Page 148) Saving the mapping table To save the assignments to the control module type, follow these steps: 1. Open the fully assigned mapping table of a control module. 2. To save the assignments at the template of the control module type used, click on the "Insert in template" button in the toolbar at the top. 3. Confirm your entries. If you want to check the assignments in the template, open the mapping table of the control module type in the following folder: "@Template Templates 7 > Library folder" Operating Manual, 01/2018, A5E AA 113

114 Linking attributes from PAA and PCS Adopting a mapping table as a template 114 Operating Manual, 01/2018, A5E AA

115 Export from PAA to PCS Selective transfer To transfer specific TH folders or CM instances, proceed as follows: 1. Open the Import/Export dialog 2. Find the field "Selective transfer > Selected PH/CM" 3. Select several instances or folders in the DCS structure. The following types are permitted: Hierarchy folder, CM Template / ACM template and CM instances 4. Transfer these by drag&drop 5. Take into account that the filter options are adapted automatically. If appropriate, select others. 6. Start the export via the "Export" button. Result The export can be performed as a direct export (PCS 7 project) or into an XML file Transfer of the S7 unit The user can enter the technological name of a unit in a CM instance in PAA. This unit is transferred automatically into the corresponding integer value (according to IEC 61158) during the transfer to PCS 7. Transferring the unit for signals and parameters If a unit is imported that does not exist in COMOS, a message should be displayed during importing. The following authorization is required to change the device group: 1. Open "Administrator > System > User management" in the Menu bar. 2. Open the user properties. 3. Select the "Rights" tab. Operating Manual, 01/2018, A5E AA 115

116 Export from PAA to PCS Transfer of the S7 unit 116 Operating Manual, 01/2018, A5E AA

117 Export from PAA to PCS Exporting digitally signed XML files: 14.3 Exporting digitally signed XML files: Note Security when performing data exchange via XML format Access to the transfer medium/transfer directory: When using the indirect data exchange via XML format between PAA and PCS 7, ensure that the transfer medium or the transfer directory of the XML files is only accessible to authorized persons. Digitally signed XML files: To describe the origin and integrity of the XML data, you can sign the XML file digitally during the data exchange in XML format. This corresponds to the requirements of the PCS 7 security concept. By checking the digital signature, you ensure that the XML file on the transfer medium has not been modified. The digital signature on the XML file is deactivated by default. Activating the digital signature is recommended. See also chapter Overview of data exchange with PCS 7 (Page 15). Requirement To sign the XML file, the following objects must be available on the PC: The certificate of the user that is signing. This certificate can be created by a commercial provider or via a "Windows Server Certification Authority" and must be saved in the Windows "MMC" console under "Current user > Certificates". The corresponding "CA" certificate must be saved in the "MMC" console under "Trusted Root Certification Authorities". For this certificate, in the properties of the "Key usage" attribute, at least one of the values must be set, either"digital signature" ("digitalsignature") or "non-repudiation" ("nonrepudiation"). The Private Key for this certificate. Procedure To use the digital signature in the PCS 7 project, in the plugin "Import / Export PCS 7" in the "Export" tab in the "Project selection" control group, activate the option "XML signature". Standards applied The RSA asymmetric signature procedure is used, according to standard "PKCS#1" (see " The attributes of the certificate are described in the certificate definition under " Operating Manual, 01/2018, A5E AA 117

118 Export from PAA to PCS Exporting a PAA project 14.4 Exporting a PAA project Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter "Export" tab (Page 147). 3. Select one of the following options: To export a PCS 7 project file, select the option PCS 7 project". To export an XML file, select the option XML file". Recommendation: If you wish to export an XML file, also activate the "XML signature" option. See also chapter Exporting digitally signed XML files: (Page 117). 4. To select a PCS 7 project or an XML file as the source for the export, click on the "..." button next to the "PCS 7 project path / XML path" field. The "Save as" dialog opens. 5. Make the required settings. 6. Confirm your entries. The "Project selection" dialog closes. 7. Select the station that you want to export in the "Selection" column. Note Identification of the project The station is used to identify the project. If you want to export the project, also select the station. 8. Enable the required options for the "Filter" control group. 9. Click the "Export" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). If you have not selected a project yet, the "Project selection" dialog opens first. 10.Click on "Import objects from A to B". See also Exporting the technological hierarchy (Page 119) Exporting instances (Page 119) Exporting the hardware configuration (Page 121) 118 Operating Manual, 01/2018, A5E AA

119 Export from PAA to PCS Exporting instances 14.5 Exporting the technological hierarchy Objective Exporting the plant hierarchy to PCS 7. If there is already a plant hierarchy in PCS 7, the hierarchy folders are synchronized with one another. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter "Export" tab (Page 147). 3. Select one of the following options: To export a PCS 7 project file, select the option PCS 7 project". To export an XML file, select the option XML file". Recommendation: If you wish to export an XML file, also activate the "XML signature" option. See also chapter Exporting digitally signed XML files: (Page 117). 4. To select a PCS 7 project or an XML file as the source for the export, click on the "..." button next to the "PCS 7 project path / XML path" field. The "Project selection" dialog opens. 5. Make the required settings. 6. Confirm your entries. The "Project selection" dialog closes. 7. Select the stations that you want to export in the Select" column. 8. Select the "Project > Plant hierarchy" option in the "Filter" control group. 9. Click the "Export" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 10.Click on the "Import objects from A to B" button. 11.Click on the "Close" button to close the "Data transfer - Generate/import" dialog Exporting instances Requirements The plant hierarchy is exported from PAA and synchronized with the plant hierarchy from PCS 7. See chapter Exporting the technological hierarchy (Page 119). Operating Manual, 01/2018, A5E AA 119

120 Export from PAA to PCS Exporting types Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter "Export" tab (Page 147). 3. Select one of the following options: To export a PCS 7 project file, select the option PCS 7 project". To export an XML file, select the option XML file". Recommendation: If you wish to export an XML file, also activate the "XML signature" option. See also chapter Exporting digitally signed XML files: (Page 117). 4. To select a PCS 7 project or an XML file as the source for the export, click on the "..." button next to the "PCS 7 project path / XML path" field. The "Project selection" dialog opens. 5. Make the required settings. Confirm your entries. 6. The "Project selection" dialog closes. 7. Select the "Project > CM instances" option in the "Filter" control group. The "Plant hierarchy" option is activated automatically because instances can only be exported together with the plant hierarchy. 8. Click "Export" to start the export. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 9. Click on the "Import objects from A to B" button. 10.Confirm your entries Exporting types Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter "Export" tab (Page 147). 3. To select a PCS 7 project or an XML file as the source for the export, click on the "..." button next to the "PCS 7 project/library" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. See also chapter Exporting digitally signed XML files: (Page 117). The "Project selection" dialog opens. 4. Make the required settings. 5. Confirm your entries. The "Project selection" dialog closes. 120 Operating Manual, 01/2018, A5E AA

121 Export from PAA to PCS Exporting the hardware configuration 6. In the "Automation Tree project/library" list, select the source project to be exported. 7. Select the "Library > < Requested option" option in the "Filter" control group. Enumerations, commands and status, functions are managed in the same way as types. 8. Click the "Export" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 9. Click on the "Import objects from A to B" button. Result The types are exported. Then assign the blocks, block contacts, block messages, etc. in PCS Exporting the hardware configuration Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter "Export" tab (Page 147). 3. To select a PCS 7 project or an XML file as the source for the export, click on the "..." button next to the "PCS 7 project/library" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. See also chapter Exporting digitally signed XML files: (Page 117). The "Project selection" dialog opens. 4. Make the required settings. 5. Confirm your entries. The "Project selection" dialog closes. 6. In the "Automation Tree project/library" list, select the source project to be exported. 7. Select the "Project > Hardware" option in the "Filter" control group. 8. If you also wish to export the hardware parameters, then in addition, activate the option "Project > Hardware > Extended parameters". See also chapter Extended hardware parameters (Page 88). 9. Click the "Export" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 10.Click on the "Import objects from A to B" button. Result The hardware configuration is exported to the PCS 7 project. Operating Manual, 01/2018, A5E AA 121

122 Export from PAA to PCS Exporting ET 200PA SMART modules from PAA to PCS Exporting ET 200 I/O modules from PAA to PCS 7 Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter Exporting a PAA project (Page 118). Note It is not necessary to create bus and terminal modules to transfer a project with ET 200 family I/O modules from PAA to PCS 7. PS, rack and terminal modules are not transferred via AI. The image below shows the example of ET 200M physical structure Exporting ET 200PA SMART modules from PAA to PCS 7 Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter Exporting a PAA project (Page 118). Note It is not necessary to create bus and terminal modules to transfer a project with ET 200SP SMART from PAA to PCS Operating Manual, 01/2018, A5E AA

123 Export from PAA to PCS Exporting ET 200iSP modules from PAA to PCS Exporting ET 200iSP modules from PAA to PCS 7 Note Following configrations can be exported ET 200iSP with single PROFIBUS interface module and 1 PS ET 200iSP with redundant PROFIBUS interface module and 2 PS Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Export" tab. See also chapter Exporting a PAA project (Page 118). Note It is not necessary to create bus and terminal modules to transfer a project with ET 200iSP from PAA to PCS 7. Operating Manual, 01/2018, A5E AA 123

124 Export from PAA to PCS Exporting ET 200iSP modules from PAA to PCS Operating Manual, 01/2018, A5E AA

125 Import from PCS 7 to PAA IO channel implementation When a signal is in both the DCS structure and in the plant structure, PAA cannot differentiate. To import the signal precisely into one of the structure, proceed as follows: Procedure 1. Open the "Import Export PCS 7" dialog 2. Open the "Import" tab 3. Select the desired path under "Structure" Hardware transfer A complete set of hardware components for data exchange with PCS 7 via the data transfer dialog is new. All HW components that are enabled for PCS 7 V8.x can be transferred from a completely configured PCS 7 project. All the hardware components in PAA are transferred to the folder "not assigned HW". On re-import to PCS 7, the hardware components end up in PCS 7 HW Config. Via the right-hand mouse button all the HW components that are enabled for the set PCS 7 version can be created. The following devices are supported: PROFINET PROFIBUS PA GSD data exchange Intelligent field devices PA/DP (Micromaster, SINAMICS (DriveES), Simocode) 15.3 Attributes of CM The data transfer now also takes into consideration the "Version" attribute of CM. Operating Manual, 01/2018, A5E AA 125

126 Import from PCS 7 to PAA 15.5 Importing digitally signed XML files 15.4 Managing PCS 7 libraries in COMOS Several libraries can now be imported into PAA. 1. Import of a PCS 7 library to a specific location in COMOS 2. Import of further libraries 3. Specification of the master library (is used during data exchange) All the libraries are then stored in COMOS at the specific location but structured hierarchically. By default, the name of the library in PAA is the PCS 7 project name. Editing libraries in the type configurator You can carry out the following actions in the type configurator: "Library" column Creation of CMT, enumerations and functions Updating the elements Moving and changing the elements "Structure" column Customizing the structure with drag&drop Creation of variants of CMT 15.5 Importing digitally signed XML files Note Security when performing data exchange via XML format Access to the transfer medium/transfer directory: When using the indirect data exchange via XML format between PAA and PCS 7, ensure that the transfer medium or the transfer directory of the XML files is only accessible to authorized persons. Digitally signed XML files: To describe the origin and integrity of the XML data, you can sign the XML file digitally during the data exchange in XML format. This corresponds to the requirements of the PCS 7 security concept. By checking the digital signature, you ensure that the XML file on the transfer medium has not been modified. The digital signature on the XML file is deactivated by default. Activating the digital signature is recommended. See also chapter Overview of data exchange with PCS 7 (Page 15). 126 Operating Manual, 01/2018, A5E AA

127 Import from PCS 7 to PAA 15.6 Importing a PCS 7 project Requirement To import a signed XML file, the certificate of the user that is signing must be available on the PC. This certificate contains the "Public Key" that is required to identify the signature of the XML file. The certificate of the user that is signing must be stored in the Windows "MMC" console under "Own user > Certificates". The corresponding "CA" certificate must be saved in the "MMC" console under "Trusted Root Certificates". Procedure To use the digital signature in the PCS 7 project, in the plugin "Import / Export PCS 7" in the "Import" tab in the "Project selection" control group, activate the option "XML signature". Standards applied The RSA asymmetric signature procedure is used, according to standard "PKCS#1" (see " The attributes of the certificate are described in the certificate definition under " Importing a PCS 7 project Requirement Export from PAA to PCS 7 is complete. See chapter Export from PAA to PCS 7 (Page 115). Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter "Import" tab (Page 145). 3. To select a PCS 7 project or an XML file as the source for the import, click on the "..." button next to the "PCS 7 project path / XML path" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. The import expects that a signed XML file is to be transferred. See also chapter Importing digitally signed XML files (Page 126). 4. Enable the required options for the "Filter" control group. 5. In the "Automation Tree project/library" list, select the target project to be imported. 6. Click on the "Import" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). Operating Manual, 01/2018, A5E AA 127

128 Import from PCS 7 to PAA 15.7 Importing the technological hierarchy 7. Click on the "Import objects from B to A" button. 8. Confirm your entries. Result The PCS 7 project is imported along with the selected objects. Errors, warnings, and messages relating to the import are displayed in the status window. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). See also Importing the technological hierarchy (Page 128) Importing the hardware configuration (Page 130) Importing control modules (Page 129) 15.7 Importing the technological hierarchy Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter "Import" tab (Page 145). 3. To select a PCS 7 project or an XML file as the source for the import, click on the "..." button next to the "PCS 7 project/library" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. The import expects that a signed XML file is to be transferred. See also chapter Importing digitally signed XML files (Page 126). 4. To select the source project to be imported, click on the "..." button in the "PCS 7 project path / XML path" line. The "Project selection" dialog opens. 5. Select the "Project > Plant hierarchy" option in the "Filter" control group. 6. In the "Automation Tree project/library" list, select the target project to be imported. 7. Click on the "Import" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 8. Click on the "Import objects from B to A" button. 9. Confirm your entries. Result The plant hierarchy from PCS 7 is imported. If a plant hierarchy already exists, the "Data transfer - Generate/import" dialog synchronizes the hierarchy folders with one another. 128 Operating Manual, 01/2018, A5E AA

129 Import from PCS 7 to PAA 15.9 Importing control modules See also Effects of importing the plant hierarchy (Page 129) 15.8 Effects of importing the plant hierarchy Requirement The plant hierarchy from PCS 7 was imported. See chapter Importing the technological hierarchy (Page 128). Effects of synchronization on existing hierarchy folders "Delete object in target" option: Deactivated Hierarchy folders are not deleted. Hierarchy folders that already exist are not duplicated. Effects of synchronization on a new hierarchy folder in PCS 7 Hierarchy folders from PCS 7 that are not available in PAA are added to the plant hierarchy of the "DSC Structure" node Importing control modules Requirements To import control modules into PAA, the following information must be available for each control module in PCS 7: Plant hierarchy Control module type Parameters and signals used Note No import of characteristic-related data types Characteristic-related data types from PCS 7 are not available in PAA. When you create parameters below commands and statuses, use the predefined data types in PAA. The control module type must already exist in PAA. Operating Manual, 01/2018, A5E AA 129

130 Import from PCS 7 to PAA Importing the hardware configuration Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter "Import" tab (Page 145). 3. To select a PCS 7 project or an XML file as the source for the import, click on the "..." button next to the "PCS 7 project path / XML path" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. The import expects that a signed XML file is to be transferred. See also chapter Importing digitally signed XML files (Page 126). 4. Select the PCS 7 source project to be imported. 5. Select the "CM instances" option in the "Filter" control group. 6. In the "Automation Tree project/library" list, select the target project to be imported. 7. Click on the "Import" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). 8. Click on the "Import objects from B to A" button. Result The control modules are imported to the current PAA project. See also Importing control module types (Page 28) Importing the hardware configuration Requirements The hardware is available in the PCS 7 project. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter "Import" tab (Page 145). 3. To select a PCS 7 project or an XML file as the source for the import, click on the "..." button next to the "PCS 7 project path / XML path" field. Recommendation: If you wish to export an XML file, also activate the "XML signature" option. The import expects that a signed XML file is to be transferred. See also chapter Importing digitally signed XML files (Page 126). 130 Operating Manual, 01/2018, A5E AA

131 Import from PCS 7 to PAA Importing ET 200SP HA from PCS 7 4. Select the PCS 7 source project to be imported. 5. Select the "Hardware" option in the "Filter" control group. 6. If you also wish to export the hardware parameters, then in addition, activate the option "Project > Hardware > Extended parameters". See also chapter Extended hardware parameters (Page 88). 7. In the "Automation Tree project/library" list, select the target project to be imported. 8. Click on the "Import" button. The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 141). Note No full synchronization in Automation Interface PC stations and other devices that cannot be configured using the hardware configuration are not currently synchronized via the Automation Interface. Make sure that these devices are not selected in the "Data transfer Generate/import" dialog. If, in exceptional cases, error messages also appear for other devices, please contact Support. 9. Click on the "Import objects from B to A" button. Result The hardware is imported to the current PAA project. If you have activated the "Extended parameters" option, when importing the hardware options in PAA, the tab "Attributes > Extended automation" will be created. The extended hardware parameters will be stored in this tab Importing ET 200SP HA from PCS 7 Requirements The PCS 7 project with ET 200SP HA is created. The following configurations are possible: ET 200SP HA with single PROFINET interface module ET 200SP HA with redundant PROFINET interface module Note Et 200SP HA can be imported without Configuration plan, EI&C symbol, Assembly plan and external properties. Operating Manual, 01/2018, A5E AA 131

132 Import from PCS 7 to PAA Importing ET 200PA SMART from PCS 7 to PAA Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter Importing the hardware configuration (Page 130). Result The hardware is imported to the current PAA project Importing ET 200M from PCS 7 to PAA Requirements The PCS 7 project with ET 200M is created. The folowing configurations are possible: ET 200M with single PROFIBUS interface module ET 200M with redundant PROFIBUS interface module ET200M with PROFINET interface module Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter Importing the hardware configuration (Page 130). Result The hardware is imported to the current PAA project. The physical structure is created including the bus modules and Profile rail Importing ET 200PA SMART from PCS 7 to PAA Requirements The PCS 7 project with ET 200PA SMART is created. The following configurations are possible: ET 200PA SMART with single PROFIBUS interface module ET 200PA SMART with redundant PROFIBUS interface module 132 Operating Manual, 01/2018, A5E AA

133 Import from PCS 7 to PAA Importing ET 200iSP from PCS 7 Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter Importing the hardware configuration (Page 130). Result The hardware is imported to the current PAA project and the new physical structure is created including the bus modules and profile rail Importing ET 200iSP from PCS 7 Requirements The PCS 7 project with ET 200iSP is created. The following configurations are possible: ET 200iSP with single PROFIBUS interface module ET 200iSP with redundant PROFIBUS interface module Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. 2. Select the "Import" tab. See also chapter Importing the hardware configuration (Page 130). Result The hardware is imported to the current PAA project and the new physical structure is created including the bus modules, terminal modules and profile rail. Operating Manual, 01/2018, A5E AA 133

134 Import from PCS 7 to PAA Importing ET 200iSP from PCS Operating Manual, 01/2018, A5E AA

135 Working with reports Signal connections on Function diagram When the Function diagram is opened, the connection between the control module signal and the connected unit signal is displayed. It is possible to navigate to the IO channel that is implemented with the channel request of the signal. See alos chapter Working with negations (Page 36). Note Before using Print or PDF-Export of function diagrams, first do the Evaluation of the reports. Do this in the menu "Documents > Evaluate", drag&drop the start object into the "Start object(s)" field, select all the functional diagrams and click "Execute". In the backround all the function diagrams will be opened, all relevant Parameter and Signal objects are placed and connected and closed again. After that you can be sure that the report has all the relevant information available Assembly plan Requirement You have created a station of the type SIMATIC 400 You have created a distributed I/O of the type ET 200M or ET 200iSP or ET 200SP HA or ET 200PA SMART Benefits The Assembly plan shows the mounting rail with the individual components and evaluates the additional information, such as the power loss. Configuration To hide the "Power loss" table and the details on the Assembly plan, deactivate the options on the "Attributes > Design" tab in the properties of the report. Operating Manual, 01/2018, A5E AA 135

136 Working with reports 16.3 I/O report Changing the Assembly plan for ET 200M The Assembly plan is used to represent the setup of the components with additional information like Power loss or the devices on rack/profile rail. Note Only the Rails 483mm/530mm/620mm are supported. The following configurations can be shown on the Assembly plan based on the new HW structure: Single and redundant PS Single and redundant IM for Profibus Single IM for Profinet Procedure 1. Open the HW configuration tool. 2. Select the I/O - ET 200M tab and add any valid configuration including Rack: Profile rail, 483mm. 3. Click Create and "OK" to close the "Hardware configuration tool". 4. Open the Assembly plan, observe & close it. 5. Click "Apply" or "OK". 6. Open Assembly plan & observe. Result Assembly plan is updated according to the changed device (e.g. Profile rail, 483mm to Profile rail, 530mm) I/O report Requirement The "Locations" tab is selected in the Navigator. A cabinet has been created. Benefits You create the I/O report below the cabinet. The report provides an overview of the utilized and free channels per cabinet. 136 Operating Manual, 01/2018, A5E AA

137 Working with reports 16.4 Bill of materials Configuration In the properties of the report, you configure how the channels are to be displayed in the report on the "Attributes > Design" tab. You can combine the two options or select no option at all. Option "Grouped" "Detailed" Description If this option is activated, the objects are displayed sorted by their MLFB. You get an overview of the number of identical objects. If this option is activated, the objects are displayed sorted by owner Bill of materials Requirement The "Locations" tab is selected in the Navigator. A cabinet has been created. Benefits You create the bill of materials below the cabinet. The bill of material provides an overview of all objects that are relevant for orders. Bill of material with bundles Contains Bundle MLFBs which each include a collection of objects. Bill of material without bundles Does not include Bundle MLFBs. All objects are listed separately. Configuration In the properties of the report, you configure how the objects are to be displayed in the report on the "Attributes > Design" tab. You can combine the two options or select no option at all. Option "Grouped" "Detailed" Description If this option is activated, the objects are displayed sorted by their MLFB. You get an overview of the number of identical objects. If this option is activated, the objects are displayed sorted by owner. Operating Manual, 01/2018, A5E AA 137

138 Working with reports 16.6 Configurable symbols 16.5 Configuration plan Requirement The "Locations" tab is selected in the Navigator. A cabinet has been created. Benefits You create the configuration plan below the cabinet. It shows a rough structure of the unit including all hardware components and all line and ring buses. The following objects are displayed: S7 400 stations ET200 stations Workstations Plant bus Terminal bus Place the required objects on the configuration plan with drag&drop and connect them Configurable symbols Adapting the symbols on a Function diagram is now possible. The following can be customized: Sequence of the connections Designation of the connections Position of the connections Block name Icon Logic blocks are allocated automatically to the runtime group. However, they are displayed on a separate CFC. All the functions of the CM are then also displayed here. The relationship between the CM and the functions is based on the input connections. If the space at the margins is not sufficient to display the input or output signals, an overflow page is created automatically. A grayed out full display of the blocks on the chart with the signals of the marginal circuits that did not fit onto the first page is displayed on this overflow page. 138 Operating Manual, 01/2018, A5E AA

139 Working with reports 16.7 Computer data sheet 16.7 Computer data sheet Requirement The "Locations" tab is selected in the Navigator. A workstation has been created. Benefits Create the computer data sheet beneath the workstation. The data sheet gives an overview of the configuration of the workstation. Information on the following topics is evaluated: Procurement Installation Hardware Other settings Software Licenses Configuration The computer data sheet evaluates the tabs Attribute > Computer Information" and Attribute > software" of the workstation. The information on the licenses is taken from the Licenses folder, which is parallel to the workstation in the Navigator. You can enter information directly into the computer data sheet. The attributes of the workstation are changed automatically. On the Attribute > software" tab of the workstation, you can import a CSV file or enter the information directly into the list. Operating Manual, 01/2018, A5E AA 139

140 Working with reports 16.7 Computer data sheet 140 Operating Manual, 01/2018, A5E AA

141 Reference Information in the "Data transfer - Generate/import" dialog Objective The "Data transfer - Generate/Import" dialog is the interface of the Automation Interface. This dialog enables you to import engineering data both in the engineering project and in the base project. Log file All events that occur during data transfer are logged in the status window. At the top edge of the status window, you can set which system messages are to be output: "Errors" Indicates an error. The import/export cannot take place if errors are detected. "Warnings" Shows information on errors that do not actually prevent an import/export but may lead to an unwanted result. "Messages" Logs the import/export process. The entries in the status window are context-sensitive. The selection in the source text jumps to the relevant place when you activate the entry by double-clicking on it in the status window. "Delete in target" option If the option is activated, it has the following effect: There are objects to be deleted in the import process: The objects exist in PAA but not in the import file. These objects are highlighted in blue in the "Data transfer - Generate/import" dialog. No full synchronization in Automation Interface PC stations and other devices that cannot be configured using the hardware configuration are not currently synchronized via the Automation Interface. Make sure that these devices are not selected in the "Data transfer Generate/import" dialog. If, in exceptional cases, error messages also appear for other devices, please contact Support. The properties of statuses and commands are overwritten during each export to PCS 7. These are therefore highlighted in different colors for each comparison in the Automation Interface. Operating Manual, 01/2018, A5E AA 141

142 Reference 17.2 Navigator Calling help on the "Data transfer - Generate/import" dialog 1. Open the "Data transfer - Generate/import" dialog. 2. Click the "Help" button. See also Export from PAA to PCS 7 (Page 115) Import from PCS 7 to PAA (Page 125) 17.2 Navigator "Units" tab In the "Units" tab, configure the plant hierarchy (PH) and execute software engineering. Icon Tab Description "Units" Plant hierarchy The following nodes are also available here: node contains the following objects: "Templates" Contains the imported control module library with the control module types from PCS 7. This folder is only created once the "Create templates" function has been executed. Icon Description Project library Group folder for enumeration types Enumeration Template container Group folder for CM types CM type/variant collection CMT template Message Signal Group folder for commands Command CM assignment Parameters Group folder for functions 142 Operating Manual, 01/2018, A5E AA

143 Reference 17.2 Navigator Icon Description Function Group folder for status Status DCS structure: Icon Description DCS structure Hierarchy folder Hierarchy folder with S88 type definition "Unit" Hierarchy folder with S88 type definition "Subunit" Unit structure: Icon Description Project DCS structure Plant Unit Subunit A50 EI&C Position "Locations" tab The "Locations" tab is used to configure the objects for the hardware. Icon Tab Description "Locations" Configured hardware The following objects can be found in this tab according to the example in this documentation: Icon Description Project Plant Building Floor Room Cabinet Station Operating Manual, 01/2018, A5E AA 143

144 Reference 17.3 "Import / Export PCS 7" plugin Icon Description Rack Power supply Communication Central assembly 17.3 "Import / Export PCS 7" plugin Calling the "Import / Export PCS 7" plugin Objective Transfer of engineering data between PCS 7 and PAA. Procedure 1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Import / Export PCS 7" command. Result The "Import / Export PCS 7" plugin opens. The following tabs are available for transferring engineering data: "Import" tab See also chapter "Import" tab (Page 145). "Export" tab See also chapter "Export" tab (Page 147). 144 Operating Manual, 01/2018, A5E AA

145 Reference 17.3 "Import / Export PCS 7" plugin "Import" tab Objective After selecting a PCS 7 project, you import the selected objects on this tab from PCS 7 to PAA. Control group Control element Description "Project selection" The "PCS 7 project" option The activated option enables you to import a PCS 7 project file. The "XML file" option The "XML signature" option "PCS 7 project path / XML path" list "Select a project" button The activated option enables you to import an XML file. The activated option enables PAA to search through the selected XML file for a digital signature. See also chapter Exporting digitally signed XML files: (Page 117). In this list, you select the target project. Up to 10 PCS 7 or XML projects are displayed for each Windows user. The projects are stored in the user folder: <User> > AppData > Local > <Options file> Depending on the option selected, this button opens the "Project selection" window or the "Open" window. "Filter > Project" "Plant hierarchy" option The following objects are included in the selected source project: "CM instances" option "Hardware" option "Extended parameters" option All PCS 7 objects of the plant hierarchy Following the import, the objects are created in the "DCS structure" node. The following objects are included in the selected source project: All PCS 7 instances Following the import, the objects are created in the "@Template" node. The following objects are included in the selected source project: All hardware objects from PCS 7 Following the import, the objects are created in the "DCS structure" node. The following objects are included in the selected source project All hardware objects from PCS 7 The extended hardware parameters of the objects See also chapter Extended hardware parameters (Page 88). After the import, the "Attribute > Advanced automation" tab is displayed with the hardware objects. Operating Manual, 01/2018, A5E AA 145

146 Reference 17.3 "Import / Export PCS 7" plugin Control group Control element Description "Filter > Library" "CM types" option The following objects are included in the selected source project: "Enumerations" option "Commands & status" option All PCS 7 types After the import, the objects are created as follows: "Templates" node: "PCS 7 template > PCS 7 Lib library folder" The following objects are included in the selected source project All enumerations from PCS 7 See also chapter Management of enumerations (Page 41). The following objects are included in the selected source project: The command and status library from PCS 7. "Selective transfer" "Functions" option "Import" button "Selected PH / CM" The following objects are included in the selected source project All functions from PCS 7 See also chapter Creating functions (Page 45). Starts the import Allows selective transfer of individual levels. "Filter:" "Filter:" table Displays errors, warnings, and messages See also Importing control module types (Page 28) Importing a PCS 7 project (Page 127) Importing the technological hierarchy (Page 128) Importing control modules (Page 129) Importing the hardware configuration (Page 130) Calling the "Import / Export PCS 7" plugin (Page 144) 146 Operating Manual, 01/2018, A5E AA

147 Reference 17.3 "Import / Export PCS 7" plugin "Export" tab You export the selected objects from PAA to PCS 7 on this tab. Control group Control element Description "Project selection" The "PCS 7 project" option The activated option enables you to import a PCS 7 project file. The "XML file" option The "XML signature" option "PCS 7 project path / XML path" field "Select a project" button Table The activated option enables you to import an XML file. The activated option enables the selected XML file to be digitally signed. See also chapter Exporting digitally signed XML files: (Page 117). Shows the file selected for import. In this list, you select the target project. Up to 10 PCS 7 or XML projects are displayed for each Windows user. The projects are stored in the user folder: <User> > AppData > Local > <Options file> Depending on the option selected, this button opens the "Project selection" window or the "Open" window. Select the stations that you want to take part in the export in the "Select" column. "Filter > Project" "Plant hierarchy" option The following objects are included in the selected source project: "CM instances" option "Hardware" option "Extended hardware" option All objects of the plant hierarchy in the "Project > PV Plant view" node See also chapter Exporting the technological hierarchy (Page 119). The following objects are included in the selected source project: All instances in the "Project > PV Plant view" node See also chapter Exporting instances (Page 119). The following objects are included in the selected source project: All hardware objects in the "Project" node See also chapterexporting the hardware configuration (Page 121). The following objects are included in the selected source project: All hardware objects in the "Project" node The extended hardware parameters of the hardware objects See also chapter Extended hardware parameters (Page 88). Operating Manual, 01/2018, A5E AA 147

148 Reference 17.4 Reference to the mapping table Control group Control element Description "Filter > Library" "CM types" option The following objects are included in the selected source project: "Enumerations" option "Commands & status" option All types in the "Project > PV Plant view" node The following objects are included in the selected source project: All enumerations in the "Project" node See also chapter Management of enumerations (Page 41). The following objects are included in the selected source project: The command and status library "Selective transfer" "Functions" option "Export" button "Selected PH / CM" The following objects are included in the selected source project: All functions in the "Project" node See also chapter Creating functions (Page 45). Starts the export Allows selective transfer of individual levels. "Filter:" "Filter:" table Displays errors, warnings, and messages See also Calling the "Import / Export PCS 7" plugin (Page 144) Exporting a PAA project (Page 118) 17.4 Reference to the mapping table Objective You can assign PAA attributes to the inserted PCS 7 control modules in the mapping table. Calling a mapping table 1. Open the properties of a control module. 2. Select the "Attributes > Automation Interface" tab. 3. Click the "Open mapping table" button. 148 Operating Manual, 01/2018, A5E AA

149 Reference 17.5 Reference to the navigation assistant Design You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Configuring a mapping table". Control element "Insert in template" button "Attribute" column "Description" column "Link type" column "Source object" column "Property" column "Value" column Description Saves the assignments in the template of the control module type used Attribute to which the information is transferred Description of the set target attribute To change the link type, double-click in this column and select the required type from the list. "Static" The linked value is not immediately accepted in the case of a static link. You initiate the use manually. A static link only serves as a basis of comparison. The content is not applied. "Dynamic" In the case of a dynamic link, the contents are always transferred from the source object to the attribute. "Full dynamic" (recommended) All properties of the linked attributes are automatically transferred in both directions. Object from which the information is read The object can be set as follows: Via drag&drop from within the Navigator In the navigation assistant See also chapter Reference to the navigation assistant (Page 149). Contains the property that is being read out If necessary, double-click in this column to select another property from the list. Contains a preview of the information to be transferred See also Configuring the mapping table of the signal designations (Page 109) Adopting a mapping table as a template (Page 112) 17.5 Reference to the navigation assistant You use the navigation assistant if you do not know the position of the source object in the unit tree. You can find additional information on this topic in the "COMOS Platform Administration" manual, keyword ""Properties" context menu: "Object evaluation" tab". Operating Manual, 01/2018, A5E AA 149

150 Reference 17.6 "Type configurator" reference plugin See also Using the navigation assistant (Page 111) 17.6 "Type configurator" reference plugin Menu bar Icon Tooltip Description "Refresh" "Create command and status library" "Functions" "Graphical properties" By pressing this button, you refresh the view in the plugin. By pressing this button you create initially the command and status library. See also chapter Creating a global command and status library (Page 43). Use this button to display a list of all functions that are available as standard. See also chapter Creating functions (Page 45). Adapting the fonts on reports. "Variant overview" "Configure message system" Shows the different versions of CMT. Adapting notifications / messages "Functions" column If you click on the "Functions" button in the menu bar, this column is displayed. Icon Tooltip Description "Select all" "Deselect all" "Generate functions" Use this button to select all the listed functions. Use this button to deselect all the selected functions. Use this button to generate all the selected functions. The selected functions are created in the "@Template > PCS 7 > Template-Container > Functions" node and displayed in the column "Type library" of the Navigator. 150 Operating Manual, 01/2018, A5E AA

151 Reference 17.6 "Type configurator" reference plugin "Types library" column Icon Tooltip Description "Insert New Object" "Copy" "Paste" "Delete" "Filter" By pressing this button you create new control module types, enumerations and functions. See also chapter Creating a control module type (Page 30), chapter Creating a global command and status library (Page 43), chapter Creating enumeration types (Page 41) and chapter Creating functions (Page 45). By pressing this button you copy the selected type in the cache. See also chapter Creating a control module type (Page 30). By pressing this button you paste the type from the cache. By pressing this button, you delete the selected type. See also chapter Creating a control module type (Page 30). By pressing this button you filter the display of the "Type library" column. Enable the button for the kind of type that you would like to display. "Type structure" column Icon Tooltip Description "Expand all" "Collapse all" "Copy" By pressing this button you expand the entire subordinate structure of the selected type. By pressing this button you collapse the entire subordinate structure of the selected type. By pressing this button you copy the selected object in the cache. "Paste" "Delete" "Edit step sequence" By pressing this button you paste the object copied in the cache. Use this button to delete the selected object including the subordinate objects. If the type is selected, the button is not active. By pressing this button you open the selected step sequence for editing on the function plan. This button is enabled only if you have selected an initial step sequence. Operating Manual, 01/2018, A5E AA 151