Automation Base 1 - Siemens · Table of contents Automation Base 1.0 6 Operating Manual, 10/2015 SIMATIC PCS 7 ... interface 1 Objective The plugins in the menu "Plugins > Automation

SIMATIC

PCS 7Automation Base 1.0

Operating Manual

10/2015 SIMATIC PCS 7 Automation Base V 1.0A5E36172379-AA

Objectives and performance scope of the data interface 1Terminology 2Overview of data exchange with PCS 7 3Requirements in PCS 7 4Preparations 5Management of control module types 6Management of equipment module types 7Management of enumerations 8"Type configurator" plugin 9Creating the Master Version 10Update type usages 11Using "Excel import" 12Engineering in PAB 13Editing large quantities of connections 14Linking attributes from PAB and PCS 7 15Exporting from PAB to PCS 7 16Importing from PCS 7 to PAB 17Working with reports 18Reference 19

Legal informationWarning 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.

DANGERindicates that death or severe personal injury will result if proper precautions are not taken.

WARNINGindicates that death or severe personal injury may result if proper precautions are not taken.

CAUTIONindicates that minor personal injury can result if proper precautions are not taken.

NOTICEindicates 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 PersonnelThe 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 productsNote the following:

WARNINGSiemens 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.

TrademarksAll 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 LiabilityWe 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 AGDivision Process Industries and DrivesPostfach 48 4890026 NÜRNBERGGERMANY

A5E36172379-AAⓅ 05/2016 Subject to change

Copyright © Siemens AG 2015.All rights reserved

Table of contents

1 Objectives and performance scope of the data interface.............................................................................7

2 Terminology..................................................................................................................................................9

3 Overview of data exchange with PCS 7.....................................................................................................11

4 Requirements in PCS 7..............................................................................................................................15

5 Preparations...............................................................................................................................................17

5.1 Creating a new engineering project.......................................................................................17

5.2 Opening a planning project....................................................................................................17

5.3 Creating the DCS structure....................................................................................................18

5.4 Standard ISA 88 in the unit structure.....................................................................................19

6 Management of control module types........................................................................................................21

6.1 Structure of control module types..........................................................................................21

6.2 Importing control module types..............................................................................................24

6.3 Managing variants using optional blocks...............................................................................25

6.4 Creating a control module type..............................................................................................26

6.5 Creating control modules.......................................................................................................27

6.6 Creating a CM in the DCS structure.......................................................................................27

6.7 Creating aggregated CMTs....................................................................................................28

7 Management of equipment module types..................................................................................................31

7.1 Creating an equipment module (type)....................................................................................31

7.2 Copying an equipment module (type)....................................................................................32

7.3 Deleting an equipment module (type)....................................................................................32

7.4 Creating control variables......................................................................................................33

7.5 Creating messages................................................................................................................33

7.6 Creating subordinate control modules...................................................................................34

7.7 Creating mapping for a control module..................................................................................35

7.8 Assigning the control module mapping to a control module...................................................36

7.9 Creating step sequences.......................................................................................................36

7.10 Editing step sequences..........................................................................................................37

7.11 Using commands and statuses in step sequences................................................................38

7.12 Description of the characteristics...........................................................................................40

7.13 Creating characteristics..........................................................................................................41

Automation Base 1.0Operating Manual, 10/2015 SIMATIC PCS 7 Automation Base V 1.0, A5E36172379-AA 3

7.14 Using characteristics in step sequences................................................................................42

7.15 Interconnecting signals and parameters of control modules with characteristics..................43

7.16 Working with negations..........................................................................................................44

7.17 Using references....................................................................................................................45

7.18 Work with basic requirements................................................................................................46

8 Management of enumerations....................................................................................................................49

8.1 Create enumeration types......................................................................................................49

8.2 Using enumerations...............................................................................................................50

9 "Type configurator" plugin..........................................................................................................................51

9.1 Opening the "Type configurator" plugin.................................................................................51

9.2 Creating a global command and status library.......................................................................51

9.3 Creating functions..................................................................................................................52

10 Creating the Master Version.......................................................................................................................55

11 Update type usages....................................................................................................................................57

12 Using "Excel import"...................................................................................................................................59

13 Engineering in PAB....................................................................................................................................61

13.1 Functional characteristics of the hardware objects................................................................61

13.2 Information on identifying hardware components..................................................................61

13.3 Hardware engineering in the Navigator..................................................................................6313.3.1 PROFINET and PROFIBUS...................................................................................................6313.3.2 Configuring a SIMATIC station...............................................................................................6713.3.3 Configuring the central processing unit (CPU).......................................................................6813.3.4 Creating an interface module as distributed I/O.....................................................................6913.3.5 Equipping interface modules with I/O modules......................................................................6913.3.6 Configuring IO modules.........................................................................................................7013.3.7 Creating a redundant SIMATIC station..................................................................................7113.3.8 Creating a redundant I/O........................................................................................................7313.3.9 Using the DP/PA coupler.......................................................................................................74

13.4 Editing hardware engineering via engineering tasks..............................................................7513.4.1 Assigning a field bus to a DP slave via a task........................................................................7513.4.2 Assigning redundant fieldbus via engineering task................................................................76

13.5 Hardware engineering with the configuration tool..................................................................7713.5.1 Opening the configuration tool...............................................................................................7713.5.2 Creating hardware with the configuration tool........................................................................7713.5.3 Creating hardware including spare I/O channels...................................................................7813.5.4 Hardware including spare I/O space for modules is created..................................................7913.5.5 Creating redundant signal modules.......................................................................................7913.5.6 Creating redundant stations...................................................................................................8013.5.7 Creating licenses....................................................................................................................80

13.6 Extended hardware parameters.............................................................................................81

13.7 Software engineering in the Navigator...................................................................................82

Table of contents

Automation Base 1.04 Operating Manual, 10/2015 SIMATIC PCS 7 Automation Base V 1.0, A5E36172379-AA

13.7.1 Notes on the plant hierarchy..................................................................................................8213.7.2 Working with channel requests..............................................................................................8313.7.3 Optional: Creating and configuring process tags...................................................................8413.7.4 Optional: Linking hardware and software: Implementing channels........................................85

13.8 Editing software engineering using engineering tasks...........................................................8513.8.1 Engineering tasks...................................................................................................................8513.8.2 Displaying the "SW interface" tab and creating tasks............................................................8613.8.3 Assigning a control module type to the DCS structure...........................................................8713.8.4 Assigning a control module type to a function........................................................................8813.8.5 Assigning an equipment module to the DCS structure..........................................................8813.8.6 Assigning a station to a position.............................................................................................8913.8.7 Assigning control module types to the DCS structure in bulk................................................90

13.9 Using symbol tables...............................................................................................................9113.9.1 Importing symbolic addresses into a symbol table.................................................................9113.9.2 Refreshing the symbol table...................................................................................................91

13.10 Engineering in the function diagram.......................................................................................9213.10.1 Editing control modules on the function diagram...................................................................9213.10.2 Editing the logic on function diagrams...................................................................................9313.10.3 Example for interlock logic on function diagrams...................................................................9413.10.4 Creating logic levels on transitions.........................................................................................94

14 Editing large quantities of connections.......................................................................................................97

15 Linking attributes from PAB and PCS 7......................................................................................................99

15.1 Configuring the mapping table of the signal designations......................................................99

15.2 Using the navigation assistant.............................................................................................101

15.3 Example of an assignment...................................................................................................102

15.4 Adopting a mapping table as a template..............................................................................102

16 Exporting from PAB to PCS 7...................................................................................................................105

16.1 Exporting digitally signed XML files:.....................................................................................105

16.2 Exporting a PAB project.......................................................................................................106

16.3 Exporting to old PCS 7 V7 projects......................................................................................107

16.4 Exporting the technological hierarchy..................................................................................107

16.5 Exporting instances..............................................................................................................108

16.6 Exporting types....................................................................................................................109

16.7 Exporting the hardware configuration..................................................................................109

17 Importing from PCS 7 to PAB...................................................................................................................111

17.1 Importing digitally signed XML files......................................................................................111

17.2 Importing a PCS 7 project....................................................................................................112

17.3 Importing the technological hierarchy..................................................................................113

17.4 Effects of importing the plant hierarchy................................................................................113

17.5 Importing control modules....................................................................................................114

Table of contents


17.6 Importing the hardware configuration...................................................................................115

18 Working with reports.................................................................................................................................117

18.1 Assembly Plan.....................................................................................................................117

18.2 I/O Report.............................................................................................................................117

18.3 Bills of materials...................................................................................................................118

18.4 Configuration plan................................................................................................................118

18.5 Computer data sheet............................................................................................................119

19 Reference.................................................................................................................................................121

19.1 Information in the "Data transfer - Generate/import" dialog.................................................121

19.2 Navigator..............................................................................................................................122

19.3 "Import/Export PCS 7" plugin...............................................................................................12419.3.1 Calling the "Import/Export PCS 7" plugin.............................................................................12419.3.2 "Import" tab..........................................................................................................................12519.3.3 "Export" tab..........................................................................................................................127

19.4 Reference to the mapping table...........................................................................................129

19.5 Reference to the navigation assistant..................................................................................130

19.6 "Type configurator" reference plugin....................................................................................130

19.7 “Excel import" reference plugin............................................................................................132

19.8 Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7".................133

Table of contents


Objectives and performance scope of the data interface 1Objective

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 Automation Base (PAB) project and the PCS 7 project, they can work in either of the two programs.

The objective is a "digital plant" through integrated engineering with PAB 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)

● Export of equipment module types (EMTs) and equipment modules (EMs)

● Bidirectional import/export of control modules and parameters, messages and signals

● Update of instances of control modules and equipment module types

● 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

● Export of interlock logic to function diagrams (IEC blocks connected across documents) from PAB to PCS 7Only blocks that are connected to at least one input parameter of a CM/EM or CMT/EMT are exported.

Renamed objectsRenamed objects are recognized once again during data exchange and are contrasted during data comparison.

Renaming is detected for the following objects:

● Unit hierarchy nodes

● Equipment module type (EMT)

● Equipment modules (EM)

● Control module types (CMT)

● Control module (CM)


● Functions

● Signal parameter (CV)

● Parameter of a technical function (EPH)

● Sequencer of a technical function (EPH)

● Features of an equipment phase (EPH)

● Command

● Status

● Enumeration

● Enumeration value

● Hardware:

– Station, slave (central, slave)

– Subnetwork, bus (global subnet)

ExceptionsThe following graphic data is ignored after the import in PAB:

● 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" See also chapters Importing from PCS

7 to PAB (Page 111) and Exporting from PAB to PCS 7 (Page 105).

"Type configurator" See also chapters Management of con‐trol module types (Page 21) and "Type configurator" plugin (Page 51).

"Connection manager" See also chapter Editing large quanti‐ties of connections (Page 97).

"Excel import" See also chapter Using "Excel import" (Page 59).

The following plugin is available in the "Plugins" menu:

Name Icon Usage"Assembly Updater" See also chapter Update type usages

(Page 57).

Objectives and performance scope of the data interface


Terminology 2Important terminology

● Automation InterfaceThe Automation Interface is an independent, standardized interface for the exchange of engineering data. The user interface for the Automation Interface has the dialog title "Data transfer - Generate/Import".

● Signal In PCS 7: The designation "signal" is only used when the signal is connected to a hardware address.In PAB: Signals are used regardless of assignment to hardware.

SynonymsThe following terms each have the same meaning:

● Block message, message

Abbreviations

PAB PCS 7 Automation BaseEMT Equipment Module TypeEM Equipment ModuleEPH Equipment PhaseCMT Control Module TypeCM Control ModuleSubCM Subordinate Control Module

See alsoInformation on identifying hardware components (Page 61)


Terminology


Overview of data exchange with PCS 7 3Bidirectional data exchange

During data exchange between PAB and PCS 7, data can be transferred and synchronized bidirectionally.

For transfer and synchronization, there are the following options:

● Direct data exchange: if PAB and PCS 7 are installed on the same PC. As such, the types and instances of equipment modules or control modules from PAB 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 PAB 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 PAB or the SIMATIC Manager.Then import the XML file that was generated by PAB or PCS 7 and proceed in the reverse order in SIMATIC Manager or PAB. Synchronization is also performed during an import. Then the alterations to the target can be deleted or applied.

NoteSecurity when performing data exchange via XML format ● Access to the transfer medium/transfer directory:

When using the indirect data exchange via XML format between PAB 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 105).

During data exchange, not only the types and instances of equipment modules or control modules from PAB and PCS 7 can be read out and contrasted via the import service of the Automation Interface (AI). The plant hierarchy, types and instances of control modules, hardware configuration etc. can also be contrasted. In doing so, alterations to the target can be deleted or applied.


NoteData exchange of types and instances

Types and instances of control modules can be transferred bidirectionally.

Types and instances of equipment modules are only transferred from PAB to PCS 7.

Perform at least the following sequences to exchange engineering data between PAB and SIMATIC PCS 7:

Overview of data exchange with PCS 7


Preparation1. Prepare PCS 7

See chapter Requirements in PCS 7 (Page 15).

2. Preparing PAB

– Preparing the PAB planning projectSee chapter Opening a planning project (Page 17).

– Creating the DCS structureSee chapter Creating the DCS structure (Page 18).

3. Managing control module types in PAB

– Importing control module types in PABSee chapter Importing control module types (Page 24).

– Configure a mapping table for the control module typesSee chapter Configuring the mapping table of the signal designations (Page 99).

– Creating control module types in PAB.See chapter Creating a control module type (Page 26).

Engineering in PAB1. Hardware engineering in the "Locations" tab

See chapter Hardware engineering in the Navigator (Page 63).

– 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" tabSee chapter Software engineering in the Navigator (Page 82).

– Signal engineering

– Implement channelsSee chapter Optional: Linking hardware and software: Implementing channels (Page 85).See chapter Working with channel requests (Page 83).This step links the hardware engineering and the software engineering.

3. Assigning control modulesEditing software engineering using engineering tasks (Page 85)

4. Create and manage equipment phases Management of equipment module types (Page 31)

5. Create or update symbol tableSee chapter Using symbol tables (Page 91).

6. Create interlock logic on function diagramsSee chapter Engineering in the function diagram (Page 92).



Finishing processes1. Linking PAB attributes and PCS 7 attributes where applicable

See chapter Linking attributes from PAB and PCS 7 (Page 99).

2. Exporting from PAB to PCS 7See chapter Exporting from PAB to PCS 7 (Page 105).

3. Importing from PCS 7 to PABSee chapter Importing from PCS 7 to PAB (Page 111).

NoteAssigning exported objects

When you export objects from PAB to PCS 7, perform the assignment in PCS 7 subsequently, if necessary.



Requirements in PCS 7 4Requirements for control module types

In order to work with control modules in PAB, 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.

Requirement to use signals in the interlock logic on function diagrams The following conditions must be met before you can import the interlock logic of blocks from a PCS 7 project:

● The hardware driver block and its connections must be assigned to a plant connection at the plant interface in PCS 7.

See alsoPreparations (Page 17)


Requirements in PCS 7


Preparations 55.1 Creating a new engineering project

Procedure1. 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 Project type"Engineering" Engineering projects"Base objects" Base projects"Templates" 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 "@30 > M00 > A20 > A10 > X01 > X20 Project presetting, SIMATIC PCS 7 V8.1".

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".

5.2 Opening a planning project

Requirement● The project structure "SIMATIC PCS 7 V8.1" is used.

See chapter Creating a new engineering project (Page 17).


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".

4. Open the project properties.

5. Check whether the project presetting "@30 > M00 > A20 > A10 > X01 > X20 Project presetting, SIMATIC PCS 7 V8.1” is being used.See also chapter Creating a new engineering project (Page 17).

5.3 Creating the DCS structure

IntroductionThe 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 V8.1 is set in the product properties.

See also chapter Creating a new engineering project (Page 17).

Procedure1. 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 "PH hierarchy folder" command in the context menu of the "DCS structure" node.

3. Select the "PH hierarchy folder" command in the context menu of the "PH01 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.

Preparations5.3 Creating the DCS structure


Using the pipe sign "|"A pipe sign "|" can be entered in the name of a PAB 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 "|".

5.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 18).

Procedure1. Open the first level of the plant hierarchy in the properties of a folder.

2. Select the "Attributes > Automation Standard" tab.

3. In the "S88 type definition" list, select the entry “Unit".

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.


7. In the "S88 type definition" list, select the entry "Subunit".

8. Confirm your entries.The icon and the description of the object change in the Navigator.

Preparations5.4 Standard ISA 88 in the unit structure


Preparations5.4 Standard ISA 88 in the unit structure


Management of control module types 66.1 Structure of control module types

Requirement● The planning project is open.

See chapter Opening a planning project (Page 17).


Structure

① PAB-specific, permanent folder② General collecting folder for all templates of the PCS 7 interface ③ A collecting folder ④ Control module type or variants⑤ Parameter or block variable of the control module⑥ Block of the control module⑦ Command⑧ Status ⑨ Mapping table for linking PCS 7-specific attributes with PAB-specific attributes⑩ Signal⑪ PCS 7-specific attributes⑫ Attributes for controlling the behavior of control modules in PAB⑬ 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.

⑭ Global command library⑮ Global status library

Management of control module types6.1 Structure of control module types


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> > @Template > @PCS 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 Standard" tab, "Optional" attribute is activated

See alsoImporting control module types (Page 24)

Managing variants using optional blocks (Page 25)

Management of control module types6.1 Structure of control module types


6.2 Importing control module types

Requirement● The project is open.


● The structure of control module types is clear.See chapter Structure of control module types (Page 21).

Procedure1. 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 125).

3. Select the file type of the import file:

– The "PCS 7 project" option: s7p

– The "XML file" option: xmlRecommendation: 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 111).

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 121).

8. Click on the "Import objects from B to A" button in the "Data transfer - generate/import" dialog.

ResultThe library with the control module types is imported into the PAB project and displayed in the "Units" tab as follows:

Node "@Template > @PCS 7 > Template-Container > CMTs > <Name CMT> Type/version 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 the @Template node.

Management of control module types6.2 Importing control module types


6.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 27) and chapter Importing control module types (Page 24).

● The "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 51).

● One of the possible combinations for optional blocks has not been used yet.

TargetGenerating versions for templates from which the control modules are derived.

Creating templates with versions 1. Select the control module type in the "Type structure" column.

2. Open the shortcut menu and select the “New version" 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.

ResultThe control module type versions are created in the "Units" tab:

● "@Template > @PCS 7 > Template-Container > CMTs > <CMT> Type/version collection > <CMT_Var1 >"

NoteAutomatic changes to variants

Structural changes to control module types are automatically written to the variants.

See alsoEngineering in PAB (Page 61)

Management of control module types6.3 Managing variants using optional blocks


6.4 Creating a control module type

RequirementThe "Type configurator" plugin is open. See also chapter Opening the "Type configurator" plugin (Page 51).

Procedure1. Select the "Insert new object > Control module types" command in the menu bar of the

plugin.The shell for a control module type is created in the "Types 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.

ResultThe 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.

NoteEditing control module types

Edit control module types only via the "Type configurator" plugin. Changes in the navigator are not applied in the plugin.

See alsoManagement of control module types (Page 21)

Management of control module types6.4 Creating a control module type


6.5 Creating control modules

Requirement● The "Type configurator" plugin is open.

See also chapter Opening the "Type configurator" plugin (Page 51).

● You have created a control module type.See also chapter Creating a control module type (Page 26).

Procedure1. 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 25).

5. Create the desired objects underneath the control module.To create messages, commands, and statuses, proceed as described for the equipment modules. See also chapter Management of equipment module types (Page 31).

NoteData types of parameters

When you create parameters below commands and statuses, use the predefined data types in PAB. Characteristic-related data types from PCS 7 are not available in PAB.


NoteEditing control module types

Edit control module types solely with the relevant plugins. Changes in the navigator are not included in the plugins.

See also"Type configurator" reference plugin (Page 130)

6.6 Creating a CM in the DCS structure

Requirement● The DCS structure has been created.

See also chapter Creating the DCS structure (Page 18).

Management of control module types6.6 Creating a CM in the DCS structure


Procedure1. Open the properties of the hierarchy folder in the DCS structure you want to link.

2. Select the "Tasks > SW interface" tab.

3. Check if the "Copy template" task is displayed and create it, if needed, using the shortcut menu command "New > Copy template".

4. Navigate to the CMT template.

5. Drag&drop the CMT template from the Navigator into the "Target object" column in the "SW interface" tab of the hierarchy folder.

6. Click the "Execute (selected)" button in the menu bar of the tab.


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.

Example

Linking a CM with position using a unit pointer1. Select the CM.

2. Open the properties of the CM.

3. Select the "General" tab.

4. Drag&drop the desired position from the unit structure into the "Unit" field.

NoteSetting 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 99).

6.7 Creating aggregated CMTs

IntroductionThe 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 26).

Management of control module types6.7 Creating aggregated CMTs


Procedure1. Select the "CMT control module types" folder in the Navigator.

2. Select the command "New > CMT collection" in the shortcut menu of the folder.The "CMT collection" folder is created parallel to the existing CMTs.

3. Select the command "New > Aggregated CMT template" in the shortcut menu of the "CMT collection" folder.The "Aggregated CMT template" object and below it a function diagram are created.

4. In the shortcut menu of the "Aggregated CMT template" object, select the command "Add CMT > Folder of the desired CMT > Desired CMT / variant of the CMT".

5. Optional: Rename the objects of the collection and the template object.

6. Repeat steps 4 and 5 for all CMTs that you want to add to the collection.

7. 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.

NoteNo exchange with PCS 7

Aggregated CMTs do not participate in data exchange with PCS 7 and are not exported.

8. Optional:

– 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 27).

NoteUpdating 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 57).





Management of equipment module types 77.1 Creating an equipment module (type)


Procedure1. Select the "Insert new object > Equipment module (type)" command in the menu bar of the

plugin.The shell for an equipment module is created in the "Type library" column. The name of the newly created shell is "EMT_<consecutive number>". The equipment module is displayed in the "Type structure" column. The equipment phase and its characteristics as well as the initial step sequence are located underneath. See also chapter Creating step sequences (Page 36).If no project has been created yet, a project is created. Any existing EMTs are listed.

2. Define the details of the equipment module (type) in the "Type attributes" column. If you have created a new equipment module (type), the "Name" field is selected automatically.

3. Right-click on the EMT in the "Type structure" column and select the "Insert new object > <desired object>" command in the context menu.The folder of characteristics cannot be renamed or deleted.


ResultThe shell of the equipment module is saved in the "Templates" node. See also chapter "Type configurator" reference plugin (Page 130).

NoteNo variants

No variants of equipment module types are supported.


7.2 Copying an equipment module (type)


Procedure1. Select the shell of an equipment module.

2. Select the "Copy" command in the "Type library" column.

3. Select the "Paste" command in the "Type library" column.The copy of the equipment module is created in the "Type library" column. The name of the newly created shell is "EMT_<consecutive number>".

4. Define the details of the equipment module in the "Type attributes" column.

5. Right-click on the EMT in the "Type structure" column and select the "Insert new object > <desired object>" command in the context menu.The folder of characteristics cannot be renamed or deleted.


ResultThe shell of the equipment module is saved in the "Templates" node. See also chapter "Type configurator" reference plugin (Page 130).

7.3 Deleting an equipment module (type)


Procedure1. Select the shell of an equipment module.

2. Select the "Delete" command in the "Type library" column.


ResultThe shell of the equipment module is deleted in the "Templates" node. See also chapter "Type configurator" reference plugin (Page 130).

Management of equipment module types7.3 Deleting an equipment module (type)


7.4 Creating control variables

Requirements● You use control variables for configuring parameters and for external interconnections.


● An equipment module has been created. See also chapter Creating an equipment module (type) (Page 31).

Procedure1. Right-click on an equipment module in the "Type structure" column and select the "Insert

new object > <desired object>" command in the shortcut menu.

2. Define the details of the control variables in the "Type attributes" column.


Text 0/ Text 1The 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. If you change the data type, the entries for Text 0 and Text 1 that already exist are deleted. The attributes are empty by default.

To edit the attributes later, open the parameter properties from the Navigator. Select the "Attributes > Automation Standard" tab. It is possible to edit both attributes independently of each other.

If you wish to define the attribute Text 0 or Text 1 to a type (EMT or CMT), they are also displayed on the instances.

7.5 Creating messages

IntroductionAn equipment module can distribute messages. These are reported in the visualization system, for example WinCC.

Requirements● The "Type configurator" plugin is open. See also section Opening the "Type configurator"

plugin (Page 51).

● An equipment module has been created. See also section Creating an equipment module (type) (Page 31).

Management of equipment module types7.5 Creating messages


Procedure1. Right-click on an equipment 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.


ResultThe message has been created. When you transfer the messages to PCS 7, you configure the block allocation and the message identifier later in PCS 7.

7.6 Creating subordinate control modules

IntroductionYou can create control modules as part of an equipment module. For calculations or interlocks, for example.

Requirement● The "Type configurator" plugin is open. See also chapter Opening the "Type configurator"

plugin (Page 51).


Procedure1. Right-click on the equipment module in the "Type structure" column and select the "Insert

new object > Control module" command.

2. Define the details of the subordinate control modules in the "Type attributes" column.If you activate the "optional" option on the subordinate control module, this control module can be omitted at an instance of the equipment module.

NoteOptional control modules

If an optional control module which is defined as a process tag (e.g. calculations, interlocks, etc.) is omitted, ensure that certain control strategies at the instance are still permitted.

3. Create the desired objects underneath the control module.


ResultThe control module is integrated as a component in the equipment module type.

Management of equipment module types7.6 Creating subordinate control modules


See also chapters Creating mapping for a control module (Page 35) and Work with basic requirements (Page 46).


7.7 Creating mapping for a control moduleIf you want to activate a control module in a step sequence, create a mapping of the equipment module (type) for the control module.

Requirements● The "Type configurator" plugin is open.

See also chapter Opening the "Type configurator" plugin (Page 51).


● At least one lower-level control module has been created.See also chapter Creating subordinate control modules (Page 34).

Procedure1. If control modules are available available in the "Types library" column, drag&drop a control

module to the equipment module in the "Type structure" column.When you create the control module using drag&drop, the following engineering task is executed from the base project: "@20 > B20 > M40 > A10 > Y00R00047 Copy in control module".

2. Right-click on an equipment module in the "Type structure" column and select the "Insert new object > Control module assignment" command.

3. To clearly identify the control module mapping, define the role of the control module mapping in the "Role" field in the "Type attribute" column. The role is displayed in the "Type structure" column as the name.

4. Optional: Enter a comment in the "Comment" field.

5. To allocate the control module mapping to a control module, drag the control module to the control module mapping in the "Type structure" column.You define the specific requirements for the control module yourself at the assigned control module. The requirements in particular include the required commands as well as the options of evaluating the status feedback messages.


Management of equipment module types7.7 Creating mapping for a control module


ResultThe control module is assigned to the control module mapping. The usage locations of the control module mapping are updated on the function diagram. See also chapter Engineering in the function diagram (Page 92).

See alsoWork with basic requirements (Page 46)

7.8 Assigning the control module mapping to a control module

Requirement● A control module mapping is created. See also chapter Creating mapping for a control

module (Page 35).

● The equipment module (type) is instantiated. See also chapter Assigning an equipment module to the DCS structure (Page 88).

Procedure1. In the instance of the equipment module, open the properties of the control module mapping.


3. Drag the required control module to the "Assigned control module" attribute.

4. Check whether the name of the required control module is displayed in the usages of the control module mapping in the step sequence.

7.9 Creating step sequences

Requirement● The "Type configurator" plugin is open. See also chapter Opening the "Type configurator"

plugin (Page 51).


Procedure1. Right-click on an equipment module in the "Type structure" column.

2. Select the "Insert new object > Step sequence" command from the shortcut menu.The step sequence is created. A start condition, a start step, a transition, and an end step are created automatically underneath. The number of step sequences is limited to 32 per equipment module.

Management of equipment module types7.9 Creating step sequences


3. Define the details of the step sequence in the "Type attributes" column.If you use multiple step sequences, you determine the order in which the step sequences are processed via the "Priority" attribute.


NoteConditions are always exported

Start and transition conditions are always exported via the Automation Interface during data exchange, even if the conditions are empty.

See alsoEditing step sequences (Page 37)

7.10 Editing step sequences

RequirementA step sequence has been created. See also chapter Creating step sequences (Page 36).

Procedure1. Right-click on the step sequence in the "Type structure" column and select the "Edit step

sequence" command in the context menu.The function diagram opens. The step sequence with start condition, start step, transition, and end step is placed. The step sequence object is marked in the "Templates" node. The "Name" of the step sequence is shown in the start condition. Edit the start condition like a transition.

2. Edit the step sequence as usual.See also chapter Engineering in the function diagram (Page 92). You can find more information on this topic in the "Logical" manual, keyword "Creating and numbering step sequences".


Management of equipment module types7.10 Editing step sequences


7.11 Using commands and statuses in step sequences

Requirement● A step sequence has been created and is open for editing. See also chapters Creating step

sequences (Page 36) and Editing step sequences (Page 37).

● A control module mapping is created. See also chapter Creating mapping for a control module (Page 35).

Procedure1. Choose one of the following options:

– If you want to assign a control module status to a transition, drag the control module mapping from the "PCS 7 templates" folder in the Navigator and drop it onto a transition. You also have the option of using statuses from the "Status for EM" folder.

NoteConfiguring transitions

You can only assign statuses to a transition. Direct use of control variables (control values) is not possible.

– If you want to assign a command of the control module to a step, drag the control module mapping from the "PCS 7 templates" folder in the Navigator and drop it onto a step.You also have the option of using commands from the "Commands for EM" folder.

NoteConfiguring steps

You can only assign commands to a step. Direct use of control variables (control values) is not possible.

A window opens.

2. Select the entry that you want to assign from the list.

3. Click "#" and enter the desired value to write a constant at a connection of the commands and statuses.

4. In order to link a connection of the commands and status with a bit memory, drag the desired bit memory from the Navigator to the connection.Make sure that the data types match.

5. In order to change the comparison operator of a command or status, select the object, right-click on the existing operator and select the "Comparison operator > <Desired operator" command from the context menu.

6. You have the option of assigning a characteristic to the commands and statuses. See also chapter Using characteristics in step sequences (Page 42).


Management of equipment module types7.11 Using commands and statuses in step sequences


ResultStatuses are placed on the left next to the transition. Commands are placed on the right next to the step. The commands and statuses of a control module mapping can be assigned multiple times. An instance of the commands and statuses is created in the Navigator below the function diagram.

NoteImplementation in PCS 7

You can perform an implementation of the commands and statuses in PCS 7 as a standard command or on a control module type.

NoteSequence of commands and statuses

Commands within a step are generated in name order. Statuses within a transition or at a logic are generated in name order. A result of this procedure can be that the sequence on the PAB functions diagrams differs from the result in the PCS 7 SFC. If the sequence is functionally important, post-processing is required in the equipment module type in PCS 7.

Example

Management of equipment module types7.11 Using commands and statuses in step sequences


7.12 Description of the characteristics

Control strategiesYou can use control strategies to define different industrial processes. Step sequences are controlled based on the control strategies. Control strategies are important for the superordinate recipe control level (batch systems). You can create a maximum of 32 control strategies. You can assign setpoints to the control strategies.

SetpointsSetpoints are specified in process engineering through manual input or by a higher control level (batch system).

The following data types are supported:

● BOOL

● INTEGER

● DOUBLE INTEGER

● REAL

● STRING

● PI

● PO

You assign setpoints to individual control strategies. Besides the desired value, the actual value is also offered as control variable by default.

The high and low limit and unit are typically determined or customized at the EM instance. Depending on the data type selected, you can also edit the high and low limit in the "Type configurator" plugin.

Process valuesThe connection of process values to the equipment module is used to control the step sequences. Typically, process signals, e.g. an actual value, are used for advancement of step sequences. You define the values on the function plan.

The unit is typically set on the EM instance.

Control valuesControl values are used to create a connection to external control modules. The control values are configured in the EMT. The actual connection to the control module is only established on the instance side.

The unit is typically set on the EM instance.

Management of equipment module types7.12 Description of the characteristics


ParametersA parameter is used to influence the behavior of a basic function at a concrete instance, e.g. with options. Another example for using parameters is the instance-specific configuration of limits.

Bit memoryBit memory is required for storing values temporarily. Bit memory is only used locally in the operating control.

The following data types are supported:

● INT

● DINT

● BOOL

● REAL

● STRING

TimersTimers are used in a variety of applications for monitoring time or for calculating a runtime.

Note textsNote texts are primarily used for operator guidance.

Position textsPosition texts are used for display of the current process state on the HMI.

See alsoCreating mapping for a control module (Page 35)

7.13 Creating characteristics

Requirements● The "Type configurator" plugin is open. See also section Opening the "Type configurator"

plugin (Page 51).

● An equipment module has been created. See also section Creating an equipment module (type) (Page 31).

Management of equipment module types7.13 Creating characteristics


Procedure1. Select the "Characteristics" folder in the "Type structure" column under the equipment

phase.

2. Right-click on a subfolder and select the "Insert new object > <characteristic>" command in the context menu.See also section Description of the characteristics (Page 40).

NoteCreating in bulk

To create multiple characteristics under the same folder, select the folder in the "Type structure" column. Click on the "Insert new object" button in the "Type attributes" column. One characteristic is created for each click.

3. Define the details of the characteristic in the "Type attributes" column.A maximum of 24 characters are allowed in the "Name" field.

4. If you work with work types and desired values, define the desired values that should be visible at the work type.


7.14 Using characteristics in step sequences

Requirement● A step sequence is open for editing. See also chapter Editing step sequences (Page 37).

● Commands and statuses are used in the step sequence. See also chapter Using commands and statuses in step sequences (Page 38).

Procedure1. Below the "Templates" node in the Navigator, select a characteristic from one of the

subfolders of the "Characteristics folder".

2. Drag the characteristic or a Sub_CV of the characteristic from the "Templates" node in the Navigator and drop it onto a connector of a status or command. You can identify from the description of the command or status whether a connector requires the characteristic itself or a Sub_CV.

NoteMultiple use

To use characteristics or their SubCVs multiple times on a function diagram, drag them multiple times from the "Templates" node in the navigator to the function diagram using drag&drop. Do not use the copy function for this purpose.

Management of equipment module types7.14 Using characteristics in step sequences


ResultA connection between the status or command and the characteristic is automatically established. During this process, a data type consistency check takes place.

NoteControl module interconnection with characteristics only on the instance side

Only use the interconnection of control modules and characteristics on the instance side.

7.15 Interconnecting signals and parameters of control modules with characteristics

Requirement● The instance of the control module includes signals and parameters.

● The control module is placed on a function diagram.See also Chapter Editing control modules on the function diagram (Page 92).

● The step sequence of the equipment module includes characteristics.See also Chapter Using characteristics in step sequences (Page 42).

● The step sequence is placed on a different function diagram than the control module.

Procedure1. Place the characteristic on the function diagram of the control module.

2. Connect the characteristic with the parameter or signal of the control module.

3. Repeat steps one and two for all characteristics that you want to interconnect with a control module.

ResultThe signals and parameters of the control module are interconnected with the characteristic.

NoteData transfer in PCS 7

After data transfer in PCS 7, an outside interconnection of the EM block has been created. The connector label identifies the CM/EM to which an interconnection exists for documentation purposes.

See alsoEditing the logic on function diagrams (Page 93)

Management of equipment module types7.15 Interconnecting signals and parameters of control modules with characteristics


7.16 Working with negations

NoteNegation 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 PAB, negations can be used at inputs and outputs. The negations at the outputs cannot be exported to PCS 7. As such, in the function plan properties, in the tab "Attribute > System data" in the control group "Settings", the "Mode function plan" 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 plan properties, the entry "PCS 7" is selected in the tab "Attribute > System data" in the control group "Settings" in the list "Mode function plan".

● Types have been placed on the function plan and are connected.

Procedure1. Select the connection at a type input.

2. The connection is displayed in magenta.

3. Select the "Settings > Signal negated" entry in the context menu.


Example

Management of equipment module types7.16 Working with negations


See alsoUsing references (Page 45)

7.17 Using references

DefinitionThe reference in PAB 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 referenceConnection to data blocks

● Block variable referenceConnections to CFC block connections, that are not defined in the "Type configurator" plugin or in the technological editor for the exchange between PAB and PCS 7

● Textual referenceConnection to control variables, that are not defined in the "Type configurator" plugin or in the technological editor for the exchange between PAB and PCS 7

RequirementA function plan is open for editing.

A block is placed, whose parameter you wish to link to the parameters of another block.

Procedure1. 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.

Management of equipment module types7.17 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 PAB, 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.CVExample for the syntax of a global variable reference with unit hierarchy: Name of the global DB.ElementNameExample 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 (V8.1 SP1)", 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 PAB finds the referenced block and the reference can be closed, a connection is made from the textual reference.


Importing textual referencesIf 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.

7.18 Work with basic requirements

IntroductionWith the help of the "Basic requirement" option, the minimum requirements on the control module to be assigned are given an abstract description; e.g. the required commands or feedback via the status.

Control modules assigned to an equipment module (type) are marked as so-called basic requirements if they describe only the requirement for one control module and are not to be included implicitly in the copied quantity in the course of instancing. If you define control module mapping, use a control module basic requirement or a specific control module as part of the equipment module type.Control modules of an equipment module type can also be marked as optional, but not those control modules which were assigned a role by control module mapping.

Management of equipment module types7.18 Work with basic requirements


Requirement● The "Type configurator" plugin is open.

See also Chapter Opening the "Type configurator" plugin (Page 51).

● An equipment module (type) is created.See also Chapter Creating an equipment module (type) (Page 31).

● At least one control module type is created.See also Chapter Creating a control module type (Page 26).

Procedure1. Create a control module mapping below the equipment module (type) in the "Type structure"

column.See also Chapter Creating mapping for a control module (Page 35).

2. Drag the desired control module types using the Drag&Drop feature from the "Type library" column to the equipment module in the "Type structure" column.

3. Enable the option "Basic requirement" in the "Type attributes" column of the lower-level control module types.

4. Using the Drag&Drop feature, drag the control module basic requirement to the control module mapping.You may assign the basic requirement as often as required to different control module mappings within an equipment module type.

NoteBasic requirements do not apply to the EMT instance

Control modules in an EMT defined as the basic requirement do not apply to instancing. In this case, assign specific control modules to make sure that the associated work types at the points of application are still allowed and functional.





Management of enumerations 88.1 Create enumeration types

NoteWorking 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.


Procedure1. Select the "Insert new object > Enumeration" command in the menu bar of the plugin.

The shell for an enumeration is created in the "Types 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.


ResultThe enumeration type is saved in the node "@Template > @PCS 7 > Global declaration> 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 50).


8.2 Using enumerations

Requirement● You have created at least one enumeration type. See also chapter Create enumeration

types (Page 49).

● You have created one CMT with a parameter and wish to use an enumeration here. See also chapter Creating a control module type (Page 26).

● You have created one EMT with a set point and wish to use an enumeration here. See also chapter Creating an equipment module (type) (Page 31).

● Parameter and/or setpoint have the data type INT, DINT, BOOL, BYTE, WORD or DWORD.


Procedure1. Select one of the following options:

– In the column, "Type library", select the CMT on which you wish to use the enumeration.Select the desired parameter in the "Type structure" column.

– In the column, "Type library", select the EMT on which you wish to use the enumeration.Select the desired set point in the "Type structure" column.

2. Select the field "Enumeration" in the "Type attribute" 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.


Editing the use1. To change the usage of an enumeration on a parameter, open the parameter properties.


3. Edit the attributes "Enumeration" and "Value".


Management of enumerations8.2 Using enumerations


"Type configurator" plugin 99.1 Opening the "Type configurator" plugin

RequirementsAn engineering project or a base project is open.

Procedure1. In the menu bar, select the "Plugins > Automation > PCS 7 interface > Type configurator"

command.

9.2 Creating a global command and status library

IntroductionThe 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.


ProcedureClick the "Create command and status library" button in the menu bar of the plugin.

ResultTwo new folders are created in the "Templates" node. One folder contains the commands, the other one the statuses. You have the option to use these commands and statuses, for example, in a step sequence. See also chapter Using commands and statuses in step sequences (Page 38).


9.3 Creating functions

IntroductionFunctions 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.

NoteTask 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.

RequirementThe type configurator plugin is open. See also chapter Opening the "Type configurator" plugin (Page 51).

Using predefined function blocks1. 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 "@Template > 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.


8. Repeat steps 4 to 7 for all the parameters to be edited.

Creating new function blocks1. 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.

"Type configurator" plugin9.3 Creating functions



6. Repeat steps 3 to 5 for all the parameters to be created.

See also"Type configurator" reference plugin (Page 130)





Creating the Master Version 10Introduction

You have the option to set a version at the template of the types.

You then use the "Assembly Updater" plugin to check if there is a difference in the version of the template at the instances and update the usage without structure and property check. See also chapter Update type usages (Page 57).

One version can be created for each PAB session.

Procedure1. Open the properties of the type which serves as template.

2. Select the "Attributes > COMOS system" tab.

3. Click on the "Generate Version" button in the "Assembly Updater" control group.A window opens.

4. Confirm the query if you want to create a new version.



Creating the Master Version


Update type usages 11Introduction

With the "Assembly Updater" plugin, you apply changes to types to the already created instances of equipment modules, 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. See also chapter Creating the Master Version (Page 55).

RequirementYou have already created instances of equipment modules (type), 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 133).

Procedure1. Select the "Plugins > Automation > Assembly updater" command in the menu bar.

2. Select the PCS 7 mode from the list.

3. Set the desired start object below which the updated template of the type is located.You may use the project node here.

4. Drag&drop the changed type from the "Templates" node in the navigator to the "Refreshed template" field.

5. Select one of the following options from the list:

– To check all structures and properties of the template object, select the entry "Structure and property verification".

– To only check the usages which have a different version than your template, select the entry "Version check".

6. 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.

7. 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.

8. Click the "Update" button to apply the displayed type changes to the instances.A dialog opens.


9. 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.

10.Confirm your entries.

NoteNo automatic synchronization of instances

When you update instances with the "Assembly updater" plugin, the instances receive a new system ID. For renamed objects to be recognized during data exchange, synchronize the ID with PCS 7.

Updating a subordinate control moduleTo 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.


6. Set the project node as the start object.

7. Drag&drop the updated equipment module (type) from the "Templates" node in the navigator to the "Refreshed template" field.

8. Update the instances of the equipment module (type) as described above.

Update type usages


Using "Excel import" 12Introduction

You can use the "Excel Import" plugin to import the plant hierarchies, CMTs and signals. The import of hardware is optional.

NoteHardware import

If you do not import the hardware, the signals on the IO channels will not be implemented.

Requirement● The Signalliste.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.

NoteEditing Excel lists

When editing Excel lists, take care not to delete or rename any columns.

Procedure1. 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 import Excel file”.A window opens.

3. Select the signal list.By default, the list is located in the folder "C:\ProgramData\Siemens\PCS 7 Automation Base\Excel" after installation.Only use the signal list provided.


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 “Starting 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 Automation Base\Excel" after installation.



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.

ResultThe CMTs, hardware and signals stated in the signal list are created.

See also“Excel import" reference plugin. (Page 132)

Using "Excel import"


Engineering in PAB 1313.1 Functional characteristics of the hardware objects

My Documentation Manager provides you with an Excel list (http://w3.siemens.com/mcms/industrial-automation-systems-simatic/en/manual-overview/tech-doc-pcs7/simatic_pcs7_v811/Pages/Default.aspx)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.

13.2 Information on identifying hardware components

ObjectiveAll hardware components that are imported or exported through the PCS 7 interface must receive a unique description both in PAB 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 PAB and PCS 7The hardware components are identified using the "Name" and "Article number" fields. In PAB, the properties "Name" and "Article number" are generated according to rules that differ from PCS 7.

PAB rule PCS 7 rule (as per HW Config)Name Sequential number Number according to slot rules.

Slot number of the module in the rack or distributed I/O. See the description on "Basics of slot rules in PCS 7" below.

Article number Freely selectable arti‐cle number

Machine-readable serial number (MLFB) of the man‐ufacturer.Example: "6ES7 417-4XT05-0AB0"

The objects are initially created based on the PAB rules in PAB. To export objects to PCS 7, they must first be renamed in accordance with the PCS 7 rules.


http://w3.siemens.com/mcms/industrial-automation-systems-simatic/en/manual-overview/tech-doc-pcs7/simatic_pcs7_v811/Pages/Default.aspx



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 addressThe power supply, the CPU and the input/output modules are plugged into the rack. The bus address must be entered in the PAB 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 outputsThe 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.

NoteSpecial 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 PAB 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 PAB to PCS 7When exporting the hardware configuration:

The configured components are identified using the "Name" and "Article number" attributes.

NoteChecking 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 PABWhen 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 PAB.

See alsoOverview of data exchange with PCS 7 (Page 11)

Engineering in PAB13.2 Information on identifying hardware components


13.3 Hardware engineering in the Navigator

13.3.1 PROFINET and PROFIBUSYou have the option of using both PROFIBUS and PROFINET. Only PROFIBUS is mentioned in the examples in the following sections.

Notes on PROFINETJust like with PROFIBUS, the bus nodes are connected to their master with the "Assign fieldbus" and "Assign 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 standard" tab:

● "MRP domain"

● "MRP role"

● "MRP diagnostics"

To use the MRP protocol, make the connections of the manufacturer devices in the desired order.

Engineering in PAB13.3 Hardware engineering in the Navigator


ExampleThe following example shows the associated connections of the manufacturer devices in PAB.





The example looks like this in the Topology editor of PCS 7:



13.3.2 Configuring a SIMATIC station

Requirement● The "Locations" tab is displayed in the Navigator.

● A plant has been created.

Creating a SIMATIC station1. 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.

Equipping a SIMATIC station with hardware1. 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 68).

– 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:



– "Communication"


7. If necessary, assign the rack to the location where it should be assembled.

See alsoEquipping interface modules with I/O modules (Page 69)

13.3.3 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 67).

● The "Locations" tab is displayed in the Navigator.

Procedure1. 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 only uses one slot, enter the value "2".

See alsoInformation on identifying hardware components (Page 61)

Creating an interface module as distributed I/O (Page 69)



13.3.4 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 67).


Procedure1. 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 alsoEquipping interface modules with I/O modules (Page 69)

Assigning a field bus to a DP slave via a task (Page 75)

13.3.5 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 69).


Procedure1. 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 module" 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:



– "Communication"


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:



– "Communication"


Then, select a module marked with "O" that is suitable for the input module.

See alsoConfiguring IO modules (Page 70)

13.3.6 Configuring IO modules

Requirement● The central processing unit (CPU) is configured

See chapter Configuring the central processing unit (CPU) (Page 68).

● The interface modules of the distributed I/O are equipped with IO modules.See chapter Equipping interface modules with I/O modules (Page 69).




Procedure1. 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 61).

13.3.7 Creating a redundant SIMATIC station

Requirement● The "Locations" tab is displayed in the Navigator.

● A plant has been created.

Creating a SIMATIC station1. 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 hardware1. 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"

NoteSpecial 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 UR2H racks are not transferred to PAB 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:



– "Communication"


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:



– "Communication"


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.




Creating a redundant I/O (Page 73)

13.3.8 Creating a redundant I/O

Requirement● Two SIMATIC stations are created for redundant hardware.

See chapter Creating a redundant SIMATIC station (Page 71).


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 module > <Interface module of the type "IM 153-2 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 153-2 HF" type.

8. Create a module underneath the interface module.

NoteInput/output modules

Use only analog or digital input/output modules with identical order numbers.


10.Open the "Attributes > Automation standard" tab in the properties of the first module.

11.Drag the second module from the Navigator to the "Redundant partner" field.


ResultThe second module is automatically linked and the redundant partner is registered in its properties in the "Attributes > Automation standard" tab.



See alsoAssigning redundant fieldbus via engineering task (Page 76)

13.3.9 Using the DP/PA coupler

IntroductionThe DP/PA coupler is used to achieve a better separation of tasks, as it establishes smaller subnets inside the fieldbus system.

Procedure1. 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: 6ES7 153-2BA82-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 IO slave.To do this, use an object with one of the following MLFBs: "PAYLINK: 6ES7 153-2BA82-0XB0 IM153-2 HF".

10.Open the "Tasks" tab in the properties of the IO slave.

11.Drag the PROFIBUS of the master to the "Target object" field of the "Assign fieldbus" task.

12.Execute the task.

13.Create a new I/O device from the ET 200 group.

14.Open the "Tasks" tab in the properties of the ET 200.

15.Drag the DP/PA link fieldbus to the "Target object" field of the "Assign fieldbus" task.

16.Execute the task.

ResultPAB 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.

NoteOnly 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.

13.4 Editing hardware engineering via engineering tasks

13.4.1 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.



You can find more information on this topic in the "EI&C Operation" manual, keyword "Using engineering tasks".

Assigning a busTo 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.

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 67).

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.

Engineering in PAB13.4 Editing hardware engineering via engineering tasks


See alsoAssigning redundant fieldbus via engineering task (Page 76)

Software engineering in the Navigator (Page 82)

13.4.2 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.


● A fieldbus has been assigned via an engineering task.See also chapter Assigning a field bus to a DP slave via a task (Page 75).



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".

Procedure1. 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.

5. Check to see if the engineering task "Assign redundant fieldbus" is available.Create the engineering task "Assign 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.

Engineering in PAB13.4 Editing hardware engineering via engineering tasks


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.


See alsoSoftware engineering in the Navigator (Page 82)

13.5 Hardware engineering with the configuration tool

13.5.1 Opening the configuration toolYou 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 V8.1.

Requirement● The project presetting for PCS 7 is set in the product properties. See also chapter Creating

a new engineering project (Page 17).

● The "Locations" tab is selected in the Navigator.

Procedure1. Right-click on the project node and select the "New > Config Configuration tool - SIMATIC

PCS 7 V8.1" 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.

13.5.2 Creating hardware with the configuration tool

Requirement● The configuration tool is open. See also chapter Opening the configuration tool (Page 77).

Engineering in PAB13.5 Hardware engineering with the configuration tool


Procedure1. Select the "Attributes > <required tab>" tab.

For example, the "Attributes > AS bundle (complementary)" tab.

2. Set a location in the "Target object" field.

3. 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.

4. Click on the button "Create configuration".

ResultThe 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.

NoteNo check for manually created hardware

Manually created hardware objects are not checked by the rules of the configuration tool.

13.5.3 Creating hardware including spare I/O channels


Procedure1. Select the "Attributes > I/O ET <required tab>" tab.

For example, the "Attributes > I/O ET 200M" tab.


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.

ResultThe 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.




13.5.4 Hardware including spare I/O space for modules is created





3. In the "Standard I/Os" control group, select the "Modules" entry from the "Quantity" list.

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.

ResultThe 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.


13.5.5 Creating redundant signal modules





3. Select signal modules with the property "can be made redundant".

4. Select the option "Yes" for the signal in the "Redundancy" column.



ResultThe 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 Standard" tab in the "Redundant partner" field.


13.5.6 Creating redundant stations


Procedure1. Select the "Attributes > WS bundle" tab.


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" entry from the "WS type" list".

ResultThe 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.


13.5.7 Creating licenses




Procedure1. Select the "Attributes > WS bundle" tab.


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".

ResultWhen you have created the configuration, a "Licenses" folder is created below each station in the Navigator.

13.6 Extended hardware parameters

ConfigurationThe 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 PAB 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 109) and chapter Importing the hardware configuration (Page 115).

● 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.

Engineering in PAB13.6 Extended hardware parameters


NoteFunctional scope

In PAB, the extended hardware parameters are only available to the assemblies supplied in the database. This is visible in PAB in the "Automation extended" tab. In addition, no extended parameters are supported at F-blocks.

NoteStandard 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.

NoteNo automatic consistency check of the hardware configuration

In PAB, 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.

13.7 Software engineering in the Navigator

13.7.1 Notes on the plant hierarchy

Requirement● The project presetting for PCS 7 is used.


● The DCS structure has been created.See chapter Creating the DCS structure (Page 18).

Engineering in PAB13.7 Software engineering in the Navigator


PAB structure in comparison to plant hierarchy in PCS 7The plant hierarchy in PCS 7 can include up to 8 levels. A 4-level plant hierarchy is used in this example:

① PlantPart of the plant hierarchy.

② UnitPart of the plant hierarchy.

③ SubunitPart of the plant hierarchy.

④ FolderCOMOS-specific structural element.

⑤ PositionPart of the plant hierarchy.

⑥ COMOS process tag (function)⑦ PCS 7 control module (CM).

See alsoOptional: Creating and configuring process tags (Page 84)

13.7.2 Working with channel requests

Requirement● Hardware engineering has been performed.

See also chapter Editing hardware engineering via engineering tasks (Page 75).

● The DCS structure has been created.See also chapter Creating the DCS structure (Page 18).



● At least one instance of a control module has been created in the DCTS 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.

Procedure1. 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.

13.7.3 Optional: Creating and configuring process tags

Requirement● The plant hierarchy is known.

See chapter Notes on the plant hierarchy (Page 82).

● The "Units" tab is open in the Navigator.

Creating and configuring process tagsYou 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 (function).

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 alsoOptional: Linking hardware and software: Implementing channels (Page 85)



13.7.4 Optional: Linking hardware and software: Implementing channels


See chapter Editing hardware engineering via engineering tasks (Page 75).

● The process tags have been created and configured.See chapter Optional: Creating and configuring process tags (Page 84).

Procedure1. 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.


Implementing channels in bulkIf you want to implement the channels in bulk, use the "Excel Import" plugin. See also chapter Using "Excel import" (Page 59).

See alsoEditing software engineering using engineering tasks (Page 85)

13.8 Editing software engineering using engineering tasks

13.8.1 Engineering tasks

ObjectiveWith the help of an engineering task, a control module or an equipment module is generated from a template and created below a position as follows.


Engineering in PAB13.8 Editing software engineering using engineering tasks


See alsoDisplaying the "SW interface" tab and creating tasks (Page 86)

13.8.2 Displaying the "SW interface" tab and creating tasks

Requirement● Software engineering has been performed.

See chapter Software engineering in the Navigator (Page 82).


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, select any tab below the "Tasks" tab.

5. Select the command "New > Copy in control module" in the context menu.The "SW interface" tab opens.

Checking and creating tasks1. Select the "Tasks > SW interface" tab.

2. Check whether the following engineering tasks are available:

– "Copy and paste control module"

– "Assigned station"

– "Copy in the equipment module"

3. Create missing tasks using the "New" context menu.

See alsoAssigning a control module type to the DCS structure (Page 87)

Assigning a control module type to a function (Page 88)

Assigning a station to a position (Page 89)

Engineering tasks (Page 85)



13.8.3 Assigning a control module type to the DCS structure



● 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 86).


Configuring and executing a task1. Select the "Templates" node in the Navigator.

2. Select the following object:"@Template > @PCS 7 > Template-Container > CMTs".

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 82).

● There is a mapping table below the inserted control module. See also chapter Configuring the mapping table of the signal designations (Page 99).

See alsoAssigning a control module type to a function (Page 88)

Assigning a station to a position (Page 89)



13.8.4 Assigning a control module type to a function



● 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 86).


Procedure1. Assign the control module type to a function.

See also chapter Assigning a control module type to the DCS structure (Page 87).


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 82).

● 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 99).

See alsoAssigning a station to a position (Page 89)

13.8.5 Assigning an equipment module to the DCS structure



● 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 86).




Procedure1. Select the "Templates" node in the Navigator.

2. Select the following object:"@Template > @PCS 7 > Template-Container > EMTs".

3. Select the template of an equipment module in the "EMTs" folder.

4. Drag the template from the Navigator and drop it into the "Target object" field in the "Copy in equipment 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.


Result● The inserted equipment module is created below the folder of the DCS structure in the

Navigator structure. See also chapter Notes on the plant hierarchy (Page 82).

● The function diagrams of the individual step sequences are write-protected. A reference to the control module is created automatically on instantiation.

● If there is a control module underneath the equipment module and the "Basic requirement" option is activated, the control module is not inserted underneath the equipment module. If the "Basic requirement" option is deactivated, the control module is inserted underneath the equipment module.

● Commands and statuses contained underneath the control module on the EMT page are not inserted during equipment module instantiation.

See alsoConfiguring the mapping table of the signal designations (Page 99)

13.8.6 Assigning a station to a position

Requirement● 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 86).

● Hardware engineering has been performed.See chapter Editing hardware engineering via engineering tasks (Page 75).




Configuring and executing an engineering task1. Select the "Locations" tab in the Navigator.

2. Select the object "0 Plant > L001 Building > G001 Floor, level > R001 Room, Control center > S001 Cabinet > Station".

3. Drag&drop the station from the Navigator to the "Target object" field in the "Assigned station" row.

4. Click the arrow of the "Execute" button in the menu bar of the "SW interface" tab.The button has the following icon:

5. Select the "Execute (selected)" entry in the "Execute" list.


See alsoAssigning control module types to the DCS structure in bulk (Page 90)

13.8.7 Assigning control module types to the DCS structure in bulk




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 86).

5. Select the "SW interface" tab and proceed as described here:Assigning a control module type to the DCS structure (Page 87) The task includes all control module types below the selected folder.



13.9 Using symbol tables

13.9.1 Importing symbolic addresses into a symbol tableYou can also import the symbolic addresses from a symbol table stored in the file system to the symbol table.

Procedure1. 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 alsoRefreshing the symbol table (Page 91)

13.9.2 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.

● To refresh the symbolic addresses of individual objects in the symbol table, select these objects and then select the "Symbol table > Refresh symbol table" command from the shortcut menu of the object.

ResultThe symbolic addresses are written into the symbol table.

Engineering in PAB13.9 Using symbol tables


13.10 Engineering in the function diagram

13.10.1 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 114) and chapter Creating control modules (Page 27).

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 85). 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".

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: "@30 > M40 > A50 A10 > A20 > A10 > A10 > A10 > A40 Bit-wise".

4. Connect the objects on the function diagram.

NoteConnecting 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.

Engineering in PAB13.10 Engineering in the function diagram


ResultThe placed objects can be exported. See chapter Exporting from PAB to PCS 7 (Page 105).

See alsoEditing the logic on function diagrams (Page 93)

13.10.2 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 92).

Use of blocksYou can use the following generic blocks:

● AND

● OR

● XOR

● NOT

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 PAB.

● The name of the block connections in PCS 7 corresponds to the label of the block connections in PAB.

NoteUnconnected blocks

When you place blocks on the function diagram but do not connect them, you may encounter errors when exchanging data with PCS 7. Delete unnecessary blocks or connect the blocks before data exchange.

See alsoExample for interlock logic on function diagrams (Page 94)



13.10.3 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 93).

Example

1

2

3

3

① Function diagram of the pump② Function diagram of the valve③ Semi-open connection with link across documents

13.10.4 Creating logic levels on transitions

Requirements● A step sequence is created and opened for editing. See also chapters Creating step

sequences (Page 36)and Editing step sequences (Page 37).

● At least one status is connected to a transition. See also chapter Using commands and statuses in step sequences (Page 38).



Procedure1. Select the desired logic block from the tool list.

2. Place the block on the connection between status and transition.You can use the following blocks:

– AND

– NAND

– OR

– NOR

NoteNo export of NAND and NOR

You have the option of working with the NAND and NOR blocks in COMOS. These are not included in an export to PCS 7.

NoteMaximum 2-stage logic level

Use a maximum of a 2-stage logic level.

Example





Editing large quantities of connections 14Introduction

In order to create large quantities of connections or references, use the "Connection manager" plugin. See also chapter Using references (Page 45).

RequirementYou 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.

Procedure1. 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.



Editing large quantities of connections


Linking attributes from PAB and PCS 7 1515.1 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 21).

● A control module has been inserted.


ObjectiveYou 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.


5. Click the "Open mapping table" button.

Step 1: Collecting PCS 7 attributes1. 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 Standard” tab: "Name"

– Signal under the control module, tab "Automation Standard": "Signal name"


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 PAB 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 102).

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 PAB attributes using the navigation assistantAlternatively, you can select the source object in the navigation assistant.

See chapter Using the navigation assistant (Page 101).

Linking attributes from PAB and PCS 715.1 Configuring the mapping table of the signal designations


See alsoAdopting a mapping table as a template (Page 102)

Reference to the mapping table (Page 129)

15.2 Using the navigation assistant

RequirementThe mapping table of the signal designations is open.

See chapter Configuring the mapping table of the signal designations (Page 99).

ProcedureYou 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 standard" tab.


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 double-click 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.


You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Calculation type: Navigation library extended".

See alsoExample of an assignment (Page 102)

Reference to the navigation assistant (Page 130)

Linking attributes from PAB and PCS 715.2 Using the navigation assistant


15.3 Example of an assignment

Requirement● The mapping table of the signal designations is open.


ProcedureThe following mapping applies based on the example in this documentation:

PCS 7 attribute, "Y30T00001 Automation standard" tab PAB attributeName of the signal: Attribute "Name Signal name"

Process tag, "A20 Signal engineering" folder, properties of the signal:"Y00T00027 Signal data" tab, "Y00A00555 Signal descrip‐tion" attributeLinked through unit pointer

Name of the control module: Attribute "Name Name"

Item:"Y30T00001 Automation standard" tab, "Name Hierarchy name" attributeLinked through unit pointer

See alsoAdopting a mapping table as a template (Page 102)

15.4 Adopting a mapping table as a template

Requirement● The mapping table of the signal designations is configured.



ObjectiveThe 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 standard" tab.

Linking attributes from PAB and PCS 715.4 Adopting a mapping table as a template



4. Edit the mapping table according to these instructions:Reference to the mapping table (Page 129)

Saving the mapping tableTo 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.


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 > @PCS 7 > Library folder"





Exporting from PAB to PCS 7 1616.1 Exporting digitally signed XML files:


When using the indirect data exchange via XML format between PAB 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 11).

RequirementTo 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 Keyfor this certificate.

ProcedureTo 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 appliedThe RSA asymmetric signature procedure is used, according to standard "PKCS#1" (see "https://www.ietf.org/rfc/rfc3447.txt"). The attributes of the certificate are described in the certificate definition under "http://www.ietf.org/rfc/rfc5280.txt".


16.2 Exporting a PAB project


7" command.

2. Select the "Export" tab.See also chapter "Export" tab (Page 127).

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 105).

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.

NoteIdentification 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 121).If you have not selected a project yet, the "Project selection" dialog opens first.

10.Click on "Import objects from A to B".

See alsoExporting the technological hierarchy (Page 107)

Exporting instances (Page 108)

Exporting the hardware configuration (Page 109)

Exporting to old PCS 7 V7 projects (Page 107)

Exporting from PAB to PCS 716.2 Exporting a PAB project


16.3 Exporting to old PCS 7 V7 projects

Working with the "Process tag types" templates from PCS 7 V7If process tag types are prepared in PCS 7 and the control module types have not yet been used, the following applies:

A new project can be created in PAB and the process tag types can be imported and used.

In this case, the following applies when exporting the PAB project:

Click on "Generate/Synchronize process tags from A to B" to generate the process tags. If you wish to export cross-diagram interconnections, enable the "Make textual interconnections" option in the Import/Export Assistant.

See alsoExporting a PAB project (Page 106)

16.4 Exporting the technological hierarchy

ObjectiveExporting the plant hierarchy to PCS 7. If there is already a plant hierarchy in PCS 7, the hierarchy folders are synchronized with one another.


7" command.





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.



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.

Exporting from PAB to PCS 716.4 Exporting the technological hierarchy


9. Click the "Export" button.The "Data transfer - Generate/import" dialog opens. See also chapter Information in the "Data transfer - Generate/import" dialog (Page 121).

10.Click on the "Import objects from A to B" button.

16.5 Exporting instances

RequirementsThe plant hierarchy is exported from PAB and synchronized with the plant hierarchy from PCS 7.

See chapter Exporting the technological hierarchy (Page 107).


7" command.





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/EM 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 121).

9. Click on the "Import objects from A to B" button.


Exporting from PAB to PCS 716.5 Exporting instances


16.6 Exporting types


7" command.


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 105).The "Project selection" dialog opens.



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.


9. Click on the "Import objects from A to B" button.

ResultThe types are exported. Then assign the blocks, block contacts, block messages, etc. in PCS 7.

16.7 Exporting the hardware configuration


7" command.


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 105).The "Project selection" dialog opens.


Exporting from PAB to PCS 716.7 Exporting the hardware configuration



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 81).


10.Click on the "Import objects from A to B" button.

ResultThe hardware configuration is exported to the PCS 7 project.

Exporting from PAB to PCS 716.7 Exporting the hardware configuration


Importing from PCS 7 to PAB 1717.1 Importing digitally signed XML files


When using the indirect data exchange via XML format between PAB 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 11).

RequirementTo 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".

ProcedureTo 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 appliedThe RSA asymmetric signature procedure is used, according to standard "PKCS#1" (see "https://www.ietf.org/rfc/rfc3447.txt"). The attributes of the certificate are described in the certificate definition under "http://www.ietf.org/rfc/rfc5280.txt".


17.2 Importing a PCS 7 project

RequirementThe export from PAB to PCS 7 has been performed.

See chapter Exporting from PAB to PCS 7 (Page 105).


7" command.


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 111).

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 121).

7. Click on the "Import objects from B to A" button.


ResultThe 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 121).

See alsoImporting the technological hierarchy (Page 113)

Importing the hardware configuration (Page 115)

Importing control modules (Page 114)

Importing from PCS 7 to PAB17.2 Importing a PCS 7 project


17.3 Importing the technological hierarchy


7" command.


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 111).

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.





ResultThe 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.

See alsoEffects of importing the plant hierarchy (Page 113)

17.4 Effects of importing the plant hierarchy

Requirement● The plant hierarchy from PCS 7 was imported.

See chapter Importing the technological hierarchy (Page 113).

Importing from PCS 7 to PAB17.4 Effects of importing the plant hierarchy


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 7Hierarchy folders from PCS 7 that are not available in PAB are added to the plant hierarchy of the "DSC Structure" node.

17.5 Importing control modules

RequirementsTo import control modules into PAB, the following information must be available for each control module in PCS 7:

● Plant hierarchy

● Control module type

● Parameters and signals used

NoteNo import of characteristic-related data types

Characteristic-related data types from PCS 7 are not available in PAB. When you create parameters below commands and statuses, use the predefined data types in PAB.

● The control module type must already exist in PAB.


7" command.



4. Select the PCS 7 source project to be imported.

5. Select the "CM instances" option in the "Filter" control group.


Importing from PCS 7 to PAB17.5 Importing control modules




ResultThe control modules are imported to the current PAB project.


17.6 Importing the hardware configuration

RequirementsThe hardware is available in the PCS 7 project.


7" command.



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 81).


Importing from PCS 7 to PAB17.6 Importing the hardware configuration



NoteNo 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.


ResultThe hardware is imported to the current PAB project.

If you have activated the "Extended parameters" option, when importing the hardware options in PAB, the tab "Attributes > Extended automation" will be created. The extended hardware parameters will be stored in this tab.

Importing from PCS 7 to PAB17.6 Importing the hardware configuration


Working with reports 1818.1 Assembly Plan

Requirement● You have created a station of the type SIMATIC 400 or

● You have created a distributed I/O of the type ET 200M or ET 200iSP.

BenefitsThe Assembly Plan shows the mounting rail with the individual components and evaluates the additional information, such as the power loss.

ConfigurationTo 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 template in the base project.

18.2 I/O Report

Requirement● The "Locations" tab is selected in the Navigator.

● A cabinet has been created.

BenefitsYou create the I/O Report below the cabinet. The report provides an overview of the utilized and free channels per cabinet.

ConfigurationIn 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 Description"Grouped" If this option is activated, the objects are displayed sorted by

their MLFB. You get an overview of the number of identical objects.

"Detailed" If this option is activated, the objects are displayed sorted by owner.


18.3 Bills of materials



BenefitsYou 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 bundlesContains Bundle MLFBs which each include a collection of objects.

● Bill of material without bundlesDoes not include Bundle MLFBs. All objects are listed separately.

ConfigurationIn 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 Description"Grouped" If this option is activated, the objects are displayed

sorted by their MLFB. You get an overview of the number of identical objects.

"Detailed" If this option is activated, the objects are displayed sorted by owner.

18.4 Configuration plan



BenefitsYou 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

Working with reports18.4 Configuration plan


● Plant bus

● Terminal bus

Place the required objects on the configuration plan with drag&drop and connect them.

18.5 Computer data sheet


● A workstation has been created.

BenefitsCreate 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

ConfigurationThe 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.

Working with reports18.5 Computer data sheet


Working with reports18.5 Computer data sheet


Reference 1919.1 Information in the "Data transfer - Generate/import" dialog

ObjectiveThe "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 fileAll 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" optionIf the option is activated, it has the following effect:

● There are objects to be deleted in the import process:

– The objects exist in PAB but not in the import file.

– These objects are highlighted in blue in the "Data transfer - Generate/import" dialog.

● A working layer is automatically generated during the import.

NoteEntries in symbol tables

The option "Delete in target" generates no working layer for the import if the objects to be deleted are exclusively entries in the symbol table. If there are only entries in symbol tables, this information is immediately deleted from the original working layer as a result of the import.


No full synchronization in Automation InterfacePC 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.

Calling help on the "Data transfer - Generate/import" dialog1. Open the "Data transfer - Generate/import" dialog.

2. Click the "Help" button.

See alsoExporting from PAB to PCS 7 (Page 105)

Importing from PCS 7 to PAB (Page 111)

19.2 Navigator

"Units" tabIn 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:● "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.

The @Template node contains the following objects:

Icon DescriptionProject libraryGroup folder for enumeration types

Enumeration

Template container

Group folder for CM/EM types

CM type/variant collection

CMT template

Reference19.2 Navigator


Icon DescriptionMessage

Signal

Group folder for commands

Command

EMT template

EMT

Equipment phaseCM assignmentParameters

Group folder for functions

FunctionGroup folder for status

Status

DCS structure:

Icon DescriptionDCS structure

Hierarchy folder

Hierarchy folder with S88 type definition "Unit"

Hierarchy folder with S88 type definition "Subunit"

Unit structure:

Icon DescriptionProject

DCS structure

Plant

Unit

Subunit

A50 EI&CPosition

Reference19.2 Navigator


"Locations" tabThe "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 DescriptionProject

Plant

Building

Floor

Room

Cabinet

Station

Rack

Power supply

Communication

Central assembly

19.3 "Import/Export PCS 7" plugin

19.3.1 Calling the "Import/Export PCS 7" plugin

ObjectiveTransfer of engineering data between PCS 7 and PAB.


7" command.

ResultThe "Import / Export PCS 7" plugin opens.

Reference19.3 "Import/Export PCS 7" plugin


The following tabs are available for transferring engineering data:

● "Import" tabSee also chapter "Import" tab (Page 125).

● "Export" tabSee also chapter "Export" tab (Page 127).

19.3.2 "Import" tab

ObjectiveAfter selecting a PCS 7 project, you import the selected objects on this tab from PCS 7 to PAB.

Control group Control element Description"Project selec‐tion"

The "PCS 7 project" option The activated option enables you to import a PCS 7 project file.

The "XML file" option The activated option enables you to import an XML file.

The "XML signature" option The activated option enables PAB to search through the selected XML file for a digital signature. See also chapter Exporting digitally signed XML files: (Page 105).

"PCS 7 project path / XML path" list

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>

"Select a project" button Depending on the option selected, this button opens the "Project selection" window or the "Open" window.



Control group Control element Description"Filter > Project" "Plant hierarchy" option The following objects are included in the selected

source project: ● All PCS 7 objects of the plant hierarchyFollowing the import, the objects are created in the "DCS structure" node.

"CM instances" option The following objects are included in the selected source project: ● All PCS 7 instancesFollowing the import, the objects are created in the "@Template" node.

"Hardware" option The following objects are included in the selected source project: ● All hardware objects from PCS 7Following the import, the objects are created in the "DCS structure" node.

"Extended parameters" op‐tion

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 81).After the import, the "Attribute > Advanced automa‐tion" tab is displayed with the hardware objects.

"Filter > Library" "CM types" option The following objects are included in the selected source project: ● All PCS 7 typesAfter the import, the objects are created as follows:● "Templates" node: "PCS 7 template > PCS 7 Lib

library folder""Enumerations" option The following objects are included in the selected

source project● All enumerations from PCS 7 See also chapter Management of enumerations (Page 49).

"Commands & status" option The following objects are included in the selected source project:● The command and status library from PCS 7.

"Functions" option The following objects are included in the selected source project● All functions from PCS 7See also chapter Creating functions (Page 52).

"Import" button Starts the import"Filter:" "Filter:" table Displays errors, warnings, and messages




Importing a PCS 7 project (Page 112)

Importing the technological hierarchy (Page 113)

Importing control modules (Page 114)

Importing the hardware configuration (Page 115)

Calling the "Import/Export PCS 7" plugin (Page 124)

19.3.3 "Export" tabYou export the selected objects from PAB to PCS 7 on this tab.

Control group Control element Description"Project selec‐tion"

The "PCS 7 project" option The activated option enables you to import a PCS 7 project file.

The "XML file" option The activated option enables you to import an XML file.The "XML signature" op‐tion

The activated option enables the selected XML file to be digitally signed. See also chapter Exporting digitally signed XML files: (Page 105).

"PCS 7 project path / XML path" field

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>

"Select a project" button Depending on the option selected, this button opens the "Project selection" window or the "Open" window.

Table Select the stations that you want to take part in the ex‐port in the “Select" column.



Control group Control element Description"Filter > Project" "Plant hierarchy" option The following objects are included in the selected source

project: ● All objects of the plant hierarchy in the "Project > PV

Plant view" nodeSee also chapter Exporting the technological hierarchy (Page 107).

"CM/EM instances" option 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 108)."Hardware" option The following objects are included in the selected source

project: ● All hardware objects in the "Project" node

See also chapterExporting the hardware configuration (Page 109).

"Extended hardware" op‐tion

The following objects are included in the selected source project: ● All hardware objects in the "Project" node● The extended hardware parameters of the hardware

objectsSee also chapter Extended hardware parameters (Page 81).

"Filter > Library" "CM/EM types" option The following objects are included in the selected source project: ● All types in the "Project > PV Plant view" node

"Actions/Conditions” op‐tion

The following objects are included in the selected source project:● With EMT step actions and transition conditionIf the option is not selected, these objects are not expor‐ted. This prevents changed objects of this type being displayed in the Import/Export Assistant because no synchronization of these objects is currently taking place.

"Enumerations" option The following objects are included in the selected source project:● All enumerations in the "Project" nodeSee also chapter Management of enumerations (Page 49).

"Commands & status" op‐tion

The following objects are included in the selected source project:● The command and status library

"Functions" option The following objects are included in the selected source project:● All functions in the "Project" nodeSee also chapter Creating functions (Page 52).



Control group Control element Description "Export" button Starts the export "Filter:" "Filter:" table Displays errors, warnings, and messages

See alsoCalling the "Import/Export PCS 7" plugin (Page 124)

Exporting a PAB project (Page 106)

19.4 Reference to the mapping table

ObjectiveYou can assign PAB attributes to the inserted PCS 7 control modules in the mapping table.

Calling a mapping table1. Open the properties of a control module.

2. Select the "Attributes > Automation standard" tab.


DesignYou can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Configuring a mapping table".

Control element Description"Insert in template" button Saves the assignments in the template of the control module type

used"Attribute" column Attribute to which the information is transferred"Description" column Description of the set target attribute"Link type" column 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.

Reference19.4 Reference to the mapping table


Control element Description"Source object" column 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 130).

"Property" column Contains the property that is being read outIf necessary, double-click in this column to select another property from the list.

"Value" column Contains a preview of the information to be transferred

See alsoConfiguring the mapping table of the signal designations (Page 99)

Adopting a mapping table as a template (Page 102)

19.5 Reference to the navigation assistantYou 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".

See alsoUsing the navigation assistant (Page 101)

19.6 "Type configurator" reference plugin

Menu bar

Icon Tooltip Description"Refresh" By pressing this button, you refresh the view

in the plugin."Create command and status library"

By pressing this button you create initially the command and status library. See also chap‐ter Creating a global command and status li‐brary (Page 51).

"Functions" Use this button to display a list of all functions that are available as standard. See also chap‐ter Creating functions (Page 52).

Reference19.6 "Type configurator" reference plugin


"Functions" columnIf you click on the "Functions" button in the menu bar, this column is displayed.

Icon Tooltip Description"Select all" Use this button to select all the listed func‐

tions."Deselect all" Use this button to deselect all the selected

functions."Generate functions" Use this button to generate all the selected

functions. The selected functions are cre‐ated in the "@Template > PCS 7 > Tem‐plate-Container > Functions" node and dis‐played in the column "Type library" of the Navigator.

"Types library" column

Icon Tooltip Description"Insert New Object" By pressing this button you create new con‐

trol module types and new equipment mod‐ules (type), enumerations and functions. See also chapter Creating a control module type (Page 26), chapter Creating an equipment module (type) (Page 31), chapter Create enu‐meration types (Page 49) and chapter Creat‐ing functions (Page 52).

"Copy" By pressing this button you copy the selected type in the cache. See also chapter Copying an equipment module (type) (Page 32).

"Paste" By pressing this button you paste the type from the cache.

"Delete" By pressing this button, you delete the selec‐ted type. See also chapter Deleting an equip‐ment module (type) (Page 32).

"Filter" By pressing this button you filter the display of the "Type library" column. Enable the but‐ton for the kind of type that you would like to display.

"Type structure" column

Icon Tooltip Description"Expand all" By pressing this button you expand the entire subordinate structure of

the selected type."Collapse all" By pressing this button you collapse the entire subordinate structure of

the selected type.

Reference19.6 "Type configurator" reference plugin


Icon Tooltip Description"Copy" By pressing this button you copy the selected object in the cache.

"Paste" By pressing this button you paste the object copied in the cache.

"Delete" Use this button to delete the selected object including the subordinate objects. If the type is selected, the button is not active.

"Edit step se‐quence"

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.

"Type attribute" column

Icon Tooltip Description"Filter" By pressing this button you filter the display of the subordinate objects of

the selected type."Insert New Ob‐ject"

By pressing this button you create characteristics in large quantities. One characteristic is created for each click. This button is enabled if you have selected the folder of a characteristic in the "Type structure".

Buttons

Button Description"OK" The created EMTs are saved with this button. The "Type configurator" plugin is closed after actuation."Cancel" Changes which were made in the user interface are not saved and the "Type configurator" plugin is closed

after actuation."Apply" Changes made to the user interface are saved. The "Type configurator" plugin remains open after actua‐

tion.

19.7 “Excel import" reference plugin.

Control element Description“Select import Excel file” field This field displays the path to the currently selected signal list. "Excel worksheet" button Use this button to select a signal list from the file system.“Excel worksheet” list This list shows which worksheet of the signal list is imported.“Starting row" field This field shows the row with which the import of the signal list begins."Select Library file" field This field displays the path to the currently selected library."Select Library File" button Use this button to select a library from the file system.“Start object" field This field displays the object from the Navigator in which the imported objects

are saved."Import into new working layer” option The activated option causes a new working layer to be created with the im‐

port."Implement CM Signals to IO Channel" option The activated option causes the CM signals to be implemented for the I/O

channels with the import.

Reference19.7 “Excel import" reference plugin.


Control element Description"Import" button Click on this button to start the import.Table The table shows errors, warnings and messages for the imported objects.

19.8 Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7"

Area of applicationThis list includes attributes that are matched in the "Assembly updater" plugin in "PCS 7" mode and are updated, if necessary.

NodeStandard tables > Y10 > M00 > A20 > Y10M00N00032 Assembly updater property assignment PCS 7"

User-defined attributes for the matching● Name (abbreviation: @N)

● Label (abbreviation: @L)

● Description (abbreviation: @D)

● CDevice (abbreviation: @C)

● MappingTableXML (abbreviation: @M)

● BackpointerSpecificationsWithLinkObjectAndName (abbreviation: @BS). Example "@BS:Y00T00093.Y00A00159"

● All attributes (if LinkObjects exist, they are taken; otherwise Values). Example "Y00T00093.Y00A00159"

The abbreviations refer to the VSUI Notation.

Attributes that are always matched● Connector (ConnectedWith, Connector Attribute)

● Backpointer

● DocObjs

● Owner

● Unit

● Location

● Implementation

Reference19.8 Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7"


Structure

Column Description"Name" You enter a name according to the following scheme in this

column: A+ 3 numbers incremented in steps of 10. For ex‐ample: "A010"Default: "A010"

"Description" Enter the description of the object whose attributes are eval‐uated in this column. For example: "Action"Default: "Default"

"Value 1" Enter the hierarchical or functional classification of the base object in this column. User classifications are permitted. For example: "C1: M00.A010.A040"Defaults: "Default"

"Value 2" Enter the attributes of the object that are to be matched. For example: "@N;@L;@D;Y00T00001.Y00A03136"Default: "@N;@L;@D"

The "Assembly updater" plugin first checks whether a classification has been stored for the object in the standard table. If the plugin does not find a classification, it uses the default definition.

Reference19.8 Standard table "Y10M00N00032 Assembly Updater Property Mapping PCS 7"


Documents

Automation Base 1 - Siemens · Table of contents Automation Base 1.0 6 Operating Manual, 10/2015 SIMATIC PCS 7 ... interface 1 Objective The plugins in the menu "Plugins > Automation