PCS7 SIEMENS Engineering System PDF
PCS7 SIEMENS Engineering System PDF
PCS7 SIEMENS Engineering System PDF
Introduction to Plant
3
______________
Engineering with PCS 7
SIMATIC Planning the Plant
4
______________
Engineering
Basic Concepts of
6
______________
Engineering
Configuration Manual
Configuration of the PCS 7
7
______________
Engineering System
10
______________
Compiling and downloading
11
______________
Test
13
______________
Servicing
14
______________
Attachment
03/2009
A5E02122455-01
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and
operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes
in this documentation qualified persons are defined as persons who are authorized to commission, ground and
label devices, systems and circuits in accordance with established safety practices and standards.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be adhered to. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
1 Preface .................................................................................................................................................... 15
2 Using the PCS 7 Documentation ............................................................................................................. 21
2.1 Using the PCS 7 documentation.............................................................................................21
2.1.1 Options for Accessing Documentation....................................................................................21
2.1.2 Documentation for the Planning Phase ..................................................................................23
2.1.3 Documentation for the Realization Phase ..............................................................................25
2.1.4 Documentation on commissioning, operation, diagnostics and servicing ..............................30
2.2 Guide to the PCS 7 Engineering System Configuration Manual ............................................31
3 Introduction to Plant Engineering with PCS 7 .......................................................................................... 33
3.1 Structure of a PCS 7 Plant......................................................................................................33
4 Planning the Plant Engineering................................................................................................................ 39
4.1 Before Beginning the Engineering ..........................................................................................39
4.2 PCS 7 Plant Components.......................................................................................................42
4.2.1 How to Find the Right Components........................................................................................42
4.2.2 Important Criteria for Selecting Components .........................................................................46
4.2.3 With Which "Third-Party Systems" can PCS 7 Communicate?..............................................48
4.2.4 How Can the Plant be Protected Against Unauthorized Access? ..........................................50
4.2.5 How can the process management be verified? ....................................................................53
4.2.6 How Can Project and Process Data Be Archived?.................................................................56
4.2.7 What Sources Can Be Used in Planning the Plant Design? ..................................................58
4.2.8 What Service Support Does SIEMENS Offer for PCS 7 ........................................................59
4.3 Capacity Options in Configuring a PCS 7 Plant .....................................................................60
4.3.1 How can PCS 7 be scaled? ....................................................................................................60
4.3.2 How many objects can be handled in a project? ....................................................................61
4.3.3 How Many CPUs are Needed for Automation? ......................................................................65
4.3.4 How Many Devices, Sensors and Actuators can be Integrated? ...........................................66
4.3.5 How Many Operator Stations are Required?..........................................................................67
4.3.6 What are the expansion limits?...............................................................................................68
4.4 Selecting fault-tolerant and fail-safe components...................................................................69
4.4.1 Introduction .............................................................................................................................69
4.4.2 Redundancy Concept of PCS 7..............................................................................................70
4.4.3 Operating Reliability Concept of PCS 7..................................................................................73
4.4.4 Recommended Use of components .......................................................................................76
4.5 Selecting the network components.........................................................................................77
4.5.1 Communication within PCS 7 .................................................................................................77
4.5.2 Which Networks / Bus Systems Are Used for Communication? ............................................78
4.5.3 Fields of Application and Parameters of the Network / Bus Systems ....................................79
4.5.4 Maximum Transmission Rate of the Network / Bus Systems.................................................80
8.11.6 Programming the interface to the I/O (driver blocks) ........................................................... 510
8.11.6.1 Concept for Drivers and Diagnostic Blocks ......................................................................... 510
8.11.6.2 List of Driver and Diagnostics Blocks .................................................................................. 512
8.11.6.3 How to Generate Module Drivers......................................................................................... 514
8.11.6.4 How to Create Your Own Driver Blocks............................................................................... 516
8.11.7 Creating Process Tags from Process Tag Types (Multiproject) .......................................... 517
8.11.7.1 Introduction into Creating Process Tags from Process Tag Types (Multiproject) ............... 517
8.11.7.2 How to Create a Process Tag Type from a CFC Chart ....................................................... 518
8.11.7.3 How to Change a Process Tag Type ................................................................................... 520
8.11.7.4 How to Insert a Process Tag Type to a Project ................................................................... 522
8.11.7.5 How to Create an Import File or Assign it to the Process Tag Type.................................... 523
8.11.7.6 How to Create Numerous Process Tags Automatically....................................................... 525
8.11.7.7 How to Edit a Process Tag .................................................................................................. 526
8.11.7.8 How to Adopt Process Tags ................................................................................................ 527
8.11.7.9 How to Synchronize Process Tags with the Process Tag Type .......................................... 529
8.11.7.10 How to Restore Lost Process Tag Type Assignments ........................................................ 531
8.11.8 Creating Sequential Control Systems (SFC) ....................................................................... 532
8.11.8.1 Introduction to Creating Sequential Control Systems (SFC) ............................................... 532
8.11.8.2 Advantages and Uses of SFC Types/SFC Instances .......................................................... 534
8.11.8.3 Overview of the Steps in Configuration ............................................................................... 536
8.11.8.4 How to Create a New SFC Chart......................................................................................... 538
8.11.8.5 How to Specify the Sequencer Properties ........................................................................... 539
8.11.8.6 How to Create the Topology of the Sequencer.................................................................... 540
8.11.8.7 How to Configure Steps ....................................................................................................... 543
8.11.8.8 How to Configure Transitions............................................................................................... 545
8.11.8.9 How to Adapt the Operating Parameters and Runtime Properties...................................... 548
8.11.8.10 Working with Charts, Types, and Instances ........................................................................ 552
8.11.8.11 How to Configure Messages in SFC.................................................................................... 554
8.11.8.12 How to Create an SFC Type................................................................................................ 555
8.11.8.13 How to Generate an SFC Instance ...................................................................................... 558
8.11.8.14 How to Modify an SFC Type Centrally................................................................................. 559
8.11.8.15 How to Compile Charts and Types ...................................................................................... 561
8.11.8.16 How to Compare SFC Charts before Download.................................................................. 564
8.11.8.17 How to Download SFC Charts to the CPU .......................................................................... 565
8.11.8.18 How to Test SFC Charts ...................................................................................................... 568
8.11.9 Creating Models (Multiproject) ............................................................................................. 570
8.11.9.1 How to Create a Model ........................................................................................................ 570
8.11.9.2 Textual Interconnections and Models .................................................................................. 573
8.11.9.3 How to Generate Replicas from Models .............................................................................. 575
8.11.9.4 How to Work with Models in the SIMATIC Manager............................................................ 577
8.11.9.5 How to Assign Replicas to a Model Later ............................................................................ 579
8.11.10 Editing Mass Data in the Process Object View.................................................................... 580
8.11.10.1 Introduction into Editing Mass Data in the Process Object View......................................... 580
8.11.10.2 Working in the process object view...................................................................................... 582
8.11.10.3 How to Edit the General Data .............................................................................................. 585
8.11.10.4 How to Edit Blocks ............................................................................................................... 587
8.11.10.5 How to Edit Parameters ....................................................................................................... 589
8.11.10.6 How to Edit Signals.............................................................................................................. 593
8.11.10.7 How to Edit Messages ......................................................................................................... 597
8.11.10.8 How to Edit Picture Objects ................................................................................................. 599
8.11.10.9 How to Edit Archive Tags..................................................................................................... 601
8.11.10.10 How to Edit Hierarchy Folders ............................................................................................. 603
Readme File
Current higher-level information can be read in the readme file:
● The readme file can be found on the DVD Process Control System; PCS 7 Toolset.
● You can also open the readme file after installing PCS 7 with the menu command Start >
SIMATIC > Product Notes > English > PCS 7 - Readme.
Conventions
In this documentation the designations of elements of the user interface are specified in the
language of this documentation. If you have installed a multi-language package for the
operating system, some of the designations will be displayed in the base language of the
operating system after a language switch and will, therefore, differ from the designations
used in the documentation.
Guide
This documentation gives you an insight into the key functions of PCS 7. You can also use
this documentation for reference and check the particular information that you require.
The configuration steps are described in a sequence that can be used for practical and fast
configuration. The manual provides important background information and interrelationships
for all of the configuration steps in order to clarify their significance and context in the overall
system.
All work instructions utilize paths that can be accessed via the menu commands of the menu
bar. For many of the functions you also have the option of using commands in the shortcut
menu for the individual objects.
PCS 7 Glossary
You will find a PCS 7 glossary containing definitions of important technical terms used in this
documentation on the DVD SIMATIC PCS 7; Manual Collection or in the PCS 7 software via
the SIMATIC Manager Help menu (menu command Help > Contents > "Glossary" button).
Further Support
If you have any technical questions, please get in touch with your Siemens representative or
responsible agent.
You will find your contact person at:
http://www.siemens.com/automation/partner
You will find a guide to the technical documentation offered for the individual
SIMATIC Products and Systems at:
http://www.siemens.com/simatic-tech-doku-portal
The online catalog and order system is found under:
http://mall.automation.siemens.com/
Training Centers
Siemens offers a number of training courses to familiarize you with the Process Control
System SIMATIC PCS 7. Please contact your regional training center or our central training
center in D 90327 Nuremberg, Germany for details:
Telephone: +49 (911) 895-3200 *)
Internet: http://www.sitrain.com
Technical Support
You can reach the Technical Support for all Industry Automation and Drive Technology
products
● Via the Web formula for the Support Request
http://www.siemens.com/automation/support-request
● Phone: + 49 180 5050 222 *)
● Fax: + 49 180 5050 223 *)
Additional information about our Technical Support can be found on the Internet pages
http://www.siemens.com/automation/service
*) Please note the following if you call the phone number listed: You may incur costs which
vary from the standard costs for land lines. Calls from a cellular network may be more
expensive.
Access Options
You have the following options for accessing the PCS 7 documentation:
● On a PCS 7 computer, via the Help menu in applications
● On a PCS 7 computer, via the Start menu in Windows
● in the Internet
– from Customer Support
– Technical documentation
● On the DVD SIMATIC PCS 7; Manual Collection
In the Internet at
The PCS 7 site provides convenient access to the complete PCS 7 documentation - the
latest news about hardware and software components released for PCS 7:
Call via Internet (http://www.siemens.com/simatic-pcs7): > [Technical documentation Vx.y]
In the following
Since the full documentation of PCS 7 is extremely wide-ranging, you will find a guideline in
the following sections that will help you to find the information you require during various
phases:
● Documentation for the Planning Phase (Page 23)
● Documentation for the Realization Phase (Page 25)
● Documentation on commissioning, operation, diagnostics and servicing (Page 30)
Documentation Content
Information about the range of services
Catalog ST PCS 7 Ordering information and prices for all hardware and software components you may
require for automating a PCS 7 plant
Catalog ST PCS 7.1 Ordering information and prices for SIMATIC PCS 7 add-ons that can be integrated in
your PCS 7 plant to create a total solution
Interactive catalog CA 01 Catalog ST PCS 7 in electronic form
PCS 7 brochures An introduction to the principles of communication and range of features in SIMATIC
PCS 7; shows the technical possibilities and the suitable features for fulfilling your
automation requirements.
Getting Started PCS 7 - First Uses a simple example project to show you the fundamental procedures and the
Steps interaction of the software components of SIMATIC PCS 7 during engineering and
runtime.
Time required for tutorial: approx. 1 hour
Specifying the components and the systems for the PCS 7 plant
Configuration manual PCS 7 Section "Engineering System":
Engineering System • Capacity options in configuring a PCS 7 plant
• Selecting the network components
• Selecting PC components for engineering and operator control and monitoring
• Selecting AS components
• Selecting I/O components
• Preparations for efficient engineering
Manual PCS 7 Comprehensive overview of PC configurations for engineering and operator control and
PC Configuration and monitoring:
Authorization • Areas of application for the various PC configurations
• Design and configuration of the PC networks
• Required hardware and software for the PC components
• Required authorizations and licenses
• Installation instructions and settings for the operating system
• Installation instructions and settings for PCS 7
Documentation Content
Whitepaper Security concept Guide for network administrators for planning and installation of securely networked
PCS 7 and WinCC PCS 7 plants with connected WebNavigator clients, SIMATIC IT applications and
customer-specific office networks:
• Planning security cells and access points
• Managing computers and users
• Managing user permissions and access rights in PCS 7 and integration in the
Windows management
• Implementing patch management
• Secure network access to security cells
List PCS 7 - Enabled modules List of modules released for PCS 7 versions
Function Manual PCS 7 time Support for planning time synchronization in a PCS 7 plant
synchronization
Documentation Content
Installation
PCS 7 readme Latest information with information about installation and using PCS 7 software
PCS 7 What's new? Compact summary of the new or changed features in PCS 7 in comparison to previous
versions
Manual PCS 7 Comprehensive overview of PC configurations for engineering and operator control and
PC Configuration and monitoring:
Authorizations • Which PC configuration can be used for specific purposes?
• How can the PC network be designed and configured?
• Which software and hardware are needed for specific PC components?
• Which authorizations and licenses are required for the individual products?
• Installation instructions and settings for the operating system and PCS 7 software
Whitepaper Security Concept Guide for network administrators for planning and installation of securely networked
PCS 7 and WinCC PCS 7 plants with connected WebNavigator clients, SIMATIC IT applications and
customer-specific office networks:
• Planning security cells and access points
• Managing computers and users
• Managing user permissions and access rights in PCS 7 and integration in the
Windows management
• Implementing patch management
• Secure network access to security cells
Documentation Content
Assembling components and systems
Configuration manual PCS 7 In the section "Configuration of PCS 7 Plants":
Engineering System • Basic configurations of a PCS 7 plant
• Guide to the Installation Instructions for the Products
• Special considerations, differences between PCS 7 and specifications in the product
installation instructionsauanleitungen der Produkte
• Rules for plant changes in runtime (CiR)
• Installation Guidelines for PCS 7: EMC and lightning protection
Function manual Time Instructions for configuration and parameter assignment of time synchronization
synchronization
Manuals for the automation • Instructions for configuring automation systems
system S7-400H/FH • Memory concept and startup scenarios
• Cycle and reaction times of the S7-400
• Technical specifications
• Operation lists
Manuals for S7-300 I/O • Manual for hardware configuration and parameter assignment of components
Modules • Technical specifications
Manuals for CPs and FMs • Manual for hardware configuration and parameter assignment of components
(S7-400, S7-300) • Technical specifications
Manuals for ET 200 • Manual for hardware configuration and parameter assignment of components
components ET 200M, • Technical specifications
ET 200S, ET 200iSP and
ET 200pro
Manuals for additional DP • Manual for hardware configuration and parameter assignment of components
components: Diagnostic • Technical specifications
repeater, DP/PA link/Y link,
DP/AS-i link, DB/EIB link,
DP/FF link
Manuals for Industrial Ethernet • Topologies and Network Configuration
and PROFIBUS networks • Configuration of the communication
Manuals for SIMATIC NET • Topologies and Network Configuration
components: CPs for Industrial • Installation instructions
Ethernet and PROFIBUS, • Technical specifications
SCALANCE X, OSM/ESM ...
Documentation Content
Engineering
Getting Started Introduction to the basic functions of PCS 7 based on the PCS 7 example project
PCS 7 - Part 1 "COLOR". It contains the most important background information required to understand
the individual engineering tasks and detailed instructions for step-by-step retro-
engineering. On completion of configuration, the OS can be put into process mode.
We recommend working through this Getting Started tutorial before beginning work with
the PCS 7 Engineering System configuration manual.
Time required for tutorial: approx. 16 hours
Getting Started Introduction to using the Efficient Engineering functions in PCS 7. The basis for this is
PCS 7 - Part 2 the PCS 7 "COLOR" project in
Getting Started PCS 7 - Part 1.
We recommend working through this Getting Started tutorial if you plan to configure a
large PCS 7 plant with numerous process tags.
Time required for tutorial: approx. 16 hours
PCS 7 Manual Step-by step instructions for converting your PCS 7 project from PCS 7 V6.x to V7.1
Software Update Without without using the new functions of PCS 7 V7.1 subsequently.
Utilization of New Functions
(PCS 7 V6.x or higher to V7.1)
PCS 7 Manual Step-by-step instructions for converting your PCS 7 project from PCS 7 V6.x to V7.1 for
Software Update With using the new functions of PCS 7 V7.1 subsequently.
Utilization of New Functions
(PCS 7 V6.x to V7.1)
Configuration manual PCS 7 Sections for configuring the engineering system:
Engineering System • Basic concepts of engineering
• Configuration of the engineering system
• Implementing the PCS 7 configuration
• Compiling, downloading, testing, archiving and documenting project data
Configuration manual PCS 7 Complete information about configuring the operator station and the HMI system of
Operator Station PCS 7:
• Configuring OS data
• Creating process pictures
• Settings in the alarm system
• Options for archiving
• Downloading a project and configuration changes
• Time synchronization and lifebeat monitoring
• Using server-server communication
• Using diagnostic functions (maintenance station)
Manual PCS 7 • Using the WebNavigator client
OS Web Option
Documentation Content
Manual PCS 7 Information for a better understanding of the integration MES functions in PCS 7 with
Integration of MES Functions SIMATIC IT:
into PCS 7 with SIMATIC IT • Basics of SIMATIC IT and PCS 7
• Implementing the ISS-95/ISS-88 standards
• Integration of SIMATIC IT Historian and SIMATIC BATCH
• Data management in SIMATIC IT and PCS 7
• Functionality and data communication and data flow
• Configuration procedure based on an example project
Manual PCS 7 Complete information about configuring the BATCH station, the system for automating
SIMATIC BATCH batch processes:
• Technological basis according to ISA-88.01
• Configuring batch plant data
• Creating recipes
• Planning and controlling batches
• Managing and archiving batch data
Manual PCS 7 Complete information about configuring the Route Control station, the system for
SIMATIC Route Control controlling routes:
• Creating the program for route control
• Functions of the block library
• Configuring materials and transport routes
Function manual PCS 7 Fault- Description of the solution concepts, function mechanisms and most important
tolerant Process Control configurations for installing fault-tolerant systems with PCS 7. It will show you the fault-
Systems tolerant solutions at all levels of automation (control level, process level, field level).
Function manual PCS 7 High- Comprehensive overview of required components, the interaction among the
precision Stamping components and their configuration for using high-precision time stamps
Function manual PCS 7 time Comprehensive overview of required components, the interaction among the
synchronization components, and their configuration for using time synchronization.
Manual PCS 7 Basic Library Driver and diagnostic blocks
Description of methods of operation, block I/Os and input/output fields of the respective
faceplates
Manual PCS 7 Standard Process automation blocks
Library Description of methods of operation, block I/Os and input/output fields of the respective
faceplates
Manual PCS 7 Advanced Process automation blocks - expandable
Process Library Description of methods of operation, block I/Os and input/output fields of the respective
faceplates
Manual PCS 7 Programming Explanation of how AS blocks and faceplates conforming to PCS 7 can be created to
for Instructions for Blocks achieve the following:
• Monitor parameter values through a faceplate
• Control parameter values and therefore the reactions of blocks through a faceplate
• Report asynchronously occurring events and block states on the OS and display
them in a faceplate or a WinCC message list
Documentation Content
Manual PCS 7 Programming Help in creating driver blocks conforming to the system to fully exploit the functions in
Instructions Driver Blocks PCS 7
(not included with PCS 7; must be ordered extra from the PCS 7 catalog)
Manuals for the individual • Basics of the engineering tool
engineering tools: CFC, SFC, • Working with the engineering tool
STEP 7, SFC visualization, • Testing and commissioning the engineering tool
PDM, WinCC, LT options, SCL,
DOCPRO
Readme and What's new for • Latest information with notes about installation of the engineering tool
the individual engineering tools: • Compact summary of the new or changed features in comparison to previous
CFC, SFC, STEP 7, SFC versions
visualization, PDM, SCL,
DOCPRO
Documentation Content
Process mode
Manual PCS 7 • Graphical user interface and operator input at the PCS 7 OS in process mode:
OS Process Control – Message system
– Trend system
– Group display
– Operator process control
• Working at the maintenance station
Manual PCS 7 • Working with a WebNavigator client
OS Web Option
Configuration manual PCS 7 • Batch control
SIMATIC BATCH • Managing and archiving batch data
Manual PCS 7 • Route control
SIMATIC Route Control • Managing and logging routes
Manual PCS 7 Service Support This documentation is aimed at trained service personnel (Service Level 1): PCS 7 users
and Diagnostics and SIMATIC S7 specialists
This manual contains the information to support you in the following tasks:
• Ensuring the availability of your PCS 7 plant
• Understanding the alarm concept of your PCS 7 plant
• Finding the right diagnostic tools when a fault occurs
• Using the right procedure when a fault occurs and providing qualified, detailed
information about the state of the PCS 7 plant to service experts
Manuals for the automation • Commissioning
system S7-400H/FH • Maintenance
Manuals for CPs and FMs • Diagnostics
(S7-400, S7-300)
Manuals for ET 200 • Commissioning
components ET 200M, • Diagnostics
ET 200S, ET 200iSP and • Maintenance
ET 200pro
Manuals for additional DP • Commissioning
components: Diagnostic • Diagnostics
repeater, DP/PA link/Y link,
DP/AS-i link, DB/EIB link,
DP/FF link
Manual Programming with • Hardware diagnostics and troubleshooting
STEP 7
Section Content
Specifying the components and the systems for the PCS 7 plant
Planning the plant This contains all the information that you need to select the right systems
engineering and components based on the requirements of your PCS 7 plant.
You will receive a complete overview of the installation options for the
following components in PCS 7:
• The automation system
• The distributed I/O
• The bus system
• The network
Assembling components and systems
Configuration of PCS 7 A guide takes you through the manual's instructions on installing the
plants hardware components. In addition, it will provides you with information and
rules about how PCS 7 differs from using SIMATIC.
Engineering
Basic Concepts of Introduction into how the requirements for efficient engineering (for
Engineering example, type-defining, reusability, central editing) are implemented with
PCS 7.
Configuration of the Introduction to the structure and use of the engineering software of PCS 7
PCS 7 engineering
system
Implementing the Complete PCS 7 configuration with step-by-step instructions, relationships
PCS 7 configuration and background information
Adopting the Data from Description of the import/export functions with step-by-step instructions,
the Plant Engineering relationships and background information
Compiling and Information about how configuration data is compiled and downloaded to
downloading the PLCs (AS, OS, BATCH).
Test Overview of the most important testing options prior to commissioning
Comparing project Instructions on how to compare different project versions using the Version
versions with VXM Cross Manager
Service Information about diagnostics, service support, data security, versioning,
and backing up project data
Introduction
PCS 7 offers a wide range of options for implementing automation tasks. The large selection
and variety of components facilitates the following:
● Employment of suitable components for special requirements
● Selection of components that can be configured exactly to meet specific requirements
The following table lists optimally matched systems, components and functions for specific
process control requirements.
Additional information
● Section "Capacity Options in Configuring a PCS 7 Plant (Page 60)"
● Section "Selecting the network components (Page 77)"
● Section "Selection of the PC components for ES, OS, BATCH, Route Control and IT
(Page 126)"
● Section "Selecting AS Components (Page 132)"
● Section "Selecting I/O components (Page 144)"
● Section "Preparation for Efficient Engineering (Page 155)"
Selection Criteria
The selection of components for a process control system involves a variety of factors. The
most important factors are:
● The type of process (continuous or discontinuous)
● The reaction of a plant to disruptions (availability and safe state)
Type of process
There are two process types:
● Continuous process
Process sequence in plants in which "the same product" is produced "unchanged" (e.g.
water desalination plants). Such processes can be automated by PCS 7 using sequential
control system (SFC). The automation can be implemented for small plant units as well
as for the entire plant.
● Discontinuous (batch) process
Process sequence in plants in which "different products" are produced (e.g. various
recipes for producing tablets or mixing paints). Such processes can be automated by
PCS 7 using SIMATIC BATCH. With the recipe-based control strategies in SIMATIC
BATCH, the process sequences of a PCS 7 plant can be flexibly adapted to changing
products, material properties, plant conditions, product stages, etc.
Additional information
● Section "Selecting fault-tolerant and fail-safe components (Page 69)"
● Function manual Process Control System PCS 7; Fault-tolerant Process Control Systems
● Manual Process Control System PCS 7; SIMATIC BATCH
Note
Please contact your Siemens representative for more information about other
communication options.
Additional information
● Section "Administration level and remote access (Page 119)"
● Section "Data Links to Other Systems (Page 113)"
Additional information
● Section "Protecting Projects/Libraries with Access Protection (Page 193)"
● Manual SIMATIC Logon; SIMATIC Electronic Signature
● Configuration manual Process Control System PCS 7; Operator Station
● Whitepaper Security concept PCS 7 and WinCC
Additional information
● Section "Comparing Project Versions with VXM (Page 687)"
● Section "How to Document Changes in the ES Log (Page 676)"
● Section "How to Document Changes in the Change Log (Page 679)"
● Online help for the Version Cross Manager
● Manual Process Control System PCS 7; SIMATIC BATCH
● Manual Process Control System PCS 7; SIMATIC Route Control
● Manual SIMATIC Logon; SIMATIC Electronic Signature
Introduction
SIMATIC PCS 7 provides a variety of functions for archiving project data and process
values.
Note
Use the Version Cross Manager to determine differences between various versions of a
project.
Note
You can view swapped out OS archives using the software product StoragePlus (option kit).
Additional information
● Section "Archiving/Retrieving Multiprojects and Project Master Data"
● Configuration manual Process Control System PCS 7; Operator Station
● Manual Process Control System PCS 7; SIMATIC BATCH
Plant structure
The plant structure is understood as the following:
● How and where the areas of a plant are configured and designed
● Which options are used to equip which areas of a plant
Note
There is no plant structure which can be recommended as universally valid. The designs
involved in engineering a plant for process automation depend on the following factors:
• Laws, regulations, standards
• Process engineering and manufacturing engineering relationships
• Local conditions (location, expansion capability, environmental conditions, etc.)
• Other requirements (e.g. sensors and actuators in use)
Additional information
● Section "Capacity Options in Configuring a PCS 7 plant"
● Section "Which data and data Formats can be imported? (Page 157)
Service Support
You can find support for servicing PCS 7 plants from Siemens on the Internet
(http://www.siemens.com/automation/service&support)
Scalability
SIMATIC PCS 7 can be adapted flexibly in a variety of ways for different plant requirements
and sizes. The configuration can be expanded or modified during later upgrading or if
technological changes are made to the plant.
SIMATIC PCS 7 covers all plant sizes. Depending on the demands you have the following
options:
● To choose between automation systems with different performance capacities – starting
with applications having few control tasks (for example: with SIMATIC PCS 7 BOX) -- up
to the automation of a very large production plant with integrated process data control
● To integrate distributed or central I/Os step-by-step
● To dimension and configure the display and operating components – starting with a small
single station system with approx. 160 process tags for laboratory automation -- up to
distributed multi-station systems with client-server architecture that includes
approx. 60,000 process tags for the automation of a large production plant
● To scale the number of configurable process objects (software for a variety of PO
quantities)
● To define network components and configure communication networks
● To enhance the functionality by systematically adding a variety of hardware and software
components (for example, operator stations with SIMATIC BATCH or a separate archive
server)
● To integrate applications for connecting SIMATIC PCS 7 to the IT world
Capacity Options
The following sections provide information about planning for PCS 7 plant capacity:
● How many process objects can be handled in a project? (Page 61)
● How Many CPUs are Needed for Automation? (Page 65)
● How Many Devices, Sensors and Actuators can be Integrated? (Page 66)
● How Many Operator Stations are Required? (Page 67)
● What are the expansion limits? (Page 68)
Plant size
The configurable size of a PCS 7 plant is scalable.
The software product licenses for an engineering station, operator station, SIMATIC BATCH
station, Route Control station and SIMATIC PDM are available with different license package
options. You can expand these package options using additional Power Packs.
Process object
In PCS 7 version V7.0 SP1 and higher, the following applies for licensing of "PO" process
objects:
All SFCs and all block instances that support operator control and monitoring and that
produce messages are considered to be PCS 7 process objects. These are the objects that
are transferred to the OS and require licenses.
In the CFC, a block that supports operator control and monitoring is assigned the attribute
"S7_m_c" in the block properties.
A process object can be one of the following blocks and objects:
● Blocks for operator control and monitoring of a plant (for example, motors, valves)
● Objects for automation (for example, level control)
● Objects for signal acquisition and signal processing (not channel driver blocks, for
example, MEAS_MON)
Level of licenses
The following table shows the plant capacities suited for PCS 7 and the plant capacity levels
that can be achieved (determined for each component of the process control system).
Additional information
● Manual Process Control System PCS 7; PC Configuration and Authorization
Note
Multicomputing (synchronous operation of more than one CPU) is not possible in PCS 7!
Mixed Capacities
The following provides an example mixed capacities for automation systems in a PCS 7
plant.
NOTICE
The values displayed in the following tables are not AS specific maximum values for the
respective position. They are an example list representing the typical distribution of the total
AS capacity available during mixed operation of all positions in a cohesive block.
Example:
Mixed capacity for automation systems in a PCS 7 plant:
Property Limit
Maximum number of OS server/redundant OS 12
server pairs
Max. number of automation systems per OS 64
server/redundant OS server pair
Maximum number of OS clients in multiclient 32 per multiple station system
mode (when each OS client has access to all 12
OS servers/redundant OS server pairs)
Number of process tags Approx. 3,000 per OS single-user system
Approx. 5,000 per OS server
Approx. 60,000 per multiple station system
Max. number of configurable messages 50,000 per OS server
Number of process values that can be archived Approx. 1,000 process value per second with OS
server
Approx. 10,000 process value per second with
central archive server
Number of OS areas 64 OS areas in 5 levels per OS server
Number of maintenance stations 1 maintenance station for monitoring diagnostic
variables
Max. number of WebNavigator clients 50
Max. number of WebNavigator diagnostic clients 3
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Manual Process Control System PCS 7; PCS 7 OS Web Option
Expansion Limit
Any potential plant expansion depends on the following factors:
● Network type connecting the PCS 7 components
● Distance bridged between the sensors and actuators (taking into consideration the
potential transmission rates)
Since almost all of the sensors and actuators for PCS 7 are integrated in the distributed I/O,
the length of the communications network is a critical factor.
Maximum Expansion
The following bus systems are used in PCS 7 with the following maximum lengths:
Additional information
● Section "Which Networks/Bus Systems Are Used for Communication? (Page 78)"
● Section "Maximum Transmission Rates of the Networks / Bus Systems (Page 80)"
4.4.1 Introduction
Components
The reaction of the plant to faults is an important aspect in process control engineering.
Since the report of a fault is often not enough, the following components are an important
part of process control engineering:
● Fault-tolerant components
● Fail-safe components
Investment Costs
The high investment costs for fault-tolerant and fail-safe components are negligible in
comparison to the costs and losses involved in the loss of production. The higher the costs
resulting from production stoppage, the more advisable the use of fault-tolerant and fail-safe
components.
Fault-tolerant Components
The use of fault-tolerant components in a process control system can minimize the risk of
production loss. A redundant configuration guarantees fault tolerance in a process control
system. This means that all components involved in the process have a backup in
continuous operation. When a fault occurs or one of the control system components fails, the
correctly operating redundant component takes over the continuing control task.
Redundancy Concept
The PCS 7 fault-tolerant components enable you to achieve the desired form of fault
tolerance in all automation levels:
● Operator stations, BATCH stations, Route Control stations, maintenance stations, central
archive server (control level)
● Bus system
● Automation system (process level)
● Distributed I/O (field level)
The following graphic shows the theoretical structure on the basis of a configuration with
fault-tolerant components.
&OLHQWV26FOLHQW%$7&+FOLHQW5RXWH&RQWUROFOLHQW
UHGXQGDQWIDXOWWROHUDQWWHUPLQDOEXV
UHGXQGDQWIDXOWWROHUDQWSODQWEXV
6ZLWFK
)DXOWWROHUDQWDXWRPDWLRQV\VWHP$6
+$6+
(70
(70 6HQVRU
DFWXDWRU
(70
)DLOVDIH
5HGXQGDQW'33$OLQN
352),%863$
352),%86'3
$FWLYHILHOGGLVWULEXWRU
<OLQN
352),%86'3
S
63,29
36,72
+/- 7 8 9
o CODE
Clear ESC
&RQQHFWLRQRIQRQUHGXQGDQW
352),%86'3GHYLFHVWR
. 4 5 6 About
0 1 2 3 Enter MEAS
ULTRAMAT 6
UHGXQGDQW352),%86'3
Additional information
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
Fail-safe Components
Fail-safe automation systems are employed for PCS 7 when a fault could endanger human
life, damage the plant or the environment. Fail-safe automation systems detect both errors in
the process along with internal errors and automatically bring the plant to a safe state when
a fault occurs.
352),%86'3
)PRGXOH
(70 (70
,0 [,0
,VRODWLRQPRGXOH ,VRODWLRQPRGXOHUHGXQGDQW
Safety Mechanisms
The following safety mechanisms are part of the PCS 7 operating reliability concept:
● The PROFIsafe profile is used for safety-related PROFIBUS DP communication between
the F CPU and distributed I/O. The fail-safe automation systems and signal modules can
recognize false user data and trigger the appropriate error responses with this safety
frame.
● Following programming (F program), the configured safety functions are processed twice
in different processor sections of the CPU. Potential errors are detected in a subsequent
comparison of the results.
● Programming errors such as division by zero or a value overflow are intercepted by
special fail-safe CFC blocks (F blocks).
● The following functions increase the level of safety:
– Comparison of F programs
– Detection of modified F-programs per checksum
– Password protected access authorization
Note
An error detected in the F program does not lead to a CPU stop but triggers a
configurable response. It either brings the corresponding F runtime group or the entire
F program into a safe state.
Using ET 200S
ET 200S can also be connected with fail-safe power modules on distributed stations to a fail-
safe automation system S7-400F/FH. The fail-safe power module brings the electronic
modules from ET 200S to a safe state. ET 200S supports the PROFIsafe profile on the
PROFIBUS DP.
Note
To learn which selected standard components can be integrated into a fail-safe automation
system, refer to the catalog Add-ons for the Process Control System SIMATIC PCS 7
(catalog ST PCS 7.1).
Additional information
● Manual SIMATIC Programmable Controllers S7 F/FH
● Manual S7-300 Fail-safe Signal Modules
● Manual SIMATIC ET 200S Distributed I/O System
Introduction
The communication within PCS 7 is based on SIMATIC NET network components that
conform with established worldwide standards. SIMATIC NET includes powerful and robust
components which were developed especially for industrial use. They have the following
properties:
● The components allow for the reliable exchange of data between all levels and
components in the PCS 7 plant.
● The components can be enhanced and expanded using standard components.
SIMATIC NET
SIMATIC NET contains the following components:
● The communication network consists of the transmission medium, the corresponding
connection and transmission components, and the respective transmission methods.
● The protocols and services are used for data communication between the components.
● The communication modules of the automation systems establish the connection to the
communication network (e.g. communication processors CP).
Additional information
Refer to the following documentation for additional information regarding network
architecture, network configuration, network components, and installation instructions:
● List PCS 7 - Enabled modules
● Manual SIMATIC NET NCM S7 for Industrial Ethernet
● Manual SIMATIC Net PROFIBUS Networks
● Manual SIMATIC NET; Triaxial Networks
● Manual SIMATIC Net Twisted Pair and Fiber-Optic Networks
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-400
● Configuration Manual Industrial Communication; Industrial Ethernet Switches
SCALANCE X-300 SCALANCE X-400
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-200
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-300
● Manual Industrial Ethernet OSM/ESM; Network Management
● Manual SIMATIC NET; AS Interface – Introduction and Basic Information
Note
We recommend the isolation of the system bus and the terminal bus. For smaller
configurations, however, this is not strictly necessary.
The MES level should always be connected via a router. This prevents unauthorized access
to the process control system.
Additional information concerning the PCS 7 security concept can be found on the Internet
(Page 174).
Ethernet/Gigabit Ethernet
The network components used in PCS 7 are Industrial Ethernet components modern
Ethernet/Gigabit Ethernet technology. This means the following:
● Communication speed of 100 Mbit/s (Fast Ethernet)
or 1 Gbit/s (Gigabit Ethernet)
● Using switching technology
● Redundancy using optical/electric rings
Additional information
● Section "Data Paths over the Terminal Bus and System Bus (Page 174)"
● Whitepaper Security Concept PCS 7 and WinCC
See also
Security concept (http://support.automation.siemens.com/WW/view/en/28580051)
SCALANCE X
SCALANCE X is the switch product family of Industrial Ethernet switches from
SIMATIC NET. Switches are active network components that distribute data to targeted
addressees.
● SCALANCE X202-2IRT
SCALANCE X202-24IRT with 2 electrical and 2 optical ports (up to 100 Mbit/s) for use in
subsystem networks with strict real-time requirements (Isochronous Realtime) and
maximum availability.
Data traffic with no real-time requirement can take place on the same network.
Duplicate network structures are therefore not required.
The redundancy manager integrated in the SCALANCE X202-2IRT enables the
configuration of redundant ring structures.
● SCALANCE X208
SCALANCE X208 with 8 ports for transmission rates up to 100 Mbit/s, suitable for
electrical Industrial Ethernet structures in linear, star or ring configurations.
● SCALANCE X204-2
SCALANCE X204-2 with 2 optical and 4 electrical ports for transmission rates up to 100
Mbit/s, suitable for optical Industrial Ethernet structures in linear or ring configuration.
5HGXQGDQWFOLHQWV26FOLHQW%$7&+FOLHQW5RXWH&RQWUROFOLHQW
UHGXQGDQWIDXOWWROHUDQW7HUPLQDOEXV
UHGXQGDQWIDXOWWROHUDQW3ODQWEXV
6ZLWFK
)DXOWWROHUDQWDXWRPDWLRQV\VWHP
$6+$6+
Additional information
● Section "Data Paths over the Terminal Bus and System Bus (Page 174)"
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-400
● Configuration Manual Industrial Communication; Industrial Ethernet Switches
SCALANCE X-300 SCALANCE X-400
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-200
● Operating Instructions Industrial Communication; Industrial Ethernet Switches
SCALANCE X-300
● Operating Instructions Industrial Communication; Industrial Ethernet SCALANCE X-100
and SCALANCE X-200 product line
Using Optical Switch Modules (OSM) and Electrical Switch Modules (ESM)
OSM/ESMs allow the configuration of "switched networks" with 100 Mbps that meet stringent
requirements for availability and comprehensive diagnostics.
Two measures are employed to decouple the load on the networks thereby leading to an
increase in network performance:
● Formation of segments, i.e., dividing the networks in subnetworks/segments
● Connecting each segment to an OSM/ESM
An OSM/ESM disposes of additional ports (with RJ45, ITP or BFOC interfaces as options) to
which terminals and additional network segments can be connected.
The redundancy manager integrated in the OSM/ESM enables configuration of redundant
ring structures.
Up to 50 OSM (optical ring) / ESM (electrical ring) can be used per ring.
260 260
1HWZRUN 1HWZRUN
260LQ
50PRGH
OSM TP62
OSM
260 2/0
(60 (60
1HWZRUN
(60
(/0
,73VWDQGDUG )LEHURSWLF)2
73;3FRUG 7ULD[LDOFDEOH
73FRUG5- 6SXUOLQH'URSFDEOH
Additional information
● Section "Data Paths over the Terminal Bus and System Bus (Page 174)"
● Manual Industrial Ethernet OSM/ESM; Network Management
Additional information
● Manual SIMATIC Net Twisted Pair and Fiber-Optic Networks
3&6WDWLRQIRU(626%$7&+5RXWH&RQWURO
1HWZRUN0RGXOH
Ethernet
,QGXVWULDO(WKHUQHW
Industrial
$XWRPDWLRQ6\VWHP
&3
Connection of the AS
The automation system is connected to Industrial Ethernet via TCP/IP or ISO via the
communication processor CP 443-1 or via the Ethernet interface of the CPU.
Connecting PC Stations
Operator stations, BATCH stations, Route Control stations, maintenance stations, the central
archive server, OpenPCS 7 station, and engineering stations are connected to Industrial
Ethernet via communication modules. The communication modules require a slot in the PC
or programming device (PG). Depending on the requirements, different types of
communication modules are used:
● Communication modules without an onboard processor (Basic Communication Ethernet -
BCE) are sufficient for connecting up to 8 lower-level automation systems (of one
operator station). As an alternative, they can also be connected over the following
components:
– Ethernet card supplied with the PC/PG
– Desktop adapter network card (Intel PRO/1000 GT, Intel PRO/1000 PT)
● If the maximum number of 8 automation systems per operator station is not enough or if
fault-tolerant automation systems are connected, communication modules with onboard
processors can be used:
– CP 1613/CP 1623 with S7-1613 software
– CP 1613/CP 1623 with S7 REDCONNECT software for redundant communication
with S7-400H/FH
Note
Communication can be established with up to 64 automation systems (including
redundant systems) using CP 1613/CP 1623.
Time-of-Day Synchronization
CP 443-1 and CP 1613/CP 1623 support time synchronization over Industrial Ethernet. A PC
with a CP 1613/CP 1623 can receive time frames from the following time transmitters:
● SIMATIC S7-400/H/FH with CP 443-1
● SIMATIC NET real-time transmitter for Industrial Ethernet (for information see catalog IK
PI)
● SIMATIC SICLOCK
● PC with CP 1613/CP 1623
You will find additional information on this topic in Function Manual Process Control System
PCS 7; Time Synchronization.
Additional information
● Section "Data Paths over the Terminal Bus and System Bus (Page 174)
26VHUYHU
26VHUYHU
5HGXQGDQW26
VHUYHUSDLU
6ZLWFK0RGXO
)DXOWWROHUDQWV\VWHPEXV
,QGXVWULDO(WKHUQHW
)DXOWWROHUDQW 6SDWLDOO\VHSDUDWHG
DXWRPDWLRQV\VWHP PRXQWLQJUDFNV
6+ZLWK&38V HDFKZLWKWZR&3
$6+ PRGXOHV
$6+
6\QFKURQLVDWLRQOLQH
26VHUYHU
26VHUYHUV
UHGXQGDQW26VHUYHUSDLU
6ZLWFKPRGXOH
UHGXQGDQWIDXOWWROHUDQWSODQWEXV
,QGXVWULDO(WKHUQHW
)DXOWWROHUDQW 6SDWLDOO\VHSDUDWH
DXWRPDWLRQV\VWHP UDFNVHDFKZLWKWZR
6+ZLWK&38V &3
$6+
$6+
6\QFKURQL]DWLRQOLQHV
Switches
All switches (SCALANCE X-400/-300/-200/OSM/ESM) feature 2-ring ports to enable
connection to double Ethernet ring structures. With OSM and ESM, the relevant pair is
synchronized via a synchronization line.
Additional information
● Section "Using Switching Technology with SCALANCE X (Page 84)"
● Section "Using Switching Technology with OSM/ESM (Page 88)"
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
● RS 485-Repeater
● RS 485 terminating element
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
/RQJGLVWDQFHZLWK
ILEHURSWLF
352),%86'3
s
G
M
S
V
B
H
N
T
W
C
I
O
U
X
SIMA TIC P ANEL PC
D
J
P
7
E
K
Q
8
F
L
R
9
4 5 6
Y Z A
1 2 3
. 0 +/-
INS
DEL
ESC
TAB
HELP ACK
,QWHJUDWHG
3RZHUVXSSO\
7HUPLQDOUHVLVWRU
352),%86'3
([LVRODWLRQ
352),%863$
'33$/LQN
([LVRODWLRQ
DQGUHSHDWHU
(7L63
352),%86'3
1
0
56L6FRXSOHU
Introduction
Shielded, twisted pair cables are used as the transmission media for electrical PROFIBUS
networks. PROFIBUS nodes are connected to bus lines via a bus terminal with a spur line or
bus cable connectors.
PROFIBUS segment
A PROFIBUS segment is formed by a bus cable terminated at both ends with surge
impedance. The individual PROFIBUS segments are connected together with repeaters. The
maximum segment line length depends on the following factors:
● Transmission rate
● Type of line used
The maximum line length for a PROFIBUS segment is limited. You can find information
about this in the section "Maximum Transmission Rates of the Networks / Bus Systems
(Page 80)".
RS 485-Repeater
The RS 485 repeater is a signal amplifier. It allows the cable length to be increased. A
maximum of 9 RS 485 repeaters can be connected in series. The following line lengths are
possible between two nodes for RS 485 repeaters:
RS 485-iS Coupler
The RS 485-iS- coupler is an isolating transformer used for intrinsically safe transfer of
PROFIBUS DP in hazardous areas (potentially explosive atmosphere).
The RS 485-iS coupler is required to connect intrinsically safe PROFIBUS DP nodes, for
example, ET 200iSP or third-party devices with Ex i DP connection, to PROFIBUS DP. The
RS 485-iS coupler can also be used as a repeater in hazardous areas.
Additional information
● Manual SIMATIC Net PROFIBUS Networks
● Manual SIMATIC, Distributed I/O Device ET 200 iSP
Recommendation
Note
Recommendation: fiber-optics are preferred for long distances or when connecting between
buildings.
Glass fiber-optics or plastic fiber-optics are used as the transmission media for optical
PROFIBUS networks.
)DLOVDIH
DXWRPDWLRQV\VWHP$6)$6)
,0
352),%86'3
&RSSHUFDEOH
(70
ZLWKVWDQGDUG,2PRGXOHV
,0)2
2%7
(70
ZLWKIDLOVDIH,2PRGXOHV
,0)2
2%7
(70
ZLWKIDLOVDIH,2PRGXOHV
3ODVWLF)LEHU2SWLFFDEOH
Additional information
● Manual SIMATIC Net PROFIBUS Networks
● Manual SIMATIC Net Twisted Pair and Fiber-Optic Networks
'3,QWHUIDFHLQWKH&38 &3([WHQGHG
$XWRPDWLRQ6\VWHP
(70
352),%86'3
(70
Connection of the AS
Automation systems are connected to PROFIBUS DP over the following components:
● CP 443-5 Extended
● Internal PROFIBUS DP interface of the CPU
The PROFIBUS DP lines can be connected to a maximum of 4 internal PROFIBUS DP
interfaces per automation system (with add-on modules depending on the CPU) and also to
a maximum additional 10 CP 443-5 Extended. IF 964-DP interface modules are available for
the PROFIBUS DP interfaces. These can be installed in the open module slots of the CPU.
Redundant PROFIBUS DP
The fault-tolerant automation system S7-400H features a PROFIBUS DP master interface on
each CPU for connecting to the PROFIBUS DP. For switched distributed I/O, the PROFIBUS
DP is connected to the I/O device through two IM 153-2 interface modules.
Configuration options: The following fault-tolerant communication solutions are offered for
PROFIBUS DP:
● Redundant PROFIBUS DP as an electrical network
● Redundant optical network with OLM with line, ring and star structure
$XWRPDWLRQV\VWHP$6+$6+
352),%86'3PDVWHULQWHUIDFH
RQHDFK+&38
'XDOFKDQQHOVZLWFKHG,2(70FRQVLVWLQJ
352),%86'3
(70 RI[,0DQG[60
5HGXQGDQW,2
PRGXOH
(70
6HQVRU
Additional information
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
Y link
To implement the changeover from a PROFIBUS master system to a single-channel
PROFIBUS master system, the Y link is preferred as the gateway.
)DXOWWROHUDQWDXWRPDWLRQV\VWHP
$6+$6+
[,0
352),%86'3
<OLQN 6XERUGLQDWH'3PDVWHUV\VWHP
S
63,29
36,72
+/- 7 8 9 Clear ESC
. 4 5 6 Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
<FRXSOHU
&RQQHFWLRQRIQRQUHGXQGDQW
352),%86'3GHYLFHVWR
UHGXQGDQW352),%86'3
Note
Use only the active backplane bus module when configuring the Y link .
Additional information
● Manual DP/ PA Link and Y Link Bus Couplings
DP/PA Link
The DP/PA link is the preferred gateway between PROFIBUS DP and PROFIBUS PA.
DP/PA Coupler
The DP/PA coupler is a physical link between PROFIBUS DP and PROFIBUS PA. The
DP/PA coupler is available in both Ex and Non-ex variations.
When few numbers are involved, the real-time requirements are not important, and no
redundant PROFIBUS DP is used, the DP/PA coupler can also be operated in "stand-alone"
mode (without IM 153-2).
$XWRPDWLRQ6\VWHP
'33$&RXSOHU
352),%863$
352),%86'3
,0
'33$/LQN
PD['33$&RXSOHU
352),%863$
Additional information
● Manual DP/ PA Link and Y Link Bus Couplings
Redundant PROFIBUS PA
PROFIBUS PA can be configured as redundant to supplement the redundant PROFIBUS
DP.
A redundant PROFIBUS PA is connected to redundant DP/PA couplers. If a communication
path fails, the communication path is preserved as far as the spur line to the field devices.
6+
'33$OLQNZLWKUHGXQGDQW,0
DQGUHGXQGDQW'33$
FRXSOHU)'&
)DXOWWROHUDQW
$)' $)'
352),%863$
352),%86'3
352),%86'3
0D[$)'
0D[
'33$OLQNZLWKUHGXQGDQW,0
DQGUHGXQGDQW'33$
FRXSOHU)'&
)DXOWWROHUDQW
$)6
352),%863$
0D[
Additional information
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
Diagnostic repeaters
We recommend the use of diagnostic repeaters to provide detailed diagnostics for
PROFIBUS DP segments (copper cable). When a fault occurs it sends a diagnostic alarm to
the DP master with detailed information about the type of fault and the location.
Principle: To be able to localize a problem in the network, the diagnostic repeater must know
the topology of the PROFIBUS subnet to which it is attached. With the function "Prepare Line
Diagnostics", the diagnostics repeater determines the distances to all nodes and saves the
data internally in a table. By calculating the distance to a line fault, the repeater can then
identify the nodes between which the fault is located based on the table.
3ODQWEXV,QGXVWULDO(WKHUQHW
/RQJGLVWDQFHV
ZLWKILEHURSWLF
'LDJQRVWLF
352),%86'3 UHSHDWHU
2/0 2/0 s
POWER TEMP
SIMA TIC P ANEL PC
A B C D E F
G H I J K L
M N O P Q R
S T U
7 8 9
V W X
4 5 6
Y Z A
1 2 3
. 0 +/-
INS
DEL
352),%86'3
ESC
TAB
HELP ACK
352),%863$
Ex
'33$/LQN
([LVRODWLRQ
DQGUHSHDWHU
352),%86'3L6
Ex
1
0
Note
Only use the active backplane bus module.
Additional information
● Manual SIMATIC Diagnostic Repeater for PROFIBUS-DP
● Manual Process Control System PCS 7; Service Support and Diagnostics
Introduction
Within the context of PCS 7, Totally Integrated Automation (TIA) provides solutions for
configuring a wide range of communication tasks.
AS interface (ASI)
The actuator sensor interface (AS interface) is a heterogeneous network system for simple,
usually binary actuators and sensors at the lowest field level. The AS interface is an
international standard based on EN 50 295.
The AS interface allows you to address all connected sensors and actuators on a
common 2-wire cable while at the same time supplying them with the required power.
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
(70
$6,QWHUIDFH
352),%86'3
INTERFACE
0 0 0
'3$6,QWHUIDFH $FWXDWRUV
/LQN VHQVRUV
%UDQFK 0 0
$6L
3RZHUVXSSO\
Additional information
● Manual SIMATIC NET DP/AS INTERFACE LINK Advanced
● Manual SIMATIC NET DP/AS Interface Link 20E
3ODQW%XV,QGXVWULDO(WKHUQHW
$XWRPDWLRQ6\VWHP
'3(,%/LQN
KNX
R
00 00
00 7
00 00
352),%86'3
s PROFIBUS
Addr.
6GK1415-0AA00
instabusEIB
Power DP/EIB-Link
DP/BF
EIB/BF
24V EIB
Phys. Adr.
$UHD&RXSOHU
6WDWLRQ
0 1
%XVOLQH
DP/EIB Link
The following DP/EIB links can be used:
● DP/EIB link with IP20 degree of protection
Additional information
● Manual SIMATIC NET DP/EIB Link
MODBUS
MODBUS is an open serial communication protocol. The Modbus protocol is used to network
third-party systems. Due to the maximum transmission rate of 38.4 Kbps, Modbus is
recommended when there are few bus nodes and low real-time requirements.
CP 341
The CP 341 is available in the following 3 models (interface physics):
● RS 232C (V.24)
● 20 mA (TTY)
● RS 422/RS 485 (X.27)
Special drivers are needed for Modbus master and Modbus slave to implement the Modbus
link. These must be ordered separately.
Additional information
● Manual SIMATIC CP 340 Point-to-Point; Installation and Parameter Assignment
● Manual SIMATIC Loadable Drivers for PtP CPs; MODBUS Protocol RTU Format; S7 is
Master
● Manual SIMATIC Loadable Drivers for PtP CPs; MODBUS Protocol RTU Format, S7 is
Slave
Foundation Fieldbus H1
Foundation Fieldbus H1 uses the same physical bus characteristics as PROFIBUS PA
confirming to IEC 61158-2 with a transmission rate of 31.25 Kbps. This technology enables
you to network intrinsically safe, bus-powered FF devices (H1 bus components with FF
interface). The voltage provided by the bus to supply the devices is superimposed by an
information signal from the respective transmitting device.
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
'3))/LQN
352),%86'3
Fieldbus
F o u n d a t i o n
TM
DP/FF Link
The following DP/FF links can be used:
● DP/FF Link
Additional information
Note
When connecting MIS-/MES systems to SIMATIC PCS 7 also observe the information in
Whitepaper Security Concept PCS 7 and WinCC.
SIMATIC IT
SIMATIC IT is a technology platform for MES (Manufacturing Execution Systems), based on
the ISA 95 standard. According to this standard, explicit business and production rules
coordinate functionality to achieve optimal workflow.
SIMATIC IT has the following main elements:
● SIMATIC IT Modeler
● SIMATIC IT Components
SIMATIC IT Modeler
SIMATIC IT Modeler connects the automation level with the ERP (Enterprise Resource
Planning) level:
● Plant control and production control levels
● Company and design level
SIMATIC IT Modeler is a cross-industry integration and coordination platform for operating
processes, data, and functions. In addition to the basic functions for internal procedural
control, user administration, etc. it also possesses the facility for plant and production
modeling.
SIMATIC IT Components
The functions and architecture of the SIMATIC IT Production Modeler and SIMATIC IT
components conform to the ISA-95 standard. Each SIMATIC IT component is reserved for a
specific task that corresponds to a function of the ISA-95 standard.
Together, the components fulfil all the standard production functions of the ISA-95 standard.
The ISA-95 terminology is used in the SIMATIC IT software (e.g. "Material list").
SIMATIC IT components:
● SIMATIC IT Production Suite (basic MES functions such as material management,
production order management, etc.)
● SIMATIC IT Historian (plant performance analysis and archiving)
● SIMATIC IT Unilab (laboratory information management system)
● SIMATIC IT Interspec (product specification management system)
● Detailed Production Scheduler
● SIMATIC IT Libraries
Connection of PCS 7
The SIMATIC PCS 7 process control system is integrated into SIMATIC IT via the CP 443-1.
Additional information
● Function Manual SIMATIC PCS 7/SIMATIC IT; Integration Pack 2007
● on the Internet (http://support.automation.siemens.com/WW/view/en/26639558)
OPC
OLE for Process Control (OPC) provides a standard mechanism for communicating with
numerous data sources. It does not matter whether these sources are machines in your
factory or a database in your control room. OPC is based on the OLE/COM technology from
Microsoft.
For detailed information about OPC, refer to the documentation OLE for Process Control
Data Access Standard, Version 2.0, published by the OPC Foundation.
Additional information
● Documentation OLE for Process Control Data Access Standard, Version 2.0
● You can access the OPC Foundation address on the Internet
(http://www.opcfoundation.org)
OpenPCS 7
A PC station with OpenPCS 7 (OpenPCS 7 station) can be used to exchange data with
external systems without the need for either knowledge of the topology or a PCS 7 OS
installation.
You can use OpenPCS 7 for data exchange with the following levels:
● Automation level
● Plant control and production control levels
● MES level (Manufacturing Execution Systems)
● ERP level (Enterprise Resource Planning)
Access Options
The following table show the PCS 7 data you can access via OpenPCS 7.
License
Note
Access to the corresponding PCS 7 data is only ensured when a license is installed. You can
find more information about this in the manual Process Control System PCS 7; PC
Configuration and Authorization.
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
(70
$6LQWHUIDFH
352),%86'3
INTERFACE
0 0 0
$FWXDWRUV
'3$6,QWHUIDFH
VHQVRUV
/LQN
%UDQFK 0 0
$6L
3RZHUVXSSO\
Figure 4-1 Example: Connecting to the IT world via OpenPCS 7
Additional information
● Section "Structure of the OpenPCS 7 station (Page 172)"
● Section "How to insert and configure an OpenPCS 7 station (Page 285)"
● Section "How to configure OpenPCS 7 stations for accessing PCS 7 data (Page 617)"
Note
Not all functions are available. You will find more detailed information on the availability of
the functions in the function manual Process Control System PCS 7; OS Web Option.
Additional information
● Manual Process Control System PCS 7; PCS 7 OS Web Option
4.6 Selection of the PC components for ES, OS, BATCH, Route Control
and IT
Note
Please note the following:
• Engineering station PCs with higher clock rates, more RAM and larger, faster hard drives
are advantageous during multiproject engineering.
• If the central archive server is used in conjunction with large amounts of data, we
recommend that you use the premium server listed in the ST PCS 7.1 catalog (SIMATIC
PCS 7 add-ons). We recommend the use of at least a RAID1 system in order to increase
the availability of the data on the central archive server.
• CPU speeds with at least 3.4 GHz or dual processor systems are recommended for
BATCH servers.
Color Monitor
We recommend monitors with a minimum resolution of 1280 x 1024 or higher in order to take
full advantage of the PCS 7 software graphics potential.
Network
The network for PCS 7 systems must be isolated using switches, routers, or gateways to
prevent interference to the PCS 7 network from office networks.
Additional information
● Manual Process Control System PCS 7; PC Configuration and Authorization
● Whitepaper Security Concept PCS 7 and WinCC
● ST PCS 7.1 catalog (add-ons for SIMATIC PCS 7)
Basic Hardware
Special versions of the basic hardware (bundles) are available for engineering stations (ES),
operator stations (OS), BATCH stations (BATCH), Route Control stations and for connecting
SIMATIC PCS 7 to the IT world. The bundles are optimized for special applications.
Color Monitors
The Siemens industrial monitor series SCD, SCM and CRT are available for use as PCS 7
process monitors. These are selected based on the ambient temperature of the plant.
A maximum of 4 monitors can be connected to a station (OS client) using a multi-VGA card.
Plant areas that have been split up in this way can be managed using 1 keyboard and 1
mouse.
Additional information
● Catalog ST PCS 7
● Catalog ST PCS 7.1 (Add-ons for SIMATIC PCS 7)
Signal Module
OS single station systems and OS clients can be expanded with a signal module. These
signal modules can control a horn and a maximum of 3 different lamps or buzzer tones that
represent a variety of message classes.
Using a hardware timer (watchdog), the signal modules can detect and signal the failure of
an operator station. A hardware acknowledgment button can also be connected.
The signal modules are installed in a PCI slot in the operator station.
Sound Card
You can also use a standard sound card installed in the operator station.
Additional information
● You can find information about the function and the installation of signal modules in
WinCC Information System under "Options > Options for Process Control".
● You can find more information about the configuration of audible signal devices in the
configuration manual Process Control System PCS 7; Operator Station.
Note
A list of all the modules that can be used for a PCS 7 version is available in the document
PCS 7 - Released Modules.
5DFN85+ %DVLFV\VWHP6+
5DFN 5DFN
Rack UR2-H
The UR2-H is a compact, special rack with a split backplane bus and therefore suitable for
configuring a complete fault-tolerant automation system.
Synchronization Modules
The synchronization modules link both of the CPUs. They are installed in the CPU and
interconnected with fiber-optic cable. Two synchronization modules are installed in each
CPU.
Parameter Default value PCS 7 Default value PCS 7 Default value PCS 7
CPU 414-3XJ00 CPU 416-2XK02 CPU 417-4XL00
CPU 414-4HL01 CPU 416-3XL00 CPU 417-4HL01
Cycle load from communication 20 20 20
[%]
OB 85 call at I/O access error Only for incoming Only for incoming Only for incoming
and outgoing errors and outgoing errors and outgoing errors
Cycle monitoring time [ms] 6,000 6,000 6,000
Minimum cycle time [ms] 0 0 0
Local data (priority classes): 1,024 1,024 1,024
1-2, 9-12, 16, 24-28
Local data (priority classes): 256 256 256
3-8, 13-15, 17-23, 29
User local data area (bytes) 16,384 17,000 32,768
Process image 768 416-2: 2,048 3,072
(I+O each) (bytes) 416-3: 3,072
Number of messages in the 3,000 3,000 2.400
diagnostic buffer
Max. communication jobs 600 1,800 3,000
Monitoring time for finished 650 650 650
message from modules [100 ms]
Monitoring time for transferring 600 600 600
parameters to modules [100 ms]
Acknowledgment-triggered Off Off Off
messaging (QTM; SFB 33-35)
Reasons for STOP message On On On
Startup at POWER ON Warm restart Warm restart Warm restart
Clock memory None None None
Time-of-Day Synchronization None None None
(QJLQHHULQJVWDWLRQ
LQFOXGLQJOLFHQVH
6+V\VWHP
2SHUDWRUVWDWLRQ
3ODQWYLVXDOL]DWLRQ
3ODQWEXV,QGXVWULDO(WKHUQHW
)DXOWWROHUDQWDXWRPDWLRQV\VWHP
$6+$6+RSWLRQDOO\ZLWKUHGXQGDQW
SRZHUVXSSO\
'XDOFKDQQHOVZLWFKHG,2(70
352),%86'3
(70 FRQVLVWLQJRI[,0DQG[60
5HGXQGDQW,2PRGXOH
(70
6HQVRU
Mixed operation
Note
Fault-tolerant and standard automation systems can be used in mixed operation.
Additional information
● Manual Process Control System PCS 7; Fault-tolerant Process Control Systems
FH Systems
Fail-safe automation systems can be configured as single-channel (F system with one CPU)
or as redundant (FH system). The redundancy of the FH systems is not relevant for failure
safety. Redundancy is not used for detecting errors but rather to increase the availability of
fail-safe automation systems.
(QJLQHHULQJVWDWLRQ
LQFOXGLQJRSWLRQSDFNDJH
6)V\VWHP
2SHUDWRUVWDWLRQ
3ODQWYLVXDOL]DWLRQ
Ethernet
3ODQWEXV,QGXVWULDO(WKHUQHW
Industrial
)PRGXOH (70
352),%86'3
352),%86'3
352),%86'3
(70 (70
,0 [,0
,VRODWLRQPRGXOH
)V\VWHP )+V\VWHP )+V\VWHPZLWK
UHGXQGDQW,2
Additional information
● Manual SIMATIC Programmable Controllers S7 F/FH
● Manual S7-300 Fail-safe Signal Modules
I/O Components
PCS 7 offers a wide range of options for connecting I/O devices and for recording and
outputting process signals via sensors and actuators:
● Analog and digital input/output modules of the S7-400 operated centrally in the
automation system
● ET 200M, ET 200S, ET 200iSP distributed I/O systems connected to the automation
system via PROFIBUS DP with a comprehensive range of signal and function modules
● Direct connection of intelligent, distributed field/process devices and operator terminals
via PROFIBUS DP/PA (also redundant or in hazard zones 0, 1 or 2)
Note
PCS 7 only supports diagnostics for the signal and function modules listed in the document
PCS 7 - Released Modules.
In addition, all other signal modules from the current S7-400 and S7-300 product range can
also be used. When used, the integration of these other signal modules is limited to process
data. This means the full diagnostics capability of PCS 7 is not automatically available.
Note
The following PCS 7 functions can not be used with central S7-400 signal modules:
• Configuration Change in RUN
• Signal modules redundancy
• Fail-safe signal modules
(QJLQHHULQJ6WDWLRQ2SHUDWRU6WDWLRQZLWK6,0$7,&3'0
ORFDOFRQILJXUDWLRQRIILHOGGHYLFHVIRU352),%86'3
352),%863$DQG+$57
3ODQW%XV,QGXVWULDO(WKHUQHW
$XWRPDWLRQ6\VWHP
(70
352),%86'3FRQQHFWLRQ
YLD(70
(7L63
352),%86'3
+$57 352),%86'3FRQQHFWLRQ
0
YLD(7L63
Ex
'33$/LQN
352),%863$
352),%86'3FRQQHFWLRQ
YLD'33$/LQN
)LHOGGHYLFHVRQ
S
36,72
+/- 7 8 9 Clear ESC
. 4 5 6 Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
Overview
The following table shows the automation systems in which the distributed I/O system
ET 200 can be used.
Additional information
● Section "Overview of Usable Distributed I/O System ET 200 (Page 148)"
What is HART?
HART (Highway Addressable Remote Transducer) is serial transmission method used to
transmit additional parameter data, such as measurement range or damping, etc., to
connected measuring transducers and actuators over a 4 mA - 20 mA current loop.
Use in PCS 7
HART devices can be used within PCS 7 in the following manner:
● HART devices can be connected to the distributed I/O system ET 200M in both standard
environments and hazardous areas. Special S7-300 hazardous area signal modules with
HART enable connection to HART devices certified for use in hazardous areas. The
S7-300 hazardous area modules with HART are diagnostics capable (with channel and
module diagnostics).
● HART devices can be connected to special analog HART electronic modules of the
distributed I/O system ET 200iSP.
All transducers or HART actuators certified for digital communication using the HART
protocol can be connected through the ET 200M and ET 200iSP.
Example configuration
(QJLQHHULQJ6WDWLRQ2SHUDWRU6WDWLRQZLWK6,0$7,&3'0
FHQWUDOL]HGFRQILJXUDWLRQRIILHOGGHYLFHVIRU352),%86'3
352),%863$DQG+$57
3ODQW%XV,QGXVWULDO(WKHUQHW
$XWRPDWLRQ6\VWHP
352),%86'3
(70
352),%86'3/LQN
YLD(70
(7L63
1
+$57
Ex 352),%86'3/LQN
0
YLD(7L63
Configuration in RUN
The following table provides an overview of the permitted configuration changes that can be
made to the distributed I/O during ongoing operation (CPU RUN).
Additional information
● Section "Rules for Configuration Changes in RUN (CiR) (Page 185)"
$QODJHQEXV,QGXVWULDO(WKHUQHW
6WDQGDUG 26
$XWRPDWLVLHUXQJV
V\VWHP
(LJHQVLFKHUH
352),%86'3
(70 %HGLHQHLQKHLW
0
$NWRUHQ
6HQVRUHQ
352),%86'3 (7L63
56L6.RSSOHU 0
0 $NWRUHQ
6HQVRUHQ
'33$/LQN
352),%863$ =RQH
=RQH
=RQH
Legend to figure
Data Import
The table supplies the following information:
● The task in which data can be imported
● The data formats that can be imported
● The application in which the data can be generated
Additional information
● Section "Import and Reuse of Plant Data (Page 217)"
● Section "Adopting the Data from the Plant Engineering (Page 627)"
Introduction
Recurring technological functions are supported by the following functions in PCS 7:
● Templates
Templates (standard types, standard solutions) are provided to support you in the
configuration of a PCS 7 plant. They are contained in the PCS 7 Standard Library and
PCS 7 Advanced Process Library.
● Type concept
We recommend the additional combining of similar functions to improve the efficiency of
the plant engineering. Similar functions can be configured by using reusable objects
(such as process tag types and models).
Additional information
● Section "Adopting the Data from the Plant Engineering (Page 627)"
Basic Components
The following figure shows the basic components of a PCS 7 plant.
,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
$6 &HQWUDOL]HG,2
352),%86'3
'LVWULEXWHG,2
Legend to figure
Additional information
● Section "Connecting Network Nodes to Ethernet (Page 91)"
● Section "Connecting PROFIBUS DP Nodes (Page 102)"
Engineering Station
Engineering stations are PCs on which the PCS 7 engineering software for configuring a
PCS 7 project is installed.
Connect an engineering station to the plant and terminal bus to download the configuration
data to the PLC (OS, BATCH, Route Control, AS) and to test in process mode.
265RXWH&RQWURO&OLHQWV %$7&+&OLHQWV
(QJLQHHULQJ
6WDWLRQ
7HUPLQDO%XV,QGXVWULDO(WKHUQHW
Additional information
● Section "Connecting Network Nodes to Ethernet (Page 91)"
● For detailed information about configuring engineering stations and installing the
operating system and PCS 7 engineering software including the required authorizations,
refer to the manual Process Control System PCS 7; PC Configuration and Authorization.
● Manual Process Control System PCS 7; SIMATIC PCS 7 BOX.
Operator Station
Operator stations are PCs on which the PCS 7 OS software is installed. The operator station
is connected to the plant bus to allow data communication with the automation system.
The architecture of the operator station is highly variable and can be flexibly adapted to a
variety of plant sizes and customer requirements. The operator station can be configured as
a single station or multiple station system with client-server architecture.
The OS server contains all the data of the operating and monitoring systems and the
interrupt and measured-value archive. It establishes the communication connection to the
automation systems. The OS servers make the process data available for the OS clients.
The OS clients are used to operate and monitor of the process mode. They access the data
of one or more OS servers.
We recommend using a terminal bus (separate from the plant bus) for data communication
between OS clients and the OS server when installing a multiple station system. The
process values archive can be stored on separate archive servers to improve performance.
To increase availability, operator stations can be set up redundantly.
26FOLHQWV
PD[LQPXOWLFOLHQWRSHUDWLRQ
$UFKLYHVHUYHU
7HUPLQDOEXV,QGXVWULDO(WKHUQHW
26VHUYHU
PD[UHGXQGDQW
3ODQWEXV,QGXVWULDO(WKHUQHW
Additional information
● Section "Connecting Network Nodes to Ethernet (Page 91)"
● Section "How Many Operator Stations are Required? (Page 67)"
● Section "Access to the PCS 7 OS via WebNavigator client (Page 125)"
● For further information on the structure of operator stations or maintenance stations and
on installing the operating system and the PCS 7 OS software including the necessary
authorizations, refer to the manual Process Control System PCS 7; PC-Configuration and
Authorization.
● Manual Process Control System PCS 7; PCS 7 BOX
● Manual Process Control System PCS 7; PCS 7 OS Web Option
BATCH station
BATCH stations are PCs on which SIMATIC BATCH is installed. The BATCH station is
connected to the terminal bus to allow data communication with the operator station. In
process mode, the BATCH station communicates with the automation system only over the
operator station.
Note
Exception: With SIMATIC BATCH versions "AS based V6.1" and "AS based 7.0", direct
communication with the automation systems is used instead of communication via the OS.
The architecture of the BATCH station is highly variable and can be flexibly adapted to a
variety of plant sizes and customer requirements. The BATCH station can be configured as a
single station or multiple station system with client-server architecture.
Typical batch process automation features one BATCH server and several BATCH clients
that process the plant project together. BATCH servers can be configured redundantly to
increase the availability.
BATCH servers and OS servers should always be operated on separate PCs. BATCH
clients and OS clients can be operated on a common PC.
Note
Exception: With SIMATIC BATCH versions "AS based V6.1" and "AS based 7.0", the
BATCH server must not be separated from the OS. In this case, the BATCH server and
operator station must run on a single computer.
26&OLHQWV %$7&+&OLHQWV
(QJLQHHULQJ
6WDWLRQ
7HUPLQDO%XV,QGXVWULDO(WKHUQHW
5HGXQGDQW 5HGXQGDQW
26VHUYHU %$7&+VHUYHU
3ODQW%XV,QGXVWULDO(WKHUQHW
$XWRPDWLRQ
V\VWHPV
Note
Exception: With SIMATIC BATCH versions "AS based V6.1" and "AS based 7.0", the
BATCH server must not be separated from the OS. In this case, the BATCH server
and operator station must run on a single computer.
Additional information
● For further information about the configuration of BATCH stations and the installation of
the operating system and SIMATIC BATCH software including the required
authorizations, refer to the manual Process Control System PCS 7; PC Configuration and
Authorization.
● Manual Process Control System PCS 7; SIMATIC BATCH
26FOLHQWV 5RXWH&RQWUROFOLHQWV
(QJLQHHULQJ
6WDWLRQ
7HUPLQDOEXV,QGXVWULDO(WKHUQHW
UHGXQGDQW
UHGXQGDQW 5RXWH&RQWURO
26VHUYHU VHUYHU
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHP
Additional information
● You can find detailed information about configuring Route Control stations and installing
the operating system and SIMATIC Route Control software including the required
authorizations in the manual Process Control System PCS 7; PC Configuration and
Authorization.
● Manual Process Control System PCS 7; SIMATIC Route Control
OpenPCS 7 station
The OpenPCS 7 station is a PC on which servers for OPC or for OLE DB are installed. The
architecture of the OpenPCS 7 station is variable and can be flexibly adapted to a variety of
plant sizes and requirements.
The OpenPCS 7 station performs the following tasks:
● It provides the PCS 7 data of the automation process via the OPC or OLE DB interface.
● It allows the client applications (OPC or OLE DB) to access the provided PCS 7 data.
The OpenPCS 7 station is connected to the terminal bus of the PCS 7 plant.
In process mode, the OpenPCS 7 station communicates with the automation systems via the
operator station (OS server).
Additional information
● Section "How to insert and configure an OpenPCS 7 station (Page 285)"
● You can find detailed information on installing the operating system and the OpenPCS 7
software, including the required license keys, in the manual titled Process Control System
PCS 7; PC Configuration and Authorization.
● Manual SIMATIC NET; Industrial Communication with PG/PC
5.3.1 Data Paths via the Terminal Bus and Plant Bus
Communication Paths
The following figure shows the communication paths and system bus using an example.
26FOLHQWV
5RXWH&RQWUROFOLHQWV %$7&+FOLHQWV
(QJLQHHULQJ
6WDWLRQ
7HUPLQDOEXV,QGXVWULDO(WKHUQHW
26VHUYHU %$7&+VHUYHU
5RXWH&RQWUROVHUYHU
3ODQWEXV,QGXVWULDO(WKHUQHW
$XWRPDWLRQV\VWHPV
Legend to figure
Topology Options
The plant bus and terminal bus can be configured as follows:
● As Industrial Ethernet (10/100 Mbps and Gigabit)
● Bus, tree, ring, star or redundant ring structures
Information concerning Industrial Ethernet properties can be found in Section "Fields of
Application and Parameters of the Network / Bus Systems (Page 79)".
Additional information
Refer to the following documentation for additional information about network architecture,
network configuration, network components and installation instructions:
● List of PCS 7-enabled modules Contains the SIMATIC NET components which are
enabled for a PCS 7 version
● Manual SIMATIC NET NCM S7 for Industrial Ethernet
● Manual SIMATIC Net PROFIBUS Networks
● Manual SIMATIC NET; Triaxial Networks
● Manual SIMATIC Net Twisted Pair and Fiber-Optic Networks
● Operating Instructions SIMATIC NET; Industrial Ethernet Switches SCALANCE X-400
● Configuration manual SIMATIC NET; Industrial Ethernet Switches SCALANCE X-400
● Operating Instructions SIMATIC NET; Industrial Ethernet Switches SCALANCE X-200
● Manual Industrial Ethernet OSM/ESM; Network Management
● Manual SIMATIC NET; AS Interface – Introduction and Basic Information
Automation systems
The following automation systems can be configured by selecting hardware and suitable
software:
Additional information
● List PCS 7 - Enabled modules
● Function manual Process Control System PCS 7; Fault-tolerant Process Control Systems
● Manual SIMATIC Programmable Controllers S7 F/FH
● Manual S7-300 Fail-safe Signal Modules
● Manual, Process Control System PCS 7; SIMATIC PCS 7 BOX.
Installation Instructions
This section is an orientation for installation instructions in the individual product
documentation.
Note
Information relating to installation in the project documentation manuals for SIMATIC
components is also valid when PCS 7 is used. There are a small number of exceptions in
terms of installation and these are dealt with in Section "Supplements to the Installation
Instructions of the Products for PCS 7 (Page 185)".
Information relating to programming and parameter assignment in the project documentation
manuals for SIMATIC components is of limited validity when PCS 7 is used. PCS 7 offers
many additional tools and functions. You should follow the procedures described in the
section “Creating the PCS 7 Configuration“ in this manual when programming and setting the
parameters of the SIMATIC components.
Note
The digital input/output modules of the ET 200S do not feature diagnostics for load voltage
failure. No QBAD is displayed on the channel drivers during load voltage supply failure.
The outputs can no longer be switched by the user program and the last valid value is
displayed at the inputs when there is no load voltage.
Overview
The following contains an introduction to the basic mechanisms of engineering with PCS 7.
In the foreground are the PCS 7 functions which enable you to configure efficiently:
● Central, plant-wide engineering (Page 188)
● Setting up the projects with the PCS 7 wizard (Page 190)
● Distributed engineering (Page 196)
● Type definition, reusability and central modifiability of engineering data (Page 205)
● Importing and reusing plant data (Page 217)
● Free assignment between hardware and software (Page 220)
● Deriving the picture hierarchy and OS areas from the PH (Page 221)
● Generating block icons (Page 223)
● Generating operator texts (Page 224)
● Basic concepts of the PCS 7 event-signaling system (Page 225)
Engineering system
The engineering system is structured on matching applications, facilitating the central,
project-wide engineering of all the components on a PCS 7 plant:
● Configuration of the hardware and field devices (HW Config, SIMATIC PDM)
● Configuration of the communications networks (HW Config)
● Configuration of continuous and sequential process sequences (CFC, SFC, PCS 7
Library)
● Configuration of discontinuous process sequences - batch processes (SIMATIC BATCH)
● Configuration of route controls (SIMATIC Route Control)
● Design of the operator control and monitoring strategies (WinCC Graphics Designer,
Faceplate Designer)
7HFKQRORJLFDO 26
IXQFWLRQEORFNV (QJLQHHULQJ
3&6(QJLQHHULQJ
,PSRUW &)& +: *UDSKLFV )DFHSODWH 6,0$7,& 6 6,0$7,&
([SRUW 6)& &RQILJ 'HVLJQHU 'HVLJQHU %$7&+ )6\VWHPV 3'0
$VVLVWDQW
/LEUDULHV
6,0$7,&0DQDJHU
8QLIRUP'DWDEDVH
Integrated database
Thanks to the engineering system's integrated database, data which has been entered once
is available throughout the system.
Additional information
● Section "PCS 7 Applications and How They Are Used (Page 249)"
6.3.1 Setting up the Projects with the PCS 7 "New Project" Wizard
In the following you will find out what benefits the PCS 7 wizard can offer you.
Result
In multiproject engineering a multiproject containing a subordinate project is created in the
SIMATIC Manager in accordance with the preview (see figure above). The preview is
adapted in line with the selected settings and shows you the structure which has been
created by the PCS 7 wizard.
There is also a master data created with the following content:
● in the plant hierarchy:
separate folders for process tag types, models and shared declarations
● in the component view:
an S7 program with the folders for source files, blocks and charts
a folder for shared declarations
Additional information
● Section "How to Create a New Multiproject with the PCS 7 Wizard (Page 258)".
6.3.2 Expanding the Projects with the PCS 7 "Expand Project" Wizard
Result
An additional SIMATIC 400 station or SIMATIC PC station is created for OS/BATCH/Route
Control/OpenPCS 7 in the selected project (in accordance with the preview).
Additional information
● Section "How to Expand a Project with Preconfigured Stations Using the PCS 7 Wizards
(Page 263)".
Introduction
We recommend that you protect your projects and libraries against unwelcome access and
log all access actions.
Note
In order to use this functionality, SIMATIC Logon needs to be installed.
Change Log
The following events can be logged via a change log if access protection is activated, for
example:
● Activating/deactivating/configuring access protection and change logs
● Opening/closing projects and libraries
● Downloading to PLCs (system data)
● Operations for downloading and copying blocks
● Changing parameters in test mode
● Activities for changing the operating states of the CPU (e.g. STOPPING the CPU)
● Resetting the CPU
You can have the change log displayed, add comments to it or export it.
Additional information
● Section "How to Provide Projects/Libraries Access Protection (Page 266)"
● Section "How to Document Changes in the Change Log (Page 679)"
● Section "How to Document Changes in the ES Log" (Page 676)"
● Manual SIMATIC Logon; SIMATIC Electronic Signature
● Online help for change log
Introduction
PCS 7 offers the following options for working with several planning engineers:
● Configuring in a Multiproject (Page 196)
● Branching and Merging Charts from a Project (Page 201)
If the project data is located on a central server, it can be exchanged between engineering
stations via the network (e.g. a project-specific block library):
● Configuration in the Network (Page 203)
Note
Please note the following:
• A project in a multiproject may only be edited by one planning engineer at any given time.
• The smallest possible unit of a project is an AS or an OS.
• Only move complete projects to a distributed engineering station.
• Only move objects (AS, OS) to a distributed engineering station in the form which is
actually necessary for editing. This means that all other objects of the multiproject are
available for editing on the central distributed engineering stations.
• An OS server must contain all the plant hierarchies of the automation systems which are
assigned to it.
CAUTION
For multiproject engineering with SIMATIC BATCH, distributed engineering on distributed
engineering stations including testing is only possible when certain conditions are met and
the additional steps are taken.
You will find additional information on this topic on the Internet
(http://support.automation.siemens.com/WW/view/en/23785345).
Operating-system requirements
Note
Please note the following:
• In the case of distributed engineering for large projects, Windows Server 2003 R2 must
be installed on the central engineering station to facilitate work on the network.
• The distributed engineering stations can use Windows XP Professional SP3 or Windows
Server 2003 R2 operating systems.
Step Description
1 Create the multiproject with a project and the master data library on the central
engineering station (using the PCS 7 "New Project" wizard).
2 Insert further projects and store the multiproject master data on the central engineering
station.
3 Move the projects, which are contained in the multiproject, and the master data library to
the distributed engineering stations.
4 Distributed Editing of the Projects
5 Moving the distributed projects back to the central engineering station
6 Executing cross-project functions on the central engineering station
Note
While cross-project functions functions are executed, all the projects involved must be
physically present in the multiproject on the central engineering station, and they may not be
being worked on.
In accordance with this procedure, the configuration process is also described in the section
"Conducting the PCS 7 Configuration".
Re. step 3 - Recommended time for moving for the purposes of distributed editing
There is no particular point in time at which the projects should be moved to the distributed
engineering stations. We recommend that you at least execute the following steps on the
central engineering station beforehand:
● Create the multiproject with the individual projects
● Create the AS and PC stations for OS, BATCH, Route Control, and OpenPCS 7
underneath the individual projects
● Create the structure of the plant hierarchy
● Compile the master data library with the objects which have to be used jointly in the
projects
In accordance with this procedure, the configuration process is also described in the section
"Conducting the PCS 7 Configuration".
Note
While cross-project functions functions are executed, all the projects involved must be
physically present in the multiproject on the central engineering station, and they may not
be being worked on.
Additional information
● Section "How to Expand the Multiproject by Adding New (Empty) Projects (Page 261)"
● Section "How to Expand a Project with Preconfigured Stations Using the PCS 7 Wizards
(Page 263)"
● Section "Introduction to Distributing the Multiproject (Multiproject Engineering)
(Page 342)"
● Section "Merging projects after distributed editing (multiproject engineering) (Page 621)"
● Section "Additional PH Functions in a Multiproject (Page 306)"
● Online Help for STEP 7
Note
This branching option can be applied independent of the multiproject engineering or in
addition to the multiproject engineering.
In the context of multiproject engineering, the master data library forms the basis for working
separately on the charts from a project.
Step Description
1 Copy a technological part of the project (individual chart, several charts) to a different project.
Result: The copy contains textual interconnections to all the sources that do not lie within the
copied sections.
2 Edit the copied section separately (add, delete, modify blocks and charts).
3 Copy the edited technological section back to the original project.
Result: The system deletes the charts with the same names from the original project. There
are textual interconnections in all the charts which await data from the deleted charts.
Thereafter, the system copies the charts from the other project.
4 Close all the textual interconnections.
Result: The interconnections are established both in the charts edited in the other project and
in the original project in which textual interconnections arose as a result of deleting charts.
Note
Always copy the charts in the component view.
If you copy a chart in the plant view, a copy of the chart in the PLC is created instead of
being replaced.
Additional information
● Section "Configuration by Several Users (Textual Interconnections) (Page 459)"
Application
If several project engineers are working from their engineering stations on one project that is
available on a central server or on a PC with a shared drive, they can also work on defined
project sections at the same time.
The following scenarios are possible in multiuser engineering:
● Edit different charts from different chart folders
● Edit different charts from the same chart folder
● Work on the same chart
Note
The central network server is an engineering station which you cannot use for
configuration. You do not require any license keys for this engineering station.
Note
Note the following:
Only one planning engineer can access the data from an OS at any given time.
WinCC Explorer prevents multiple project engineers from logging on to the same OS.
● If the values monitored in test mode are no longer updated as a result of offline changes
(e.g., because a block was deleted), the system displays "#" characters on a red
background at the corresponding connections instead of the values.
● If one project engineer has started a compilation process and another project engineer
changes a parameter in test mode, this parameter change is rejected with the message
that the data is currently being used by another application (access conflict).
Additional information
● Online help on CFC
Principle
Plant engineering gives rise to plant parts, functions or program sections which only differ
from one another in a few respects.
In the interests of working efficiently, create basic elements (units, program sections, etc.)
which can be reused repeatedly and which only have to be supplied with the current
parameters.
Block type
Block types are precompiled parts of programs used to process recurring functions which
can be inserted in CFC charts. The block type creates a block instance to which you can
then assign parameters and can interconnect. The block type determines the characteristics
for all the instances of this type.
You can adapt block types to your project requirements, e.g. adapt operator texts or make
parameters visible/hidden. To ensure that there is only one version of a block type used
throughout a project, store all the block types centrally in the master data library (Page 214)
and adapt them prior to instantiation.
NOTICE
Store the block types in the master data library. This means that you can be sure that only
one version of a particular block type (with a type name) is used throughout the entire
project.
Different versions of blocks in different programs can lead to conflicts if the programs are to
be controlled and monitored by one OS. This happens if variables of the same block type
(identical type name) possess the same structure.
Central Modifiability
If the interface description and/or system attributes of a block type are changed, and it is
imported into the CFC data storage system, it overwrites (updates) an existing block type of
the same name. All the block instances of this type are also changed to correspond to the
new block type.
The central type modifiability relates to FBs and FCs.
Before the central change is executed, a warning appears referring to the consequences and
containing information about the old and new block types, for example name, date of the last
interface change.
Changing the type centrally can have an unwelcome impact upon block instances.
Interconnections and parameter-assignments can be lost. In this case you have to adapt the
corresponding block instances yourself.
Central type modifications are logged, and this log is displayed automatically after updates.
You can also call up this log at a later point in time via the menu command Options > Logs:
Block Types.... If block instances need to be adjusted, the log help to minimize the workload
and the risk of error.
Note
Refer to the online helps for the CFC, SFC and IEA to find out which type changes the
instances and replicas support.
Additional information
● Section "How to Adapt Blocks to Specific Projects (Page 323)"
● Manual Process Control System PCS 7 Library
● Manual Process Control System PCS 7; Programming Instructions for Blocks
● Online help on CFC
SFC type
SFC types allow sequential controllers to be defined as reusable templates. An SFC type is
a sequential controller which can be configured in the SFC editor and be inserted into a CFC
chart. An executable SFC instance is created. SFC instances appear in the CFC chart as
blocks with an interface corresponding to the block instances.
To run an SFC instance, both the SFC type and the SFC instance must be compiled and
downloaded into the automation system.
To ensure that there is only one version of an SFC type used throughout a project, store all
the SFC types centrally in the master data library (Page 214) and adapt them prior to
instantiation.
Characteristics (control strategies, setpoints, parameter, note texts, position texts, etc.),
which can be used in the sequencers, can be defined for SFC types. A control strategy is
specified by operation or by a higher-level controller (e.g. SIMATIC BATCH).
Note
You cannot assign SFC types to a hierarchy folder in the plant view since they themselves
are not relevant to execution.
Central Modifiability
Modifications to the interface of the SFC type are transferred to the SFC instances.
The following changes take effect automatically in SFC instances following the compilation
and downloading of the AS.
● Change to the topology (step/transition sequence, changed jump target)
● Change to the step configuration
● Change to the transition configuration
The SFC visualization is only updated following the compilation and downloading of the OS.
Additional information
● Section "How to Create an SFC Type (Page 555)"
● Manual SFC for S7; Sequential Function Chart
Central Modifiability
When a process tag type is modified, the process tags existing in the project are
automatically synchronized. Synchronization can be initiated again with a menu command if
actions have been undertaken which result in inconsistencies between the process tag type
and the process tags (because, for example, not all of the process tags of a project were
accessible during the automatic synchronization process).
Using the "Create/Change Process Tag Type" wizard, the following inconsistencies can be
harmonized between the process tag type and the process tags:
● Parameter, signal connection points and messages which are not present on the process
tag type are deleted from the process tags. The corresponding attributes are reset.
● Parameter, signal connection points and messages which have been newly defined on
the process tag type are added to the process tags. The corresponding attributes are set.
● Categories which have been changed on the process tag type are corrected on the
process tags.
● Inconsistencies between the process tag type and the process tag which cannot be
harmonized automatically are displayed in the log.
Note
Changes to the chart of the process tag type are not taken into account when the process
tags are synchronized. In this case, you must delete the relevant charts beforehand and
then carry out a new import for the changed process tag type using the Import/Export
Assistant.
You cannot change the names of the blocks for an existing process tag type or for
process tags derived from this. Otherwise, import/export is no longer possible.
Note
Ensure that all the projects are available in the multiproject in order to facilitate
harmonization of the project tags.
Additional information
● Section "Introduction into Creating Process Tags from Process Tag Types (Multiproject)
(Page 517)".
Model
Models are used to define more complex functions than process tag types (through to plant
sections), and store these as reusable templates. A model consists of hierarchy folders with
CFC/SFC charts, pictures, reports and additional documents. A number of replicas can be
copied in a single transaction from a model with the aid of the Import/Export Assistant on the
basis of an import file. The replicas are then adapted in line with the requisite, specific
automation task.
Note
You can only create models in a multiproject.
Store the models centrally in the master data library (Page 214). Adapt the model before
creating replicas.
Creating Replicas
The blocks for importing/exporting parameter descriptions, interconnection descriptions and
messages are prepared in the charts for a model. After the model is linked to an import file,
the model is imported with the Import/Export Assistant. The generated replicas are assigned
the parameters, interconnections, and messages of the model.
Each line in an import file creates a replica in the target project. The replicas retain the
assignment to the model.
Central Modifiability
You can use the "Create/Change Model" wizard to make changes to models.
If you modify models or the I/O points of a model that already have replicas, a message is
displayed indicating this since the import data no longer matches the model data.
Using the "Create/Change Model" wizard, check the consistency of the model with the
assigned import file as well as the replicas for changes in the IEA identification.
Note
The block names may no longer be modified for an existing model or for a replica of a model.
Otherwise, import/export is no longer possible.
Additional information
● Section "How to Create a Model (Page 570)"
● Online help for the IEA
In addition, the following objects can be included in the master data library.
● Objects from the PCS 7 Advanced Process Library
● Objects from the PCS 7 Basic Library
● Objects from the PCS 7 Library
● Objects from the S7 standard library
● Objects from libraries of suppliers
● User-created objects
Additional information
● Section "How to Create a Master Data Library (Page 315)".
Note
You can find which other module versions are released for PCS 7 in the document entitled
PCS 7 - Released Modules, which can be accessed with the menu command Start >
SIMATIC > Documentation > English.
Create a new catalog profile in HW Config and use drag-and-drop to move the required
components from the "PCS 7_Vx.y" hardware catalog to the new catalog profile. You can
assign any name to the catalog profile.
Additional information
● Section "Defining a Project-Specific Catalog Profile (Page 353)".
Import/Export Interfaces
All the essential applications of the PCS 7 engineering system have import/export interfaces.
The use of these import/export interfaces has the following advantages:
● Plant-planning data can be harmonized with control-system engineering data. This is how
control system engineering and plant engineering can be independently edited at the
same time.
● Data from the engineering system can be exported as a template, be effectively
duplicated and adapted in an external program (such as MS Excel) and then be imported
back into the engineering system. This allows you to optimize the configuration of
recurring or similar plant information.
Symbol Table
PCS 7 can compile the symbolic names into the requisite absolute addresses provided the
symbolic names have been assigned to the absolute addresses. This happens in PCS 7
during hardware configuration or when a hardware configuration is imported.
Example
For example, you can assign the symbolic name MOTOR_751_ON to the operand A 4.0 in
the symbol table and use MOTOR_751_ON as an address in a source statement.
Additional information
● Section "How to Assign Symbols to Input and Output Addresses (Page 366)".
6.8 Deriving the Picture Hierarchy and OS Areas from the Plant Hierarchy
Requirement
Note
If you use the "OS Compilation" function, the structure of the plant hierarchy is only copied
into the Picture Tree Manager if the option "Derive picture hierarchy from the plant hierarchy"
is activated in the general PH settings in the SIMATIC Manager.
Deactivate this option once you have adapted the picture hierarchy in the Picture Tree
Manager and if you do not wish to overwrite the picture hierarchy the next time you compile
the OS.
When the OS is compiled, the OS areas are transferred to the Picture Tree Manager for
further editing. The hierarchy levels are always displayed in the Picture Tree Manager,
starting with the hierarchy level that has been defined as the OS area.
Recommendation: Allow for the required OS areas in the structuring of the PH and specify
the area identifiers.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Online help Help on PH, IEA and PO
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
Additional information
● Section "How to Import/Export I/Os and Messages (Page 330)"
● Configuration manual Process Control System PCS 7; Operator Station
Event-Signaling Classes
Distinctions are made between the following classes of signals:
Event-signaling Description
classes
Process control I&C system messages are generated when SIMATIC PCS 7 detects and
signals signals errors in its own components (AS, OS, etc.). Such errors range from
failure of a component to a wire-break signal for a connected I/O module.
Process control signals are generated by the driver blocks in PCS 7 and do
not have to be configured.
Process signals Process signals indicate process events that take place in the automated
process, such as limit value violations and event signals.
• Process signals are predefined for the blocks and therefore do not need
to be configured. However, if necessary, message texts and a message
priority can be changed in the CFC block properties, centrally in the list of
process objects or by means of import and export.
• Events signals are a subgroup of process signals. They signal process
variables which serve to evaluate a technological variable, such as an
elapsed-time counter.
Operating messages Operating messages are generated when an operator controls process
variables, for example, changes the operating mode of a controller.
Operating messages are generated automatically when you use the
faceplates which are provided by the PCS 7 Library.
If you configure faceplates according to the manual entitled PCS 7
Programming Instructions for Blocks, you can also use PCS 7 operating
messages for your own blocks.
Origin of a Message
Messages can originate in different locations within the control system depending on the
configuration. The time stamp of the message is influenced by where it originates.
The illustration below shows an example with a distributed I/O, ET 200M.
6LQJOHXVHUV\VWHP26
2ULJLQRIDPHVVDJH
LQWKHRSHUDWRUVWDWLRQ
3ODQWEXV,QGXVWULDO(WKHUQHW
6,0$7,&6 2ULJLQRIDPHVVDJH
LQWKHDXWRPDWLRQV\VWHP
352),%86'3
(70
2ULJLQRIDPHVVDJH
LQ,0
"Loop-in-alarm" function
Process and control technology messages from technological blocks which are visualized on
the OS feature the "loop-in-alarm" function. You can use this function to select the faceplate
for this process tag straight from the signal list.
Additional information
The message-configuration procedure is described in detail together with the step-by-step
instructions in the configuration manual Process Control System PCS 7; Operator Station.
The section below provides a brief summary of the individual features of the PCS 7 for
configuring a convenient message system.
Additional information
● Section "How to Configure Messages in SFC (Page 554)"
● Configuration Manual Process Control System PCS 7; Operator Station
Step What?
1 • Inserting the "STATEREP" block into a CFC chart
• Interconnecting the control signal for a process status (e.g. starting up a part of the plant) to a state input on
the "STATEREP" block (state1 to state32)
A status input represents a status for showing and hiding messages.
2 Creating shared declarations
3 Assigning blocks in the process object view for groups.
4 Assigning messages from blocks in groups, which you wish to hide, to the status in the process object view.
Additional information
● Section "How to Configure Showing and Hiding Messages Automatically (Page 499)"
● Configuration manual Process Control System PCS 7; Operator Station
Acknowledgement concept
PCS 7 uses a central acknowledgement concept. If a message is acknowledged on an OS,
this acknowledgement is transferred to the reporting block in the AS. From there it is
forwarded centrally as an acknowledged message to all the operator stations which are
being supplied.
Note
Configure the same message method for all automation systems of a multiproject (standard
message procedure or acknowledgment-triggered reporting).
Do not mix both methods within a multiproject. Otherwise the plant operator cannot
recognize the message procedure that generated the message. This could lead to false
conclusions being drawn.
Additional information
● Section "How to Activate Acknowledgment-triggered Reporting (QTM)" (Page 418)"
Introduction
Events frequently have to be read in with high-precision timing during initial value acquisition
following the failure of part of plant with a subsequent flurry of messages: Even if there is a
large number of messages, the message which led to the failure of the unit (initial value)
must be clearly identifiable.
Additional information
● Section "How to configure the hardware for the high-precision time stamps (Page 417)"
● Function Manual Process Control System PCS 7; High-Precision Time Stamping
Additional information
● You can find more detailed information on the function and installation of signal modules
in the manual Process Control System PCS 7; WinCC Basic Process Control
● You can find more detailed information on configuring the acoustic signaling device in the
configuration manual Process Control System PCS 7 Operator Station
SIMATIC Manager
The SIMATIC Manager is the central starting point for all engineering tasks. The PCS 7
project is managed, archived and documented there. All the applications of the engineering
system are accessible from the SIMATIC Manager. If there is a connection between ES, OS,
BATCH, Route Control and AS, the configuration data can be transferred to the target
systems from the SIMATIC Manager and then tested online.
Note
One major feature of these views is that the objects they contain exist only once.
View Purpose
Component view In the component view, you organize the projects of the multiproject, create
(Page 238) hardware components and start the hardware configuration of the automation
systems, bus components, process I/O, and PC stations.
Plant View The plant view function is used to arrange and depict the plant according to
(Page 241) technological aspects. Arrange the automation, operator control and monitoring
functions hierarchically in the plant view. The structures for the PCS 7 OS in
process mode are derived from this plant hierarchy (for example, OS areas,
picture hierarchy).
Process object view The process object view provides a universal view of the process tags. It shows
(Page 243) the plant hierarchy combined with a table view of all the aspects of the process
tag/process object (for example, parameters, signals, messages, etc.).
In the process object view, all the data of the basic control throughout a project
can be displayed in a process control-oriented view. The multiproject collects
the data contained in all of the projects.
0XOWLSURMHFW
)LUVW3URMHFWLQWKH0XOWLSURMHFWRSHQ
6,0$7,&VWDWLRQ
&38
6SURJUDP
6RXUFHVRIWKH6SURJUDP
%ORFNV)%V)&V2%V'%V
&KDUWV&)&FKDUWV6)&FKDUWV6)&W\SHV
,QWHUIDFHVEHWZHHQWKU&3DQGWKHSODQWEXV
6KDUHGGHFODUDWLRQV
6,0$7,&3&VWDWLRQVIRU(626RU%$7&+
0XOWLSURMHFWPDVWHUGDWDOLEUDU\
6SURJUDP
6RXUFHVRIWKH6SURJUDP
%ORFNV)%V)&V2%V'%V
&KDUWV&)&FKDUWV6)&FKDUWV6)&W\SHV
6KDUHGGHFODUDWLRQV
(QXPHUDWLRQV
8QLWVRIPHDVXUH
(TXLSPHQWSURSHUWLHV
2WKHUSURMHFWLQWHKPXOWLSURMHFWFORVHG
0XOWLSURMHFW
)LUVWSURMHFWLQWKHPXOWLSURMHFWRSHQ
6KDUHGGHFODUDWLRQV
3ODQW
)LUVWSDUWRIWKHSODQW
7HFKQRORJLFDOIXQFWLRQZLWKW&)&6)&FKDUWV
0XOWLSURMHFWPDVWHUGDWDOLEUDU\
6KDUHGGHFODUDWLRQV
0RGHOV
3URFHVVWDJW\SHV
7HPSODWHV
2WKHUSURMHFWLQWHKPXOWLSURMHFWFORVHG
Object-oriented working
In SIMATIC Manager the different object types are linked directly to the application required
to process it. The associated application is also started once an object opens.
component view
The component view is used to manage the multiproject and the projects it contains. In
addition, it can be used to carry out the following functions:
● Creating the hardware components
● Setting up the hardware configuration
● Setting up and testing the AS configuration
● Setting up the OS configuration
● Setting up the BATCH configuration
● Starting the Route Control configuration
● Running cross-project functions
Multiproject engineering
Use the component view to carry out the following functions in the multiproject:
● Split up the multiproject technologically for distributed editing
● Merge the projects back into the multiproject after distributed editing
● Run the cross-project functions after the projects have been synchronized
Hardware Configuration
Working in the component view, you configure the hardware of the automation systems, the
bus components, and the process I/O. In the component view, you create the following
objects below the projects:
● SIMATIC S7-400 stations (AS)
● SIMATIC PC stations for the engineering station (ES), operator stations (OS), BATCH
stations (BATCH), Route Control stations and OpenPCS 7 station
Double-click on "Hardware" for the selected station to access the HW Config application.
Use HW Config to add additional hardware components (for example, CP, ET 200M) or
software applications (server or client) to the stations and set the hardware component
parameters.
Note
After you have completed hardware configuration, you then work mainly in the plant view
and in the process object view.
AS Configuration
The objects in the component view are identified as components according to their
importance (for example, S7 program, station, OS, PLC/AS (CPU), chart folder).
In the component view, you organize the block types and SFC types by copying them from
the master data library to the chart folders of the AS in which they are used. Only then are
they available in the catalog for CFC/SFC configuration.
OS Configuration
Starting the component view, you begin configuration of the operator station for process
mode. The WinCC Explorer starts after selecting the OS with the context menu command
Open object.
Refer to the configuration manual Process Control System PCS 7; Operator Station for more
information.
BATCH Configuration
Start the batch control configuration from the component view. Open the BATCH
configuration dialog with the menu command Options > SIMATIC BATCH.
Refer to the configuration manual Process Control System PCS 7; SIMATIC BATCH for
more information.
Offline or Online?
The component view can be switched between the following states:
Component View > Offline This view of the project structure visualizes the project data on the engineering
station. The offline view is set as the default when you create a new project. In the
offline view, the complete data on the engineering station is displayed for the S7
program (offline).
Component View > Online This view of the project structure visualizes the project data on the target system
(CPU). In the online view, the data on the target system are displayed for the S7
program (online). You use this view for access to the target system.
Plant hierarchy
In the plant view, you structure the project according to technological aspects. In the process
you hierarchically organize automation, operator control and monitoring functions into the
hierarchy levels plant, unit or function. Name the relevant hierarchy folder according to its
technological significance. Arrange the following in the hierarchy folder:
● CFC and SFC charts for the AS
● Pictures and reports for the OS
● Additional documents such as descriptions of units, process tag sheets, planning
documents etc. (from MS Word, MS Excel, etc.)
The resulting project structure is the plant hierarchy.
Additional Aspects
Please observe the following aspects of the plant view:
● The technological objects (plants, units, functions, ...) can be handled as a single entity
(for example, when copied).
● The technological objects can be used to work independent of a fixed hardware
assignment.
● The OS areas and the image hierarchy for the OS are derived from the plant hierarchy.
● The plant hierarchy is the basis for the plant-oriented identification of process objects.
The hierarchy path forms the plant designation (higher level designation HID). It can used
to specify the folders that contribute to the naming scheme.
● You insert and position the process pictures in the plant view. The block icons of the
blocks used in the process picture can be generated automatically from the plant
hierarchy.
AS-OS assignment
An OS must be assigned an AS in the plant view of each hierarchy folder. This AS-OS
assignment has the following consequences in the component view:
● All CFC and SFC charts inserted in the plant view are stored in the chart folder of the
assigned AS.
● All pictures and reports inserted in the plant view are stored in the folder of the assigned
OS.
Structure
On the left, the process object view displays the plant hierarchy (tree). On the right, you see
a table of the underlying objects along with their attributes (contents window).
The tree displays the same objects as in the plant view. In addition, the process object view
of the tree also shows the CFCs, SFCs, OS pictures, OS reports and additional documents.
Tab Purpose
General Here, you see all the underlying process objects (process tags, CFCs, SFCs,
OS pictures, OS reports, or additional documents) for the plant section currently
selected in the tree along with general information on the objects.
Blocks Here, the block properties of the blocks in all subordinate CFC charts are
display for the plant section currently selected in the tree. SFC instances are
also identified as blocks here.
Parameter Here, you see all the I/O points of the process tags and CFCs displayed in the
"General" tab that were selected explicitly for editing in the process object view
(S7_edit = para).
Signals Here, you see all the I/O points of the process tags and CFCs displayed in the
"General" tab that were selected explicitly for editing in the process object view
(S7_edit = signal).
Messages Here, you see the corresponding messages for all the process tags, CFCs and
SFCs displayed in the "General" tab.
Picture objects Here, you see all the picture links that exist in WinCC for the process tags and
CFCs displayed in the "General" tab.
Archive tags Here, all process tags, CFC charts, SFC charts and the existing interconnected
WinCC archive tags listed in the "General" tab are displayed along with their
attributes.
The attribute that are relevant for PCS 7 (subset of all attributes defined in the
tag logging) are displayed.
Hierarchy folder Here, the hierarchy folders of the PH are display (one line for each hierarchy
folder) for the plant section currently selected in the tree.
Equipment Here, the equipment properties are displayed for the projected selected in the
properties tree.
These equipment properties are instances of equipment properties types that
have been configured in the shared declarations (one line for each equipment
property). The attributes are entered in the instance when a type is changed.
Shared Here, you can edit the attributes of the types, enumerations, units of measure
Declarations and equipment properties contained in the multiproject.
Object Purpose
Hierarchy folder Expand the plant hierarchy by adding objects such as plant, unit, and function
within a project.
CFC/SFC Create empty CFCs and SFCs that can then be further edited with the
appropriate editors.
Additional Create empty or import available additional documents, for example, MS Excel
document or MS Word if the relevant application is installed.
Picture Create empty pictures that can then be further edited with the Graphics
Designer.
Report Create empty reports that can then be further edited with the page layout editor.
Equipment Create equipment properties of the units and change their properties.
properties
Process tag (from Insert process tags from the catalog of process tag types in the master data
library) library. You can drag the process tag type to a hierarchy folder in the process
object view or in the plant view. This creates a process tag in this hierarchy
folder.
Access protection Activate access protection to restrict the access to the selected project by
certain users.
Offline or Online?
The process object view can be switched between the following states:
Process object view > Offline This view visualizes the project data on the engineering station. The offline view is
set as the default when you create a new project. In the offline view, the complete
data on the engineering station is displayed for the S7 program (offline).
Process object view > Online In test mode (online), additional columns are displayed in the "General",
"Parameters" and "Signals" tabs, with which you can test and commission the
process tags and CFC charts online on the CPU (target system).
Additional information
● Section "Editing Mass Data in the Process Object View (Page 580)"
● Online help for PH, IEA and PO
Application Purpose
HW Config Configuring the hardware
Hardware configuration displays the hardware structure of a station or a PC
station. With HW Config, you specify the racks and their slot assignments
according to the actual structure of the station; you configure and assign
parameters to the modules, and configure the distributed I/Os.
NetPro Configuration of networks and connections
Using NetPro, you can configure, make parameter assignments, and document
the network configuration for your plant extremely simply and clearly.
CFC Configuring continuous processes
CFC (Continuous Function Chart) is a graphic editor that can be used in
conjunction with the STEP 7 software package. It is used to create the entire
software structure of the CPU from ready-made blocks. When working with the
editor, you place blocks on function charts, assign parameters to them, and
interconnect them.
SFC Configuring sequential control systems
SFC (Sequential Function Chart) is a tool for creating a sequential control
system. With this application, you can create and commission technological
sequential control systems.
SCL Programming blocks
SCL (Structured Control Language) is high-level programming language for
programmable controllers. Along with high language elements it also contains
typical elements of the AS as a language element:
• Inputs
• Outputs
• Timers
• Memory bit
• Block calls
SCL supplements and expands the STEP 7 programming software with its
programming languages LAD, FBD and STL.
Graphics Designer Editing of process pictures
(WinCC) In the Graphics Designer, you edit the mimic diagrams that the operator
displays and uses for process control on the operator station. PCS 7 provides a
function for use when creating process pictures that automatically inserts all
block icons (clear, graphical representations of measuring points) in the process
picture.
You can also insert other graphic objects and define the dynamic attributes of
the objects. For example, you can visualize the current state of a valve so that
the operator immediately sees whether the valve is "open" or "closed".
Application Purpose
Tag Logging Archiving process values
(WinCC) Tag logging is used to archive process values and includes the following
functions:
• Creation of archives
• Assignment of the process values to the archives
Alarm Logging Archiving messages and alarms
(WinCC) Alarm Logging is used for the following functions in the processing of messages
and alarms:
• Receiving messages from processes
• Preparing and displaying messages in process mode
• Acknowledgments by the operator
• Archiving
Report Designer Design of the layout for printouts of process values or messages.
(WinCC) The Report Designer provides functions for creating and outputting reports. You
can adapt the supplied standard layouts individually. The Report Designer
provides the required editors.
OpenPCS 7 Connection to the works management level
New PCS 7 data important for the works and enterprise management level is
constantly being produced in a production process. OPC/OLE DB provides you
with access to this data. This package allows you to use the data from the
higher control levels and create your own statistical information and evaluations.
SIMATIC BATCH Automation of batch processes (discontinuous processes)
With the SIMATIC BATCH software package, you can configure process cells
with recipe-oriented control strategies with exacting requirements. In this way
complex tasks with alternating process sequences can be edited.
SIMATIC Route Automating of route controls
Control Using the SIMATIC Route Control software package, you control and monitor
material transports in process mode (route control).
SIMATIC PDM SIMATIC PDM is a software package for configuration, parameter assignment,
commissioning, and maintenance of devices (for example, transducers) and for
configuring networks.
SIMATIC PDM allows simple monitoring of process values, alarms, and status
information of the device.
Faceplate Designer Creation of faceplates
Using the Faceplate Designer, you create PCS 7-compliant templates for
faceplates.
Version Cross Comparing project versions
Manager You use the Version Cross Manager to perform the following comparisons:
• Compare versions of projects and libraries with graphic display of
differences
• Compare versions of two S7 programs for differences relating to the
programming
• Compare versions of two CFC/SFC charts
• Export project data in XML format
Version Trail Create versions
You use Version Trail to create versions of multiprojects, projects and libraries.
Application Purpose
S7 H Systems This supports you in the configuration of an S7-400H/S7-400FH.
CFC charts created by the user have the functions necessary for error detection
added to them automatically.
S7 F Systems This supports you when configuring an S7-400F/S7-400FH.
CFC charts (F charts with F blocks) created by the user already include the
functions required for error detection and the reaction to errors.
Import/Export Tool for fast engineering of mass data (for example, importing process tag types
Assistant and models).
PCS 7 Advanced The PCS 7 libraries include blocks and functions for use in PCS 7 plants.
Process Library
Hardware Catalog The hardware catalog "PCS7_Vx.y" contains all approved devices and modules
(the latest version in each case).
DOCPRO Using DOCPRO, you can create and manage plant documentation.
SFC Visualization SFC visualization of the Operator System allows sequential control systems
configured with the SFC editor to be represented and operated in the same way
as on the engineering system. This does not involve any extra configuration
effort.
Introduction
The basic activities described below are arranged in a practical order that you can follow to
achieve a rational workflow during configuration.
Depending on the requirements of your project, some of the steps in configuration are
mandatory and others are optional. From the table below, you can see which configuration
steps are necessary and which are options.
Described Procedures
The creation of the configuration as described in the following sections is structured
according to this procedure. The PCS 7 project must be created by multiproject engineering
as a prerequisite to handling all topics. The PCS 7 project is subdivided into several projects,
subjected to distributed editing, and then finally merged back into the multiproject for cross-
project functions.
Note
With the procedure described here, you have full system support. You can, of course, follow
a different procedure, however you then lose some or all the support provided by PCS 7.
Additional information
● Manual Process Control System PCS 7; PC Configuration and Authorization
What? Where?
Making the Default Settings for the PCS 7 Project (Page 257) SIMATIC Manager
Creating a New Multiproject with the PCS 7 Wizard (Page 258) PCS 7 "New Project" Wizard
(in the SIMATIC Manager)
Expanding a Multiproject by Adding New (Empty) Projects SIMATIC Manager
(Page 261)
Expanding a Project by Adding Preconfigured Stations PCS 7 "Expand Project" Wizard
(Page 263) (in the SIMATIC Manager)
Expanding a Project by Adding Additional Objects (Page 265) SIMATIC Manager
Configuring Access Protection for Projects/Libraries (Page 266) SIMATIC Manager
(with SIMATIC Logon)
Procedure
1. Open SIMATIC Manager with the menu command Start > SIMATIC > SIMATIC Manager.
2. In SIMATIC Manager, select the menu command Options > Settings…
.The "Settings" dialog box opens.
3. Set the location for storing projects and libraries in the "General" tab.
Specify the path for storing your projects/libraries if you do not want to use the default
path but rather, for example, a specially created project drive.
4. Ensure that backups (images) are loaded.
5. In the "Language" tab, set the language and the mnemonics with which you want to work.
6. In the "Date and Time" tab, set the desired format and specify if the module should show
the local time of the programming device / PC (for UTC system time -> convert to local
time).
7. In the "Wizards" tab, check if the "PCS 7" option is set.
This setting is required to be able to later start the PCS 7 "New Project" and "Expand
Project" wizards.
8. In the "Message Numbers" tab leave the default setting "Always prompt for setting" or
select " Always assign unique message numbers CPU-wide".
9. In the "Archive" tab, you can select the archiving program you want to use (for example,
PKZip) and the paths for archiving/retrieval.
10.Click "OK".
You enter all other settings the first time you create the PCS 7 project with the PCS 7 "New
SIMATIC Manager Project" wizard. You can change these settings later in the "Settings"
dialog box.
Note
You will have to restart the SIMATIC Manager for some of the settings, for example, when
changing the language.
Additional information
● Online help for the "Settings" dialog box
Procedure
1. Select the menu command File > "New Project" Wizard in the SIMATIC Manager.
2. You can check the structure of the multiproject using the "Preview" button.
3. Click "Continue".
4. Select the desired CPU (bundle) and the number of communication modules (CP 443-5)
as required.
5. Click "Continue".
Result
The multiproject is created and contains one project as shown in the preview. The relevant
objects are created in the component view and in the plant view. There is also a master data
created with the following content:
● in the component view:
an S7 program with the folders for source files, blocks and charts
a folder for shared declarations
● in the plant view:
separate folders for process tag types, models and shared declarations
Procedure
1. Select the multiproject in the SIMATIC Manager.
2. Select the menu command File > Multiproject > Create in Multiproject...
3. Enter a name for the new project and specify a storage location.
4. Click "OK".
Result
An empty project is created in the multiproject, which you can later configure (for example,
using HW Config, Technological Hierarchy) or add preconfigured stations to using the PCS 7
"Expand Project" wizard.
Additional information
● When working in multiproject engineering, in the section "Configuring in a Multiproject
(Page 196)" read the information relating to the rules for distributing the automation
systems, operator stations and SIMATIC PC stations in the individual projects of the
multiproject.
● Section "How to Expand a Project with Preconfigured Stations Using the PCS 7 Wizards
(Page 263)".
Introduction
If you want to continue using an existing project (single project unchanged or modified), you
can integrate it in your multiproject.
If the project already belongs to another multiproject, a message is displayed. If you want to
include such a project in the multiproject, it is removed from the other multiproject.
Procedure
1. Open the multiproject.
2. Select the menu command File > Multiproject > Insert in Multiproject... in the SIMATIC
Manager.
3. Select the project you want to insert.
4. Click "OK".
Note
If this project originates from an earlier PCS 7 version, keep to the procedure described in
the manuals Process Control System PCS 7; SW Update ....
Introduction
You can remove projects which are no longer required from the multiproject.
Procedure
1. Open the multiproject.
2. Select the project you want to remove from the multiproject.
3. Select the menu command File > Multiproject > Remove from Multiproject in the SIMATIC
Manager.
Result
The project is no longer a part of the multiproject. It is, however, not deleted; only the
assignment to the multiproject is canceled. You can delete the project with the menu
command File > Delete > User Projects.
8.3.7 How to Expand a Project with Preconfigured Stations Using the PCS 7 Wizards
Inserting an AS
1. Select the project to be expanded in the SIMATIC Manager.
2. Select the menu command Insert > Preconfigured Station….
3. Select "CPU" from the drop-down list and select the required CPU.
4. Select the required bundle from the "Bundle" list.
You can find the components of the bundle in the "Description" column.
5. Select the number of communication modules (distributed I/O) you want to set up from
the "Number of communication modules (CP 443-5)" drop-down list.
6. Click "Continue".
7. If you also want to insert a PC station, select the desired station type (OS objects).
8. Click "Continue".
9. You are shown the project name and storage location in the next dialog.
10.Click "Finish".
Result
The appropriate automation system is created, including the hardware configuration for all
components of the selected bundle.
Inserting a PC Station
1. Select the project to be expanded in the SIMATIC Manager.
2. Select the menu command Insert > Preconfigured Station….
3. Select "CPU" from the drop-down list and select the entry "(Do not install hardware)".
4. Click "Continue".
5. Select from the following under "OS objects":
– PCS 7 OS
– SIMATIC BATCH
– SIMATIC Route Control
– OpenPCS 7
6. Then select from the following:
– Single station system
– Multiple station system
– Multiple station system redundant
7. Click "Next".
The project name and storage location will be displayed for you in the next dialog.
8. Click "Finish".
Result
The appropriate SIMATIC PC stations including the hardware configuration are created.
Introduction
The PCS 7 wizards create the basic configuration, which you can expand with additional
objects based on the requirements of your plant.
Procedure
The procedure described here does not depend on the selected view. The objects you can
select to be included depend on the currently selected object and the selected view.
1. Select the folder/object in the SIMATIC Manager.
2. Select the Insert folder.
All of the objects that can be inserted below the folder are available in the Insert menu.
The available selection depends on whether you selected the object in the Process
Object View, Plant View or in the Component View.
3. Select the object you require with the menu command and specify the object name.
Additional information
● Online help for the SIMATIC Manager
Introduction
As of PCS 7 V7.0, you have the option to assign a project password to provide access
protection for projects and libraries.
Once you have configured the access protection, you can record online actions in a change
log.
Requirements
● SIMATIC Logon is installed.
● The "Project administrator" and "Project editor" roles in SIMATIC Logon are automatically
created during the PCS 7 installation.
● You are assigned the "Project administrator" role in SIMATIC Logon.
● You are logged on as the project administrator or project editor.
Rules
● The user currently logged on (project administrator, project editor) is displayed in the
status bar of the SIMATIC Manager.
● The project format is changed the first time access protection is activated. You receive
notice that the modified project can no longer be edited with older PCS 7 versions.
● By using the function Remove Access Protection and Change Log you lose the
information about the users who have access to the project or library and all the change
logs.
Additional information
● Section "Protecting Projects/Libraries with Access Protection (Page 193)"
● Section "How to Document Changes in the ES Log" (Page 676)"
● Online help for the SIMATIC Manager
● Manual SIMATIC Logon; SIMATIC Electronic Signature
Introduction
The following describes how you can open protected projects/libraries. This generally
depends on whether or not the SIMATIC Logon Service is installed.
Note
If you open a multiproject that contains protected projects/libraries without first logging on to
the SIMATIC Logon Service, the protected projects/libraries are grayed out and cannot be
edited.
To view which projects/libraries these are (incl. path), position the mouse cursor over the
gray project or library (tooltip), or access the detail view.
If you attempt to open a protected project/library and are not registered as the project
administrator or project editor, or do not know the password, the project/library will not open.
Procedure
If... Then
• SIMATIC Logon Service is installed 1. Select the menu command
• Are registered as a project administrator File > Open in the SIMATIC Manager.
or project editor 2. Select the desired project/multiproject/
• You have logged on with the SIMATIC library.
Logon Service 3. Click "OK".
• The project/library is not open
• SIMATIC Logon Service is installed 1. Select the menu command
• Are registered as a project administrator File > Open in the SIMATIC Manager.
or project editor 2. Select the desired project/multiproject/
• The project/library is not open library.
3. Click "OK".
4. Enter your user name and password in the "SIMATIC Logon Service"
dialog box.
5. Click "OK".
• SIMATIC Logon Service is not installed, 1. Select the menu command
• The project/library is not open File > Open in the SIMATIC Manager.
2. Select the desired project/multiproject/
library.
3. Click "OK".
3. Enter the
project password in the "Enter Project Password" dialog box.
4. Click "OK".
Result
The protected project/library opens and can be edited.
Introduction
To visualize the process on the operator station you use faceplates, which show the plant
operator the measured values, operating limits, units, and operator texts of the blocks, for
example.
PCS 7 allows you to export texts that are stored in one language in a project, have them
translated, reimport them, and have them displayed in the translated language.
Note
If operator texts or display texts have been changed compared to the PCS 7 version in
blocks for the system which is being updated and you wish to use the new PCS 7 V7.1
faceplates, you should back up the "old" operator texts.
Requirement
The desired language is already installed in the project.
(Select the menu command Options > Language for Display Devicesin the SIMATIC
Manager in order to have the list of available languages displayed).
Rules
● The new texts must not be longer than the default texts. If longer texts can not be
avoided, check whether the text is still displayed correctly.
● Export:
The export is carried out for all the blocks and symbol tables that lie under the selected
object. One export file is created for every text type. This contains one column each for
the source and the target language.
The texts in the source language may not be changed.
● Import:
The import is carried out for all the blocks and symbol tables that lie under the selected
object. During importing the contents of the columns for the target language (right
column) is imported into the selected object. Only those texts are imported for which an
agreement with an existing text is found in the column for the source language.
Exporting
1. Open the project to be updated in the SIMATIC Manager.
2. Select the folder of the master data library (or if it does not exist, the project folder) in the
component view.
3. Select the menu command Options > Manage Multilingual Texts > Export.
The "Export User Texts" dialog box opens.
4. Make the following settings:
– In the "Text tables" group select the storage location and the format of the export file
(possible formats: *.xls and *.csv).
– In the "Language" group select the target language and source language in
accordance with your display language.
– Select the text types to be exported in the "Text types" group.
– If appropriate, activate the "Enter points of use of texts in the export file" check box.
5. Click "OK".
An export file is created for each text type in the target directory.
If you manage several project-specific languages, repeat Steps 3 and 4. Note that you must
then set different export file names or target directories.
Importing
1. Open the project to be updated in the SIMATIC Manager.
2. Select the folder of the master data library (or if it does not exist, the project folder) in the
component view.
3. Select the menu command Options > Manage Multilingual Texts > Import.
The "Import User Texts" dialog box opens.
4. In the "Source" group, select the storage location and the format of the import file
(possible formats: *.xls and *.csv).
5. Click "OK".
The texts are imported and a log file of the import is output.
Additional information
● Online help for the SIMATIC Manager
● Manual SIMATIC; Programming with STEP 7
● Manual Process Control System PCS 7; Operator Station
Note
If you require distributed editing of the projects of the multiproject, read the information in the
section "Configuring in a Multiproject (Page 196)" on the distribution of automation systems,
operator stations and SIMATIC PC stations to the individual projects of the multiproject.
8.4.2 How to Insert the SIMATIC 400 Stations in the Projects of the Multiproject
Introduction
Once you have created the multiproject with the PCS 7 wizard, as default, one automation
system is already inserted. You can insert additional automation systems as follows:
● With the PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations Using the PCS 7 Wizards (Page 263)".
● Manually (described below)
Procedure
1. Select the project where you want to insert a SIMATIC station in the component view of
the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC 400 Station.
A new station is inserted ("SIMATIC 400 Station(1)"; you can adapt the name to your
requirements).
3. Follow the same procedure if you want to install additional SIMATIC stations.
Additional information
● Section "How to Create a SIMATIC 400 Station (Page 359)"
● Online help for the SIMATIC Manager
Introduction
This section describes how to start the basic configuration of the automation systems. We
recommend the following work sequence for multiprojects:
● The automation systems will be created in the individual projects and the communication
processors for network connection will be configured on the central engineering station.
This is described below.
● The complete hardware configuration with attached I/O will be completed on the
distributed engineering stations after the projects are distributed for editing. The complete
hardware configuration is described in the section "Configuring the Hardware".
Note
If you have created the SIMATIC 400 station with PCS 7 "Expand Project" wizard, all
hardware components of the respective bundle are already available.
Procedure
Follow the steps outlined below to start the basic configuration of the automation systems:
1. Select the required SIMATIC 400 station from the component view and open the HW
Config by double-clicking the "Hardware" object in the detail window.
The hardware configuration of the automation system is opened.
2. If the hardware catalog is not visible, select the menu command View > Catalog.
3. In the SIMATIC 400 > Rack-400 hardware catalog, select the required rack and insert it
by dragging with the mouse.
Make sure that the arrangement selected here matches the arrangement of the physical
hardware.
4. In the "SIMATIC 400 > PS-400" hardware catalog, select the required power supply and
add it by dragging with the mouse.
5. In the SIMATIC 400 > CPU-400 hardware catalog, select the required CPU and insert it
by dragging with the mouse.
6. Click "OK" to confirm the "Properties - PROFIBUS Interface" dialog box that opens.
7. Follow the same procedure if you want to install additional components.
8. Select the menu command Station > Save and Compile in HW Config.
Additional information
● Section "Configuring the Hardware"
8.4.4 How to Insert CPs in the SIMATIC Stations and Assign Them to Networks
Introduction
The communications processors (CP) inserted in the SIMATIC 400 stations must be
configured for network attachment in HW Config and assigned to the communications
network. In multiproject engineering, it is advisable to carry out this configuration work on the
central engineering station for all projects. This ensures, for example, that node addresses
are unique on the bus.
Note
If you have created the SIMATIC 400 station with PCS 7 "Expand Project" wizard, all
hardware components of the respective bundle, including the CPs, are already available.
This means that you require the procedure described here to add other CPs later on.
Procedure
1. Select the required SIMATIC 400 station from the component view and open the HW
Config by double-clicking the "Hardware" object in the detail view.
The hardware configuration of the automation system is opened.
2. If the hardware catalog is not visible, select the menu command View > Catalog.
3. In the "SIMATIC 400 > CP-400" hardware catalog, select the CP (CP 443-1) you require
for the network being used and insert it with drag-and-drop.
Once you have inserted the CP, the "Properties - Interface" dialog box is opened.
4. Set the required CP address on the bus in the "Properties - Interface" dialog box.
5. Select the subnet from the "Subnet" group:
– If you have not yet set up a subnet, click "New" and define a new network.
– If you have already set up a subnet, select the required network in the "Subnet" group.
6. Click "OK".
The "Properties" dialog box closes.
7. Select Station > Save and Compile from the menu.
Additional information
● Section "Configuring the Hardware"
Introduction
The engineering station is configured in the SIMATIC Manager. The following steps are
carried out during this process:
● Insertion of a SIMATIC PC station
● Configuration of the hardware in HW Config
● Configuration of the communication connection in NetPro
The communication connections set up for the PC station can then be checked with the
diagnostics functions of the Station Configuration Editor.
Procedure
1. Select the project into which you want to insert the engineering station in the component
view of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC PC Station.
A new SIMATIC PC station is inserted in the selected project.
3. Select the SIMATIC PC station, select the menu command Edit > Object Properties...,
and enter the required name.
4. Select the SIMATIC station from the component view and open the HW Config by double-
clicking the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station is opened.
5. If the hardware catalog is not visible, select the menu command View > Catalog.
6. Under "SIMATIC PC Station > HMI ..." in the hardware catalog, select the required
"WinCC application" and drag it into the configuration table:
7. In the "SIMATIC PC Station > CP Industrial Ethernet" hardware catalog, select the
communications processor installed in the SIMATIC PC station and drag it to the PC
station.
If you use a standard network card, select the "IE General" processor.
The "Properties - Ethernet Interface" dialog box opens.
8. Set the required address on the bus for the CP:
– If the network adapter is connected to the terminal bus, activate the "IP protocol is
being used" check box.
– If the network adapter is connected to the plant bus, activate the "Set MAC address /
Use ISO protocol" check box. If a maintenance station is being operated, activate the
"IP protocol is being used" check box.
– For a network card connected to the plant bus via BCE, enter the
name in the "General" tab and set the
"Interval" to "30" in the "Send keep alive for connections" group of the "Options" tab.
Additional information
● Section "Setting up PC Stations (Page 255)"
● Manual Process Control System PCS 7; PC Configuration and Authorization
Introduction
Each OS server, redundant OS server, and OS client of a PCS 7 OS is managed as a
SIMATIC PC station in the SIMATIC Manager. The SIMATIC PC station always contains the
following objects:
● A WinCC application
● A communications processor that is not inserted by the wizard
● An OS
If you created the multiproject with the PCS 7 wizards, you will already have inserted a
PCS 7 OS if you selected the appropriate option. You can insert additional operator stations
as follows:
● With PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations Using the PCS 7 Wizard (Page 263)".
● Manually (described below)
Procedure
1. In the component view of SIMATIC Manager, select the project where you want to add
the operator station.
2. Select the menu command Insert > Station > SIMATIC PC Station.
A new SIMATIC PC station is inserted in the selected project.
3. Select the SIMATIC PC station, select the menu command Edit > Object Properties and
enter the required name.
4. Select the SIMATIC station from the component view and open the HW Config by double-
clicking the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station is opened.
5. If the hardware catalog is not visible, select the menu command View > Catalog.
6. Under "SIMATIC PC Station > HMI" in the hardware catalog, select the required WinCC
application and drag it into the configuration table:
– SPOSA application (for OpenPCS 7 station)
– WinCC application (for OS server or OS single station system)
– WinCC application (stby) (for redundant OS server)
– WinCC application client (for OS client)
– WinCC appl. client ref (for reference OS client)
– WinCC application ref (for reference OS single station system)
– WinCC CAS appl. (for central archive server)
– WinCC CAS appl. (stby) (for redundant central archive server)
7. In the "SIMATIC PC Station > CP Industrial Ethernet" hardware catalog, select the
communications processor installed in the SIMATIC PC station and drag it to the PC
station.
If you use a standard network card, select the "IE General" processor.
The "Properties - Ethernet Interface" dialog box opens.
8. Set the required address on the bus for the CP:
– If the network adapter is connected to the terminal bus, activate the "IP protocol is
being used" check box.
– If the network adapter is connected to the plant bus, activate the "Set MAC address /
Use ISO protocol" check box. If a maintenance station is used, activate the "IP
protocol is being used" check box.
– For a network adapter connected to the plant bus via BCE, enter the name in the
"General" tab and set the "Interval" to "30" in the "Send keep alive for connections"
group of the "Options" tab.
9. Select the subnet from the "Subnet" group:
– If you have not yet set up a subnet, click "New" and define a new network.
– If you have already set up a subnet, select the required network in the "Subnet" group.
10.Click "OK".
The "Properties" dialog box closes.
11.Select the menu command Station> Save and Compile.
12.Follow the same procedure if you want to install additional SIMATIC stations.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Manual Process Control System PCS 7; PC Configuration and Authorization
Introduction
The BATCH server and each BATCH client of a BATCH station are managed and SIMATIC
PC stations in the SIMATIC Manager. This always contains the following object:
● A BATCH application (standard, standby, client)
If you created the multiproject with the PCS 7 wizard, you will already have inserted a
BATCH station if you selected the appropriate option. You can insert additional SIMATIC
BATCH stations as follows:
● With PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations Using the PCS 7 Wizard (Page 263)".
● Manually (described below)
WARNING
Configuring applications (WinCC, SIMATIC BATCH, etc.) on separate "SIMATIC PC
station" objects and subsequently merging them to create one PC station by assigning
the same computer name to the "SIMATIC PC station" objects is not permitted!
Requirement
The relevant SIMATIC BATCH add-on package is installed and licensed on the engineering
station.
Procedure
1. Select the project into which you want to insert the BATCH station in the component view
of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC PC Station.
A new SIMATIC PC station is inserted in the selected project.
3. Set the computer name of the SIMATIC PC station:
– to do this, select the PC station.
– Select the menu command Edit > Object Properties.
– Enter the computer name in the "Computer name" group or activate the "Computer
name identical to PC station name" check box.
4. Select the SIMATIC station from the component view and open the HW Config by double-
clicking the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station is opened.
5. If the hardware catalog is not visible, select the menu command View > Catalog.
6. Under "SIMATIC PC Station > BATCH" in the hardware catalog, select the required
BATCH application and drag it into the configuration table:
– BATCH application (for BATCH server)
– BATCH application (stby) (for redundant BATCH server)
– BATCH application client (for BATCH client)
7. In the "SIMATIC PC Station > CP Industrial Ethernet" hardware catalog, select the
communications processor installed in the SIMATIC PC station and drag it to the PC
station.
If you use a standard network card, select the "IE General" processor.
The "Properties - Ethernet Interface" dialog box opens.
8. Set the required address on the bus for the CP:
– If the network adapter is connected to the terminal bus, activate the "IP protocol is
being used" check box.
9. Select the subnet from the "Subnet" group:
– If you have not yet set up a subnet, click "New" and define a new network.
– If you have already set up a subnet, select the required network in the "Subnet" group.
10.Click "OK".
The "Properties" dialog box closes.
11.Select Station > Save and Compile from the menu.
12.Follow the same procedure if you want to install additional BATCH stations.
Additional information
● Manual Process Control System PCS 7; SIMATIC BATCH
● Manual Process Control System PCS 7; PC Configuration and Authorization
Introduction
The Route Control server and every Route Control client of a Route Control station is
handled as a SIMATIC PC station in the SIMATIC Manager. This always contains the
following object:
● A Route Control application (standard, standby, client)
If you created the multiproject with the PCS 7 wizard, you will already have inserted a Route
Control station if you selected the appropriate option. You can insert additional SIMATIC
Route Control stations as follows:
● With PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations Using the PCS 7 Wizard (Page 263)".
● Manually (described below)
Requirement
The SIMATIC Route Control add-on package is installed and licensed on the engineering
station.
Procedure
1. Select the project into which you want to insert the Route Control station in the
component view of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC PC Station.
A new SIMATIC PC station is inserted in the selected project.
3. Set the computer name of the SIMATIC PC station:
– to do this, select the PC station.
– Select the menu command Edit > Object Properties.
– Enter the computer name in the "Computer name" group or activate the "Computer
name identical to PC station name" check box.
4. Select the SIMATIC station from the component view and open the HW Config by double-
clicking the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station is opened.
5. If the hardware catalog is not visible, select the menu command View > Catalog.
6. Under "SIMATIC PC Station > Route Control" in the hardware catalog, select the required
Route Control application and drag it into the configuration table:
– RC application (for Route Control server)
– RC application (stby) (for redundant Route Control server)
– RC application Client (for Route Control client)
7. In the "SIMATIC PC Station > CP Industrial Ethernet" hardware catalog, select the
communications processor installed in the SIMATIC PC station and drag it to the PC
station.
If you use a standard network card, select the "IE General" processor.
The "Properties - Ethernet Interface" dialog box opens.
8. Set the required address on the bus for the CP:
– If the network adapter is connected to the terminal bus, activate the "IP protocol is
being used" check box.
– If the network adapter is connected to the plant bus, activate the "Set MAC address /
Use ISO protocol" check box. If a maintenance station is used, activate the "IP
protocol is being used" check box.
– For a network adapter connected to the plant bus via BCE, enter the name in the
"General" tab and set the "Interval" to "30" in the "Send keep alive for connections"
group of the "Options" tab.
9. Select the subnet from the "Subnet" group:
– If you have not yet set up a subnet, click "New" and define a new network.
– If you have already set up a subnet, select the required network in the "Subnet" group.
10.Click "OK".
The "Properties" dialog box closes.
11.Select Station > Save and Compile from the menu.
12.Follow the same procedure if you want to install additional Route Control stations.
Additional information
● Manual Process Control System PCS 7; PC Configuration and Authorization
● Manual Process Control System PCS 7; SIMATIC Route Control
Introduction
The OpenPCS 7 station is configured as a SIMATIC PC station in the SIMATIC Manager. It
always contains the "SPOSA Application" object.
The following steps are carried out during this process:
● Insertion of a SIMATIC PC station
● Configuration of the hardware in HW Config
The communication connections set up for the PC station can then be checked with the
diagnostics functions of the Station Configuration Editor.
If you created the multiproject with the PCS 7 wizard, you will already have inserted an
OpenPCS 7 station provided that you selected the appropriate option. You can also insert an
OpenPCS 7 station as follows:
● With PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations Using the PCS 7 Wizard (Page 263)".
● Manually (described below)
Procedure
1. Select the project into which you want to insert the OpenPCS 7 station in the component
view of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC PC Station.
A new SIMATIC PC station is inserted in the selected project.
3. Select the SIMATIC PC station, select the menu command Edit > Object Properties and
enter the required name.
4. Select the SIMATIC station from the component view and open the HW Config by double-
clicking the "Configuration" object in the detail view.
The hardware configuration of the SIMATIC PC station is opened.
5. If the hardware catalog is not visible, select the menu command View > Catalog.
6. Under "SIMATIC PC Station > HMI ..." in the hardware catalog, select the required
SPOSA application and drag it into the configuration table:
7. Select Station > Save and Compile from the menu.
Additional information
● Section "How to configure OpenPCS 7 stations for accessing PCS 7 data (Page 617)"
● Manual Process Control System PCS 7; PC Configuration and Authorization
Introduction
The project-specific network settings for the communication modules (Ethernet) are
downloaded directly to the PC station by the engineering station.
Requirements
● The following is installed on each PC station:
– Operating system
– Specific software for the PC station (e.g., PCS 7 Engineering, OS server)
● All PC stations to be downloaded are linked to the engineering station by means of at
least one network.
● The operating system network is administrated.
● The network addresses of the PC stations are configured.
● The protocol for the communication on the terminal bus is set to TCP/IP.
● The following settings are made on each PC station:
– The communication card for communication between the PC station and the terminal
bus is selected.
– The network addresses for the system bus are set.
– The access point of the PC station is set to "S7ONLINE: = PC internal (local)".
● The PCS 7 project is created.
Procedure
Note
Please note the following:
• Perform the following steps for the engineering station first before configuring and
downloading the other PC stations.
• When configuring the local PC station, the "Use configured target computer" check box
must be deactivated (see Step 6).
Note
If the selected PC station does not appear in the list, this suggests network problems or a
faulty configuration in the project.
Please ensure that the "Use configured target computer" check box is activated (as
opposed to the local PC station).
7. Click "Configure".
The "Configure: Selected Station>" dialog box opens.
8. In the "Configure: Target Computer" dialog box, click "OK".
The "Information" dialog box opens.
9. Click "OK".
The configuration data are transferred to the PC station.
The dialog box message line signals completion of the "Configuration" step.
To activate the network connections, you must then download the network settings to this
PC station.
10.Click "Close".
11.Select the menu command PLC > Download for the computer selected in step 2.
The "Download Target System in Current Project" dialog box opens.
Note
The configured network address of the Ethernet interface in the PC station must match
the preset address in the target system.
12.When the dialog box tells you that you are overwriting the configuration data, respond as
follows:
– During initial commissioning, click "Yes".
– If the PC station is in process mode, you can only click "Yes" when a communication
interruption is permissible.
The "Stop Target Module" dialog box opens.
13.In the "Stop Target Module" dialog box, click "OK" to confirm.
The "Download" dialog box opens.
14.Click "OK" to confirm.
The download process is executed.
Nach dem Übernehmen der Projektierung ist die PC-Station betriebsbereit.
15.Repeat steps 2 through 14 for all of the PC stations.
NOTICE
You must not deactivate the TCP/IP protocol or the ISO protocol during operation. These
protocols are mandatory for the configured operating mode!
If a bus within a system must be switched to a different protocol (for example, from TCP
protocol to ISO protocol), you must temporarily set a mixed protocol (TCP and ISO) on the
engineering station. You then download the configuration data to the AS and the operator
control and monitoring systems.
Additional information
● Manual SIMATIC NET; Commissioning PC Stations - Manual and Getting Started
Note to Reader
The following description is based on the following points:
● The plant hierarchy is created on the central engineering station and, if necessary, filled
with additional documents. This is described below.
● The CFC/SFC charts or OS pictures/OS reports created on the distributed engineering
stations are then assigned to the hierarchy folders.
What? Where?
Creating the Plant Hierarchy (Page 294) SIMATIC Manager
Inserting Additional Hierarchy Folders into the Plant Hierarchy Plant hierarchy
(Page 297)
Specifying the AS/Os Assignment (Page 300) Hierarchy folder in the plant
hierarchy
Assignment of Objects of the Plant Hierarchy (Page 302) Component view
Checking the Consistency in the Plant Hierarchy (Page 304) SIMATIC Manager
Introduction
When you create a multiproject with the PCS 7 wizard, defaults or specified parameter
settings made in the individual steps of the PCS 7 wizard were used (for example, the
number of hierarchy levels, assignment to AS). You can change these settings later or adapt
them for hierarchy folders to be added later.
Note
To ensure consistent naming throughout the entire project, make sure that you select a
suitable naming scheme for the hierarchy folders in the plant view during configuration.
The number of characters in the names of the hierarchy folders must not exceed the number
of characters specified for the HID.
Setting Description
Number of hierarchy Specifies the maximum number of possible hierarchy levels, maximum
levels eight levels. At each level, you can insert as many hierarchy folders as
required.
Basing the Picture With this option, the OS picture hierarchy is derived completely from the
hierarchy on the plant configured data of the plant hierarchy. This picture hierarchy is transferred
hierarchy to the Picture Tree Manager when you later compile the OS.
Derive diagnostics With this option, the diagnostics screens are generated in the plant
screens from the plant hierarchy for the maintenance station.
hierarchy You can also specify if the names of the diagnostic screens to be
generated should derived from the name of the hierarchy folders or from
the comments of the hardware components.
You can only select this option when the option "Derive picture hierarchy
from the plant hierarchy" is also set.
Migrating diagnostics After you have selected an OS for the diagnostics area, properties will be
settings automatically modified at this OS (and at all other OS of the multiproject),
including the expansion of the startup list. These settings must be
migrated in the course of an upgrade to higher PCS 7 versions.
Level Settings
Max. number of Specifies the maximum number of characters permitted for the name of a
characters hierarchy folder at this level (1 to 24)
Included in HID You can select the levels from which hierarchy folder names (if selected
for inclusion) will be included in the HID. You can use folders that are not
selected for inclusion in the designation to create additional "drawers" (for
example, for supplementary documents, such as plant descriptions,
process tag sheets, etc.).
If a level is included in the naming scheme of the HID, this means that the
names are entered in the origin of the message (OS) and in the tag names
on the OS (measuring point).
Note: Remember that when assigning names and compiling the OS, the
tag name must not be longer than 128 characters. The name consists of
the following elements:
• Name of the folder in the hierarchy path (including server prefix)
• Chart name
• Block name
• Separator
• I/O name
With separator With this option, a separator can be included in the HID after the name of
hierarchy folders of this level.
Separators are used in the textual representation of the hierarchy path to
differentiate between the names of the hierarchy folders. The "\" character
is used as the separator.
OS area With this, you can decide which hierarchy level should count as the OS
area. The default is the 1st level.
The definition of an OS area is necessary for area-specific messages in
process mode.
Procedure
1. Open the plant hierarchy in the SIMATIC Manager with the menu command View > Plant
View.
2. Select a hierarchy folder and select the menu command Options > Plant Hierarchy >
Customize....
If you have selected several projects in a multiproject, you will first see a dialog box with a
list of the selected projects. You can make the setting shown in the following dialog box
only after selecting a project.
Note
The settings function as a template and are passed on to all other projects that were
included in the selection. Projects that were not selected retain their settings.
If you select the multiproject explicitly, all the projects it contains will adopt the settings
you made in the template project.
3. Click "OK".
The "Plant Hierarchy - Settings" dialog box opens.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Online help for the "Plant Hierarchy - Settings" dialog
Note
The characters [ ' ] [ . ] [ % ] [ \ ] [ * ] [ ? ] [ : ] [spaces] within a name are converted to the
substitute character $ when you compile the OS.
The ES separator [ \ ] is converted to the [ / ] character.
If, for example, you assign the name "TICA:1" for a CFC chart (this becomes "TICA$1" on
the OS) and the name "TICA*1" for another CFC chart, (also becomes "TICA$1"), you will
receive an error message when you transfer the second chart because the chart name
already exists.
● The maximum length of a tag name is 128 characters. Remember, however, that many of
the editing windows on the OS can not display 128 characters in their entirety. You
should therefore restrict the length of the HID.
● Remember that special characters associated with certain national languages take up
two characters, thus reducing the maximum name length accordingly.
● Remember that the length of the texts transferred depends on the maximum text length of
a target block in the OS (Tag Logging, for example, event 50 characters; origin 32
characters). When compiling the "OS" texts up to a maximum length of 255 characters
are transferred.
Remedy:
Increase the maximum character length of the user text field or select a shorter HID.
● The message texts of the transfer messages are made up of the hierarchy path, chart
name, and the block name (if you decided to include the names in the HID).
Introduction
Use the PCS 7 wizard to create a maximum of 8 hierarchy levels without additional nesting
of hierarchy folders. You can expand this structure that was created by the PCS 7 wizard
with additional hierarchy folders and/or technological objects.
Hierarchy folder
The hierarchy folder is used to structure the plant in a hierarchy. It can contain additional
hierarchy folders and objects:
● CFC charts
● SFC charts
● OS pictures
● OS reports
● Equipment Properties
● Additional documents (for example: Excel, Word)
The higher-level designation (HID) of an object results from the names of the hierarchy
folders (path) and the object name (if you decided to include the names in the HID).
Procedure
1. Open the plant hierarchy in the SIMATIC Manager with the menu command View > Plant
View.
2. Select a hierarchy folder where you want to insert the additional hierarchy folder.
3. Select the menu command Insert > Technology Objects > Hierarchy Folder.
4. Enter the technological name of the hierarchy folder.
Introduction
The technological objects CFC charts, SFC charts, OS images, OS reports, and equipment
properties can be inserted in the plant hierarchy in both the plant view and process object
view. The methods for inserting objects are practically identical. Below you will find a
description of how to insert technological objects into the plant view.
Inserting an Object
You can insert the following objects: CFC/SFC chart, OS picture/OS report, equipment
properties.
1. Open the plant view in the SIMATIC Manager with the menu command View > Plant
View.
2. Select a hierarchy folder where you want to insert the object.
3. Select the menu command Insert > Technology Objects > "<Required Object>".
Note
You can also create a new additional document by selecting the type in the "Registered
Applications" box, entering the name and confirming with "OK".
The additional document is created in the PH. Double-click the document to open and
edit it.
3. Click "Import".
4. Select the required additional document.
5. Click "OK".
The selection is entered.
Additional information
● Section "Relationships between the Views (Page 246)"
● Section "Cross-view Functions and How to Use Them (Page 247)"
Introduction
You must assign an OS and an AS for the hierarchy folder in the plant hierarchy. The AS/OS
assignment produces the following results in the component view:
● All CFC and SFC charts inserted in the plant hierarchy are stored in the chart folder of the
assigned AS.
● All OS images and OS reports inserted in the plant hierarchy are stored in the folder of
the assigned OS.
Procedure
1. Select the hierarchy folder for which you want to make the AS-OS assignment in the plant
view.
2. Select the menu command Edit > Object Properties and change to the "AS-OS
Assignment" tab.
3. From the "Assigned AS (Chart Folder)" drop-down list, select the S7 program that you
want to assign to the selected hierarchy folder.
4. If the lower-level objects have a different assignment and you want to have the same
assignment for all lower-level objects, check the "Pass on selected assignment to Pass
on all the lower-level objects" check box.
Note
The "Pass on selected assignment to all lower-level objects" check box is only active if
the lower-level objects have another assignment or no assignment.
5. From the "Assigned OS" list, select the operator station you want to assign to the
selected hierarchy folder.
6. If the lower-level objects have a different assignment and you want to have the same
assignment for all lower-level objects, check the "Pass on selected assignment to Pass
on all the lower-level objects" check box.
Note
If the "area-oriented" compilation mode is activated, the OS assignment can only be
changed for PH folders of the OS area level.
7. Click "OK".
Result
The AS/OS assignment is selected, and the lower-level objects are passed on or not passed
on according to your setting.
Note
If you have distributed the projects so that there is only one OS or one AS in a project, you
do not need to make an AS/OS assignment.
Additional information
● Online help for PH, IEA and PO
● Online help for the "AS-OS Assignment" tab
Introduction
You can also assign objects from the component view, for example, a CFC chart or SFC
chart, to the plant hierarchy later. This is always the case when, for example, charts are
inserted directly in the component view and you then create a plant hierarchy later. If you
create charts in the plant view or in the object view they are automatically assigned to the
plant hierarchy.
Requirement
The hierarchy folder has the same AS or OS assignment as the assigned object. If the
destination hierarchy folder has a different AS-OS assignment, the assigned object is also
moved to this AS/OS in the component view.
Note
If you have selected the setting "Base picture hierarchy on the plant hierarchy" in the settings
of the plant hierarchy, only one picture of the same OS is permitted per hierarchy folder.
Procedure
1. Select the required object in the component view.
2. Hold down the <Shift> key (move) and drag the object to the required hierarchy folder of
the PH.
If you have created OS pictures/OS reports directly in the OS and want to assign these
object to the plant hierarchy later, proceed as follows:
1. Select the OS in the component view of your project.
2. Select the menu command Options > OS > Import WinCC Objects.
3. Select the required object in the component view.
4. Use Drag&Drop while simultaneously holding down the <Shift> key to drag the object
from the component view to the required hierarchy folder of the PH.
NOTICE
The process variables referenced in the C scripts in WinCC must be defined in the
"#define section".
Introduction
You can use PCS 7 to determine whether the configured data are consistent with the
settings made in the project or multiproject.
Consistency Check
The following properties are evaluated in the consistency check:
● Non-unique names of S7 programs, CFC charts and SFC charts
● Brackets in the names of hierarchy folders
● Length of the hierarchy folder names
● Number of hierarchy folder levels
● Area assignment to an OS for uniqueness and completeness
The following is checked when the check box "Derive picture hierarchy from the plant
hierarchy" is activated:
● Number of OS pictures per hierarchy folder
● Unique picture names for OS
The results are displayed in the individual tabs.
Additional information concerning the test results in the tabs is available by clicking "Help".
Note
If a multiproject is selected, the following checks are also made:
• Check for unique names of S7 programs. Check if the names of CFC charts and SFC
charts are unique in the entire multiproject.
• Check if only one object for each type (S7 program, OS) is available in the master data
library.
• Check for uniformity in the OS assignment when area folders have the same name in the
multiproject
• Check for uniformity in the OS compiling mode ("AS oriented" or "Area oriented")
throughout all projects in the multiproject
• Check for consistent PH settings in the multiproject (levels of the OS area, derivation of
the picture hierarchy and diagnostics, HID relevance)
If a project or hierarchy folder is selected, then the tests are related exclusively to that project
/ hierarchy folder.
Procedure
1. Select the multiproject or a project in the plant hierarchy.
2. Select the menu command Options > Plant Hierarchy > Check Consistency.
The "Consistency Check - Log" dialog box opens, with the errors.
3. Clear the errors and run the consistency check again.
Display Log
On completion of the check, a message is displayed or if an error occurred, the error log is
output.
You can also display the log later without running the check again with the menu command
Options > Plant Hierarchy > Display Log. A log is displayed when the last consistency check
has shown that the configured data are consistent with the settings that have been made.
Note
Violations of the naming scheme can occur, for example, when you change settings at a
later date or copy/move folders to different levels. The system tolerates these violations to
avoid unnecessary error messages while you are working.
Additional information
For Additional information about the log, refer to the online help.
Function Description
Creating a Multiproject In the SIMATIC Manager, the PCS 7 wizard automatically creates a
multiproject.
• The project is created with the content selected in the PCS 7 wizard
(PH, AS, OS).
• Two hierarchy folders are created in the master data library in the PH
that serve as storage for process tag types, models and shared
declarations.
Cross-project • The consistency check allows multiple assignment of names to process
Consistency Checks tags to be recognized early. This prevents these errors from canceling
the data transfer procedure to the OS (during the compile OS function ).
• You can check the uniqueness of the S7 programs in all of the
multiproject projects. The uniqueness of the S7 programs is a
requirement for the proper functioning of the Import/Export Wizard and
the diagnostic function.
• Within the master data library, a check is made to ensure that there is
only one S7 program and only one OS.
Passing on PH Settings The PH settings for the projects in a multiproject can be changed by using
to other Projects of a the menu command Options > Plant Hierarchy > Customize...:
Multiproject • Settings for an individual project
If you select an individual project in a multiproject, you can define PH
settings which are exclusive to this project.
• Identical settings for several/all projects
If you select several projects in a multiproject or the multiproject itself to
display the settings dialog box, then an additional dialog box is
displayed in advance. Use this dialog box to select a project template
and then enter the TM settings in the next dialog box. The settings of
this template are passed on to all projects included in the selection.
Create/update block The menu command Options > Plant Hierarchy > Create/update block
icons in all projects of a icons... is used to take into account all the pictures whose block icons are
multiproject based on the PH, starting with the selected object (multiproject, project,
hierarchy folder).
In a multiproject, the path in the PH is the key for searching in other
projects. PH structures with the same name are searched for in all projects
of the multiproject. The CFC charts found there are included in the editing
process.
Function Description
Synchronizing When working in a multiproject, in some situations it is necessary to create
Hierarchy Folders in redundant folders in parts of the plant hierarchy in all or individual projects
the Multiproject of a multiproject.
There are two applications:
• In SIMATIC BATCH, the folder identified as "Process cell" is required in
the first hierarchy level in all projects.
• By using the same names in the plant hierarchy in the individual
projects of the multiproject, AS and OS parts that belong together are
detected when the functions "Create/Update Block Icons" and
"Create/Update Diagnostic Screens" are executed.
The plant hierarchy synchronization function in the multiproject allows you
to save multiple configurations. This also protects the project from
(accidental) changes that would result in differing names. You can start the
synchronization function in either the process object view or the plant view
by selecting the menu command Options > Plant Hierarchy > Synchronize
in the Multiproject....
Renaming or Modifying When attributes of a hierarchy folder are renamed or modified, a check is
Attributes of the carried out to determine if the hierarchy folders derived from it exist in the
Hierarchy Folder other projects of the multiproject. If this is the case, they are renames and
the attributes are set accordingly.
Create/update Use menu command Options > Plant Hierarchy > Create/update block
diagnostics screens icons to create or update diagnostics screens for a project or for the
projects of a multiproject. Requirements: A diagnostics structure must have
already been set up in the project.
Additional information
● Online help for PH, IEA and PO
Introduction
You can assign attributes to the hierarchy folder in the PH in accordance with the ISA-88.01
standard. This "ISA-88 type definition" is required, for example, for BATCH plants and
applications at works management level (MES).
You can use the object properties to change the hierarchy folder object type from "Neutral"
to "Process cell," "Unit" or "Equipment module".
Procedure
1. Select the object whose settings you want to change in the PH.
2. Select the menu command Edit > Object Properties
3. Open the "ISA-88 Type Definition" tab.
4. Change the object type for example from "<Neutral>" to "Process cell."
5. Click "OK".
Result
When you create further folders, the folders in the two levels directly below are assigned the
attributes for "Unit" and "Equipment module" according to their hierarchical level.
Neutral Folders
The three-level hierarchy can be extended by adding neutral folders to improve the
structuring of the project, for example, to divide units into groups. The neutral folders can be
created at any level. The total number of possible levels (ISA-88 hierarchy levels, levels with
neutral folders) is limited to eight.
Neutral folders can, for example, be inserted above the "Unit" level. This level can then be
used, for example, as the area level. A further level could, for example, be inserted below the
"Equipment Module" level. This level can then serve as a control module level.
Additional information
● Online help for PH, IEA and PO
Advantages of a Library
During configuration it is advantageous if all objects (blocks, charts, source files, process tag
types, models, SFC types) used in the project are grouped in their own library. This means,
for example, that you can be sure that only one version of a particular block type is used
throughout the entire project. Different versions in different programs can lead to conflicts if
the programs are to be controlled and monitored on one OS.
Reason: block types of the same name in different programs, must have the same variable
structures, since there is only one variable structure for a block type on the OS.
Note
Remember to update your master data library or SFC types if you have added blocks from
the PCS 7 library and its version was later changed.
The function "Update block types" is available for synchronizing the block types and SFC
types. You can find information about this in the section "How to Update the Block and SFC
Types (Page 321)".
Note
The supplied libraries are always copied during PCS 7 installation. If you have edited
supplied libraries, the libraries you have changed will be overwritten by the originals if you
install again.
What? Where?
Creating the Master Data Library (Page 315) SIMATIC Manager
Copying Objects to the Master Data Library SIMATIC Manager
(Page 319)
How to Adapt Blocks to Specific Projects SIMATIC Manager (component view)
(Page 323)
Creating Process Tag Types (Page 518) SIMATIC Manager (plant view)
Creating models (Page 570) SIMATIC Manager (plant view)
Testing the Library Objects (Page 341) CFC or SFC Editors
Documenting the Library Objects (Page 341) In the relevant editors
Hiding Libraries (Page 317) SIMATIC Manager
● Shared declarations
You can define the following elements as shared declarations, which you can use in a
variety of applications:
– Enumerations
– Units
– Equipment Properties
● Models
A model consists of additional hierarchy folders that contain the following elements:
– CFC/SFC charts
– OS pictures
– OS reports
– Additional documents
Any number of replicas can be created from these elements by using the Import Export
Assistant.
● Templates
The PCS 7 libraries (PCS 7 Advanced Process Library, Basic Library, PCS 7 Library) also
contain templates for various technical functions.
Additional information
● Online help for PH, IEA and PO
Introduction
If you have created your multiproject with the PCS 7 wizard, it already contains a master
data library. SIMATIC Manager can be used in the following manner to define a master data
library if you still do not have one in your multiproject:
● Create a new library and define it as the master data library.
● Define an existing library as the master data library.
Note
Each multiproject can only contain one master data library. The master data library can
only contain one S7 program.
Procedure
Requirements: no library is defined as a master data library in the multiproject. If, however, a
master data library is defined, the definition of an existing master data library must be
reversed. This can be achieved by carrying out the second step under "Procedure".
To create a new library as the master data library in your multiproject, proceed as follows:
1. Select the menu command File > New in the SIMATIC Manager
2. Open the "Libraries" tab and enter a name for the library (preferably the multiproject
name).
3. Enter the storage location (path), if necessary.
The library is created and opened.
4. Select the library in the multiproject in the component view and then the menu command
File > Multiproject > Define as Master Data Library.
The library is defined as a master data library.
5. Select the library and then the menu command Insert > Program > S7 Program.
An S7 program is created, including block and source folders.
6. Add a chart folder below the S7 program with the menu command Insert > S7 Software >
Chart Folder.
Result
Your multiproject has a new master data library. The models or process tag types folders do
not need to be set up explicitly in the plant hierarchy. These are automatically set up when
models or process tag types are created.
Naming
Note
The SIMATIC Manager supports names longer than 8 characters. The name of the library
directory is, however, limited to 8 characters. Library names must therefore differ from each
other in the first 8 characters. The names are not case-sensitive.
Please make sure that the name of the file always coincides with the name of the library
originally set up. Name changes do not take effect at the file level in SIMATIC Manager.
Introduction
This section explains the most important functions when handling libraries. Become familiar
with these functions prior to adding objects to the master data library from other libraries.
Library functions
In the SIMATIC Manager, you can use the following functions with libraries:
● Open a library with the menu command File > Open > in the "Libraries" tab.
● You can copy a library by saving it under a different name with the menu command File >
Save As.
● You can delete a library with the menu command File > Delete in the "Libraries" tab.
● You can delete parts of libraries such as charts, blocks, and source files with the menu
command Edit > Delete.
● Libraries not in use can be hidden and then made visible again in the following manner:
– Select the menu command File > Manage in the "Libraries" tab.
– Select the desired library and click "Hide".
The library can be made visible again with the "Display" button.
Note
We recommend that you hide all of the libraries except for the master data library since
the master data library contains all the objects used in the project.
Result
A new library is set up in the multiproject.
Naming
Note
The SIMATIC Manager supports names longer than 8 characters. The name of the library
directory is, however, limited to 8 characters. Library names must therefore differ from each
other in the first 8 characters. The names are not case-sensitive.
Please make sure that the name of the file always coincides with the name of the library
originally set up. Name changes do not take effect at the file level in SIMATIC Manager.
8.6.5 How to Copy Objects from Other Libraries to the Master Data Library
Introduction
The following section describes how to enter objects from the supplied PCS 7 library or from
libraries from other suppliers in the master data library.
NOTICE
Only the AS blocks of one PCS 7 library version can be loaded on a SIMATIC station at any
one time.
Procedure
If you want to copy part of a library, for example, software, blocks, pictures etc., proceed as
follows:
1. Select the menu command File > Open in the SIMATIC Manager.
2. Open the "Libraries" tab.
3. Select the desired library and click "OK".
The library opens.
4. Select the object to be copied (for example, process tag type, blocks) in the open library
(source) and then select the menu command Edit > Copy.
5. Select the folder in the master data library (destination) where you want to store the
copied object.
6. Select Edit > Paste from the menu.
Result
The copied object is stored in the master data library.
Note
Simultaneous use of the libraries "Standard Library" (STEP 7), "CFC Library" (ES/CFC),
"PCS 7 Library":
The libraries of STEP 7, ES/CFC, and PCS 7 contain blocks with the same name (but
with different functions) as well as blocks with the same number (but with different
functions).
• Same block name - CONT_C/CONT_S/PULSGEN/CTU/CTD/CTUD
For these blocks, please use the blocks from the CFC Library, since these are better
adapted to the PCS 7 environment.
• Same block number
Solution: The blocks must be assigned free FB/FC numbers in the block folder.
– For: FC 61 ...125 in the libraries "Standard Library - S5-S7 Converting Blocks" and
"Standard Library - TI-S7 Converting Blocks" and "CFC Library ELEMENTA"
– For: FC 1 ... FC 40 in the libraries "Standard Library - Communication Blocks",
"Standard Library - IEC Function Blocks" and the reserved FC inventory in CFC.
● The symbolic name is also copied when blocks from a library are copied.
● When copying into the block folder, the "Insert Function Block" dialog box opens if the
system detects that the system attributes of a block you want to insert into the chart from
a library differ from those of the exiting block. You can perform an attribute update here
(see also the online help for STEP 7).
Note
Remember that the CPU may switch to STOP if FCs are missing.
● Remember that the block numbers used to access the blocks are stored in the code of
the multiple instance block. These numbers (and in turn, the code) can be changed by
using the menu command Options > Rewire...., which provides access to the rewiring
function in the SIMATIC Manager. Exception: with protected blocks.
Introduction
After including a new version of a block type or SFC type in the master data library or after
adapting a block type in the master data library, you can use the "Update block types"
function to list all components in which an older version of the modified block type or SFC
type is used. You can also select the components in which the modified block type or SFC
type should be updated throughout the entire multiproject.
The blocks of the templates (process tag types, models) are also updated.
If differences are found at SFC types, you can call up the Version Cross Manager (VXM) by
using the "Display differences" command button before carrying out updating, if the VXM
optional package is installed. The VXM displays the detailed differences of the compared
SFC types.
Procedure
1. Select one or more blocks in the block folder of the master data library or one or more
SFC types in the chart folder or the chart folder.
2. Select the menu command Options > Charts > Update Block Types....
The "Update Block Types" dialog box opens.
3. Select the S7 programs to be checked for differences compared with the block types/SFC
types selected in the master data library.
4. Click "Continue".
All the selected S7 programs are checked and a further dialog box for selecting the
block/SFC types is opened. Here you also obtain information about the possible effects of
updating the block/SFC types.
5. Specify the block/SFC types to be updated for the individual S7 programs: All the
block/SFC types to be updated are selected. If necessary, you can deselect any types
which are not being updated.
If there are no block/SFC types to be updated, no block/SFC types are displayed. In this
case, close the dialog box.
6. Click "Finish".
Result
The block/SFC types are updated in all the selected S7 programs and a log is displayed.
Note
An update is required after changing blocks. Make the changes to the blocks only in the
master data library.
Additional information
● Online help on the dialog boxes
Introduction
The blocks from the PCS 7 libraries are suitable for most situations encountered during
configuration and can usually be used unchanged. If blocks must be adapted for a specific
project and for special requirements, adapt the blocks before using them in the projects and
then store them in the master data library.
What? Where?
Changing the Attributes of the Block I/Os LAD/CSF/STL Editor
(Page 324)
Locking Message Attributes Against Changes at PCS 7 message configuration
Block Instances (Page 326)
Translating Message Texts (Page 327) SIMATIC Manager
Setting the Language for Display Devices SIMATIC Manager
(Page 328)
Exporting/importing operator and display texts SIMATIC Manager
(Page 330)
Note
You may only adapt the blocks to the project requirements in the library. We also assume
that you are adapting the blocks in the master data library.
Introduction
The block I/Os of the block types have attributes that you can adapt to the project
requirements.
Procedure
1. Select the block to be modified in the block folder of the master data library.
2. Select the menu command Edit > Open Object.
The LAD/STL/FBD editor is launched (if the block is protected, you will receive a
message). If you select an object in the tree of the interface, its content is displayed.
3. In the right-hand window, select the desired I/O followed by the menu command Edit >
Object Properties.
The "Properties" dialog box opens.
4. Select the "Attributes" tab
The attributes are displayed in the form of a table.
5. Modify the attributes and their values in this table, or enter them again.
If you click the "Attribute" column, a selection of the possible attributes for this I/O appear
in a drop-down list.
Modifying attributes is not difficult since there is a syntax check when the attributes are
entered and you will be informed of errors or missing information.
Note
Information regarding the use of attributes and their description can be found in the online
help for the LAD/STL/FBD editors.
Procedure
1. Select the block to be modified in the block folder of the master data library.
2. Select the command Special Object Properties > Message... in the shortcut menu.
The "Message Configuration" dialog box opens. This displays all the messages
configured for this block.
3. Place a check mark in the column behind the text that you wish to lock.
4. Click "OK" to apply the changes.
Result
The text is locked.
Note
If block instances already exist, the locking of the message attribute can be passed on to the
instances by repeating the block import.
Additional information
● For more detailed information on adapting operator and message texts, refer to the
Configuration Manual Process Control System PCS 7; Operator Station.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
Procedure
1. In the SIMATIC Manager, select the menu command Options > Language for Display
Devices....
2. Set the language for the PCS 7 blocks, for example, "German (Germany)".
3. Select the language from the "Languages installed in the project" list that you want to
define as the standard and then click "Standard".
4. Click "OK".
For your project, you can select several languages from the list of available languages and
define one of them as standard.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Online help for the dialog box
8.6.7.6 How to Create your own Blocks for the Master Data Library
Note
In CFC, you can assign the block icons to specific instances in the object properties of the
blocks.
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
Introduction
The entire content of a table can be exported from the process object view for the external
assignment of modified parameter values and interconnections to a copied unit. You can
then import the modified data again. This method can be used as an alternative to the
Import/Export Assistant.
Note
The instances are edited during import/export procedure described above. The ability to
make centralized changes is lost.
Languages
PCS 7 can be used to store all operating and display texts in any language. The only
requirement is that the language is already installed in your project.
The available languages can be displayed in the SIMATIC Manager with the menu command
Options > Language for Display Devices. The number of languages offered is specified
when Windows is installed (system characteristics).
Exporting Blocks
1. Select the menu command Options > Process Objects > Export Blocks
An export file (CSV file) is created that contains all the attributes and information about the
blocks of the object (project, hierarchy folder or CFC chart) selected in the tree window.
Exporting I/Os
1. Select the menu command Options > Process Objects > Export I/Os....
An export file (CSV file) is generated containing all the attributes of the selected I/Os and
information about the I/Os of the object (project, hierarchy folder, or CFC chart) selected in
the tree.
The information from the process object view ("Parameters" and "Signals" without filters)
including the titles is written.
Exporting Messages
1. Select the menu command Options > Process Objects > Export Messages....
An export file (CSV file) is generated containing all the message texts (and block
information) concerning the object (project, hierarchy folder, or CFC chart) selected in the
tree.
Additional Editing
NOTICE
Never overwrite management information (language identification or path specifications)
while editing the exported texts.
Only edit lines beginning with "T-ID=".
NOTICE
Always open the file inside of the program, for example, when using MS Excel with the
menu command File > Open and not by double clicking the file.
Never edit the first column or the first row with the spreadsheet editing tool and do not
delete any semicolons.
Importing Blocks
1. Select the menu command Options > Process Objects > Import Blocks....
2. Select the required import file (CSV file).
The attributes and information of the blocks of the selected import file are imported into the
desired project. They are assigned to the blocks.
Importing I/Os
1. Select the menu command Options > Process Objects > Import I/Os....
2. Select the required import file (CSV file).
The I/O attributes and information of the selected import file are imported into the desired
project. They are assigned to the I/Os of the designated process tags (hierarchy, chart,
block, I/O).
Importing Messages
1. Select the menu command Options > Process Objects > Import Messages....
2. Select the required import file (CSV file).
The message texts of the selected import file are imported into the desired project. They are
assigned to the blocks of the designated process tags (hierarchy, chart, block).
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Online help on the dialog boxes
Introduction
Process tag types are installed automatically in the "Process Tag Types" folder in the master
data library as soon as a new process tag type is generated from a CFC chart. The process
tag types are managed in the master data library. The following functions are available:
Function Purpose
Creating/Changing • Creating a process tag type from CFC charts
Process Tag Type – You select the I/Os of blocks and charts that are to be assigned
parameter descriptions and signals.
– You select blocks with messages for the assignment of message texts.
• Changing an existing process tag type
• Check the existing process tags for deviations compared to the process
tag type and to synchronize any differences.
Synchronize When a process tag type is modified, the process tags existing in the project
are automatically synchronized.
Synchronization can be carried out directly if inconsistencies between the
process tag type and the process tags (for example: not all of the process
tags of a project were accessible during the synchronization process) exist.
Assigning/creating To generate process tags, an import file must be assigned to the relevant
an import file process tag type. Use the wizard "Assigning an import file to a process tag
type" to carry out the following:
• Assign an existing import file
• Open and check an import file that has already been assigned
• Create and assign a new import file
Importing Import of the data of the process tag types
The process tag type is copied from the master data library to the specified
target projects as a process tag. Thereafter the data is imported. The same
number of process tags are generated as there are entries in the import file.
As a result of the import, a process tag of this process tag type is created in
the target project for every row of the import file according to the specified
hierarchy path.
Exporting Export of the data of the process tags for a process tag type
The following options are available:
• Selecting one process tag to export it individually.
• Select an upper-level hierarchy folder or the project node in order to select
all lower-level process tags for export.
As the result, a row is created in the relevant export file for each process tag
of a process tag type found.
Additional information
● Section "How to Create a Process Tag Type from a CFC Chart (Page 518)"
● Section "How to Modify a Process Tag Type (Page 520)"
● Section "How to Synchronize Process Tags with the Process Tag Type (Page 529)"
● Section "What Happens during Import? (Page 637)"
● Section "What Happens during Export? (Page 642)"
● Online help for PH, IEA and PO
Introduction
Models are created from the hierarchy folders in the master data library that contain the
required CFC charts. The new models are stored and managed in the master data library.
The following functions are available:
Function Purpose
Creating/Modifying You can create models with the Import/Export Assistant (IEA) as follows:
Models • You select the I/Os of blocks and charts that are to be assigned parameter
descriptions and signals and imported.
• You select blocks with messages for the assignment of message texts.
• You assign the import file to model data.
You obtain a model in which the selected I/Os and messages are each
assigned to a column of an import file.
If you modify an existing model and change the column structure or the
column titles, the assignment to the structure of the current IEA file is no
longer correct. In this case you must select a suitable IEA file or adapt the file.
If replicas of the modified model exist then modifications can be carried out on
the replicas.
Importing Importing of the data of the models
The model is copied from the master data library to the specified target
projects as a replica. Thereafter the data is imported. The same number of
replicas are generated as there are entries in the import file.
As a result of the import, a replica of this model is created in the destination
project for each row of the import file, according to the information in the
hierarchy path .
Exporting Exporting of the replica data for a model
The following options are available:
• Selecting one model to export it individually.
• Selecting an upper-level hierarchy folder or the project node in order to
select all lower-level replicas for export.
As the result, one row is created in the relevant export file for each replica of a
model found.
Additional information
● Section "How to Create a Model (Page 570)"
● Section "What Happens during Import? (Page 637)"
● Section "What Happens during Export? (Page 642)"
● Online help for PH, IEA and PO
Introduction
If you have created your multiproject with the PCS 7 wizards, the master data library already
contains a "Shared Declarations" folder. You can then use this to store shared declarations
that can be used by various applications. You can explicitly create the "Shared Declarations"
folder if it does not yet exist.
The "Shared Declarations" folder contains the following subfolders:
● Enumerations
● Units
● Equipment Properties
Shared declarations
You can define the following elements as shared declarations:
● Enumerations
Using the enumerations, you can define textual representatives for the parameter values
of the block or chart I/Os with data types "BOOL," "BYTE," "INT," "DINT," "WORD," and
"DWORD". A suitable text is assigned to each value of an enumeration and this is
displayed at the I/O. Several values can be assigned to each enumeration.
● Units
The unit of measure (for example, mbar, l/h, kg, etc.) is a text with a maximum of 16
characters. It can be entered during the parameter and interconnection descriptions of
block or chart I/Os. It is used for example, in process pictures when visualizing the values
of the block I/Os. All the units of measure included in the CFC basic set are available as
defaults.
● Equipment properties
Equipment properties are parameters of a unit, such as shell material, volumes etc.. The
type of equipment property is defined as a "shared declaration". Instances of this type are
used in SIMATIC BATCH and its attributes are individually adapted.
Procedure
1. Select the master data library of the multiproject.
2. Select the menu command Insert > Shared Declarations > Shared Declarations.
The "Shared Declarations" folder is created with the subfolders "Enumerations", "Units"
and "Equipment Properties".
3. When declaring an enumeration, select the "Enumerations" folder and then the menu
command Insert > Shared declarations > Enumeration followed by the menu command
Insert > Shared declarations > Value.
4. When declaring a unit, select the "Units" folder and then the menu command Insert >
Shared Declarations > Unit.
5. If you want to declare an equipment property, mark the "Equipment Properties" folder and
select the menu command Insert > Shared Declarations > Equipment Property.
Additional information
● Online help for the SIMATIC Manager
Requirement
The AS must be accessible from the engineering station since the test is always executed in
the AS. Test the corresponding OS pictures in the OS if the models contain OS pictures.
Additional information
● Online help of the relevant tools (for example, CFC Editor)
Additional information
● Online help of the relevant tools (for example, CFC Editor)
Note to Reader
Pay attention to the following sections if you now want to edit the multiproject (including the
master data library) on distributed stations and with several editors at the same time.
If you do not want to distribute the multiproject for editing, you can skip the following sections
and continue with the section "Configuring the Hardware".
Introduction
It is possible to edit the projects of the multiproject on distributed stations allowing several
editors to work on smaller handier projects at the same time.
The distributed editing of projects and the merging on a central engineering station server for
cross-project functions is the most efficient method compared with other procedures.
Despite distributing the projects on several engineering stations, it is possible to read other
projects at any time. This can, for example, be used to copy functions and to access
libraries.
Note
You should always work with a multiproject even if it only contains one project. In this case,
you do not need to distribute it for editing.
Requirements
If you want to distribute projects on different computers within a network, the following
conditions must always be met:
● The projects are located in folders that are shared for read and write access.
– The folders in which the multiproject or the projects are to be located must be set for
sharing before the multiproject is set up.
– The share names must be unique within the network.
– The shares and share names of the resources (folders) involved in the multiproject
must not be changed.
Reason: when a project is inserted into the multiproject, PCS 7 generates a reference
to the location of this project. The reference depends on the share and share names
of the resources involved.
– A project can only be found using the share name under which it was included in the
multiproject.
– For security reasons complete drives should not be shared.
– Folders must only be shared in one hierarchy level.
● PCS 7 must be installed on the computers where the folders containing the projects are
located. PCS 7 provides the necessary database server functions for accessing the
projects.
● If you include projects for which you have configured messages in a multiproject, make
sure that the message number ranges of the CPUs do not overlap if you are using
project-oriented assignment of message numbers. If you use CPU-oriented message
number assignment, such overlapping does not occur.
If you execute cross-project functions, we recommend consolidating all projects on one
programming device/personal computer.
If you want to execute cross-project functions while the projects are distributed on different
computers then comply with the following:
● All the computers on which the projects and the multiproject are located can be reached
over the network during the entire editing time.
● While class-project functions are executing, no editing must take place.
Recommendations
We recommend the following procedure when working with multiprojects:
● One engineer manages the multiproject centrally. This engineer creates the structures for
the projects. This person also distributes the projects for distributed editing and returns
them again to the multiproject (including synchronization of the cross-project data and
execution of cross-project functions).
The following activities should only be performed on the central engineering station:
– Moving, copying, and deleting the projects of the multiproject
– Moving projects out of the multiproject for distributed editing
– Merging of the projects into the multiproject following distributed editing
● It is not possible to make a general recommendation about how many stations a project
should have. We recommend that projects on a distributed engineering station have only
one 1 AS or 1 OS.
● Only move the PCS 7 objects to a distributed engineering station that are actually
necessary for editing. This means that all other objects of the multiproject are available
for editing on other distributed engineering stations.
● Keep in mind the number of available project editors when distributing the projects.
Note
If there is only one OS in the project, this must always be recompiled on the central
engineering station. This ensures the correct structure of the cross-project connections to
the automation systems.
CAUTION
For multiproject engineering with SIMATIC BATCH, distributed engineering on distributed
engineering stations including testing is only possible when certain conditions are met and
the additional steps are taken.
You will find additional information on this topic on the Internet
(http://support.automation.siemens.com/WW/view/en/23785345).
Additional information
● Section "Conditions for Additional Editing in the Multiproject (Page 345)".
Boundary conditions
Observe the following conditions when working in the multiproject:
● Network operation is only possible if an operating system is installed on the central
engineering station in accordance with the requirements of the "pcs7 readme.rtf" file
(Section: "Operating System Selection").
The same applies to distributed engineering stations.
● The storage location of projects within the network must be specified in UNC notation:
\\computername\sharename\storagepath
not designated with the letter of the drive (not "d:\projects\storagepath...").
● The folder with the project must already be shared with other project editors on the
relevant PC. The share name must be unique.
● The storage paths must not be modified later (after storing projects)!
● All the projects and the S7 programs must have unique names within the multiproject.
● After distributed editing of projects containing an OS, each OS must be recompiled on the
central engineering station. To speed up compilation, unmodified objects can be
deactivated in the "Compile and Download Objects" dialog box (menu command in the
SIMATIC Manager PLC > Compile and Download Objects).
● A mixture of the previous project-oriented and the new CPU-oriented message number
concept is not possible.
CAUTION
For multiproject engineering with SIMATIC BATCH, distributed engineering on distributed
engineering stations including testing is only possible when certain conditions are met and
the additional steps are taken.
You will find additional information on this topic on the Internet
(http://support.automation.siemens.com/WW/view/en/23785345).
Additional information
● Section "Merging projects after distributed editing (multiproject engineering) (Page 621)"
● Section "Introduction to Compiling and Downloading (Page 665)"
● Online help on STEP 7
Prior to Distribution
There is no particular point in time at which the projects should be moved to the distributed
engineering stations. The "Must/Optional" columns in the following table indicate which tasks
must be performed and which can be performed prior to distribution.
The description for executing the configuration is structured according to this series of steps.
Requirements
● The multiproject is located on a central engineering station to which all other engineering
stations have access.
● The multiproject contains the libraries (in particular the master data library with the
models and process tag types).
Procedure
1. Specify the storage location for your projects. Create the required folder structure with the
Windows Explorer.
Refer to the details in the sections "Distributing the Multiproject for Distributed Editing
(Multiproject Engineering) (Page 342)" and "Conditions for Additional Editing in the
Multiproject (Page 345)".
2. In the SIMATIC Manager, select the menu command Options > Customize and set the
storage location of the projects, multiprojects, and libraries. Comply with the DOS name
conventions.
Additional information
● Online help for the SIMATIC Manager
Requirements
● The project is physically located on the central engineering station and is included in the
multiproject.
● The distributed engineering station is obtainable over the network.
Procedure
1. Select the project in the multiproject that you want to move to the distributed engineering
station in the component view of the SIMATIC Manager.
2. Select the menu command File> Save as ....
3. Make the following settings:
– Enable the "Insert in multiproject" option.
– Select the "Current multiproject" entry from the corresponding drop-down list.
– Enable the "Replace current project" option.
– Enter the required storage location (path) on the distributed engineering station (in
UNC notation).
4. Click "OK".
Result
● An identical copy of the project of the central engineering station is created on the
distributed engineering station. The copy is inserted automatically in the multiproject and
replaces the original project.
● The existing original project is removed from the multiproject, but remains on the central
engineering station. You can either keep the original project as a backup or delete it.
Note
Before the copied project can be copied back to its old location (same folder name), this
backup must be deleted.
Note
In the same way, you can also save the project on a data medium and pass this on for
distributed editing or archive the project with the "Archive" function and pass on the
archive on a data medium.
Note
You can also move a project to a distributed engineering station as follows:
1. In the component view of the SIMATIC Manager select the project within the multiproject
that you remove from the multiproject.
2. Select the menu command File > Multiproject > Remove for Editing...
The "Select Directory" dialog box opens.
3. Select a directory and click "OK".
Result
The project is marked as "removed for editing" and displayed in gray.
When a project has been removed, in contrast to the procedure described above, you can
not use the "Archive", "Save As", and "Compile OS" functions.
Additional information
● Section "Merging Projects after Distributed Editing (Multiproject Engineering) (Page 621)"
● Section "How to Move Project Edited on Distributed Stations to the Central Engineering
Station (Page 622)"
Requirement
All the PCS 7 software components required for editing are installed on the distributed
engineering station.
Note
These changes must be reversed before the project is copied or moved back to the
central engineering station.
Additional information
● Section "How to Move Projects Edited on Distributed Stations to the Central Engineering
Station (Page 622)"
Overview
Configuring the hardware involves the following topics:
● Defining a Project-Specific Catalog Profile (Page 353)
● Exporting/Importing the Hardware Configuration (Page 354)
● Configuring the SIMATIC 400 Station (CPU, CPs, Central I/O) (Page 357)
● Setting Time Synchronization (Page 379)
● Configuring the Distributed I/O (Standard) (Page 382)
● Configuring the Distributed I/O for Configuration Changes RUN (Page 396)
● Configuring the Hardware for High-precision Time Stamps (Page 417)
● Activating acknowledgment-triggered reporting (Page 418)
● Downloading the configuration to the CPU (Page 419)
Introduction
The configuration of the hardware involves the configuration of your plant at the automation
level (AS, OS, BATCH, Route Control, OpenPCS 7) in the SIMATIC Manager and in
HW Config. You may create your SIMATIC 400 stations distributed in various projects and
configure the required I/O and communication hardware.
You configure various project types in the PCS 7 OS according to the structure of your plant.
For example, you can configure process cells with one or more OS servers or OS clients.
Generally, you work with a multiple station project and create several OS servers and OS
clients.
In addition you can create and configure redundant components in the hardware
configuration (for example redundant OS, use of H-stations).
What? Where?
Adding all the SIMATIC 400 stations to the project. SIMATIC Manager
Inserting the engineering station (ES), operator stations (OS), BATCH
stations (BATCH), Route Control stations and OpenPCS 7 station as
PC stations in the project.
Adding hardware components to the SIMATIC 400 stations. HW Config
You insert hardware components and applications that belong to the
particular PC station.
Note to Reader
For multiproject engineering, the SIMATIC 400 stations and PC stations are often already in
your project. The following section describes how you continue by adding the hardware
components to the SIMATIC 400 stations.
If the PC stations have not yet been created, first perform the following tasks before
continuing below:
● "How to Insert an Engineering Station and Configure It (Page 277)"
● "How to Insert an Operator Station and Configure It (Page 279)"
● "How to Insert a BATCH Station and Configure It (Page 281)"
● "How to Insert a Route Control Station and Configure It (Page 283)"
● "How to insert and configure an OpenPCS 7 station (Page 285)"
Additional information
Information on configuring the hardware for the operator stations can also be found in the
configuration manual, Process Control System PCS 7; Operator Station.
Note
DP slaves installed later (using GSD files) are only contained in the "Standard" profile
("Additional Field Devices" folder) and are not automatically included in user-created profiles!
Note
You can remove catalog profiles that you do not require with the menu command Profile >
Delete.
Introduction
You cannot only edit station configurations within the project (e.g. by saving or opening). You
can also export it to a text file (ASCII file, CFG file), edit (adapt) it and then import it again
independently of the project. The symbolic names of the inputs and outputs can also be
exported and imported.
Application
The export/import functions can be used as follows, for example:
● Data import from hardware planning tools
● Station configuration using electronic media (for example, e-mail)
● The export file can be printed out with a word processing system or can be edited for
documentation purposes.
Where Is it Described?
You can find a detailed description of importing and exporting the hardware configuration in
the section "Import/Export of the Hardware Configuration (Page 653)".
8.8.5 Configuring the SIMATIC 400 Station (CPU, CPs, Central I/O)
Introduction
Before you can start with the configuration of the hardware, first create a concept for
assigning addresses. The networks are independent of each other and have their own range
of numbers for addresses.
We distinguish between the following addresses:
● Node Addresses
● Input/Output Addresses (I/O Addresses)
Node Addresses
Node addresses are addresses of programmable modules (PROFIBUS, Industrial Ethernet
addresses). They are needed in order to address the various nodes of a subnet, e.g. to
download a user program over the plant bus (Industrial Ethernet) to a CPU. You will find
more information about assigning node addresses on a subnet in the section on networking
stations.
(626 $6[[
03,
,QGXVWULDO(WKHUQHW
352),%86'3
(70 (76
&3H[W
&3
352),%86'3 &38
(70 (76 (7L63
1
0
Note
For the high-precision time stamp, PROFIBUS DP must be connected to the SIMATIC 400
station via a CP 443-5 Extended or via the internal PROFIBUS DP interface.
Introduction
The following table provides you with an overview of the various configuration steps and the
corresponding tools.
What? Where?
Creating a SIMATIC 400 station (Page 359) SIMATIC Manager
Inserting modules in a SIMATIC 400 station (Page 360) HW Config
Inserting a communications processor (CP) (Page 364) HW Config
Setting the CPU properties (Page 367) HW Config
Setting the process image (Page 371) HW Config
Configuring fault-tolerant systems (H systems) (Page 377) HW Config
See the manual Process Control System PCS 7; Fault-
tolerant Process Control Systems for more information.
Configuring Fail-safe Systems (F systems) (Page 377) HW Config
See the manual Automation Systems S7-400F/S7-400FH,
Fail-safe Systems for more information.
Setting the time synchronization (Page 381) HW Config
Configuring the distributed I/O for standard (Page 382) HW Config
Configuring the distributed I/O devices for configuration HW Config
changes in RUN (CiR) (Page 402)
Assigning icons for the input and output addresses HW Config (Symbol Table)
(Page 366)
Configuring PA devices (Page 386) PDM
Configuring the diagnostic repeater (Page 387) SIMATIC Manager + HW Config
Configuring intelligent field devices (Page 389) PDM
Configuring HART devices (Page 392) PDM
Configuring Y links and Y adapters (Page 394) HW Config
Importing/exporting the hardware configuration HW Config
Configuring the high-precision time stamps (Page 417) HW Config
Activating acknowledgment-triggered reporting (Page 418) HW Config
Downloading the configuration to the CPU (Page 419) HW Config
Additional information
● Online Help for HW Config
Introduction
In multiproject engineering, automation systems may have already been created in your
project. You can insert additional automation systems as follows:
● With PCS 7 "Expand Project" wizard
You can find information about this in the section "How to Expand a Project with
Preconfigured Stations (Page 263)".
● Manually if you do not use any supplied bundles (described below)
Procedure
Before you can start to configure and assign parameters, you will need a SIMATIC 400
station in your project that you can insert at the level immediately below the project, where
you can then set its properties.
1. Select the project to which you want to add another automation system in the SIMATIC
Manager component view.
2. Select the menu command Insert > Station > SIMATIC 400 Station.
A new SIMATIC PC station is inserted in the selected project.
3. Repeat the procedure to add further automation systems.
You can change the names as required by selecting the menu command Object Properties
from the SIMATIC 400 station shortcut menu.
Additional information
● Section "How to Insert Modules to a SIMATIC 400 Station (Page 360)"
Introduction
After you have created the SIMATIC 400 station, add the hardware components to the
station from the hardware catalog.
Hardware Catalog
The hardware catalog is normally displayed when you open HW Config. If this is not the
case, open it in HW Config with the menu command View > Catalog.
In the bottom third of the catalog, you will see the order number and a brief description of the
currently selected component. Compare this order number with the order number of your
existing component. You can then be sure that you have selected the right component.
Note
In the hardware catalog, you can select from various profiles (Standard, PCS 7, etc.). All the
profiles are based on the "Standard" profile and represent a subset of this profile.
The "PCS 7_Vx.y" profile is displayed by default when you first start the hardware
configuration. This profile shows the current versions of all modules and devices released for
PCS 7 Vx.y.
If you cannot find the module you require in this profile (for example, an older CPU that is
nevertheless released for PCS 7), select the "Standard" profile and then select the required
module from it. Please note that module default settings may vary from one module to
another.
You will find a list of released modules in: Start > SIMATIC > Documentation > English >
PCS 7 - Released Modules.
You can create an individual profile with the modules and devices which you frequently
require: You can find information about this in the section "Defining a Project-Specific
Catalog Profile (Page 353)".
Procedure
1. Select the station in the component view and double-click the "Hardware" object in the
detail window.
The HW Config and hardware catalog open.
Note
When you want to add additional modules to a SIMATIC 400 station created with the
PCS 7 wizards, continue with Step 6.
2. In the SIMATIC 400 > Rack-400 hardware catalog, select the required rack and insert it
by dragging with the mouse.
Make sure that the arrangement selected here matches the arrangement of the physical
hardware.
3. In the "SIMATIC 400 > PS-400" hardware catalog, select the required power supply and
add it by dragging with the mouse.
4. In the SIMATIC 400 > CPU-400 hardware catalog, select the required CPU and insert it
by dragging with the mouse.
5. Click "OK" to confirm the "Properties - PROFIBUS Interface" dialog box that opens.
6. Proceed in the same way to add any other components you require, for example:
– "SM 400": digital and analog signal modules (CPUs)
– "CP 400": communication modules: You can find information about this in the section
"How to Insert a Communications Processor (Page 364)".
7. Select the menu command Station > Save in HW Config.
Note
If you want to connect PROFIBUS DP to a CP 443-5 Extended, you do not need to set the
properties.
Note that the integral PROFIBUS DP interface does not perform the same range of functions
as the CP 443-5 Extended (e.g. number of PROFIBUS nodes).
Additional information
● Section "How to Configure the Distributed I/O (Page 382)"
● Section "How to Insert a Communications Processor (Page 364)"
Note
If you use a CPU with an integrated Ethernet interface, you can make the connection to the
plant bus with it. You then do not need a CP 443-1 communication processor.
Adding a CP 443-1
1. Select the required SIMATIC 400 station from the component view and double-click the
"Hardware" object in the detail window.
The hardware configuration of the automation system is opened.
2. Select "SIMATIC 400 > CP-400 > Industrial Ethernet ..." in the hardware catalog and drag
the CP you require.
Make sure that the arrangement selected here matches the arrangement of the physical
hardware.
Once you have inserted the CP, the "Properties - Ethernet Interface CP 443-1" dialog box
is opened.
3. Activate the check box "Set MAC address/Use ISO protocol" and assign the desired MAC
address (for example 08.00.06.01.00.12 or the preset address of the CP used), or accept
the default address.
Make sure that the address is unique on the bus.
4. Enter the IP address and subnet mask or deactivate the "IP protocol is being used" check
box.
5. Click "New" and replace the name "Ethernet(1)" with a name that will be more meaningful
later on.
6. Then click "OK" twice.
The "Properties" dialog box closes.
Note
The high-precision time stamps are used in conjunction with the IM 153-2 or routing
(parameter assignment for the DP/PA slaves over the ES and the plant bus) via the
integrated PROFIBUS DP interface or the CP 443-5 Extended.
Note
The addresses 1 and 126 are default addresses for DP slaves. Do not use the default
addresses in your project.
4. Click "New" and replace the name "PROFIBUS(1)" with a name that will later be more
meaningful.
5. Select the "Network Settings" tab and set the transmission rate "1.5 Mbps" and the "DP"
profile.
6. Then click "OK" twice.
The "Properties" dialog box for the PROFIBUS interface closes.
Additional information
● Online Help for HW Config
Introduction
You can assign symbols to the addresses of inputs and outputs when configuring modules
without needing to start the symbol table in the SIMATIC Manager (symbols editor).
You can also find information about this in the section "Free Assignment between Hardware
and Software (Page 220)"
Note
The assigned symbols are not downloaded when you download to the station with the menu
command PLC > Download to Module....
Effect: If you use menu command PLC > Upload to PG to upload to the programming device,
no symbols are displayed.
Procedure
1. Select the digital/analog module whose addresses you want to assign symbols to.
2. Select the menu command Edit > Symbols....
The symbol table opens.
3. Enter the required symbols for the addresses listed.
4. Click "OK".
Tip:
If you click the "Add Symbol" button in the dialog box, the name of the address is entered as
a symbol.
Additional information
● Online Help for HW Config
What? Where?
Setting the CPU startup mode (see below) HW Config (Object Properties)
Setting OB 85 (I/O access error) (see below) HW Config (Object Properties)
Setting the Process Image (Page 371) HW Config (Object Properties)
Adapting the local data (see below) HW Config (Object Properties)
Warm restart
In a warm restart, execution of the program restarts at the beginning of the program with a
"basic setting" of the system data and user address areas. Non-retentive timers, counters,
and memory bits are reset. All data blocks and their contents are retained.
When you restart (warm restart) an S7-400 (for example by changing the mode selector from
STOP to RUN or by turning the power ON) organization block OB100 is processed before
cyclic program execution begins (OB 32 - OB 38). As default, all the PCS 7 blocks that have
a special startup behavior are installed in OB100.
Warm restart = Default setting for PCS 7 and normal applications
Cold restart
A cold restart is used only in exceptional situations when one of the following functions is
required:
● During a cold restart, the process image input table is read and the user program is
executed, starting at the first command in OB1.
● Data blocks created by SFCs in the RAM are deleted, while the other data blocks have
the default values from the load memory.
● The process image and all timers, counters, and memory bits are reset regardless of
whether they were set as retentive.
Hot restart
In a hot restart, program execution is resumed at the pointer to which it was interrupted
(timers, counters, and memory bits are not reset).
Note
A hot restart is not permitted when using S7-400 CPUs in the PCS 7 process control system.
Note
Make sure that you also take into account any reserves configured for CiR (configuration
change in RUN).
Additional information
● Section "Default Parameter Values for the CPUs (Page 378)"
● Online Help for HW Config
Introduction
The driver blocks for the modules in the PCS 7 library do not access the I/O directly to query
the current signal states, but rather access a memory area in the system memory of the CPU
and the distributed I/O: the process input image (PII) and process output image (PIQ). This
process image includes both the digital inputs and outputs as well as the analog inputs and
outputs.
The process image starts with I/O address 0 and ends at a high limit as set in HW Config.
Note
The default size of the process image depends on the CPU.
You can also find information about this in the section "Default Parameter Values for the
CPUs (Page 378)"
Note
Please note the following:
• Each input/output address must be assigned to a process image partition.
• Each input/output address that you assign to a process image partition no longer belongs
to the OB1 process input/output image.
• Input/output addresses can only be assigned once throughout the OB 1 process image
and all process image partitions.
• Make sure that signals and signal processing (module and corresponding driver) are
executed in the same OB.
You make the assignment to the process images during hardware configuration of the I/O
modules (see Figure below).
Note
Changing the cyclic interrupt time in the RUN of a CPU
Each change to the cyclic interrupt time of a CPU requires compilation of the program.
Otherwise, the CPU_RT block continues to work using the old values.
Additional information
● Online Help for HW Config
SIMATIC H Station
For a fault-tolerant automation system, a SIMATIC H station is added to the project as a
separate station type in SIMATIC Manager. This station type is required if you want to
configure two central racks each with an H CPU, thereby configuring your process control
system with redundancy.
Modifying Parameters
When you work with new projects created with PCS 7 V7.1, PCS 7 sets default values for
the automation systems.
The table in the section "Default Performance Parameters of the CPUs (Page 138)" shows
the default parameters for the performance capability of typical CPUs for PCS 7 projects.
These values are set as defaults in the configuration of the CPU with PCS 7 software.
The default parameters suffice for typical applications but can be changed within limits as
required for configuration.
You can modify these parameters on the tabs of the CPU "Properties" dialog box using the
menu command Edit > Object Properties.
Note
After adapting the parameters, a download with the CPU in STOP is necessary.
Additional information
● Section "Default Performance Parameters of the CPUs (Page 138)"
Note
In PCS 7 UTC time is always used internally in the system.
Time information displayed to the plant operator in process mode (OS Runtime) can be
displayed optionally in UTC or local time. This makes system configuration possible across
time zone boundaries.
This makes it possible to configure a system, for example, with the automation system in a
different time zone than the operator station. When necessary, the operator can also change
over between displayed in UTC or local time during operation.
Time Stamp
The time stamp in the diagnostic buffer, messages and OB start information is generated
with UTC.
Additional information
● Function Manual Process Control System PCS 7; Time Synchronization
● Configuration manual Process Control System PCS 7; Operator Station
● Manual Process Control System PCS 7; PC Configuration and Authorization
Additional information
● Manual Process Control System PCS 7; High-precision Time Stamps
● Function Manual Process Control System PCS 7; Time Synchronization
Introduction
In the following configuration instructions, we start from an example configuration for the
distributed I/Os with the following components:
● ET 200M (communication via PROFIBUS DP)
● S7-300 I/O modules plugged into the ET 200M
To configure the distributed I/Os, carry out the following configuration steps one after the
other:
1. Add DP slave
2. Add I/O modules
3. Add symbolic names for the channels
Note
From the hardware catalog, select the IM 153 that matches the backplane bus you are
using (passive or active backplane bus) and the product version marked on the actual
IM 153 module you intend to use. In PCS 7, the active backplane bus is used.
3. For the "PROFIBUS Address", select an address for the DP slave that is unique in your
DP network (for example, 7). You must set the selected address on the IM 153-... using
DIL switches (hardware switches).
4. Click "OK".
5. Select the ET 200M and select the menu command Edit > Object Properties....
6. Open the "Operating Parameters" tab.
7. Check the "Change Module during Operation" check box.
8. Click "OK".
Note
If you do not check this check box and a module fails, the AS will interpret the module
failure as a failure of the ET 200M.
2. Select the first module and select the menu command Edit > Object Properties....
3. Set the address and the process image partition in the "Address" tab.
4. Set any other properties of the module according to your configuration requirements, for
example, diagnostic alarms or measuring ranges.
5. Repeat the procedure for the other modules.
Note
The channel specific setting "Reaction to CPU-STOP" (OCV, KLV, SV) of a module (for
example, analog output module with four channels) within the ET 200M distributed I/O
station must be set identically for all channels.
Note
Make sure that the measuring range for the analog input module is also be set on the
module itself using a coding key. You can find the code letter for setting the coding key in
the object properties of the module in the "Inputs" tab to the right of the "Coding Key
Setting".
If you use an ET 200M (IM 153-x), you must install at least one input/output module in the
ET 200M or a CiR object to avoid consistency errors when saving and compiling the
hardware configuration.
3. Follow the same procedure with the other modules and enter the symbolic names for all
the other process values you require. Use the process tag list of the plant description.
Additional information
● Online Help for HW Config
● Manual SIMATIC; Distributed I/O Device ET 200M
● Manual SIMATIC; Distributed I/O System ET 200S
● Manual SIMATIC; Distributed I/O Device ET200iSP:
● Manual SIMATIC; Distributed I/O Device ET 200pro
Introduction
PCS 7 communicates with PA field devices via a DP/PA adapter or a DP/PA link. A DP/PA
link is configured below and preparations are made for the further configuration of the PA
devices with SIMATIC PDM.
Requirement
● The SIMATIC PDM (Process Device Manager) add-on package must be installed.
Procedure
1. Select the required SIMATIC 400 station from the component view and double-click the
"Hardware" object in the detail window.
The hardware configuration of the automation system is opened.
2. Configure a DP master system in HW Config.
3. Drag the DP/PA link (IM 153-2) from the hardware catalog to the DP master system.
The dialog box for "Properties - PROFIBUS Interface" opens.
4. Set the PROFIBUS interface parameters.
The dialog box for defining the master system opens.
5. Define the master system (DP or PA) and click "OK".
6. Select the DP/PA link so that you can view the DP slave structure in the bottom part of
the station window.
Slot 2 represents the ”master” for the PA devices.
7. Double-click Slot 2 to configure the PA subnet.
8. Click "Properties" in the "Interface" group on the "General" tab and select the subnet with
a transmission rate of 45.45 Kbps. Then click "OK".
9. Configure the PA devices.
You will find the PA devices in the "hardware catalog" under "PROFIBUS PA" (standard
profile).
Note
The "PROFIBUS PA" entry is only visible if SIMATIC PDM is installed.
You must configure at least one PA device in PROFIBUS PA. Otherwise errors will occur
during compilation or the consistency check.
The rest of the configuration for the PA devices takes place in SIMATIC PDM (double-
click the device).
Additional information
● Online Help for HW Config
● Manual SIMATIC; DP/PA Link and Y Link Bus Couplers
● Manual PDM; The Process Device Manager
● Section "Configuring the SIMATIC 400 Station (CPU, CPs, Central I/O)"
Introduction
The diagnostic repeater provides simple diagnostics for communication errors in PROFIBUS
DP chains using the DPVx protocol.
Requirements
● The diagnostic repeater is installed and wired up.
● The PROFIBUS address is set.
● The diagnostic repeater is configured (configuration and parameters).
● The DR switch behind the flap is set to ON (as supplied).
● The power supply for the DP master is turned on.
Configuring Hardware
1. Select the required SIMATIC 400 station from the component view and double-click the
"Hardware" object in the detail window.
The hardware configuration of the automation system is opened.
2. Drag the diagnostic repeater from the "PROFIBUS DP > Network Components" hardware
catalog to the DP master system of your CPU.
The "Properties - PROFIBUS Interface Diagnostic Repeater" dialog box opens..
3. Set the address and the properties (bus parameters), and click "OK".
4. Double-click the diagnostic repeater.
The "Properties – DP Slave" dialog box opens.
5. In the "Parameter Assignment" tab, set the DP alarm mode to DPV0 (OB 82 is called for
diagnostic events).
Requirement: The mode on the DP master must be set to DPV1.
6. Select Station > Save and Compile from the menu.
7. Select the menu command CPU > Download to Module....
The current configuration is loaded.
This completes the hardware configuration of the diagnostic repeater. Now carry out the
topology identification.
Note
If several PROFIBUS networks exist, the topology must be identified for each individual
network.
Additional information
● Manual SIMATIC; Diagnostic Repeater for PROFIBUS-DP
SIMATIC PDM
SIMATIC PDM is a complete and heterogeneous tool for configuration, parameter
assignment, commissioning, and diagnostics in conjunction with intelligent process devices.
You can use SIMATIC PDM during all phases of a project (engineering, commissioning, and
runtime). SIMATIC PDM allows a number of process devices to be configured with a single
software package using a standardized user interface.
SIMATIC PDM is used as an integrated tool in SIMATIC Manager and HW Config.
Integration in HW Config allows you to edit devices that are attached to PROFIBUS DP. All
other devices are edited in the process device network and plant view of SIMATIC PDM.
The display of device parameters and functions is uniform for all supported process devices
and does not depend on their communications connection, for example, whether they use
PROFIBUS DP/PA or the HART protocol.
The following key functions are particularly useful for testing and commissioning process
device data:
● Creating process device data
● Changing process device data
● Validating the process device data
● Managing process device data
● Simulating process device data
You can also display selected values, alarms and status signals for the device on screen and
thus monitor the process. Process-related values can also be manipulated using simulation
or with the devices in manual mode.
Communication
SIMATIC PDM supports several communications protocols and components for
communication with the following devices:
● Devices with PROFIBUS DP communication
● Devices with PROFIBUS PA communication
● HART devices
These devices can be attached in various ways. In its basic form, we distinguish
between:
– HART devices over PROFIBUS DP connected to ET 200M or ET 200iSP
– HART devices connected to HART multiplexers or HART interface
System Requirements
● You have created a device in HW Config that is configured with SIMATIC PDM.
● In order to work online with SIMATIC PDM, you require a PROFIBUS DP interface, e.g.
CP 5611. The CP must be set to the PROFIBUS DP interface (this is done in the
SIMATIC Manager via Options > Set PG/PC Interface).
Procedure in HW Config
1. Double-click the device you want to configure with SIMATIC PDM in HW Config.
The "User" dialog box opens.
2. Select the "Specialist" option to access all the modification options.
3. Click "OK".
SIMATIC PDM opens.
Additional information
● Manual PDM; The Process Device Manager
● Online help on STEP 7
Introduction
HART devices are intended for distributed operation on the IM 153-2 (ET 200M) or IM 152
(ET 200iSP).
Configuration with an ET 200M is illustrated below.
Start SIMATIC PDM to assign parameters to the HART measuring transducers attached to
the HART devices.
Requirement
You have opened a station with a DP master system and an ET 200M or ET 200iSP with
free slots in HW Config.
Additional information
● Manual PDM; The Process Device Manager
Introduction
To implement the changeover from a PROFIBUS master system to a single-channel
PROFIBUS master system, the Y link is preferred as the gateway.
From the point of view of the programmable controller, the Y link is a DP slave, and from the
point of view of the underlying DP master system, it is a DP master.
Procedure
1. Select the required SIMATIC H station from the component view and double-click the
"Hardware" object in the detail window.
The hardware configuration of the automation system is opened.
2. Drag an IM 153-2 from the "PROFIBUS DP > DP/PA Link" hardware catalog to the
redundant DP master system on your CPU.
The "Properties - PROFIBUS Interface IM 153-2" dialog box opens.
3. If necessary, change the suggested address for the IM 153-2 in the higher-level DP
master system and click "OK".
The dialog box for selecting the lower-level master system opens.
4. Select "Interface module for PROFIBUS DP" and click "OK".
The Y link is inserted into the redundant DP master system. The transmission rate of the
lower-level DP master system is set to 1.5 Mbps as default.
5. If you want to change the transmission rate of the lower-level DP master system, double-
click the DP master system.
The dialog box with the properties of the lower-level master system opens.
6. Click "Properties". The "PROFIBUS properties" dialog box is displayed.
7. Enter the name of the lower-level DP master system and select the “Network Settings“
tab.
8. Select the transmission speed 45.45 Kbps to 12 Mbps and click "OK".
9. Then configure the DP slaves for the lower-level DP master system.
Additional information
● Manual SIMATIC; DP/PA Link and Y Link Bus Couplers
Configuration Support
Apart from the diagnostic options provided by the maintenance station, you can also use the
diagnostic options provided by SIMATIC PDM to support you when configuring.
Use "SIMATIC PDM - LifeList" to test which DP devices and HART device are accessible on
the network.
Information on the causes of any connection errors can be found in the online help for
SIMATIC PDM.
Note
SIMATIC PDM requires device-specific information for devices with diagnostic capability.
After installing SIMATIC PDM you can supplement this information through the "Manage
Device Catalog" tool.
Additional information
● Online help on STEP 7
● Online help on SIMATIC PDM
● Manual PDM; The Process Device Manager
● Manual Process Control System PCS 7;Service Support and Diagnostics
8.8.8 Configuring Distributed I/O Devices for Configuration Changes in RUN Mode (CiR)
Introduction
There are some process cells that must not be shut down during operation. This may be due
to the complexity of the automated process or the high cost of restarting. Nevertheless, it
may be necessary to extend or modify the plant.
Using CiR (Configuration in RUN), it is possible to make certain changes to the configuration
in RUN mode.
Principle
To be able to make changes to the process cell during operation using CiR, you must make
provision for subsequent extending the hardware of your automation system specially for the
master system in your original configuration. You define suitable CiR objects that you can
later replace with real objects (slaves and/or modules) in the RUN operating state. You can
then download a configuration modified in this way to the CPU while the process is running.
Validity
You can make modifications to the plant during operation with CiR in sections of the plant
with a distributed I/O.
CiR requires the configuration shown in the figure below. For the sake of clarity, the
illustration shows only a DP and a PA master system.
The configuration consists of the following components:
● CPU (412, 414, 416, 417, firmware version 3.1.0 or later
414H, 417H in stand-alone mode, firmware version V3.1.0 or later)
● CP 443-5 Extended (firmware version 5.0 or later)
● ET 200M: IM 153 (as of 6ES7153-2BA00-0XA00)
352),%86'3PDVWHUV\VWHP
0RGXODU 68%1(7'3PDVWHUV\VWHP
'3VODYH ,0
'3PDVWHU (70 '33$
(76 FRXSOHU
RU(7L63 '33$OLQN
3$VODYH
ILHOGGHYLFHV
&RPSDFW
'3VODYH 3$VODYH
ILHOGGHYLFHV
Steps Involved
The steps required for a program and configuration change and the associated process cell
status are illustrated below.
Terminology
Term Meaning
CiR element Generic term for CiR object and CiR module
CiR object Placeholder for slaves to be added to the DP or PA master system later
CiR module Placeholder for modules to be added to an ET 200M/ET 200iSP station later
CiR elements
Note
When calculating the bus parameters, PCS 7 takes into account both the configured slaves
and the CiR elements. As a result, when converting the CiR elements into real slaves and/or
modules with the CPU in RUN, the bus parameters do not need to be changed.
CiR objects
Specify the following properties for a CiR object:
● The guaranteed number of slaves that can be added
(Default: 15 on the DP master system; 6 on the PA master system)
● Number of input and output bytes for future use
They relate to future user data addresses. Diagnostic addresses are configured
separately from them.
Default: 1220 each on the DP master system, 80 each on the PA master system).
CiR modules
For the modular I/O device ET 200M/ET 200iSP, define additional I/O volume using a CiR
module by specifying the total number of additional input and output bytes. This information
relates to future user data addresses. You can configure diagnostic addresses regardless of
this.
You do not have to fully utilize the additional user data volume. The currently available user
data volume must not, however, ever be exceeded. PCS 7 makes sure this is the case.
Note
If you want to add or remove slaves or modules or make a change to the existing process
image partition assignment, this is possible for up to four DP master systems.
8.8.8.4 How to Define CiR Elements for Future Plant Expansion (CPU-STOP)
Note
The rule of thumb for the reserves is: As little as possible – as much as necessary, since the
CiR synchronization time depends on the size of the reserves.
The CiR synchronization time is relevant when you activate a configuration change in RUN.
A CiR action interrupts operation on the AS at a maximum for this time. This is limited on the
system side by an upper limit of 1 second and is monitored by the system. During this time,
process outputs and process inputs are kept at the last valid values.
Make sure that you do not exceed a CiR synchronization time of 1 second.
The SFC 104 must not be used to set the CiR synchronization time with PCS 7 (it can cause
the CPU to STOP).
• We recommend that you only make the changes on one DP chain at a time, using small
steps and when starting a CiR. This will make it easier to monitor the changes in RUN.
• If your changes in RUN relate only to a DP chain, the maximum CiR synchronization time
is displayed when you select the CiR object.
• If you want to make changes to more than one chain at the same time, add the times of
the individual chains together.
• When you download the configuration data to the CPU, you will once again be informed
whether the CiR synchronization time is possible with the settings you have made.
Note
Please note the following:
• CiR elements can only be added automatically if there is no CiR object already in
the selected DP master system.
• CiR elements cannot be automatically added to DP master systems downstream of
an IM 153-2.
• If CiR capability is activated, slaves containing a CiR module and CiR objects (for
example, DP/PA link) are indicated in orange.
3. The defaults of the CiR objects are identical for all CPUs. Therefore, after activating the
CiR capability of a master system, each corresponding CiR object should be checked for
the following:
Does the CiR synchronization time of the master system specified in the properties
window for the CiR object match the high limit for the CiR synchronization time of the
CPU set on the CPU?
If necessary, you will have to reduce the number of guaranteed slaves in one or more
CiR objects.
Note
If there are no longer enough resources available on the master system, these values are
reduced accordingly. The resulting bus parameters "Target Rotation Time", "Target
Rotation Time Typical" and "Watchdog" are displayed in the properties window for the
CiR object.
Changing the Number of Additional Slaves and/or Number of Input and Output Bytes
1. In HW Config, select the desired CiR object.
2. Select the menu command Edit > Object Properties...
The "Properties" dialog box opens.
3. You can change the guaranteed number of additional slaves as required.
The resulting bus parameters Target Rotation Time, Target Rotation Time Typical and
Watchdog are displayed at the bottom of the station window.
4. Change the number of input and output bytes as required.
To do this, check the "Advanced Settings" check box (default). Do not increase the
number as this will increase the CiR synchronization time.
Note
A maximum of 244 input and output bytes are available for ET 200iSP. You can find more
information about this in the manual SIMATIC; Distributed I/O Device ET 200iSP.
Introduction
In STOP mode, you can delete CiR objects in DP and PA master systems or CiR modules in
modular slaves of the type ET 200M/ET 200iSP that you are defined earlier.
The configuration change does not depend on the operating state. It can only be
downloaded in STOP mode, however.
Note
Please note the following:
• CiR elements can only be deleted if there is a CiR object in the selected DP master
system.
• You cannot delete all CiR elements on the DP master system below an IM 153-2
(DP/PA link).
Note
If you attempt an illegal operation when adding real slaves or modules to the configuration,
you will only be made aware of this by an error message when you download the
configuration.
After any change to the process cell, you should use the menu command Station > Check
CiR Capability to check that the CiR capability still exists.
Rules
When adding components, keep to the following rules:
● Within a type ET 200M/ET 200iSP modular DP slave, you may only insert a CiR module
at the slot immediately after the last configured module.
This rule is automatically taken into account when you add CiR elements automatically.
● Within a master system, you must assign a higher PROFIBUS address to the added
slave than the highest address used up to now.
● With the ET 200iSP, you can insert or remove only one module per station and download.
Adding a DP or PA Slave
1. Use the menu command View > Catalog to open the hardware catalog.
2. Drag the slave you want to add from the hardware catalog and onto the relevant CiR
object at the top of the station window.
The added slave appears at the top of the station window. The name of the slave is
displayed on an orange background to indicate that this slave was created from a CiR object.
Note
When you add a new slave, PCS 7 updates the guaranteed and the maximum number of
slaves and number of input and output bytes of the CiR object.
We recommend you select the station number of the added DP slave as follows:
Station number =
highest station number of all previously configured DP slaves + 1
If you add a type ET 200M/ET 200iSP CiR-compliant modular DP slave, this will have a CiR
module right from the start.
Note
When you add a module to an ET 200M-/ET 200iSP station, PCS 7 updates the number of
input and output bytes of the corresponding CiR module.
Result
In the following figure, you can see the configuration in HW Config view after placing a
module on the CiR module.
Note
When you download the configuration to the CPU, the INTF LED lights up and then goes
off again, the EXTF LED is lit permanently. First begin to add the real stations or modules
when the INTF LED goes out again. The EXTF LED then also goes off again.
3. Back up your current configuration every time you download the station configuration
from HW Config (regardless of the operating state of the CPU).
This is the only way to make sure that you can continue working and not lose CiR
capability if an error occurs (loss of data).
Introduction
You can reverse previous configuration changes that you have downloaded to the CPU by
removing the slaves or modules that you added.
Rules
The following rules apply when removing modules and slaves:
● Remove at most slaves or modules from a maximum of 4 master systems.
● Within a DP or PA master system, start by removing the slave with the highest
PROFIBUS address.
Then continue with the slave with the next highest PROFIBUS address.
● Within a type ET 200M/ET 200iSP modular DP slave, start by removing the module with
the highest slot number. In HW Config, this is the lowest module.
PCS 7 offers the following diagnostic features: The module to be removed next is entered
in the lower section of the station window in the standard font, all other modules are in
italics.
Then continue with the module with the next highest slot number.
Procedure
1. Select the object to be removed in the upper section of the station window.
2. Select the menu command Edit > Delete.
3. If necessary, repeat steps 1 and 2 for every other object that you want to remove.
4. Select the menu command Station > Check CiR Compatibility.
5. Download the modified configuration to the CPU.
Note
Please note the following:
• When you delete a slave, PCS 7 updates the guaranteed and the maximum number of
slaves and the number of input and output bytes of the associated CiR object.
• When you delete a module in a modular slave of the type ET 200M/ET 200iSP, PCS 7
updates the number of input and output bytes of the corresponding CiR module.
8.8.8.8 Changing the Parameter Settings for Existing Modules in ET 200M / ET 200iSP Stations
(CPU RUN)
Note
The addresses of existing modules must not be changed with CiR.
Requirements
● A CiR object exists in the DP master system to be configured.
● The number of modules to be modified is less than 100.
For details of the ET 200M-/ET 200iSP modules that can have parameters changed while
the CPU is in RUN mode, refer to the information text in the hardware catalog (text: online
configuration).
Note
in PCS 7, the input and output values have the status "BAD" after this OB 83 start.
4. Once the CPU has ended OB 83, it sends the parameter data records. Every affected
module receives all of its data records, regardless of how many data records are affected
by your change.
5. OB 83 is then started again (start event W#16#3267 if sending was successful, or
W#16#3968 if it was not successful). No other priority class is interrupted by running this
OB 83.
Note
In PCS 7, the input and output values have the status "OK" after the OB 83 start with the
start event W#16#3267.
You can only access values in the process image that belong to the process image
partition of the OB currently executing.
6. If the data records were transferred successfully, the DP master identified the modules as
available in the module status data..
If the data records were not transferred successfully, the DP master identified the
modules as unavailable in the module status data. In the second situation, an I/O access
error occurs when the module is accessed (while updating the process input image or
while transferring the process output image to the module or when accessing the module
directly. This starts OB85.)
7. The input or output data from the modules reacts as it does after a plugging-in alarm: At
the current time they are not correct because the module may not have analyzed its data
records yet. The restriction that data record SFCs must no longer be active for the
module does not, however, apply any longer.
Note
If changing the parameter assignments for a module consists of deactivating the
diagnostic alarm, for example, it is possible that the module may still send an alarm that
has already been prepared.
Note
Never save your hardware configuration at this point; otherwise the CiR download
capability will be lost.
8.8.9.1 How to Configure the Hardware for the High-Precision Time Stamps
NOTICE
Time stamps should only be used for selected signals that are of importance to the
process. They must NOT be used for every binary signal that is read.
On the other hand, it is possible for lots of signals to be signaled at the same time (for
example, when a fault occurs). This increases the risk of messages being lost due to
buffer overflow.
Introduction
If signals that trigger messages change their state in quick succession, a flurry of messages
can be triggered. This can mean that the state of a plant is no longer adequately monitored.
By configuring the "acknowledgment-triggered reporting (ATR)" function, you can suppress
the repeated signaling of "fluttering" states until an acknowledgment is received.
Procedure
1. Select the required station in the component view.
2. Double-click the "Hardware" object in the detail window.
The HW Config and hardware catalog open.
3. Select the CPU.
4. Select the menu command Edit > Object Properties....
The "Properties - ("CPU-xxx")" dialog box opens.
5. In the "Diagnostics/Clock" tab, activate the "Acknowledgment-triggered reporting of
SFB 33-35" check box in the "System Diagnostics" group.
Result
SFBs 33 to 35 then only report a change of signal if the previous change of signal (the
previous incoming message) has been acknowledged.
Introduction
Hardware configuration of the SIMATIC stations is completed.
First save and compile the hardware configuration you have created and then pass on the
information to the CPU.
Rules
Note
In some situations it is possible to download the hardware configuration during operation
(CPU in RUN). You can find a list of the configuration changes (CiR) you are allowed to
make in RUN in the section titled "Overview of the permitted configuration changes
(Page 400)".
Other configuration changes mean that the hardware configuration can only be downloaded
when the CPU is in STOP!
Requirements
● The data link from the engineering station to the automation system must be working.
● The hardware configuration of the automation systems to be loaded opens.
● The SIMATIC station is in the STOP operating state.
Procedure
1. Select the menu command Station > Save and Compile in HW Config.
Existing consistency errors are signaled to you. Click "Details" for detailed information
about the errors that have occurred.
2. Select the menu command CPU > Download to Module.
The "Select Target Modules" dialog box opens.
3. Select the target module and click "OK".
The "Select node address" dialog box opens.
4. Click the "Refresh" button.
All the nodes that can be reached are listed in the "Accessible Nodes" group.
5. Select the required node and click "OK".
The configuration is loaded into the PLC.
If the change log is activated, it opens. Enter a comment here in the "Reason" group and
click "OK".
6. On completion of the download, restart the CPU.
7. Select the menu command Station > Exit to close the hardware configuration.
Result
Your project is created, for example, with the following structure in the component view.
Requirements
● The changed hardware configuration must be complete.
● The changed hardware configuration must have been saved and compiled.
Procedure
1. Check that the current configuration can be downloaded with the menu command
Station > Check CiR Capability.
2. Select the menu command Station > Save and Compile in HW Config.
3. Download the configuration to the CPU with the menu command PLC > Download to
Module....
Note
Please note the following:
• If the configuration changes cannot be downloaded, close HW Config without saving.
This avoids inconsistencies between the configuration in the CPU and on the ES.
• When you download the configuration to the CPU, the INTF LED lights up and then
goes off again, the EXTF LED is lit permanently. You cannot start to add the real
stations or modules until the INTF LED goes out again. The EXTF LED then also goes
off again.
Recommendation
Back up your current configuration whenever you download the station configuration from
HW Config, regardless of the operating state of the CPU. This is the only way to make sure
that you can continue working and not lose CiR capability if an error occurs (loss of data).
Additional information
● Online Help for HW Config
8.8.11.3 Reaction of the CPU after Downloading Configuration Changes in CPU RUN (CiR)
Note
If a Power Off occurs while the system data is being analyzed or the CPU switches to STOP
mode, the only practical course is to run a warm restart.
Once the system data has been analyzed, the CPU starts OB 80 with event W#16#350A and
enters the duration of the analysis in its start information. This allows you, for example, to
consider this time in your cyclic interrupt OBs for control algorithms.
Note
Make sure that OB80 is always loaded on your CPU. Otherwise the CPU switches to STOP
when an OB 80 start event occurs.
system and the time per byte for a specific CPU type, refer to the technical specifications
of your CPU.
Note
CiR synchronization time:
• The CiR synchronization time calculated in this way is based on a worst-case
scenario. This means that during CiR, the actual CiR synchronization time is always
less than or equal to the calculated time.
• The CiR synchronization time of a master system is displayed in the properties
window of the CiR object in HW Config.
The following figure shows the relationship between the CiR synchronization time of a
master system and its entire I/O volume based on the example of a CPU 417-4.
CiR synchronization in ms
Total I/O
volumes in bytes
. .
.
* corresponds to the maximum address area of the MPI interface, for example
(2 K inputs + 2 K outputs)
Example Calculation
The following table is an example of a CPU 417-4 with six DP master systems.
The maximum permitted CiR synchronization time is 550 ms. This allows changes to be
made to several DP master systems, provided that the sum of the CiR synchronization times
of these master systems does not exceed 550 ms. From the last column, you can see which
DP master systems can be modified in one CiR action.
DP master Total I/O CiR Synchronization Time of the Master System Distribution of Changes to DP
system Vol. in Bytes Master Systems
1 1500 100 ms + 1500 bytes * 0.12 ms/byte = 280 ms either 1 (280 ms) or
(1 and 2) (500 ms)
2 1000 100 ms + 1000 bytes * 0.12 ms/byte = 220 ms either 2 (220 ms) or
(2 and 1) (500 ms) or
(2 and 3) (500 ms)
3 1500 100 ms + 1500 bytes * 0.12 ms/byte = 280 ms either 3 (280 ms) or
(3 and 2) (500 ms)
4 2,500 100 ms + 2500 bytes * 0.12 ms/byte = 400 ms 4 (400 ms)
5 3,000 100 ms + 3000 bytes * 0.12 ms/byte = 460 ms 5 (460 ms)
6 7,000 100 ms + 7000 bytes * 0.12 ms/byte = 940 ms Cannot be modified!
● If ET 200M stations are used with a full configuration (128 bytes for inputs, 128 bytes for
outputs, some of which may be in CiR modules), you can operate 2000/(128 + 128), i.e.
approximately 8 ET 200M stations.
● If you typically require 48 bytes per ET 200M station (e.g. 6 analog modules each with
four channels of 2 bytes or a smaller configuration with a CiR module), you can therefore
operate 2000/48, i.e. approximately 42 ET 200M stations.
If such a configuration is insufficient, you can improve the situation as follows:
● Use a more powerful CPU (CPU with a smaller time per byte - you will find more
information on this topic in the technical specifications for the CPU).
● Select several smaller master systems rather than one large master system.
● Select one or more master system is with a very large configuration and a CiR object with
no guaranteed slaves. In such master systems, only changes to parameter settings for
existing modules are possible within the framework of CiR. Select additional small master
systems in which you add or remove slaves or modules, or change the existing process
image partition assignment.
Error Displays
From the beginning of the validation until completion of the SDB evaluation, the INTF LED is
lit. It is also lit when the parameters of modules are reassigned.
On completion of the CiR action, there is a difference between the expected and actual
configuration (the expected configuration has changed because you downloaded a
configuration change to the CPU); as a result, the EXTF LED lights up. If slaves are added
when the configuration is changed, the BUS1F or BUS2F LEDs also flash. Once you have
performed the relevant hardware changes, the EXTF, BUS1F and BUS2F LEDs go out
again.
Effects on the Operating System Functions during the CiR Synchronization Time
During the CiR synchronization time, the operating system functions respond as follows:
Introduction
Networks – known as subnets in PCS 7 – are used, on the one hand, for communication
between automation systems and SIMATIC PC stations (Industrial Ethernet) and, on the
other hand, between automation systems and the distributed I/Os (PROFIBUS DP).
Overview
Creating network connections in PCS 7 involves the following topics:
● Displaying networked / non-networked stations (Page 427)
● Creating and configuring new subnets (Page 428)
● Creating and configuring a network connection to a station (Page 429)
● Changing station addresses (Page 430)
● Changing the transmission rate and operating mode in the PC network (Page 432)
● Saving the network configuration (Page 434)
● Checking the consistency of the network (Page 435)
● Cross-project Networks (Page 437)
● Configuring Redundant Networks (Page 438)
● Tips on Editing the Network Configuration (Page 439)
Procedure
1. In the component view of the SIMATIC Manager, select the project for which you want to
display the network.
2. Select the required network in the detailed window.
3. Select Edit > Open Object from the menu.
Result
NetPro opens and all the stations of the project are displayed graphically with their network
assignment.
Additional information
● Section "How to Create and Assign Parameters for the Network Attachment of a Station
(Page 429)"
● Online Help for NetPro
Note to Reader
You can create subnets while configuring the station and connect modules (more precisely:
their interfaces) to a subnet. You are already familiar with this option.
With complex networked plants it is better to work in the network view (NetPro). This is
described below.
Procedure
1. Select the station in the Component View of the SIMATIC Manager.
2. Select the menu command Options > Configure Network.
NetPro opens and the network configuration of the selected project is displayed.
3. Click "Subnets" in the "Catalog" window.
If it is not visible, open the "Catalog" Window with the menu command View > Catalog.
4. Drag the required subnet into the window for the graphical network view.
Positions which can not be used for attaching the subnet are indicated when the mouse
pointer takes on the shape of a "Forbidden" sign.
The subnet is displayed as a horizontal line.
5. Double-click the symbol of the subnet.
The "Properties" dialog box for the subnet opens.
6. Set the parameters for the subnet (for example, assign a unique name).
Tip
If you hold the mouse cursor over the icon for the subnet, a tooltip is displayed with the
properties of the subnet.
8.9.4 How to Create and Assign Parameters for the Network Connection of a Station
Requirements
● NetPro is open.
● The configured stations are visible.
Procedure
1. Use the mouse to select the interface icon of the node (small box with the same color as
the corresponding network type) and pull it toward the subnet to establish a connection.
Network connections which are not permissible (for example connecting an MPI interface
to an Ethernet type subnet), the mouse pointer takes on the shape of a "Forbidden" sign.
The network attachment is displayed as a vertical line between the station/DP slave and
subnet.
2. Select the network connection, followed by the menu command Edit > Object
Properties....
3. Make the settings for the node properties (for example, name and address of the node).
Tip
If you hold the mouse cursor over the icon for the interface, a tooltip is displayed with the
properties of the interface (name of the module, subnet type, and, if already networked, the
node address).
Node address
You specify the node address in the object properties of the Ethernet CP. The following
properties are defined:
● MAC Address
● in addition in the IP protocol:
IP address/subnet mask/address of the gateway
MAC Address
Each Ethernet module is assigned a unique MAC address. You will find the MAC address on
the module.
Please note that when using PC modules with a fixed MAC address, you must accept this
MAC address. The freely available MAC address initially recommended by the system may
differ from the address of the module.
With more recent CPUs, a check box allows you to decide if you want to set the MAC
address and use the ISO protocol. You only need to enter a MAC address if you intend to
use the ISO protocol. Otherwise, the field remains disabled; the address assigned to the CP
in the factory is then not overwritten when you download the configuration data.
IP Protocol
The IP parameters are displayed only when the current module supports the TCP/IP
protocol.
STEP 7 assigns default settings for "IP address", "Subnet mask" and the "Address of the
gateway" for the interface of the node depending on the subnet mask and gateway of the
subnet.
Enter a new IP address/subnet mask/address of the gateway if you do not want to use the
default setting.
Requirement
● NetPro is open.
● The configured stations are visible.
Procedure
1. Select the CP whose addressing you want to change.
2. Select the menu command Edit > Object Properties....
3. Select the "General" tab in the "Properties" dialog box and click "Properties".
4. Enter the MAC, IP address and if necessary the subnet mask address into the following
dialog box.
5. Click "OK".
Additional information
● Online help on NetPro (or HW Config)
8.9.6 How to Change the Transmission Rate and Operating Mode in the PC Network
Introduction
In order to guarantee communication in a network, ensure that the following parameters are
set uniformly for all the network nodes:
● Transmission rate
● Operating mode
Note
Siemens devices are set in the factory so that the parameters for the transmission rate
and the operating mode are recognized automatically ("Autonegotiation").
This setting only has to be changed if communication with nodes that do not dispose of
the Autonegotiation setting is required in the network.
Requirement
The Autonegotiation setting has to be changed because communication with nodes in the
network that do not dispose of the Autonegotiation setting is required..
Introduction
To save the network configuration and the connection tables, you can use the Network >
Save and Network > Save and Compile... menu commands.
Save
If you have created network objects in NetPro or changed their properties in NetPro, NetPro
saves the following:
● Node Addresses
● Subnet properties (for example, transmission rate)
● Connections
● Modified module parameters (for example, of CPUs)
Option What?
Compile and check The loadable system data blocks (SDBs) of the complete network
everything configuration are generated; these contain all the connections, node
addresses, subnet properties, input/output addresses and module
parameter assignments.
Compile changes only The loadable system data blocks (SDBs) of modified connections,
node addresses, subnet properties, input/output addresses or module
parameter assignments are created.
Introduction
We recommend that you check the consistency of the network prior to saving.
The following are examples of states which are displayed during the consistency check:
● Nodes that are not connected to a subnet
(exception: non-networked MPI nodes)
● Subnets with only one node
● Inconsistent connections
Alternative Procedures
A consistency check takes place during the following actions:
● Network > Check Consistency menu command
● Network > Check Consistency Project-wide menu command
● Network > Save and Compile... menu command (in the next dialog box, select the option
"Compile and check everything")
● Download to the target system (consistency check of the stations and connections to be
downloaded)
Procedure
1. Select the menu command Network > Check Consistency in NetPro.
Result
The consistency check is carried out.
Following this, the window "Outputs for consistency check for <path + project name>" opens.
If necessary, errors and warnings are displayed in this box such as those concerning
hardware-configuration, network or connection configuration.
Cross-project Networks
With PCS 7, you can configure cross-project Ethernet networks and later use these to
configure connections. Networks included in more than one project are not created in one
step. Subnets already configured in the individual projects are merged in the multiproject and
assigned to a logical "Entire Network ". The "Entire Network" represents the common
properties of all of the assigned subnets. The individual subnets of a merged network
continue to be retained.
Merged and therefore cross-project networks have the same subnet type and identical S7
subnet IDs. They are represented in NetPro by the name extension "Part of: Ethernet
Interproject".
Additional information
● Section "How to Merge Subnets from Different Projects into a Multiproject (Page 624)"
● Online Help for NetPro
Redundant Networks
Both the PROFIBUS DP field bus and the Industrial Ethernet plant bus can be configured
redundantly.
Basic Procedure
1. Use the PCS 7 wizard to create a project with a CPU 414H or CPU 417H.
A SIMATIC H station and two PROFIBUS systems are created in the project (these are
already connected to the corresponding PROFIBUS DP interface of the CPU).
2. Add a CP 443-1 to each subsystem of the H station and in HW Config and create a new
Ethernet subnet for each CP.
When you continue with the configuration, make sure that you assign other redundant
components (for example, redundant OS server) to the correct plant bus.
Result
You have created a redundant field bus and a redundant plant bus.
Additional information
● Function manual Process Control System PCS 7; Fault-tolerant Process Control Systems
Introduction
Below you will find tips on how to edit an existing network configuration.
Note
Only the communication partners of a programmable module can be highlighted.
Note
You can copy individual network objects or entire subnets with network attachments,
stations, and DP slaves. When copying, remember that all the nodes of a subnet must
have a different node address. Therefore it may be necessary for you to change the node
addresses.
Data Communication
Several automation systems are inserted into a plant section when configuring middle- and
large-size plants. The automation systems share the automation tasks and therefore must be
able to exchange data. Data communication between the automation systems and the PC
stations is also necessary.
The following sections explain how to define these communication connections and which
special features must be taken into account.
Introduction
Communication connections (connections, for short) must always be configured, when data
exchange between the automation systems or the automation system and a PC station (for
example, an OS station) is required in the user program using communication blocks.
Connection
A connection is the logical assignment of two communication partners for the purpose of
carrying out communication services (for example, the exchange of process values). A
connection specifies the following:
● The communication partners involved (for example, two SIMATIC 400 stations)
● The connection type (S7 connection, S7 connection fault-tolerant)
● Special properties such as:
– Whether a connection remains permanently configured
– Which one of the partners initializes the connection configuration
– Whether operating state messages should be transmitted
Connection Configuration
During connection configuration, a unique local identifier is assigned per connection, the
"local ID". The local ID can also be a symbolic name (named connection). This local ID is
required when assigning parameters to the communication blocks.
For each programmable module that can be the end point of a connection, there is a
separate connection table.
Special Feature
PCS 7 automatically assigns a local ID for both end points of the connection if both
communication partners are S7-400 stations or if one of the communication partners is an
S7-400 station and the other is a SIMATIC PC station.
You configure the connection only in the connection table of one partner; the other
communication partner then automatically has the matching entry in its own connection
table.
Additional information
● Section "Blocks for Different Connection Types (Page 506)"
Requirement
Two SIMATIC 400 stations have already been created.
Note
Make sure that there are no duplicate "PROFIBUS DP" or "Industrial Ethernet" node
addresses in your project (if uncertain, check with NetPro).
Procedure
1. Select the required project in the component view of the SIMATIC Manager.
2. Select the menu command Options > Configure Network.
The network view opens. The SIMATIC 400 stations, the corresponding ET 200M I/O
devices, the operator stations, and the networks existing in your projects are displayed in
the network view.
3. Select the module for which the connection is to be created in the network view, for
example, the CPU of the SIMATIC 400(1).
The connection table of the selected module is displayed in the lower part of the network
view.
4. Select an empty row in the connection table and select the menu command Insert >
New Connection....
5. Select the required connection partner in the "Insert New Connection" dialog box. Here,
select the CPU of the SIMATIC 400(2).
Note
If you create a connection to a partner in another project of the multiproject, you must
enter a connection name (reference). Based on the connection name, cross-project
connections can later be merged.
You enter the connection name in the "Properties" dialog box for the connection when
configuring the corresponding PC station (OS) (group: "Connection Identification"; field:
"Local ID").
6. Select the "S7 connection" entry from the "Type" drop-down list.
7. Activate the "Show properties before inserting" if you want to view or change the
properties of the connection after "OK" or "Add".
The content of the "Properties..." dialog box depends on the selected connection.
Result
PCS 7 enters the connection in the connection table of the local (selected) partner and
assigns the local ID (can be changed) for this connection and, if necessary, the required
partner ID you will need for programming the communication function blocks. The partner ID
is the value for the block parameter "ID".
Downloading Connections
Download the connection into the CPUs of the corresponding stations after the new
connection is configured.
1. Select the menu command Network > Save and Compile....
The "Save and Compile" dialog box opens.
2. Select from the options "Compile and check everything" and
"Compile changes only".
3. Select the CPU in one of the stations where you configured the connection.
4. Select the menu command PLC > Download in the current project > Connections and
Gateways.
All connections and gateways are downloaded.
Note
The configuration data of the partner station must also be downloaded.
Additional information
● Section "Cross-Project Connections in a Multiproject (Page 453)"
● Online help for the dialog box
Note
If several connections are configured between PC stations to one AS, these connections
must all have the same name.
Procedure
1. Select the required project in the component view of the SIMATIC Manager.
2. Select the menu command Options > Configure Network.
The network view opens. The SIMATIC 400 stations, the corresponding ET 200M I/O
devices, the operator stations, and the networks existing in your projects are displayed in
the network view.
4. To insert a new connection, select the menu command Insert > New Connection....
The "New Connection" dialog box opens.
5. Select the CPU in the "Connection partner" field that should be coupled with the OS.
Note
If you are working in a multiproject, use the multiproject folder to select the target project
and the required CPU found there.
7. Click "OK".
The "Properties - S7 Connection" dialog box opens.
Note
A connection name is entered as a default (S7 connection_1) in "Local ID:".
8. Adapt the name of the local ID to the project requirements (for example, the name of the
AS). This helps to avoid errors and maintain an overview.
You will find the connection name once again in the connection table (Named
Connection).
For compiling the OS, the corresponding S7 program can now be transferred to the OS
using this path (depending on the settings for compiling the OS).
9. Click "OK".
Note
To avoid errors and improve clarity, you should change the default connection name (S7
connection_1) to suit your project (for example, name of the AS).
Note
After the initial download of the hardware configuration from HW Config (CPU-STOP),
download the changes to the configuration only using "Compile and Download Objects"
or from within NetPro.
Go to Partner Station
Requirements:
● The project where the connection partner is located is open.
● The subnets of the participating projects are merged.
When you are editing in the connection table, then go directly to the connection table of a
connection partner as follows:
1. Select a connection in the connection table.
2. Select the menu command Edit > Go to Connection Partner.
This function is also possible for cross-project connections in the multiproject.
Note
To avoid the AS generating messages during operation when the OS simulation starts or
terminated on the engineering station, the connection ID for the engineering station should
be higher than 0xc00.
Additional information
● Section "Cross-Project Connections in a Multiproject (Page 453)"
Requirements
● NetPro is open.
● A CPU or a WinCC application is selected.
Note
The column widths and the selection of displayed columns is stored according to the specific
project after the project is closed. The project settings remain valid even the project is
opened from a different computer.
Additional information
● Online help for connection tables.
Introduction
If cross-project subnets are configured then connections can also be configured over all of
the subnets. The end points of these connections can be in different projects.
PCS 7 provides support both when creating cross-project connections within the multiproject
and when synchronizing connections configured without the multiproject context.
Note
Only the local ID of a connection can be changed without breaking the connection (changes
made directly in the table).
Fault-tolerant S7 connections cannot be broken.
If you have broken connections at both ends, you can merge them again with the menu
command Edit > Merge Connections....
You will find additional information on this topic in the Online Help for the dialog box.
Additional information
● Section "How to Merge Cross-Project Connections (Page 455)"
Requirements
The following conditions must be met in order to merge connections within a multiproject:
● The exact same connection name is used in the projects for the corresponding
connections. This name also functions as a reference.
● S7 connections to an unspecified partner can be merged to a cross-project S7 connection
only in NetPro. These connections are ignored in the SIMATIC Manager.
Procedure
1. Select the required multiproject in the SIMATIC Manager
2. Select the menu command File > Multiproject > Synchronize Projects.
The "Synchronize Projects in the Multiproject<name of the multiproject>" dialog box
opens.
3. Select the "Merge connections" entry in the left window.
4. Click "Execute".
5. If the "Result" dialog box does not indicate an error, click "Save".
Result
The connections are merged and synchronized in the multiproject.
Redundant connections
The fault-tolerant connection is a separate connection type. The following partners can
communicate over fault-tolerant connections:
● SIMATIC H station (two H-CPUs) communicates with SIMATIC H station (2 H-CPUs)
● SIMATIC PC station communicates with SIMATIC H station (2 H-CPUs)
The properties of fault-tolerant connections correspond to those of the S7 connections;
however restricted to H-CPUs and OPC servers of SIMATIC PC stations.
With a fault-tolerant S7 connection, two connection paths between the connection end points
are normally possible.
Requirements
● The hardware configuration for the two subsystems of a fault-tolerant system are
identical.
● The participating communication partners are H-CPUs or a suitably configured SIMATIC
PC station.
● For the use fault-tolerant S7 connections between a SIMATIC PC station and a fault-
tolerant automation system, the software package S7-REDCONNECT is installed on the
SIMATIC PC station.
Procedure
1. Select the CPU of an H station (H-CPU) from which you want to configure a new
connection.
2. Select the menu command Insert > New Connection....
3. Select the required connection partner in the opened "Insert New Connection" dialog box.
4. Select the "Fault-tolerant S7 connection" entry from the "Type" drop-down list.
5. The remaining steps are the same as for configuring an S7 connection.
Additional information
● Manual Process Control System PCS 7, Fault-tolerant Process Control Systems
Introduction
Define the AS functions in the plant hierarchy by inserting and programming CFC/SFC
charts after you have created the S7 programs including the chart folder in the component
view. The following table provides you with an overview of the basic steps in programming
that are described in greater detail below.
Note
If the dialog box with the "Version" tab appears automatically, this means that versioning is
active in the project properties and a change has been made in the chart. You can expect
versioning to increase in this case.
You cannot set a version number that is smaller than the last saved version.
The Object Properties of a CFC/SFC chart also include information on the software version
last used to edit the charts (PCS 7 Vx.y).
Basic Procedure
Prior to programming the CFC and SFC charts, you should decide whether the project will be
edited by more than one engineer. To allow this, branching and merging at the chart level is
possible (S7 program).
The distribution within the project is made according to technological aspects (for example,
unit with the relevant charts is copied to a different project). Existing cross-chart
interconnections are automatically replaced with textual interconnections.
On completion of editing copy the parts back into the original project. Any charts with the
same name are replaced following a prompt for confirmation. The textual interconnections
are then reestablished.
Textual interconnections that cannot be closed because a block was deleted are indicated in
a log. The interconnections can then be systematically edited by hand.
Note
Always copy the charts in the component view.
If you copy a chart in the plant view, a copy of the chart is created instead of being
replaced.
Copying a Program with Project-Wide Assignment of Message Numbers to a Project with CPU-Wide
Assignment of Message Numbers
● If you want to copy a program in which message numbers are assigned project-wide to
another project in which the message numbers were assigned CPU-wide, select the
required program in the SIMATIC Manager, followed by the menu command File > Save
As..., and activate the "With reorganization" check box. This also applies if the project
contains more than one program (more than one AS).
● Default entries are made for the message attributes when they are copied.
Copying a Program with CPU-Wide Assignment of Message Numbers to a Project with Project-Wide
Assignment of Message Numbers
You can only copy individual FBs with messages.
NOTICE
The assignment of message numbers in the programs must be uniform within a project!
If a block with messages that references a text library is copied to another program, you
must also copy the corresponding text libraries or create another text library with the same
name or change the reference in the message text.
Additional information
● Online help on STEP 7
Note
We recommend that you store all the blocks, charts, process tag types, etc. used in the
project in the master data library and then only access the master data library during
configuration. This applies in particular to objects you have copied from a library and then
modified for the project.
Note
For detailed information about the CFC Editor, refer to the Online help and the
corresponding manuals.
Block type
For every function block a type definition exists that specifies the following:
● The algorithm
● The type name
● The data interface (these are the input and output parameters)
The type definition also specifies the data types of the input and output parameters. These
input and output parameters are known as block inputs and block outputs since this is how
they appear in the graphic display of the block.
Block Instance
A block instance is created from the block type after the block type is placed into your CFC
chart.
You can create any number of block instances from a particular block type. Depending on
their individual use, separate block instances can be named, interconnected, and assigned
parameters without changing the way the specific type function.
One useful aspect of this type instance concept, for example, is that following later central
changes to the block type, these changes can be automatically made in all block instances.
Additional information
● Section "Introduction into Creating Process Tags from Process Tag Types (Multiproject)
(Page 517)"
● Manual CFC for S7; Continuous Function Chart and in the online help.
Requirement
A project structure (plant view) is created in the SIMATIC Manager which allows you to
configure CFC/SFC charts.
Note
When entering units, ensure that the following special characters are not used: [ ' ] [ $ ].
Additional information
● Online help on CFC
● Manual CFC for S7; Continuous Function Chart
● Getting Started CFC for S7; Continuous Function Chart
Introduction
The project structure is specified when you create the plant hierarchy. Here, you will find all
the CFC charts. The assignment to the plant sections is specified in the plant view.
Requirement
A project with an S7 program has been created in the SIMATIC Manager.
Procedure
1. Select the desired hierarchy folder in the plant view of the SIMATIC Manager.
2. Select the menu command Insert > Technological Objects > CFC.
A blank CFC chart with the default name is created. A new CFC chart consists of a chart
partition with 6 sheets without further chart partitions.
3. Change the name according to your requirements.
Note
The chart name may not exceed 22 characters. The name may not contain the following
characters: \ / . " %
Chart-in-chart technique
You can provide a CFC chart with I/Os so that it can be inserted into other charts and
interconnected with any blocks or CFC charts. By inserting charts into charts, you create
nested charts.
A chart without chart I/Os can also be inserted into a different CFC chart. This may be the
case if you prefer to create the chart I/Os at a later time.
Additional information
● Section "How to Define CFC Chart I/Os (Page 482)"
● Online help on CFC
● Chart-in-chart technique: Manual Process Control System PCS 7, Getting Started - Part 2
Introduction
When inserting a block, select a block type in the master data library or in the block catalog
and then place it into the CFC chart. The block will then be assigned a name that is unique
within the chart. The block that is inserted is an instance of the block type. You can create
any number of block instances from each block type.
Note
The comment of the block type is not included in the block instance.
Procedure
1. Select the CFC chart in the SIMATIC Manager.
2. Select the menu command Edit > Open Object.
The CFC chart opens in the CFC editor. A new CFC chart consists of a chart partition
with 6 sheets without further chart partitions.
3. Select the "Libraries" tab in the block catalog.
Here, you will also see the master data library.
4. Select the block type you want to insert from the master data library and drag into the
chart.
An instance of the block type is created in the CFC chart.
5. Insert further blocks into the CFC chart in the same way.
The runtime properties of a block are predefined. If necessary, you can change the runtime
properties: You can find additional information about this in section "Runtime Groups and
Runtime Properties (Page 473)".
Tab Description
Blocks Here the blocks are sorted according to block families. You also find the
blocks which are in use, below the name of the S7 program.
Charts Here you will find all the charts that you have created in the chart folder of
the S7 program. A small open folder icon is used to symbolize the chart
which is open in the CFC Editor.
Libraries Here you will normally find all the libraries provided by PCS 7 along with
your master data library. Hide all the libraries that you do not need for
project engineering by using the ""Hide" function (see Section "Using
Libraries (Page 317)"). The master data library is always displayed.
Additional information
● Online help on CFC
Block I/Os
Each block has a number of different I/Os.
The I/Os of a block can be "visible" or "invisible": You can only see any "invisible"
parameters in the properties of the block but not in the representation in the CFC chart.
Use the properties of the block to specify which I/Os in the CFC chart will remain visible or
hidden. If connections interconnected to a block are switched invisible, this is indicated by a
small triangle in the block header.
Procedure
1. Select the block in the CFC chart and then select the menu command Edit > Object
Properties....
The "Properties - Block" dialog box opens, and the "General" tab is active.
2. Enter a unique name for the block instance in the "Name" box. The names of block
instances must be unique in a CFC chart.
Note
The maximum length of a block name is 16 characters (for nested charts 22 characters).
The name may not contain the following characters: \ / . " %
Note
If you change units or operator texts, these are no longer taken into account during block
type importing.
8. Click on the input of the block with which you want to interconnect the output.
The CFC editor automatically creates a line indicating the interconnection.
Note
Steps 7 and 8 can be carried out in reverse sequence.
You can create further interconnections in the shortcut menu if the I/O is selected:
• Interconnection to Address...
• Interconnection to a Runtime Group... (only for data type BOOL)
9. Make the other parameters settings and create the interconnections in the same way.
Note
Select a connection line to facilitate follow-up. The line blinks in a different color in both
the chart and in the chart overview.
Click on the chart to stop the blinking.
Additional information
● Online help on CFC
● Interconnecting with Process Pictures: Manual Process Control System PCS 7, Getting
Started - Part 2
● Archive tags: Configuration manual Process Control System PCS 7; Operator Station
Introduction
This section describes some of the basics required to understand the runtime properties of
blocks.
Runtime properties
The runtime properties of a block decide how the block is included in the run sequence
within the entire structure of the CPU. These properties are decisive for the response of the
target system in terms of reaction times, dead times, or the stability of time-dependent
structures, for example, closed loops.
The runtime properties of the blocks have default settings but these can be adapted
individually for each block.
When it is inserted, each block is assigned default runtime properties. It is therefore installed
in a run sequence in a task (OB). The tasks form the interface between the operating system
of the CPU and the S7 program. Blocks can also be installed in runtime groups that are
themselves installed in tasks (OBs).
Note
When you create new chart, a runtime group is created automatically in which all the blocks
of this chart will be installed.
Runtime groups
Runtime groups are used to structure tasks (OBs). The blocks are installed in sequential
order in the runtime groups. Runtime groups allow the blocks of a CFC chart to be handled
individually.
You can do the following with runtime groups:
● Switching selected blocks within an OB off and then on again
If a runtime group is deactivated, the blocks it contains are no longer passed through.
Runtime groups are activated or deactivated using a block output of the data type
"BOOL".
● Process selected blocks with a specific reduction ratio (after a specified number of cycles
and/or with a phase offset) to achieve better load distribution on the CPU.
● If OBs contain a large number of installed blocks, these can be put together in smaller
units.
Advantage: Instead of creating one "large" FC when you compile each OB, "smaller" FCs
are created depending on the number of runtime groups.
If the program is modified later, only the runtime groups/FCs that actually contain
modified blocks are given the "modified ID".
In this way later compilations and online downloads to make changes can be executed in
shorter time.
Note
For the reasons listed above, make sure that you do not install too many blocks in an OB
or in a runtime group. Only this will lead to a noticeable improvement in performance
when you compile or download changes in comparison to compiling and downloading the
entire program.
You must also take into account the startup OB (OB 100), the error OBs (OB 8x) and any
special OBs you may use.
Insert Point
When you insert a block, the insert point of the block in the run sequence is fixed.
The default rule is as follows: he block is inserted after the block displayed in the status bar
of the CFC.
The following is displayed in the status bar (alternative):
● When you first create a chart, the default of the specific PLC
● The last new block to be inserted (color marking: black text on a light gray background)
● The block specified by the run sequence
The current insert point is displayed to the right in the status bar. It displays the task name
(OBx), the chart and block name after which the next block will be installed in the run
sequence when a block is inserted in the CFC chart.
Additional information
● Online help on CFC
Additional information
● Online help on CFC
Note
When you insert blocks in the CFC chart, they are automatically installed in the run
sequence.
Procedure
1. Start optimization in the the run sequence editor via the menu command Options >
Optimize Run Sequence...,
or - for selected tasks or runtime groups - in the shortcut menu via the menu command
Optimize Groups/Tasks....
With this function, you can optimize the run sequence of a program based on the data flow.
This keeps the dead time to a minimum while the sequence is running in the CPU.
Optimizing is carried out separately for tasks and runtime groups.
Rules
● The content of runtime groups, created by the driver generator ("Generate Module
Drivers" @......) are not optimized since the correct order is already set here.
● If optimization is executed after creating the module drivers, there is no guarantee that
the runtime groups of the driver blocks are in the order specified by the driver generator.
Therefore the module driver is restarted during the next compilation (the "Create module
driver" check box is activated).
NOTICE
If blocks are interconnected over INOUT parameters, the data flow may be reversed (from
input to output). This is not taken into consideration when optimizing the run sequence.
Remedy: in this case, you must optimize the order yourself and exclude the relevant
runtime group from the optimization.
NOTICE
During cascaded interconnections and other connections with several return jumps,
deactivate runtime group optimization at the runtime group.
Introduction
When you insert blocks in the chart, they are automatically installed in the run sequence.
The installation position is decided by the "Predecessor for Installation". Certain blocks are
also installed more than once in tasks depending on the entry in the task list assigned to the
block type by the system attribute (S7_tasklist). Blocks with startup characteristics are, for
example, also installed in OB100.
You can see the other tasks in which the block is also installed in the dialog box of the
properties, under the "To be installed in OBs/tasks" group in the "General" tab.
Procedure
1. Start the run sequence editor in the CFC editor with the menu command Edit > Open Run
Sequence.
Here, you can make the following adaptations:
– Move objects (SFC chart, runtime group or block)
– Removing a Block
– Installing Blocks
– Setting Installation Pointers
Moving Objects
You move can object by selecting it (SFC chart, runtime group, or block) in the right or left
window and then dragging it with drag-and-drop to the object after which you want to install
it.
The following takes place after an object is dropped onto a runtime group:
● The object is installed at the first position within the runtime group when the structure is
expanded [-].
● The object is installed after the runtime group if the structure is not expanded [+].
● If the runtime group is empty, you will be asked whether or not you want to install the
block within the runtime group. If you answer with "yes," it is installed inside the runtime
group, if you answer with "no" it is installed after the runtime group.
If you drag an object to a task, it is installed before the objects already installed.
Note
Ensure when moving blocks that all the blocks of a chart are located exclusively in the
corresponding runtime group. After moving a block to another group, the chart-oriented
structure no longer exists and would make it difficult or even impossible to work on a chart-
by-chart basis in multiuser engineering.
Removing a Block
You can only remove (delete) blocks from a task if it is installed more than once in the run
sequence. At least one insert point must remain.
If this was the only block installed, it will not be deleted. Otherwise, the block is deleted and
the run sequence of the blocks following it are adapted.
Installing Blocks
You can also install blocks, runtime groups, or SFC charts more than once by copying and
pasting. Use the following functions for this purpose:
● The corresponding menu commands
● The toolbar icons
● With drag-and-drop with the <Ctrl> key pressed
● While displaying the CFC chart, drag from a CFC chart to the required place in the run
sequence.
Note
Objects with the system identifier "@" are automatically installed in the run sequence
while the module drivers are created. They may only be edited in the SIMATIC Manager
with the menu command Options > Charts > Generate Module Drivers.... Do not delete or
move these objects manually.
Additional information
● Online help on CFC
Introduction
A chart can be supplied with I/Os in order to enable the following additional uses:
● Inserting into a different chart and interconnecting with other charts or blocks (chart-in-
chart technique).
● Compiling as a block type
There are two different procedures for creating chart I/Os:
● Create unassigned chart I/Os followed by interconnecting
● Create the chart I/Os with the interconnection
Note
If you use this method, the attributes (for example, S7_m_c) of the block I/O are not
adopted. You must then assign the attributes to the chart I/Os yourself.
4. Use drag-and-drop to drag a block/chart I/O to a chart I/Os with a compatible data type.
As an alternative with existing chart I/Os,
assign the I/Os of the blocks placed in the chart and/or nested charts to the existing chart
I/Os without needing to open the chart inputs/outputs dialog.
1. mark the I/O and select the menu command Insert > Interconnection to Chart I/O....
A dialog box opens containing a list of all the available I/Os for the relevant I/O type.
2. Select the required chart I/O and click "OK".
Note
You can only assign unconnected I/Os with a compatible data type.
Note
If an I/O that is interconnected with the chart interface is hidden, there is no sheet bar entry.
The interconnection can then only be recognized by the object properties of the block ("I/Os"
tab, "Interconnection" column).
Additional information
● Online help on CFC
Introduction
CFC charts must be compiled into a code that the CPU of the AS can understand. Since
compilation always includes all the charts of an S7 program, you should only start at the end
of the compilation.
Procedure
1. Select the menu command Options> Customize> Compile/Download... in the CFC Editor.
2. Define the settings for compilation.
You will find additional information on this topic in Section "Settings for Compilation".
3. Select the menu command Chart > Compile > Charts as Programs....
The "Compile Program" dialog box opens.
4. Activate the following check boxes if necessary:
– Generating module drivers
(for additional information please refer to the Online help)
– Generating SCL source
Note
If you do not want to use the blocks of the current PCS 7 Library, you can use the
"Module Driver Settings" command button to open a dialog box in which you can
select the desired drive library.
5. Click "OK".
Note
If you only work with CFC and SFC in your program, you can leave the standard compilation
settings unchanged.
You will find an overview of the blocks generated during compilation in the online help.
Note
Central compiling and downloading of all objects can be executed in the SIMATIC Manager
with the menu command PLC > Compile and Download Objects.... This dialog box lists all
the objects of the multiproject that can be compiled or downloaded.
The hardware configuration must be downloaded to the CPU before this function can work
(initial commissioning of the automation system).
You can find information about this in the section "How to Download to All CPUs
(Page 668)".
Additional information
● Section "How to Download CFC Charts to the CPU (Page 488)"
● Section "Downloading to All CPUs (Page 668)"
● Online help on CFC
Introduction
During configuration, testing and commissioning, there is often the need to compare a
new/changed CFC chart with the previously loaded version before downloading it.
Requirement
Before the initial download in the CFC editor with the menu command Options > Settings >
Compile/Download..., activate the check box "Generate image of downloaded program for
comparison" in the "Settings for Compiling/Downloading" dialog box.
Procedure
1. In the CFC editor, select the menu command PLC > Download....
2. Click "Show Changes".
The Version Cross Manager opens and the image created by the previous download (see
section "Requirements") is compared with the version to be downloaded and
correspondingly displayed.
Note
The "Show Changes" button is only enabled when the "Version Cross Manager" add-on
package is installed and an image has been generated for the loaded program.
Additional information
● Online help on CFC
Introduction
After compiling the charts, download them to the CPU and view the process rate in test
mode afterwards.
The program is downloaded to the CPU assigned to the active chart.
Requirement
There must be a connection between the CPU and your programming device/PC.
Procedure
1. Select the menu command PLC > Download....
The "Download PLC" dialog box opens in which you can determine the type of download.
2. Select the scope of the download:
– Entire program
The entire content of the "Block" folder is downloaded and, following a prompt, the
CPU is set to STOP.
– Changes
The CPU can be in the "RUN-P" mode. The download of the modified blocks is as
safe as possible (bumpless) to avoid the CPU changing to "STOP".
– In test CPU (entire program)
With this type of download, you can download a modified program to another CPU or
to an S7 PLCSIM, without losing the delta download capability in the original CPU.
Note
The possibility of the CPU going into STOP mode cannot be completely eliminated.
The reasons for this include temporary inconsistencies that cannot be checked by the
loader (for example, local requirements of blocks that do not include reference lists).
3. Click "OK".
If download-relevant changes have been made to the user program, a message is
displayed indicating that the program must first be compiled and you are asked whether
you want to compile and then download.
Note
Downloading from the CFC to the PLC must take place from the programs created in
CFC. Only this download function guarantees that the configuration data will be
consistent with the CPU data.
The same download function is available in the SIMATIC Manager with the following
menu commands:
• Menu command PLC > Compile and Download Objects... and then activate the
"Charts" object for compiling and downloading
• In the component view: mark the "Charts" folder and select the menu command PLC >
Download
Additional information
● Section "How to Compile CFC Charts (Page 485)"
● Section "Downloading to All CPUs (Page 668)"
● Online help on CFC
Test mode
CFC Editor provides test functions that support the commissioning process. These are used
to monitor and influence the AS sequential control system process and to change setpoints if
necessary. For this purpose switch the CFC Editor into a test mode.
Requirements
● There must be a connection between the CPU and your PC.
● The program has been downloaded.
Troubleshooting
From within the CFC chart, you can open the block type associated with the block instance.
Mark the required block in the CFC and select the menu command Edit > Go To > Block
Type.
If the source file of the block is included in the project, the tool used to create it
(LAD/FBD/STL or SCL) opens and the block type can be edited.
If the source file is not in the project, LAD/FBD/STL is still open. You can then only read the
block information (exception: the system attributes of the I/Os can be edited).
If a SFC instance is marked in the CFC chart, this is opened in the SFC Editor (the
corresponding SFC type can be opened in the SIMATIC Manager or in the SFC Editor).
Additional information
● Online help on CFC
● Manual Process Control System PCS 7, Getting Started - Part 1
● Manual CFC for S7; Continuous Function Chart
NOTICE
Up to 128 parameters can be used for forcing.
Note
If you activate forcing at the chart folder, the program will need to be recompiled and
downloaded (compilation of the entire program).
Note
All force settings will be lost if a CPU cold restart is performed while forcing is activated.
However, the settings will be retained in the offline program. To restore consistency between
the offline and online programs within this context, disable "Support forcing" at the chart
folder, compile and download the data, re-enable "Support forcing" at the chart folder and
then recompile and download the data.
Procedure
The use of these attributes is enabled by means of corresponding options in the component
view of the SIMATIC Manager.
In the object properties of the chart folder, select the "Advanced" tab and activate the
"Support forcing" check box. This will enable the Force function.
Once it has been enabled, you have two ways of forcing values:
● In the CFC Editor
In the object properties of the block input, activate the required options:
– "Add forcing" (check box)
This enables forcing at this input.
This option cannot be changed in test mode.
Each change requires the program to be compiled and downloaded again.
– "Forcing active" (check box)
This permanently replaces the value of the interconnection with the force value.
The value of the interconnection becomes active again when forcing is disabled.
A change in test mode does not require recompilation to take place.
– "Force value" (input field)
Enter a value here that is to be applied to the block input if the options "Add forcing"
and "Forcing active" are enabled.
A change in test mode does not require recompilation to take place.
You can make the settings for more than one block input in the CFC. The
corresponding columns for the force function are available in the "I/Os" tab of the
block object properties.
● In the process object view
In the process object view, you can make the settings for the desired inputs for all blocks
in the project. The corresponding columns for the force function are available in the
"Parameters" and "Signals" tabs. The procedure is the same as with the CFC Editor.
Representation
The interconnection of the forced input is identified in the CFC chart by means of a colored
rectangle at the block input:
● A green rectangle means: "Add forcing" is activated
● A red rectangle means: "Add forcing" and "Forcing active" are activated
Note
Colored rectangles are only visible for interconnection, as forcing is only possible for
interconnected parameters.
In test mode, the force value is distinguished from the other dynamic values by a different
background color. The default setting is "light blue" and can be changed in the "Color
Settings" (Options > Settings > Colors...).
The background color of the force value is identical to the representation in the chart.
Additional information
● Online help on CFC
Trend display
The trend display is a tool in the CFC editor that allows you to track the values of one or
more signals on a CPU qualitatively over time. The trend display shows the signal
continuously over time while it is being recorded. The trend display works with any target
system that supports normal online operation.
Requirement
The test mode in the CFC Editor is activated for the current CPU.
Procedure
1. Open the trend display window for the desired CPU with the menu command View >
Trend Display.
2. In the trend display group, click the "Rename" button and enter the desired name for the
trend display.
3. Enter the number of measuring points for the time axis in the "Display" group.
4. In the "Recording" group, click the "Change" button and enter the current operating mode
for the trend display and the abort conditions.
5. Click "Apply".
6. Open the CFC chart whose values you wish to display.
7. At the function block level, select the I/O name whose value you wish to display.
8. Select the menu command Test > I/Os > Insert In Trend Display.
The Trend Display window opens.
9. Select the desired channel in the "Select Channel" dialog box and click "OK".
10.Open the Trend Display window. Enter the desired high and low limits here and then click
"Apply".
11.Keep repeating steps 6 to 10 until you have finished inserting all the values you want to
display into the trend display.
12.Click "Start" in the trend display.
The selected values will start to be displayed.
Additional information
● Online help on CFC
AS runtime measurement
To avoid runtime errors in new and modified configurations, we recommend that you monitor
the execution time of the OBs. In the configuration described below, the warning limits can
be set to any value. You can signal the warning limits over the PCS 7 OS.
The runtime is measured with the TIME_BEG and TIME_END blocks (subsequently referred
to as block pair). In addition, you will require the MEAS_MON block for the warning limits.
WARNING
Please note the following warnings:
• All work on the process control system must be performed by trained service personnel.
• Always observe the plant-specific rules and government regulations when making
changes to your system.
• Observe the plant-specific boundary conditions and adjust the work accordingly.
• Always bear in mind that changes in a system can impact other sections of the system.
Procedure
1. Create a new chart in CFC (runtime monitoring ASNo x).
2. Place a block pair in this chart - for in each cyclic interrupt OB.
To view the cyclic interrupt OBs, select the menu command Edit > Open Run Sequence.
3. Connect the "TM" I/Os of a block pair.
Assigning blocks to cyclic interrupt OBs
1. Select a TIME_xxx block.
2. Select the menu command Edit > Open Run Sequence.
The "Run Sequence Editor" dialog box opens.
The selected block is highlighted in the tree view. The other block pairs can also be found
in this OB.
Move a pair of blocks into each of the cyclic interrupt OBs.
3. Place the TIME_BEG block as the first block in the cyclic interrupt OB.
4. Place the TIME_END block as the last block in the cyclic interrupt OB.
5. Place the MEAS_MON block and interconnect it if you also require warning limits.
6. Repeat step 3 through 5 for all blocks of the type TIME_BEG and TIME_END.
Notes on Troubleshooting
You can reduce the execution time of an OB by installing the runtime groups with reduction
ratios and phase offsets, or starting blocks in other OBs.
If it is possible to increase the cycle monitoring time, then it can be carried out in HW Config
(Properties of the CPU, "Cycle/Clock Memory" tab).
If there is a CPU stop due to failure of I/O components, the use of the SUBNET block can
help. When an error OB (for example, OB 86, rack failure) occurs, the SUBNET block allows
only the driver blocks that signaled the error to execute their routine. This reduces the
execution time necessary.
Additional information
● Online help on CFC
● Direct help on the blocks: click the "?" symbol in CFC and then the block header.
Introduction
The following section describes how to configure the automatic displaying and hiding of
messages in process mode.
Requirement
● Configuring of the technological functions in CFC and SFC is completed.
● The block groups of the plant parts whose messages you want to hide are specified.
Procedure
1. Insert the "STATEREP" block into a CFC chart from the PCS 7 library.
2. Connect the control signals from a process status logic that was created beforehand to
the Status inputs (State 1 to max. State 32).
3. Open the plant view in the SIMATIC Manager.
4. Double-click the "Shared Declaration" folder.
5. Double-click the "Listings" folder.
6. Select the "Operating State" folder.
7. In the pop-up menu select the Insert New Object > Value menu command and enter an
object name that represents the state.
Repeat the process for all states (state 1 to max, state 31).
8. Select the object name.
9. Select the Edit > Object Properties menu command and assign values to the individual
states beginning with 1 (please do not use 0).
10.Open the process object view in the SIMATIC Manager.
11.Select the "Blocks" tab.
12.Enter a name for the "STATEREP" block in the "Block group" column.
Note
The name of a block group must be unique throughout the multiproject.
The names of the block groups must differ from the names that were assigned as the OS
area identifier.
13.Assign this name to all the blocks that are to belong to this group.
14.Now select the "Messages" tab.
15.Select the "Block group" entry from the "Filter by column:" drop-down list.
16.Enter the name of the block group in the "Display" input box.
17.Assign a status (Status 1 to Status 32) to all the messages of the displayed block group
that you want to hide. The corresponding column names are replaced by the previous
defining of the "Operating state".
Result
The signal assigned to a status input controls the displaying and hiding of all the messages
that are assigned to this status.
Introduction
In SIMATIC Manager you can call a function that identifies all objects configured and
requiring a PCS 7 license. The result is displayed per license type in the "PCS 7 License
Information" dialog box. This allows you to check whether existing PCS 7 licenses or the
licenses you intend to order are sufficient for your project or how many objects requiring a
license you can still add to your project.
In the left-hand box, all components installed which require a PCS 7 license are displayed.
In the right-hand box the accompanying configured license objects are displayed.
PCS 7 components
The PCS 7 component list is determined by the installation. Multiprojects, projects and
stations are displayed in the "Configured license objects" box.
The following are displayed in the "Select the desired license:" box:
● Process objects (only relevant for CFC in PCS 7)
Countable process objects (PO) may be classed as any SFCs and block instances that
support reporting, as well as operator control and monitoring. These are the objects that
are transferred to the OS and require licenses. Driver blocks are not classed as POs.
These objects are only entered in the count if they can be downloaded to an AS. Block
instances in S7 programs without hardware assignment (at the project level or in libraries)
are not considered.
● Diagnosis objects (maintenance RT)
Multiprojects or subprojects are displayed. The square bracket [...] contains the number
of project licenses. On the next level, AS objects with subordinate ASs, then PC stations,
network objects and user objects are displayed.
● Process objects in WinCC
For each sub or multiproject one or more OSs are displayed, the configured license is in
square brackets [...] after it. OS servers, OS server standby and reference OS servers
can be displayed.
● Archive tags
One or more OSs are displayed for each sub or multiproject. If an archive server is
available, this is also displayed. On the next level, those OSs which store data on this
archive server are listed. The number of archive tags is displayed in square brackets [...]
on the affected objects, differentiating between short-term and long-term archiving.
Additional information
● You will find additional information on this topic in Section "Counting and booking process
object licenses (Page 503)".
Introduction
Countable process objects (PO) may be classed as any SFCs and block instances that
support operator control and monitoring and have the "With interrupt" property. These are
the objects that get transferred to the OS during the compile and download operation and
which require a license.
Driver blocks are not classed as process objects.
You can start a function in the SIMATIC Manager that identifies all of the process objects
configured and booked in the Automation License Manager (ALM). The result is displayed in
the "PCS 7 license information" dialog box. This allows you to check whether the existing
"SIMATIC PCS 7 AS RT PO" license or the license you intend to order is adequate for your
project and the number of process objects you can still add to your project.
Sequence
The compile and download operation involves detecting the process objects within the
program, and the CPU and memory card serial numbers. Aided by this number, a program is
assigned to the CPU. A process object info is created in the ES data management for each
CPU that is downloaded; this records identifiers and the number of process object licenses
used.
During the download process, the system determines if process object licenses have already
been used for the current CPU (and if so how many). The number of process objects that
were identified during the last download is read from the process object info that was created
in the ES data management. The difference between this and the current number identified
is then compared to the number of licenses available in the Automation License Manager
(ALM). If the required process objects are covered by the license, the difference is booked in
the ALM and the download is executed.
If the current program contains fewer process objects than the one previously downloaded,
the number of available process object licenses is increased again by the download process.
If not enough licenses are available the license violation will generate a corresponding
message that must be acknowledged. Now you may either terminate the download or
continue it in spite of this message. The number of licenses that are required but unavailable
will be recorded as a shortage. If you have purchased additional licenses, these missing
licenses are included and registered in the ALM at the next download.
Note
Before removing the CPU, if there is an existing connection between the ES and the
CPU, you will first need to book back the process objects on the CPU.
Note
No process objects are booked back within this context.
Therefore, you should book back the process objects prior to deletion.
Note
It is particularly important to book back licenses if plant engineering is being performed at
different locations, but the process object licenses are required for the target plant.
Additional information
● Section "How many objects can be handled in a project? (Page 61)"
Introduction
Process objects are only entered in the count if they can be downloaded to an AS. Block
instances in S7 programs without hardware assignment (at the project level or in libraries)
are not considered.
Procedure
1. Select either the multiproject or project in the SIMATIC Manager (any view).
2. Select the Options >PCS 7 license information menu command.
The "PCS 7 license information" dialog box opens.
Additional information
● Online help for the "PCS 7 license information" dialog box
Introduction
You have already configured the connections in NetPro. During the configuration, you
decided which AS will exchange data with which AS (AS-AS communication).
The values that you want to send via the connections created in NetPro must now be
interconnected with the blocks installed in the CFC charts for sending and receiving the
values. The communication blocks required to this purpose are supplied with PCS 7.
Introduction
The following table shows you an overview of the communication blocks available in PCS 7
for AS-AS communication (S7 connection). These blocks are located in the CFC in the
PCS 7 Standard Library (call: PCS 7 Library Vxy > Blocks+Templates\Blocks > COMM).
SEND_BO
The SEND_BO block sends up to 128 BOOL values via an Industrial Ethernet connection to
another S7 CPU, which must then call the function block type "REC_BO" (FB 208) of the
PCS 7 Library to receive the data.
The consistent data are available in REC_BO only on completion of the job (after arrival of
the DONE = TRUE acknowledgment). The acknowledgment can be detected on the CIW
output by a signal change to 0.
By applying the value 1 to the FAST parameter, the FB allows the sending of a frame per
function block call. This fast send job sequence is only practical when the frame can be
transmitted in the time available between two FB calls.
REC_BO
The REC_BO block receives 128 BOOL values via an Industrial Ethernet connections from
another CPU, which must then call the function block type "SEND_BO" in the PCS 7 Library
(FB 207) to send the data. In STEP 7, a homogeneous transport connection must be set up
for this purpose and transferred to the automation system.
The data are available only on completion of the job when the signal at output NDR changes
from 0 to 1.
SEND_R
The SEND_R block sends up to 32 BOOL and 32 REAL change driven values over an
Industrial Ethernet connection to another CPU that must then call the function block type
"REC_R" (FB210) of the library PCS 7 Library to receive the data.
The consistent data are available in REC_R only on completion of the job (after arrival of the
DONE = TRUE acknowledgment). The acknowledgment can be detected on the CIW output
by a signal change to 0.
By applying the value 1 to the FAST parameter, the FB allows the sending of a frame per
function block call. This fast send job sequence is only practical when the frame can be
transmitted in the time available between two FB calls.
REC_R
The REC_R block receives 32 BOOL and 32 REAL values over an Industrial Ethernet
connection from another CPU that must then call the function block type "SEND_R" in the
PCS 7 Library (FB 209) to send the data. In STEP 7, a homogeneous transport connection
must be set up for this purpose and transferred to the automation system.
The data are available only on completion of the job when the signal at output NDR changes
from 0 to 1.
Introduction
You have configured the connection in NetPro. You have defined that communication should
take place between two communication partners.
During CFC configuration and in this case you must still place the corresponding
communication blocks in a CFC chart and assign the following parameters:
● Connection ID that you have assigned in NetPro
● Frame identifier R_ID
● Data that should be transmitted
Connection ID
A connection is identified by its ID (connection identifier).
Several frames can be exchanged on one connection and they are identified by the R_ID
(frame identifier).
The ID establishes the connection between the hardware (logical connection on the CP) and
the software (FB). Since several jobs (SEND/REC block pairs) can be handled on one
connection, the R_ID is used for identification.
A block pair (send, receive) must exist in the CFC chart for each frame that is transferred
over a connection. Therefore you must configure a send block in the sending CPU and a
receive block in the receiving CPU.
$6 $6
6(1'B%2 5(&B%2
/RFDO,' 5HPRWH,'
5B,' )% )% 5B,'
5(&B5 6(1'B5
5B,' )% )% 5B,'
6FRQQHFWLRQ
ಯSLSHಯ
6(1'B5 5(&B5
5B,' )% )% 5B,'
Requirement
The connection between the automation systems involved is configured in NetPro.
Basic Procedure
1. Create a CFC chart in the sending CPU with a send block (SEND_BO).
2. Assign parameters and interconnect the block (ID, R_ID, BO_00 ... BO_127, etc.).
3. Create a CFC chart in the receiving CPU with a receive block (REC_BO).
4. Assign parameters and interconnect the block (ID, R_ID, RD_BO_00 ... RD_BO_127 etc.).
5. Follow the same procedure for each S7 connection you want to configure.
6. Compile, download, and if necessary, test the configuration.
Follow the same procedure if you use the SEND_R and REC_R block pair.
Additional information
● Online help on CFC
● Direct help on the blocks: click the "?" symbol in CFC and then the block header.
Introduction
The I/O interfacing described below also ensures high performance for capacity. The
configuration is fast and easy to execute.
Concept
The concept of the driver and diagnostic blocks for PCS 7 can be characterized as follows:
● The separation of user data processing (channel block) and diagnostic data processing
(module block)
● The symbolic addressing of the I/O signals
● The automatic generation of the MODULE blocks by CFC
This block concept supports all modules from the list of approved modules.
If own and external new module types are included, the meta-knowledge for the driver
generators can be extended by additional XML files (object and action lists). Creating these
files is described in the manual Process Control System PCS 7 Programming Guide Driver
Blocks.
Note
Please note the following:
• The library with the driver blocks have to installed using the Setup program on the PC.
This is the only method of ensuring that the meta-knowledge required for the driver
generator is available. You may not copy the library from another computer.
• You can also use driver blocks from another library (for example own blocks from an own
library). You can specify this additional library in the "Generate Driver Blocks" dialog box.
The driver generator then searches for the block to be imported in the library specified
here. If the block is not found here, it is searched for in the library specified in the control
file (XML file).
• If the S7 program contains a signal-processing block (CH_xx, CH_U_xx, PA_xx), but this
is not from one PCS 7 libraries, you have to specify the version of the driver library from
which the driver blocks are to be imported in the "Generate Module Drivers" dialog box.
Time-Optimized Processing
To allow time-optimized processing during runtime, the organization blocks for error handling
(for example, OB85, OB86, etc.) are automatically divided into runtime groups and the driver
blocks installed in the relevant runtime groups.
If an error or fault occurs, the SUBNET block, for example, activates the relevant runtime
group, the RACK block or module block contained in the runtime group detects the problem,
evaluates it and outputs a control system message to the OS.
The diagnostic information of the module block is also transferred (output OMODE_xx) to the
corresponding CHANNEL block (input MODE). If necessary, this information can be
displayed in a process picture (color of the measured value changes or flashing display, etc.)
by a PCS 7 block that can be operated and monitored on the OS or by a user block.
Introduction
The blocks for signal preprocessing listed under "Driver Blocks" must be inserted by the user
and interconnected to the module. The "Generate Module Driver" function is used to
configure these and interconnect them to the diagnostic blocks.
Additional information
● Online help of the corresponding blocks (CFC)
Procedure
1. Open the SIMATIC Manager and the project in which you want to generate the drivers.
2. Select the chart folder of a S7 program in the component view. No charts may be
selected in this folder.
3. Select the menu command Options > Charts > Generate Module Drivers....
As an alternative, you can activate the "Generate Module Drivers" check box in the
"Charts as Program..." dialog box in CFC when compiling CFC/SFC charts.
Each time you recompile, only the required module drivers will be generated or updated.
4. Select the required options and click "OK"K
Note
If the address areas for digital input and output modules have been packed in HW Config
("Pack Address"), the driver generator cannot supply unique addresses to the
corresponding blocks.
The addresses may not be packed in order to have a defined slot assignment for each for
each module.
NOTICE
No changes are allowed to the system charts since these involve system functions
(indicated by "@"). This also applies to changes to the installation in OBs or runtime
groups.
Additional information
● Section "How to Configure the Distributed I/O (Page 382)"
Drivers for Peripheral Devices or I/O Modules not Integrated for Use in PCS 7
The driver concept covers the I/O devices and I/O modules currently released for use in
PCS 7. You will find the released I/O devices and I/O modules in the document "PCS 7 -
Released Modules.pdf" on the Toolset DVD Process Control System; PCS 7-Software
Toolset".
Procedure
If you want to connect other peripheral devices or I/O modules to the AS in a fixed
configuration, you can create the driver blocks yourself using the driver concept (one block
per device with user data and diagnostic data processing).
You then store the driver blocks you have created in the master data library. You can use
these in the same way as the supplied driver blocks (signal-proceessing blocks and
diagnostics blocks).
8.11.7.1 Introduction into Creating Process Tags from Process Tag Types (Multiproject)
Introduction
Use the wizard for process tag types to copy the process tag type from the master data
library to the specified destination project. There it is inserted as a process tag. Then the
associated data is imported from an import file.
Depending on the entries in the import file, you can create any number of process tags in
one import action. As a result of the import, a process tag of this process tag type is created
in the target project for every row of the import file according to the specified hierarchy path.
Overview
Creating process tags from process tag types and subsequent editing of the tags involves
the following topics:
● Creating a Process Tag Type from a CFC Chart (Page 518)
● Changing a Process Tag Type (Page 520)
● Inserting a Process Tag into the Project (Page 522)
● Creating Numerous Process Tags Automatically (Page 525)
● Editing a Process Tag (Page 526)
● Adapting a Process Tag (Page 527)
● Adapting a Process Tag to a Process Tag Type (Page 529)
● Restoring Lost Process Tag Type Assignments (Page 531)
Requirement
A CFC chart has been created in the project or in the master data library that contains the
automation functions, parameters, and messages of the process tag to be implemented
according to a specified process tag description.
Procedure
1. Select the intended CFC chart in the SIMATIC Manager (any view).
2. Select the menu command Options > Process Tags > Create/Modify Process Tag Type...
.The wizard is started and displayed with the "Introduction" page. The current master data
library is displayed.
3. Click "Continue".
The wizard changes to the "Which I/Os do you want to assign to the process tag type?"
page.
4. In the left window "I/Os in the chart of the process tag type", select the flagged I/O for
"Parameter" and "Signal". (By double clicking or by marking and clicking on the "arrow"
button.)
The flagged I/O is adopted and displayed bold.
5. Edit the selected I/O points in the right window, "I/O points for parameters/signals".
You can edit the columns "Parameter/signal" (using a drop-down list),
"Process tag connector" and "Category" (using a drop-down list).
The drop-down list opens after clicking the corresponding input box.
6. In the left window, "I/Os in the chart of the process tag type", select the messages of the
relevant blocks.
All the messages are displayed in the "I/O points for messages" window.
7. Verify your selection and click "Finish".
Result
The new process tag type is stored in the master data library. The CFC chart from which the
process tag type originated, is located in the S7 program. There it can be reused or deleted if
no longer required.
Additional information
● Online help for PH, IEA and PO
Introduction
If you change a process tag type already used to create process tags, you may decide
whether the changes should be applied to the process tags that were created prior to
changing the process tag type.
Requirement
The CFC chart is stored in the master data library.
Procedure
1. Select the desired CFC chart in the SIMATIC Manager (Plant View).
2. Select the menu command Options > Process Tags > Create/Modify Process Tag Type...
.The wizard is started and displayed with the "Introduction" page. The current master data
library is displayed.
3. Click "Continue".
The wizard changes to the "Which I/Os do you want to assign to the process tag type?"
page.
4. In the left window "I/Os in the chart of the process tag type", select the flagged I/O for
"Parameter" and "Signal". (By double-clicking or by marking and clicking the "arrow"
button.)
The flagged I/O is adopted and displayed bold.
5. Edit the selected I/O points in the right window, "I/O points for parameters/signals".
You can edit the columns "Parameter/signal" (using a drop-down list), "Process tag
connector" and "Category" (using a drop-down list).
The drop-down list opens after clicking the corresponding input box.
6. In the left window, "I/Os in the chart of the process tag type", select the messages of the
relevant blocks.
All the messages are displayed in the "I/O points for messages" window.
7. If no process tags can be located in the project for the modified process tag type, click
"Continue" and then "Finish".
The wizard closes.
Otherwise:
8. Click "Next".
The wizard switches to the "Do you want to finish the process tag type and apply changes
to the existing process tags?" page.
9. Click "Make".
The change log appears.
10.Click "Exit".
Result
Changes made to the process tag type and the process tags are completed. The wizard
closes.
Note
Changes that you make in the chart of the process tag type are not taken into account when
the process tags are synchronized. In this case, you must carry out a new import for the
changed process tag type.
In the import file, add the keyword "delete" for each process tag to be deleted in the "Import
mode" column of the "General column group".
To create a new process tag, insert an additional row in which the field of the "Import mode"
column remains empty. Any interconnections made to these process tags are lost.
You can also delete process tags manually in the SIMATIC Manager.
The import file must also be amended accordingly if I/Os were added during the modification
process.
Additional information
● Online help for PH, IEA and PO
Note
If you create process tags by copying and pasting, you still need to assign parameters
and interconnect them.
If you work with the import file, the data relating to the parameter assignment and
interconnection is taken from the import file.
8.11.7.5 How to Create an Import File or Assign it to the Process Tag Type
Introduction
An import file must be assigned to the desired process tag type in order to create process
tags. The following steps can be carried out with the "Assigning an import file to a process
tag type" wizard.
● Assign an existing import file
● Open and check an import file that has already been assigned
● Create and assign a new import file
Procedure
1. Select the applicable process tag type in the master data library.
2. Select the menu command Options > Process Tags > Assign/Create Import File....
The wizard is started and displayed with the "Introduction" page. The current master data
library is displayed.
3. Click "Continue".
The wizard changes to the "Which import file do you want to assign to the process tag
type?" page.
The "Import file" drop-down list displays either a file or - if no assignment has been made
- the "No import file assigned" text.
4. You have the following options:
– To check an assigned import file to find out whether all the information is accurate,
open the file by clicking "Open File" and edit the file with the IEA file editor if
necessary.
– To assign an import file that exists in the project, click "Other File..." and select the
desired file in the dialog field.
– To create a new import file, click "Create Template File..." and select the desired
columns/column groups in the dialog field. Then edit the template with the IEA file
editor that you open with "Open File".
Note
The "Column title" column can be edited if you select the "No import file assigned" text
in the "Import file" drop-down list. You can change the titles and then generate the
template file.
In the "Importing" column, a check mark indicates which I/O points exist in the import
file. If the check mark is not there, the flagged I/O exists in the process tag type but
not in the currently assigned import file.
5. Click "Finish".
Result
The import file is assigned to the process tag type.
Additional information
● Section "Creating/Editing Import Files with the IEA File Editor (Page 646)"
● Online help for PH, IEA and PO
Requirement
An import file must have been assigned to the process tag types.
Note to Reader
You can find a detailed description of the settings of the import files in the section
“Importing/Exporting Process Tags/Models“. The following is a description of the basic
procedure used when import files have already been assigned.
Procedure
1. Select the desired hierarchy folder, project node / process tag library (hierarchy folder in
the master data library), or the process tag type.
2. Select the menu command Options > Process Tags > Import....
The "Import" dialog box opens.
The wizard searches for the process tag types and corresponding import files (in all
hierarchy subfolders as well) and lists them. The import is executed for all the import files
listed.
3. If you do not want to import certain files, you can select them and remove them from the
list with the "Remove" button.
By clicking "Other File", you can search for a different import file and select it instead of
the other file.
4. Click "Continue" and then "Finish".
Result
The actual import process starts.
Depending on the setting of the "Only show errors and warnings in log" check box, the
complete list of import activities or only the errors that occurred are displayed in the log
window.
The log is saved in a log file. The name and path of the file are displayed below the log
window. You can modify this setting with the "Other File" button.
Additional information
● Section "How to Import Process Tag Types and Models (Page 639)".
Introduction
In the process object view, you can edit individual process tags of the project, such as
changing comments, values, and interconnections (as long as these are defined as
"Parameter" or "Signal").
Procedure
1. Open the process object view with the menu command View > Process Object View.
2. Select the desired process tag in the tree (left window).
3. In the table on the right, select the required tab and make your modifications there (in the
editable cells).
Example: You want to interconnect an I/O with another I/O.
Requirements: The I/O of the block is defined as a parameter.
1. Select the process tag.
2. Select the "Parameters" tab.
3. Select the cell for the required I/O in the "Interconnection" column.
4. Select the menu command Insert Interconnection... in the shortcut menu.
The "Insert Interconnections" dialog box opens.
5. Select the process tag in the tree and the block containing the I/O you want to
interconnect.
6. Click "Apply".
As an alternative, you can double-click the I/O or drag the I/O to the selected cell in the
process object.
Result
The interconnection is entered; the dialog box remains open. The next cell of the column is
selected.
NOTICE
After renaming process tags and subsequently compiling the OS, all interconnections in
pictures and archives as well as tags in scripts are automatically adapted. However, the
names of the archive tags are not adapted; these continue to show the old process tag
names. You can change the archive tag names accordingly. In this case, be sure that you
also adapt the associated trend controls, for example.
The interconnections are only corrected for the local process tags of the OS. Any
interconnections to process tags of another OS via server-server communication must be
adapted manually.
Introduction
You can reassign CFC charts that have no assignment to the process tag type during import
if the constraints are observed.
Requirements
The names of the CFC chart blocks and I/Os correspond with the names on the process tag
type.
This applies to the following:
● I/Os that are identified as a parameter/signal.
● Blocks identified for messages.
Procedure - Scenario 1
1. Use one of the existing charts to create a process tag type with the menu command
Options > Process Tags > Create/Modify Process Tag Type....
You will find additional information on this topic in Section "How to Create a Process Tag
Type from a CFC Chart (Page 518)".
2. Assign a suitable import file to the process tag type with the menu command Options >
Process Tags > Assign/Create Import File....
3. Start the import with the menu command Options > Process Tags > Import... and open
the import file on dialog page 2(3) using the "Open File" button.
4. Add each chart to be adopted to a row in the file. Continue until the import can be
finalized.
Note
Please note the following:
• Make sure that the charts you adopt are located in the folder entered in the
"Hierarchy" column of the import file.
• If you want to retain the values of the charts and you do not want them to be
overwritten with the values of the process tag type, then delete the corresponding
fields in the import file.
Result - Situation 1
If the conditions for adopting the process tags are fulfilled, the CFC chart becomes the
process tag of the imported process tag type and the I/O name and category is applied from
the process tag type. Any additional process tag identifiers (message block or block I/Os) are
reset.
Additional blocks and I/Os that are not in the process tag type are tolerated and ignored.
If the adopted process tag is part of the replica of a model, the IEA flags remain unchanged.
If, however, it is not part of a replica, then preset IEA flags are reset if necessary.
Situation 2: chart has lost its assignment to the process tag type
You have canceled the assignment to the process tag type via the object properties of a
CFC chart that was already a process tag (with the menu command Object Properties > in
the "Process Tag Type" tab, chart selected, "Cancel" button).
In order to reassign the chart proceed as described under Items 3 and 4 of Situation 1.
Procedure - Situation 3
1. Select the process tag type in the PH.
2. Select the menu command Options > Process Tags > Export....
The "Import/Export Wizard" dialog box opens.
3. Click "Continue" and select the export file in the next dialog box ("Open File" or "Other
File" buttons).
4. Click "Continue".
5. If necessary, select the path and the name of the log file and click "Finish".
The export is executed and the export file is created. The actions are logged in the
window and stored in the log file.
6. Click "Back" to check the export file and then open the export file you have just created.
Result - Situation 3
All copies of the process tag type are included in the export file.
You can now use these files for further work, by adding entries when needed, and then using
them for the import process.
8.11.7.9 How to Synchronize Process Tags with the Process Tag Type
Introduction
When a process tag type is modified, the process tags existing in the multiproject are
automatically synchronized. Synchronization can be carried out directly if modifications result
in inconsistencies between the process tag type and the process tags (for example:not all of
the process tags of a project were accessible during the synchronization process).
Requirements
● Process tags are available in the multiproject.
● The modified process tag type is located in the master data library.
Procedure
1. Select the applicable process tag type (in the master data library) and then select the
menu command Options > Process Tags > Update.....
The "Synchronize Process Tags" wizard is started, and the current master data library is
displayed.
2. Click "Continue".
The wizard changes to the "Do you wish to synchronize the existing process tags the
process tag type?" page.
3. Click "Finish".
The synchronization process log appears.
Note
Changes that you make in the chart of the process tag type are not taken into account when
the process tags are synchronized. In this case, you must carry out a new import for the
changed process tag type.
In the import file, add the keyword "delete" for each process tag to be deleted in the "Import
mode" column of the "General column group". To create a new process tag, insert an
additional row in which the field of the "Import mode" column remains empty.
Additional information
● Online help for PH, IEA and PO
Introduction
If process tags exist in a project but the corresponding process tag type is no longer in the
master data library, it is not possible to import or export these process tags. The
import/export file structure is always required for the import/export process. This, however, is
located only on the process tag type.
Remedy
You can create a process tag type from an existing process tag in the project and reestablish
the assignment.
Procedure
1. Select the applicable process tag in the project.
2. Select the menu command Options > Process Tags > Create/Change Process Tag
Type....
The wizard is started and the current master data library is displayed.
3. Click "Continue".
The wizard displays an error message and asks whether the selected chart should be
created as a process tag type in the master data library.
4. Click "Yes".
The wizard changes to the "Which I/Os do you want to assign to the process tag type?"
page.
5. Click "Finish".
Result
The process tag type is created and stored in the master data library. The assignment of
process tags to the process tag type is therefore reestablished.
You now still have to assign the import file or create a new one.
Rules
Note
It is possible to modify the process tag type if necessary during this procedure. Existing
process tags are adapted automatically.
Note
If the process tag was adapted for a specified technological task, for which the process tag
type is irrelevant or may not even be present, then the corresponding changes (for example:
interconnections, assignment of parameters) have to made in the CFC chart.
How It Works
Using the SFC editor, you create your sequential control system using graphic tools. The
SFC elements of the chart are positioned in the sequencer according to fixed rules. You do
not have to concern yourself with details such as algorithms or the assignment of machine
resources. This allows you to concentrate on the technological aspects of the configuration.
After creating the plan topology, switch over to configuring the object properties. Here you
will need to formulate the sequencer properties as well as the individual steps and
transitions. In this way, you configure the actions and conditions.
After configuration, you compile the executable machine code with SFC, download it to the
PLC and test it with the SFC test functions.
Additional information
● Online help on SFC
● Manual SFC for S7; Sequential Function Chart
● Manual Process Control System PCS 7, Getting Started - Part 1
SFC type
In SFC, there is not only the object type "SFC chart" but also "SFC type".
The SFC type allows the definition of sequential control systems including an extendable
interface.
The SFC type sequential logic is based on the SFC type interface I/Os. In contrast to the
SFC chart, the SFC type does not access process signals randomly.
Alone, the SFC type cannot execute. An SFC type, just like a function block type, must be
placed in a CFC chart before it contains an executable object, in this case an SFC instance.
To run an SFC instance, both the SFC type and the SFC instance are downloaded to the
automation system.
Note
SFC types can also be located in libraries (for example, SFC Library).
For SFC types to be usable, they have to be located in the chart folder of the program. This
can be realized as follows:
• If you place an SFC type from the library directly into a CFC chart, the SFC type is copied
into the chart folder of the program. The SFC type is then visible in the CFC catalog in the
"Blocks" tab and can be placed in the CFC chart from there.
• Copy the SFC types from the chart folder of the library into the chart folder of the
program. The SFC types can then be used in the CFC catalog in the "Blocks" tab and can
be placed in the chart from there.
SFC instance
An SFC instance is derived from an SFC type. For this purpose the SFC type is inserted in a
CFC chart in the same way as a function block type in CFC. The SFC instances are
therefore always assigned to a CFC chart and are addressed via the chart. Like CFC
instances, SFC instances are represented as blocks: their interface is visible in the CFC
chart.
SFC instances are not displayed in the SIMATIC Manager since they can only be addressed
via the CFC chart. With the assignment of the CFC chart to the plant hierarchy, the SFC
instances it contains are also indirectly assigned to the plant hierarchy.
Basic Procedure
1. You create the SFC type in the SFC-Editor. At the same time you configure its
sequencers and the SFC interface.
You will find additional information on this topic in Section "How to Create an SFC Type
(Page 555)".
2. You create the SFC instances in the CFC chart and set the parameters and interconnect
them.
You will find additional information on this topic in Section "How to Generate an SFC
Instance (Page 558)".
Additional information
● Online help on SFC
● Manual SFC Visualization for S7
Introduction
The following is a series of steps that you must execute when configuring sequential control
systems (SFC charts) for your PLC: The same series of steps also applies to the
configuration of SFC types, however in this case, the I/Os and characteristics must still be
defined.
Requirement
A project structure is created in the SIMATIC Manager in which you can configure CFC/SFC
charts.
Note
When entering units, ensure that the following special characters are not used: [ ' ] [ $ ].
Introduction
You can create SFC charts and SFC types in the SIMATIC Manager.
Requirements
● The required project structure already exists in the SIMATIC Manager.
● The hierarchy folder used for creating the chart must be assigned a chart folder.
Procedure
1. Select the desired hierarchy folder in the plant view of the SIMATIC Manager.
2. Select the menu command Insert > Technological Objects > SFC.
The SFC chart is inserted into the hierarchy folder. The SFC chart is automatically
assigned to a chart folder.
The chart receives a standard name from the system (for example, SFC(1)).
3. Change the name according to your requirements. The name must be unique on the
CPU. This is checked by the system.
4. Double-click the new SFC chart in the right window (content of the hierarchy folder).
Result
The SFC editor starts (if it is not already started) and the SFC chart is displayed in its initial
state in a window of the SFC editor.
Naming
Note
Please note the following:
• The names of the SFC charts can be a maximum of 22 characters.
• The names of the SFC types can be up to a maximum of 16 characters long. Although
you can enter 24 characters in the properties, when the instances are created, only 16
characters are permitted.
• The following characters are not permitted in names: \, ., /, ", %
Additional information
● Online help on SFC
Introduction
The sequencer properties are used to determine how the sequencer starts or which
sequential control systems start first. The sequencer of a newly created SFC chart (type)
already has a start condition (RUN = 1). As a result, it is connected to the operating state
logic (OSL). For each further sequencer you must specify the start conditions yourself. The
start conditions and the priorities determine which sequencer starts.
Procedure
1. Select the menu command Edit > Sequencer Properties... in the SFC editor.
The "Properties" dialog box opens.
2. Set the sequencer properties listed in the following table.
Additional information
● Online help on SFC
Syntax Rules
The basic rule for chart topology is as follows: a step (S) is always followed by a transition
(T) and vice versa (sequence: S-T-S or T-S-T). The editor automatically abides by the rules.
Example:
If you insert a simultaneous branch in a sequencer following a transition but prior to a step, a
transition is created automatically before the step, since the syntax rules require a transition
before and after a simultaneous branch.
Data backup
Note
All changes made in the SFC editor are saved immediately - there is therefore no extra save
option in SFC. Please remember that you cannot undo or cancel changes in the SFC editor
after closing the editor without saving.
We recommend archiving the data contained in the entire multiproject or the relevant project
using the menu command File > Archive....
Steps
Actions are defined in the steps. These contain statements with which, for example, values
of block inputs can be modified or other SFC charts activated or deactivated.
Tab Meaning
General In this tab, you can edit the general properties of the selected step (for example
name, comment).
Initialization The tabs for the processing phases (actions) "Initialization", "Processing" and
Processing "Termination" all have the same structure. Here, you configure the statements
that will control the process.
Termination
In these tabs, you can define the following actions for the steps:
• Actions that should be carried out once upon activating the step (initializing)
• Actions that should be carried out in cycles when the step is processed
(processing)
• Actions that should be carried out once upon exiting the step (termination)
Each step for which you have defined an action is displayed in dark gray. This
means that you can see at a glance whether or not a step has already had
parameters assigned.
Procedure
1. Select the step you want to edit in the SFC Editor.
2. Select the menu command Edit > Object Properties....
The "Properties" dialog box for the step opens.
3. Enter the desired properties in the "General" tab.
Note
All other tabs can theoretically be edited in the same manner.
4. Select the required tab (Initialization, Processing, Termination) and position the mouse
pointer in the input field for the left address (the operator) of the required statement line.
5. Click "Browse".
The "Browse" dialog box opens.
In this dialog box, you can see the CFC charts of the project with the PH assignment, the
chart name, and the comment in the first three columns. In the next three columns, you
can see all the blocks belonging to the chart selected in the first columns. As soon as you
select a block, the last column displays all the relevant I/Os.
6. Select the required CFC chart.
All the blocks for the chart are displayed.
Additional information
● Online help on SFC
Transitions
A transition contains the conditions according to which control passes from one step to its
successor step or steps. Several conditions can be logically combined using Boolean
operators. The result of the logic operation decides whether control is passed to the next
step. Transitions are theoretically configured in the same way as steps.
Properties of Transitions
You can make the following settings in the "Properties" dialog box for the transition:
Tab Meaning
General In this tab, you can edit the general properties of the selected transition (for
example, name, comment).
Condition In this tab, you define the conditions for the SFC chart / SFC type that cause
transitions to enable the next step in the sequencer.
To allow a three-stage transition logic, you can combine the conditions logically
to create a Boolean expression.
OS Comment In this tab, you can enter an OS comment with a maximum length of 256
characters for every condition in the SFC chart / SFC type.
Formulated conditions are entered as defaults in the "Conditions" or "Start
Condition" tab.
Conditions
Transition conditions allow for the following options:
● Values to be read from block I/Os or shared addresses
● To logically combine the read values with a constant or another read value using Boolean
operators (=, >, <, ...)
The result of a condition is a Boolean variable that can be logically combined with the results
of other conditions.
Procedure
1. Select the transition you want to edit in the SFC Editor.
2. Select the menu command Edit > Object Properties....
The "Properties" dialog box for the transition opens.
3. Enter the desired properties in the "General" tab.
4. Select the "Condition" tab and position the mouse pointer in the input field for the left
address (the operator) of the required statement line.
5. Click "Browse".
The "Browse" dialog box opens.
In this dialog box, you can see the CFC charts of the project with the PH assignment, the
chart name, and the comment in the first three columns. In the next three columns, you
can see all the blocks belonging to the chart selected in the first columns. As soon as you
select a block, the last column displays all the relevant I/Os.
6. Select the required CFC chart.
All the blocks for the chart are displayed.
7. Select the required block.
All the I/Os for the block are displayed.
8. Select the required I/O and select the shortcut menu command Apply I/O.
The selected block I/O is entered with the corresponding complete path. The mouse
pointer is automatically positioned in the input field for the right address.
9. Select the required operator with which the two addresses will be logically combined.
10.Depending on the left address, enter a setpoint for the right address such as TRUE or
FALSE or an interconnection onto a block I/O (menu command Browse).
11.Specify the 3-level transition logic. The Boolean operators are designed as buttons.
Clicking on the operator switches it from "AND (&)" to "OR (≥1)". Changing “AND" to
"NAND" and “OR" to "NOR" is carried out by clicking the address output.
The negation is displayed by a period in bold print on the output line.
12.Open the "OS Comment" tab.
In this tab, you can enter an OS comment with a maximum length of 256 characters for
every condition in the SFC chart / SFC type.
Formulated conditions are entered as defaults in the "Conditions" or "Start Condition" tab.
Opening the “OS Comment" tab the first time applies the formulated condition as an OS
comment. This can be changed at any time.
If the OS comment is the formulated condition, in other words the default, this is indicated
at the start of the line by the "Link" symbol.
13.Click "Apply" to apply the settings.
14.Click "Close".
Additional information
● Online help on SFC
Introduction
You can display and modify the operating parameters and runtime properties for the active
SFC chart. The initial state of the SFC chart is specified with the operating parameters.
Tab Meaning
General You can enter or change the following in this tab:
• Name of
• Author
• Comment
• Write-protected
PLC Operating In this tab, you can change the default settings for the operating
Parameters parameters of the AS and the start options of the SFC chart.
• Default settings for the initial state of the SFC chart:
– "Step Control Mode"
– "Operating Mode"
– "Command Output"
– "Cyclic Operation"
– "Time Monitoring"
• Options for the SFC startup after a CPU complete restart
– "Initialize SFC"
– "Retain SFC status"
• Options for starting the SFC chart:
– "Autostart"
– "Use default operating parameters when SFC starts"
The settings for this option determine the runtime characteristics of the
sequential control system.
OS In this tab, you can specify if the SFC chart should be included in the next
compilation of the OS.
Version In this tab, you can change the version number of the SFC chart.
Tab Meaning
General You can enter or change the following in this tab:
• Name
• Author
• Comment
• Write-protected
PLC Operating In this tab, you can change the default settings for the operating
Parameters parameters of the AS and the start options of the SFC type.
• Default settings for the initial state of the SFC type:
– "Step Control Mode"
– "Operating Mode"
– "Command Output"
– "Cyclic Operation"
– "Time Monitoring"
• Options for the SFC startup after a CPU restart
– "Initialize SFC"
– "Retain SFC status"
• Options for starting the SFC chart:
– "Autostart"
– "Use default operating parameters when SFC starts"
The settings for this option determine the runtime characteristics of the
sequential control system.
Options In this tab you can set the options for SIMATIC BATCH for the SFC type.
• Category:
– None"
– "EOP"
– "EPH"
• Allow operator instructions
• SIMATIC IT
– "MES-relevant"
• Control strategy selection
Version In this tab, you can change the version number of the SFC type.
Procedure
1. Select the menu command SFC > Properties....
The "SFC Chart Properties" dialog box opens.
2. Adapt the operating parameters and runtime properties.
3. Click "OK".
Operating mode
In the list box select whether the execution is controlled by the operator or carried out
automatically.
● AUTO (process mode):
The execution is controlled automatically. The program defaults apply. The defaults are
determined either by the parameter assignment or the interconnection of SFC external
view inputs in the CFC chart. In the "Auto" mode, the step control modes "T" and "T / T
and C" can be set.
● MANUAL (operator mode) (default):
The execution is controlled manually by the operator (for example, in the SFC test mode
or on the OS in SFC). All step control modes are permitted.
Option Meaning
Command output Default: On
During installation and commissioning, or if errors occur, blocking command
output in conjunction with certain operating modes can bring the sequential
control system to a defined state without influencing the process.
The actions are processed by activated steps if the check box is activated,
otherwise the actions are not processed.
Cyclic Operation Default: Off
When the sequence is completed and the check box is activated, the SFC
chart or the SFC instance that was created by this type, switches over from
the operating state "completed" into the operating state "starting". The SFC
chart or the SFC instance automatically begins with start-processing.
Time Monitoring Default: Off
If this option is activated (check mark), the monitoring times (# 0 ms) set as
parameters in the object properties of the steps are evaluated. A message is
generated (step error) if this time is exceeded.
Autostart Default: Off
After restarting and if the check box is activated, the SFC chart or the SFC
instance that was created by this type, is now in the operating state "starting".
The SFC chart or the SFC instance automatically begins with start-
processing. Otherwise the SFC chart or the SFC instance is in the operating
state "ready" waiting for the start command.
Use default Default: Off
operating If this option is activated, all the operating parameters set in the "Defaults"
parameters when group (and possibly changed in test mode) are reactivated when the chart or
SFC starts instance starts.
Introduction
You can do the following with SFC charts and SFC types:
● In the SIMATIC Manager and SFC Editor:
– Create new
– Open for editing
– Change the properties
● In the SIMATIC Manager only:
– Copy and delete
● Within a CFC chart:
– Copying and deleting SFC instances
What? How ?
Open SFC chart in the In the SFC editor, select the menu command SFC > Open... and then select
SFC Editor the required chart.
Opening an SFC Type Select the menu command SFC > Open... in the SFC editor. To open an
in the SFC Editor SFC type, you must select the entry "SFC type" from the drop-down list in
the "Open" dialog box field from the "Object type" field.
Open SFC chart in the Select the required SFC chart in the component view or plant view with the
SIMATIC Manager menu command Edit> Open Object.
Open SFC type in the Select the required SFC type in the component view with the menu
SIMATIC Manager command Edit > Open Object.
Opening SFC Select the SFC instance in the CFC chart and in the shortcut menu the
Instances menu command Open.
Copying, Moving and Deleting SFC Charts, SFC Types and SFC Instances
Additional information
● Online help on SFC
Introduction
You can configure specific message texts for each SFC chart/SFC type. You can change the
message text in a dialog box.
Procedure
1. Select the menu command SFC > Message... in the SFC Editor.
The "PCS 7 Message Configuration" dialog box opens.
2. Use the table below to configure the block-related message types and messages for
display on the PCS 7 OS.
Column Meaning
Message name This column displays the name of the block-related message within the message
configuration.
Message Class Select the required message class in this field.
Priority Select the priority level for acknowledging individual messages in this field. The higher the
value, the higher the priority.
Event Enter the message text in this field.
Single acknowledgment Activate the check box, if the message should be acknowledged as a single message.
Info text Enter the info text in this field.
With acknowledgment Activate this check box if the messages generated should be acknowledged. Depending on
whether this check box is activated or not, the "Message class" column will either display
those classes that can be acknowledged or those that cannot be acknowledged.
For the SFC type only!
Whether or not this column is displayed depends on whether you are editing message types
or messages. By putting a check mark in this column, you can interlock the text you entered
in the column before it.
Note
If you edit existing messages, the entries for Origin, OS area, and Batch ID are displayed in
red and italics if they were edited during message configuration and the entries are not
uniform. To make the entries uniform, overwrite the displayed text.
If you have not yet created a PCS 7 OS, a display device is created automatically and given
an internal name.
SFC type
The SFC type is managed in the SIMATIC Manager component view.
An SFC type does not have any runtime properties, since it is not relevant to execution of the
program. An SFC type cannot be installed in the run sequence.
Requirement
● A PCS 7 project is created.
Procedure
1. Mark the chart folder and select the menu command Insert > S7 Software > SFC Type in
the component view of the SIMATIC Manager.
The next free FB number is automatically reserved for the SFC type being created, and
this is copied into the block folder as a type template with this number. The FB number
can be changed later in the "Object properties" dialog box.
When you first create an SFC type, the blocks required for compilation are copied to the
current program and then managed in the ES. The blocks are contained in the delivery of
the PCS 7 Library.
Note
SFC types cannot be assigned to a hierarchy folder in the plant view since they
themselves are not relevant to execution (from the perspective of the process to be
automated).
2. Select the SFC type in the SIMATIC Manager and then the menu command Edit > Object
Properties....
The "SFC Type Properties" dialog box opens.
3. Set the SFC type properties and the operating parameters.
You will find additional information on this topic in the Online Help and in Section "How to
Adapt the Operating Parameters and Runtime Properties (Page 548)".
4. Select the SFC type in the SIMATIC Manager and then the menu command Edit > Open
Object....
The SFC type opens.
5. Select the SFC Editor menu command View > Characteristics and add the control
strategies, setpoints (note: do not forget the control strategy assignment), process values,
block contacts, etc.
6. Add and then configure the sequencers. Edit the start conditions.
You will find additional information on this topic in Section "How to Specify the Sequencer
Properties (Page 539)".
7. Configure messages for the SFC type.
You can configure a maximum of seven messages that require an acknowledgment and
five messages that do not. The SFC type itself requires the remaining available
messages (one per message type and 10 notify messages for SIMATIC BATCH).
You will find additional information on this topic in Section "How to Configure Messages in
SFC (Page 554)".
8. Configure a text box in the SFC editor via menu command SFC > Text Boxes.... You can
configure a text box for an SFC type, as done with the SFC chart.
You can find additional configuration options in the online help on SFC and in the manual
SFC for S7; Sequential Function Chart.
are also possible. As a result the SFC type is self-contained. There are no external
accesses originating from SFC type which bypass the interface.
Additional information
● Online help on SFC
● Manual SFC for S7; Sequential Function Chart
SFC instance
An SFC instance is generated by dragging the SFC type from the CFC block catalog into the
CFC chart.
The SFC types in the chart folder of the AS are displayed in the CFC block catalog (in "All
blocks" and in the folder of the family if they are assigned to a family, otherwise in the "Other
blocks" folder).
The SFC instance is displayed like a CFC instance block. If there is not enough free space to
position the SFC instance and it overlaps one or more objects that have already been
placed, it will be displayed as an overlapping block (light gray and without visible I/Os). After
moving them to a free location in the chart, the overlapping blocks are displayed as normal
blocks again.
You can assign parameters to the SFC instance and interconnect it in test mode.
If you have defined block contacts, when you interconnect an I/O of this block, the other I/Os
are automatically interconnected (predefined I/Os for interconnection with the SFC type
("S7_connect" attribute)). The most important I/Os are already predefined in the
technological blocks of the PCS 7 Library.
Procedure
1. Open the CFC chart in which you want to interconnect an SFC instance with the blocks of
basic control.
2. Select the SFC type in the CFC block catalog "Other blocks" and place it in the CFC
chart.
An instance of the SFC type is generated in the CFC chart.
3. Specify the properties of the SFC instance.
In the CFC, you can modify the general properties (name, comment) in the object
properties of the SFC instance.
4. Adapt the operating parameters and options to suit the instance:
Using the Open command in the shortcut menu, open the SFC instance in the CFC and
adapt the operating parameters, which determine the runtime characteristics in the AS, in
the "Properties" dialog box.
You will find additional information on this topic in Section "How to Adapt the Operating
Parameters and Runtime Properties (Page 548)".
As an option, you can select which of the control strategies specified by the SFC type is
to be used for the SFC instance.
5. Configure and interconnect the interface of the SFC instance:
Assign the parameters for the I/Os of the SFC instance in the CFC using the object
properties or in the SFC using the "I/Os" interface editor.
In CFC, you interconnect the I/Os of the SFC instance with the I/Os of the CFC blocks or
with shared addresses or you create textual interconnections.
Additional information
● Online help on SFC
Introduction
SFC types can also be kept in the master data library. To be able to use them, you need to
copy the SFC types from the chart folder of the master data library into the chart folder of the
S7 program of the AS. The SFC types in the CFC block catalog of the "Blocks" tab (other
blocks) are visible in the result and can be placed in the CFC chart from there. You can find
information about this in the section "How to Create an SFC Instance (Page 558)".
To run an SFC instance, both the SFC type and the SFC instance are downloaded to the
automation system.
Procedure
1. Open the SFC type in the chart folder.
The SFC type is opened in the SFC editor.
2. Carry out the required changes in the SFC editor.
The changes are done on the SFC type and on each of the existing SFC instances.
3. Compile, download, and test the program.
4. Copy the SFC type to the master data library so that the modified version is available in
the CFC block catalog.
5. If the modifications made are relevant for assigning parameters or interconnections,
these modifications must be carried out in all the SFC instances.
In order to do this, open the relevant CFC charts and complete them.
Additional information
● Section "How to Download SFC Charts (Page 565)"
● Manual Process Control System PCS 7, Getting Started - Part 2
Compile
During compilation (scope: entire program) all charts (including SFC types) of the current
chart folder are transferred block-by-block to the SCL Compiler and compiled. After changing
the SFC chart (SFC type, SFC instance), you only need to compile the changes (scope:
"changes").
Consistency is automatically checked during the compiling process. You can also start this
check manually.
After compiling, download the user program to the CPU, test it and then put it into operation.
Note
If you only work with CFC and SFC in your program, you can leave the standard
compilation settings unchanged.
You will find an overview of the blocks generated during compilation in the online help.
Consistency Check
Prior to the actual compilation, the system automatically makes the following consistency
checks:
● Checks whether the block types in the user program match the types imported into CFC.
● Checks whether symbolic references to shared addresses are entered in the symbol
table.
● Checks whether the data blocks (DB) to which there are interconnections actually exist in
the user program.
● Checks whether in/out parameters or block outputs of the type "ANY", "STRING",
"DATE_AND_TIME" or "POINTER" are supplied with values (interconnected).
● Checks whether all the blocks accessed by SFC conditions or statements still exist.
Note
You can also check the consistency without compiling. To do this, select the menu
command SFC > Check Consistency.
Procedure
1. Select the menu command SFC > Compile....
The "Compile program" dialog box appears.
2. Activate one of the following options in the "Scope" group to specify the scope of the
compilation:
– Entire program: all the charts are compiled.
– Changes: only the objects changed since the last compilation are compiled.
3. Activate the "Generate SCL source" check box if required.
4. Click "OK".
The compilation process will begin.
Result
The charts of the current program (chart folder) are checked for consistency and then
compiled.
Display Logs
The result of the consistency check and all messages occurring during compilation are
displayed automatically following compilation.
You can also display the log later and print it out with the menu command Options > Logs....
Additional information
● Online help on SFC
Introduction
During configuration, testing and commissioning, there is often the need to compare a
new/changed SFC chart with the previously loaded version before downloading it.
Requirement
Before the initial download in the SFC editor with the menu command Options > Settings >
Compile/Download, activate the check box "Generate image of downloaded program for
comparison" in the "Settings for Compiling/Laden" dialog box.
Procedure
1. Select the menu command PLC > Download... in the SFC Editor.
2. Click "Show Changes".
The Version Cross Manager opens and the image created by the previous download (see
Requirements) is compared with the version to be downloaded and correspondingly
displayed.
Note
The "Show Changes" button is only enabled when the "Version Cross Manager" add-on
package is installed and an image has been generated for the loaded program.
Additional information
● Online help on SFC
Download
Before the graphic charts can be put into operation on a CPU, the charts must first be
compiled and downloaded to the CPU. The charts are downloaded to the CPU to which the
user program containing the current chart folder is assigned.
Requirements
● There must be a connection between the CPU and your programming device/PC.
● The edit mode is set (not the test mode).
● If you download the entire program, the CPU is in STOP mode.
If you only download changes, the CPU may be in RUN-P mode.
Procedure
1. Select the menu command PLC > Download... in the SFC Editor.
The "Download Archive System" dialog box opens.
2. Activate one of the following options in the "Download mode" group to specify the scope
of the compilation:
– Entire program
The entire content of the "Blocks" folder is downloaded.
– Changes
Only the blocks changed since the last compilation are compiled (the CPU can be in
the "RUN-P" state).
– Download to test CPU
With this type of download, you can download a modified program to another CPU or
to an S7 PLCSIM, without losing the delta download capability in the original CPU.
3. Click "OK".
The compilation process will begin.
Note
With the programs created in SFC, you must download to the CPU from SFC (or CFC),
since only this download function guarantees the consistency of the configuration data
with the CPU data.
The same download function is available in the SIMATIC Manager with the following
menu commands:
• Menu command PLC > Compile and Download Objects... and then activate the
"Charts" object for compiling and downloading
• In the component view: mark the "Charts" folder and select the menu command PLC >
Download
Result
The program (or only the changes) is downloaded to the CPU.
Note
If you have made download-relevant changes in the configuration and have not compiled
since you made the changes, you will be prompted to compile before you download. The
download is automatically carried out after error free compiling.
Note
Compiling the entire program does not necessarily mean a complete download. If the
program was already loaded in the CPU prior to compiling, then it is possible to download
only changes.
If a full download is aborted, changes cannot be downloaded until the full download is
completed. Reason: the blocks on the CPU were deleted prior to the download.
Downloading changes
If you select "Download: changes only" in the "RUN-P" CPU mode, you can download
changes to your configuration to the PLC without having to change the CPU to the STOP
mode. With this type of download, you only download changes that have been made since
the last download. Please comply with the following:
● If the chart topology has been changed in the SFC charts (steps or transitions added,
deleted, copied, moved, jump destination changed, ...), these charts must be deactivated
when changes are downloaded.
● Modifications to the interface of the SFC type are transferred to the SFC instances
immediately. The SFC instances must therefore be deactivated during downloads and
execution stopped on the CPU.
● If SFC charts have been modified (chart properties, object properties are the
steps/transitions) without changing their structure, you can download the charts after they
have been compiled while the CPU is in RUN without needing to deactivate the modified
SFC chart.
● If you have not changed the chart itself, but only the objects that are accessed (for
example, a symbol in the symbol table, runtime groups, block I/O), you do not need to
deactivate the chart before it is downloaded.
● After you download changes, a stopped SFC chart with the property "Autostart: on" is not
started automatically, it must be restarted by the operator.
Note
Please take note that there is no absolute guarantee that the CPU will not switch into the
STOP mode when changes are downloaded.
Test mode
The SFC Editor provides test functions that support the commissioning process. These are
used to monitor and influence the AS sequential control system process and to change
setpoints if necessary. For this purpose switch the SFC Editor into a test mode.
Requirements
● There must be a connection between the CPU and your programming device/PC.
● The program has been downloaded.
Test
Once you have started the test mode, you can test the functionality of your SFC.
The SFC can be started in "manual" mode. You can also influence the operating parameters
used for executing the SFC (for example, cyclic operation).
If the SFC is in the "RUN" operating mode, the following appears:
● Which step is currently active
● Which actions are executed in this step
● The transitions that are active and the conditions that must be satisfied for this transition
Note
Any operator input that you made or parameters you assigned in test mode are then
performed simultaneously in the CPU and in the data of the SFC.
If you switch an S7 CPU off and on again without battery backup, these parameter
changes are lost in the CPU. In such cases, to restore the parameter settings you must
recompile the chart folder and download it to the CPU again from your PC/programming
device.
Additional information
● Online help on SFC
● Manual Process Control System PCS 7, Getting Started - Part 1
● Manual SFC for S7; Sequential Function Chart
Introduction
Generally a plant is structured by dividing it into smaller functional units that can be
classified, for example, as fixed setpoint controls or motor controllers.
Instead of planning these functional units each time it is possible to create a supply of
prefabricated functional units known as models in the engineering system. Then you only
have to copy and modify them according to the requirements of the new solution.
To ensure that there is only one version of a model throughout a project, all models should
be stored centrally in the master data library and all adaptations should be made prior to
generating the replicas.
Model
Note
You can only create or modify models in a multiproject.
Replicas
The model can be imported with the Import/Export Assistant after it is prepared in this way
and linked it to an import file. The generated replicas are assigned the parameters,
interconnections, and messages of the model. Each line in an import file creates a replica in
the destination project.
Requirement
The functional unit from which you want to create a model has been tested on the
automation system and on the operator station.
Creating a Model
1. Select the hierarchy folder containing the CFC chart (or CFC charts, SFC charts, etc.)
required for the model in the master data library (or a hierarchy folder containing a nested
hierarchy folder with a CFC chart).
2. Start the wizard with the menu command Options > Models > Create/Modify Model... and
select the following in the next steps:
– Which I/Os do you want to import as parameters or signals?
– For which blocks do you want to import message texts?
– Which import data do you want to assign to specific model data?
In the "Which import data do you want to assign to specific models?" step, the text "No
import file assigned" is initially entered in the "Import File" input field. By clicking "Other
File..,", you can browse and enter an import file.
Result
You then have a model available with an assignment to a column of the import file for each
selected I/O and each selected message; as a result every column of the import file has
been used (1:1 assignment).
When working with messages the following applies: not all lines of the model data must be
supplied with data from the import file. The number of messages in the import file can,
therefore, be less than the number of messages in the model (in this case the 1:1
assignment does not apply).
The hierarchy folder is displayed as a model in the SIMATIC Manager.
Modifying a Model
Models that do not have replicas can be modified at any time.
1. Select the menu command Options > Models > Create/Modify Model....
If you modify models that already have replicas, a message is displayed since the import
data no longer match the model data.
If you modify the I/O points (IEA flags) of a model that already has replicas, a message is
displayed and the dialog box is expanded by an additional step. All the modifications that
have been made are logged in this additional dialog box. The following modifications are
then made to all replicas:
● If IEA flags are missing in the replicas, they are set.
● If there are more IEA flags set in the replicas than in the model, these are removed from
the replicas.
Note
The block names may no longer be modified in an existing model or in replicas of a
model. Otherwise, import/export is no longer possible.
With the IEA, you can assign parameters to block I/Os and chart I/Os and interconnect them;
you can also rename chart I/Os.
Note
Please remember that it may be necessary to adapt the IEA file as well.
Additional information
● Section "How to Work with Models in the SIMATIC Manager (Page 577)"
● Online help for PH, IEA and PO
Introduction
Using a textual interconnection, you interconnect the inputs and outputs of blocks or nested
charts for the import. This can be done both within a chart and across charts.
Requirements
● The interconnection partners are in the same chart folder.
Syntax
The interconnection has the following syntax:
cfc\block.io
or
cfc\chart.io
or
sfc.I/O
If folders of the PH are included in the name, the path of the plant hierarchy can also
precede the name (ph\ph\cfc\chart.block] but this is ignored.
Textual interconnections
Textual interconnections are possible only for I/Os defined as parameters.
Textual interconnections can start both at outputs and imports if these are defined as
parameters. Multiple interconnections are possible only at the outputs of the CFC charts.
Only single interconnections are possible at the inputs.
When creating the IEA file, the textual interconnection check box must be activated on the
"Parameters" tab of the "Create File Template" dialog box.
Multiple Interconnections
Multiple interconnections are interconnections that lead from one output to several inputs.
● Multiple interconnections can be entered in the import file for parameter and signal
outputs. The I/O names are separated in the column by quotation marks (“).
● If you want to retain an existing single interconnection and add a new interconnection,
enter the separator character " (quotation mark) after the text for the interconnection.
Without this separator character, the old interconnection would be replaced by the new
one.
● If a multiple interconnection already exists, the interconnection is always created during
import in addition to the existing and connections. This happens regardless of whether or
not there is a separator character.
● The keyword "---" deletes all interconnections at the output.
During export, the existing multiple interconnections are also indicated by the " separator
character.
Rules
The following rules apply when working with textual interconnections in models:
● When you create a model/process tag, the "Create Template File" function enters the
interconnection partner according to the interconnection in the model for the textual
interconnection in the "TextRef" column. This would lead to an interconnection in the
model and thereby change the model during the import process.
This column must, therefore, be corrected. To prevent accidental changes to the model,
the interconnection partner is prefixed by a question mark ("?") in the "TextRef" column,
which would lead to an error during import.
● As part of the correction process, you can search for "?" with the IEA file editor and
modify these cells accordingly.
Textual interconnections should, whenever possible, only originate at inputs. For this
reason, no "TextRef" columns are created for outputs when the file template is generated
even if the "Textual Interconnection" option has been activated in the selection dialog. If
required, you must create these extra with the "Expand Column Group" function of the
IEA editor.
● Textual interconnections are set up at parameter I/O points, interconnections to shared
addresses at signal I/O points.
Introduction
Using the Assistant for models, you import the data of the model.
The model is copied from the master data library to the specified target projects as a replica.
Thereafter the data is imported. According to the entry in the import file, you can create any
number of replicas.
When you import, you can decide whether or not the imported signals will be entered in the
symbol table (option: "Also enter signals in the symbol table"). With PCS 7, we recommend
that you do not use the option because these entries are made when you configure the
hardware with HW Config.
Requirement
The corresponding import file is available.
Note to Reader
You can find a detailed description of the settings of the import files in the section
“Importing/Exporting Process Tags/Models“. The following is a description of the basic
procedure used when import files have already been assigned.
Procedure
1. Select the required model in the master data library.
2. Select the menu command Options > Models > Import...
The wizard searches for the process tag types and corresponding import files (in all
hierarchy subfolders as well) and lists them. The import is executed for all the import files
listed.
3. If you do not want to import certain files, you can select them and remove them from the
list with the "Remove" button.
By clicking "Other File", you can search for a different import file and select it instead of
the other file.
4. Click "Continue" and then "Finish".
The actual import process starts.
Result
Depending on the setting of the "Only show errors and warnings in log" check box, either the
complete list of import activities or only the errors that occurred are displayed in the log
window.
The log is saved in a log file. The name and path of the file are displayed below the log
window. You can modify this setting with the "Other File" button.
Additional information
● Section "How to Import Process Tag Types and Models (Page 639)"
● Online help for PH, IEA and PO
Copying Models
Note
In a multiproject, a model must not exist more than once and must be located in the master
data library.
Removing Models
If you no longer want a model to be available for import/export, or if you want the model to
become a normal hierarchy folder again, then proceed in the following manner:
1. Select the hierarchy folder
2. Select the menu command Edit > Object Properties....
3. Open the "Models" tab.
4. Click "Cancel".
The assignment to the import file is deleted. This also means that all existing replicas of the
model are changed to normal hierarchy folders.
Removing Replicas
Model replicas can be removed in the same manner as models. Proceed in the following
manner to change replicas back into "normal" hierarchy folders.
1. Select one of the replicas
2. Select the menu command Edit > Object Properties....
3. Open the "Models" tab.
4. Select the replica and click "Cancel".
Applications
By using the IEA, you can convert replicas or neutral hierarchy folders with CFC charts that
do not belong to a model into replicas of an existing model if the structure of the replica
corresponds completely with the structure of the model.
The following applications are conceivable:
● You imported into a project and then adapted the replicas locally. A handling error (for
example, in distributed engineering the model was forgotten after branching and merging)
replicas exist but the corresponding model is missing.
● You want to continue working with the IEA in a project after several charts have already
been created and adapted locally. You want to assign the hierarchy folders with these
charts to a model as replica.
The procedure for the situations outlined above is described below.
Procedure
If replicas no longer have a corresponding model, then a suitable model can be created for
them in the following manner:
1. Select the replica.
2. Select the menu command Options > Models > Create/Modify Model....
3. Select the previous import file in subsequent dialog steps and assign this import data to
the model data.
You can find further information about this in the section "How to Create a Model
(Page 570)".
4. Start the export using the Options > Models > Export... menu command.
You will receive an IEA file that includes the current data of all existing replicas.
8.11.10.1 Introduction into Editing Mass Data in the Process Object View
Introduction
In the process object view (Page 243), all project-wide data of the basic automation can be
displayed and edited in a view based on process control. Project-wide means that the data
from all the projects is contained in a multiproject.
Overview
Editing mass data in the process object view involves the following topics:
● Displaying general data (Page 585)
● Editing Blocks (Page 587)
● Editing Parameters (Page 589)
● Editing Signals (Page 593)
● Editing Messages (Page 597)
● Editing Picture Objects (Page 599)
● Editing Archive Tags (Page 601)
● Editing Hierarchy Folders (Page 603)
● Editing Equipment Properties (Page 605)
● Editing the Shared Declarations (Page 606)
● Testing in the Process Object View (Page 607)
Filtering
In the process object view, you can limit the number of objects selected for display by using
a filter. The default setting is: <no filter>.
In the "Filter by column:" list box, select the column in which you wish to use the filter text
("Display:" input field) to define the objects that are to be displayed in the table.
Examples:
● You want to display all the CFC charts in the table.
In "Filter by column:", select the type and, in the "Display:" input field, enter "cf".
All object types that begin with the letters "cf" are displayed (e.g. all CFC charts).
● You want to display all the objects from a certain range in the table:
In "Filter by column:", select the path and, in the "Display:" input field, enter "*Boiler".
All the objects whose paths contain the "Boiler" character string are displayed.
Special filter entries apply to the "Simulate outputs" column.
Note
The filter settings that you make on the "General" tab apply to all other tabs. The filter
settings on these tabs specify the selection you make.
Sorting
You can sort the data displayed in the process object view in ascending and descending
alphanumeric order. To do this, click the heading of the column whose data is to be sorted. A
small arrow will indicate whether the data has been sorted in ascending or descending order.
Dividing a table
You can divide the window into two halves (left and right), so that each has an individual
scroll bar. This is a function which you may recognize from Excel, for instance.
Displaying/Hiding columns
You can use the menu command Options > Settings... to hide columns, show columns that
were previously hidden, and change the order of the columns on the "Columns" tab.
Note
Within a project, on the "Blocks" tab you can assign the OS-relevant attribute to a newly
defined column, or remove an attribute that has already been assigned, using the
corresponding shortcut menu command.
Note
Please note the following:
• You do not have to enter the complete text you are searching for; entering only a part of it
is sufficient if this guarantees that the text being sought can be identified uniquely.
• If you click "Replace"/"Replace all" without having entered text in the "Replace by:" entry
field, the text found will be deleted.
Additional information
● Online help for PH, IEA and PO
"General" tab
In this tab, all the underlying ES objects (objects of the PH) for the part of the plant selected
in the hierarchy window are displayed along with their general information. If the selection is
changed, the relevant objects are read in again.
Note
If the block is a component of a fail-safe program, at the beginning of the line the field with
the line number has a yellow background.
Column Meaning
Hierarchy Displays the technological path of the object (or the storage location of the
projects/libraries).
Name of Displays the icon of the object and the object name. You can change the
object name.
Comment Input field for the comment on the object. You can change the comment.
Type Displays the object type, for example process tag, CFC, SFC, OS picture,
report, or additional document.
Process tag type Displays the name of the process tag type from which the process tag was
derived.
FID Input field for the function identifier. If you modify the text here, it will be
entered in the CFC/SFC in the "Part 3" tab labeling field "Designation:" .
LID Input field for the location identifier. If you modify the text here, it will be
entered in the CFC/SFC in the "Part 3" tab labeling field "Designation block
according to place:". .
Status This column is visible only in the online view. A status message is displayed
here if the check box is activated in the "Watch" column. The status display
displays texts and colors the same as in CFC.
Monitoring This column is visible only in the online view. Here, you can enter or remove
the process tag or the chart for the test mode. If the watch function is switched
on, the columns "Activated," "Simulate inputs," and "Simulate outputs" are
displayed dynamically. They are then displayed with a yellow background.
Sampling time Shows the current execution cycle for the charts for which a runtime group
with the same name has been created. You can change the execution cycle.
The drop-down list shows the cycles determined from the specified OB cycle
and any reduction ratios for the runtime group.
Selected With this option, you can activate or deactivate charts in the run sequence.
The check box can be set offline and online.
Column Meaning
Simulate inputs With this option, the input signals of the sensor are changed to the simulation
values of the driver blocks (CH_AI, CH_DI, CH_U_AI, CH_U_DI, CH_CNT,
PA_AI, PA_DI, PA_TOT).
The check box can be set offline and online. Exception: If all SIM_ON I/Os are
interconnected, the check box is disabled. If only some of the SIM_ON I/Os
are interconnected, the check box is enabled, the setting however, applies
only to the SIM_ON I/Os that are not interconnected.
Simulate outputs With this option, the output of signals to the actuators in the automation
system is changed from the calculated value to the simulation value of the
driver blocks (CH_AO, CH_DO, CH_U_AO, CH_U_DO, PA_AO, PA_DO).
The check box can be set offline and online. Exception: If all SIM_ON I/Os are
interconnected, the check box is disabled. If only some of the SIM_ON I/Os
are interconnected, the check box is enabled, the setting however, applies
only to the SIM_ON I/Os that are not interconnected.
AS Displays the component path to the S7 program containing the process tag or
the CFC/SFC chart.
By clicking in the box, you can display a drop down list. If the project contains
several S7 programs, these are displayed in the drop-down list. By selecting a
different S7 program, you move the associated chart.
OS Displays the component path for the OS containing the OS picture or the OS
report.
By clicking in the box, you can display a drop down list. If the project contains
several operator stations, these are displayed in the drop down list. By
selecting a different OS, you move the associated object.
Block icons In this column you can see the pictures for which block icons will be
automatically generated (in the PH or when the OS is compiled). You can set
or reset the attribute "Derive block icons from the plant hierarchy" for each of
the collected pictures without needing to open the object properties of each
picture.
Can be controlled You use this column to determine if the SFC chart from the AS-OS
and monitored engineering should be transferred to the OS for visualization.
Author Input field for the name of the author. If SIMATIC Logon Service was activated
when a shared declaration was created, the user logged on at the time is
entered here.
You can change the names for charts and additional documents.
Version Displays the version number of the CFC and SFC charts that you can change
here.
Size Shows the size of the object in bytes as far as is practically possible.
Last modified Displays the date of the last modification to the object.
Additional information
● Online help for PH, IEA and PO
"Blocks" Tab
In this tab, the block properties of all blocks in the CFC charts are displayed for the object
currently selected in the hierarchy window. SFC instances are also identified as blocks here.
Note
If the block is a component of a fail-safe program, at the beginning of the line the field with
the line number has a yellow background.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed).
Chart Shows the name of the process tag or CFC (cannot be changed).
Plan comments Shows the comment on the chart (cannot be changed).
Block Shows the block name. You can change the name.
You can enter a maximum of 16 characters for block names.
Block comment Shows the comment on the block. You can change the comment.
Create block icon You can use this check box to specify if a block icon should be generated for
this block.
Activate the "Operator C and M possible" check box to enable this option. You
can then edit the cell in the "Block icon" column.
Block icon This shows the name of the icon with which the block is displayed in the OS
picture.
The cell can only be edited if the check box in the "Create block icon" column
is activated.
You enter a name for this block instance here if there is more than one variant
of block icons for this block type. If no name is entered, the default block icon
is used.
OCM possible This check box determines if the block can be operated and monitored
(system attribute "S7_m_c").
MES-relevant Check box which determines whether the information of this I/O can be
transferred to the management levels MIS/MES in response to a request.
The option can only be set when the "Operator C and M possible" check box
is activated.
Note: In the default setting, the column is hidden since this information is not
normally used in PCS 7. To display the column in the process object view, use
the menu command Options > Settings..., and select the "Columns" tab.
Readback enabled Indicates whether or not the I/O is marked as being capable of being read
back (I/O with system attribute "S7_read_back"). You cannot modify the
option.
Column Meaning
Block group Indicates blocks that belong to a specific message group, intended automatic
alarm suppression based on the operating state. You can change the name of
the group or enter it if the block has not yet been assigned to a group. You
can enter exiting group names from a drop-down list. The name can have a
maximum of 24 characters.
With interrupt Indicates blocks that have message response (cannot be changed).
Instance DB Shows the object names of the corresponding instance data blocks (for
example, DB86) (cannot be changed).
Family Shows the name of the block family to which the block belongs (for example,
CONTROL) (cannot be changed).
Author Shows the name of the author or the membership in a specific library for
PCS 7 blocks (for example, DRIVER70) (cannot be changed).
Block type Shows the name of the block type from which the block originates (cannot be
changed).
Internal ID Shows the name of the internal ID (for example, FC 262) (cannot be
changed).
Process tag type Shows the name of the process tag type from which the process tag (chart)
containing this block was created (cannot be changed).
Additional information
● Online help for PH, IEA, and PO
"Parameters" Tab
This tab displays the I/O points for all the process tags and CFC charts displayed in the
"General" tab that were specifically selected for parameter assignment or interconnections
between the process tags or CFC charts.
I/Os for the "Parameters" tab can be selected at the following locations:
● In the SIMATIC Manager using the menu command Options > Process objects > Select
I/Os... (display of objects selected in the tree view)
● In the CFC in the "Properties – I/O" dialog (of a block)
● On block type: system attribute S7_edit = para
Editing
The following parameter values can be entered for those I/Os visible in the "Parameter" tab.
● The value
● The unit
● The identifier
● Operator text for binary states and commentary.
As an alternative to the value, you can also insert block interconnections.
You can open the corresponding CFC chart in the shortcut menu. The relevant I/O of the
block is selected.
You can limit the number of objects selected for display by using a filter. You will find
additional information on this topic in Section "Working in the process object view
(Page 582)".
Each cell displayed in the table with a white background can be edited directly in the process
object view.
Note
If the connection is a structured connection from a fail-safe program, the field with the line
number is displayed yellow at the beginning.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed).
Chart Shows the name of the process tag or CFC (cannot be changed).
Chart comment Shows the comment that has been entered in the chart properties (cannot be
changed).
Block Shows the block name (cannot be changed).
Block comment Shows the comment on the block. You can change the comment.
I/O Shows the name of the block I/O (cannot be changed).
I/O comment Input field for the comment on the block I/O. You can change the comment.
Process tag Shows the name of the flagged I/O as specified for the process tag type
connector (cannot be changed).
Category Shows the category of the flagged I/O as specified for the process tag type
(cannot be changed).
Status This column is visible only in the online view. The status message is displayed
here if the check box is activated in the "Watch" column. In terms of color and
text, the column is analogous to CFC.
Monitoring This column is visible only in the online view. Here, you can register or
unregister the I/O for test mode. If "Watch" is switched on, the columns
"Status" and "Value" are displayed dynamically. They are then displayed with
a yellow background.
Value Input field for the value of the I/O according to the data type and permitted
range of values. You cannot edit the value if it involves an interconnected I/O
type IN or IN_OUT.
If the I/O is a STRUCT data type, the value of the first structure element is
displayed with an elementary data type. You can only change the value if the
structure can be configured.
If this is the value of an enumeration, you can select the text for the
enumeration value from a drop-down list if there is text in the enumeration of
the shared declaration. The enumerations and their values are declared and
managed on the ES.
The column is displayed dynamically (on a yellow background) if "Watch" is
switched on during test mode. If I/Os are interconnected, the value monitored
which cannot be edited is displayed on a (grayish yellow background). A red
background indicates a problem in transmission (value failed).
Unit Input field for the unit of the value. In addition to entering texts, common units
(kg, m, s, min, etc.) can also be selected from the drop-down list (I/O with
system attribute "S7_unit").
Note: The list of units is generated from the basic CFC set. This basic set can
be managed and changed in the ES.
Column Meaning
Interconnection Input field for interconnecting the I/O.
In addition to entering text, you can also open the interconnection dialog box
with the shortcut menu command Insert interconnection.... Interconnections
written as text are displayed with a yellow background.
Note:
When you select the shortcut menu command Go to Interconnection Partner,
you switch to the line of the interconnection partner if the interconnection
partner is identified in the process object view as a parameter.
Add forcing Check box that indicates whether forcing has been added for the I/O.
If this check box is activated, the two columns that follow - "Forcing active"
and "Forcing value" - will be enabled for editing.
If this option cannot be used, the I/O is not enabled for forcing.
Forcing active Check box that indicates whether forcing is active for this I/O.
To use this option, "Add forcing" must be activated.
Force value Input field for the forcing value.
This value is dependent on the data type of the I/O. To enter a value, "Add
forcing" must be activated.
OCM possible Check box with which you can display whether the I/O can be controlled and
monitored by the operator (I/O with system attribute "S7_m_c"; the attribute
cannot be changed).
Identifier Input field for the shortcut of the I/O (I/O with system attribute "S7_shortcut").
Text 0 Input field for a text describing the state "0". The text is only displayed and can
only be edited when the I/O is of the data type "BOOL" and has the system
attribute "S7_string_0".
Exception: if the I/O also has the "S7_enum" system attribute, only the input
field is active in the "Enumeration" column.
Text 1 Input field for a text describing the state "1". The text is only displayed and can
only be edited when the I/O is of the data type "BOOL" and has the system
attribute "S7_string_1".
Exception: if the I/O also has the "S7_enum" system attribute, only the input
field is active in the "Enumeration" column.
Watched Check box that decides whether the I/O is registered in test mode (I/O with
system attribute "S7_dynamic"). You can modify the option.
Archiving Indicates whether or not the block I/Os that can be controlled and monitored
by the operator are intended for archiving (I/O with system attribute
"S7_archive"). You can change this entry. By clicking in the box, you can
display a drop down list. The following types of archiving can be selected:
• No archiving
• Archiving
• Long-term archiving
Readback enabled Indicates whether or not the I/O is marked as being capable of being read
back (I/O with system attribute "S7_read_back"). You cannot modify the
option.
Column Meaning
MES-relevant Check box which determines whether the information of this I/O can be
transferred to the management levels MIS/MES in response to a request.
The option can only be set when the "Operator C and M possible" check box
is activated.
Note: In the default setting, the column is hidden since this information is not
normally used in PCS 7. To display the column in the process object view, use
the menu command Options > Settings..., and select the "Columns" tab.
Enumeration For I/Os with the system attribute "S7_enum", the object name of the
enumeration assigned to the I/O is listed here. You can change the name.
If you click in the text box, a drop-down list opens from which you can select
the desired name for the enumeration. The enumerations and their values are
declared and managed on the ES.
Data type Shows the data type of the I/O (cannot be changed).
I/O Shows the I/O type (IN = input, OUT = output, IN_OUT = in/out parameter)
and cannot be changed.
Block type Shows the name of the block type from which the block originates (cannot be
changed).
Chart type Here, you can see whether the flagged I/O belongs to a CFC or SFC chart.
Process tag type Shows the name of the process tag type from which the process tag (chart)
containing this block was created (cannot be changed).
Additional information
● Online help for PH, IEA and PO
"Signals" Tab
This tab displays the flag I/Os for all the process tags and CFC charts displayed in the
"General" tab that were selected explicitly for signal interconnections.
I/Os for the "Signals" tab can be selected at the following locations:
● In the SIMATIC Manager with the menu command Options > Process Objects > Select
I/Os....
● In CFC in the "Properties – I/O" dialog box
● On block type: system attribute S7_edit = signal
Processing
You can enter symbol names for the interconnections with I/O devices as well as text
attributes and commentary for the I/Os displayed in the "Signal" tab.
As an alternative to entering interconnection symbols as text, signals can also be selected in
a dialog box if they have already been specified by the hardware configuration.
In the shortcut menu, you can open either the relevant CFC chart or the hardware
configuration (HW Config) or the symbol table.
You can limit the number of objects selected for display by using a filter. You will find
additional information on this topic in Section "Working in the process object view
(Page 582)".
Each cell displayed in the table with a white background can be edited directly in the process
object view.
Note
If the connection is a structured connection from a fail-safe program, the field with the line
number is displayed yellow at the beginning.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed).
Chart Shows the name of the process tag or CFC (cannot be changed).
Plan comments Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Shows the comment on the block. You can change the comment.
I/O Shows the name of the block I/O (cannot be changed).
I/O comment Input field for the comment on the block I/O. You can change the comment.
Process tag Shows the name of the flagged I/O as specified for the process tag type
connector (cannot be changed).
Category Shows the category of the flagged I/O as specified for the process tag type
(cannot be changed).
Status This column is visible only in the online view. A status message is displayed
here if the option is set in the "Watch" column. In terms of color and text, the
status display is analogous to CFC.
Monitoring This column is visible only in the online view. Here, you can register or
unregister the I/O for test mode. The columns "Status" and "Value" are
displayed dynamically if "Watch" is switched on during test mode.
Value Input field for the value of the I/O according to the data type and permitted
range of values. You cannot edit the value if it involves an interconnected I/O
type IN or IN_OUT.
If this is the value of an enumeration, you can select the text for the
enumeration value from a drop-down list if it is present. The enumerations and
their values are declared and managed on the ES.
The column is displayed dynamically (on a yellow background) if "Watch" is
switched on during test mode. If I/Os are interconnected, the value monitored
which cannot be edited is displayed on a (grayish yellow background). A red
background indicates a problem in transmission (value failed).
Unit *) Input field for the unit of the value. In addition to entering texts, common units
(kg, m, s, min, etc.) can also be selected from the drop-down list (I/O with
system attribute "S7_unit").
Note: The list of units is generated from the basic CFC set. This basic set can
be managed and changed in the ES.
Signal Input field for the name of the interconnected signal. You can also directly
enter an absolute address. If a symbol exists for the absolute address you
enter, it will be displayed. Otherwise, the absolute address will be displayed
with '%' preceding it. In addition to entering text, you can also open the
interconnection dialog box with the shortcut menu command Insert signal....
Signal comment Input field for the signal comment read from the symbol table (cannot be
changed).
Column Meaning
Add forcing Check box that indicates whether forcing has been added for the I/O.
If this check box is activated, the two columns that follow - "Forcing active"
and "Forcing value" - will be enabled for editing.
If this option cannot be used, the I/O is not enabled for forcing.
Forcing active Check box that indicates whether forcing is active for this I/O.
To use this option, "Add forcing" must be activated.
Force value Input field for the forcing value.
This value is dependent on the data type of the I/O. To enter a value, "Add
forcing" must be activated.
Absolute address Absolute address of the signal (for example, QW 12 or I3.1) read from the
symbol table or originating from the "Signal" input field if the absolute address
was entered there (cannot be modified).
Hardware address Hardware address of the signal. Read from HW Config (cannot be changed).
Measurement type Measuring type of the signal for input modules; output type of the signal for
output modules. Read from HW Config (cannot be changed).
Measuring range Measuring range of the signal for input modules; output range of the signal for
output modules. Read from HW Config (cannot be changed).
AS Displays the component path to the S7 program containing the process tag or
the CFC chart (cannot be modified).
OCM possible Check box with which you can display whether the I/O can be controlled and
monitored by the operator (I/O with system attribute "S7_m_c"; the attribute
cannot be changed).
Identifier *) Input field for the shortcut of the I/O (I/O with system attribute "S7_shortcut").
Text 0 *) Input field for a text describing the state "0". The text is only displayed and can
only be edited when the I/O is of the data type "BOOL" and has the system
attribute "S7_string_0".
Text 1 *) Input field for a text describing the state "1". The text is only displayed and can
only be edited when the I/O is of the data type "BOOL" and has the system
attribute "S7_string_1".
Watched Check box that decides whether the I/O is registered in test mode (I/O with
system attribute "S7_dynamic"). You can modify the option.
Archiving Indicates which block I/Os that support OCM are intended for archiving. You
can change this entry. Clicking in the edit box displays a drop-down list box.
You can select the following types of archiving:
• No archiving
• Archiving
• Long-term archiving
Note: If you identify an I/O for archiving, it will only be displayed on the
"Archive tags" tab once you have performed compilation on the OS.
Readback enabled Indicates whether or not the I/O is marked as being capable of being read
back (I/O with system attribute "S7_read_back"). You cannot modify the
option.
MES-relevant *) Check box which determines whether the information of this I/O can be
transferred to the management levels MIS/MES in response to a request.
The option can only be set when the "Operator C and M possible" check box
is activated.
Column Meaning
Enumeration *) For I/Os with the system attribute "S7_enum", the object name of the
enumeration assigned to the I/O is listed here. You can change the name.
If you click in the text box, a drop-down list opens from which you can select
the desired name for the enumeration. The enumerations and their values are
declared and managed on the ES.
You can also enter a name in the input field for which no enumeration has yet
been defined.
Data type Shows the data type of the I/O (cannot be changed).
I/O Shows the I/O type (IN = input, OUT = output, IN_OUT = in/out parameter)
and cannot be changed.
Block type Shows the name of the block type from which the block originates (cannot be
changed).
Chart type Here, you can see whether the flagged I/O belongs to a CFC or SFC chart.
Process tag type Shows the name of the process tag type from which the process tag is derived
(cannot be changed).
*) Note: The column is hidden in the default setting, since this information is not normally
used in PCS 7. To display the column in the process object view, select the menu command
Options > Settings..., followed by the "Columns" tab, "Object types" group, and "Process
object view" folder. Here, select the desired entry and activate the option you require in the
"Visible columns" group.
Additional information
● Online help for PH, IEA and PO
"Messages" Tab
This displays the message texts of the signaling blocks belonging to the process tags and
CFC/SFC charts displayed in the "General" tab.
Processing
You can open the corresponding chart in the shortcut menu.
You can limit the number of objects selected for display by using a filter. You will find
additional information on this topic in Section "Working in the process object view
(Page 582)".
Each cell displayed in the table with a white background can be edited directly in the process
object view.
Note
If the message about a block is from a fail-safe program, the field with the line number is
displayed yellow at the beginning.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed).
Chart Shows the name of the process tag or CFC (cannot be changed).
Plan comments Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Shows the comment on the block. You can change the comment.
I/O Shows the name of the block I/O (cannot be changed).
I/O comment Input field for the comment on the block I/O. You can change the comment.
Sub number Sub number of the message (cannot be changed).
Class Message class as specified for the block type. You can select from a drop-
down list.
You cannot change the message class if it is locked in the block type
message.
Priority Message priority. You can select from a drop-down list.
You will not be able to change the priority under the following conditions:
• If it is locked in the block type message
• If the message was configured according to the old message concept
("message numbers assigned uniquely throughout the project")
Trigger action Initiates the "GMsgFunction" standard function (can be changed using "Global
Script" PCS 7 Editor)
Column Meaning
Origin Origin of the block. In PCS 7 the keyword $$HID$$ is used.
You cannot change the text if it is locked in the block type message.
OS area OS area text according to which the message list can be filtered online. In
PCS 7, the keyword $$AREA$$ is used.
You cannot change the text if it is locked in the block type message.
Event Input field for the event text (for example, "$$BlockComment$$ too high).
You cannot change the text if it is locked in the block type message.
Single Activate the check box, if the message should be acknowledged as a single
acknowledgment message.
Batch ID BATCH message text.
You cannot change the text if it is locked in the block type message.
Info text ( You cannot change the text if it is locked in the block type message.
Operator control/ Note: In addition to the "Info text" column, the tab also contains the "Free
Free Text 1-5) Text 1" to "Free Text 5" and "Operator control" columns. The columns are
hidden in the default setting, since these texts are not normally used in PCS 7
*).
Status 1-10 (32) *) In the status columns you specify in which operating states (Status 1 to
Status 32) the message is to be hidden in the process mode of the OS.
In the default setting, Columns 11 to 32 are not displayed.
The status columns can be modified under the following prerequisites:
• The block belonging to the message is contained in a block group.
• The CPU-wide message concept is set in the current project.
The default column headings are replaced by concrete operating states, if the
current selection only contains messages from block groups at whose SR
blocks (Status Representation blocks) the same listing type is configured. The
listing types contains the possible operating states in a list form.
Block group Shows the name of the block group whose blocks belong to a specific
message group and for which operating-state-specific automatic hiding of
messages is specified (cannot be changed).
Block type Shows the name of the block type from which the block originates (cannot be
changed).
Chart type Here, you can see whether the flagged I/O belongs to a CFC or SFC chart.
Process tag type Shows the name of the process tag type from which the process tag is derived
(cannot be changed).
*) Note: The column is hidden in the default setting, since this information is not normally
used in PCS 7. To display the column in the process object view, select the menu command
Options > Settings..., followed by the "Columns" tab, "Object types" group, and "Process
object view" folder. Here, select the desired entry and activate the required check box in the
"Visible columns" group.
Additional information
● Online help for PH, IEA and PO
Processing
The displayed interconnections and assignments cannot be edited. The tab essentially has a
cross-reference function, and is used to provide a fast overview of the existing or missing
picture interconnections and assignments of one or more process tags.
If you would like to modify the content of a picture, use the shortcut menu to also open the
WinCC Graphics of the selected OS picture (the shortcut menu can also be used to open the
CFC chart).
You can limit the number of objects selected for display by using a filter. You will find
additional information on this topic in Section "Working in the process object view
(Page 582)".
Each cell displayed in the table with a white background can be edited directly in the process
object view.
Note
If the operable block is a fail-safe block or if the operable connection is a structured
connection from a fail-safe program, the field with the line number is highlighted in yellow at
the beginning of the corresponding line.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed).
Chart Shows the name of the process tag or CFC (cannot be changed).
Plan comments Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Shows the comment on the block. You can change the comment.
I/O Shows the name of the block I/O or SFC I/O (cannot be changed). This row is
empty if a picture object is assigned to the block as a whole.
I/O comment Input field for the comment on the I/O. You can change the comment. This
row is empty if a picture object is assigned to the block as a whole.
Process tag Shows the name of the flagged I/O as specified for the process tag type
connector (cannot be changed). This row is empty if a picture object is assigned to the
block as a whole.
OS Displays the component path of the OS where the OS picture is located. In a
multiproject, the project name is also displayed in the path of an OS from a
different project (cannot be modified).
Picture Name of the OS picture (cannot be modified).
Picture object Name of the picture object, for example, faceplate, user object (cannot be
modified).
Property Name of the interconnected or assigned property of the picture object (cannot
be modified).
Block type Shows the name of the block type from which the block originates (cannot be
changed).
Chart type Here, you can see whether the OS picture is assigned to a CFC or SFC chart.
Process tag type Shows the name of the process tag type from which the process tag is derived
(cannot be changed).
Additional information
● Online help for PH, IEA and PO
● Configuration manual Process Control System PCS 7; Operator Station
Processing
The archive tags must first be created in WinCC Tag Logging. The attributes of the archive
tags can then be edited directly in the table (without opening WinCC Tag Logging).
When necessary, you can open WinCC Tag Logging from the shortcut menu.
You can limit the number of objects selected for display by using a filter. You will find
additional information on this topic in Section "Working in the process object view
(Page 582)".
Each cell displayed in the table with a white background can be edited directly in the process
object view.
Note
If the connection is a structured connection from a fail-safe program, the field with the line
number is displayed yellow at the beginning.
Column Meaning
Hierarchy Shows the technological path of the process tag or CFC (cannot be changed)
Chart Shows the name of the process tag or CFC (cannot be changed)
Plan comments Shows the comment on the object (cannot be changed)
Block Shows the block name (cannot be changed).
Block comment Shows the comment on the block. You can change the comment.
I/O Shows the name of the block I/O or SFC I/O (cannot be changed). This cell is
empty if an image object is assigned to the block as a whole.
I/O comment Input field for the comment on the I/O. You can change the comment.
Process tag Shows the name of the flagged I/O as specified for the process tag type
connector (cannot be changed).
OS Displays the component path for the OS containing the OS picture or the OS
report.
In a multiproject, the project name is also displayed in the path of an OS from
a different project (cannot be modified).
Archive name Name of the measured value archive (cannot be modified).
Variable name Input field for the name of the archive tag.
Variable comment Input field for the comment of the archive tag.
Column Meaning
Long-term archiving Indicates whether or not the archive tag is intended for long-term or short-term
archiving. Modifications made in this column have a direct effect on the
WinCC measured value archive without recompiling the OS. The changes
also affect the "Parameters" tab and the relevant block I/Os in CFC.
Variable supply Type of variable supply. You make the selection from a drop-down list
(system, manual input).
Archiving Here, you can specify whether archiving begins immediately at system
startup. You make the selection from a drop-down list (enabled, blocked).
Acquisition cycle Cycle for acquiring data. You can select from a drop-down list.
Factor for archiving Here you can specify the factor for the archiving cycle. The factor cannot be
cycle modified if the acquisition type is acyclic.
Archiving/display Here you can enter the cycle used for archiving and for displaying the data.
cycle You can select from a drop-down list. The cycle cannot be modified if the
acquisition type is acyclic.
Save on fault/error Here, you enter the type of correction if faults or errors occur. You make the
selection from a drop-down list (last value, substitute value).
Archive if Here, you specify the state change of the logical signal, the type of change,
and the time at which the change is archived. You can select from a drop-
down list. The entry is possible only for binary tags.
Unit Unit from the ES data management. This is only displayed here and can be
modified in the "Parameters" tab.
Data type Displays the data type of the I/O.
I/O Displays the I/O type (IN = input, OUT = output, IN_OUT = in/out parameter).
Block type Displays the name of the block type from which the block originates.
Chart type Here, you can see whether the archive tag belongs to a CFC or SFC chart.
Process tag type Displays the name of the process tag type from which the process tag was
derived.
Additional information
● Online help for PH, IEA and PO
● Configuration manual Process Control System PCS 7; Operator Station
Column Meaning
Hierarchy Shows the technological path of the hierarchy folder (cannot be changed).
Name of Shows the name of the hierarchy folder. You can change the name.
The maximum number of characters is specified in the "Plant Hierarchy -
Settings" dialog box (menu command Options > Plant Hierarchy > Settings...)
for each hierarchy level in the current project.
The name cannot be changed for hierarchy folders that are labeled as links
and for system-generated diagnostic folders.
Comment You can change the comment. The comment cannot be changed for hierarchy
folders that are labeled as links.
ISA-88 type This column is hidden by default.
It displays the ISA-88 type, which can be changed. All possible ISA-88 types
and <neutral> are offered in a drop-down list for the respective hierarchy level.
The ISA-88 type cannot be changed for hierarchy folders that are labeled as
links, or for system-generated diagnostic folders.
AS Displays the component path to the S7 program containing the hierarchy
folder.
You can display a drop-down list by clicking on an input field. If the project
contains several S7 programs, these are displayed in the drop-down list. By
selecting another S7 program, you can move the hierarchy folders with all
subordinate levels to this program or remove the assignment to the AS with
<not assigned>.
OS Shows the component path of the OS which contains the hierarchy folders.
You can display a drop-down list by clicking on an input field. If the project
contains several OS, these are displayed in the drop-down list. You can move
the respective object with all subordinate levels in this OS by selecting
another OS or remove the assignment to the OS with <not assigned>.
When you compile area-by-area, you can only change the OS assignment at
the hierarchy folder of the OS area level.
OS Area Identifier You can change the name for the hierarchy folder of the OS area level in this
column.
Column Meaning
Picture name for OS You can change the name of hierarchy folders below the OS area level in this
column.
Picture order You can change the picture order for the picture selection on the OS in this
column. The numbers in the drop-down list indicate the arrangement of the
pictures in descending order from left to right.
Author Input field for the name of the author. If SIMATIC Logon Service was activated
when a hierarchy folder was created, the user logged on at the time it entered
here.
Last modified You can see the date of the last change in this column (cannot be changed).
Additional information
● Online help for PH, IEA and PO
● Configuration manual Process Control System PCS 7; Operator Station
Column Meaning
Hierarchy Shows the path of the equipment property in the tree (cannot be changed).
Name of In this column, you select the desired name of the equipment property type
from the drop-down list for one of the available instances. The configured
attributes of the type are applied when the data is updated with <F5>.
Display name The display name can be in a foreign language and is transferred to WinCC
when the OS is compiled (cannot be changed). You can only change the
display name at the type ("Shared Declarations" tab).
Comment The comment of the type is displayed in this column when the instance is
created. You can change the comment.
Value You can assign the equipment property a value in this column. The syntax is
checked for conformity to the data type. If an enumeration is configured at the
type, you can select a configured value from a drop-down list.
Unit Shows the configured unit (cannot be changed). You can only change the unit
at the type ("Shared Declarations" tab).
Data type This column shows the configured data type (cannot be changed). You can
only change the unit at the type ("Shared Declarations" tab).
Enumeration If an enumeration is configured at the equipment property type, it is shown
here (cannot be changed). You can only change the enumeration at the type
("Shared Declarations" tab).
Author Input field for the name of the author. If SIMATIC Logon Service was activated
when an equipment property was created, the user logged on at the time is
entered here.
Additional information
● Online help for PH, IEA and PO
● Manual Process Control System PCS 7; SIMATIC BATCH
Column Meaning
Hierarchy Shows the path of the object in the tree (cannot be changed).
Name of Shows the names of objects, contained in the folders of the shared
declarations.
Display name The display name can be in a foreign language and is transferred to WinCC
when the OS is compiled. The display name can only be changed for the
enumerations and for equipment property types.
Comment Shows the comment on the object. You can change the comment.
Type Shows the type name of the object. Type names are: enumeration, value, unit
of measure, equipment property (cannot be changed).
Value Shows the configured values of the enumerations. You can change the value.
The fields are empty for units of measure and equipment properties.
Unit This column shows the configured units for the equipment property. You can
change the unit by selecting another from the drop-down list. The fields are
empty for enumerations and units of measure.
Data type Show the configured data type for the equipment property. You can change
the data type by selecting another from the drop-down list. The fields are
empty for enumerations and units of measure.
Enumeration Shows the configured enumeration for the equipment property. You can
change the enumeration for the INT, DINT, SOURCE, DEST and VIA data
types by selecting one from the drop-down list. The fields are empty for
enumerations and units of measure.
Control strategy Shows if the enumeration involves a control strategy (check box is activated).
You can change the attribute.
Author Input field for the name of the author. If SIMATIC Logon Service was activated
when a shared declaration was created, the user logged on at the time is
entered here.
The check boxes are empty for units of measure and equipment properties.
Version Shows the current version of the configured types: enumerations, units of
measure and equipment properties. You can change the version.
Additional information
● Online help for PH, IEA and PO
Tab Description
General In this tab, it is not possible to delete, move, or copy objects. Apart from the "AS" column, all the
columns remain editable if they can be modified in offline mode.
When test mode is activated, changes in the "Activated", "Simulate inputs" and "Simulate outputs"
columns are saved in the engineering station and downloaded to the AS. This also applies if the
process tag or chart is not registered for the test.
"Parameters" and In these tabs, the columns "Watch", "Value" and "Watched" can be edited.
"Signals" When test mode is activated, changes in the "Value" and "Watches" columns are saved in the
engineering station and downloaded to the AS. This also applies when the I/O is not registered for
the test.
A faulty or undefined value is indicated with "####".
Dynamic values are shown on a different background according to their status as follows:
• Yellow (dynamic, can be changed)
• Gray-yellow (dynamic, cannot be changed)
• Red (failed)
The color of the field changes from yellow to white when it is clicked on to edit the value. The offline
value is then shown.
Additional information
● Online help for PH, IEA and PO
Introduction
The PCS 7 operator station (OS) is configured in various substeps. The configuration is
carried out using several PCS 7 tools:
● In the SIMATIC Manager
● In the WinCC Explorer
The entire configuration of the OS is carried out in the engineering system so that all the
configuration data can be managed centrally.
Depending on the requirements of your project, some of the steps in configuration are
mandatory and others optional.
For a completed description of configuring the OS functions, refer to the Configuration
Manual Process Control System PCS 7; Operator Station.
Below you will find preliminary information in the form of a table listing all the configuration
steps. From the table, you can see which configuration steps are necessary and which are
options.
SIMATIC Manager
Compiling the OS
You must run the "Compile OS" function once you have completed ES configuration of all
data in the SIMATIC Manager, and before you start to configure the OS data in the WinCC
Explorer. You must also compile the OS if you subsequently changed the ES configuration.
All the data from the SIMATIC Manager, such as variables, messages, texts, and the
hardware and connection configuration is "made known" to the OS for further configuration.
WinCC Explorer
Additional information
● Configuration Manual Process Control System PCS 7; Operator Station.
Introduction
With the OS "Lifebeat Monitoring" function, you can monitor the functions of the CPUs and
operator stations connected to the plant bus in PCS 7. This means that you always have an
up-to-date overview of the state of your plant.
The monitoring function is executed from the operator station declared as the lifebeat
monitor.
Lifebeat Monitor
The lifebeat monitor monitors all OS servers, OS clients and all automation systems.
Requirements:
All the components to be monitored are connected to a continuous network and assigned to
the lifebeat monitor. The monitoring is performed in a cycle that you can specify when
configuring lifebeat monitoring.
The lifebeat monitoring is configured in the WinCC "Lifebeat Monitoring" editor.
Additional information
You will find step-by step instructions on configuring the AS/OS lifebeat monitoring in the
configuration manual Process Control System PCS 7; Operator Station.
Introduction
SIMATIC BATCH is a PCS 7 program package that enables discontinuous processes,
known as batch processes, to be configured, planned, controlled and logged.
Simple batch processes with configurable sequential control systems are automated with the
CFC and SFC tools included in the PCS 7 Engineering System. In more demanding systems
with recipe procedures, SIMATIC BATCH is used.
With SIMATIC BATCH, recipe structures are designed, modified, and started graphically on
an operator station or on a separate PC.
Configuration involves the following:
● Engineering
● Rights Administration
● Recipe Creation (offline)
● Process mode
Engineering
Configuration of the batch process cell takes place along with the basic engineering of the
S7-400 on the engineering station in the SIMATIC Manager (for example, phase and
operation types, equipment properties, user data types, units of measure).
Rights Administration
SIMATIC BATCH uses the PCS 7 central user management.
Process mode
The first phase of process mode is batch planning. The production orders are created here.
These are divided into batch orders that can then be approved and started. The actual Batch
processing programs (equipment phases) run on the automation system and are coordinated
by the batch control.
The batch data management makes use of individual WinCC components. The values for
the required measured value sequences for a batch report are obtained from the measured
value archive and all Batch-relevant messages are filtered from the message archive and
displayed within BatchCC.
Additional information
● Online help for SIMATIC BATCH
● Manual Process Control System PCS 7; SIMATIC BATCH
Introduction
SIMATIC Route Control is a program package from PCS 7 for automating the transport of
materials in plants.
SIMATIC Route Control searches for a route through the sections of the available route
network and controls the material transport, for example, by opening valves and activating
pumps.
SIMATIC Route Control includes both the configuration and the runtime system and offers
numerous interfaces to the PCS 7 base system and to the user programs.
Depending on the plant design, both straightforward transport processes and complex route
combinations are possible.
The configuration tasks involve the following:
● Engineering
● Permission management
Engineering
The PCS 7 project is the central configuration environment including the data storage.
You configure the following here:
Rights Administration
The central user management from PCS 7 is used for SIMATIC Route Control.
Additional information
● Online help for SIMATIC Route Control
● Manual Process Control System PCS 7; SIMATIC Route Control
Introduction
To enable access to the PCS 7 data, assign the OS server data to the OpenPCS 7 station
and download the configuration data.
Requirements
● The OpenPCS 7 station has been created.
● The target path of the OpenPCS 7 station has been entered.
Procedure
1. Open the project in the SIMATIC Manager and activate the component view.
2. Select the OpenPCS 7 station in the tree view:
SIMATIC PC-Station > SPOSA application > Open_PCS7_Station
3. Select the menu command Options > OS > Assign OS Server....
The "Assignment of OS Server for <name of OpenPCS 7 station>" dialog box opens.
4. Activate the check box of the OS server whose server data you want to assign to the
OpenPCS 7 station selected above.
5. Click "OK".
6. Select the menu command CPU > Download.
The OpenPCS 7 station is configured and loaded.
Note
Ensure appropriate access protection for your OPC client application.
Additional information
● Section "How to insert and configure an OpenPCS 7 station (Page 285)"
● Section "Connecting to the IT world via OpenPCS 7 (Page 123)"
● Section "Structure of the OpenPCS 7 station (Page 172)"
● Manual SIMATIC NET; Industrial Communication with PG/PC
● System manual SIMATIC HMI; OPC - OLE for Process Control
● Manual Process Control System PCS 7; PC Configuration and Authorization
8.15.2 How to configure the OpenPCS 7 stations for accessing historical alarms in a
central archive server
Introduction
Transparent OPC A&E access to historical alarms in a central archive server (CAS)
If, while reading messages on an OS (via OPC Alarms & Events), you also wish to access
messages relating to this OS that are located in an archive on a central archive server,
assign the central archive server to the OpenPCS 7 station and download the OpenPCS 7
station.
Requirement
● The OpenPCS 7 station has been created.
● The target path of the OpenPCS 7 station has been entered.
Procedure
1. Open the project in the SIMATIC Manager and activate the component view.
2. Select the OpenPCS 7 station in the tree view:
SIMATIC PC-Station > SPOSA application > Open_PCS7_Station
3. Select the menu command Options > OS > Assign OS Server....
The "Assignment of OS Server for <name of OpenPCS 7 station>" dialog box opens.
4. Activate the check box of the central archive server whose server data you want to assign
to the OpenPCS 7 station selected above.
5. Click "OK".
6. Select the menu command PLC > Download.
The OpenPCS 7 station is configured and downloaded.
Open PCS7 - Transparent OPC A&E access to historical alarms (historical A&E) on a central archive
server (CAS)
If, while reading messages on an operator station, you wish to use OPC Alarms & Events to
gain additional access to messages for this OS that are stored in an archive on a CAS, then
you will need to carry out the following configuration steps:
1. In the tree view, select the OS object:
SIMATIC PC station > WinCC Appl. > OS(x)
2. Select the menu command Options > OS > Assign OS Server... to assign the CAS to the
OS server.
The "Assignment of Server to OS(x)" dialog box opens.
3. Select the CAS and click "OK".
4. Deactivate the "All servers" check box for all alarm controls of the OS server
and select only those servers (with the exception of the CAS) whose messages are to be
displayed.
Note
When a time range is specified in an alarm control, the messages archived in the CAS
are automatically included - even if the CAS was not one of the servers selected.
Additional information
● Section "How to configure OpenPCS 7 stations for accessing PCS 7 data (Page 617)"
Overview
Merging projects of a multiproject following distributed editing involves the following topics:
● How to Move Projects Edited on Distributed Stations to the Central Engineering Station
(Page 622)
● Merging Subnets in the Multiproject Across Projects (Page 624)
● Merging Connections Across Projects (Page 625)
● How to Configure New Cross-Project Connections Between AS and OS (Page 626)
CAUTION
For multiproject engineering with SIMATIC BATCH, distributed engineering on distributed
engineering stations including testing is only possible when certain conditions are met and
the additional steps are taken.
You will find additional information on this topic on the Internet
(http://support.automation.siemens.com/WW/view/en/23785345).
8.16.2 How to Move Projects Edited on Distributed Stations to the Central Engineering
Station
Requirements
● The project is physically located on a distributed engineering station and is included in the
multiproject.
● The distributed engineering station is obtainable over the network.
Procedure
1. If necessary, delete the existing project of the same name (version prior to moving to
distributed engineering station) on the central engineering station (backup copy).
2. Use the menu command File> Open... in the SIMATIC Manager to open the project from
the central engineering station on the distributed engineering station
3. Click the "Browse" button.
4. Go to the "Browse" menu and enter the path of the project being moved in UNC notation
in the "Search in directory" field.
5. Click "Start Search".
The project is displayed in the "User projects" tab.
6. Select the required project in this tab and click "OK".
The project opens.
7. Select the menu command File> Save as ....
8. Make the following settings
– Disable the "With Reorganization (slow)" check box.
– Enable the "Insert in multiproject" option.
– Select the "Current multiproject" entry in the corresponding drop-down list.
– Enable the "Replace current project" check box.
9. Click "OK".
Result
An identical copy of the distributed engineering station project is created on the central
engineering station in the multiproject. The original is retained on the distributed engineering
station and can remain there as a backup or be deleted.
Rules
Note
Before the copied project can be copied back to its old location (same directory name), this
backup has to be deleted or renamed on the central engineering station. You can find
additional information about this in the following section: "How to Move Projects to
Distributed Engineering Stations (Page 348)"
Note
You can also move a project back to the central engineering station if it was moved out with
the "Remove to edit..." function and provided that it can be accessed via the same path that
was used during its removal:
1. Select the project labeled "project removed for editing" on the central engineering station
(grayed out).
2. Select the menu command File > Multiproject > Reapply after Editing....
The project is reincorporated from the distributed engineering station into the multiproject
on the central engineering station.
Additional information
● Section "How to Move Projects to the Central Engineering Station (Page 348)"
Introduction
If you use cross-project networks in the multiproject, the networks in the projects must be
merged back into the multiproject.
Requirement
Writing access to the participating projects and their subnets is possible.
Procedure
1. Select the required multiproject in the SIMATIC Manager
2. Select the menu command File > Multiproject > Synchronize Projects....
The "Synchronize Projects in Multiproject <xxx>" dialog box opens.
3. Go to the left window and select the Ethernet networks you want to connect and click
"Execute".
The dialog box for merging/separating the subnets opens.
4. In the left field, select the subnet and click "->".
The selected subnet is merged in the selected overall network.
5. Change the default name of the cross-project network according to the requirements of
your project (click the name twice).
6. Follow the same procedure for all the subnets you want to merge.
7. Click "Apply" and then "Close" in order to close the dialog box.
In the same dialog box you can separate those networks that have already been merged.
In this dialog box, you can also create new cross-project subnets ("New" button).
Check Consistency
After merging the subnets and prior to downloading to NetPro use the menu command
Network > Check Cross-project Consistency to check whether there is consistency
throughout the multiproject.
Procedure
Cross-project connections can be merged as follows:
● During synchronization of projects in a multiproject in the SIMATIC Manager, using the
menu command File > Multiproject > Synchronize Projects....
● In NetPro with the menu command Edit > Merge Connections....
Sequence
The following variations occur in the sequence:
Additional information
● Online help on STEP 7
● Section "How to Merge Cross-Project Connections (Page 455)".
Introduction
Cross-project connections between AS and OS components are configured in the same way
as cross-project connections between AS components.
Requirements
● The networks involved are merged at multiproject level.
You can find information about this in the section "How to Merge Subnets from Different
Projects into a Multiproject (Page 624)"
● The AS/OS assignment is specified.
You will find additional information on this topic in Section "How to Specify the AS/OS
Assignment (Page 300)"
Procedure
When creating cross-project connections between AS and OS components, in contrast to the
procedure described in the section "Cross-project Connections in a Multiproject (Page 453)",
you select a connection partner in a different project.
Import/Export Functions
All the essential applications of the PCS 7 engineering system have import/export interfaces.
The use of these import/export interfaces has the following advantages:
● Plant-planning data can be harmonized with control-system engineering data. This is how
control system engineering and plant engineering can be independently edited at the
same time.
● Data from the engineering system can be exported as a template, be effectively
duplicated and adapted in an external program (such as MS Excel) and then be imported
back into the engineering system. This allows the configuration of repeated or similar
plant information to the optimized.
Described as Follows
The following import/export functions are described in the following sections:
● Import/export of process tags/models
● Import/Export of the Hardware Configuration
Introduction
The starting point for mass data processing is to identify repeated functions.
Additional information
● Section "How to Create a Process Tag Type from a CFC Chart (Page 518)"
● Section "How to Create a Model (Page 570)"
Note
The Import/Export Assistant (IEA) is an option package in itself in PCS 7, which requires an
own authorization.
The IEA is supplied together with the PH and the process object view on the PCS 7-Toolset
DVD. The programs are also installed together.
'HILQH
PRGHO
(6GDWDPDQDJHPHQW 3ODQQLQJV\VWHP
)XQFWLRQXQLWV
$VVLJQ ,2VLJQDOV
LPSRUWGDWD
,($ ,QWHUFRQQHFWLRQDQG
ILOH SDUDPHWHUGHVFULS
WLRQ
&RS\DQG
SDUDPHWHUL]H
PRGHO
,PSRUW
H[SRUW
ORJ
8SGDWH
SODQQLQJV\VWHP
Overview
Working with process tag types and models in the import/export wizard includes the following
subjects:
● Requirements and Steps in Configuration (Page 630)
● Functions for Working with Process Tags and Models (Page 633)
● How to Create an Import File and Assign it to the Process Tag Type (Page 523)
● What happens during import? (Page 637)
● How to Import Process Tag Types and Models (Page 639)
● What happens during export? (Page 642)
● How to Export Process Tag Types and Models (Page 643)
● Restrictions with the IEA (Page 644)
Requirement
The process tag types and/or models have been created in the master data library.
0DVWHUGDWDOLEUDU\ 'DWDIURPWKHSODQW
HQJLQHHULQJ
:L]DUG$VVLJQFUHDWHLPSRUWILOH
$VVLJQHGLPSRUWILOH
3URFHVVWDJW\SH%
'DWDIRUSURFHVVWDJ
3URFHVVWDJW\SH$
'DWDIRUSURFHVVWDJ
3URFHVVWDJW\SH;
'DWDIRUSURFHVVWDJ;
0RGHO$ $VVLJQHGLPSRUWILOH
0RGHO%
0RGHO;
$VVLJQHGLPSRUWILOH
:L]DUG,PSRUWSURFHVVWDJ
:L]DUG([SRUWSURFHVVWDJ
:L]DUG6\QFKURQL]HSURFHVVWDJ
$VVLJQHGLPSRUWILOH
'DWDIRUSURFHVVWDJ
'DWDIRUSURFHVVWDJ
'DWDIRUSURFHVVWDJ;
:L]DUG,PSRUWPRGHO
:L]DUG([SRUWPRGHO
$VVLJQHGLPSRUWILOH
'DWDIRUSURFHVVWDJ
'DWDIRUSURFHVVWDJ
'DWDIRUSURFHVVWDJ;
Start IEA
You start the Import/Export Assistant in the SIMATIC Manager either in the plant view or in
the process object view after selecting a hierarchy folder. (Single process tag types can also
be selected when working with process tag types.)
From the Options menu select the menu command Process tag or Models and then, in the
following submenu, the required function.
Additional information
● Online help for PH, IEA and PO
Introduction
With the Import/Export Assistant (IEA), you can work with process tag types and their
process tags or models and their replicas. The IEA provides functions for reusing and
adapting the process tag types/models.
Rules
● When working with the "import/export" functions of the Import/Export Assistant, further
hierarchy folders may be contained in the model.
● Only one OS picture per hierarchy folder may exist if the picture hierarchy is derived from
the PH.
● If the model includes nested hierarchical folders, they may not be renamed.
Additional information
Tip
Note
In order to increase the clarity of the charts switch the model block I/Os that you do not
require to invisible.
If you edit later in the IEA, you will see the selections set in the CFC in the process object
view and can correct them there if necessary. The same applies to selections in models.
Note
An interconnection is deleted when the signal name (symbol or textual interconnection)
consists of the code word "---" (three dashes).
An interconnection remains unchanged, if no interconnection name (symbol or textual
interconnection) is specified.
4. The I/O data types for signals are determined and assigned to the interconnections.
Note
The rule for interconnections with shared addresses is as follows: if the "Include signal in
the symbol table" option is set, the names can be found in the model resource symbol
table.
With PCS 7, we recommend that you do not use the option because these entries are
made when you configure the hardware with HW Config.
Sequence
Use the assistant for process tags or models to import the following data:
● Process tag typedata
The process tag type is copied from the master data library to the specified target
projects as a process tag and the data are then imported. Any number of process tags
can be created, depending on the entries in the import file.
As a result of the import, a process tag of this process tag type is created in the target
project for every row of the import file according to the specified hierarchy path.
● Modeldata
The model is copied from the master data library to the specified target project as a
replica and the data are then imported. You can create any number of replicas according
to the entries made in the import file.
Note
When you import a process tag or model, you can decide whether or not the imported
signals will be entered in the symbol table (option: "Also enter signals in the symbol
table").
With PCS 7, we recommend that you do not use the option because these entries are
made when you configure the hardware with HW Config.
Note
Before importing, check the language set for display. If you created the model in German
and if the current setting of the SIMATIC Manager is "English", the German message
texts will be written into the English text file.
Procedure
1. Select the desired hierarchy folder, project node / process tag library (hierarchy folder in
the master data library), or the process tag type.
2. Select the menu command Options > Models > Import...
or Options > Process Tags > Import....
The wizard searches for the models/process tag types and corresponding import files (in
all hierarchy subfolders as well), and lists them. The import function will include all listed
import files.
3. If you do not want to import certain files, you can select them and remove them from the
list with the "Remove" button.
By clicking "Other File...", you can search for a different import file and select it instead of
the other file.
4. Click "Continue" and then "Finish".
Result
The actual import process starts. Depending on the setting of the "Only show errors and
warnings in log" check box, the complete list of import activities or only the errors that
occurred are displayed in the log window.
The log is saved in a log file. The name and path of the file are displayed below the log
window. You can modify this setting with the "Other File" button.
In the following figure, both models and their replicas are shown as they appear in the
SIMATIC Manager.
Note
When you import, all the rows with the "delete" keyword are processed first and the
subjects deleted. Only then are new objects created.
If you have already created interconnections to the replicas, these will be lost.
Options
You can export data for models or process tags by using the assistant. The following options
are available:
● Individually select a model/process tag type to export it by itself.
● You can select an upper level hierarchy folder or the project node in order to export all
lower level models (replicas) or process tags.
This results in an export file that contains a line for each located replica of a model or for
each process tag of a process tag type.
The structure of the export file corresponds to that of the import file.
Procedure
1. Select the desired hierarchy folder, project node / process tag library (hierarchy folder in
the master data library), or the process tag type.
Note
After selecting a replica you are forwarded to the corresponding model in the master data
library after the prompt.
Result
The export procedure starts. Any existing export files are overwritten during the export
procedure.
Repeated export
By exporting the model(s)/process tags more than once, you can create several export files
(copies). During the export procedure you must modify the file name of the assigned export
file. If you do not change the file names the export file with the same name is overwritten.
Introduction
The following sections explain how to create and edit the import/export files (IEA file) with the
IEA file editor. The description includes the following topics:
● Creating/Editing Import Files with the IEA File Editor (Page 646)
● Exchanging Data with Excel/Access (Page 648)
● Structure of the IEA File (Page 650)
3URMHFW
3ODQW
KLHUDUFK\
,PSRUWILOH
+LHUDUFK\ 3DUDPHWHU 3DUDPHWHU 6LJQDO 0HVVDJH
LQWHUFRQQ
+? 3, 6, 6, 0,
9?5$?3 9DOYHRSHQ ,QWHUUXSW
9?5$?7 9?5$?39 +HDWLQJRQ ,QWHUUXSW
Additional information
● Online help for the PH, IEA, PO and IEA file editor
Introduction
The import/export data (IEA file) is available as a text file in CSV format. The CSV format is
supported by many applications (MS Excel, MS Access, etc.) and is therefore suitable as a
general data interface between any planning tool and the ES. In IEA these files are expected
to have the *.iea extension. You may have to change the extension.
CSV (Comma Separated Value) is an ASCII text format used for storing data configured in
the form of a table. The character separating the cells depends on the Regional and
Language Options in the operating system (German: semicolon); a new row is created by
pressing Enter.
You can create and edit a CSV file with spread sheet programs (for example, MS Excel) or
as an export file from a database (dBase, Access, etc.). You can also conveniently edit the
file (with the extension *.iea) using the IEA File Editor.
Note
If you open a CSV file by double-clicking it, the content of the file is not shown in table
form in Excel.
All cells should be formatted as "Text", otherwise the displayed information may be
incorrect. Example: The numeric string "1.23" could be displayed as "23 Jan.".
File Structure
There must be a column group for each I/O and message.
Row Meaning
0 There can be a comment line before the first header (starting with "#" or "//") containing both the version number
and the date created.
1 The first header row contains the titles of the column groups.
2 The second header line contains the column identifiers. This information tells the Import/Export Assistant how to
interpret the columns. These identifiers are the same in all language versions.
3 The third header row contains the keywords for the relevant flagged I/O. This decides which data will be
imported for this I/O. Not every keyword must be entered; only the first one is mandatory.
4-x The next rows contain the data. There is one row for replica or process tag. During import, each row generates
a replica of the model in the specified hierarchy folder. With process tags, the process tag is created in the
hierarchy folder.
Project; Hierarchy; FID; LID; Chart; High limit; Measured value Alarm high
Prj; H\; F; O.; C|; P|; S|; M|
; ; ; ; ChName| Value| SymbolName| Event|
ChComment; ConComment| SymbolComment|
S7_shortcut| ConComment|
S7_unit; S7_shortcut|
S7_unit;
Pro_A V12\RA1\P01; ; ; P01|Internal 90|Com.| Tpress|ComS.| Int. pressure
pressure; OG|mbar; ComA.|PK|mbar; too high
Pro_A V12\RA1\P02; ; ; P02|External 8.5|Com.| Apress|ComS.| Ext. pressure
pressure; OG|bar; ComA.|PK|bar; too high
Pro_A V12\RA2\T01; ; ; T01|Temp contr 90|com.| Mtemp.|ComS.| Temperature
OG|degC; ComA.|MT|degC; exceeded
Pro_B V12\RA2\T02; Delete
Additional information
● Online help for PH, IEA and PO
Introduction
You can work on station configurations not only within the entire project (for example, saving
or opening), but also independent of the project by exporting it to a text file (ASCII file, CFG
file), editing it, and then importing it again. In this way the symbolic names of the inputs and
outputs are also exported or imported (as long as you have not changed the default setting).
Application
You can use the import/export of the hardware configuration to do the following:
● To import hardware planning tool data
● To distribute data using electronic media (for example, e-mail)
● To print the export file using a word processor or to continue processing the export file for
the purpose of documentation
Another important application of importing a station configuration exists in a plant when
identical or almost identical configurations in different parts of the plant occur. Using the
import function, you can create the required plant configuration quickly.
What is Exported/Imported?
When you configure the hardware, the data necessary for the configuration and parameter
assignment of modules are exported/imported.
The following data are not collected:
● Data managed by other applications (for example, programs, connections, shared data)
● A selected CPU password
● Cross-station data (for example, the linking of intelligent DP slaves or configurations for
direct data communication)
Note
If your configuration contains modules from older option packages, it is possible that not
all the data of the module will be included with the "Export Station" function. In this case,
check whether the module data are complete following the import.
Procedure
1. Select the required station in the component view.
2. Select the menu command Edit > Open Object.
The station configuration opens in HW Config.
Result
The station configuration is exported and stored in the selected path in the form of a CFG
file.
Export Settings
● Legible or compact format
– In the legible format the parameter identifiers are entered in the export file as strings.
– In the compact format the identifiers are entered in the export file in hexadecimal
format.
NOTICE
When you export the station configuration to read it in using other PCS 7 versions,
select the "Compact" option.
CAUTION
If you export a station configuration with symbols, you can no longer import the file with
earlier PCS 7 versions.
Additional information
● Online Help for HW Config
CFG File
The procedure for exporting the station configuration described in the section "How to Export
a Station Configuration (Page 653)" results in an ASCII file, which you can view and edit in a
text editor such as "Notepad" or "WordPad".
This file (CFG file) contains all the data of the hardware configuration including the
parameter assignments from the dialog boxes of the HW Config graphic user interface and
the corresponding symbols (if these were exported).
Based on the introductory text in the individual fields, the sections are easy to identify.
You will find a section from a possible CFG file structure in the following example.
Example
Additional information
● Online Help for HW Config
Expansion
CFG files should always be created based on an existing exported station configuration. You
can find information about this in the section "How to Export a Station Configuration
(Page 653)".
The CFG file should already contain all the objects (passages of the file) required for station
expansion. This allows you to make the required expansions simply by copying and pasting.
Keep the configuration consistent, the copied objects must be adapted accordingly (for
example, rack assignment, addresses, symbols).
For an explanation of the structure and content of the CFG file, refer to the section "Structure
and Content of the CFG File (Page 655)".
With this as a basis, you can edit the individual sections of the file to suit your purposes
(copy, paste, edit).
NOTICE
You should be familiar with the content of the sections of the CFG file in detail since editing
is not supported by the system. Errors will only be detected during the subsequent import.
This can lead to inconsistent data that you would then have to re-edit in HW Config.
Procedure - Example
You want to add a further digital input module to an ET 200M and change the existing slot
assignments.
1. Identify the area you want to change.
Additional information
● Online help for HW Config
Procedure
Recommendation: Do not import a station configuration that was previously exported from
the same project. In this case, PCS 7 cannot handle the network assignment. Select a
different or new project for the import. Use the following procedure:
1. Select the HW Config menu command Station > Import... while an empty station
configuration is open.
If no station configuration is open, a dialog box opens in which you select a project. In this
case, navigate to the project into which you want to import the station configuration.
2. Use the open dialog box to navigate to the CFG file you want to import.
3. Click "OK".
The station configuration is imported. During import, the imported file is checked for errors
and conflicts and messages are displayed.
Note
If you also want to import DP master systems during import, these must not have the
same names as DP master systems that already exist in the project.
Additional information
● Online help for HW Config
9.2.5.6 How to Import an Expanded Import File (Extra Remote I/O, Field Device, Module)
Additional information
● Online help for HW Config
9.2.5.7 How to Update an Imported Station Configuration (Change Attributes, Signal Assignments
of Modules)
Note
The import process is much quicker if only the changed parts are overwritten.
2. Save the error log if one is generated. You can then eliminate any errors based on the
log.
3. KClick "Yes", in order to store the imported data.
Selecting "No" will terminate the import process. The station configuration then remains
unchanged.
Additional information
● Online help for HW Config
Overview
The functions for compiling and downloading are available in the following editors:
● HW Config
Compiling and downloading the hardware configuration
You can find further information about this in the section "Hardware Configuration".
● NetPro
Compiling and downloading the network and connection configuration from the hardware
configuration
You can find further information about this in the section "Creating Network Connections".
● CFC
Compiling and downloading the CFC configuration
You can find information about this in the section "Creating CFC Charts".
● SFC
Compiling and downloading the SFC configuration
You can find information about this in the section "Creating SFC Charts".
● SIMATIC Manager
Compiling and downloading individual or all objects in a multiproject.
Note
OS server data must only be downloaded once after the initial download to the OS
clients. Each time an OS client is restarted in process mode or when downloading
changes to the OS server, the OS server data is automatically updated.
Note on ensuring that the OS server data is up-to-date: the server data includes the
computer name of the engineering station from which the data was first downloaded. If
you change engineering stations or change the storage location of the project/multiproject
on the engineering station, make sure that the OS is recompiled and remember that the
server data must be downloaded once from the new computer (computer name) or
storage location.
The compiling and downloading of the OS and the updating of the OS server data on the
OS clients is described in detail in the configuration manual Process Control System
PCS 7; Operator Station and is therefore not dealt with in detail here.
Initially you only need to compile and download the AS data in order to test the program or
the CFC and SFC configuration.
Overview
The sections about compiling and downloading for PCS 7 deal with the following topics:
● Requirements for Compiling and Downloading (Page 667)
● Downloading to all PLCs (Page 668)
● Options for compiling and downloading (Page 673)
● How to Document Changes in the ES Log" (Page 676)
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
Introduction
Use the "Compile and Download Objects" central function to download an entire
project/multiproject. PCS 7 provides the "Compile and Download Objects" dialog for this
task. This dialog box displays the objects exactly the same way as in the SIMATIC Manager
component view. All of the automation systems, operator stations, and SIMATIC PC stations
that you created in SIMATIC Manager are displayed.
Use the "Compile and Download Objects" dialog box , to centrally carry out all of the
required settings for compiling and downloading. In addition this is where you can specify,
whether you want to compile and download the entire project or, for example, only individual
operator stations.
Note
If you select the SIMATIC 400 station in the SIMATIC Manager, followed by the menu
commands PLC > Download or PLC > Compile and Download Objects... ("HW Config"
object activated for compiling and downloading), the delta downloading capability will be lost.
Requirements
● The PC stations and automation systems are configured and downloaded from NetPro
(the connections are also downloaded)
● The CFC and SFC configuration is completed.
● You have selected one of the following objects in the SIMATIC Manager:
– Multiproject
– Project
– Station
– S7 program without station assignment
Rules
● A complete automation system download is only possible when the CPU is in the STOP
operating mode.
● Downloading the entire program to an OS is only possible when the OS servers are shut
down (are not in process mode).
● Downloading changes to an OS is possible only if the OS is in process mode.
● When you have made changes during commissioning, we recommend you synchronize
the projects of the multiproject before downloading to the target system. To do this, select
the menu command File > Multiproject > Synchronize Projects.... You can the use the
central "Compile and Download Objects" function to send the changes to the target
system.
Procedure
Note
You should also read the information in the section "Options for Compiling and Downloading
(Page 673)".
1. Select the object that you want to compile or compile and download in the SIMATIC
Manager.
2. Select the menu command PLC > Compile and Download Objects... in the SIMATIC
Manager.
The "Compile and Download Objects" dialog box opens.
3. Open the tree view and activate the corresponding checkboxes in the "Compile" or
"Download" columns for all objects that you wish to compile and/or download.
If you tick both checkboxes for an object, the object is compiled and then downloaded.
Activate the corresponding checkbox on the "Connections" object if you want to compile
the and download connections.
4. Use the "Status" and "Operating Mode" buttons to check the statuses (changed,
compiled, downloaded, etc.) and modes of your objects (RUN, activated, etc.), so that
you can make the correct settings for compiling and downloading.
5. Select the object you want to compile and/or download and click "Edit".
Enter the settings for compiling and/or downloading (for example, compiling and
downloading the entire program or only changes).
Note
When you have completed the settings for compiling an operator station, it takes some
time for the compiling settings to be saved and for the download dialog box to be opened!
The target path of the OS should already be entered here (but if it is not, enter it).
6. Click "Check.
This checks the validity of the settings. If settings are not valid, the download is not
performed.
7. Perform the required settings for the individual objects.
Click "Help" in the dialog box for detailed information about the settings.
8. Activate the "Compile only" option if you only want to check the blocks and not download
them to the CPU.
9. Activate the "Do not load if compilation error is detected" option if you want to prevent
downloading corrupt blocks to the CPU.
10.Click "Start".
The compilation/download operation is started.
11.Follow the instructions on the screen.
12.If you wish to see a log once the compiling/downloading is completed, click the following
buttons in the "Open Log" area:
– "Single Object" - The detailed compilation and download log of the selected AS or the
compilation log of the selected OS is displayed.
– "All" - The results of all compiling and download actions (without details) are
displayed.
Note
Do not use the "Compile and Download Objects" function for S7 PLCSIM
downloading.
Note
If the "Marked parameters“ checkbox is activated, only the block I/Os with the "Can be
read back" attribute (S7_read_back = true) are read back. This setting must first be
entered at the I/Os of the block type. The attribute cannot be modified in the block
instances.
5. Click "OK".
Note
A complete compiling of the charts is automatically carried out if they are read back.
Additional information
● Section "Options for Compiling and Downloading (Page 673)"
● Online help on the "Compile and Download Objects" dialog box
Option Description
Settings for Compilation/Download
"Edit..." button Opens a dialog in which the compiling and downloading settings can be
changed for object selected in the "Objects" column.
"Check" button Checks the compiling and downloading properties of objects selected for
compilation or download in the "Objects" column.
This button is not active for block folders. The button is only active if the
objects support this function.
The following is checked for a "hardware" object:
• Are the modules in the STOP mode (not with modules that automatically
stop and can be started again, for example, CPs)?
• If password protection has been configured and a password has been
entered: the entry takes place via the "Edit" button with the selected block
folder or CPU.
Update
"Status" button Updates the current status of the objects in the selection table.
With the "Hardware" object, "undefined" is displayed after a status update if
the station contains a cross-station PROFIBUS subnet. In this case, the editing
of the other station that is also connected to this PROFIBUS subnet can have
effects on the currently displayed station.
"Operating Mode" button Updates modified operating modes in the display.
"Status on opening" check box When the check box is deactivated (default), the "Compile and Download
Objects" dialog box opens immediately after the menu command CPU >
Compile and Download Objects... is selected. undefined" is however entered
everywhere in the "Status" column. To update for the first time, click the
"Status" button.
When the check box is activated, expect a long delay before the dialog box
opens regardless of the number of objects.
Option Description
View log
"Single Object" button Shows the log of the most recent compilation or download process for the
object selected in the "Objects" column
"All..." button Opens the "Open Log" dialog box where you can select the type of full log.
This may be the log of the most recent compilation or of the most recent
download process or the last "Settings for Compilation/Download" check log
that was generated by pressing the "Test" button.
The full log lists all messages for the individual objects.
Select Objects
"Select All" and With this button, you can select or deselect all objects in the "Compile" or
"Deselect All" buttons "Download" columns.
If the "Compile Only" check box is selected, the button only affects the
"Compile" column. If the "Compile Only" check box is deactivated, the "Select
All " and "Deselect All" buttons select or deselect all objects in both columns.
"Compile only" check box Activate this check box if you only want to compile the selected objects. The
objects will not be downloaded to the CPU and the "Download" column is
hidden.
"Do not load if compilation error is If the check box is activated, a compilation error (for example, a time stamp
detected" check box conflict) means that no object is downloaded.
If the check box is not activated, all objects are downloaded that were
compiled without error. Objects that caused an error during compilation are not
downloaded.
Note
A hardware configuration can only be downloaded when the CPU is in STOP mode.
The download procedure will not be interrupted by acknowledgment prompts when the
following settings are made for downloading multiple HW objects.
When several CPUs are installed in a station, the settings must be made for every CPU.
● CPU password
Enter a password here if the CPU is password-protected. If you do not enter a password,
the download process will be interrupted later by a prompt for the password.
Additional information
● Online help for "Compile and Download Objects" dialog box (Station properties)
Introduction
The ES log enables you to document the user, time, changes made, the affected CPU and
the reason for the changes. If you activate the option "ES log active", the actions during
downloading and the current time stamps are logged in addition to the protected actions in
CFC/SFC.
Requirements
● The SIMATIC Logon Service is installed.
● The change log is activated.
Rules
● Note that an activated ES log can only be deactivated on the computer on which
SIMATIC Logon Service is installed.
Reason: The deactivation and activation tasks themselves must be recorded in the ES
log.
● Before the download is performed to each individual CPU with the "Compile and
Download Objects" function in the SIMATIC Manager, there is a pause in the operation
brought about by the opening of the ES log if it is activated for the currently selected chart
folder.
Note
If you copy the program or chart folder with an activated ES log to a computer on which
the SIMATIC Logon Service is not installed, you receive an error message when you
attempt to download or switch to test mode and the action is not carried out.
You cannot deactivate the ES log in this situation because there is no "ES log" tab in the
"Object Properties" dialog box of the chart folder.
Logging
The following is logged in the "Logs" dialog box in the "ES log" tab:
● Every action is registered in chronological order (last action in the top line) in a main line
followed by a line giving the reason and perhaps a log of the action itself (a download, for
example).
● For the action "Download entire program", the ES log is deleted from the log but archived
as a file with a date identifier at the same time. The archiving action and the file name
used (including the path) are recorded in the log.
● For the action "Start test mode", all subsequent actions resulting in a change (of value) in
the CPU are logged. The logging includes the value and how it changed (address, old
value, new value).
Specifically, these are:
– In the CFC
Assignment of parameters to I/Os
Activation/deactivation of forcing and force value changes
Activation/deactivation of runtime groups
– In the SFC:
Assignment of parameters to constants in steps
Assignment of parameters to constants in transitions
Assignment of parameters to constants in sequencer properties
Additional information
● Online help for the dialog boxes "ES log" and "Logs"
Introduction
The change log enables you to document the user, time, changes made, the affected CPU
and the reason for the changes.
Requirement
● The SIMATIC Logon Service is installed.
● The access protection is activated.
Rules
● Note that an activated change log can only be deactivated on the computer on which
SIMATIC Logon Service is installed.
Reason: The deactivation and activation tasks themselves must be recorded in the
change log.
● Before the download is performed to each individual CPU using the "Compile and
Download Objects" function in the SIMATIC Manager, there is a pause in the operation
caused by opening the change log if it is activated for the currently selected chart folder.
Note
If you copy the program or chart folder with an activated change log to a computer on
which the SIMATIC Logon Service is not installed, you receive an error message when
you attempt to download or switch to test mode and the action is not carried out.
You cannot deactivate the change log in this situation because there is no "Change Log"
tab in the "Object Properties" dialog box of the chart folder.
Additional information
● Online help for change log
Test Options
The Process object view provides a test mode for assisting you in testing and commissioning
process tags and CFC charts online on the CPU. You will find additional information on this
topic in Section "How to Test in the Process Object View (Page 607)".
You can document changes made in test mode with the ES log (which user, when, on which
CPU, what change was made, etc. ).
Requirements:
● The SIMATIC Logon Service is installed.
● The ES log for the currently selected chart folder is activated.
You will find additional information on this topic in Section "How to Document Changes in
the ES Log" (Page 676)".
You will also find the essential test functions in the editors with which you configured the
programs. With these functions, you can test the configuration. The following editors provide
test functions:
● CFC
Testing the CFC configuration
You will find additional information on this topic in Section "How to Test CFC Charts
(Page 490)"
● SFC
Testing the SFC configuration
You will find additional information on this topic in Section "How to Test SFC Charts
(Page 568)"
Overview
The following procedures should be distinguished for testing:
● Testing with S7-PLCSIM (Page 682)
● Testing in Running Plants (Page 685)
● Testing Field Devices (Page 685)
Additional information
● Manual Process Control System PCS 7; Getting Started – Parts 1 and 2
S7 PLCSIM
S7 PLCSIM is an optionally available software package for simulating an AS. After
installation it can be started in the SIMATIC Manager.
You can use S7-PLCSIM to edit and test your program on a simulated automation system.
Since the simulation is implemented in S7 PLCSIM using the PCS 7 blocks, you do not
require any S7 hardware (CPU or signal modules). You can test programs for S7-400 CPUs
with a simulated automation system. This allows you to test operator control and monitoring
of the simulated AS (OS process mode) on the engineering station.
S7-PLCSIM provides a simple user interface for monitoring and modifying the various
parameters that are used in your program (for example, for switching inputs on and off). You
can also use the various applications in the PCS 7 software while the simulated CPU is
processing your program. For example, you have the option of operator control and
monitoring of I/O values in S7-PLCSIM.
Rules
Note
Please note the following:
• The simulation of I/O modules is not carried out with S7-PLCSIM but by the blocks
CH_DI, CH_AI etc. within the CFC charts (see also: Function Manual Process Control
System PCS 7; Standard Library).
• S7-PLCSIM is not suitable for the simulation of large-scale configurations in the PCS 7
environment.
Installation of S7 PLCSIM
S7-PLCSIM is not automatically installed as part of the PCS 7 installation routine, but if you
select the relevant option it will be installed at the same time.
You can also install it subsequently, as the software is located on the PCS 7 Toolset DVD.
To run the software, you require a separate authorization.
Procedure
The simulation can be started from the SIMATIC Manager when there are no connections to
actual automation systems.
1. Start the SIMATIC Manager.
2. Select the AS you wish to simulate.
3. Select the menu command Options> Simulate Modules.
S7-PLCSIM launches and the "Open Project" dialog box opens.
4. Select option "Select CPU Access Nodes".
5. Click "OK".
The "Select CPU Access Nodes" dialog box opens.
6. In the tree view, select the "-plant bus name-addr: MAC: xxx" object, for example.
PLCSIM supports the following connection types: Industrial Ethernet (ISO protocol or
TCP/IP), MPI and PROFIBUS DP.
Note
For TCP/IP, you will need to set the logical device name to "PLCSIM(RFC1006)"
(WinCC Explorer > Tag Management > SIMATIC S7 PROTOCOL SUITE > TCP/IP >
Shortcut Menu > System Parameters > "Unit" tab).
7. Click "OK".
The "S7-PLCSIM" application window opens.
8. In HW Config, select the menu command PLC > Download to Module....
The hardware configuration is downloaded into the simulated AS.
9. In the SIMATIC Manager, select the "Charts" object in the tree.
10.Select the menu command PLC > Download.
All of the required data is downloaded into the simulated AS.
11.Configure S7-PLCSIM for testing by adding inputs/outputs in S7-PLCSIM so that input
values can be simulated and output values can be monitored. Please also check that the
program can be executed.
12.Switch the simulated CPU to RUN mode.
13.Select the object "OS" in the SIMATIC Manager.
14.Select the menu command "Options > OS > Start OS Simulation.
The OS simulation starts up.
15.Open the SFC and CFC charts and select the menu command Test > Test Mode.
16.Test the program.
Please observe the information relating to block simulation in Function Manual Process
Control System PCS 7; Standard Library.
Note
After using S7-PLCSIM, the real connections may need to be reestablished and the
corresponding OS compiled again (changes only) with the real connection.
Additional information
● Online help for S7-PLCSIM
● How do I use S7-PLCSIM with SIMATIC PCS 7?
(http://support.automation.siemens.com/WW/news/en/16522013)
WARNING
Testing a program while a process is running can lead to serious damage to property or
persons if errors occur in the function or in the program!
Ensure that no dangerous situations can occur before you execute this function!
Testing in a running plant does not differ significantly from the procedure described in the
section "How to Test with S7-PLCSIM (Page 682)" or from the test configuration with an AS.
The range of accessible AS and OS is normally much larger than during a test configuration.
There are higher requirements for safety during ongoing operation and the number of
persons involved is greater. The warning above should make this clear.
In addition, you must ensure that any disruption or interruption in the operation of the plant
due to the test is kept to a minimum. The plant operator should be usually consulted
beforehand.
Note to Reader
The options for parameter configuration and diagnostics using SIMATIC PDM are not
described in this manual.
Additional information
● Online help for SIMATIC Manager and SIMATIC PDM
● Manual PDM; The Process Device Manager
Introduction
The Version Cross Manager (VXM) is a separate application you can order as an option. The
Version Cross Manager enables you to quickly and reliably compare the project data from
two PCS 7 projects in order to identify differences. This feature allows you to recognize if
and what has changed.
Requirements
Archived configuration versions must be compared to determine any changes since the last
supply and acceptance, for example, after it was delivered to the customer or after
certification by the Technical Inspectorate or FDA authorities.
This information is important, for example, in the following areas of application:
● A previously accepted project status is to be approved after changes were made and
expansions were added. You therefore need to know the status of changes since the last
acceptance.
● The contractual and accepted project status has been expanded due to subsequent
changes in requirements and the expansions are to be verified.
● In parallel to the commissioning of a project status at a plant, the status was expanded at
an engineering office. The expansions are to be identified in order to add them to the
current project status.
● The documentation of an already completely documented project status is to be updated.
It is to be determined which object documentation requires revision due to changes.
● The process control project data of a plant should be synchronized with the planning data
of the plant. To do this, export the project data in the manufacturer-independent
XML-format and import it into CAx systems (CAD, CAE, E-CAD or E-CAE).
Introduction
Automation solutions are configured in the PCS 7 engineering system in the form of CFC
and SFC charts using blocks. The project version is compiled as a program and downloaded
to the AS. This version can be saved by archiving the project (for example, after the
customer, Technical Inspectorate or FDA representative have accepted the project).
This project will be changed over time, errors will be corrected and additions will be made,
for example. If a further acceptance test becomes necessary, the Version Cross Manager
(VXM) can be used to indicate all the changes that have been made.
Functions
The VXM offers the following main functions:
● Comparison of projects and XML files
● Import and export of project and planning data
● Generation of process tags from CAx function block diagrams
What is Compared?
With the VXM you select an object as "Master" and an additional object as "Compare
Object". When you open the object to be compared, the comparison starts automatically.
The following objects are supported:
● Project
● Library
● HW configuration
● CFC/SFC engineering data, such as charts, types, chart folders, block folders.
● Shared declarations
● S7 Program
● S7 blocks
● S7 symbols
● Messages
Example
Additional information
● Online help for VXM
Requirement
The Version Cross Manager is installed.
Procedure
1. Select the menu command Start > SIMATIC > STEP 7 > VXM - Compare Versions.
The Version Cross Manager is started.
2. Select the menu command File > Open/Compare....
The "Open/Compare" dialog box opens.
3. For A, select:
– First Object
Make the selection and settings you require in the "Open" dialog box.
Filtering
You can use a filter to restrict the comparison of the object trees to specific objects and
attributes.
The filter setting is taken into account by VXM not only during the comparison but also when
displaying the results. As a result, only the objects and attributes actually used in the
comparison are displayed.
You can use them to specify whether or not a file is to open with a new filter setting or
without a filter or, if the file appears in the list under the "File" menu, whether or not it should
open with its default setting.
A number of filter criteria are set by default in VXM.
Additional information
● Online help for VXM
Introduction
A variety of software tools from various manufacturers is involved in the work process during
the configuration phase of an industrial plant. XML (Extensible Markup Language) has
established itself as a data exchange format in many areas.
The synchronization of the PCS 7 project data with the planning data of the plant is
supported by the export of the plant data into XML format.
Export Options
The project data can be exported as follows:
● VXM
All data is written during export from the VXM.
Filters set in the VXM also affect the result of the export. Only objects and attributes
displayed in the VXM through the configured filter are exported.
● SIMATIC Manager
When you export from the SIMATIC Manager, the project is exported.
The export from the SIMATIC Manager cannot be assigned a filter. In this case, the
complete project data is always exported (the filter CAx is preset and cannot be
changed).
– First Object
Make the selection and settings you require in the "Open" dialog box.
Note
The export is only possible if a comparison has not yet been carried out.
Additional information
● Online help for VXM
Introduction
You can import planning data following a project comparison. The result of the comparison
documents which planning data is added or changed. The changed or extended planning
data is imported by transferring additional objects with their properties at the appropriate
point in the project, and adjusting the relevant properties and attributes of the changed data
in the target object.
Before the import is started, the system queries whether any existing objects in the target
project should be deleted, for example, because they are considered obsolete.
You can perform the import from the standard view or from the differences view. The source
can be a project or an XML file.
Procedure
1. Select the menu command Start > SIMATIC > STEP 7 > VXM - Compare Versions.
The Version Cross Manager is started.
2. Select the menu command File > Open/Compare....
The "Open/Compare" dialog box opens.
3. For A, select:
– First Object
Make the selection and settings you require in the "Open" dialog box.
7. Click "OK".
The VXM reads the selected objects/files in, including all lower-level objects, and carries
out a comparison at the same time.
The two objects are superimposed in a comparison tree. The deviations shown are color-
coded (see Section "How to Compare Project Versions (Page 691)").
Note
Please note the following:
• If you activate the "No filter" check box, you cannot make any settings. When you
open the file, everything is selected and displayed with all details.
• If you activate the "Set filters when opening a file" check box, the "Set Filters" dialog
box opens before a file is opened.
Additional information
● Online help for VXM
Introduction
Planning data refers to the plant description data that is considered relevant for the
engineering system. This is the data from the plant hierarchy and the equipment properties
of a plant.
The transfer and comparison of planning data is supported by the import function and the
generator function. In addition, descriptions can be transferred from CAx function block
diagrams in order to generate control system CFC charts (process tags) from them using a
software generator. The data is exchanged on the basis of a defined XML format
(SimaticML). Conversely, modified data can also be fed back to the engineering system, for
example, to synchronize the database of a CAx planning tool. This is enabled by a
corresponding export function.
The CAx Generator functionality allows you to generate or update process tags in PCS 7
projects (CFC charts) using the CAx function block diagrams created at planning level.
Procedure
1. Select the menu command Start > SIMATIC > STEP 7 > VXM - Compare Versions.
The Version Cross Manager is started.
2. Select the menu command File > Open/Compare....
The "Open/Compare" dialog box opens.
3. For A, select:
– First Object
Make the selection and settings you require in the "Open" dialog box.
Additional information
● Online help for VXM
Introduction
A maintenance station can be used to provide full diagnostics for a PCS 7 plant.. The
maintenance station is an operator station that is specially configured and assigned
parameters for use in diagnostic and maintenance functions.
We particularly recommend the use of a maintenance station in medium and large
PCS 7-systems.
Maintenance station
With the maintenance station, PCS 7 enables you to call up information on the states of all
PCS 7 components on diagnostics screens which are hierarchically structured. As part of
this process, the data of a component are analyzed using the available online functions of
the associated tools. You can access ES data from the diagnostics screens (can be
controlled via access protection mechanisms).
Diagnostic screens for process control diagnostics can be generated automatically for the
entire plant and made available graphically on the maintenance station. The topmost level
forms an overview screen for the entire system.
Requirements
● The cross-project consistency checks were successful (for example, names of the S7
programs unique throughout the multiproject)
● Blocks from a PCS 7 library beginning with version V6.1 are used in the project.
● The module drivers are generated and interconnected with the signal-processing blocks
in the CFC charts.
● The diagnostic blocks are set to "OCM possible".
● The check box "Derive diagnostic pictures from the plant hierarchy" is activated in the PH
settings.
Diagnostics Options
You will find information on the states of individual PCS 7 components with diagnostic
capability on the maintenance station's special diagnostics screens.
Additional information
● The Configuration Manual Process Control System PCS 7; Operator Station contains a
description of how the maintenance station is configured.
● You will find a description of working with the maintenance station in process mode in the
Manual Process Control System PCS 7; OS Process Control.
(VWDEOLVKLQJRIFRQQHFWLRQWKURXJK
WKHRSHUDWLQJV\VWHPSURJUDP
1HWPHHWLQJ
&XVWRPHU6XSSRUW 3&VWDWLRQLQ
6HUYLFHSHUVRQQHO 3&6SODQW
7&3,3RUPRGHP 7&3,3RUPRGHP
Transmission Paths
The data can be sent as follows:
● via a telephone line (modem)
● via TCP/IP connection (internal plant network connection)
Security Requirements
If you wish to perform remote diagnostics in a PCS 7 plant, you need to protect the this plant
against unauthorized access.
Several measures are required to realize a security concept. Optimal protection is only
provided with all security measures as a whole.
Additional information
● Online help of the operating system
● Whitepaper Security Concept PCS 7 and WinCC
● Operating Manual Process Control System PCS 7; PC Configuration and Authorization
Additional information
You will find a detailed description of the additional diagnostics options that are available
with PCS 7, as well as what to do if service becomes necessary, in the Manual Process
Control System PCS 7; Service Support and Diagnostics.
This manual contains the following information for your support:
● Taking measures to ensure the availability of a PCS 7 plant.
● Checking the requirements for effective diagnostics of your PCS 7 plant.
● Understanding the alarm concept of a PCS 7 plant
● Using the right procedure if a problem occurs, and providing detailed information about
the state of the PCS 7 plant for service experts
● Selecting the correct diagnostic tool so that you can run diagnostics on your PCS 7 plant
with the specified aids.
Introduction
SIMATIC PCS 7 provides a variety of functions for archiving/versioning and documenting
configuration data and archiving/versioning process values.
Archiving
PCS 7 provides two basic functions for logging:
● Archiving process values (e.g. measured values; messages)
The operator station saves measured values and messages in archives so that the data
can be called up over a longer period of time.
You can find more information about this in the configuration manual Process Control
System PCS 7; Operator Station.
● Archiving projects
The multiproject is archived with all projects and the master data library.
You can find more information about this in the sections "How to Archive a Multiproject
and the Project Master Data (Page 705)" and "How to Retrieve a Multiproject and the
Project Master Data (Page 706)".
NOTICE
Create backup copies of your project as often as possible.
You should keep at least five older versions of the data. If there is a network failure,
hard disk crash or network disruption, you can always revert to a backup of your project.
Versioning
In PCS 7, versioning represents documented backup of data for PCS 7 plant in version
archives.
Version Trail (add-on package) is used for versioning in PCS 7. In a version archive, you can
manage multiple backups (versions) of an object (for example, a project or a library). The
archived data can not be changed after this.
Version Trail takes over the complete management of the version history. The system
automatically sets the versioning based on specifically configured guidelines. You can
increment the version numbers in whole number steps, for example. Version Trail ensures
that there is only one valid version of a project with the same identifier in the version history.
You use Version Trail, for example, to pass a project version of a plant to others (transfer
version) and if you wish to determine the changes in a current project version.
Document
Documenting involves the creation of the plant documentation. The DOCPRO add-on
package for PCS 7 is used for this purpose.
● Creating and managing plant documentation
● Centralized control of printing (project segments or entire project)
● Custom layout (e.g. DIN 6771)
You can find information about this in the section "Creating the Project Documentation
(Page 710).
Introduction
You can save a multiproject in compressed form in an archive file just like projects or
libraries. The compressed files are saved to a hard disk or transportable data media.
If parts of the multiproject are stored on network drives, you can use the following file
compression tool to create an archive for multiproject data:
● PKZIP for Windows (available on the PCS 7 Toolset DVD; installed at the same time as
PCS 7)
Procedure
1. Select the multiproject in the SIMATIC Manager.
2. Select the menu command File > Archive...
.The "Archive" dialog box opens.
3. Select the required multiproject and click "OK".
The "Archive - Select Archive" dialog box opens.
4. Select the name and path of the archive, as well as the archiving program (PKZip)
5. Click the "Save" button.
Additional information
● Online help for the SIMATIC Manager
● Manual Process Control System PCS 7; Service Support and Diagnostics
Procedure
1. In the SIMATIC Manager, select the menu command File > Retrieve....
The "Retrieve - Select Archive" dialog box opens.
2. Select the archive you want to retrieve.
3. Click on the "Open" button.
4. In the "Select destination directory" dialog box that appears, select the target directory for
unpacking the archive files.
5. Click "OK".
Note
The multiproject is retrieved in the target directory, with an additional sub-directory. The
system bases the name of this sub-directory on the name of the multiproject (in order to
prevent any multiprojects with the same name from being overwritten).
Following retrieval, you must generate the server data, assign this to the OS clients, and
download it to all OS PLCs.
Result
A new directory is created in the selected directory and the complete project directory
structure of the unpacked multiproject now appears on the same level below this directory.
Additional information
● Online help for the SIMATIC Manager
● Manual Process Control System PCS 7; Service Support and Diagnostics
Recommendation
Save various project states.
Create a backup in the following situations:
● After configuration changes
● Before and after system component upgrades
● Before and after the software update of the configuration software
Additional information
You will find a step-by-step description of saving and backing up ES and OS project data in
the manual Process Control System PCS 7; Service Support and Diagnostics.
13.4.3 Versioning
Introduction
You can save versioned PCS 7 project data with Version Trail. Data archived in this way can
no longer be changed. You can retrieve stored versioned project data and use it again or
compare it with other versions or with the current project.
You use Version Trail, for example, to transfer a project version of a plant (transfer version)
and later compare it to the current plant project version (using VXM).
Note
You can assign access permissions for archived objects using SIMATIC Logon.
Requirements
Ensure the following to work with Version Trail:
● A user must be logged on and all relevant actions must be logged under this user's name.
● Version Trail is not open.
● The object to be versioned (multiproject, project, library) is not open.
Procedure
The procedure described here assumes that you have not yet created an archive in the
versioned project.
To save a versioned multiproject, single project or a library, proceed as follows:
1. Select the menu command File > Versioned Project > Archive....
The "Open Project" dialog box opens.
2. You can specify the object (multiproject, project, library) for which you want to create a
versioned backup as follows:
– Select the object.
– Search for the object using the "Browse" button.
3. Click "OK".
The "Save SIMATIC Project <path> in Versioned Project" dialog box opens.
4. Click "Open".
The "Open Versioned Project" dialog box opens.
5. Select the required versioned project from the list and click "OK".
The "Save SIMATIC Project <path> in Versioned Project" dialog box opens.
6. Select the versioned project in the tree view and select the context menu command Insert
New Object > Archive....
The "Open Project" dialog box opens.
7. Select the required object as described in step 3.
The "Properties" dialog box opens.
8. Enter the name and any comment and click "OK".
The "Properties" dialog box closes.
9. In the "Version designation" group, select the appropriate checkbox to indicate whether to
increment the main or secondary version.
N.B. Only "Increment main version" is possible during the first archiving.
The "Save SIMATIC Project <path> in Versioned Project" dialog box opens.
10.Enter the name of the version and click "Archive...".
Compression is started and the name of the versioned object ultimately appears in the
detail window.
Result
The object has been assigned a version and saved in compressed form.
If you wish to create a new version of the same project in the same versioned project, some
intermediate steps may be skipped.
Security
Version Trail is protected by the SIMATIC Logon Service. SIMATIC Logon Service check if a
user is logged on in SIMATIC Manager.
To log on a user, select the menu command Options > SIMATIC Logon Service... in the
SIMATIC Manager.
If no user is logged on, the "SIMATIC Logon Service" dialog box appears in Version Trail
before every protected action.
This also applies to creating a new versioned project.
Additional information
● Online help for the SIMATIC Manager
● Online help for Version Trail
Procedure
To retrieve a versioned multiproject, single project or a library, proceed as follows:
1. Select the menu command File > Versioned Project > Retrieve....
The "Open Versioned Project" dialog box opens.
2. Select the required versioned project from the list and click "OK".
The "Retrieve SIMATIC Project from Versioned Project" dialog box opens.
3. Select the project in the tree view and the version that you want to retrieve in the detailed
view.
4. Click "Retrieve".
The "Select Director" dialog box opens.
5. Select the target directory and click "OK".
Decompression is started.
If there is already a folder with the same name at the storage location, a dialog box opens
informing you of this.
You can abort the retrieval by clicking "Cancel" or store the retrieved data under a new
name by clicking "Rename".
You get a message informing you of the name of the project and path where it has been
saved.
Result
You have now decompressed and restored the desired version of your project.
Additional information
● Online help for Version Trail
13.4.4 Document
Overview
After creating the process cell, it is necessary to structure the project data in a clear manner.
Clearly structured documentation makes both future development of the project and service
and maintenance much easier.
DOCPRO is an application that can be used for effective creation and management of plant
documentation. It gives you the following options:
● To structure the project data in any way
● To prepare the project data in the form of standardized technical documentation
● To print out the project data in a unified format
Additional information
● Online help for DOCPRO
● Manual DOCPRO; Creating Documentation
Introduction
DOCPRO can generate documentation to an electronic manual (PDF format). There is no
automatic conversion function in PCS 7!
Requirement
You have a full license agreement for the program Adobe Acrobat from Adobe Systems
Incorporated.
Basic Procedure
1. Create the documentation for a project in DOCPRO, for example, with the aid of the
DOCPRO wizard.
2. Print the documentation from DOCPRO to a file. Check the "Print to file" check box inside
the Windows Print dialog box.
3. Open the Acrobat Distiller and drag all the files created by DOCPRO from the Explorer to
the Distiller.
The Distiller creates the corresponding PDF file from every single file.
Note
Siemens accepts no liability for the programs offered by Adobe Systems Incorporated.
For detailed information on using the Acrobat Reader, refer to the Acrobat Online manual
that can be started with the menu command Help.
Additional information
● Online help for DOCPRO
● Manual DOCPRO; Creating Documentation
Overview
This overview contains information about the following topics:
● Installation Guidelines for PCS 7 (Page 714)
● Lightning protection (Page 716)
● Electrical installation (Page 718)
● Basics of EMC-Compliant Installation of PCS 7 (Page 723)
● Degrees of Protection (Housing Protection) (Page 726)
Introduction
The installation guidelines must be observed to ensure correct operation of a PCS 7 control
system. This appendix contains additional information about lightning protection, grounding
and EMC-compliant installation. The basic installation guidelines can be found in the
installation manuals of the components (for example. Installation Manual Programmable
Controllers S7-400, Hardware and Installation).
Components
The configuration method is largely determined by the components used in PCS 7:
● SIMATIC PC stations
● SIMATIC NET (Industrial Ethernet and PROFIBUS)
● S7-400/S7-400H/FH
● Distributed I/O (ET 200M, ET 200S, ET 200iSP, and field devices)
Each component has numerous configuration variations that can be adapted to meet the
requirements of a particular application.
There is also the option of installing programmable controllers and the distributed I/O
systems in cabinets.
For more detailed information about the installation of an entire plant (lightning protection,
grounding, etc.) refer to the relevant sections below. The options available for connecting
process signals to the CPUs are described in detail in the section Installation of the.
Note
ET 200M is used as an example of distributed I/Os in the following document. Refer to the
relevant product manuals for more information about installing other ET models.
Cabinet Installation
S7-400 programmable controllers and ET 200M modules can be installed in cabinets for the
PCS 7 control system. The following illustration shows the S7-400 programmable controller
and distributed I/O system ET 200 M installed in a cabinet. The different racks can be
combined as necessary to allow you, for example, to install the distributed I/Os in separate
closets (electronics closets, wiring closets).
The cabinets consisting of system-specific (system and I/O units) and system-neutral
modules (basic cabinets, power supply units and add-on packages) offer adequate
protection against the following factors:
● Unauthorized access
● Mechanical influences
● Contamination and corrosion
Due to the modularity and associated variability, the cabinets can be adapted to different
types of system and different sizes of system.
EMC Compliance
The PCS 7 control system and its components comply with the EMC requirements of
European standards. These standards require that EMC-compliant devices have sufficient
immunity to noise during operation when correctly installed, suitably maintained, and be
used for correct purposes in a normal EMC environment. The emission of noise is limited to
guarantee normal operation of radio and telecommunication devices.
The cabinets of the PCS 7 control system consisting of the system units, I/O units, basic
cabinets, power supply units and add-on packages are CE compliant. This means that the
cabinets and the PCS 7 control system comply with the EMC regulations such as:
● Electromagnetic compatibility (89/336/EEC; 92/31/EEC)
● Low voltage directive (73/23/EEC; 93/68/EEC)
● Hazardous areas directive (94/9/EEC)
Introduction
Industrial plants and power stations must be equipped with lightning protection to protect
people, buildings and equipment from damage resulting from lightning strikes. Process
control systems with extensive cabling networks are often at risk since high voltages can
occur between points at great distances from each other. The destruction of electronic
components due to lightning can lead to plant failure with extremely expensive
consequences.
The risk of damage by lightning can result from
● A building being struck directly
● A lightning strike in the immediate vicinity of the system
● A remote strike (for example, in a free line)
● Cloud-to-cloud-discharge
Originating in the lightning channel, the lightning creates a cylinder-shaped electromagnetic
wave that penetrates into the building and induces voltages in cable loops. The closer the
lightning strike, the more powerful the fields created.
Both with lightning from cloud to cloud or from cloud to earth, the charges induced in free
lines (high and low power and telecommunication lines) change. These changed charges
then flow as traveling waves along the cable. If these traveling waves reach equipment at the
end of the cable they can also enter the plant or system that you want to protect. Generally,
only signal and bus cables in the vicinity of transformers and signal and telecommunication
lines are actually at risk.
The lightning protection for a process control system can be roughly divided into exterior and
interior lightning protection.
Additional information
The rules for bridging the interfaces between the lightning protection zones and an example
circuit for networked SIMATIC 400 stations are explained in the installation manual "S7-400
Programmable Controllers, Hardware and Installation".
Introduction
The correct operation of PCS 7 components depends to a large extent on adherence to
certain rules of electrical installation. This involves the following aspects:
● Equipotential bonding (VDE 0100)
● Grounding
● Overvoltage Protection
● Shielding
● Cabling
Equipotential Bonding
In accordance with VDE 0100, all electrically conductive metal parts of a system (cabinet
panels, racks etc.) must be interconnected. This ensures that any potential differences are
reduced to such an extent that there is no danger for either human beings or equipment.
Grounding
Low-resistance ground connections reduce the risk of electrical interference in case of short
circuits or faults in the system. By using low-impedance connections for grounding and
shielding cables and devices, the effects of noise on the system and the emission of noise
from the system can be reduced.
The SIMATIC S7-400 programmable controller and the distributed I/O system ET 200M
allow both grounded and ungrounded operation.
Overvoltage Protection
Overvoltages can occur at module outputs when inductors are turned off (at relays, for
example). The digital modules of the SIMATIC S7 400 have integrated overvoltage
protection. In certain situations (for example, when there is an additional contact between the
module output and inductor), an external overvoltage suppressor (for example, an arc-
suppression diode) must be installed directly on the inductor.
7UDQVPLWWHU 5HFHLYHU
/
XVXDOO\
6LJQDOFDEOH
SHUPLVVLEOH
/
(TXLSRWHQWLDOERQGLQJV\VWHP
7UDQVPLWWHU 5HFHLYHU
/
6LJQDOFDEOH SHUPLVVLEOH
/
(TXLSRWHQWLDOERQGLQJV\VWHP
6LJQDOOLQH EHWWHU
/
(TXLSRWHQWLDOERQGLQJV\VWHP
6LJQDOOLQH *RRG
/
(TXLSRWHQWLDOERQGLQJV\VWHP
(QFRGHU 5HFHLYHU
6KLHOG /
6LJQDOOLQH YHU\JRRG
/
(TXLSRWHQWLDOERQGLQJV\VWHP
Connecting the cable shield of electrical cables at the entrance to the electronics cabinet
Care must be taken that interference running along the cable shield is not allowed to enter
electronics cabinets.
If the cable shields are grounded inside the cabinet or casing, the field generated in the
shield grounding cables by the shield current is coupled not only into the unshielded signal
cables but also into the loops on the modules behind the inlet protection circuits and
generates interference voltages. For this reason, when grounding both ends of a shield, the
grounding should take place directly at the housing opening.
Also ensure that the shields contact the grounding rail over a sufficiently large area. Long
thin wires between the shield and ground bar have high inductance and are therefore
unsuitable for discharging interference currents with high frequencies.
Note the following points:
● Use short wire lengths (if possible do not use wires at all but make direct large-area
contact)
● Choose a suitable route for the shield grounding wires (do not lead them close to
sensitive electronics)
● Use a short, thick cable from the shield bar to the equipotential bonding system
If cabinets or casings are included to shield the control system, remember the following
points:
● Cabinet panels such as side panels, back panels, ceilings and floors should be contacted
at adequate intervals when cascaded.
● Doors should have extra contacts to the cabinet chassis.
● Cables leaving the shielding cabinet should either be shielded or fed via filters specified
for PCS 7.
● If there are sources of strong interference in the cabinet (transformers, cables to motors,
etc.), they must be separated from sensitive electronics by partitions. The partitions
should be connected with low impedance to the equipotential bonding system via the
cabinet.
All housings, cabinets, etc.should be connected to the equipotential bonding system over the
shortest route possible. Often, an independent equipotential bonding system is created. This
is connected to the equipotential bonding system of the remaining plant by a single cable.
It is a mistake to connect the PCS 7 process control system to a ground point outside the
plant. The magnetic fields generated by the interference currents flowing in the equipotential
bonding system induce voltages in the additional surface between the equipotential bonding
conductors and the connection to ground.
)LHOGOLQHV
&DEOH
)LHOGOLQHV
&DEOH
The lines of a signal or bus connection should be in one cable and be surrounded by a
common shield. The cable should be laid as close as possible to the exciting cable to keep
the insulation stress to a minimum.
The cable carriers (for example, cable racks) should be connected to the equipotential
bonding system if there is no interference-carrying part of the equipotential bonding system
within close proximity. The cable shield can then be contacted at both ends with the casings
of the electronic equipment and in turn connected to the equipotential bonding system.
Additional information
For more detailed information about the electrical installation, refer to the installation manual
S7-400 Programmable Controllers; Installation and Hardware.
Introduction
Although the SIMATIC PCS 7 system and its components were designed for use in an
industrial environment and meet strict EMC requirements, an EMC assessment should be
performed prior to installing the control system and possible sources of noise identified.
Mechanisms
Interference arising from various coupling mechanisms can affect the PCS 7 control system.
The type of coupling mechanism depends on the distance between the source of the
interference and the PCS 7 control system and the transmission medium.
Additional information
For additional information about plant installation, refer to the manual S7-400 Programmable
Controllers; Installation and Hardware.
IP standard
Housing protection is stipulated in standard EN 60529 in Europe by the IP codes IPxx with 2
numbers.
The following table explains the IP norms conforming to EN 60529/IEC529:
Protection level
The casings of most SIMATIC components have ventilation openings. To allow more
effective cooling of the electronics components, ambient air can flow through the casing. The
maximum operating temperatures quoted in the technical specifications apply only when
there is unrestricted flow of air through the ventilation openings.
Depending on the size of the ventilation openings, such modules comply with the degrees of
protection IP 20, IP 30 to IP 40. You will find the actual degree of protection of a SIMATIC
component in its documentation.
Components with the degrees of protection mentioned above do not provide protection
against dust and water! If the installation site requires protection of this kind, the components
must be installed in an additional enclosure (such as a switching enclosure) that provides a
higher degree of protection (for example, IP 65/IP 67).
Note
Make sure that the temperature inside the additional enclosure does not exceed the
permitted ambient temperature for the installed components. Select an enclosure with
adequate dimensions or use heat exchangers.
B C
Backup, 706 Cabinet construction, 714
Basic concept, 225 Cable shield, 718
Event-signaling system, 225 bring into contact, 718
Basic configuration, 161, 275 Cabling, 718
configure hardware, 275 Cancel, 302
in PCS 7 plants, 161 Assignment of object - PH, 302
Basic Elements, 205 catalog profile, 353
for Reuse, 205 project-specific for a hardware configuration, 216,
BATCH, 126 353
PC components, 126 Catalog profile, 216
BATCH archive, 56 Central I/O, 145
BATCH stations, 281 Central, plant-wide engineering, 188
Configure, 281 CFC chart, 463, 467, 485, 487, 488, 490
Insert, 281 Comparing before downloading, 487
Block, 323, 328, 468, 470, 473, 506 Compile, 485
configure, 470 create, 463
for an FDL, ISO/TCP connection, 506 creating, 467
for different connection types, 506 Download to the CPU, 488
for FMS connections, 506 test, 490
for S7 connections, 506 CFC chart I/Os, 482
inserting into a CFC chart, 468 define, 482
interconnect, 470 Change, 559
project-specific adaptation, 323 Process tag type, 520
Runtime properties, 473 Change Module during Operation, 382
Set language, 328 Change parameter settings, 412
Block drivers, 510 of existing modules in ET 200M stations, 412
Generating, 514 changes
Block I/O attributes, 324 Installation rules for CIR, 185
modify, 324 Changes, 15, 185, 421, 676
Block icon, 206, 223, 329 compared with the previous version, 15
creating/updating OS pictures automatically, 329 Configuration in RUN, 421
Generate, 223 ES Log, 676
use, 206 in runtime CiR, 185
Block type, 206, 321 Changing, 152, 324, 415, 430, 439, 520, 663
update, 321 Attribute: Signal configuration of modules, 663
use, 206 central, 205
Blocks, 587 Configuration to distributed I/O, 152
edit, 587 Network configuration, 439
Braided shields, 718 Node address, 430
Branching, 201 Parameter assignment of a channel, 415
Charts from a Project, 201 SFC type centrally, 559
Bring into contact, 718 Chart, 561
Cable shield, 718 Compiling, 561
Bus systems, 68, 78, 79, 80 Check
Area of application, 79 consistency of the PH, 304
for communication, 78 Checking, 304, 435
Maximum expansion, 68 consistency of the network, 435
maximum transmission rate, 80
Parameter, 79
CiR, 185, 396, 399, 400 Compiling and downloading, 665, 667, 673
CiR elements, 396 AS data, 665
CiR objects, 396 Options, 673
Installation rules, 185 OS server data, 665
Introduction, 399 Requirements for OS, 667
Modules, 396 component view, 238
Principles, 396 AS configuration, 238
Recommendations, 400 hardware configuration, 238
CiR element, 402, 406, 407 multiproject engineering, 238
Define, 402 OS configuration, 238
Delete, 406 Route Control configuration, 238
Use in RUN, 407 Component view
Columns, 582 important functions, 238
Defining, 582 Components, 46, 48, 50, 53, 56, 69, 134, 139, 141
Displaying/Hiding, 582 Fail-safe automation Systems, 141
Setting, 582 Fault-tolerant automation systems, 139
Sorting, 582 for access protection, 50
Commissioning, 30 for data links to third-party systems, 48
Documentation, 30 for validation, 53
Communication, 48, 78, 174, 176, 440, 442 of an automation system, 134
Bus systems, 78 Selection, 46
Communication partners, 440 to archive the process data, 56
configuring communication between SIMATIC which avoid production loss, 69
stations, 442 Concept, 355
Data communication via the terminal bus and plant Address assignment, 355
bus, 174 Configuration, 152, 161, 178, 203, 228, 273, 275, 355,
Networks, 78 359, 377, 399, 419, 421, 440, 536, 609
to third-party systems, 48 Basic configuration in PCS 7, 161
with the terminal bus and plant bus, 176 change to distributed I/O, 152
Communication connection, 77, 440 Concept for the address assignment, 355
Connection Types and Connection Partners, 440 Configure hardware, 275
with SIMATIC NET, 77 Connections, 440
Communications processor, 276, 364 Create a SIMATIC station, 359
insert, 364 Download to the CPU, 419
Insert, 276 Downloading changes in RUN, 421
Compare, 691 Expanding CFG Files, 658
Project versions, 691 Fail-safe systems, 377
Compare before downloading, 487, 564 Fault-tolerant systems, 377
SFC chart, 564 Hardware, 351
Comparing before downloading in RUN - CiR, 399
CFC chart, 487 in the Network, 203
Comparing project versions, 687 Messages, 228
Version Cross Manager, 687 of a SIMATIC station, 355
Compile, 327, 330, 485, 561 of the AS and PC stations, 273
CFC chart, 485 of the automation system, 178
Message texts, 327 Overview, 357
Texts which are of relevance to the operator, 330 Sequence control, 536
Compiling Structure and Content of the CFG File, 655
Chart, 561 configuration manual
SFC chart/type, 561 Structure, 31
Type, 561 Configuration manual, 31
Configuration modifications, 400
Permissible, 400
Configuration steps, 465, 630 Connect, 91, 102, 106, 114, 116, 117, 118, 119, 120,
for creating CFC charts, 465 122, 123, 144, 150
Configuration tasks, 256 Connect KNX to PROFIBUS DP, 116
create a PCS 7 project, 256 Connecting the ASI bus to PROFIBUS DP, 114
for working with the I/E Assistant, 630 Ethernet, 91
set up a PCS 7 project, 256 H1 Bus Fieldbus Foundation to PROFIBUS DP, 118
Configure, 277, 290, 382, 417, 438, 442, 446, 453, HART devices to distributed I/O, 150
456, 457, 459, 497, 539, 545, 554, 613, 615, 617, 619, HMI systems via OPC, 122
626, 723 I/O device, 144
AS runtime measurement, 497 I/Os with driver blocks, 510
Blocks, 470 instabus EIB to PROFIBUS DP, 116
Communication between two SIMATIC MODBUS to PROFIBUS DP, 117
stations, 442 Network nodes, 91
Connection between a PC and a SIMATIC 400 PROFIBUS DP nodes, 102
station, 446 PROFIBUS PA to PROFIBUS DP, 106
Connection to the works management level, 617, To the IT world via OpenPCS 7, 123
619 Connecting
cross-project connections between AS and OS, 626 to MIS/MES, 119
Diagnostic repeaters, 387 To the IT world with SIMATIC IT, 120
Distributed I/Os, 382 Connection between a PC and a SIMATIC 400
EMC-compliant, 723 station, 446
Engineering station, 277 Configuring, 446
Messages in the SFC, 554 Connection Configuration, 440
OpenPCS 7 station, 285 Connection partners, 440
Operator Station, 279 Connection table, 451
PA devices, 386 Connection to the works management level, 617, 619
PC stations, 286 configuring, 617
Plant hierarchy, 290 Configuring, 619
redundant networks, 438 Connection types, 440
Route Control functions, 615 Connections, 440
Route Control stations, 283 Configuring, 440
Sequencer properties, 539 Consistency, 304, 382, 435
SIMATIC BATCH functions, 613 check the PH, 304
Steps - SFC, 543 checking the network, 435
textual interconnections by several users, 459 Errors, 382
Transitions - SFC, 545 Convert, 711
Y coupler, 394 convert documentation into a PDF file, 711
Y link, 394 Copy, 299, 302, 319, 552, 577, 583
Configuring, 279, 281, 283, 285, 286, 351, 357, 386, Charts, 302
387, 392, 394, 428, 429, 470, 543 In the PH, 299
AS functions, 457 Objects to the master data library, 319
BATCH stations, 281 SFC chart, 552
Cross-AS functions, 453 Copying
Hardware for the high-precision time stamp, 417 Replicas of the model, 577
HART devices with SIMATIC PDM, 392 Correlations, 246
Network connections, 429 between the views, 246
new subnet, 428
OS functions, 609
redundant connections, 456
Coupling, 106, 114, 116, 117, 118, 122, 723 Cross-project connections, 455, 625
Connect KNX to PROFIBUS DP, 116 merging, 455, 625
Connecting the ASI bus to PROFIBUS DP, 114 Cross-project networks, 624
Coupling mechanisms, 723 Cross-project Networks
H1 Bus Fieldbus Foundation to PROFIBUS DP, 118 merging in the network, 624
HMI systems via OPC, 122 Cross-project S7 connections, 626
instabus EIB to PROFIBUS DP, 116 between AS and OS components, 626
MODBUS to PROFIBUS DP, 117 Configuring, 626
PROFIBUS PA to PROFIBUS DP, 106
CP 443-1, 364
CP 443-5 Extended, 364 D
CPU, 65, 367, 378
data, 645
Default parameters, 378
Data, 157, 627, 648
requisite number, 65
Exchanging with MS Excel/Access, 648
set properties, 367
IEA File in the ES, 645
CPUs for PCS 7 projects, 137, 138
import, 157
Default parameters, 138
Data
Limits, 137
Adopting from the plant engineering, 627
Create, 292, 328, 329, 359, 463, 516, 517, 518, 532,
Data backup, 706
540, 555, 570, 710
Data communication
CFC chart, 463
with MS Excel/Access, 648
Create driver blocks yourself, 516
Data Communication, 174, 648
Documentation, 710
Communication via the terminal bus and plant
Master data library, 315
bus, 174
own blocks, 328
Data formats, 157
Plant hierarchy, 292
import, 157
Process tags from process tag types, 517
Data links, 113
Sequence control, 532
to other systems, 113
SFC type, 555
Data-handling steps, 346
SIMATIC station, 359
Multiproject, 346
Topology of the sequential control system, 540
Deactivate, 676
Create automatically, 525
ES Log, 676
Process Tags, 525
Default parameters, 378
Create you own block, 328
of the CPUs, 378
create, 328
Default parameters, 138
Creating, 258, 289, 315, 426, 428, 429, 467, 514, 538,
of the CPUs for PCS 7 projects, 138
558, 575
Defaults, 256, 257
a new SFC chart, 538
In the SIMATIC Manager, 256
automatically creating block icons for OS
Define
pictures, 329
CiR elements, 402
CFC chart, 467
Defining, 353, 402, 482, 582
Model, 570
a project-specific catalog profile for a hardware
Multiproject with the PCS 7 wizard, 258
configuration, 353
network connections, 426
CFC chart I/Os, 482
Network connections, 429
Columns, 582
new subnet, 428
Degree of protection - Housing protection, 726
Plant hierarchy, 289
Delete, 406, 552, 577, 583
Process tag type from a CFC chart, 518
Model, 577
replicas of models, 575
SFC charts, 552
SFC instance, 558
Creating CFC Charts, 465
Configuration steps, 465
Modules, 382 L
Objects in the hierarchy folder, 298
Language, 328
Operator Station, 279
set for blocks, 328
Route Control stations, 283
set for display devices, 328
Station, 359
Languages, 330
Inserting, 279, 298, 382
Library, 214, 310, 317, 341
BATCH stations, 281
Test objects, 341
OpenPCS 7 station, 285
using the master data library/libraries, 214
instabus EIB, 116
work with, 317
connect to PROFIBUS DP, 116
Library objects, 341
Install, 726
document, 341
in an additional enclosure, 726
test, 341
Installation
License
ungrounded, 718
Booking back process objects, 505
Installation guidelines, 714
License information, 501, 505
Cabinet Installation, 714
Lifebeat, 612
Components, 714
Lifebeat monitoring, 612
Frame-mounting, 714
monitoring, 612
PCS 7, 714
Lifebeat monitoring, 612
Protection requirements, 714
monitoring, 612
Wall-mounting, 714
Lightning protection, 716
Installation help, 180
Lightning protection zones, 716
PCS 7 plant, 180
Limits, 137
Installation Instructions, 185
of the CPUs for PCS 7 projects, 137
Special features, deviations, 185
List, 512
Installation rules, 185
Driver blocks, 512
Plant change in runtime CiR, 185
Local ID, 446
Integrate, 66, 153
local PC station
Distributed I/O in Hazardous Areas, 153
setting up, 255
Number of actuators, 66
Local PC station, 255
Number of devices, 66
Local time conversion, 228
Number of sensors, 66
Location designation, 637
Interaction between hardware and software, 220
Lock, 326
Interconnect, 470
Lock message attributes against changes to block
Blocks, 470
instances, 326
Interface, 510
Interior Lightning Protection, 716
Introduction, 196, 357, 399
M
CiR, 399
Configuration, 357 Maintenance station, 699
Configure in RUN, 399 Diagnostics with, 699
Multiproject, 196 Manage texts, 270
IP standard, 726 multilingual, 270
ISA-88 type definition, 308 Management levels, 82
of the hierarchy folder, 308 plan with Ethernet, 82
IT, 126 Mass data, 580
PC components, 126 edit in the process object view, 580
Master data library, 310, 312, 315, 319
Blocks, 319
K create, 315
Objects, 312
KNX, 116
connect to PROFIBUS DP, 116
Process object view, 526, 580, 584, 607, 681 connect nodes, 102
editing mass data, 580 connecting the ASI bus, 114
Editing process tags, 526 DP slave, 382
Finding, 584 PROFIBUS PA, 106
Replacing, 584 connect to PROFIBUS DP, 106
test, 607 PROFIBUS PA networks, 109
Test mode, 681 Redundant, 109
Process objects PROFIBUS segment, 98
Book back, 504 Program, 506
Booking, 504 Programming, 508
Counting, 504 SIMATIC connections, 506, 508
Counting and booking, 503 Programs, 565
Displaying statistics, 505 download, 565
Process tag type, 158, 210, 335, 518, 520, 523, 531, Project, 262, 265, 348, 622
629, 633, 639, 643 expand by adding components, 265
Assign an import file, 523 move projects to distributed engineering
change, 520 stations, 348
create, 518 move to a central engineering station:, 622
Exporting, 643 remove from multiproject, 262
import, 639 Project data, 707, 709
Repair assignment, 531 retrieving with a version ID, 709
use, 210 Saving versioned data, 707
work with, 335 Project data - XML format, 693
Process tags, 526, 527 export, 693
adopt, 527 project documentation, 710
create automatically, 525 Create, 710
synchronize, 529 Project library, 310
Process Tags, 382, 517, 522, 525, 529, 630 Project master data, 705, 706
create from process tag types, 517 Archiving, 705
edit, 526 Retrieving, 706
handling, 630 Project versions, 691
insert in project, 522 compare, 691
working with the IEA, 630 Projects, 350
Process type, 46 of projects, 350
Discontinuous, 46 Projects following distributed editing, 621, 622
Process Type merging, 621
Continuous, 46 move to a central engineering station:, 622
Production loss, 69 Projects in the Multiproject, 347
avoid, 69 store, 347
PROFIBUS, 96, 98, 100, 103, 104, 394 project-specific, 353
Configuration of redundant networks, 103 defining a catalog profile for a hardware
connecting non-redundant devices to redundant configuration, 353
systems, 104 Project-specific, 216, 323
electrical transmission media, 98 Adapt blocks, 323
Non-redundant P. on redundant systems, 394 define a catalog profile for a hardware
optical transmission media, 100 configuration, 216
plan the field level, 96 Properties, 148
PROFIBUS DP, 102, 106, 114, 116, 117, 118, 382 ET 200, 148
connect from PROFIBUS PA, 106 ET 200iSP, 148
connect H1 bus (Fieldbus Foundation), 118 ET 200M, 148
connect instabus EIB, 116 ET 200pro, 148
connect KNX, 116 ET 200S, 148
connect MODBUS, 117
Structure, 31, 93, 103, 109, 163, 165, 168, 170, 172, T
650, 718
Target system, 665
Configuration manual, 31
Template, 158
electrical, 718
Terminal bus, 174
Engineering Station, 163
Data Communication, 174
IEA file, 650
Test, 341, 490, 568, 607, 681, 682, 685
OpenPCS 7 station, 172
CFC chart, 490
Operator Station, 165
Field devices, 685
redundant Ethernet networks, 93
In the process object view, 681
redundant PROFIBUS networks, 103
Library objects, 341
Redundant PROFIBUS PA networks, 109
on a running plant, 685
SIMATIC BATCH, 168
Process object view, 607
SIMATIC Route Control, 170
SFC program, 568
Subnet, 428
with S7 PLCSIM, 682
creating and configuring, 428
Test mode, 495
Swap out, 56
Trend display, 495
Archive, 56
Text lists, 330
Switch, 88
Texts, 330
Switching technology, 84, 88
export/import, 330
ESM, 84, 88
tests of relevance to the, 330
OSM, 84, 88
Textual interconnection, 459, 573
SCALANCE X, 84
configuration by several users, 459
Symbolic connection name, 446
Third-party systems, 48
Symbolic names, 382
Communication, 48
Assigning, 382
TIA, 33
Symbols, 366
Time, 381
assign symbols for input and output addresses, 366
Synchronization on the AS, 381
Symmetrical Signal Circuits, 718
Time stamp, 417
Synchronization, 379, 381
Time stamp (10 ms), 417
Time of day on the AS, 381
Time stamp with high precision, 233
Synchronize
Time-of-Day Synchronization, 379, 381
Process tags, 529
Principle, 379
Synchronizing, 529
Setting on the AS, 381
System planning, 39
Topology of the sequential control system, 540
important questions at the start, 39
create, 540
Systems, 42
Totally integrated automation, 33
select, 42
Transitions, 545
to be used, 42
Configuring, 545
Systems to be used, 42
transmission media, 90
find, 42
electrical, 90
select, 42
optical, 90
Transmission rate, 80, 432
changing on the PC network, 432
Trend display, 495
in test mode, 495
Type, 561
compile, 561
U W
Undo, 411 Wall-mounting, 714
used CiR elements, 411 WinCC archive, 56
Update, 321, 329, 663, 667 Work, 214, 317, 335, 337, 646
automatically creating block icons for OS with IEA files, 646
pictures, 329 with libraries, 317
Block type, 321 with models, 337
OS server data, 667 with process tag types, 335
SFC type, 321 with process tags, 630
Updating with SFC types, 209
Imported station configuration, 663 with the master data library/libraries, 214
use, 206, 688 working, 209
Block icon, 206
Block type, 206
Faceplate, 206 X
Model, 213
XML, 217, 693
Process tag type, 210
Use, 136, 210, 213
Version Cross Manager, 688
Y
Use of an automation system, 132
Selection criteria, 132 Y coupler, 394
Used CiR elements, 411 Y link, 394
Undo, 411
User-data management, 50
Using
Fail-safe automation systems, 136
V
Validation, 53
Components, 53
Functions, 53
in accordance with 21 CFR Part 11, 53
Validity, 15
Documentation, 15
Verification, 53
Process management, 53
Version Cross Manager, 687, 688
comparing project versions, 687
use, 688
Versioning, 707
Project data, 707
views
component view, 238
process object view, 243
Views, 238, 241, 243, 246, 247
Correlations, 246
cross-view functions, 247
Plant View, 241