Professional Documents
Culture Documents
Preface,
Contents
Configuring PCS 7 7
Testing 9
Comparing Project Versions
with VXC 10
Service 12
Appendix 13
Index
Edition 07/2005
A5E00346923-02
Safety Guidelines
This manual contains notices intended to ensure personal safety, as well as to protect the products and
connected equipment against damage. These notices are highlighted by the symbols shown below and
graded according to severity by the following texts:
Danger
! indicates that death, severe personal injury or substantial property damage will result if proper
precautions are not taken.
Warning
! indicates that death, severe personal injury or substantial property damage can result if proper
precautions are not taken.
Caution
! indicates that minor personal injury can result if proper precautions are not taken.
Caution
indicates that property damage can result if proper precautions are not taken.
Notice
draws your attention to particularly important information on the product, handling the product, or to a
particular part of the documentation.
Qualified Personnel
Only qualified personnel should be allowed to install and work on this equipment. Qualified persons
are defined as persons who are authorized to commission, to ground and to tag circuits, equipment, and
systems in accordance with established safety practices and standards.
Correct Usage
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
This product can only function correctly and safely if it is transported, stored, set up, and installed
correctly, and operated and maintained as recommended.
Trademarks
SIMATIC®, SIMATIC HMI® and SIMATIC NET® are registered trademarks of SIEMENS AG.
Third parties using for their own purposes any other names in this document which refer to trademarks
might infringe upon the rights of the trademark owners.
Copyright Siemens AG 2005 All rights reserved Disclaimer of Liability
The reproduction, transmission or use of this document or its We have checked the contents of this manual for agreement with
contents is not permitted without express written authority. the hardware and software described. Since deviations cannot be
Offenders will be liable for damages. All rights, including rights precluded entirely, we cannot guarantee full agreement. However,
created by patent grant or registration of a utility model or design, the data in this manual are reviewed regularly and any necessary
are reserved. corrections included in subsequent editions. Suggestions for
improvement are welcomed.
Siemens AG
Bereich Automation and Drives
Geschaeftsgebiet Industrial Automation Systems Siemens AG 2005
Postfach 4848, D- 90327 Nuernberg Technical data subject to change.
Siemens Aktiengesellschaft A5E00346923-02
Preface
Getting Started
PCS 7 Getting Started – Part 1 is intended for newcomers to PCS 7. It provides an
initial overview of the process control system PCS 7 and provides newcomers with
the information they require to create a simple project alone. The project can be
configured on an existing SIMATIC station.
PCS 7 Getting Started – Part 2 is intended for users that have already worked
through Getting Started – Part 1. It introduces you to functions of PCS 7 that you
can use for fast and effective plant configuration. You can use these functions in
particular when you configure large and complex systems.
Both parts of Getting Started introduce the functions based on a concrete sample
project called "COLOR". At the same time, the correct order for creating a
configuration is outlined.
Both parts of Getting Started are available under Start > SIMATIC >
Documentation > English > ....
Required Experience
This ES configuration manual is intended for personnel involved in configuring,
commissioning, and service.
Basic experience of working with the PC/programming device and working with
Windows are assumed.
Validity
The ES Configuration Manual is valid for the software on the DVD "Process Control
System PCS 7 Engineering Toolset V6.1".
Readme File
Please refer to the readme file for important general information:
• The readme file is on the DVD "Process Control System PCS 7 Engineering
Toolset V 6.1".
• You can also open the readme file after installing PCS 7 with the menu
command Start > Simatic > Product Notes > General > PCS 7 Readme.
Further Support
If you have any technical questions, please get in touch with your Siemens
representative or agent responsible.
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 here 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 PCS 7 automation system. 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 A&D 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
12 Service 12-1
12.1 Diagnostics with a Maintenance Station.................................................... 12-1
12.2 Teleservice with PC Anywhere.................................................................. 12-3
12.3 Further Service Support and Diagnostics.................................................. 12-3
13 Appendix 13-1
13.1 Installation Guidelines for PCS 7............................................................... 13-1
13.2 Lightning Protection................................................................................... 13-4
13.3 Electrical Installation.................................................................................. 13-6
13.4 Basics of EMC-Compliant Installation of PCS 7...................................... 13-11
13.5 Degrees of Protection (Housing Protection)............................................ 13-13
Index Index-1
Access options
The following options are available for accessing the PCS 7 documentation:
• PCS 7 computer: help menus in applications
• PCS 7 computer: Windows Start menu
• Internet: Customer Support (http://www.ad.siemens.com/meta/support)
• Internet: at http://www.pcs7.de
• Manual Collection "Process Control System PCS 7 – Electronic Manuals"
Preview
Because the entire documentation of PCS 7 is extremely wide-ranging, you will find
a guideline below that will help you to find the information you require during
various phases:
• Documentation for the planning phase
• Documentation for the realization phase
• Documentation for commissioning, operation, diagnostics and servicing
Documentation Contents
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.A 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 Product Brief 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 you automation requirements.
Getting Started PCS 7 – Uses a simple sample project to show you the fundamental procedures and
First Steps the interaction of the software components of SIMATIC PCS 7 during
engineering and in process operation.
Time required for tutorial: approx. 1 hour
Selecting the components and systems for the PCS 7 plant
Configuration manual Section "Engineering System":
PCS 7 Engineering System • Capacity options in configuring a PCS 7 plant
• Selecting network components
• Selecting PC components for engineering and operator control and
monitoring
• Selecting AS components
• Selecting I/O components
• Preparations for efficient engineering
Manual PC Configuration Comprehensive overview of PC configurations for engineering and operator
and Authorization control and monitoring:
• 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
List PCS 7 - Released List of modules released for PCS 7 versions
Modules
Documentation Contents
Installation
PCS 7 readme Latest information with notes 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 PC Configuration Comprehensive overview of PC configurations for engineering and operator
and Authorization control and monitoring:
• 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
Configuration of components and systems
Configuration Manual Section "Structuring a PCS 7 Project":
PCS 7 Engineering System • Basic configurations of a PCS 7 plant
• Guideline in the installation instructions for the productsauanleitungen
der Produkte
• Special considerations, differences between PCS 7 and specifications in
the installation instructions of the productsauanleitungen der Produkte
• Rules for plant changes during ongoing operation (CiR)
• Configuration guidelines PCS 7: EMC and lightning protection
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
Modules components
• Technical specifications
Manuals for CPs and FMs • Manual for hardware configuration and parameter assignment of
(S7-400, S7-300) components
• Technical specifications
Manuals for ET 200 • Manual for hardware configuration and parameter assignment of
components ET 200M, components
ET 200S, ET 200iSP • Technical specifications
Manuals for additional DP • Manual for hardware configuration and parameter assignment of
components: Diagnostic components
Repeater, DP/PA Link/Y • Technical specifications
Link, DP/AS-i Link
Documentation Contents
Manuals for Industrial • Topologies and Network Configuration
Ethernet and PROFIBUS • Configuration of the communication
networks
Manuals for SIMATIC NET • Topologies and Network Configuration
components: CPs for • Installation instructions
Industrial Ethernet and
• Technical specifications
PROFIBUS, OSM/ESM ...
Engineering
Getting Started PCS 7 - Introduction to the basic functions of PCS 7 based on the PCS 7 project
Part 1 "COLOR". Contains the most important background information required to
(with video sequences) 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 hour
Getting Started PCS 7 - Introduction to using the functions for efficient engineering from PCS 7. This
Part 2 is based on the PCS 7 "COLOR" project configured in Getting Started PCS 7
(with video sequences) - Part 1.
PCS 7 Project "COLOR".
We recommend working through this Getting Started tutorial if you plan to
configure a large PCS 7 plant with a large number of process tags.
Time required for tutorial: approx. 16 hour
Manual Software Update Step-by step instructions on converting your PCS 7 project from PCS 7 V6.0
Without Using New to V6.1 without subsequent use of the new functions of PCS 7 V6.1.
Functions
Manual SW-Update With Step-by step instructions on converting your PCS 7 project from PCS 7 V6.0
Using New Functions to V6.1 and subsequently using the new functions of PCS 7 V6.1.
Manual Brief Instructions Describes how to update software from PCS 7 versions V5.1/V5.2 to V6.1.
on Updating Software This documentation guides through the steps in the manuals for a software
PCS 7 V5.1/V5.2 to PCS 7 update from V5.x to V6.0 and a software update from V6.0 to V6.1.
V6.1
Configuration Manual Sections for configuring the engineering system:
PCS 7 Engineering System • Basic concepts of engineering
• Configuration of the engineering system
• Creating the PCS 7 configuration
• Compiling, downloading, testing, archiving and documenting project
data
Configuration manual Complete information about configuring the PCS 7 operator station, the HMI
PCS 7 Operator Station system of PCS 7:
• Configuring OS data
• Creating process pictures
• Settings in the alarm system
• Options for archiving
• Downloading and project and configuration changes
• Time synchronization and lifebeat monitoring
• Using server-server communication
• Using diagnostic functions (maintenance station)
Manual PCS 7 OS Web • Using the Web client
Option
Documentation Contents
Configuration Manual Complete information about configuring the PCS 7 BATCH station, the
PCS 7 BATCH system for automating batch processes:
• Technological basis according to ISA S88.01
• Configuring batch plant data
• Creating recipes
• Planning and controlling batches
• Managing and archiving batch data
Manual PCS 7 Fault- Informs you about the basic solution concept, the method of operation and
tolerant Process Control the most important configurations to be made when building fault-tolerant
Systems systems using the SIMATIC PCS 7 process control system. It presents fault-
tolerant solutions on all automation levels (control, process, field).
Manual PCS 7 10 ms Time Comprehensive overview of required components, the interaction among the
Stamps components and their configuration for using 10 ms time stamps
Manual PCS 7 Library Description of method of operation, block I/Os and input/output field of the
respective faceplates
Manual PCS 7 Explanation of how AS blocks and faceplates conforming to PCS 7can be
Programming Instructions created to ...
Blocks • 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
Manual PCS 7 Help in creating driver blocks conforming to the system to fully exploit the
Programming Instructions functions in PCS 7
Driver Blocks (not included with PCS 7; must be ordered extra from the PCS 7 Catalog)
@PCS 7 Configuring and using the PCS 7 interface for the plant operations level
Manuals for the individual • Basics of the engineering tool
engineering tools: CFC, • Working with the engineering tool
SFC, STEP 7, SFC
• Testing and commissioning the engineering tool
Visualization, PDM,
WinCC, LT Options, SCL,
DOCPRO
Readme and What's New • Latest information with notes about installation of the engineering tool
for the individual • Compact summary of the new or changed features in comparison to
engineering tools: CFC, previous versions
SFC, STEP 7, SFC
Visualization, PDM, SCL,
DOCPRO
Documentation Contents
Process Mode
Manual PCS 7 OS Process • Graphical user interface and operator input at the PCS 7 OS in process
Control mode:
- Alarm system
- Trend system
- Group display
- Controlling the process
• Working at the maintenance station
Manual PCS 7 OS Web • Working with a Web client
Option
Configuration Manual • Batch control
PCS 7 BATCH • Managing and archiving batch data
Manual Service Support This manual is intended for trained service personnel (Service Level 1):
and Diagnostics PCS 7 users and SIMATIC S7 specialists
The manual contains information providing support for:
• 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
• Maintenance
Manuals for additional DP • Commissioning
components: Diagnostic • Diagnostics
Repeater, DP/PA Link/Y
Link,
DP/AS-i Link
Manual Programming with • Hardware diagnostics and troubleshooting
STEP 7
Basic Layout of the Configuration Manual for the PCS 7 Engineering System
The PCS 7 engineering system configuration manual is divided into three sections:
Section Phase
Selecting the components and systems for the PCS 7 plant
Planning the plant This contains all the information that you need to select the right systems and
engineering components based on the requirements of your PCS 7 plant.
You are provided with a comprehensive overview of the configuration options
for automation systems, distributed I/Os, bus systems and networks for PCS 7.
Configuration of components and systems
Configuration of PCS 7 A guide to manuals containing configuration instructions for the hardware
plants components. You are also provided with notes and information about the ways
in which PCS 7 deviates from other SIMATIC applications.
Engineering
Basic Concepts of This provides an introduction to the requirements for efficient engineering with
Engineering PCS 7 (for example, type-defining, reusability, central editing).
Configuration of the Introduction to the structure and use of the engineering software from PCS 7
PCS 7 engineering
system
Creating the PCS 7 Complete configuration of a PCS 7 project based on step-by-step instructions,
configuration contexts and background information.
Compiling and Information about how configuration data is compiled and downloaded to the
downloading PLCs (AS, OS, BATCH).
Testing This section also provides and overview of the most important testing features
prior to commissioning.
Comparing project This offers instruction on how to use the Version Cross Checker to version and
versions compare various project states.
Archiving and Information about data security and backing up project data
documenting
@
SIMATIC PCS 7 1
3 4 Internet/ Plant Plant
OS 4 3 2
Combined Intranet Information Maintenance
Single Station 4 5
Engineering/ Engineering SIMATIC
(Multi-VGA) Station IT Framework
Operator Station OS Clients BATCH Clients
Maintenance Components
3 4
Station
PCS 7 SIMATIC PDM
BOX Engineering @PCS 7/OPC Server
Toolset
6
Terminal Bus Industrial Ethernet
OS Server Archive Server BATCH Server
Ethernet
4 4 5 Industrial
PROFIBUS DP
PROFIBUS DP
PROFIBUS DP
HART Fail-safe
PROFIBUS DP
INTERFACE
with CP 341
00 7
00 00
s PROFIBUS
Addr.
DP/PA Link
6GK1415-0AA00
9
instabus EIB
Ex
Power DP/EIB-Link
DP/PA Link
DP/BF
EIB/BF
24V EIB
DP/PA Link
Phys. Adr.
63,29
36,72
+/-
.
7
4
8
5
9
6
o CODE
Clear ESC
Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
Zone 1 P RO F I
PROCESS FIELD BUS
Zone 2 BUS
PCS 7 offers a wide range of possibilities for realizing automation tasks. The large
selection and variety of components enables you to
• Use appropriate components to fulfill special requirements
• Select components that can be exactly configured to meet specific
requirements
The following table lists optimally matched systems, components and functions for
specific process control requirements.
Further information
• Section "Capacity Options in Configuring a PCS 7 plant"
• Section "Selecting network components"
• Section "Selecting PC Components for ES, OS, BATCH and IT"
• Section "Selecting AS components"
• Section "Selecting I/O components"
• Section "Preparations for Efficient Engineering"
Type of process
• 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 charts (SFC). The automation
can implemented for small plant units as well as for the entire plant.
• Discontinuous 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.
Further information
• Section "Selecting fault-tolerant and fail-safe components"
• Manual Process Control System PCS 7; Fault-tolerant Process Control
Systems
Note
Please contact your Siemens representative for more information about
communication options.
Selecting components
Select the components that you need for the data link to the third-party systems:
Further information
• Section "Administration Level and Remote Access"
• Section "Data Links to Other Communication Systems"
Further information
• Manual Process Control System PCS 7; SIMATIC BATCH
• Online help Version Cross Checker
• Online help SIMATIC Logon and Electronic Signature
SIMATIC PCS 7 provides a variety of functions for archiving project data and
process values.
Note
Swapped out OS archives can be viewed with the software product StoragePlus
(optional package).
Further information
• Section "Archiving/Retrieving Multiprojects and Project Master Data"
• Manual Process Control System PCS 7; Operator Station
• Manual Process Control System PCS 7; SIMATIC BATCH
Note
No general recommendations can be made for the plant design. The designs
involved in engineering a plant for process automation depend on:
• Laws, standard specifications, norms
• Process and production engineering factors
• Local conditions (location, expansion possibilities, environmental conditions,
etc.)
• Miscellaneous requirements (such as the sensors and actuators employed).
Further information
• Section "Capacity Options in Configuring a PCS 7 plant"
• Section Which Data and Data Formats Can be Imported?
The following table shows the services offered by Siemens for PCS 7 plants:
Field service Fast local help Tel.: +49 (0) 180 50 50 444
Personalized service contracts
Replacement parts Replacement parts and repairs Tel.: +49 (0) 180 50 50 448
Scalability
SIMATIC PCS 7 can be flexibly adapted in a variety of ways for different plant
requirements and sizes. Add-ons and reconfiguration are no problem if the plant is
later expanded or technological changes are made.
SIMATIC PCS 7 covers all plant sizes. Depending on the requirements, for
example, you can:
• Select a variety of powerful automation systems:
- from applications with few control tasks (for example with SIMATIC PCS 7
BOX)
etc.
- to automation solutions for very large production facilities with integrated
process data control
• Install distributed or central I/Os step-by-step
• Configure and scale the display and control components:
- from small single-workstation systems and approximately 160 process
tags, for example for laboratory automation
etc.
- to distributed multiple-workstation systems with client/server architecture
with around 60,000 process tags, for example for automation of large
production facilities
• Scale the number of configurable process objects (software for a variety of PO
quantities)
• Select network components and configure communications networks
• Enhance the functionality by selectively adding a variety of hardware and
software components (for example operator stations with SIMATIC BATCH or
a separate archive server)
• 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?
• How Many CPUs Are Needed for the Automation?
• How Many Devices, Sensors and Actuators Can Be Integrated?
• How Many Operator Stations Are Required?
• What Are the Expansion Limits?
Process objects
A process object is a process tag that is displayed in a CFC chart. A process object
is therefore a functional unit of a process control system.
Plant size
The configurable size of a PCS 7 plant can be scaled to the number of process
objects (PO).
The software product licenses for Engineering, Operator Stations and SIMATIC
BATCH are offered for a various number of configurable process objects (PO). This
number can be increased at any time with additional PowerPacks. The licenses for
SIMATIC PDM are offered for a various number of configurable devices.
Further Information
• Manual Process Control System PCS 7; PC Configuration and Authorization
Note
Multicomputing (synchroneous 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.
Caution
The values shown in the following table are not maximum values for each item
specific to the automation system. They represent an example of a typical
distribution of total available automation system capacity in which all items are
operated together in a contingent block.
Example:
Mixed capacity for automation systems in a PCS 7 plant:
or:
Property Limit
Maximum number of OS server/redundant 12
OS server pairs
Maximum number of OS clients in multiclient 32 per multiple-workstation system
mode (when each OS client has access to all
12 OS servers/redundant server pairs)
Number of process tags Approx. 5,000 per OS server
Approx. 60,000 per multiple-workstation
system
Number of process value/s that can be Approx. 1,000 process value/s with OS
archived server
Approx. 10,000 process value/s with central
archive server (SQL server)
OS areas 64 OS areas in 5 levels per OS server
Maintenance station 1 maintenance station for monitoring
diagnostic variables
Note
Each monitor counts as an OS client when multiple monitors are used.
Maximum length
The following bus systems are used in PCS 7 with the following maximum lengths:
Further information
• Section "Which Networks / Bus Systems Are Used for Communication?"
• Section "Maximum Transmission Rates of the Networks / Bus Systems"
3.4.1 Introduction
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.
Redundancy concept
The components of the PCS 7 enable you to assign any degree of fault tolerance
to all automation levels, from operator stations (control level) to the bus system,
from the automation system (process level) to the distributed I/O (field level).
OSM
ET 200M
7
ET 200M Sensor /
Actuator 8
ET 200M
Fail-safe
Y Link PROFIBUS DP
10
S
63,29
o CODE
Connection non-redundant
PROFIBUS DP devices to
36,72
+/- 7 8 9 Clear ESC
. 4 5 6 Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
redundant PROFIBUS DP
No. in Description
illustration
1 Several OS/BATCH clients can access data on an OS/BATCH server.
An OS/BATCH client can access data on up to 12 OS/BATCH servers or redundant
OS/BATCH server pairs.
2 The terminal bus in ring form is used for the client-server and server-server communication.
This avoids communication failures, for example if the cable is damaged or broken.
The availability can also be increased by building a redundant terminal bus and segmenting
the terminal bus.
3 The OS server and BATCH server itself can be installed with redundancy if required.
A maximum of 32 OS/BATCH clients can access data on an OS/BATCH server or
redundant OS/BATCH server pair.
5 The redundant plant bus (Industrial Ethernet in a ring structure) ensures reliable
communication between automation systems, engineering stations and OS/BATCH
servers.
6 The redundant S7-400H automation system (AS 414H or AS 417H) is connected with an
Ethernet communication processor (CP) to each automation subsystem via the plant bus.
Each automation subsystem can be connected to several PROFIBUS DP lines. The
internal PROFIBUS DP interfaces or additional communication processors can be for
connections.
7 The connection of the ET 200M distributed I/O to the redundant PROFIBUS-DP lines is
made using two 153-2 IMs on a special bus module.
8 You can evaluate the sensor signals with redundant digital or analog input/output modules.
If one of the two input modules fails, the sensor signal continues to be evaluated by the
remaining operational input module.
9 The PROFIBUS-PA I/O is connected to the redundant PROFIBUS-DP by DP/PA Link and
two 157 IMs.
10 The Y-link enables you to connect non-redundant PROFIBUS DP device to a redundant
PROFIBUS DP.
Further Information
• Manual Process Control System PCS 7; Fault-tolerant Process Control
Systems
Fail-safe automation systems are employed for PCS 7 when a fault could endanger
human life, damage the plant or the environment. They detect errors in the
process, even their own internal errors, and automatically bring the plant to a safe
state when a fault occurs.
Safety concept
The fail-safe automation systems from PCS 7 can be configured single-channel (F
system with one CPU) or redundant (FH system).
1 2 3
PROFIBUS DP
F module
ET 200M ET 200M
IM 153 2x IM 153
Isolation module Isolation module redundant
No. in Description
illustration
1 The fail-safe S7-300 signal modules are connected via the ET 200M to the fail-safe
S7-400F automation system (AS 414F or AS 417F).
2 Fail-safe automation system can also be configured redundantly. The use of the fail-safe
and fault-tolerant S7-400FH automation system (AS 414FH or AS 417FH) for PCS 7
provides optimum safety and availability.
3 Fail-safe S7-300 signal modules (F modules) can also be redundantly connected to
increase availability even further.
Safety mechanisms
• The PROFIsafe profile is used for safety-related PROFIBUS DP
communication between the F CPU and distributed I/O. Based on this safety
frame, the fail-safe automation systems and signal modules can recognize
corrupt user data and trigger appropriate error responses.
• 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).
• Additional safety is provided by functions such as the comparison of
F programs, detection of F program changes per checksum and access
authorization per password.
Note
An error detected in the F program does result in a CPU STOP; it triggers a
definable reaction that brings the affected F runtime group or the entire F program
to a safe state.
Using ET 200S
ET 200S can also be centrally connected to a fail-safe S7-400F/FH automation
system by using a fail-safe power module. 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
Refer to the catalog Add Ons for the Process Control System SIMATIC PCS 7
(Catalog ST PCS 7.A) to learn which selected standard components can be
integrated into a fail-safe automation system.
Further Information
• Manual SIMATIC Programmable Controllers S7 F/FH
• Manual S7-300 Fail-safe Signal Modules
• Manual SIMATIC ET 200S Distributed I/O System
The safety and availability requirements are also decisive factors in the selection of
fault-tolerant and fail-safe components for a plant. The following table provides
recommendations for components based on the level of requirements for systems.
SIMATIC NET
SIMATIC NET includes
• Communication network consisting of transmission medium, corresponding
connection and transmission components and the respective transmission
methods
• Protocols and services used for data communication between the components
• Communication modules of the automation systems that establish the
connection to the communication network (e.g. communication processors
(CP)).
Further information
Refer to the following SIMATIC NET manuals for additional information about
network architecture, network configuration, network components:
• List PCS 7 - Released 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
• Manual Industrial Ethernet OSM/ESM; Network Management
• Manual SIMATIC NET; AS Interface – Introduction and Basic Information
The following table shows you the network / bus systems used for the
communication between components in a PCS 7 plant.
The following table provides an overview of the most important decision criteria for
the use of network / bus system:
The following table lists the maximum transmission rates of the network / bus
systems. The transmission rate depends on the network physics:
• Electrical network: Network installed with electrical conductive connections
(copper cable)
• Optical network: Network installed with fiber-optic cables (FO)
Note
Isolation of the plant bus and terminal bus is always recommended but not an
absolute necessity.
The connection to the MES layer should always be made through a router to
protect against unauthorized access to the process control system (e.g. by
computer viruses in office applications).
1 3 2 3 1
OSM OSM
Network 1 Network 2
OSM in
4
OSM TP62 OSM TP62
OSM OSM
ESM ESM
Network 3
5
ESM
6 6
1
3
ELM
Further information
Section "Data Paths over the Terminal Bus and Plant Bus"
Further information
• Manual Industrial Ethernet OSM/ESM; Network Management
Network Module
Ethernet
Industrial Ethernet
Industrial
Automation System
CP 443-1
Connection of the AS
The automation systems are connected to Industrial Ethernet via TCP/IP, ISO and
UDP using the CP 443-1 communication processor.
Note
Communication can be established with up to 64 automation systems (including
redundant systems) via the CP 1613.
Time-of-day synchronization
CP 443-1 and CP 1613 support time synchronization over Industrial Ethernet (Fast
Ethernet). A PC with a CP 1613 can receive time-of-day frames from the following
time-of-day transmitters:
• SIMATIC S7-400/H/FH with CP 443-1
• SIMATIC NET time transmitter for Industrial Ethernet (see catalog IK PI)
• SIMATIC SICLOCK
• PC with CP 1613
Further information
Section Data Paths over the Terminal Bus and Plant Bus
Redundant
OS Server Pair
Synchronization Lines
Further information
• Section "Use of switching technology"
• Manual Process Control System PCS 7; Fault-tolerant Process Control
Systems
PROFIBUS networks can be built using the following components based on the
transmission medium used and the devices to be connected:
• Optical Link Module (OLM)
• Optical Bus Terminal (OBT)
• Y Link
• DP/PA coupler and DP/PA Link
• Diagnostic repeater
• RS 485 repeater
• RS 485 terminating element
Automation System
Long distances
with fiber optic
PROFIBUS DP
s
S
V
B
H
N
T
W
C
I
O
U
X
SIMATIC PANEL PC
D
J
P
7
E
K
Q
8
F
L
R
4 5 6
Y Z A
1 2 3
. 0 +/-
INS
DEL
ESC
TAB
HELP ACK
Integrated:
- Power supply
- Terminal resistor
PROFIBUS DP
- Ex isolation
PROFIBUS PA
Ex
DP/PA Link
Ex isolation
and repeater ET 200iSP
PROFIBUS DP/iS
Ex
1
0
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 cable length of a segment depends on the:
• Transmission rate
• Type of cable
The maximum cable length of a PROFIBUS segment is limited: see section
"Maximum Transmission Rate of the Networks / Bus Systems").
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 cable lengths are possible when RS 485 repeaters are used between two
nodes:
Further information
• Manual SIMATIC Net PROFIBUS Networks
Note
Recommendation: Fiber-optic cable should be the preferred for long distances and
when connecting between buildings.
Glass fiber-optics or plastic fiber-optics are used as the transmission media for
optical PROFIBUS networks.
Fail-safe
Automation System AS 414F/AS 417F
IM 153-2
PROFIBUS DP
Copper Cable
ET 200M
with standard I/O modules
IM 153-2 FO
OBT
ET 200M
with fail-safe I/O modules
IM 153-2 FO
OBT
ET 200M
with fail-safe I/O modules
Further Information
• Manual SIMATIC NET; PROFIBUS Networks
• Manual SIMATIC Net; Twisted Pair and Fiber-Optic Networks
Automation System
ET 200M
PROFIBUS DP
ET 200M
Connection of the AS
The connection of the automation systems to the PROFIBUS DP is made via:
• CP 443-5 Extended or
• Internal DP interface of the CPU
The PROFIBUS DP lines can be connected to up to 4 internal DP interfaces per
automation system (with add-on modules depending on the CPU) and also to up to
10 CP 443-5 Extended. IF 964-DP interface modules are available for the DP
interfaces. These can be installed in available module slots of the CPU.
Redundant PROFIBUS DP
The fault-tolerant S7-400H automation system features a PROFIBUS-DP master
interface on each CPU for connecting to PROFIBUS-DP. For switched distributed
I/O, the connection to the I/O device is made through two IM 153-2 interface
modules.
The following fault-tolerant communication configurations are offered for
PROFIBUS-DP:
• Redundant PROFIBUS-DP as an electrical network
• Redundant optical network with OLM with line, ring and star structure
Redundant I/O
ET 200M module
Sensor
Further 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.
2 x IM 157
PROFIBUS DP
63,29
36,72
+/- 7 8 9 Clear ESC
. 4 5 6 Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
Y Coupler
Connection non-redundant
PROFIBUS DP device to
redundant PROFIBUS DP
Note
Use only the active backplane bus module when configuring the Y Link.
Further information
• Manual DP/ PA Link and Y Link Bus Connections
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 the physical link between the PROFIBUS-DP and
PROFIBUS-PA. The DP/PA coupler is available for hazardous and non-hazardous
areas.
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
stand-alone (without IM 157).
Automation System
DP/PA Coupler
PROFIBUS PA
PROFIBUS DP
IM 157
DP/PA Link
(max. 5 DP/PA Coupler)
PROFIBUS PA
Further information
• Manual DP/ PA Link and Y Link Bus Connections
Diagnostic Repeater
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.
Long distance
with fiber optic
Diagnostic
PROFIBUS DP Repeater
OLM OLM s
POWER TEMP
SIMATIC PANEL 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
PROFIBUS DP
ESC
TAB
HELP ACK
PROFIBUS PA
Ex
DP/PA Link
Ex isolation
and repeater
PROFIBUS DP/iS
Ex
1
0
Properties
The diagnostics repeater has the following features:
• Diagnostics function for two PROFIBUS segments: The diagnostics function
reports the location fault and cause line faults such as wire break or missing
terminal resistors.
• Repeater function for three PROFIBUS segments: The diagnostics repeater
amplifies data signals on bus lines and connects the individual RS 485
segments.
• Transmission rate: from 9.6 Kbps to 12 Mbps
See also section Maximum Transmission Rates of the Networks / Bus
Systems"
• Cable length: When standard cables are used, the diagnostics repeater can
monitor a maximum of 100 meters of cable in each PROFIBUS segment.
Note
Only use the active backplane bus module.
Further information
• Manual SIMATIC Diagnostics Repeater for PROFIBUS-DP
• Manual Process Control System PCS 7; Service Support and Diagnostics
Within the context of PCS 7, Totally Integrated Automation (TIA) provides solutions
for configuring a wide range of communication tasks.
AS interface
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.
Automation System
ET 200M
AS Interface
PROFIBUS DP
INTERFACE
M M M
DP/AS-i Link Actuators/
Sensors
Branch M M
AS-i
Power Supply
Further information
• Manual SIMATIC Distributed I/O Device DP/AS-i Link
• Manual SIMATIC NET DP/AS Interface Link 20
• Manual SIMATIC NET DP/AS Interface Link 20E
Instabus EIB
Instabus EIB (European Installation Bus) is an open standard for building
automation.
Automation System
instabus EIB
DP/EIB Link 00
00 7
00
00
00
PROFIBUS DP
s PROFIBUS
Addr.
6GK1415-0AA00
instabus EIB
Power DP/EIB-Link
DP/BF
EIB/BF
24V EIB
Phys. Adr.
Area Coupler
Station
0 1
Bus line
DP/EIB link
The following DP/EIB links can be used:
• DP/EIB Link with IP20 protection
Further 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 transmission rate of a maximum 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 need to be ordered separately.
Further information
• Manual SIMATIC CP 341 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
SIMATIC IT
SIMATIC IT is an engineering platform for e-manufacturing based on the ISA S95
standard. According to this standard, explicit business and production rules
coordinate functionality to achieve optimal workflow.
The main elements of SIMATIC IT are:
• SIMATIC IT Framework
• SIMATIC IT components
SIMATIC IT Framework
SIMATIC IT Framework connects the automation level to the operational
management and production control levels, as well as to the company
management and planning levels.
SIMATIC IT Framework is cross-industry integration and coordination platform for
operating processes, data and functions and possesses the facility for plant and
production modeling in addition to the basic functions for internal sequence control,
user administration etc.
SIMATIC IT components
SIMATIC IT components are standard products made available to various industrial
sectors by IT functions defined in line with ISA S95, for example:
• Production Suite (basic MES functions such as material management,
production order management)
• SIMATIC IT Historian (plant performance analysis)
• SIMATIC IT Unilab (laboratory information management system)
• SIMATIC IT Interspec (product specification management system)
• Detailed Production Scheduler
• SIMATIC IT Suite Libraries
Connecting to PCS 7
The SIMATIC PCS 7 process control system can be integrated into SIMATIC IT
Framework through the CP 443-1 IT.
Further information
Refer to the following for more information:
http://www.ad.siemens.de/mes/simatic_it/index_00.htm
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.
Further information
• Documentation OLE for Process Control Data Access Standard, Version 2.0
• You can contact the OPC Foundation in the Internet at:
http://www.opcfoundation.org
@PCS 7
@PCS 7 is software based on @aGlance that provides access to process data
acquired with SIMATIC PCS 7. @PCS 7 provides access to the following PCS 7
data:
• WinCC archives (message, measured value and user archives)
• WinCC data management
Each @aGlance-compliant client application of MIS/MES is therefore capable of
accessing the data of PCS 7.
@aGlance
@aGlance is communication software for the exchanging information between a
variety of industrial data sources such as Scada packages, process control
systems and programmable controllers. The Web technology of web@aGlance
provides a standard for visualization and analysis of process data via the Internet.
Using the standards provided by @aGlance, the visualization and analysis of the
data can be performed on any computer regardless of the operating system - and
also via Intranet and Internet. You can analyze, process and evaluate data using
tools such as Excel or Visual Basic applications.
Connecting to PCS 7
@aGlance is already integrated in every PCS 7 OS in the form of an @PCS 7
server. A Web@aGlance packages and a normal Web browser are the only things
needed for read access on the target PC. An additional license for @PCS 7 needs
to be installed on the PCS 7 OS to activate write access and communication with
other @aGlance servers.
When @PCS 7 is started on the PCS 7 OS, the @PCS 7 system desktop opens. It
allows access to the @PCS 7 system and a variety of @PCS 7 editors in which
you can perform a range of tasks for communication with the plant operations level.
An administration tool is available to configure logon activities with access
permission.
Because you can freely select operating systems and applications for the server
and clients, you can implement @aGlance regardless of the existing hardware and
software architecture. You are therefore not limited to specific providers or systems
that are installed or will be installed in the future in your company.
Web-Browser
- Internet-Explorer
- Netscape
Internet/
Client Applications Intranet
- Microsoft Excel
- InfoPlus.21
- MATLAB
- Application with
Visual Basic C++ Web-Server
@aGlance/IT
Web@aGlance
Client Add-ons
Network
@PCS 7 Server
@aGlance/IT
Server Add-Ons
@PCS 7 Web Read Access
@PCS 7 Web Write Access
@PCS 7 Full Client Access Server Applications
@PCS 7 Server To Server - Other PLS
- Process histories
SIMATIC CS 7
Operator Station
Further information
• Manual SIMATIC @PCS7 V6.0; Interface to Plant Operations Level
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.
Further information
• Manual Process Control System PCS 7; PCS 7 OS Web Option
Note
• PCs with higher CPU speeds, more RAM and larger hard disks are an
advantage for engineering stations when working with multiprojects. Faster
hard disks are also advantageous in such circumstances.
• More RAM is recommended for archive servers.
• We also recommend CPU speeds above 2 GHz or dual processor systems for
BATCH servers.
Color monitor
We recommend monitors with a resolution of 1280 x 1024 or higher in order to fully
exploit the graphic potential of the PCS 7 software.
Network
The network for PCS 7 systems must be isolated using switches, routers or
gateways to prevent disruption to the PCS 7 network from office networks, for
example.
Further Information
• Manual Process Control System PCS 7; PC Configuration and Authorization
Basic hardware
Special versions of the basic hardware (bundles) are available for engineering
stations (ES), operator stations (OS), BATCH stations (BATCH) and for connecting
SIMATIC PCS 7 to the IT world. The bundles are optimized for special applications.
Color monitors
The Siemens industrial monitor range SCD, SCM and CRT are available for the
PCS 7 process monitors. These are selected based on the ambient temperature of
the plant.
Up to 4 monitors can be connected to a workstation (OS client) via a multi-VGA
card. Plant areas divided in such a way can be operated with 1 keyboard and 1
mouse.
Further Information
• Catalog ST PCS 7
• Catalog ST PCS 7.A (add-ons for SIMATIC PCS 7)
Sound card
You can also use a standard sound card installed in the operator station.
Further Information
• For more information about the features and installation of signal modules,
refer to the manual Process Control System PCS 7, WinCC Basic Process
Control
• For more information about the configuration of audible signal devices, refer to
the configuration manual Process Control System PCS 7; Operator Station
Selected components from SIMATIC S7-400 form the basis of the PCS 7 process
control system. The following can be configured by selecting hardware and suitable
software:
• Standard automation systems
• Fault-tolerant automation systems (H systems)
• Fail-safe automation systems (F systems)
• Fail-safe and fault-tolerant automation systems (FH systems)
Configuration in RUN
The automation systems released for PCS 7 support the "Configuration in RUN"
function:
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.
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
Synchronization modules are used to link the two central processing units. They
are installed in the central controller module and interconnected with fiber-optic
cable. Two synchronization modules are installed in each central controller.
The following table provides an overview of the limits for the most important
performance specification of the CPUs used in PCS 7 projects:
The following table shows the default parameters regarding the performance of the
CPUs for PCS 7 projects. These values are set as defaults in the configuration of
the CPU with PCS 7 software.
They suffice for typical applications but can be changed within limits as required for
configuration.
Parameters 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
cycle
OB85 call for process update on the Only for incoming and Only for incoming and Only for incoming and
system outgoing errors outgoing errors outgoing errors
Cycle monitoring time [ms] cycle 6,000 6,000 6,000
Minimum cycle time [ms] cycle 0 0 0
Local data: priority class: 1,024 1,024 1,024
1-2, 9-12, 16, 24-28
Local data: priority class: 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
Diagnostics buffer number of 3,000 3,000 3,000
elements
Instances for alarms and 600 1,800 3,000
communication calls
Module finished message 650 650 650
monitoring time [100] ms
Parameter monitoring time [100] ms 600 600 600
QTM out out out
Reasons for STOP message in in in
Startup mode Warm restart Warm restart Warm restart
Clock memory None None None
Time-of-day synchronization None None None
Engineering Station
inlcuding license
S7 H System
Operator Station
(plant visualization)
Ethernet
Redundant I/O
ET 200M module
Sensor
Combined Operation
Note
It is possible to operate the fault-tolerant and standard automation systems in
combination.
Further 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. It is not used for fault detection; it serves only to increase
the availability of fail-safe automation systems.
Engineering Station
inlcuding option package
S7 F system
S7 H system
Operator Station
(plant visualization)
Ethernet
Plant Bus Industrial Ethernet
Industrial
ET 200M
PROFIBUS DP
PROFIBUS DP
PROFIBUS DP
F Module
ET 200M ET 200M
IM 153 2x IM 153
Isolation Module
F system FH system FH system with
redundant I/O
Further information
• Manual SIMATIC Programmable Controllers S7 F/FH
• Manual Automation System S7-300; Fail-safe Signal Modules
3.8.1 Introduction
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.
All other signal modules from the current S7-400 and S7-300 product range can
also be used. When these other signal modules are used, however, the integration
is limited to process data, which means the full diagnostics capability of PCS 7 is
not automatically available.
Note
The following PCS 7 functions cannot be used with central S7-400 signal modules:
• Configuration in RUN
• Signal modules redundancy
• Fail-safe signal modules
Ethernet
Plant Bus Industrial Ethernet
Industrial
Automation System
ET 200M
HART
c
ET 200iSP
1
HART
0
PROFIBUS DP connection
via ET 200iSP
Ex
DP/PA Link
PROFIBUS PA
PROFIBUS DP connection
via DP/PA Link
Field devices on
S PROFIBUS DP
o CAL oLIM oAR o CODE
63,29
36,72
+/- 7 8 9 Clear ESC
. 4 5 6 Info
0 1 2 3 Enter MEAS
ULTRAMAT 6
The following table shows the automation systems in which the distributed I/O
system ET 200 can be used.
Further information
Section "Overview of Usable Distributed I/O System ET 200 "
The following table provides an overview of the most important properties of the
distributed I/O system from ET 200 used in PCS 7.
What is HART?
HART (Highway Addressable Remote Transducer) is serial transmission method
used to transmit additional parameter data such as measurement range, damping
etc. to connected measuring transducers and actuators over a 4-20 mA current
loop.
Use in PCS 7
• HART devices can be connected to the distributed I/O system ET 200M in both
standard environments as well as 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 and HART actuators certified for digital communication using the
HART protocol can be connected through the ET 200M and ET 200iSP.
Example Configuration
ET 200M
HART
c
ET 200iSP
1
HART
0
Further information
Section Rules for Configuration Changes in RUN (CiR)
Standard OS
Automation
Systems
Intrinsically safe
PROFIBUS DP
HART
c
COMMUNICATION FOUNDATION
M
Acuators/
Sensors
PROFIBUS DP/iS ET 200iSP
M
Ex
M Acuators/
Sensors
HART
c
COMMUNICATION FOUNDATION
DP/PA Link
PROFIBUS PA Zone 0
Zone 1
Zone 2
Legend to illustration
Further information
• Section "Import and Reuse of Plant Data"
• Section Adopting the Data from the Plant Engineering"
Introduction
• 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 Process
Control Library.
• It is also recommended to assemble similar function to improve the efficiency
of the plant engineering. The configuration of similar functions can be achieved
by implementing repeatedly used objects (such as process tag types and
models).
Further information
• Section "Adopting the Data from the Plant Engineering"
1 2 3
Ethernet
Industrial Ethernet
Industrial
Automation System
AS 400 Central I/O
4
PROFIBUS DP
Distributed I/O
Legend to illustration
Further information
• Section "Connecting Network Nodes to Ethernet"
• Section "Connecting PROFIBUS DP Nodes"
Engineering Station
Engineering stations are PCs on which the PCS 7 engineering software for
configuring a PCS 7 project is installed.
An engineering station must be connected to the plant and terminal bus to
download the configuration data to the PLC (OS, BATCH, AS) and test in process
mode.
PCS 7 ES
Redundant Redundant
OS Server OS Server BATCH Server
Ethernet
Plant Bus Industrial Ethernet
Industrial
• For large plants - PCS 7 project engineering with several engineering stations:
Further information
• Section "Connecting Network Nodes to Ethernet"
• 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 Authorizations.
• Configuration 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 exchange 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 workstation or multiple workstation system with
client/server architecture.
When installing a multiple workstation system, a terminal bus (separate from the
plant bus) is recommended for data communication between OS clients and the
OS server. The process values archive can be stored on separate archive servers
to improve performance.
To increase availability, operator stations can be set up redundantly.
OS Servers
max. 12 (redundant)
Ethernet
Plant Bus Industrial Ethernet
Industrial
Further information
• Section "Connecting Network Nodes to Ethernet"
• Section "How Many Operator Stations Are Required?"
• For detailed 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.
• Configuration manual Process Control System PCS 7; PCS 7 Box
BATCH station
BATCH stations are PCs on which the SIMATIC BATCH is installed. The BATCH
station is connected to the terminal bus to allow data exchange with the operator
station. In process mode, the BATCH station communicates with the automation
system only over the operator station.
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 workstation or multiple workstation 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.
Redundant Redundant
OS Server BATCH Server
Industrial
Automation
Systems
Further information
For detailed information about the configuration of BATCH stations and the
installation of the operating system and PCS 7 BATCH software including the
required authorizations, refer to the manual Process Control System PCS 7; PC
Configuration and Authorizations.
4.3.1 Data Paths over the Terminal Bus and Plant Bus
The following illustration shows the communication paths over the terminal bus and
plant bus.
Automation Systems
Topology Options
The plant bus and terminal bus can be configured as:
• Industrial Ethernet (10/100 Mbps)
• Bus, tree, ring, star or redundant ring structures
Properties of Industrial Ethernet: see section "Areas of Application and Parameters
of the Network/Bus Systems"
Further information
Refer to the following documentation for additional information about network
architecture, network configuration, network components and installation
instructions:
• List PCS 7 - Released Modules: contains SIMATIC NET components released
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
• Manual Industrial Ethernet OSM/ESM; Network Management
• Manual SIMATIC NET; AS Interface – Introduction and Basic Information
Further information
• List PCS 7 - Released Modules
• 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
• Configuration manual Process Control System PCS 7; SIMATIC PCS 7 BOX
Note
Information relating to installation in the project documentation manuals for
SIMATIC components is also valid when PCS 7 is used. The few exceptions
relating to installation are described in the section "Supplements to the Assembly
Instructions for PCS 7 Products".
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. This means no QBAD is reported when the load voltage fails on the
channel drivers.
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.
Below, you will find an introduction to the basic mechanisms of engineering with
PCS 7. The main emphasis is on PCS 7 functions that allow rational configuration:
• Central, Plantwide Engineering
• Creating Projects with the PCS 7 Wizard "New Project"
• Distributed Engineering
• Typing, Reusability, and Central Modifiability of Engineering Data
• Import and Reuse of Plant Data
• Free Assignment between Hardware and Software
• Deriving the Picture Hierarchy and OS Areas from the PH
• Generating Block Icons
• Generating Operator Texts
• Basic Concepts of the PCS 7 Message System
Engineering System
The engineering system is made up of coordinated applications that allow central,
project-wide engineering of all components of 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 activities (CFC, SFC,
PCS 7 Library)
• Configuration of discontinuous process activities - batch processes (SIMATIC
BATCH)
PCS 7 Engineering
Import/ CFC/SFC HW WinCC Faceplate SIMATIC F-Tool SIMATIC
Export Config Graphics Designer BATCH (S7 F Systems) PDM
Libraries
Assistant Designer
SIMATIC Manager /
Uniform Database
Further information
• Section "PCS 7 Applications and How They Are Used".
Introduction
The "New Project" PCS 7 Wizard makes it easier to create a new PCS 7 project
because all the necessary objects can be created automatically.
The "New Project" PCS 7 Wizard is started in the SIMATIC Manager.
The next section must explain the advantages of using the wizard.
Note
We recommend that you always create a multiproject even if you only want a
single PCS 7 project because the master data library is then also created and
managed in the multiproject.
Working with a multiproject has many advantages and subsequent extension of the
project poses no problems.
All the information in the following sections relates to a project in a multiproject.
Result
In multiproject engineering, a multiproject is created with a subproject in the
SIMATIC Manager in keeping with the preview (see figure above). The preview is
adapted to the selected settings and shows you the structure that has been created
by the wizard.
A master data library with the following content is also created:
• In the plant hierarchy: one folder for process tag types and one for models
• In the Component view: one S7 program with the folders for sources, blocks
and charts
Subsequent Expansion
Subsequent expansion of the multiproject by adding projects and objects is done in
the SIMATIC Manager.
Further information
• Section "How to Create a new Multiproject with the PCS 7 Wizard".
Introduction
PCS 7 provides the following options to allow more than one configuration engineer
to work at the same time:
• Configuring in a Multiproject
• Branching and Merging Charts of a Project
If the project data is located on a central server, it can be exchanged between the
engineering stations (for example, project-specific block library):
• Configuring in a Network
Application
You use multiproject engineering when you want to work on large-scale projects
with several project teams at the same time.
To allow this, you divide up the automation solution technologically into several
projects. The projects are created on a central engineering station below a
"multiproject" and distributed to the individual computers of the configuration
engineers (distributed engineering stations) for editing. After editing and returning
the projects to the multiproject, data relevant to more than one project can be
synchronized with system support.
Note
• A project of a multiproject must only be edited by one engineer at any one
time.
• The smallest possible unit of a project is an AS or an OS.
• Move only entire projects to the distributed engineering station.
• Only move the objects (AS, OS) in the form of a project to a distributed
engineering station that are actually needed for editing there. This means that
all other objects of the multiproject are available for editing on other distributed
engineering stations.
• An OS server must include all the technological hierarchies of the automation
systems assigned to it.
Note
Requirement: For distributed engineering (for large projects), Windows 2003
Server or Windows 2000 Server must be installed on the central engineering
station to allow work over the network. The distributed engineering stations can
use the Windows XP / 2003 Server / 2000 Professional operating system.
Step Description
1 Create the multiproject with one project and the master data library on the central
engineering station (with the "New Project" wizard)
2 Create further projects and the master data library of the multiproject on the central
engineering station
3 Move the projects and the master data library in the multiproject to distributed engineering
stations
4 Distributed editing of the projects
5 Return the distributed projects to the central engineering station
6 Run cross-project functions on the central engineering station
Note on step 3 - Recommended time for moving out for 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 take the following steps
on the central engineering station first:
• Create the multiproject with the individual projects
• Create the AS and PC stations for OS and BATCH below the individual
projects
• Create the structure of the plant hierarchy
• Create the master data library with the objects common to the projects
Creating the configuration in the section "Creating the PCS 7 Configuration" is
described according to this procedure.
Note
While cross-project functions are executing, all the projects involved must exist
physically in the multiproject on the central engineering station and it is not
permitted to work on them at this time.
Further information
• Online help of STEP 7
• Section "How to Add Projects to the Multiproject"
• Section "Distributing the Multiproject for Distributed Editing (Multiproject
Engineering)"
• Section "Merging Projects after Distributed Editing (Multiproject Engineering)"
• Section "Additional PH Functions in a Multiproject"
Application
Branching and merging to allow editing by several configuration engineers is also
possible at the chart level (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 by textual interconnections.
On completion of editing, the parts are copied back to the original project. Charts
with the same name are replaced (following a prompt for confirmation). The textual
interconnections are then re-established.
Note
This option of distribution (branching) can be used independent of multiproject
engineering or in addition to multiproject engineering.
Within the context of multiproject engineering, the master data library is the basis
for separate work on charts of a project.
Step Description
1 Copy a technological part of the project (single chart, several charts) to a different project.
Result: The copy contains textual interconnections to all sources not located in the copied
parts.
2 Edit the copied part separately (add, delete, modify blocks and charts)
3 Copy the edited technological part back to the original project
Result: The system first deletes the charts with the same names in the original project.
There are now textual interconnections in all charts that expect data from the deleted charts.
The system the copies the charts from the other project.
4 Re-establish all textual interconnections with the menu command
Result: The interconnections are established again 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.
Further information
• Section "Configuration by Several Users (Textual Interconnections)"
Application
If several engineers need to work at their engineering stations in a network on one
project located on a central server at the same time, this is possible for defined
parts of the project (such as AS, OS).
Note
Working in a network on project data located on a central server should only be
used in multiproject engineering for the data exchange between the engineers (for
example master data library with process tag types and models).
Caution
• At any one time, only one engineer can access the data of one project.
• At any one time, only one engineer can access the data of an OS (blocks
WinCC Explorer).
• When working on tables that can contain data from different projects, make
sure that these projects are not edited by other users at the same time.
• Only one commissioning engineer can work on the plant hierarchy of a project
at any one time. This also applies to the properties of the hierarchy folder.
• No configuration work must be done in the following situations (applies within a
project):
- During compilation and downloading of S7 programs
- During compilation and downloading of PCS 7 objects (OS, AS, BATCH)
- During reorganization of the project
- During import or export with the Import/Export Assistant
Principle
During plant engineering, plant parts, functions or program parts result that differ
from each other only in a few aspects.
To work efficiently, you can create basic elements (units, program sections etc.)
that can be reused and simply need the current parameter settings to be supplied.
Note
The advantage of the type-instance concept is that they can be modified centrally.
This means that changes can be made later to the centrally located types block
types, SFC types, process tag types and models and the changes then adopted in
all instances and replicas.
Refer to the online help systems of CFC, SFC, and IEA to find out which type
changes can be accepted by the instances and replicas.
Block Type
Block types are pre-programmed program parts for processing repeated functions
that can be inserted in CFC charts. When they are inserted, a block instance is
created from the block type, and parameters can then be set for the instance and it
can be interconnected. The block type determines the characteristics for all
instances of this type.
Block types can be adapted to project requirements (for example adapting operator
texts; showing/hiding parameters). To ensure that only one version of a block type
is used throughout a project, all block types should be stored centrally in the
master data library and all adaptations should be made prior to instantiation.
Caution
By storing block types in the master data library, you make sure that only one
version of a block type (with one type name) is used throughout the project.
Different block types in different programs can lead to conflicts if the programs are
to be controlled and monitored on one OS. The reason for this is that variables of
the same block type (same type name) must also have the same structure.
Central Modifiability
If the interface description and/or the system attributes of a block type are modified
and this is imported into the CFC data management, an existing block type of the
same name can be replaced by this new version (updated). All block instances of
this type are also modified so that they match the new block type.
The ability to make central type modifications relates to FBs and FCs.
Before the central modification is made, a warning is displayed pointing out the
effects and with information on the old and new block type such as the name, date
of the last interface modification etc.
Central type modification can, in some circumstances, have undesired effects on
the block instances; in other words, interconnections and parameter settings can
be lost. In this case, you must make any adaptations necessary to the block
instances yourself.
A log is kept of the changes made during a central type modification and displayed
automatically following the update. You can also display this log later with the
menu command Options > Logs: Block Types.... If adaptations of the block
instances are necessary, the log can be used as support to reduce both effort and
the risk of errors.
Further information
• Manual Process Control System PCS 7 Library
• Manual Process Control System PCS 7; Programming Instructions Blocks
• Section "Adapting Blocks to Project Requirements"
• Online help in CFC
Central Modifiability
When a process tag type is modified, the process tags existing in the project are
automatically synchronized. If actions are taken that cause inconsistencies
between the process tag type and process tags (for example when some process
tags of the project were not available at the time of the automatic synchronization),
synchronization can also be started explicitly by a menu command.
Note
Modifications that you make in the chart of the process tag type are not taken into
account when the process tags are synchronized. This case, you must first delete
the relevant charts and then repeat the import for the modified process tag type
with the Import/Export Assistant. The easiest way to achieve this is to activate the
"Delete" option in the import file.
For process tag type that is already been created or a process tag derived from it,
the names of the blocks must not be modified again. Import/export would otherwise
be impossible.
The assistant can resolve the following inconsistencies between the process tag
type and the process tags.
• Parameters/flagged signal I/Os and messages that do not exist in the process
tag type are removed from the process tags, in other words, the relevant
attributes are reset.
• Parameters/flagged signal I/Os and messages that have been redefined in the
process tag type are added to the process tags, in other words, the relevant
attributes are set.
• Categories changed in the process tag type are corrected in the process tags.
• Inconsistencies between the process tag type and the process tag that cannot
be synchronized automatically are entered in the log.
During this procedure, all the projects in the multiproject should be available.
Example: Level control process tag as a basis for creating a process tag type
In the following example, the process tag is a CFC chart (with additional attributes)
for signal acquisition, signal preprocessing, automation, operator control and
monitoring of the control system function level control. It has the following features:
• A level sensor is fitted to a tank. This converts the level from 0 through 1500 l
to a current of 4 – 20 mA.
• The signal cable is connected to a channel of an analog input module. The
signal has a name contained in the signal list of your plant. This raw signal can
be accessed by the automation blocks using the signal name.
• A driver block for analog value input (CH_AI) converts the raw signal to a
preprocessed signal (0 through 1500 l) um.
• A controller block (CTRL_PID) calculates a manipulated variable from 0
through 100% from the setpoint and process value (supplied by the level
sensor).
• A driver block for analog value output (CH_AO) converts the signal to the raw
signal and passes to an analog output module.
• A control valve is connected to the analog output module over a 4 – 20 mA
current lead. At 4 mA, the valve is closed, at 20 mA it is fully open, at values
between it is in an intermediate position.
• The controller block has a faceplate on the OS as well as archive tags for
setpoint and process value and messages for violating the high and low level
limits.
Based on a process tag defined in this way, it is possible (on completion of the test)
to create a process tag type with Import/Export Assistant.
Further information
• Section "Creating Process Tags from Process Tag Types (Multiproject)"
SFC Type
SFC types allow sequential control systems to be defined as reusable templates.
An SFC type is a sequential control system that can be configured in the SFC
editor and inserted into a CFC chart. When it is inserted, an executable SFC
instance is generated. SFC instances are displayed as blocks with an interface in
the CFC chart (analogous to block instances).
To run an SFC instance, both the SFC type and the SFC instance must be
downloaded to the automation system.
To ensure that only one version of an SFC type is used throughout the project, all
SFC types should be stored centrally in the master data library and all adaptations
should be made prior to instantiation.
Control strategies can also be defined SFC types and these can be used in the
sequencers. A control strategy can be set by the operator or by a higher-level
control (for example SIMATIC BATCH).
Note
In the plant view, SFC types cannot be assigned to a hierarchy folder since they
themselves are not relevant for execution.
Central Modifiability
Changes to the topology (step/transition sequence, changed jump target) or
step/transition configurations are made to the SFC type and become effective
automatically in the SFC instances following compilation and download of the AS.
SFC Visualization is updated only after compiling and downloading the OS.
Further information
• Section "How to Create an SFC Type"
Model
Models allow more complex functions than the process tag types (even as complex
as units) to be defined as reusable templates. A model consists of hierarchy folders
with CFC/SFC charts, pictures, reports, and additional documents from which any
number of replicas can be generated using the Import/Export Assistant and then
modified to match the specific, required automation task.
Note
Models can only be created in a multiproject.
The modes are stored centrally in the master data library. All adaptations should be
made before the replicas are generated.
Generating Replicas
The blocks for import/export of parameter descriptions, interconnection
descriptions and messages are prepared in the charts of a model. After linking the
model prepared in this way 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 destination project. The replicas
retain their assignment to the model.
Central Modifiability
If you modify models that already have replicas, a message is displayed since the
import data no longer matches the model data.
With the "Create/Modify Models wizard", you can check the consistency of the
model with the assigned import file and the replicas in terms of modified IEA flags.
Note
In an existing model or in replicas of a model, the names of the blocks must not be
modified. Import/export would otherwise be impossible.
Further information
• Section "How to Create a Model"
• Online help on IEA
Libraries
To provide a better overview, libraries that are no longer used should be hidden
(made invisible) using the menu command.
Further information
• Section "How to Create a Master Data Library".
Note
For more information on the module versions released for PCS 7, refer to the
document PCS 7 - Released Modules (menu command: Start > Simatic >
Documentation > English).
You create a new catalog profile in HW Config and then drag the required
components from the hardware catalog "PCS 7_V6.1" to the new catalog profile.
You can assign any name to the new catalog profile.
Further information
• Section "Defining a Project-Specific Catalog Profile".
Import/Export Interface
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:
• Data from the plant planning can be synchronized with the data of the control
system engineering. This allows control system engineering and class
engineering to be edited at the same time independent of each other.
• Data from the engineering system can be exported as a template, reproduced
in an external program (for example Excel), and then imported back into the
engineering system. This allows the configuration of repeated or similar plant
information to the optimized.
Symbol Table
PCS 7 can translate the symbolic names into the required absolute addresses.
This is only possible, however, when the symbolic names are assigned to the
absolute addresses. This assignment is made in PCS 7 during the hardware
configuration (or when importing a hardware configuration).
Example
You can, for example assign the symbolic name MOTOR_751_ON to the address
Q4.0 in the symbol table and use MOTOR_751_ON as an address in a program
statement.
Further information
• Section "How to Assign Symbols to Input and Output Addresses".
Requirement:
Note
The "Compile OS" function only enters the structure of the plant hierarchy in the
Picture Tree Manager if you activated the option "Base picture hierarchy on the
plant hierarchy" in the general settings for the PH in the SIMATIC Manager.
You then deactivate this option again after you have made changes to the picture
hierarchy in the Picture Tree Manager that you do not want to be overwritten when
you compile the OS again.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
• Online help Help on PH, IEA and PO
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
• Section "How to Import/Export I/Os and Messages"
Message Classes
Messages can be divided into the following classes:
Origin of a Message
Depending on the configuration, messages can originate at various locations within
PCS 7. The origin of the message influences the time stamp of the message.
The following diagram shows an example with the ET 200M distributed I/O station.
SIMATIC S7 400
2. Origin of the message
in the automation system
PROFIBUS DP
Where they Where the message is Where the time stamp is Messages
originate configured added
Operator station In the "Alarm Logging" On the operator station Control system messages
(OS) editor of the WinCC of the OS, attachment of
Explorer non-S7 systems
Automation In the block types in the In the automation Process and process
system (AS) project library or in the system control messages of the
block instances within the SIMATIC stations
CFC charts
Distributed I/O In the block instances of In the ET 200M by the IM Selected events for initial
(ET 200M) the "IM_DRV" driver block 153-2 (with activated value acquisition when a
in the CFC charts 10 ms time stamps) plant fails
(10 ms accuracy)
"Loop-in-alarm" Function
Process and control system messages from technological blocks that are
visualized on the OS include the "loop-in-alarm" function. This function allows
direct selection of the faceplate for this process tag from within the message list.
Further information
Configuring messages is described in detail in step-by-step instructions in the
Configuration Manual Process Control System PCS 7; Operator Station. The
following section provides you with a brief overview of the features provided by
PCS 7 for configuration of a user-friendly message system.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
• Section "Message Configuration in SFC"
Acknowledgment Concept
PCS 7 uses a central acknowledgment concept. If a message is acknowledged on
an OS, the signaling block on the AS is informed of the acknowledgment. From
here, it is passed on to all relevant operator stations as an acknowledged
message.
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 with which the message was generated.
This could lead to false conclusions being drawn.
Further information
• Section "How to Activate Acknowledgment-Triggered Reporting (ATR)"
10 ms Time Stamps
Reading in events with high timing accuracy is often necessary during initial value
acquisition following failure of a unit with the flurry of messages this causes: From
the large number of messages, it must be possible to regulars the message that
led to failure of the unit (initial value).
10 ms time stamps allow extremely accurate time stamping of an incoming event: If
two sensors of two stations on different PROFIBUS-DP chains connected to
different automation systems are activated at the same time, the time stamps of
these signal changes must not differ by more than a maximum of 10 ms. This
assumes time-of-day synchronization of all the devices connected to the plant bus.
Further information
• Section "How to Configure the Hardware for 10 ms Time Stamps"
• Function Manual Process Control System PCS 7 10 ms Time Stamps
Further Information
• For more detailed information on the function and installation of signal
modules, refer to the manual Process Control System PCS 7; WinCC Basic
Process Control
• For more detailed information on configuring the acoustic signaling device,
refer to the Configuration Manual Process Control System PCS 7 Operator
Station
The SIMATIC Manager is the central starting point for all engineering tasks. Here,
the PCS 7 project is managed, archived and documented. Starting from the
SIMATIC Manager, you have access to all the applications of the engineering
system. If there is a connection between ES, OS, BATCH, and AS, the
configuration data can be transferred from the SIMATIC Manager to the target
systems. Testing in online mode is done on the ES (see section "Testing" and refer
to the Configuration Manual Process Control System PCS 7 Operator Station).
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
hardware components and start the hardware configuration of the automation
systems, bus components, process I/O, and PC stations.
Plant View In the plant view, you can structure and display a project according to technological
aspects; in other words, you structure automation and operator control and
monitoring functions hierarchically. The structures for the PCS 7 OS in process
mode are derived from this plant hierarchy (for example OS areas, pitch hierarchy).
Process Object View The process object view provides a universal view of the process tags. It shows 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. Project-wide means that the data
of all projects in a multiproject is acquired.
Multiproject
First project of the multiproject (open)
SIMATIC 400 station
CPU
S7 program
Source files of the S7 program
Blocks (FBs, FCs, OBs, DBs)
Charts (CFC charts, SFC charts, SFC types)
CP interface to the plant bus
Multiproject
First project of the multiproject (open)
Process cell
First unit
Technological function with CFC/SFC charts (closed.)
Object-Oriented Working
The various object types are linked directly to the application required to edit them
in the SIMATIC Manager, in other words, when you open the object the
corresponding application is also started.
Multiproject Engineering
In the component view, you work with all the functions such as archiving,
dearchiving, copying, deleting, pasting etc the projects of the multiproject.
In the component view:
• You split up the multiproject technologically for distributed editing
• You merge the projects back into the multiproject following editing
• You 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 station for the engineering station (ES), operator stations (OS)
and BATCH stations (BATCH)
When you double-click on "Hardware" with a station selected, you change to the
HW Config application where you can add and assign parameters for further
hardware components (for example CP, ET 200M) or other software applications
(server or client) in the stations. This step in configuration is known as hardware
configuration.
Note
Once 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 the
from the master data library to the chart folder's of the AS in which they are used.
Only then are they are available in the catalog for CFC/SFC configuration.
OS Configuration
Starting the component view, you begin configuration of the operator station for
process mode. Selecting the "Open Object" context-sensitive menu command with
the OS selected, starts the WinCC-Explorer (see Configuration Manual Process
Control System PCS 7; Operator Station).
Offline or Online?
You can switch over the component view between:
Component view > offline This view of the project structure visualizes the project data on the
engineering station. This is the default view 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. The
automation, operator control and monitoring functions are arranged hierarchically
(plant, unit, functions, ...). You name the hierarchy folders according to their
technological significance. You 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 Word, Excel, ...)
The resulting project structure is the plant hierarchy.
Further Aspects
• The technological objects (plants (process cells), units, functions (phases), ...)
can be handled as a single entity (for example copied).
• The technological objects can be manipulated without any concrete hardware
assignment.
• You can derive the OS areas and the pitch hierarchy for the PCS 7 OS from
the plant hierarchy.
• The plant hierarchy is the basis for plant-oriented identification of process
objects. The hierarchy path forms the plant designation (higher level
designation HID) with which you can 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
For each hierarchy folder, an assignment to an OS and to an AS must be made in
the plant hierarchy. 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 hierarchy are stored in the folder of
the assigned OS.
You use the process object view when you require details of process tags and CFC
charts and want to edit their attributes and aspects. Working with the process
object view is ideal when you want to assign to say parameters, comments or
interconnections for large volumes of objects.
Advantages
Compared with the plant view, the advantage of the process object is that all
modifiable attributes of an object can be edited. All editable aspects are consistent
and presented in a practical form for the user.
Jumps to CFC, SFC, HW Config, WinCC Explorer allow editing of aspects that
cannot be edited directly in the process object view (such as module parameter
assignments, picture contents).
The context-sensitive menu of the process object view provides functions such as
"Undo" and "Redo" with which you can undo or restore changes.
Structure
On the left-hand side, the process object view displays the plant hierarchy (tree
structure). On the right-hand side, you see a table of the underlying objects along
with their attributes (contents window).
The tree structure displays the same objects as in the plant view. In the tree
structure, the process object view also shows the CFCs, SFCs, pictures, reports
and additional documents.
Tab Purpose
General Here, you see all the underlying process objects (process tags, CFCs, SFCs,
reports, or additional documents) for the plant section currently selected in the tree
structure along with general information on the objects.
Parameters Here, you see all the flagged I/Os 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 flagged I/Os 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.
Measured Value Here, you see all the archive links that exist in WinCC for the process tags and
Archives CFCs displayed in the "General" tab.
Object Purpose
Hierarchy Folder Expansion of the plant hierarchy by adding objects such as plant, unit, function etc.
within a project.
CFC/SFC Creation of empty CFCs and SFCs that can then be further edited with the
appropriate editors.
Additional Creation of empty or import of existing additional documents, for example Excel or
Document Word if the relevant application is installed.
Picture Creation of empty pictures that can then be further edited with the Graphics
Designer.
Report Creation of empty reports that can then be further edited with the page layout
editor.
Process Tag (from Insertion of process tags from the catalog of process tags 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.
Offline or Online?
You can switch over the process object view between:
Process object view > offline This view visualizes the project data on the engineering station. This is
the default view when you create a new project. In the offline view, the
entire data is displayed on the engineering station.
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).
Further information
• Online help Help on PH, IEA and PO
• Section "Editing Mass Data in the Process Object View"
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.
With NetPro you can do the following:
• Create a graphic view of your network
• Specify the properties and parameters for each subnet
• Specify the node properties for each networked module
• Configure connections (also cross-project connections)
• Document the network configuration
• Download the network configuration and hardware configuration to the target
system
SCL Programming blocks
SCL (Structured Control Language) is high-level programming language for
programmable controllers. It includes not only high-level language elements but
also typical elements of a PLC such as inputs, outputs, timers, the memory, block
calls etc. as language elements. In other words, SCL supplements and expands the
STEP 7 programming software with its programming languages LAD, FBD and
STL.
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.
Graphics Designer Editing of process pictures
In the Graphics Designer, you ended the process pictures that are displayed for the
operator on the operator station and that are used for controlling the process. When
you are creating process pictures, PCS 7 provides you with a function that allows
you to insert all the block icons (clear, graphic representations of a process tag)
automatically in the process picture.
You can also insert other graphic objects and define the dynamic attributes of the
objects. A simple example: You can visualize the current state of a valve so that the
operator sees immediately whether the valve is open or closed.
Application Purpose
Tag Logging Archiving process values
The "Tag Logging" editor is an important tool for archiving measured values. In Tag
Logging, you can create various different archives and assign the process values
you want to save to these archives. This allows you to define archiving strategies
tailored to the needs of your plant.
Alarm Logging Archiving messages and alarms
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.
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.
@PCS 7 Connection to the works management level
In a production process, new data of relevance to the works and enterprise
management levels is constantly being produced. You can access this data using
the @PCS 7 software package. This package allows you to use the data from the
higher control levels and create your own statistical information and evaluations.
SIMATIC BATCH Automating batch processes
With the SIMATIC BATCH software package, you can configure process cells with
recipe-oriented control strategies with exacting requirements. This allows complex
tasks with changing control sequences to be handled simply and flexibly.
SIMATC 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.
S7 H Systems This supports you when configuring 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 Library The PCS 7 libraries include blocks and functions for use in PCS 7 plants.
Hardware Catalog The hardware catalog "PCS7_V6.1" contains all approved devices and modules (in
each case, the latest version).
DOCPRO Using DOCPRO, you can create and manage plant documentation.
SFC visualization SFC Visualization of the operating system allows sequential control systems
configured with the SFC tool to be represented and operated in the same way as
on the engineering system. This does not involve any extra configuration effort.
Overview
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.
Procedure Described
Creating the configuration as described in the following sections is structured
according to this procedure. To be able to work through all the topics, we assume
that the PCS 7 project was created during multiproject engineering; in other words,
the PCS 7 project is divided into several projects, these projects are distributed for
editing and merged back into the multiproject to allow cross-project functions to be
implemented.
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.
Further information
• Manual Process Control System PCS 7; PC Configuration and Authorization
This overview shows you the individual steps for creating and setting up a PCS 7
project:
What? Where?
Setting the Defaults for the PCS 7 Project SIMATIC Manager
Creating a New Multiproject with the PCS 7 Wizard PCS 7 Wizard (in the SIMATIC
Manager)
Expanding the Multiproject by Adding Further Projects SIMATIC Manager
Expanding a Project of the Multiproject by Adding Further SIMATIC Manager
Components
Note
Some settings, for example changing language, require the program to be
restarted.
You make all other settings when you first create the PCS 7 project with the PCS 7
"New Project" wizard. You can change these settings later in the "Settings" dialog
box.
Further information
• Online help for the "Settings" dialog box
Procedure
To create a multiproject with the wizard, follow the steps outlined below:
1. In the SIMATIC Manager, select the menu command File > "New Project"
Wizard.
2. Select the option "Multiproject with project and master data library" and confirm
with "Next".
You can check the structure of the multiproject using the "Preview" button.
3. Select the required CPU and confirm with "Next".
4. In the next two dialogs, specify the configuration you require (CFC/SFC chart;
PCS 7 OS) and confirm with "Next".
5. Enter the name of the multiproject in "Directory Name".
6. Start to create the multiproject with the "Finish" button.
7. In the "Message Number Assignment Selection" dialog box, set the message
concept to "Always assign unique message numbers project-wide".
8. Confirm the dialog box with "OK".
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. A master data library with the following content is also created:
• In the Component view: one S7 program with the folders for sources, blocks
and charts
• In the plant hierarchy: one folder for process tag types and one for models
Note
If you want to create a single project with the PCS 7 Wizard, activate the "Single
Project" option. The remaining steps are the same for both types and is explained
below based on the example of a multiproject.
You also use this option if you want to create a further project for your multiproject
and want support from the wizard. After creating the project, assign it to the
multiproject (File > Multiproject > Insert into Multiproject).
To create a new (empty) project in your multiproject, follow the steps outlined
below:
1. Select the required multiproject in the SIMATIC Manager
2. Select the menu command File > Multiproject > Generate in Multiproject.
3. Enter a name and specify where it will be stored.
4. Confirm the dialog box with OK.
Result:
A new empty project is created in the multiproject and can be configured
(HW Config, plant hierarchy etc.).
Further information
When working in multiproject engineering, read the information in the section
"Configuring in a Multiproject" on the rules for distributing the automation systems,
operator stations and BATCH stations in the individual projects of the multiproject.
Procedure
To include a project in the multiproject, follow the steps outlined below:
1. Open an existing multiproject.
2. Select File > Multiproject > Insert into Multiproject in the SIMATIC Manager.
3. Select the project you want to insert.
4. Confirm the dialog box with OK.
Note
If these projects originate from an earlier PCS 7 version, keep to the procedure
described in the manuals Process Control System PCS 7; SW Update ....
Procedure
If you want to remove an unnecessary project from the multiproject, follow the
steps outlined below:
1. Select the project you want to take out of the multiproject.
2. Select File > Multiproject > Remove From Multiproject in the SIMATIC
Manager.
Result: The project is no longer part of the multiproject. It is, however, not deleted;
only the assignment to the multiproject is canceled. If you want to delete the
project, you can do this with the menu command File > Delete > User Projects.
The PCS 7 "New Project" Wizard is used to create the basic configuration that you
can then expand by adding further objects.
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" menu.
Result: All 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 in the menu and specify the object name.
Further information
• Online help on the SIMATIC Manager
Procedure
1. Select the project in the component view of the SIMATIC Manager.
2. Select the Insert > Shared declarations > Shared declarations menu
command.
Result: The "shared declarations" folder with the "Enumerations" and "Units"
subfolder is created.
3. If you want to declare an enumeration, select the "Enumerations" folder and
then the Insert > Shared declarations > Enumeration menu command
followed by the Insert > Shared declarations > Value menu command.
4. If you want to declare a unit, select the "Units" folder and then the Insert >
Shared declarations > Unit menu command.
Further information
• Online help on the SIMATIC Manager
Note
If you require distributed editing of the projects of the multiproject, read the
information in the section "Configuring in a Multiproject" on the distribution of
automation systems, operator stations and BATCH stations to the individual
projects of the multiproject.
7.4.1 How to Insert the SIMATIC 400 Stations in the Projects of the
Multiproject
Once you have created the multiproject with the PCS 7 Wizard, as default, there is
already one automation system inserted. Insert any further automation systems
you require manually.
Procedure
1. Select the project into which 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
Result: 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 further SIMATIC stations.
Further information
• Online help on the SIMATIC Manager
• Section "How to Create a SIMATIC Station"
This section describes how to start the basic configuration of the automation
systems. We assume the following for a multiproject
• that the automation systems will be created in the individual projects and that
the communications processors for network attachment will be configured on
the central engineering station. This is described below.
• that the full hardware configuration with attached I/O will be completed on the
distributed engineering stations after distributing projects for editing. The full
hardware configuration is described in the section "Configuring the Hardware".
Procedure
To start the basic configuration of the automation systems, follow the steps outlined
below:
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on the "Hardware" object (right-hand pane).
Result: Hardware configuration of the automation systems opens.
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 insert 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. Confirm the open dialog box "Properties - PROFIBUS Interface DP" with "OK".
6. Continue in the same way to add any other components you require.
7. Select the menu command Station > Save and Compile in HW Config.
Further information
• Section "Configuring the Hardware"
7.4.3 How to Insert CPs in the SIMATIC Stations and Assign Them to
Networks
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 perform this
configuration work on the central engineering station for all projects. This ensures,
for example, that node addresses are unique on the bus.
Procedure
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on the "Hardware" object in the detailed view.
Result: Hardware configuration of the automation systems opens.
2. If the hardware catalog is not visible, select the menu command View >
Catalog.
3. In the hardware catalog SIMATIC 400 > CP-400, select the CP you require for
the network being used (CP 443-1 or CP 443-5Ext) and insert it by dragging
with the mouse.
Result: Once you have inserted the CP, the "Properties – Interface" dialog box
opens.
4. Set the required address on the bus for the CP you have selected.
5. Select the subnet in the "Subnet" group:
- If you have not yet set up a subnet, click on the "New" button and define
new network.
- If you have already set up a subnet, select the required network in the
"Subnet" group.
6. Exit the properties dialog by confirming your entries with "OK"
7. Select the menu command Station > Save and Compile.
Further information
• Section "Configuring the Hardware"
Procedure
1. Select the project into which you want to insert the operator station in the
component view of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC PC Station.
Result: 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 PC station in the component view and open HW Config by
double-clicking on the "Configuration" object in the detailed view.
Result: The hardware configuration of the SIMATIC PC station opens.
5. If the hardware catalog is not visible, select the menu command View >
Catalog.
The hardware catalog opens.
6. Under SIMATIC PC Station > HMI ... in the hardware catalog, select the
required WinCC application and drag it into the configuration table:
- WinCC application (for example for OS server or single station)
- WinCC application (stby) (for redundant OS server)
- WinCC application client (for OS client)
- WinCC application CAS (for central archive server)
7. In the hardware catalog SIMATIC PC Station > CP Industrial Ethernet, select
the communications processor installed in the SIMATIC PC station and drag it
with the mouse to the PC station.
If you are using a standard network adapter, select the processor IE General.
Result: The "Properties - Ethernet Interface" dialog box opens.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
• Manual Process Control System PCS 7; PC Configuration and Authorization
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 must insert any further
BATCH stations you require manually.
Warning
! Configuring applications (WinCC, SIMATIC BATCH, ...) on separate "SIMATIC PC
station" objects and then merging them to create one PC station by assigning the
same computer name to the "SIMATIC PC station" objects is not permitted!
Requirement
The SIMATIC BATCH optional 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.
Result: A new SIMATIC PC station is inserted in the selected project.
3. Set the computer name of the SIMATIC PC station:
- Select the SIMATIC PC station.
- Select the menu command Edit > Object Properties.
- Enter the computer name in the last field.
4. Select the SIMATIC PC station in the component view and open HW Config by
double-clicking on the "Configuration" object in the detailed view.
Result: The hardware configuration of the SIMATIC PC station opens.
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 BATCH application and drag it into the configuration table:
- BATCH application for BATCH server
- BATCH application client for BATCH client
- BATCH application (stby) for redundant BATCH server
7. In the hardware catalog SIMATIC PC Station > CP Industrial Ethernet, select
the communications processor installed in the SIMATIC PC station and drag it
with the mouse to the PC station.
If you are using a standard network adapter, select the processor IE General.
Result: The "Properties - Ethernet Interface" dialog box opens.
Further information
• Manual Process Control System PCS 7; SIMATIC BATCH
• Manual Process Control System PCS 7; PC Configuration and Authorization
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.
Result: 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 PC station in the component view and open HW Config by
double-clicking on the "Configuration" object in the detailed view.
Result: The hardware configuration of the SIMATIC PC station opens.
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
WinCC application and drag it into the configuration table.
7. In the hardware catalog SIMATIC PC Station > CP Industrial Ethernet, select
the communications processor installed in the SIMATIC PC station and drag it
with the mouse to the PC station.
If you are using a standard network adapter, select the processor IE General.
Result: The "Properties - Ethernet Interface" dialog box opens.
Further information
• Manual Process Control System PCS 7; PC Configuration and Authorization
• Section "Setting up PC Stations"
As of PCS 7 V6.1 SP1, the project-specific network settings for the communication
adapters (Ethernet) of the engineering station are downloaded direct to the PC
station (remote).
Requirements
• The following is installed on each PC station:
- Operating system
- Specific software for the PC station (for example, PCS 7 Engineering, OS
Server)
• All PC stations to be downloaded are connected to the engineering station via
at least one network.
• The operating system network is set up.
• The network addresses of the PC stations are set.
• The protocol for the communication is set to TCP/IP.
• The following is settings have been made on each PC station:
- The communication adapter for communication between the PC station
and the terminal bus has been selected.
- The network addresses for the plant bus are set.
- The access point of the PC station has been set to: "S7ONLINE: = PC
internal (local)".
• The PCS 7 project has been created.
Note
Perform the following steps for the engineering station before continuing the
configuration and download for additional PC stations.
Note
If the selected PC station is not shown, this indicates a network problem or an error
in the project configuration.
Caution
The TCP/IP and ISO protocols cannot be disabled since they are both needed for
the configured operation!
If the protocol of a bus in a plant needs to be switched (from TCP to ISO, for
example), you need to briefly set a mixed protocol (TCP and ISO) on the
engineering station. The configuration data can then be downloaded to the AS and
the HMI systems.
Further information
• Documentation SIMATIC Net; Commissioning PC Stations - Instructions and
Quick Start
Described below
We assume the following for a multiproject
• that the plant hierarchy is created on the central engineering station and, if
necessary, is filled with additional documents. This is described below.
• that the CFC/SFC charts or OS pictures/OS reports created on the distributed
engineering stations are assigned to the hierarchy folders.
• Master data library (in the example: s7_Pro4_Lib) with the folders for models
and process tag types.
- In the component view, and S7 program with the folders for
Source files
Blocks
Charts
- In the plant view, the folders for
Process tag types
Models
Preview
The following sections describe the following:
• Which settings you need to make for the plant hierarchy.
• How to expand the units and technological functions to the plant hierarchy
according to the technological aspects of your plant.
• Which rules apply when creating the plant hierarchy.
If you create a multiproject with the PCS 7 assistant, certain defaults or parameter
settings are made in the dialogs (for example the number of hierarchy levels,
assignment to AS etc.). You can change the 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 You can select the maximum number of possible hierarchy levels in the
levels: project. A maximum of eight levels of hierarchy folders is possible. 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. When you later compiled the OS, this
Hierarchy picture hierarchy is transferred to the Picture Tree Manager.
Derive diagnostics With this option, the diagnostics screens are generated in the plant hierarchy
screens from the plant for the maintenance station.
hierarchy You can only select this option when the option "Derive picture hierarchy from
the plant hierarchy" is set.
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)
Setting Description
Included in HID You can select the levels whose 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 further "drawers" (for
example for additional documents, such as plant descriptions, process tag
sheets,...).
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 tags on the
OS (measuring point).
Note: When assigning names, remember that when you compile the OS, the
tag name must not be longer than 128 characters. This name is made up of
the name of the folder in the hierarchy path, the chart name, the block name,
the separator and the 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
separate 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...".
Result: 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 have the function of 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.
4. Make the following settings for the plant hierarchy for the project.
(Refer to the section "Settings and Properties of the Plant Hierarchy").
5. Confirm your settings in the dialog box with "OK".
Further Information
• Configuration Manual Process Control System PCS 7; Operator Station.
Note
The characters [ ‘ ] [ . ] [ % ] [ \ ] [ * ] [ ? ] [ : ] [ blank ] 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.
With the wizard, you can create a maximum of 8 hierarchy levels without further
nesting of hierarchy folders. You can further extend this structure created by the
wizard by adding further hierarchy folders and/or technological objects.
Hierarchy Folder
The hierarchy folder is used to structure the plant in a hierarchy. It can contain
further hierarchy folders and objects such as CFC charts, SFC charts, process
pictures, reports or additional documents (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 use these are
formed the HID).
Procedure
1. Open the plant hierarchy in the SIMATIC Manager with the menu command
View > Plant View.
2. Select a hierarchy folder below which you want to insert a further hierarchy
folder.
3. Select the menu command Insert > Technological Object > Hierarchy Folder.
4. Enter the technological name of the hierarchy folder.
The technological objects CFC charts, SFC charts, OS pictures, and OS reports
can be inserted in the plant hierarchy both in the plant view and in the process
object view. The methods for inserting objects are practically identical. Below, we
describe how to insert the objects in the plant view.
Procedure
1. Open the plant hierarchy in the SIMATIC Manager with the menu command
View > Plant View.
2. Select the hierarchy folder below which you want to insert the object.
3. Select the menu command Insert > Technological Object > "<required object>".
Note
You can also create a new additional document here by selecting the type in the
"Registered Applications" box, entering the name and confirming with "OK". Result:
The additional document is created in the PH. You can then open it and edit it by
double-clicking on it.
Further information
• Section "Relationships between the Views"
• Section "Cross-View Functions and How to Use Them"
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 CPU" drop-down list box, select the S7 program 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 the lower-level objects" check box.
Note
The "Pass on selected assignment to lower-level objects" option is only active
when the lower-level objects have a different or no assignment.
5. From the "Assigned OS" drop-down list box, 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 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.
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.
Further information
• Online help on the PH, IEA and PO
• Online help for the "PLC-OS Assignment" tab
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 always create the charts and pictures in the plant view or the
process object view, these assignments are made automatically.
Requirement
The hierarchy folder must have the same PLC or OS assignment as the assigned
object. If the destination hierarchy folder has a different PLC/OS assignment, the
assigned object is also moved to this PLC/OS in the component view.
Procedure
1. Select the required object in the component view.
2. Holding down the Shift key (move), drag the object to the required hierarchy
folder of the PH.
If you have created pictures/reports directly in the OS and want to make these
objects known in the plant hierarchy later, follow the steps outlined below:
1. Select the OS in the component view of your project.
2. Select the menu command Options > Import WinCC Objects.
3. Select the required object in the component view.
4. Holding down the Shift key, drag the object from the component view to the
required hierarchy folder of the PH.
Caution
The process variables referenced in the C scripts in WinCC must be defined in the
"#define section".
With the menu command Options > Plant Hierarchy > Consistency Check, you
can check whether the configured data is consistent with the settings made in the
project or multiproject.
Consistency tests
• The names, number of objects and uniqueness of hierarchy folders, CFC
charts, SFC charts, pictures, reports and settings for the OS area are
automatically checked.
• The results are displayed in the individual tab dialogs.
• Information about the test results in the tabs is available by pressing the "Help"
button.
Note
If a multiproject is selected, the following checks are also made:
• Check for unique names of S7 programs. Check whether the names of CFC
charts and SFC charts are unique in the entire multiproject.
• Check that only one object for each type (S7 program, OS) is available in the
master data library.
• Check for differing PH / settings
• If project or hierarchy folder is selected, the checks relate solely to the project.
Procedure
1. Select the multiproject or a project in the plant hierarchy.
2. Select the Options > Plant Hierarchy > Check Consistency menu
command.
Result: the "Check Consistency - Log" dialog box opens displaying errors.
3. Eliminate the errors and run the consistency check again.
Test 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.
Further information
For further information on the log, refer to the online help.
Further information
• Online help on the PH, IEA and PO
Introduction
In the PH, it is possible to assign attributes to the hierarchy folder in compliance
with the S88.01 standard. This "S88 Type Definition" is required, for example, for
BATCH process cells and applications at the business management level (MES).
Using the object properties, you can change the object type of the highest
hierarchy folder from "neutral" to "Process Cell".
Procedure
1. Select the object whose settings you want to change in the PH.
2. Select the menu command Edit > Object Properties and then the "S88 Type
Definition" tab.
3. Change the object type from <neutral> to process cell and confirm with "OK"
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 (S88
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.
Further information
• Online help on the PH, IEA and PO
Overview
It is helpful during configuration, if all objects (blocks, charts, source files, process
tag types, models, SFC types etc.) 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 in which you use blocks from the
PCS 7 library after a change of version of the PCS 7 library.
To synchronize block types, you can use the function "Update Block Types", refer
to the section "How to Update Block Types".
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 SIMATIC Manager
Copying Objects to the Master Data Library SIMATIC Manager
Adapting Blocks to the Project Requirements SIMATIC Manager (component view)
Creating Process Tag Types SIMATIC Manager (plant view)
Creating Models SIMATIC Manager (plant view)
Testing the Library Objects CFC or SFC Editor
Documenting the Library Objects In the relevant editors
Hiding Libraries SIMATIC Manager
Component View
You copy all the block types (technological blocks, driver blocks, communication
blocks etc.) required in the multiproject to the block folder of the master data library
in the component view. This may be a collection from PCS 7 libraries, libraries of
suppliers, or blocks you have written yourself.
The blocks from the PCS 7 libraries are suitable for most situations encountered
during configuration and can usually be used unchanged. If blocks need to be
adapted for special requirements, make the adaptations early; in other words,
before the blocks are used in the projects.
SFC types are stored in the chart folder of the master data library. Note: SFC types
can also be part of process tag types or models.
• Models
A model consists of hierarchy folders with CFC/SFC charts, pictures, reports,
and additional documents from which any number of replicas can be created
using the IEA.
The hierarchy folders of the library are handled differently from the hierarchy
folders of the project. This means:
• When it is copied or moved, the hierarchy folder loses its identifier if the target
is not a master data library, or the same hierarchy folder already exists in the
target.
If a hierarchy folder loses its identifier, its symbol changes to that of a normal
hierarchy folder.
• You cannot insert any new hierarchy folders with this identifier explicitly in the
master data library. They are, however, created automatically in the master
data library when you create models or process tag types and the
corresponding folder no longer exists.
• Hierarchy folders that lose their identifier do not regain it when they are
returned to the master data library.
Further information
• Online help on the PH, IEA and PO
Note
Only one library can be defined in the multiproject as the master data library. The
master data library can only contain one S7 program.
Procedure
To create a new library as the master data library in your multiproject, follow the
steps outlined below:
Requirement: No library must be defined in the multiproject as a master data
library. If necessary, you may need to cancel the definition of an existing master
data library (see Step 2).
1. In the SIMATIC Manager, select the menu command File > New > Libraries
and enter a library name (ideally the multiproject name) and, where necessary,
the path to the storage location.
Result: The library is created and opened.
2. Select the library in the multiproject in the component view and Select the
menu command File > Multiproject > Define as Master Data Library.
Result: The library is defined as master data library.
3. Select the library and then the menu command Insert > Program > S7
Program.
Result: An S7 program along with a block and source file folder is created.
4. Add a chart folder below the S7 program with 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 created explicitly in the plant hierarchy. These are
created automatically when you create models process tag types.
Note
The SIMATIC Manager permits names longer than 8 characters. The name of the
library directory is, however, restricted to 8 characters. Library names must
therefore differ from each other in the first 8 characters. The names are not case-
sensitive.
Remember that the name of the file is always the same as the original name of the
library when created because changes to names are not synchronized at the file
level in the SIMATIC Manager.
This section explains the most important functions when handling libraries. You
should know these functions, for example, when you want to include objects from
libraries in the master data library.
Library Functions
In the SIMATIC Manager, you can use the following functions with libraries:
• Open a library with the menu command File > Open > "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 > Libraries.
• You can delete parts of libraries such as charts, blocks, source files with the
menu command Edit > Delete.
• You can hide unused libraries and show them again: With the menu command
File > Manage > Libraries and then by selecting the library and the "Hide"
button to hide them. The library can be made visible again with the "Display"
button.
Note
Since the master data library contains all the objects to be used in the project, you
should hide all the libraries except for the master data library.
Note
The SIMATIC Manager permits names longer than 8 characters. The name of the
library directory is, however, restricted to 8 characters. Library names must
therefore differ from each other in the first 8 characters. The names are not case-
sensitive.
Remember that the name of the file is always the same as the original name of the
library when created because changes to names are not synchronized at the file
level in the SIMATIC Manager.
7.6.5 How to Copy Objects from other Libraries to the Master Data
Library
The following section describes how to enter objects from the supplied PCS 7
library (PCS 7 Library) or from libraries from other suppliers in the master data
library.
Procedure
If you want to copy part of a library, for example software, blocks, pictures etc,
follow the steps outlined below:
1. In the SIMATIC Manager, select the menu command File -> Open and change
to the "Libraries" tab.
2. Select the required library and confirm with "OK".
Result: The library is opened.
3. Select the part of the library you want to copy in the open library (source).
Select the menu command Edit > Copy (for example process tag types,
blocks).
4. Select the folder in the master data library (destination) in which you want to
store the copied part of the library.
5. Select the menu command Edit > Paste.
Result: The copied library is stored in the master data library.
Notes on Copying
• If you want to copy the supplied process tag types from the PCS 7 Library to
your master data library, select the required process tag type in the
"Templates" folder, copy it and then paste it into the "Charts" folder of your
master data library.
• If you copy blocks from different libraries, it is possible that blocks could have
different names (and functions) but the same block numbers. In this case, a
dialog opens in which you can rename the block or synchronize the attributes.
• Renaming (rewiring) works only when copying to offline.
• The symbolic name is copied when you copy the blocks from a library. If you
do not copy from a library, but from an S7 program, the symbolic name is lost
and must be entered later in the symbol table.
Note
Remember that the CPU changes to STOP if FCs are missing.
• Remember that the block numbers of the blocks it calls are entered in the code
of the multiple instance block. If you change these numbers and the numbers
in the code, it is possible to rewire in the SIMATIC Manager (Options >
Rewire...). Exception: with protected blocks.
Procedure
1. Select one or more blocks in the block folder of the master data library.
2. Select the menu command Options > Charts > Update Block Types.
Result: the "Update Block Types" dialog box opens.
3. Select the S7 programs to be checked for differences compared with the block
types selected in the master data library.
4. Complete the dialog with "Next".
Result: All selected S7 programs are checked and a further dialog opens in
which you can select the block types. Here, you can also see information on
the consequences.
5. Specify the block types to be updated for the specific programs: All the block
types to be updated are selected. Where necessary, you can deselect those
you do not want updating.
If there are no block types to be updated (none displayed), close the dialog.
6. Complete the dialog with "Next".
Result: The block types are updated in the selected S7 programs and a log is
displayed.
Further information
• Context-sensitive online help for the two dialogs above
What? Where?
How to Modify Attributes of the Block I/Os LAD/CSF/STL Editor
Locking Message Attributes Against PCS 7 message configuration
Changes in Block Instances
Translating Message Texts SIMATIC Manager
Setting the Language for Display Devices SIMATIC Manager
Exporting/Importing Operator and Display SIMATIC Manager
Texts
Note
Blocks must only be adapted to project requirements in the library. In the following
sections, it is assumed that this is the master data library.
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.
Result: The LAD/STL/FBD editor is started (you receive a message if the block
is protected). If you select an object in the tree structure of the interface, its
content is displayed.
3. In the right-hand pane, select the required I/O and select the menu command
Edit > Object Properties.
Result: The properties dialog opens.
4. Select the "Attributes" tab
Result: The attributes are displayed in table form.
5. Here, you can modify or enter the attributes and their values.
By clicking in the "Attribute" column, you open a drop-down list box displaying
the possible attributes for this I/O.
You can modify attributes without any great difficulty, since there is a syntax check
when you enter attributes and you will be informed of errors or missing information.
Note
You will find information on using attributes and a description of the attributes in
the online help on the LAD/STL/FBD editor.
Procedure
1. Select the block to be modified in the block folder of the master data library.
2. Select the Special Object Properties > Message... context menu command.
Result: Message configuration is opened. This displays all the messages
configured for this block.
3. By putting a check mark in the column, you can interlock the text you
entered in the column before it.
4. Confirm your settings with "OK".
Note
If block instances already exist, the modification can be passed on to the instances
by repeating the block import.
Further information
For more detailed information on adapting operator and message texts, refer to the
Configuration Manual Process Control System PCS 7; Operator Station.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station.
Procedure
1. In the SIMATIC Manager, select the Options > Language for Display
Devices... menu command.
2. Set the language for the PCS 7 blocks, for example "English (USA)".
3. Select the language you want to define as default in the "Installed Language in
Project" box and click the "Standard" button.
4. Complete the dialog with "OK".
For your project, you can select several languages from the list of available
languages and define one of them as standard.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station.
• Online help on the dialog
7.6.7.6 How to Create your own Blocks for the Master Data Library
You can create PCS 7-compliant AS blocks or faceplates yourself and store them
in the master data library.
You will find information on creating your own blocks in the manual Process
Control System PCS 7; Programming Instructions Blocks.
This also describes how to store your own blocks in a library and how they can be
installed on the target computer with setup for inclusion in the master data library.
Note
In CFC, you can assign the block icons to specific instances in the object
properties of the blocks.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station.
Application
With the option of exporting entire contents of entire tables from the process object
view, you can, for example, assign modified parameter values and interconnections
to a copied unit externally. You can then import the modified data again. This
method can be used as an an alternative to the Import/Export Assistant.
Note
With the measure described above for importing and exporting, you edit the
instances; in other words the option of central modification is lost.
Languages
PCS 7 allows you to store all the operator and display texts in any language. The
only requirement is that the language is already installed in your project:
You can display the available languages in the SIMATIC Manager with the menu
command Options > Language for Display Devices. The number of languages
available is decided when you install Windows (system property).
Further Editing
Note
When editing exported texts, make sure that you do not overwrite any
management information (language IDs or path information).
With the ASCII editor, you edit only lines that begin with "T-ID=".
Caution
Always open the files from within the tool (for example start Excel > File > Open)
and not by double-clicking on the file.
If you edit with a spreadsheet editing tool never edit the first column or the first row
and do not delete any semicolons.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
• Online help on the individual dialog boxes
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:
Functions Purpose
Create/Change • Create process tag types from CFC charts as follows:
Process Tag Type - By selecting I/Os of blocks and charts that will be given descriptions for
parameters and signals.
- By selecting blocks with messages that you want to assign message
texts to.
• By modifying an existing process tag type
• Check existing process tags for discrepancies compared with the process tag
type and synchronize any differences.
Synchronize When a process tag type is modified, the process tags existing in the project are
automatically synchronized.
If actions were taken that caused inconsistencies between the process tag type
and process tags (for example when some process tags of the project were not
available at the time of the automatic synchronization), synchronization can also
be started explicitly.
Assign/create import To generate process tags, an import file must be assigned to the relevant process
file tag type. With the "assign import file to a process tag type" assistant, you can do
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
Functions Purpose
Import 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. The data is then 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.
Export Export of the data of the process tags for a process tag type
The following options are available:
• Select a process tag to export this alone.
• You can select a parent hierarchy folder or the project node to select and
export all underlying process tags.
As the result, a row is created in the relevant export file for each process tag of a
process tag type found.
Further information
• Section "How to Create a Process Tag Type from a CFC Chart"
• Section "How to Modify a Process Tag Type"
• Section "How to Synchronize Process Tags with the Process Tag Type"
• Section "What Happens during Import?"
• Section "What Happens during Export?"
• Online help on the PH, IEA and PO
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:
Functions Purpose
Creating/Modifying You can create models with the Import/Export Assistant as follows:
Models • By selecting I/Os of blocks and charts that will be given descriptions for
parameters and signals and that will then be imported.
• By selecting blocks with messages that you assign message texts to and
then import.
• By assigning the model data to an import file.
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, so that the column structure or the column titles
change, 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, you can also make the modifications in the
replicas.
Import Import of the data of the models
The model is copied from the master data library to the specified target projects
as a replica. The data is then 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.
Export Export of the data of the replicas for a model
The following options are available:
• Select a model to export this alone.
• You can select a parent hierarchy folder or the project node to select and
export all underlying replicas.
As the result, a row is created in the relevant export file for each replica of a
model found.
Further information
• Section "How to Create a Model"
• Section "What Happens during Import?"
• Section "What Happens during Export?"
• Online help on the PH, IEA and PO
Objects you stored in the master data library were created with the corresponding
tools (for example CFC Editor). These tools provide functions for compiling,
downloading, and testing.
Unsuccessful completion of the test, the objects are then stored in the master data
library.
Process tags and models are then declared as a process tag type or model
following the test and stored automatically in the master data library.
Requirement
Since the test always takes place on the AS, it must be possible to reach the AS
from the engineering station. If the modes contain pictures, the pictures are tested
on the OS.
Further information
• In the online help of the relevant tools (for example CFC Editor)
Objects you stored in the master data library were created with the corresponding
tools (for example CFC Editor or LAD/STL/FBD editor). These tools have their own
print functions with which you can document these objects (printouts).
Further information
• Online help of the relevant tools (for example CFC Editor)
Further Reading
If you now want to edit the multiproject (including the master data library) prepared
as described above on distributed stations with several editors at the same
time, remember the following.
If you do not want to distribute the multiproject for editing, you can skip the
following sections and continue at 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, 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 requirements must always be met:
• The projects are located in folders that are shared for read and write access.
This means the following:
- The shares for drives on which the multiproject or the projects are located
must be created before setting up the multiproject.
- 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.
- Entire drives must not be shared. Folders must only be shared in 1
hierarchy level.
• PCS 7 must be installed on the computers on which the folders with the
projects are located since PCS 7 provides the necessary database server
functions for access to 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 member assignment, such overlapping does
not occur.
If you want to use cross-project functions in such a constellation, you must also
make sure that the following conditions are met:
• 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.
We recommend that you merge all the projects onto one programming device/PC
and run the cross-project functions locally.
Recommendations
• 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 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. The projects on a distributed engineering station should
each 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 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.
Further information
• Section "Conditions for Further Editing in the Multiproject".
Further information
• Section Requirements for Compiling and Downloading"
• 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 columns "Must/Can" in the following table
indicate which steps must be performed and which can be performed prior to
distribution.
The description of the steps in configuration assumes that this procedure is used.
Requirement
• 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 sections "Distributing the Multiproject for Distributed Editing
(Multiproject Engineering)" and "Conditions for Further Editing in the
Multiproject".
2. In the SIMATIC Manager, select the menu command Options > Customize
and set the storage location of the projects, multiprojects, and libraries. The
DOS naming convention must be adhered to.
Further information
• Online help on 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 ...
Make the following settings:
- Enable the "Insert in multiproject" option.
- Select "Current multiproject" in the drop-down list box.
- Enable the "Replace current project" option.
- Enter the required storage location on the distributed engineering station
(in UNC notation).
3. Confirm the dialog box with 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. It can remain there as a backup or can be
deleted.
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. Select the menu command File > Multiproject > Remove for editing...
Result: The "Select directory" dialog opens.
2. Select a directory and confirm the dialog with "OK".
3. Result: The project is marked as "removed for editing" and grayed out.
When a project has been moved, in contrast to the procedure described above,
you cannot use the "Archive", "Save As", and "Compile OS" functions.
Further information
• Section "How to Move Project Edited on Distributed Stations to the
Central Engineering Station"
Requirement
All the PCS 7 software components required for editing are installed on the
distributed engineering station.
Note
Before the project can be copied back to the central engineering station, the
modifications made in this section must be reversed.
Further information
• Section "How to Move Projects Edited on Distributed Stations to the Central
Engineering Station"
Introduction
You map the structure of your plant at the automation level (AS, OS, BATCH) in
the SIMATIC Manager and in HW Config. You create your SIMATIC 400 station
(when necessary distributed in various projects) and configure the required I/O and
communication hardware.
Depending on your plans structure, you can configure various project types on the
PCS 7 OS. This means that you can configure plants with one or more OS servers
or clients. Generally, you work with a multiple workstation project; in other words
you will create several OS servers and OS clients.
You also have the opportunity of creating redundancy at each level (for example
redundant OS, use of H stations, etc).
Tool Purpose
Commissioning Wizard Configuring the PC station
SIMATIC Manager Insert all the SIMATIC 400 stations in the project.
You insert the engineering station, the operator stations, and the BATCH
stations in the project as PC stations.
HW Config Insert hardware components in the SIMATIC 400 stations.
You insert hardware components and a WinCC application that belong to the
particular PCS 7 OS or BATCH station.
Further Reading
In multiproject engineering, the SIMATIC 400 stations and the PC stations for the
engineering station, operator stations, and BATCH stations may already have been
created in your project. The following section describes how you continue by
adding the hardware components to the SIMATIC 400 stations.
If this is not the case, work through the following sections first before you continue
here:
• Inserting and Configuring the Operator Stations
• Inserting and Configuring the BATCH Stations
• Inserting and Configuring the Engineering Station
Further information
• You are also find information on hardware configuration of the OS stations 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 delete catalog profiles that you do not require with the menu command
Profile > Delete.
Existing catalog profiles with the same name:
If a catalog profile of the same name already exists, a screen prompt is displayed.
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. The symbolic
names of the inputs and outputs can also be exported and imported.
Applications
• Data import from hardware planning tools
• Station configuration using electronic media (for example E-mail)
• An export file can be printed out with word processing systems or can be
edited for documentation purposes.
Further information
• Online help on HW Config
• Section "Import/Export of the Hardware Configuration"
Node Addresses
Node addresses are addresses of programmable modules (PROFIBUS, Industrial
Ethernet addresses). They are required to address the various nodes of a subnet,
for example to download a user program over the plant bus (Industrial Ethernet) to
the CPU. You will find more information on assigning a node addresses on a
subnet in the section on networking stations.
ES / OS AS 4xx-2
MPI
2
Industrial Ethernet
1
PROFIBUS DP (1)
ET 200M ET 200S
CP 443-5 ext.
CP 443-1
PROFIBUS DP (2) CPU 416-2
ET 200M ET 200S ET 200iS
1
0
1) Industrial Ethernet: Max. 100 Mbps; max. 1024 nodes (BCE: max. 100 Mbps;
max. 8 nodes)
2) MPI: MPI is required in PCS 7 only for test and diagnostic purposes
DP master system: Max. 12 Mbps; max. 126 nodes; profile: PROFIBUS DP
Note
For the 10 ms time stamp, PROFIBUS DP must be connected to the SIMATIC 400
station via a CP 443-5 Extended or via the internal DP interface.
What? Where?
Creating a SIMATIC 400 Station SIMATIC Manager
Inserting Modules in a SIMATIC 400 Station HW Config
Inserting a Communications Processor (CP) HW Config
Setting the CPU Properties HW Config
Setting the Process Image HW Config
Configuring Fault-tolerant Systems (H Systems) HW Config
See Manual Process Control System PCS 7; Fault-tolerant
Process Control Systems.
Configuring Fail-safe Systems (F Systems) HW Config
See Manual S7- 400F/S7-400FH Programmable Controllers,
Fail-safe Systems.
Setting Time-of-Day Synchronization HW Config
Configuring the Distributed I/O for Standard HW Config
Configuring the Distributed I/O for Configuration Changes in HW Config
Run (CiR)
Assigning Symbols for Input and Output Addresses HW Config (Symbol Table)
Configuring PA Devices PDM
Configuring the Diagnostic Repeater SIMATIC Manager + HW Config
Configuring Intelligent Field Devices PDM
Configuring HART Devices PDM
Configuring Y-Links and Y-Adapters HW Config
Importing/Exporting the Hardware Configuration HW Config
Configuring 10 ms Time Stamps HW Config
Activating Acknowledgment-triggered Reporting HW Config
Downloading the Configuration to the CPU HW Config
Further information
• Online help on HW Config
Procedure
Before you can start to configure and assign parameters, you require a
SIMATIC 400 station in your project that you insert at the level directly below the
project, where you can then set its properties.
1. Select the project into which you want to insert the automation system in the
component view of the SIMATIC Manager.
2. Select the menu command Insert > Station > SIMATIC 400 Station.
Result: A new SIMATIC 400 station is inserted in the selected project.
3. Follow the same procedure if you want to install further automation systems.
You can adapt the names by selecting the SIMATIC 400 station, right-clicking and
selecting the Object Properties menu command.
Further information
• Section "How to Insert Modules in a SIMATIC 400 Station"
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 lower third of the catalog you can see the order number and a brief
description of the currently selected component. Compare the order number with
the actual physical component. This allows you to check that you have selected the
correct 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_V61" profile is displayed as default when you first start the hardware
configuration. In this profile, you will see the current versions of the modules and
devices released for PCS 7.
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 where you
will find the required module.
You will find a list of released modules in: Start > SIMATIC > Documentation >
English > PCS 7 - Released Modules.
You can create your own personal profile with the modules and devices you
commonly use: see Defining a Project-Specific Catalog Profile.
Procedure
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on "Hardware" (right-hand pane).
Result: HW Config and the hardware catalog are opened.
2. Select SIMATIC 400 > Rack 400 in the hardware catalog and drag and insert
the required rack.
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 insert 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. Confirm the open dialog box "Properties - PROFIBUS Interface DP" with "OK".
6. Continue in the same way to add any other components you require, for
example:
- SM 400: Digital and analog signal modules (central I/O modules)
- CP 400: communication modules: refer to the section "How to Insert a
Communications Processor"
7. Select the menu command Station > Save in HW Config.
Note
If you want to connect PROFIBUS DP to a CP 443-5 Ext., you do not need to set
the properties.
Note that the integrated DP interface does not have the same range of functions as
the CP 443-5 Ext. (for example number of PROFIBUS nodes).
Further information
• Section "How to Configure the Distributed I/O"
• Section "How to Insert a Communications Processor"
Procedure
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on the "Hardware" object (right-hand pane).
Result: Hardware configuration of the automation systems opens.
2. Select SIMATIC 400 > CP-400 > Industrial Ethernet ... in the hardware
catalog and drag and insert the required CP.
Make sure that the arrangement selected here matches the arrangement of the
physical hardware.
3. Result: Once you have inserted the CP, the "Properties – Ethernet Interface
CP 443-1" dialog box opens.
Set the properties as follows:
4. Activate the "Set MAC address" option and assign the required MAC
addresses (for example 08.00.06.01.00.12) or accept the default addresses.
Make sure that the address is unique on the bus.
5. Enter the IP address and subnet mask or deactivate the "IP protocol is being
used" option.
6. Click the "New" button and replace the name "Ethernet(1)" with a name that
will later be more meaningful.
7. Close the properties dialog of the Ethernet interface by clicking "OK" twice.
Note
Over the integrated DP interface or the CP 443-5 Ext., you use the 10 ms time
stamps in conjunction with the IM 153-2 or routing (parameter assignment for the
DP/PA slaves over the ES and the plant bus).
Procedure
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on the "Hardware" object (right-hand pane).
Result: Hardware configuration of the automation systems opens.
2. Select SIMATIC 400 > CP-400 > PROFIBUS ... in the hardware catalog and
drag and insert the required CP in the SIMATIC 400 station.
3. Result: Once you have inserted the CP, the "Properties – PROFIBUS Interface
CP 443-5 EXT" dialog box opens.
Set the properties as follows:
4. Assign the required PROFIBUS address for the
DP master ("Parameters" tab; "Address:" combo box).
Note
The addresses 1 and 126 are default addresses for PROFIBUS slaves. Do not use
these in the project.
5. Create a new network with the New" button and replace "PROFIBUS(1)" with a
name that will later be more meaningful.
6. Change to the "Network Settings" tab and set the transmission rate "1.5 Mbps"
and the "DP" profile.
7. Complete the dialog by clicking "OK" twice.
Further information
• Online help on 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).
Refer to the section "Free Assignment between Hardware and Software"
Note
The assigned symbols are not downloaded when you download to the station
(menu command: PLC > Download to Module).
Effect: If you upload a station configuration back to the PG (menu command: PLC
> Upload to PG), 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.
Result: The symbol table is opened.
3. Enter the required symbols for the addresses listed.
4. Confirm your entries with "OK".
Note
If you click on the "Add Symbol" button in the dialog, the name of the address is
entered as a symbol.
Further information
• Online help on HW Config
What? Where?
Setting the startup mode of the CPU (see below) HW Config (Object Properties)
Setting OB85 (I/O access error) (see below) HW Config (Object Properties)
Setting the Process Image 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 (OB1). 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 instruction in OB1.
• Data blocks created by SFCs in the work memory are deleted, 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
When using S7-400 CPUs in the PCS 7 process control system, the hot restart is
not permitted.
Assigning local data to priority classes: Some priority classes require more or
less memory in the local data stack than others. With suitable parameter settings
for the S7-400-CPUs, it is possible to set local data areas of different sizes for the
various priority classes. You can deselect priority classes that are not required.
This extends the memory area of the S7-400-CPUs available for other priority
classes. Deselected OBs are ignored during program execution and therefore save
computing time.
How to calculate the local data is described in an FAQ on the Web.
Note
Make sure that you also take into account the reserves configured for
Configuration in RUN (CiR).
Further information
• Online help on HW Config
• Section "Default Parameter Values for the CPUs"
Processing of the Process Image Tables for CPUs Supplied after 10/98
Start of the current cyclic processing Start of the next cyclic processing
Å Current cycle time of OB1 Æ
Output of the Update of the Processing of Output Update of the Processing of
PIQ PII OB1, or the of the PIQ PII OB1, or the
cyclic interrupts cyclic interrupts
etc. Æ
Procedure
To set the process image size, follow the steps outlined below:
1. Open the hardware configuration.
2. Select the CPU.
3. Select Edit > Object Properties.
Result: The "Properties - CPU ..." dialog box is displayed.
4. Select the "Cycle/Clock Memory" tab and set the size of the process image.
5. Confirm the dialog box with OK.
Note
The default size of the process image is CPU-specific.
See also Section "Default Parameter Values for the CPUs"
Note
• Each input/output address must be assigned to a process image partitions.
• 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).
Procedure
To set the process image partitions, follow the steps outlined below:
1. In the hardware configuration, select the I/O module you want to assign to a
process image partition.
2. Select the menu command Edit > Object Properties > Addresses.
3. Change to the "Addresses" tab and make the required assignment to a process
image partition (PIPx; x=1 through 15).
4. Confirm the dialog box with OK.
You can specify which process image partition is assigned to which OB when you
assign parameters to the CPU and the priority of the OB (see following Figure).
Procedure
To assign the process image partitions to OBs, follow the steps outlined below:
1. Select the CPU in the hardware configuration CPU.
2. Select the menu command Edit > Object Properties.
3. Change to the "Cyclic Interrupts" tab and make the settings you require.
4. Confirm the dialog box with OK.
Further information
• Online help on HW Config
SIMATIC H Station
For a fault-tolerant automation system, a SIMATIC H station is inserted in the
project in the SIMATIC Manager as a separate station type. Only this station type
allows the configuration of two central units each with an H-CPU providing a
redundant structure for the process control system.
Where is it Described?
For a step-by-step description of configuring fault-tolerant process control systems,
refer to the manual Process Control System PCS 7; Fault-tolerant Process Control
Systems.
Where is it Described?
• Manual Automation Systems S7-400F/S7-400FH, Fail-safe Systems.
• For a step-by-step description of configuring fault-tolerant process control
systems, refer to the manual Process Control System PCS 7; Fault-tolerant
Process Control Systems.
Note
After adapting the parameters, a download with the CPU in STOP is necessary.
Further information
• Section "Default Parameter Values for the CPUs"
Note
As of PCS 7 V6.0, UTC is always used internally in the system. Time information
displayed to the operator in process mode is in local time calculated based on
UTC. This makes system configuration possible across time zone boundaries.
This allows system configurations in which, for example, the automation system is
in a different time zone from the operator station. When necessary, the operator
can also change over between displayed in UTC or local time during operation.
Settings CPU
1. Open the hardware configuration of the required station.
2. Select the CPU and select the menu command Edit> Object Properties.
3. Change to the "Diagnostics/Clock" tab.
4. In the "Clock" group, select the type of synchronization "As slave" for the
synchronization on the PLC and (On MPI > None).
5. Confirm your entry with "OK".
Further information
• Manual Process Control System PCS 7; 10 ms Time Stamps
Overview
PROFIBUS DP is the most widely used fieldbus system in Europe (master/slave
bus system). The technical properties of this bus allow its use in almost all areas of
industrial automation.
Apart from its extremely simple installation (twisted pair cable), its extremely high
transmission rate (up to 12 Mbps), the flexible network structures possible (bus,
star, ring) and the option of redundancy with a fiber-optic double ring are its major
features.
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).
Confirm the dialog box with OK.
4. Select the ET 200M and select the menu command Edit> Object Properties.
5. Change to the "Operating Parameters" tab.
6. Activate the option "Replace modules during operation" and confirm the dialog
with "OK".
Note
If you do not select this option and the module fails, the AS interprets the module
failure as a failure of the ET 200M.
2. Now make the module settings for your particular situation (diagnostic
interrupt, measurement ranges etc.) in the Object Properties (select the module
> Edit > Object Properties).
(For all modules: Setting address and process image partition in the
"Addresses" tab.)
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
Remember that the measuring range for the analog input module must also be set
on the module itself using a coding key. You can find the code letter for setting the
measuring range selection module in the object properties of the module in the
"Inputs" tab to the right beside "Position of Measuring Range Selection Module".
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.
Further information
• Online help on HW Config
• Manual SIMATIC; Distributed I/O Device ET 200M
• Manual SIMATIC; Distributed I/O Device ET 200S
• Manual SIMATIC; Distributed I/O Device ET 200iSP
Introduction
Communication with PA field devices is over a DP/PA adapter or a DP/PA Link. To
configure field devices for PROFIBUS-PA (PROFIBUS for Process Automation),
remember the following points:
DP/PA Link
The DP/PA Link is a gateway between PROFIBUS DP and PROFIBUS PA. It
consists of the IM 157 interface module and a maximum of 5 DP/PA couplers
interconnected over backplane connectors.
The DP/PA Link is a DP slave (in the role of a quasi "master") that opens
PROFIBUS- PA for the connection of PROFIBUS- PA devices.
The device must be arranged as a DP slave taken from the hardware catalog and
attached to the DP master system (see also section "How to Configure the
Distributed I/O").
The display of the DP/PA Link not only shows the icon for the device itself but also
an icon for the "DP/PA system" - similar to that of the DP master system. The PA
field devices must be attached to this icon.
To attach PA devices, PROFIBUS-PA operates at a fixed transmission rate of
45.45 Kbps (no configuration necessary).
Procedure
1. Install the optional software SIMATIC PDM (PDM = Process Device Manager)
to be able to configure the PA slaves from the hardware catalog later.
2. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on the "Hardware" object (right-hand pane).
Result: Hardware configuration of the automation systems opens.
3. Configure a DP master system (HW Config).
4. Drag the DP/PA Link (IM 157) from the hardware catalog to the DP master
system.
Result: The dialog for specifying the master system opens.
5. Specify the master system (DP or PA) and confirm with "OK".
Result: The properties dialog PROFIBUS Interface opens.
6. Make the settings for the PROFIBUS interface.
7. Select the DP/PA Link to be able to see DP slave structure in the lower part of
the station window.
8. Slot 2 represents the "master" for the PA devices.
Double-click on slot 2 to configure the PA subnet.
9. Click the "Properties" button (below "Interface") in the "General" tab and select
the subnet with a transmission rate of 45.45 Kbps.
Note
The "PROFIBUS-PA" entry is only visible when the SIMATIC PDM optional
software is installed.
You must configure at least one PA device in PROFIBUS PA. Otherwise errors will
occur during compilation and the consistency check.
From now on, the PA devices are configured with SIMATIC PDM (double-click on
the device).
Further information
• Online help on HW Config
• Manual SIMATIC; Bus Adapters DP/PA-Link and Y-Link
• Manual PDM; The Process Device Manager
• Section "Configuring the SIMATIC 400 Station (CPU, CPs, Central I/O)"
Introduction
The diagnostic repeater allows simple diagnostics for detecting communication
errors in PROFIBUS DP chains with the DP Vx 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.
Topology Identification
Requirement: To be able to detect the topology, a PG/PC must be connected to the
relevant PROFIBUS network and a DP module must exist and be configured. If
several PROFIBUS networks exist, the topology must be identified for each
individual network.
1. Connect the PG/PC to the PG interface of the diagnostic repeater of the
network.
2. To identify the technology, change to the SIMATIC Manager and select the
project for which you require the typology identification in the component view.
3. Select the PROFIBUS master system in which the diagnostic repeater is
located.
4. Select the menu command Options > Set PG/PC Interface and select the
"Interface parameter assignment used" as in your configuration (for example
CP 5611 (PROFIBUS)).
5. Select the menu command "Properties" and set the properties you require in
the properties dialog.
Make sure that the address is set to "0".
6. Acknowledge the dialog with "OK" and also the warning that is displayed.
7. Select the menu command PLC > PROFIBUS > Prepare Line Diagnostics.
8. In the "Prepare Line Diagnostics" dialog, select the "Restart" menu command.
Result: The system data is acquired.
9. Close a dialog with the "Close" menu command as soon as the identification is
completed.
10. Select the menu command Options > Set PG/PC Interface and reset the
interface parameter assignment to "PC internal (local)".
11. Acknowledge the dialog with "OK" and also the warning that is displayed.
12. Select the required diagnostic function with the menu command PLC >
Diagnostics/Settings > ...
Further information
• Manual SIMATIC; Diagnostic Repeater for PROFIBUS- DP
Overview
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 large number of process
devices to be configured with one software package using a uniform user interface.
You use SIMATIC PDM as an integrated tool in the SIMATIC Manager (network
and plant view) and in HW Config.
The integration in HW Config allows you to edit devices 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 attachment, for example
whether they use PROFIBUS DP/PA or the HART protocol.
The following main functions have advantages particularly for testing and
commissioning as follows:
• Setting
• Changing
• Verification
• Management
• Simulation
of process device data.
You can also display selected values, alarms and status signals from the device on
the screen and effectively implement process monitoring. Using simulation or in the
manual mode of the devices, process-relevant values can be manipulated.
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. The following basic forms can
be distinguished:
- 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.
• To be able to go online with PDM, you require a PROFIBUS DP interface, for
example CP 5611. The CP must be set to the PROFIBUS DP interface (in the
SIMATIC Manager: menu command Options > Set PG/PC Interface).
Further information
• Manual PDM; The Process Device Manager
• Online help on STEP 7
HART Modules
HART modules are analog modules to which HART transducers can be connected
(HART = Highway Addressable Remote Transducer).
HART modules are intended for distributed operation on the IM 153-2 (ET 200M) or
IM 152 (ET 200iSP).
To assign parameters for the HART transducers, start the SIMATIC PDM
parameter assignment tool.
Further 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.
Y-Link
The Y-Link consists of two IM 157 interface modules and a Y-adapter. The
Y-adapter is part of the Y-Link and is used to interface PROFIBUS-DP with the
DP master in the IM 157.
From the perspective of the programmable controller, the Y-Link is a DP slave, and
from the perspective of the underlying DP master system, it is a DP master.
Procedure
1. Select the required SIMATIC H station in the component view and open
HW Config by double-clicking on the "Hardware" object (right-hand pane).
Result: Hardware configuration of the automation systems opens.
2. Drag an IM 157 from the PROFIBUS-DP > DP/PA-Link folder to the redundant
DP master system of your CPU.
The "Properties - PROFIBUS Interface IM 157" dialog opens.
3. Change the proposed address of the IM 157 in the DP higher-level master
system and confirm with "OK".
Result: After closing this dialog, a dialog opens in which the lower-level master
system is displayed.
4. Select PROFIBUS-DP here and confirm with OK.
Result: The Y-Link is inserted in the redundant Insert 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 on it.
Result: The dialog with the properties of the lower-level master system is
displayed.
6. Select the "Properties" button
Result: The "Properties PROFIBUS" dialog box is opened.
7. Enter the name of the lower-level DP master system and change to the
"Network Settings" tab.
8. Select the transmission rate 45.45 Kbps to 12 Mbps and confirm with "OK".
9. Then configure the DP slaves for the lower-level DP master system.
Further Information
• Manual SIMATIC; Bus Adapters DP/PA-Link and Y-Link
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 check which DP devices and HART devices are
obtainable in the network (causes of possible connection errors are described in
the online help for SIMATIC PDM).
Note
SIMATIC PDM requires device-specific information for devices with diagnostic
capability. After installing SIMATIC PDM, this information is available for the
devices included in the SIMATIC PDM list "Integrated devices.chm" Start >
SIMATIC > Documentation > "Language" > SIMATIC PDM - Integrated
Devices.
You can add further devices using the "Manage device catalog" tool.
Further information
• Online help of STEP 7
• Online help on SIMATIC PDM
• Manual PDM; The Process Device Manager
• Manual Process Control System PCS 7; Service Support and Diagnostics
Introduction
There are plants that must not be closed down during operation. This may, for
example, be due to the complexity of the automated process or due to the high
costs 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.
Principle
A modification to the plant during operation using CiR is possible when you make
provision for subsequent hardware expansion of your automation system for a
specific 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 plant during operation with CiR (Configuration in
RUN) in sections of plant with a distributed I/O. This is possible only with a
configuration as shown in the figure (to avoid overcomplicating the picture, only
one DP and one PA master system are shown) and the following hardware.
• CPU (412, 414, 416, 417 as of firmware version V3.1.0 / 414H, 417H in single
operation as of firmware version V3.1.0)
• CP 443-5 Ext (as of firmware version V5.0)
• IM 153 (as of 6ES7153-2BA00-0XA00)
• IM 157 (as of 6ES7157-0AA82-0XA00)
Steps Involved
Below, you will see the steps required for a program and configuration modification
along with the corresponding plant status.
If necessary, repeat the CiR procedure (step 4 in the table above) several times in
succession. The only thing you then need to take into account is that you have
adequate numbers of slaves and I/O volume in reserve so that you can implement
all your plant expansions.
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 station later
CiR Elements
The following CiR elements exist:
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:
• Number of slaves that you can add with certainty (default: 15)
• Number of input and output bytes for future use (default: 1220 each for a DP
master system, 244 each for a PA master system). These relate to future user
data addresses. You can configure diagnostic addresses regardless of this.
CiR Modules
For the modular I/O device ET 200M (IMs of the type HF = High Feature), 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.
The additional user data volume never needs to be used fully. The currently
available user data volume must not, however, ever been exceeded. This is
prevented by PCS 7.
Note
If you add or remove slaves or modules, or want to make a modification to the
existing process image partition assignment, this is possible for a maximum of four
DP master systems.
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.
Make sure that you do not exceed a CiR synchronization time of 1 second.
• 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 modifications to more than one chain of the same time,
please add the individual times of the chains.
• When you download the configuration data to the CPU, you will once again be
informed whether the CiR synchronization time will be adhered to with the
settings you have made.
• To ensure the traceability of changes in RUN, we recommend that you only
make changes in small steps and only to one DP chain each time you start
CiR.
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.
The system sets an upper limit of 1 second and this is also monitored by the
system. During this time, process outputs and process inputs are kept at the last
valid values.
Note
• The automatic addition of CiR elements is possible only when no CiR object
already exists in the selected DP master system.
• The automatic addition of CiR elements is not available in DP master systems
behind an IM 157.
• If CiR capability is activated, slaves containing a CiR module and CiR objects
(for example DP/PA-Link) are indicated in orange.
The defaults of the CiR objects are identical for all CPUs. After activating the CiR
capability of a master system you should therefore check each CiR object to make
sure that the CiR synchronization time of the master system shown in the
properties window of the CiR object matches the upper limit set for the CiR
synchronization time of the CPU. In some situations, you may need to reduce the
number of guaranteed slaves for one or more CiR objects or increase the CiR
synchronization time of the CPU using SFC 104 "CiR".
Note
If there are no longer enough resources available in 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 of the CiR object.
Note
Deleting all CiR elements is possible only when a CiR object exists in the selected
DP master system.
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.
Following each change to the plant, you should check whether CiR capability still
exists (menu command Station > Check CiR Capability).
Rules
When adding components, keep to the following rules:
• Within a modular DP slave of the type ET 200M, you must only insert a CiR
module in the slot immediately after the last configured module (If you add CiR
elements automatically, this rule is adhered to automatically).
• Within a master system, you must assign a higher PROFIBUS address to the
added slave than the highest address used up to now.
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.
If you add a DP slave of the type ET 200M with CiR capability, this has a CiR
module from the very beginning.
Note
When you add a module to an ET 200M station, PCS 7 updates the number of
input and output bytes of the corresponding CiR module.
In the following figure, you can see the HW Config view after positioning 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. You can only start to add the real
stations or modules when the INTF LED has gone off again (maximum 1 sec). The
EXTF LED then also goes off again.
Back up your current configuration each time you have downloaded the station
configuration from HW Config (regardless of the operating state of the CPU). This
is the only way that you can continue working and not lose CiR capability if an error
occurs (loss of data).
Procedure
1. Select the object you want to remove.
2. Select the menu command Edit > Delete.
3. If necessary, repeat steps 1 and 2 for each further object you want to remove.
4. Select the menu command Station > Check CiR Compatibility.
5. Download the modified configuration to the CPU.
Note
• When you delete a slave, PCS 7 updates the guaranteed and the maximum
number of slaves and number of input and output bytes of the CiR object.
• When you delete a module in a modular slave of the type ET 200M, PCS 7
updates the number of input and output bytes of the corresponding CiR
module.
Note
The addresses of existing modules must not be modified with CiR.
Requirements
• A CiR object exists in the relevant DP master system.
• The number of modules to be modified is less than 100.
For details of the ET 200M modules (signal modules and function modules) that
can have parameters changed with the CPU in RUN, please refer to the
information text in the hardware catalog" (information text: reconfigurable online).
Note
in PCS 7, the input and output values have the status "BAD" after this OB83 start
Once the CPU has completed OB83, it sends the parameter data records and each
module affected receives all its data records (regardless of how many data records
are affected by the change).
There is then another OB83 start (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 this OB83 start.
Note
In PCS 7, the input and output value is have the status "OK" following the OB83
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.
If the transfer of the data records was successful, the DP master identifies the
modules as available in the module status data and if unsuccessful, it marks them
as unavailable. In the second situation, an I/O access an error occurs if the module
is accessed (went updating the process input image or when transferring the
process output image to the module or during direct access to the module that
starts OB85.
The input or output data of the modules behaves in the same way as if an
insert/remove interrupt had occurred; in other words they may not currently being
correct (because the module may not have evaluated its data records). The
restriction that data record SFCs must no longer be acted for the module does not,
however, apply any longer.
Note
If the change to the parameter settings for a module involves, for example,
deactivating the diagnostic interrupt, it is possible that the module still sends an
interrupt that it had already prepared.
7.8.7.9 ET 200M Modules that Allow New Parameter Settings and their
Reactions
The following table contains a list of modules from the ET 200M range whose
parameter settings can be changed. Please read notes 1 to 4 on the table.
Key to the Table:
1. If you make channel-specific changes to parameter settings, for example
deactivate diagnostics or a channel, no leaving state alarm is generated. If
there was a channel-specific entering state alarm prior to changing the
parameters, this remains set. This means that the LEDs on the station
(IM153-2), on the DP interface module (CP 443-5 ext) and on the CPU (EXTF)
remain lit. The corresponding message on the OS is not indicated as having
exited the state.
Remedies: Do not change parameter settings when an alarm is pending. Or
remove and reinsert the module..
2. If you change the parameter settings of a channel, the activated and
unaffected channels temporarily return an analog value W#16#7FFF, which
leads to the QBAD status in the channel blocks. After completing the
parameter changes, the current analog value is once again indicated by the
block.
3. If you need to change the setting for the measuring range module, we
recommend the following procedure: Remove the module, change the
parameter settings in HW Config, change the measuring range module on the
module and reinsert the module.
4. It is not possible to change the parameter settings of F modules in fail-safe
operation. When using F modules in stand operation, the module whose
parameter settings are changed must be removed and reinserted. We
recommend the following order: Remove the module, change the parameter
settings with HW Config, and reinsert the module.
Caution
Time stamps should only be used for important selected signals relevant to the
process and under no circumstances for all the binary signals that are read in.
This function is useful when large numbers of signals are reported at the same
time (for example when a fault occurs). Applying this to all binary signals would
increase the risk of messages being lost due to buffer overflow.
Requirement
Time stamps can only be used when the time-of-day is synchronized on all the
devices belonging to the system. This requires a connection to a time master.
Where is it Described?
• You will find detailed step-by-step instructions on configuring 10 ms time
stamps in the function manual Process Control System PCS 7; 10 ms Time
Stamps.
• You will find a full description and step-by-step instructions on setting time-of-
day synchronization in the configuration manual Process Control System
PCS 7; Operator Station.
Introduction
If signals that trigger messages change the 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, it is
possible to suppress the repeated signaling of "fluttering" states until an
acknowledgment is received.
Procedure
1. Select the required SIMATIC 400 station in the component view and open
HW Config by double-clicking on "Hardware" (right-hand pane).
Result: HW Config and the hardware catalog are opened.
2. Select the CPU.
3. Select the menu command Edit > Object Properties.
Result: The "Properties - ("CPU-xxx")" dialog box opens.
4. In the "Diagnostics/Clock" tab, activate the option "Acknowledgment-triggered
reporting of SFB 33-35".
Result: When this function is activated, SFBs 33 to 35 only report a signal change
again when the previous signal change (in other words, the previous entering state
message) has been acknowledged.
Note
In some situations it is possible to download the hardware configuration during
operation (CPU in RUN). The configuration changes you can make in RUN (CiR)
are listed in the section "Overview of the Permitted Configuration Changes".
Other configuration changes mean that the hardware configuration can only be
downloaded when the CPU is in STOP!
Note
For more detailed information about making system changes during operation in
H systems, refer to the manual S7-400H Programmable Controller, Fault-Tolerant
Systems
Procedure
Requirement. Functioning data connection from the engineering station to the
automation system.
1. Select the menu command Station > Save and Compile in HW Config.
Result: Any consistency errors are reported now and you can obtain more
information on them with "Details...".
2. To download the configuration, select the menu command PLC > Download
to Module.
Result: A dialog box opens in which you can decide whether to download in
STOP or in RUN. Here, select STOP.
3. Select "Download in STOP".
Result: A dialog box is displayed in which the destination modules are listed.
4. Here, you select the modules you want to download to. When you first
download, you must download to all modules and then later only the modules
in which you have made changes.
Result: After querying the node address for the download, the configuration is
downloaded to the target system. When you download, the CPU of the
SIMATIC station and any communications processors are set to the "STOP"
mode following a prompt.
5. On completion of the download, restart the CPU.
6. Close hardware configuration with the menu command Station > Exit.
Result: Your project is created, for example, with the following structure in the
component view.
Procedure
Once you have made the changes, you should save and compile the configuration.
Then perform the following steps:
1. Check that the current configuration can be downloaded with the menu
command Station > Check CiR Capability.
2. Download the configuration to the CPU (menu command PLC > Download to
Module ...).
3. Select the menu command Station > Save and Compile in HW Config.
Note
• 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 can only start to add
the real stations or modules when the INTF LED has gone off again. The EXTF
LED then also goes off again.
Recommendation
Back up your current configuration each time you have downloaded the station
configuration from HW Config (regardless of the operating state of the CPU). This
is the only way that you can continue working and not lose CiR capability if an error
occurs (loss of data).
Further information
• Online help on CiR
Note
If there is a power down during the system evaluation, all the CPU changes to
STOP mode, the only practical course is to run a warm restart.
Following this, OB80 starts with event W#16#350A and enters the duration of the
evaluation in its start information. This allows you, for example, to take the time into
account in control algorithm is in your cyclic interrupt OBs.
Note
Make sure that OB80 is always loaded on your CPU. Otherwise, the CPU changes
to STOP when an OB80 start event occurs.
Note
• 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 illustrates 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
1000
400
200
Total I/O
volumes in bytes
1K 4 K* 8 K**
* corresponds to the maximum address area of the MPI interface, for example
(2 K inputs+ 2 K outputs)
Based on this diagram, you can easily obtain the maximum configuration of the
master system based on the maximum CiR synchronization time if you only want to
make changes to one DP master system. This is explained based on an example
(see below).
The CPU now compares the calculated CiR synchronization time with the current
upper limit for the CiR synchronization time. The default setting for this upper limit
is 1 second and can be reduced or increased depending on your needs by calling
SFC 104 "CiR" (max. 2.5 s).
If the calculated value is less than or equal to the current upper limit, the CPU
accepts the modified configuration, otherwise it rejects it.
From the formula above, it is clear that the CiR synchronization time can be
influenced as follows:
The CiR synchronization time is reduced:
• the less input and output bytes you select for a master system,
• the less guaranteed slaves you select for the master systems you intend to
modify (the number of guaranteed slaves affects the number of input and
output bytes directly.),
• the less master systems you want to modify in 1 CiR action.
This is of particular significance for F systems. Here, the F monitoring time must
include the CiR synchronization time. The highest value of all the DP master
systems with a CiR object must be used (if only one DP master system is modified
per CiR action) or the sum of the master systems to be modified at the same time.
The following table is an example of a CPU 417-4 with six DP master systems.
We assume that the maximum permitted CiR synchronization time is 550 ms. This
means that modifications can be made to more than one DP master system as
long as the total CiR synchronization times of these master systems does not
exceed the value 550 ms. From the last column, you can see which DP master
systems can be modified in one CiR action.
Error Displays
From the beginning of the validation until completion of the SDB evaluation, the
INTF-LED is lit. It continues to be lit if changes are made to module parameters.
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 is lit. If
you have added slaves in the changed configuration, the BUS1F or BUS2F LED
also flashes. Once you have made the actual hardware modifications, the EXTF,
BUS1F and BUS2F LEDs go off.
Effects on the Operating System Functions during the CiR Synchronization Time
Overview
Creating network connections in PCS 7 involves the following topics:
• How to Display Networked/Non-networked Stations
• How to Create and Assign Parameters for a New Subnet
• How to Create and Assign Parameters for the Network Attachment of a Station
• How to Change the Node Address
• How to Save the Network Configuration
• How to Check the Consistency of the Network
• Cross-project Networks
• Configuring Redundant Networks
Procedure
1. Select the project for which you want to display the networking in the
component view of the SIMATIC Manager.
2. Select the required network in the right-hand window.
3. Select the menu command Edit> Open Object.
Result: NetPro opens and all the stations of the project are displayed
graphically with their network assignment.
Further information
• Online help on NetPro
• Section "How to Create and Assign Parameters for the Network Attachment of
a Station"
During the configuration of the station, you already have the option of creating
subnets and connecting 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.
Result: NetPro opens and the network configuration of the selected project is
displayed.
3. Click on "Subnets" in the "Catalog" window.
If the "Catalog" Windows is not visible, operate with the menu command View
> Catalog.
4. Click on the required subnet, whole down the mouse button and drag the
subnet to the window for the graphic network view.
A mouse cursor in the shape of a "Forbidden" sign indicates locations where it
is not possible to position the subnet.
Result: The subnet is displayed as a horizontal line.
5. Double-click on the symbol of the subnet.
Result: The properties dialog of the subnet opens.
6. Set the parameters for the subnet (for example, assign a unique name).
Tip:
If you hold the cursor over the symbol of the subnet, a tooltip with information on
the properties of the subnet is displayed.
Requirement
NetPro is open and the configured stations are visible.
Procedure
1. Click on the icon for the interface of the node (small box in the color of the
corresponding network type), whole down the mouse key and drag the mouse
pointer to the subnet.
If an attachment is not possible (for example: attachment of an MPI interface to
an Ethernet type subnet), the mouse pointer takes shape of a "Forbidden" sign.
Result: The network attachment is displayed as a vertical line between the
station/DP slave and subnet.
2. Select the network attachment and select the menu command Edit > Object
Properties.
3. Double-click on the icon for the network attachment or on the icon for the
interface.
Result: The properties dialog of the subnet node opens.
4. 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).
You specify the node address in the object properties of the Ethernet CP. The
following properties are defined:
• MAC address
• additional for 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 proposed by
the system may differ from the address of the module.
With more recent CPUs, a check box allows you to decide whether 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 and 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" tabbing the properties dialog and click the "Properties"
button.
4. Enter the MAC address, IP address and, if applicable, the subnet mask in the
dialog that opens.
5. Confirm the dialogs with "OK".
Further information
• Online help on NetPro (or HW Config)
Introduction
To save the network configuration and the connection tables, you can use the
menu commands Network > Slave and Network > Save and Compile.
Saving
When 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 Loadable system data block (SDBs) of the complete network configuration
everything are generated; these contain all the connections, node addresses, subnet
properties, input/output addresses and module parameter assignments.
Compile changes only Loadable system data block (SDBs) of modified connections, node
addresses, subnet properties, input/output addresses or module
parameter assignments are created.
Before you save, you should check the consistency of the network configuration.
The following, for example, is reported:
• 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 is running when you perform the following actions:
• Menu command Network > Check Consistency
• Menu command Network > Check Consistency Project-wide
• Menu command Network > Save and Compile (in the next dialog, select the
option "Compile and check everything")
• Download to the target system (consistency check of the stations and
connections to be downloaded)
Procedure
Select the menu command Network > Check Consistency in NetPro.
Result: The consistency check is run. Following this, the window "Outputs for
consistency check for <path + project name> opens. Any errors and warnings are
displayed here (these can relate to the hardware configuration, network or
connection configuration).
Cross-project Networks
With PCS 7, you can configure cross-project Ethernet networks and then configure
connections over them. Networks included in more than one project are not created
in one step. The subnets configured in the individual projects are merged in the
multiproject and assigned to a logical "entire network" that represents the common
properties of all 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".
Further information
• Section "How to Merge Subnets from Different Projects into a Multiproject"
• Online help on NetPro
Redundant Networks
Both the fieldbus (PROFIBUS DP for the connection between the AS and
distributed I/O) and the plant bus (Industrial Ethernet for the connection between
AS and OS server) can be designed redundantly.
Basic Procedure
1. Create a project (single project) with the PC Station Wizard (CPU 414H or
CPU 417H).
Result: A SIMATIC H station and two PROFIBUS systems are created in the
project and the PROFIBUS systems are already connected to the 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.
As a result, you have both a redundant fieldbus system and a redundant plant bus
system.
When you continue with the configuration, make sure that you assign other
redundant components (for example redundant OS server) to the correct plant bus.
Further information
• Function manual Process Control System PCS 7; Fault-tolerant Process
Control Systems.
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. If necessary, you must change the
node addresses.
Introduction
Communication connections or simply connections must always be configured,
when data exchange between the automation systems or the automation system
and an operator station is required in the user program using communication
blocks.
What is a Connection?
A connection is a logical assignment between two communication partners
for executing communication services
(for example 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 (for example whether a connection remains permanently
established; which of the partners initializes connection establishment; whether
operating state messages will be sent).
Special Feature
PCS 7 automatically assigns a local ID for both endpoints of the connection if both
communication partners are S7-400 stations or when 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 connection
table.
Further information
• Section "Blocks for Different Connection Types"
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.
Result: The network view is opened with the SIMATIC 400 stations, the
corresponding ET 200M I/O devices, the operator station and the networks in
your project.
3. Double-click on a SIMATIC 400 station in your project in the SIMATIC Manager
and select the CPU.
4. Select the module for which the connection is to be created in the network
view, for example, the CPU of the SIMATIC 400(1).
Result: The connection table of the selected module is displayed in the lower
part of the network view.
5. Select an empty row in the connection table and select the menu command
"Insert > New Connection".
6. 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 of the connection when
configuring the corresponding PC station (OS) (area: "Connection Identification";
field: "Local ID").
9. After configuring a new connection, this must still be downloaded to the CPU of
the relevant stations.
- Select the CPU in a station in which you configured the connection.
- Select the menu command PLC > Download in the current project >
Connections and Gateways
Result: All connections and gateways are downloaded.
Note
The configuration data of the partner station must also be downloaded.
Further information
• Section "Cross-Project Connections in a Multiproject "
• In the online help for the dialog
Note
If several PC station connections are configured on one AS, all these connections
must have the same name (Recommendation: specify name of AS).
Procedure
1. Select the required project in the component view of the SIMATIC Manager.
2. Select the menu command Options > Configure Network.
Result: The network view is opened with the SIMATIC 400 stations, the
corresponding ET 200M I/O devices, the operator station and the networks in
your project.
3. Select "WinCC Application" in the symbol of the "SIMATIC PC station".
Result: The connection table is displayed in the lower part of the NetPro
window.
4. To insert a new connection, select the menu command Insert > New
Connection.
Result: The "New Connection" dialog box opens.
5. In the "Connection partner" field, select the CPU that will be connected to the
OS and make sure that the option "Display properties dialog before inserting" is
selected.
Note
If you are working in a multiproject, you must select the target project using the
multiproject folder and select the required CPU.
Note
To avoid errors and improve clarity, you should change the default connection
name (S7connection_1) to suit your project (for example, name of the AS).
8. Close the connection configuration with the Network > Save and Compile
menu command.
9. Select the PC station and download the configuration with the menu command
PLC > Download in the current project > Selected Station.
Note
Once you have downloaded the hardware configuration for the first time from
HW Config (STOP), changes to the configuration should then only be downloaded
using "Compile and Download Objects" or from within NetPro.
Note
Change local ID only: You can change the local ID directly in the "Local ID" column
of the connection table.
Go to partner station: When you are editing in the connection table, you can
change easily to the connection table of a connection partner:
Select a connection in the connection table.
Select the menu command Edit > Go to Partner Connection.
This function is also possible for cross-project connections in the multiproject. The
project in which the connection partner is located must be open and the subnets of
the projects involved must already have been merged.
Note
To avoid the AS generating messages during operation when the OS simulation is
started or terminated on the engineering station, the connection ID for the
engineering station should be higher than 0xc00.
Further information
• Section "Cross-Project Connections in a Multiproject "
Requirements
• NetPro is open.
• A CPU or a WinCC application is selected.
Tip:
If the columns are set too narrow, the entire content of individual fields is displayed
if you position the mouse pointer briefly over a field.
Note
The column widths and the visible columns are saved for the particular project
when you close the project; in other words if you open the project on a different
computer, the settings remain valid there.
Go to Partner Station
When you are editing in the connection table, you can go directly to the connection
table of a connection partner:
1. Select a connection in the connection table.
2. Select the menu command Edit > Go to Partner Connection.
This function is also possible for cross-project connections in the multiproject. The
project in which the connection partner is located must be open in NetPro.
Further Information
• For more detailed information on the columns of the connection table, refer to
the context-sensitive help.
Introduction
If cross-project subnets are configured, connections can also be configured over
such subnets. The endpoints 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 modified without breaking the connection
(modification 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 (see also the online help for the
dialog).
Further information
• Section "How to Merge Cross-Project Connections"
Requirements
To merge connections within a multiproject, the following conditions must be met:
• The corresponding connections in the various projects must have exactly the
same connection names (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.
Merging Connections
To merge connections, follow the steps outlined below:
1. Select the required multiproject in the SIMATIC Manager
2. Select the menu command File > Multiproject > Synchronize Projects.
The "Synchronize Projects in the Multiproject" dialog opens.
3. In the left-hand window, select the entry "Merge connections".
4. Click the "Execute" button.
5. If the "Result" field does not indicate an error, click on the "Save" button. 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:
• S7 H station (two H-CPUs) <-> S7 H station (two H-CPUs)
• SIMATIC PC station <-> S7 H station (two H-CPUs)
The properties of fault-tolerant connections correspond to those of the S7
connections; however restricted to S7-H-CPUs and OPC servers of SIMATIC PC
stations.
With a fault-tolerant S7 connection, two connection paths between the connection
endpoints are normally possible.
Requirement
• The hardware configuration of the two subsystems of a fault-tolerant system
must be identical.
• The communication partners involved are H-CPUs or a suitably configured PC
station.
• To use fault-tolerant S7 connections between a PC station and a fault-tolerant
automation system, the software package S7- REDCONNECT must be
installed on the PC station.
Basic Procedure
1. Select the CPU of an age 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 "Insert New Connection" dialog
box.
4. Select the connection type "S7 connection fault-tolerant".
5. The remaining steps are the same as for configuring an S7 connection.
Further information
• Manual Process Control System PCS 7, Fault-Tolerant Process Control
Systems
Overview
After creating the S7 programs including the chart folder in the component view, all
the resources exist for specifying the AS functions in the plant hierarchy by
inserting and programming CFC charts and SFC charts. The following table
provides you with an overview of the basic steps in programming that are then
described in greater detail below.
Overview
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 by textual interconnections.
On completion of editing, the parts are copied back to the original project. Charts
with the same name are replaced (following a prompt for confirmation). The textual
interconnections are then re-established.
If textual interconnections cannot be closed, for example because a block was
deleted, they are reported in a log and can be edited manually later.
• An unwanted interconnection can result in the original project if, for example,
cross-chart interconnections are modified in the temporary project and only one
of the charts involved is returned to the original project.
Example: Chart CFC_A as an interconnection to a block in chart CFC_B. Both
charts are copied to a temporary project and edited. During editing, the
interconnection between the charts is deleted. Only CFC_A is returned to the
original project. A textual interconnection results in CFC_B of the original
project, that can actually be closed.
Result: The interconnection deleted in the temporary project reappears in the
original project.
• Textual interconnections created before copying/moving are included in the
target project (temporary project). This might be a concrete path reference (that
can be closed) or a character string (required connection that will only be
configured in the target project).
Caution
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.
Further information
• Online help of STEP 7
Note
You should 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 on the CFC Editor or on the programming languages, refer
to the online help and the relevant manuals.
Block Type
A type definition that specifies the algorithm, the type name, and the data interface
(the input and output parameters) exists for each function block.
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
If you now place a block in your CFC chart, by inserting it in your chart, you create
a block instance of this block type. Instance in this sense means that it is a usage
of the selected block type.
You can create any number of block instances from a particular block type. You
can assign names to these block instances, interconnect them, and assign
parameters to them without changing the functionality specific to the type.
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.
Further information
• Manual CFC for S7; Continuous Function Chart and in the online help.
• Section "Creating Process Tags from Process Tag Types (Multiproject)"
Requirement
You have created a project structure (plant view) in the SIMATIC Manager in which
you can configure CFC/SFC charts.
Procedure
The following table lists the steps required to create the configuration.
Further information
• Online help on CFC
• Manual CFC for S7; Continuous Function Chart
• Getting Started CFC for S7; Continuous Function Chart
Requirement
project with an S7 program has been created in the SIMATIC Manager.
Procedure
How to create an empty CFC chart:
1. Select the required hierarchy folder in the plant view of the SIMATIC Manager.
2. Select the menu command Insert> Technological Objects > CFC.
Result: An empty CFC chart with a default name is created and you can
change it to meet your requirements. A new CFC chart consists of a chart
partition with 6 sheets without further chart partitions.
Note
The maximum length of a chart name is 22 characters. The name must not include
the following characters: \ / . " %.
Further information
• Online help on CFC
• Section "How to Define CFC Chart I/Os"
• Charts in charts: Manual Process Control System PCS 7; Getting Started -
Part 2
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.
Result: The CFC chart is opened in the CFC Editor. A new CFC chart consists
of a chart partition with 6 sheets without further chart partitions.
3. Go to the "Libraries" tab in the catalog. Here, you will also see the master data
library.
4. In the master data library, select the block type you want to insert and drag it to
the chart.
Result: An instance of the block type is created in the CFC chart.
5. Insert further blocks into the CFC chart in the same way.
Each inserted block is given default runtime properties (these can be changed;
refer to the section "Runtime Groups and Runtime Properties").
Note
You can search for a block by specifying a block name in the input field of the
catalog and then searching for it using the Find button (binoculars). If the text you
entered is not found as a block name, CFC searches for a block with a
corresponding comment. The folder (for example of the block family) in which the
block is located is opened and the block is selected.
With the "Find initial letter" check box, you can decide whether or not the search
starts at the initial letters (restricted search) or whether part of a name or comment
should be searched for (default: free search).
Further information
• Online help on CFC
Procedure
1. Select the block in the CFC chart and select the menu command Edit> Object
Properties.
Result: 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
For blocks, the maximum length of the name is 16 characters (for nested charts 22
characters). The name must not include the following characters: \ / . " %.
3. Select the "Inputs/Outputs" tab. Here, you can set the parameters for all the
I/Os of a block (values of the I/Os, hidden/visible, released for testing, relevant
for archiving etc.). The "Name" column lists the names of all inputs and
outputs.
Note
If you change units or operator texts, these are no longer taken into account during
block type import.
4. Once you have made all the parameter settings, confirm your entries with
"OK".
Result: The name is now displayed in the CFC chart in the header of the block.
5. Follow the same procedure to place further blocks in the CFC chart.
6. To interconnect, click on the required output of the block.
7. Now click on the input of the block with which you want to interconnect the
output.
Result: The CFC Editor automatically creates a line indicating the
interconnection.
Note
The order of steps 6 and 7 can also be swapped.
You can create further interconnections in the context-sensitive menu if the I/O is
selected:
• Interconnection to address ...
• Interconnection to runtime group ...
8. Make the other parameters settings and create the interconnections in the
same way.
Note
To make tracking easier, a connecting line can be displayed (this flashes in a
different color both in the chart and in the chart overview).
Flashing can be canceled again by clicking on the chart.
Further information
• Online help on CFC
• Interconnection with process pictures: Manual Process Control System PCS 7;
Getting Started - Part 2
• Archive tags: Configuration manual Process Control System PCS 7; Operator
Station
• Section "How to Assign Parameters and Interconnect the Blocks"
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 run-time 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
sequentially 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:
• Deactivate or activate selected blocks of an OB. (Runtime groups are activated
or deactivated using a block output of the data type "BOOL"). If a run-time
group is deactivated, the blocks it contains are no longer executed.
• Execute selected blocks with a specific scan rate (every nth number of cycles)
and/or with a phase offset to achieve better load balance 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".
This means that later compilations and online downloads of changes take
far less 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. Otherwise, there will be no noticeable improvement in
performance when you compile or download changes only compared with
compiling and downloading the entire program.
You must also take into account the startup 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.
As default, the rule is as follows: The block is inserted after the block displayed in
the status bar of the CFC.
One of the following is displayed in the status bar:
• When you first create a chart, the default of the specific PLC
• The last newly inserted block (color code: black font on light-green
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.
Further information
• Online help on CFC
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, "General" tab under "To be installed in OBs/tasks".
Moving Objects
You move an object by selecting it (SFC chart, runtime group, or block) in the right
or left window and then dragging it to the object after which you want to install it.
If you drag an object to a run-time 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 is the structure is not expanded
[+].
• and 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 run-time group, if you answer with "no" it is installed after the run-
time group.
If you drag an object to a task, it is installed before the objects already installed.
Note
When moving blocks, remember that according to the improved run sequence
model as of PCS 7 V6.0, all blocks of a chart are located only 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 using the relevant menu commands or the buttons in the
toolbar or by dragging them while holding down the Ctrl key (see also: Moving
Objects).
You can also install blocks (if you have the windows displayed simultaneously) by
dragging them directly from a CFC chart to the required position in the run
sequence.
Note
Objects with the "@" system identifier were automatically installed in the run
sequence when the module drivers were generated and should only be
manipulated with the function in the SIMATIC Manager Options > Charts >
Generate Module Drivers...; in other words, they should not be moved or deleted
manually.
Further information
• Online help on CFC
Note
When you insert blocks in the CFC chart, they are automatically installed in the run
sequence.
Procedure
You start the optimization in the runtime editor using the menu command Options
> Optimize Run Sequence.
• Excluding the entire task including the runtime groups it contains from the
optimization (option: None).
Note
• You can enable optimization of an individual runtime group in the Object
Properties of the runtime group, option: Optimization run sequence (this option
is set as default). This means that you can remove individual runtime groups
from the optimization by resetting this option.
• 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 you optimize before 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. The module driver is therefore started again the next time you
compile (option "Generate Module Drivers" is set and cannot be deselected).
Caution
If blocks are interconnected over INOUT parameters, the data flow may be
reversed; in other words, from input to output. This cannot be taken into account
when optimizing the run sequence.
Remedy: In this case, you must optimize the order yourself and exclude the
relevant runtime group from the optimization.
Caution
With cascaded interconnections and other connections with several return jumps,
runtime group optimization should be deactivated for the runtime group.
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.
Note
You can only assign unconnected I/Os with a compatible data type.
Note
If an I/O that is connected with the chart interface is made invisible, there is no
sheet bar entry. The interconnection can then only be recognized by the object
properties of the block (tab: I/Os, column: Interconnection).
System Attributes
Just like the block I/Os, you can also assign system attributes to the individual
chart I/Os.
The following rules apply:
• If an I/O is reconfigured by dragging it to define it as a chart I/O, it adopts the
system attributes of the block I/O.
• If a predefined chart I/O is interconnected with a block I/O, you must define the
system attributes yourself - there are not adopted from the block I/O.
A chart with chart I/Os does not have system attributes itself (apart from those of
the I/Os).
Further 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. In the CFC Editor, select the menu command Chart > Compile > Charts as
Program.
Result: the "Compile Program" menu opens.
2. When necessary, activate the following options:
- Update sampling time
- Delete empty runtime groups
- Generate module drivers
(see also online help)
3. Confirm the dialog box with OK.
Note
If the check box is disabled (grayed) but the check mark is set, the "Optimize Run
Sequence" function was run after the module drivers were generated. The driver
blocks are therefore no longer in the prescribed order and the driver generator
must be started again prior to compilation.
The optimized run sequence of the other blocks and runtime groups is not affected
so that optimization does not need to be repeated.
If you optimize before 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. The module driver is therefore started again the next time you compile
(option "Generate Module Drivers" is set and cannot be deselected).
Note
If you work only 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
You can compile and download all objects centrally in the SIMATIC Manager with
the menu command PLC > Compile and Download Objects. You are supported
here by PCS 7. This dialog lists all objects of the multiproject that can be compiled
or downloaded.
Use this function, the hardware configuration should have been downloaded to the
CPU once (initial commission of the automation station).
Further information
• Section "How to Download CFC Charts to the CPU"
• Section "Downloading to All CPUs"
• Online help on CFC
Requirement
Before you can download, there must be a connection between the CPU and your
PC.
Procedure
1. Select the menu command PLC > Download in the CFC Editor.
Result: A dialog opens in which you can decide how the download will be
performed ("Scope" and "Include user data blocks").
2. Select the scope:
- Entire program
The entire content of the "Block" folder is downloaded and, following a
prompt, the CPU is set to STOP.
- Changes only
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".
Note
Please remember, however, that it is not possible to fully exclude the risk that the
CPU nevertheless changes to STOP. The reasons for this include, for example
temporary inconsistencies that cannot be checked by the loader (for example local
requirements of blocks that do not include reference lists).
Note
With the programs created in CFC, you must download to the PLC from CFC,
since only this download function guarantees the consistency of the configuration
data with the CPU data.
The same download function is also used when you select the menu command
"PLC > Compile and Download Objects" or select the chart folder and PLC >
Download in the SIMATIC Manager.
Further information
• Section "How to Compile CFC Charts"
• Section "Downloading to All CPUs"
• Online help on CFC
Introduction
The Test mode relates to the CPU belonging to the active CFC chart.
To support you during commissioning, the CFC editor provides test functions that
allow you to monitor and influence the execution of the blocks on the CPU and, if
required, to change settings. As alternatives, the Test mode can be run in two
modes:
• Process mode
• Laboratory mode
Laboratory Mode
The laboratory mode allows convenient and efficient testing and commissioning. In
the laboratory mode, in contrast to the process mode, communication for online
dynamic display of charts is unrestricted.
When Test mode is activated, all blocks have the status "watch on".
Requirement
Testing is possible only when there is a connection between the CPU and your PC
and the program has been downloaded.
Procedure
You can select the mode for the test in the CFC Editor using the menu commands
in the "Debug" menu. It is not possible to change over once you are in Test mode.
• Activating Test Mode:
Select the menu command Debug > Test Mode in CFC. The Test mode is
activated. You can now activate the debug menu functions; Most of the
functions of the Edit mode become inactive.
• Deactivating Test Mode
Select the menu command Debug > Test Mode in CFC again. The Test mode
is deactivated. When you deactivate the Test mode, the debug functions
become inactive and the functions of the Edit mode are activated again.
Troubleshooting
From within the CFC chart, you can open the block type belonging to a block
instance. In the CFC chart, select the menu command Edit > Go To > Block Type.
If the source file of the block is included in the project, the tool with which it was
created (LAD/FBD/STL or SCL) opens with which you can edit the block type. If the
source file is not in the project, LAD/FBD/STL is nevertheless opened. You can
then only read the block information (exception: The system attributes of the I/Os
are editable). If an SFC instance is selected in the CFC chart, the corresponding
SFC type is opened in the SFC editor.
Further information
• Online help on CFC
• Manual Process Control System PCS 7, Getting Started - Part 1
• Manual CFC for S7; Continuous Function Chart
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.
Procedure
• Open the trend display
The window of the trend display can be opened for each CPU with the menu
command View > Trend Display.
• Set the trend display
With the trend display open, set
- the number of measuring points for the time axis in the "Display" area
- the current mode of the trend display and any abort conditions in the
"Recording" area with the "Change" button.
• Start/hold trend display
If test mode is active for the current CPU, recording can be controlled in the
"Recording" area with the "Start"/"Hold" button.
• I/O assignment to a channel
The assignment of an input/output to a channel can be specified when the
trend display is open using the Debug > Inputs/Outputs > Insert in Trend
Display menu command.
• Export trend display
If the trend display is open, the export format can be set using the menu
command Options > Settings > Export Trend Data.
With the "Export" button, you can export the current trend display in a format
that can be read with Excel.
Further information
• Online help on CFC
AS Runtime Measurement
To avoid runtime errors in new and modified configurations, it is advisable to
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 (known as a
block pair below). For the warning limits, you also require the MEAS_MON block.
Warning
! • Only qualified personnel should work on process control systems.
• Keep to the plant-specific and legal regulations when making changes to a
plant.
• Note the plant-specific constraints and adapt the version accordingly.
• Remember at all times that changes to a plant can have effects on other parts
of the plant.
Procedure
1. Create a new chart in CFC (runtime monitoring ASNo x).
2. Place a block pair in this chart for in every cyclic interrupt OB.
3. Connect the "TM" I/Os of a block pair.
Notes on Troubleshooting
You can reduce the execution time of an OB by installing the runtime groups with
scan rates and phase offsets, or calling blocks in other OBs.
If you can increase the cycle monitoring time, this will be possible 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. The effect of the SUBNET block is that when an error OB (for
example OB 86, rack failure) is called, only the driver blocks that signaled the error
execute. This reduces the execution time necessary.
Further information
• Online help on CFC
• For help on specific blocks, first click the "?" button in CFC and the click on the
header of the block.
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 send over 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 for this are supplied with PCS 7.
SEND_BO
The block sends up to 128 BOOL values over an Industrial Ethernet connection to
other S7-CPUs that must then call the function block type "REC_BO" (FB208) of
the PCS 7 Communication library to receive the data.
The consistent data are available in REC_BO only on completion of the job (in
other words, after arrival of the DONE = TRUE acknowledgment). The
acknowledgment is recognizable by a signal change to 0 at the output CIW.
By applying the value 1 to the FAST parameter, the FB allows the sending of a
frame per function block call. It is, however, only practical to use this fast send job
sequence when the frame can be transmitted in the time available between two FB
calls.
REC_BO
The block receives 128 BOOL values over an Industrial Ethernet connection from
another S7-CPU that must then call the function block type "SEND_BO" (FB207) of
the PCS 7 Communication library 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 is available only on completion of the job when the signal at output NDR
changes from 0 to 1.
SEND_R
The block sends up to 32 BOOL and 32 REAL values change-driven over an
Industrial Ethernet connection to another S7-CPU that must then call the function
block type "REC_R" (FB210) of the PCS 7 Communication library to receive the
data.
The consistent data is available in REC_R only on completion of the job (in other
words, after arrival of the DONE = TRUE acknowledgment). The acknowledgment
is recognizable by a signal change to 0 at the output CIW.
By applying the value 1 to the FAST parameter, the FB allows the sending of a
frame per function block call. It is, however, only practical to use this fast send job
sequence when the frame can be transmitted in the time available between two FB
calls.
REC_R
The block receives 32 BOOL and 32 REAL values over an Industrial Ethernet
connection from another S7-CPU that must then call the function block type
"SEND_R" (FB209) of the PCS 7 Communication library 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 is available only on completion of the job when the signal at output NDR
changes from 0 to 1.
Introduction
You have configure the connection in NetPro, in other words, you have defined that
communication will take place between two communication partners.
In the CFC configuration, you must place the relevant communication blocks in the
CFC chart and assign parameters to them (ID that you assigned in NetPro; frame
ID R_ID; data to be transferred etc.).
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 its used for identification.
For each frame that is transferred over a connection, a block pair (send, receive)
must exist in the CFC chart. This means that you must configure a send block in
the sending CPU and a receive block in the receiving CPU.
AS1 AS2
SEND_BO REC_BO
REC_R SEND_R
R_ID=2 FB FB R_ID=2
210 209
SEND_R REC_R
S7 connection
R_ID=3 FB ("pipe") FB R_ID=3
209 210
Requirement
The connection between the automation systems involved is configured in NetPro.
Principle Procedure
1. Create a CFC chart in the sending CPU with a send block (SEND_BO).
2. Assign parameters to the block and interconnect it (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 to the block and interconnect it (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.
Further information
• Online help on CFC
• For help on specific blocks, first click the "?" button in CFC and the click on the
header of the block.
Introduction
The interface to the I/O (driver concept) described below was developed to ensure
high performance even in large systems. Care was taken to ensure that
configuration was both fast and simple.
Driver Concept
The driver concept of PCS 7 is characterized by the separation of user data
processing (channel blocks) and diagnostic processing (module blocks), the
symbolic addressing of I/O signals and the automatic generation of module blocks
by CFC.
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 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.
Signal-processing Blocks
Procedure
1. Open the SIMATIC Manager and the project in which you want to generate the
drivers.
2. Select the chart folder of an S7 program in the component view (make sure no
charts are selected in this chart folder).
3. Select the menu command Options > Charts > Generate Module Drivers.
As an alternative, you can set the option "Generate Module Drivers" in the
"Charts as Program" dialog in CFC when compiling CFC/SFC charts. Each
time you recompile, the required module drivers will be generated or updated.
4. Select the required options and confirm with "OK".
Caution
If modifications are made to the driver blocks during configuration (for example
extension of existing blocks or installation of new blocks etc.), the menu command
"Generate Module Drivers..." must be activated again at the latest on completion of
the configuration.
Compiling
Note
You should only set this "generate module drivers" option if you have changed
something in the configuration of the signal-processing blocks and the
configuration of the hardware since the last compilation or you have configured
something for the first time.
If the option is not set, the driver generator is not called and the time required for
compiling is shorter.
If the option is disabled (grayed) but the check mark is set, the "Optimize Run
Sequence" function was run after the module drivers were generated. The driver
blocks are therefore no longer in the prescribed order and the driver generator
must be started again prior to compilation. The optimized run sequence of the
other blocks and runtime groups is not affected so that optimization does not need
to be repeated.
Caution
There must be no intervention in the system charts since these involve system
functions (indicated by "@"). This also applies to changes to the installation in OBs
or runtime groups.
Further information
• Section "How to Configure the Distributed I/O"
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
hardware list "PCS 7 - Released Modules.pdf" on the Toolset CD "Process Control
System PCS 7 Software".
Procedure
If you want to connect other peripheral devices or I/O modules to the AS in a
concrete 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 then use them in the same way as the supplied driver blocks (signal-
processing blocks and diagnostic blocks).
Further information
• Manual Process Control System PCS 7; Programming Instructions Driver
Blocks
Introduction
Using the wizard for process tag types, the process tag type is copied from the
master data library to the specified target projects as a process tag and the
corresponding data is then imported. This is based on 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 in the plant hierarchy.
Overview
Creating process tags from process tag types and subsequent editing of the tags
involves the following topics:
• How to Create a Process Tag Type from a CFC Chart
• How to Modify a Process Tag Type
• How to Add a Process Tag Type to a Project
• Automatic Creation of a Number of Process Tags
• How to Edit a Process Tag
• How to Adopt Process Tags
• How to Synchronize Process Tags with the Process Tag Type
• How to Restore Lost Process Tag Type Assignments
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...
Result: The wizard is started and the "Introduction" page is displayed. The
current master data library is displayed.
3. Click the "Next" button.
Result: The dialog for copying the chart to the master data library as a process
tag type opens.
4. Confirm the dialog box with OK.
Result: The wizard changes to the "Which I/Os do you want to assign to the
process tag type?"
5. In the left-hand window "I/Os in the chart of the process tag type", select the
flagged I/O for "Parameter" and "Signal". (By double-clicking or selecting and
clicking the "Arrow" button).
Result: The flagged I/O is adopted and displayed bold.
6. In the right-hand window "I/O points for parameters/signals", you can edit the
selected flagged I/Os.
The "Parameter/Signal" columns can be edited (using a drop-down list box),
"Process tag interface" and "Category" (using a drop-down list box).
The drop-down list box appears when you click the input field.
7. In the left-hand window, "I/Os in the chart of the process tag type", select the
messages of the relevant blocks. Al the messages are displayed in the "I/O
points for messages" window.
8. Check the selection and click on the "Next" button and then "Finish".
Result: The new process tag type is stored in the master data library. The CFC
chart that was the origin of the process tag type is located in the S7 program
and can continue to be used there or, if it is no longer required, can be deleted.
Further information
• Online help on the PH, IEA and PO
Requirement
The CFC chart is stored in the master data library.
Procedure
1. Select the intended CFC chart in the SIMATIC Manager (plant view).
2. Select the menu command Options > Process Tags > Create/Modify
Process Tag Type...
Result: The wizard is started and the "Introduction" page is displayed. The
current master data library is displayed.
3. Click the "Next" button.
Result: The wizard changes to the "Which I/Os do you want to assign to the
process tag type?"
4. In the left-hand window "I/Os in the chart of the process tag type", select the
flagged I/O for "Parameter" and "Signal". (By double-clicking or selecting and
clicking the button). The flagged I/O is adopted and displayed bold.
5. In the right-hand window "I/O points for parameters/signals", you can edit the
selected flagged I/Os. You can edit the columns "Parameter/signal" (using a
drop-down list box), "Process tag connector" and "Category" (using a drop-
down list box). The drop-down list box appears when you click the input field.
6. In the left-hand window, "I/Os in the chart of the process tag type", select the
messages of the relevant blocks. Al the messages are displayed in the "I/O
points for messages" window.
7. If there are no process tags of the modified process tag type, click on "Next"
and then "Finish".
Result: The Wizard is closed.
Otherwise:
8. Click the "Next" button.
Result: You will see dialog page 3(3) "Do you want to complete the process tag
type and apply changes to the existing process tags?".
9. Click the "Finish" button.
Result: You obtain the log of the changes.
10. Click the "Exit" button.
Result: The changes to the process tag type and the process tags are
completed; the wizard is closed
Note
Modifications 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 run a new
import for the modified 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.
If there were already interconnections to these process tags, they are lost.
You can also delete process tags manually in the SIMATIC Manager.
If I/Os were added during the modifications, the import file must also be extended
accordingly.
Further information
• Online help on the PH, IEA and PO
Procedure
To insert process tags into a project, you have the following options (in the
SIMATIC Manager):
• Using the menu command Insert > Process Tag (from library), open the
"Process Tag Types" catalog in the process object view.
The catalog lists all the process tag types of the master data 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.
- Another option is to copy a process tag type in the catalog using Ctrl + C
and then paste it into one or more hierarchy folders one after the other with
Ctrl + V.
• With the menu command Options > Process Tags > Import... (with a process
tag type selected in the master data library), you can run an import and
generate any number of process tags from a process tag type (refer to the
section "Automatic Creation of a Number of Process Tags").
• Drag existing process tags to a hierarchy folder of another project (or use
"Copy" and "Paste"). If you paste into the same project, you will be asked
whether you want to overwrite or rename the existing object. Remember that
the chart name must only occur once.
Note
If you create process tags by copying and pasting, you still need to assign
parameters for them 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.
7.11.5.4 How to Assign an Import File to the Process Tag Type (Create an
Import File)
To generate process tags, an import file must be assigned to the relevant process
tag type. With the "assign import file to a process tag type" assistant, you can do
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.
Procedure
1. Select the intended process tag type in the SIMATIC Manager (plant view).
2. Select the menu command Options > Process Tags > Assign/Create Import
File.... The assistant starts and displays the "Introduction" page. The current
master data library is displayed.
3. Click on "Next": The assistant changes to the "Which import file do you want to
assign to the process tag type?" page. The "Import file" combo box displays
either a file or if no assignment has been made yet, it displays the text <no
import file assigned>.
4. The following options are now available:
- To check an assigned import file to find out whether all the information is
accurate, you can open the file ("Open File" button) and then edit the file
with the IEA file editor.
- To assign an import file that exists in the project, click the "Other File..."
button and select the required file in the dialog.
- To create a new import file, click on "Create Template File..." and select
the required columns/column groups in the dialog. Then edit the template
with the IEA file editor that you open with the "Open File" button.
Note
The "Column title" column can be edited if you select the <no import file assigned>
text in the "Import file" combo box. You can change the titles and then generate the
template file.
In the "Importing" column, a check mark indicates which flagged I/Os 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 on "Finish". The import file is assigned to the process tag type.
Further information
• Online help on the PH, IEA and PO
• Section "Creating/Editing Import Files with the IEA File Editor"
7.11.5.5 How to Create an Import File or Assign it to the Process Tag Type
To generate process tags, an import file must be assigned to the relevant process
tag type. With the "assign import file to a process tag type" assistant, you can do
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
Note
The "Column title" column can be edited if you select the <no import file assigned>
text in the "Import file" combo box. You can change the titles and then generate the
template file.
In the "Importing" column, a check mark indicates which flagged I/Os 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.
Further information
• Section "Creating/Editing Import Files with the IEA File Editor"
• Online help on the PH, IEA, and PO
Requirement
To create process tags from process tag types, the relevant process tag types
must have an import file assigned to them.
Further Reading
You will find a detailed description of the settings of the import files in the section
"Importing/Exporting Process Tags/Models". Below, you will find a description of
the basic procedure for existing assigned import files.
Procedure
1. Select the required hierarchy folder, project node or process tag library
(hierarchy folder in the master data library) or the process tag type.
2. Select the menu command Options > Process Tags > Import...
Result: The import dialog opens.
After starting the function, the wizard searches for the process tag types and
corresponding import files (in all hierarchy subfolders as well) and displays
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. With the "Other File" button, you can
browse for a different import file and select it instead of the selected file.
4. Start the actual import with the "Next" button followed by "Finish".
Result: Depending on the options selected, 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 and the name and path of the file are displayed below
the log window. You can modify this setting with the "Browse" button.
Further information
• Section "How to Import Process Tag Types and Models".
Procedure
1. Open the process object view with the menu command View > Process
Object View.
2. Select the required process tag in the tree structure (left-hand window).
3. In the table on the right, select the required tab and make your modifications
there (in the writable cells).
Example: You want to interconnect an I/O with another I/O.
Follow the steps below:
Requirement for the example: The I/O of the block is defined as a parameter.
1. Select the process tag.
2. Select the "Parameter" tab.
3. Select the cell for the required I/O in the "Interconnection" column.
4. Select "Insert Interconnection..." in the context-sensitive menu.
Result: The "Insert Interconnections" dialog box opens.
5. Select the process tag in the tree structure and the block containing the I/O you
want to interconnect.
6. Click "Apply".
(As an alternative, you can double-click on 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.
Requirements
A check is made to establish whether the following criteria of the CFC chart match
those of the process tag type:
• I/Os that are identified as parameters/signals.
• Blocks identified for messages.
The names of the blocks and I/Os must match.
Principle Procedure
1. Create a process tag type from one of the existing charts using the menu
command Options > Process Tags > Create/Change Process Tag Type....
Refer to the section "How to Create a Process Tag Type from a CFC Chart".
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 in the 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
• 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; in other words you do not want
them to be overwritten with the values of the process tag type, delete the
relevant fields in the import file.
Result: If the conditions for adopting the process tags are met, the CFC chart
becomes the process tag of the imported process tag type and the I/O name and
category is adopted 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 it is not part of a replica, set IEA flags may be reset.
Situation 2: Chart Has Lost its Assignment to the Process Tag Type
You have canceled the assignment of a CFC chart that was already a process tag
to the process tag type in its object properties (Object Properties > Tab: Process
Tag Type, chart selected, "Clear" button).
Follow steps 3. and 4. as described for situation 1.
Principle Procedure
1. Select the process tag type in the PH.
2. Select the menu command Options > Process Tags > Export.
Result: The "Import/Export Assistant Export Process Tags" dialog opens.
3. Select "Next" and in the next dialog select the export file ("Open File" or "New
File") and confirm with "Next"
4. If required, select the path and name of the log file and confirm with "Finish".
The export is made and the export file is created. The actions are logged in the
window and stored in the log file.
5. Select "Back" to check the export file and open the export file you have just
created.
Result: All copies of the process tag type are included in the file.
You can now uses file to work with, for example by adding entries, and then use it
for import.
7.11.5.9 How to Synchronize Process Tags with the Process Tag Type
When a process tag type is modified, the process tags existing in the multiproject
are automatically synchronized. If actions were taken that caused inconsistencies
between the process tag type and process tags (for example when some process
tags of the project were not available at the time of the automatic synchronization),
synchronization can also be started explicitly.
Requirement
Process tags exist in the multiproject and the modified process tag type is in the
master data library.
Procedure
1. Select the process tag type (in the master data library) and then select the
menu command Options > Process Tags > Update....
Result: The "Update Process Tags" wizard opens and the current master data
library is displayed.
2. Click the "Next" button.
Result: The wizard changes to the page "Do you want to compare the existing
process tags with the process tag type?".
Note
Modifications 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 run a new
import for the modified 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.
Further information
• Online help on the PH, IEA and PO
Remedy
You can create a process tag type from an existing process tag in the project and
re-establish the assignment.
Procedure
1. Select the process tag in the project.
2. Select the menu command Options > Process Tags > Create/Modify
Process Tag Type...
Result: The wizard starts and the current master data library is displayed.
3. Click the "Next" button.
Result: 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 on "Yes".
Result: The wizard changes to the "Which I/Os do you want to assign to the
process tag type?"
5. Click the "Finish" button.
Result: The process tag type is created and is stored in the master data library.
The assignment of process tags to the process tag type is therefore re-
established.
You now still have to assign the import file or create a new import file.
Note
During this action, you can, of course, modify the process tag type if this is
necessary. Existing process tags are adapted automatically.
Note
Please remember that the process tag may have been adapted for a specific
technological purpose that is either irrelevant for the process tag type or is not
allowed to exist. In this case, you must make the appropriate modifications (for
example interconnections, parameter settings) 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 need to be aware of details such as algorithms or the
assignment of machine resources but can concentrate solely on the technological
aspects of your configuration.
After creating the chart topology, you move on to configure the object properties
where you formulate the properties of the sequencers and the individual steps and
transitions; in other words, 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.
Further 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
interface.
The sequence logic of the SFC type is based on the interface I/Os of the SFC type;
in other words, in contrast to an SFC chart, an SFC type cannot access all process
signals.
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, 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 the SFC Library). However,
before they can be used, they must be copied from the library's chart folder to the
chart folder of the program. The SFC types are then visible 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. To achieve this, 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. SFC instances are represented as blocks like CFC instances; in other words
the 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.
Basics of Configuration
1. The SFC type is created. At the same time, the sequencers and the interface
are configured, refer to the section "How to Create an SFC Type"
2. The SFC instances are generated, assign parameters, and connected in the
CFC chart. Refer to the section "How to Create an SFC Instance"
Note
• You will find templates of sequences in the "SFC Library". You can copy these
templates and modify them for your own use.
• You can control and monitor SFC instances and SFC charts on the OS with
the optional package SFC Visualization. You also configure operation and
monitoring of SFCs in SFC Visualization.
Further information
• Online help on SFC
• Manual SFC Visualization for S7
Requirement
You have created a project structure in the SIMATIC Manager in which you can
configure CFC/SFC charts.
Procedure
Requirement
The required project structure must already exist in the SIMATIC Manager.
Note
• The names of the SFC charts can be up to a maximum of 22 characters long.
• 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: \, ., /, ", %.
Further information
• Online help on SFC
Chart Layout
The newly created SFC chart (SFC type) initially consists of one sequencer that
can be expanded to up to 8 (SFC type 32) sequencers. Each sequencer is created
in its own working window; you can switch between sequencers using the tabs at
the bottom edge of the window.
A new sequencer created with the menu command Insert > Sequence > ... is
inserted at a selected position in the chart in its initial status consisting of an initial
step, transition and final step and a tab is added at the lower edge of the window.
Each tab has the name of the sequencer (RUN, SEQ1, ...).
If you insert or delete SFC elements in the sequencer, its layout is changed
automatically according to predefined rules. These determine the clearance
between chart elements, the extent of steps and transitions, the alignment of
alternative sequences etc. You can change the display/layout rules at any time with
the menu command Options > Customize > Display....
You can center the entire plant topology on the display area. This achieves a
uniform distribution of the elements in the chart. With the zoom functions, you can
increase or reduce the size of the display (in percentage steps determined by the
zoom factor).
Syntax Rules
The chart topology is formed by the sequences of steps and transitions. The
fundamental rule of the chart topology is that a step (S) must be followed by a
transition (T) and a transition must always be followed by a step (sequence : S-T-S
or T-S-T). The editor automatically adheres to the rules.
Example:
If you insert a simultaneous sequence in a sequencer following a transition and
before a step, a transition is created automatically before the step since the syntax
rules require a transition before and after a simultaneous sequence.
Introduction
With the sequencer properties, you can specify how the sequencer starts (or which
of the sequential control systems starts first). The sequencer of a newly created
SFC chart (type) already has a start condition (RUN = 1) and is therefore linked
with the operating state logic (OSL). For each further sequential control system,
you must specify the start conditions yourself. The start conditions and the priorities
specify which sequencer starts.
Procedure
Select the menu command Edit > Sequencer Properties in the SFC Editor.
Result: A dialog opens in which you can set the sequencer properties listed in the
following table.
Further information
• Online help on SFC
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
value, name, comment).
Initialization In these tabs, you can define the actions for the steps
Processing • executed once when the step is activated (Initialization)
Termination • executed cyclically when the step is processed (Processing)
• executed once when the step is exited (Termination)
durchgeführt werden sollen.
The tabs for the processing phases (actions) "Initialization", "Processing" and
"Termination" all have the same structure. Here, you configure the statements that
will control the process.
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 had parameters
values assigned to it.
Procedure
1. Select the step you want to edit in the SFC Editor.
2. Select the menu command Edit > Object Properties.
Result: The properties dialog of the step opens.
3. Make the entries you require in the "General" tab.
4. In principle, the editing required in the other tabs is identical.
Select the required tab and position the mouse pointer in the input field for the
left address (the operator) of the required statement line.
5. Click the "Browse" button.
Result: The "Browse" dialog is opened. 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.
Result: All blocks of the chart are displayed.
Note
In SFC, the operator combines two addresses in a statement or condition.
• Statement: The first address is assigned the value of the second address.
• Condition: The addresses are compared with each other. The result is TRUE
or FALSE.
Operators are: = (statement), < (less than), <= (less than or equal to), = (equal to),
>= (greater than or equal to), > (greater than), <> (not equal to).
Further 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. In principle, you assign parameter values for the
transitions in the same way as for the steps.
Properties of Transitions
You can make the following settings in the Properties dialog of the transition:
Tab Meaning
General In this tab, you can edit the general properties for the selected transition (name,
comment).
Condition In this tab, you can define the conditions for the SFC chart/type that cause
transitions to pass on control within 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/type. The defaults are the conditions
formulated in the "Conditions" or "Start Condition" tab.
Conditions
Conditions in a transition allow you to do the following:
• 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.
Result: The properties dialog of the transition opens.
3. Make the entries you require 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.
Further information
• Online help on SFC
Procedure
The SFC > Properties... menu command opens a dialog box. Here, you have the
choice of three tabs:
• General
This tab is used to enter or modify the chart name, the author and the
comment.
• PLC Operating Parameters
In this tab, you can do the following:
- Set the defaults for the initial state of the chart. These defaults cover the
following: "Step control", "Operating mode", "Command output", "Cyclic
operation" and "Time monitoring".
- Set/reset the options for starting the chart. These are: "Autostart" and "Use
defaults of the operating parameters when SFC starts".
• OS
In this tab, you can set or reset the option for "Transfer chart to OS for
visualization".
Operating Mode
Default: Manual
In the combo box, you can decide whether the control is manual or automatic.
• AUTO (process mode): The sequence is controlled automatically; in other
words, the commands in the program apply. The commands are decided, for
example by the parameter assignment or interconnection of inputs of the SFC
external view in the CFC chart. In the "Auto" mode, the step control modes "T"
and "T / T and C" can be set.
• MAN (operator control mode): The sequence is controlled manually by the
operator (for example in the SFC test mode or on the OS in SFV). All step
control modes are permitted.
The different step control modes affect the behavior of prepared or true transitions.
It is possible to change the step control modes in all operating modes. The
individual step control modes are mutually exclusive.
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.
If this option is set (check mark), the actions of active steps are processed, if the
option is not set, the actions are not processed.
Cyclic Operation Default: Off
If the option is set (check mark), after the SFC chart or SFC instance generated
from this type has run, it changes from the "Completed" to the "Starting" mode; in
other words it begins automatically with the start condition.
Time Monitoring Default: Off
If this option is set (check mark), the monitoring times (# 0 ms) set in the object
properties of the steps are evaluated. If this time elapses, a message is output
(step error).
Autostart Default: Off
If the option is set (check mark), the SFC chart or the SFC instance generated
from this type is in the "Starting" mode following a restart on the CPU; in other
words, it starts automatically to process the start. If the option is not set, the chart
or instance is in the "Idle" mode and is waiting for a start command.
Use default operating Default: Off
parameters when SFC If this option is set, all the operating parameters in the "Defaults" group become
starts effective again when you start the chart or instance, for example after you made
changes in test mode.
What How
Opening a SFC In the SFC Editor, select the menu command SFC > Open, and then select the
chart/SFC type in the required chart.
SFC Editor To open an SFC type, you must select "SFC type" from the drop-down list box
in the "Object type" field in the "Open" dialog of the SFC editor.
Opening an SFC Chart: Select the required chart in the component view or plant view and select
chart/SFC type in the the menu command Edit > Open Object.
SIMATIC Manager Type: Select the required charts in the component view and then select the
menu command Edit > Open Object.
Opening SFC Instances To open the SFC instance, select the instance in the CFC chart and then the
Open command in the context-sensitive menu.
Further information
• Online help on SFC
Procedure
You can start configuring messages in the SFC Editor with the menu command
SFC > Message....
You can configure specific message texts for each SFC chart/SFC type. You can
modify the message texts in a dialog (for example to distinguish messages from
different charts/types).
In this dialog box, you can configure block-related message types and block-
related messages that will be output on WinCC display devices.
Settings
Tab 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 In this field, you select which messages must be acknowledged with which
priority. The higher value, the higher the priority.
Event Enter the Message text in this field.
Single acknowledgment Click on the check box, if you want the message to be acknowledged as a
single message.
Info text Enter the information text in this field.
SFC type only !
Whether or not this column is displayed depends on whether you are editing
message types on 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 in the message configuration and
the entries are not uniform. To make the entries uniform, overwrite the displayed
text.
If you have not yet created a WinCC display device, a display device is created
automatically and given an internal name.
SFC type
The SFC type is an object that can be manipulated in the SIMATIC Manager
(component view) in much the same way as the SFC chart.
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 must already exist.
Procedure
1. You create SFC types in the component view of the SIMATIC Manager with a
chart folder selected using the menu command Insert > S7 Software > SFC
Type.
Result: The next free FB number is automatically reserved for the SFC type
and is copied to the block folder as the type template with this number. This
means that when you create the type, you can configure messages and create
instances of the type without needing to compile the type. You can change the
FB number later in the Object Properties dialog.
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
included in the supplied block 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. In the properties dialog, adapt the properties of the SFC type to meet your
requirements; In the SIMATIC Manager: Edit > Object Properties.
3. Set the properties and the operating parameters.
You will find more detailed information in the online help and in the section
"How to Adapt the Operating Parameters and Runtime Properties".
4. Define the characteristics (in 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.
5. Add sequencers and configure them, edit the start conditions (refer also to the
section "How to Specify the Sequencer Properties").
6. Configure the messages for the SFC type.
You can configure seven messages with mandatory acknowledgment and five
messages that do not require acknowledgment. The SFC type itself requires
the remaining available messages (one per message type and 10 notify
messages for BATCH). You should also refer to the Section "Configuring
Messages in SFC".
7. Configure a footer (in the SFC Editor: menu command SFC > Footers...).
You can configure a footer for an SFC type just as for an SFC chart.
8. .....
You will find other configuration options in the online help on SFC and in the
manual SFC for S7; Sequential Function Chart.
Note
In the "SFC Library", you will find the "TypeStates" SFC type in SFC Library >
Blocks+Templates > Templates. This already contains several sequencers for
state-oriented execution of the sequential control system.
You will also find the "TypeCtrlStrategy" SFC type that contains control strategy-
oriented execution of the sequential control system. You can copy these templates
and modify them for your own use.
SFC instance
You create an SFC instance by dragging the SFC type from the block catalog to
the chart in CFC.
The SFC types in the chart folder 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; in other words, it overlaps one or more
objects that have already been placed, it is 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)). In the technological blocks of the
PCS 7 library, the most important I/Os are already predefined.
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 block catalog (Other blocks) of CFC and place it in
the CFC chart.
Result: An instance of the SFC type is generated in the 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 of the instance.
Open the SFC instance in CFC (context-sensitive menu: Open) and in the
Properties dialog, adapt the operating parameters that specify how the chart
executes (Refer to the section "How to Adapt the Operating Parameters and
Runtime Properties").
As an option, you can decide which of the control strategies provided by the
SFC type should be used for the SFC instance.
5. Assign parameters and interconnect the interface of the SFC instance.
You make the parameter settings 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.
Further information
• Online help on SFC
Principle Procedure
1. Open the SFC type in the chart folder.
Result: The SFC type is opened in the SFC Editor.
2. Make the required modifications in the SFC Editor.
Result: The modifications are made to the type and to every existing instance.
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 catalog.
5. If the modifications you have made are relevant to the parameter assignment
or interconnections, these must still be carried out in all the SFC instances.
To do this, open the relevant CFC charts and complete them.
Further Information
• Section "How to Download SFC Charts"
• Manual Process Control System PCS 7; Getting Started - Part 2
Compiling
When compiling (scope: entire program) all charts (including SFC types) of the
current chart folder are converted to the source language and then compiled. After
changing the SFC chart (SFC type, SFC instance), you only need to compile the
changes (Compile: "Changes only").
During compilation, a consistency check is performed automatically. You can also
start this check manually.
After you have compiled, you can download the user program to the CPU, test it
and start it up.
• view the statistics showing how many resources (DBs, FCs) are available for
compiling the charts and how many are already being used.
Note
If you work only 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.
Procedure - Compilation
1. Select the menu command SFC > Compile....
Result: A dialog box opens in which you can choose between the following
option buttons:
- Compile "Entire program" (all charts are compile)
- Compile "Changes" (only the objects changed since the last compilation
are compiled).
2. If necessary, select one of the following options:
- Option "Delete empty runtime groups": If this option is set, the empty
runtime groups are deleted prior to compilation.
These empty runtime groups can result from copying when branching and
merging projects. When these empty run-time groups are created, the
original names of the run-time groups are lost due to implicit
incrementation of the numbers.
- Option "Close textual interconnections": If this option is set, all the textual
interconnections are closed prior to compilation if the referenced
interconnection partner exists; in other words, there are converted to real
interconnections.
Note
If the option is not set or if there are textual interconnections that cannot be closed,
substitute values are generated; in other words, the default parameter value of this
block type is used.
- The options "Generate module drivers" and "Update sampling time" are not
relevant for SFC and are used by CFC.
3. Select the type of compilation you require ("Entire program" or "Changes only")
and start the compilation with "OK".
Result: The charts of the current program (chart folder) are checked for
consistency and then compiled.
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 (menu command Options > Logs...).
Note
You can also run a consistency check without compiling by selecting the Chart >
Consistency Check... menu command.
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 (in
other words interconnected).
• Checks whether all the blocks accessed by SFC conditions or statements still
exist.
Further information
• Online help on SFC
Downloading
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.
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 also used when you select the menu command
PLC > Compile and Download Objects in the SIMATIC Manager or select the
chart folder and then PLC > Download.
Requirements
You have already completed the following steps:
• There must be a connection between the CPU and your PG/PC.
• The edit mode is set (not the test mode).
You can download the entire program (CPU in STOP mode) or changes only (CPU
can be in the RUN-P mode).
Procedure
1. Make sure that the conditions listed above are met.
2. In the SFC Editor, select the menu command PLC > Download... and select
the type of downloaded in the dialog box, either "Entire program" or "Changes".
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. If the compilation is free of errors, the download will be started
automatically when compilation is completed.
Entire Program
If you select "Entire program", all the charts of the active chart folder are
downloaded to the CPU. After prompting you for confirmation, the CPU is set to
"STOP" and all the blocks on the CPU are deleted.
Note
Compiling the entire program does not necessarily mean a complete download. If
the program was already loaded on the CPU prior to compiling, it is possible to
download the changes only.
If a full download is aborted, no downloaded changes is possible until the full
download is completed. Reason: The blocks on the CPU were deleted prior to the
download.
Downloading Changes
If you select "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.
• 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.
• 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 be 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 downloading changes, the halted SFC chart is not started with the
property "Autostart: on" but must be started again by the operator.
Note
Please note that there is no absolute guarantee that the CPU will not change to the
STOP mode when you download changes.
Test Functions
To support you during commissioning, the SFC editor provides test functions that
allow you to monitor and influence the execution of the sequencer on the CPU and,
if required, to change setpoints.
Test Modes
The Test mode relates to the CPU belonging to the active chart. As alternatives,
the Test mode can be run in two modes:
Requirement
Testing is possible only when there is a connection between the CPU and your PC
and the program has been downloaded.
Testing
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 with which the SFC executes (for example cyclic operation).
When the SFC is in "RUN", you see
• which step is currently active
• which actions are executed in this step
• which transitions are active and which conditions must be satisfied for this
transition.
Further 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 fixed setpoint controls, motor controllers etc.
Instead of implementing new functional units each time they are required, you can
create a pool of ready-made functional units (models) in the engineering system
that you then only need to copy and modify for the new situation. You can also put
the models in your project library so that they can be used again.
Model
Note
You can only create or modify models in a multiproject.
A model consists of hierarchy folders with CFC/SFC charts, pictures, reports, and
additional documents. A model also contains a connection to an import/export file
(IEA file).
Using the Import/Export Assistant (IEA), you link block/chart I/Os and messages of
blocks with the columns of an import file.
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.
Replicas
After linking the model prepared in this way to an import file, the model can be
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 destination project.
Requirement
The functional unit from which you want to create a model has already been tested
on the automation system and on the operator station.
Modifying a Model
Models that do not yet have replicas can be modified at any time (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 flagged I/Os (IEA flags) of a model that already has replicas, a
message is displayed and the dialog is extended by an additional step. All the
modifications that have been made are logged in this additional dialog box. The
modifications are then made in all replicas; in other words:
• 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
In an existing model or in replicas of a model, the names of the blocks must not be
modified. Import/export would otherwise be impossible.
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
Remember that it may be necessary to adapt the IEA file as well.
Further information
• Online help on the PH, IEA, and PO
• Section "How to Work with Models in the SIMATIC Manager"
Requirement
The interconnection partners are in the same chart folder.
Syntax
The interconnection has the following syntax:
cfc\block.io or cfc\chart.io
If folders of the PH are included in the name, the path of the plant hierarchy can
also precede the name (th\th\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. Only single interconnections are possible at the inputs.
When creating the IEA file, the textual interconnection option must be activated in
the "Parameters" tab.
Multiple Interconnections
Multiple interconnections are interconnections that lead from one output to several
inputs.
Multiple interconnections can be entered in the import file for parameters or signal
outputs. The I/O names are separated in the column by double quotes (").
• If you want to retain an existing single interconnection and add a new
interconnection, enter the delimiter " (double quote) after the text for the
interconnection. Without this delimiter, 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 regardless of
whether the delimiter exists or not.
During export, the existing multiple interconnections are also indicated by the "
delimiter.
Rules
Note
• 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. During import,
this would lead to an interconnection in the model and therefore change the
model.
This column must therefore be corrected. To prevent accidental changes to the
model, the interconnection partner has a preceding question mark ("?") in the
"TextRef" column that would cause an error during import.
When correcting, you can then 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 was marked
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 flagged I/Os,
interconnections to shared addresses at signal flagged I/Os.
Generating Replicas
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 project as a
replica and the data is then 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: "Include 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
To generate replicas from models, the corresponding import file must exist.
Further Reading
You will find a detailed description of the settings of the import files with the IEA file
editor in the section "Importing/Exporting Process Tags/Models". Below, you will
find a description of the basic procedure for existing import files.
Procedure
1. Select the required model in the master data library.
2. Select the menu command Options > Models > Import...
Result: After starting the function, the assistant searches for the models and
corresponding import files (in all hierarchy subfolders as well) and displays
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. With the "Other File" button, you can
browse for a different import file and select it instead of the selected file.
4. Start the actual import with the "Finish" button.
Result: Depending on the options selected, 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 and the name and path of the file are displayed
below the log window. You can modify this setting with the "Other File" button.
Further information
• Online help on the PH, IEA, and PO
• Section "How to Import Process Tag Types and Models"
Copying Models
Note
In a multiproject, a model must not exist more than once and must be located in
the master data library.
With the process object view all the data of the basic control throughout a project
can be displayed in a process control-oriented view. Project-wide means that the
data of all projects in a multiproject is acquired.
Overview
Editing mass data in the process object view involves the following topics:
• How to Display the General Data
• How to Edit Parameters
• How to Edit Signals
• How to Edit Messages
• How to Edit Picture Objects
• How to Edit Measured Value Archives
• How to Test in the Process Object View
Filtering
In the process object view, you can limit the objects displayed using a filter. The
default is: <no filter>).
In the "Filter by column:" combo box, select the column in which you want to select
the objects to be displayed in the table using the filter text ("Display:" input field).
Examples:
• You want to display all CFC charts in the table.
In "Filter by column:", select the type and enter cf in the "Display:" input field.
Result: All object types are displayed that start with the letters cf, for example
all CFC charts.
• You want to display all objects from a particular area.
In the "Filter by column:" combo box, select the path and enter "tank" in the
"Display:" input field.
Result: All objects containing the string "tank" in their paths are displayed.
There are special filter entries for the "Simulate outputs" column.
Note
The filter settings you make in the "General" tab also apply to the other tabs. The
filter settings in these tabs further restrict the selection.
Sorting
The data in the process object view can be sorted in ascending or descending
order (alphanumerically). Simply click on the column header of the column
according to which you want to sort. A small arrow indicates the ascending or
descending order.
Further information
• Online help on the PH, IEA, and PO
Rules
In the process object you, you can also copy, move, and delete objects in the same
way as in the plant view. The following restrictions apply however:
• It is only possible to copy from the content window (right-hand window) to the
tree structure (left-handle window) or to a different view in the "General" tab.
• Copying and moving from the tree window or from another view to the content
window is not possible.
• Deleting objects is possible only in the tree window or in the "General" tab.
Blocks of Information
You can select, copy blocks of information in the table and paste the information
elsewhere. This function is available not only within the table but also between the
table and, for example, office applications such as Excel and Access.
This allows you to copy data quickly and simply from existing lists into PCS 7. If an
error occurs when doing this, you can correct the error using the "Undo" function
implemented in the table (right-click for context-sensitive menu).
Further information
• Online help on the PH, IEA, and PO
Note
• You do not need to specify an entire text but simply enough of the text to make
it identifiable.
• If you click the "Replace"/"Replace All" button and have not entered any text in
the "Replace with": box, the found text is deleted.
Further information
• Online help on the PH, IEA, and PO
General
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.
Column Meaning
Hierarchy / Path Displays the technological path of the object (or the storage location of the
projects / libraries).
Name Displays the icon of the object and the object name. You can modify the object
name here.
Comment Shows the comment on the object. You can change the comment.
Type Displays the object type, for example, process tag, CFC, SFC, picture, report, or
additional document.
Process tag type Displays the name of the process tag type from which the process tag was
derived.
FID Text box for the function identifier. The text modified here is entered in the
CFC/SFC in the labeling field, "Part 3" tab, "Name:".
LID Text box for the location identifier. The text modified here is entered in the
CFC/SFC in the labeling field, "Part 3" tab, "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 set in the the"Watch" column. In terms of color and text, the
status display is analogous to CFC.
Watch This column is visible only in the online view. Here, you can register the process
tag or the chart for test mode. If the watch is activated, the columns "Activated",
"Simulate inputs", and "Simulate outputs" are displayed dynamically.
Activated With this option, you can activate or deactivate charts in the run sequence. The
check box can be set offline and online.
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.
Column Meaning
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.
CPU 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 box. If the project contains
several S7 programs, these are displayed in the drop-down list box. If you select
a different S7 program, you can move the chart.
OS Displays the component path of the OS containing the picture or report.
By clicking in the box, you can display a drop-down list box. If the project contains
several operator stations, these are displayed in the drop-down list box. By
selecting a different OS, you can move the 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 the individual pictures.
Author Text field for the name of the author.
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.
Further information
• Online help on the PH, IEA, and PO
Parameters
This tab displays the flagged I/Os for all the process tags and CFC charts
displayed in the "General" tab that were selected explicitly for parameter
assignment or interconnections between the process tags or CFC charts.
I/Os can be selected for the "Parameters" tab
• in the SIMATIC Manager using the menu command Options > Process
Objects > Select I/Os... (display of the objects selected in the tree structure)
• in CFC in the "Properties – I/O" dialog (of a block)
• in the block type system attribute S7_edit = para
• in the process tag type in the "Create/Change Process Tag Type" dialog box
Processing
You can enter the value, unit, identifier, operate texts for binary states and
comments for the I/Os visible here. As an alternative to the value, you can also
insert block interconnections.
Each cell displayed in the table with a white background can be edited directly in
the process object view.
You can open the corresponding CFC chart in the context-sensitive menu. The
relevant I/O of the block is selected.
You can limit the selection of objects displayed using a filter (refer to the section
"Filtering and Sorting").
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).
Comment Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Show 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 Text field for the comment on the block I/O. You can change the comment.
Process tag connector Shows the name of the flagged I/O as specified for the process tag type (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 option is set in the the"Watch" column. In terms of color and text, the
column is analogous to CFC.
Watch This column is visible only in the online view. Here, the I/O can be registered or
deregistered for the test mode. If monitoring is activated, the columns "Status"
and "Value" are displayed dynamically.
Column Meaning
Value Text 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 a interconnected I/O of the type
IN or IN_OUT.
If this is the value of an enumeration, if it exists, the text for the enumeration
value can be selected from a drop-down list box. The enumerations and their
values are declared and managed on the ES.
If "Watch" is active in test mode, the column is displayed dynamically.
Unit Text field for the unit of the value. Apart from entering texts, you can also select
common units (kg, m, s, min, ...) from the drop-down list box (I/O with system
attribute "S7_unit"). See also Entering Units.
Interconnection Text field for interconnecting the I/O. Apart from entering text, you can also start
the interconnection dialog from the context-sensitive menu "Insert
Interconnection". A textual interconnection is displayed on a yellow background.
See also: Rules for Displays and Entries in the "Interconnection" Column.
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 Text field for the shortcut of the I/O (I/O with system attribute "S7_shortcut").
Text 0 Text 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 Text 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 In this column, you can see 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. If you click in the text box, a
drop-down list box is displayed. The following can be selected:
• No archiving
• Archiving
• Long-term archiving
Can be read back 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 Option with which you can decide 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 selected when the "Operator C and M possible" check box
is set.
Note: In the default setting, the column is hidden since this information is not
normally used in PCS 7. If you want the column to be displayed in your process
object view, you can select this with Options > Settings > Columns.
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 box opens from which you can select
the required name of 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).
Column Meaning
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).
Further information
• Online help on the PH, IEA, and PO
Signals
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. As
default, these are all the VALUE inputs and outputs of the PCS 7 channel driver
blocks.
I/Os can be selected for the "Signals" tab
• in the SIMATIC Manager with the menu command: Options > Process
Objects > Select I/Os...
• in CFC in the "Properties – I/O" dialog box
• in the block type: system attribute S7_edit = signal.
Processing
You can enter symbolic names for the interconnection with the I/O as well as text
attributes and comments.
As an alternative to textual entry of the interconnection symbol, signals can also be
selected in a dialog if they have already been specified by the hardware
configuration.
In the context-sensitive menu, you can open either the relevant CFC chart or the
hardware configuration (HW Config) or the symbol table.
You can limit the selection of objects displayed using a filter (refer to the section
"Filtering and Sorting").
Each cell displayed in the table with a white background can be edited directly in
the process object view.
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).
Comment Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Show 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 Text field for the comment on the block I/O. You can change the comment.
Process tag connector Shows the name of the flagged I/O as specified for the process tag type (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 the"Watch" column. In terms of color and text, the status
display is analogous to CFC.
Column Meaning
Watch This column is visible only in the online view. Here, you can register or deregister
the I/O for test mode. If monitoring is activated, the columns "Status" and "Value"
are displayed dynamically.
Value Text 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 a interconnected I/O of the type
IN or IN_OUT.
If this is the value of an enumeration, if it exists, you can select the text for the
enumeration value from a drop-down list box. The enumerations and their values
are declared and managed on the ES.
If "Watch" is activated in test mode, the column is displayed dynamically (on a
yellow background). If I/Os are interconnected, the value to be monitored is
displayed on a grayish yellow background (cannot be edited). A red background
indicates a problem in transmission (value failed).
Unit Text field for the unit of the value. From a drop-down list box, you can select the
most common units (kg, m, s, min, ...) for this I/O (with system attribute
"S7_unit").
Note: The list of units is generated from the basic set of CFC. This basic set can
be managed and changed in the ES.
Signal Text field for the name of the interconnected signal. You can also enter an
absolute address. If a symbol exists for the absolute address you enter, this is
displayed; if not the absolute address is displayed preceded by '%'. Apart from
entering text, you can also start the interconnection dialog from the context-
sensitive menu "Insert Signal".
Signal comment Text field for the signal comment read from the symbol table (cannot be
changed).
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).
CPU 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 Text field for the shortcut of the I/O (I/O with system attribute "S7_shortcut").
Text 0 Text 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 Text 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.
Can be read back 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
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 box opens from which you can select
the required name of the enumeration. The enumerations and their values are
declared and managed on the ES.
You can also enter a name in the text box 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).
Further information
• Online help on the PH, IEA, and PO
Messages
This displays the message texts of the signaling blocks belonging to the process
tags and CFC/SFC charts displayed in the "General" tab.
Processing
The relevant charge can be opened from the context-sensitive menu.
You can limit the selection of objects displayed using a filter (refer to the section
"Filtering and Sorting").
Each cell displayed in the table with a white background can be edited directly in
the process object view.
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).
Comment Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Show 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 Text 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 box.
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 box.
You cannot change the priority
• 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").
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 Text field for the event text (for example "$$BlockComment$$ too high).
You cannot change the text if it is locked in the block type message.
Batch ID BATCH message text.
You cannot change the text if it is locked in the block type message.
Column Meaning
Info text You cannot change the text if it is locked in the block type message.
Note: Apart from the "Info text" column, the tab also includes the "Free text 1" ....
"Free text 5" and "Operator input" columns. In the default setting, the columns are
hidden since these texts are not normally used in PCS 7. If you want the columns
to be displayed in your process object view, you can set this with Options >
Settings > Columns.
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).
Further information
• Online help on the PH, IEA, and PO
Picture Objects
This displays all the blocks of the CFC charts that can potentially be controlled and
monitored by the operator for the process tags and CFC charts displayed in the
"General" tab, along with any existing picture interconnections and picture
assignments. All the SFC charts and any existing picture and connections and
picture assignments are also displayed.
For each block, you can see the location at which they are used (in which OS, in
which picture, interconnected with which picture object). With block icons, you can
select the appearance of the icon. If a row next to the block is empty, this means
that the block is not controlled or monitored by the operator on any OS of the
project.
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 want to change something in a picture, you can open the selected picture
WinCC Graphics Designer using the context-sensitive menu (you can also open
the CFC chart in the context-sensitive menu).
You can limit the selection of objects displayed using a filter (refer to the section
"Filtering and Sorting").
Each cell displayed in the table with a white background can be edited directly in
the process object view.
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).
Comment Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Show the comment on the block. You can change the comment.
Create block icon Check box with which you can decide whether or not a block icon is generated for
this block. With SFC, this row is displayed empty.
The option can only be selected when the "Operator C and M possible" check box
is set.
If you set the option, you can also edit the cell in the "Block icon" column.
Block icon 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 set. With SFC,
this row is displayed empty.
Here, you enter a name for this block instance if there is more than one variant of
block icons for this block type. If no name is entered, the standard block icon is
used.
Column Meaning
OCM possible Check box with which you can decide whether the block can be controlled and
monitored by the operator (system attribute "S7_m_c") or whether the SFC chart
is transferred to the OS for visualization.
MES-relevant Check box with which you can decide whether the information of the picture
objects can be transferred to the management levels MIS/MES in response to a
request.
The option can only be selected when the "Operator C and M possible" check box
is set.
Note: In the default setting, the column is hidden since this information is not
normally used in PCS 7. If you want the column to be displayed in your process
object view, you can set this with Options > Settings > Columns.
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 Text 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 connector Shows the name of the flagged I/O as specified for the process tag type (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 on which the 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 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).
Further information
• Online help on the 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 context-sensitive
menu.
You can limit the selection of objects displayed using a filter (refer to the section
"Filtering and Sorting").
Each cell displayed in the table with a white background can be edited directly in
the process object view.
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).
Comment Shows the comment on the object (cannot be changed).
Block Shows the block name (cannot be changed).
Block comment Show the comment on the block. You can change the comment.
I/O Displays the name of the block I/Os or SFC I/O (cannot be modified). This sale is
displayed empty if a picture object is assigned to the block as a whole.
I/O comment Text field for the comment on the I/O. You can change the comment.
Process tag connector Shows the name of the flagged I/O as specified for the process tag type (cannot
be changed).
OS Displays the component path of the OS containing the picture or 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 Text field for the name of the archive tag.
Variable comment Text field for the comment of the archive tag.
Long-term archiving Indicates whether or not the archive tag is intended for long-term or short-term
archiving. A change made here, takes effect directly in the measured value
archive of WinCC; in other words, the OS does not need to be recompiled. 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 box
(system, manual input).
Column Meaning
Archiving Here, you can specify whether archiving begins immediately at system startup.
You make the selection from a drop-down list box (enabled, disabled).
Acquisition cycle Cycle for acquiring data. You can make the selection from a drop-down list box.
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 cycle Here, you can enter the cycle used for archiving and for displaying the data. You
can make the selection from a drop-down list box. 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 box (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 make the selection from a
drop-down list box. 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.
Further information
• Online help on the PH, IEA, and PO
• Configuration Manual Process Control System PCS 7; Operator Station.
The "Messages", "Picture Objects", and "Measured Value Archive" tabs cannot be
selected in test mode.
Procedure
You can set the selection of the test mode in the process object view with the
"View" menu. Enabling and disabling only affects the active window of the process
object view.
• Activating Test Mode:
In the SIMATIC Manager, you can enable the test mode with the View >
Online menu command. When you enable the test mode, no new window
opens, the existing window is switched over.
• Activating Test Mode:
You can disable the test mode with the menu command View > Offline.
When you change to test mode, the online and offline data is checked to make
sure it matches (similar to the test mode in CFC and SFC). If there are deviations,
a message to this effect is displayed.
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.
Changes in the "Activated", "simulate inputs", and "Simulate outputs" columns are
effective both online and offline. 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.
"Signal" Changes in the "Value" and "Watched" columns are effective both online and offline.
This also applies when the I/O is not marked for testing.
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)
If you want to edit the value, the color changes from yellow to white when you click in
the cell. The offline value is then shown.
Further information
• Online help on the PH, IEA, and PO
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:
• Data from the plant planning can be synchronized with the data of the control
system engineering. This allows control system engineering and class
engineering to be edited at the same time independent of each other.
• Data from the engineering system can be exported as a template, reproduced
in an external program (for example Excel), and then imported back into the
engineering system. This allows the configuration of repeated or similar plant
information to the optimized.
Preview
These sections describe the following import/export functions:
• Import/export of process tags/models
• Import/export of the hardware configuration
Further information
• Section "How to Create a Process Tag Type from a CFC Chart"
• Section "How to Create a Model"
Note
The Import/Export Assistant (IEA) is a separate optional package in PCS 7 and
requires a separate authorization.
The IEA is supplied on the PCS 7 Toolset CD along with the PH and the process
object view and is installed along with them.
Define
model
ES data Planning system
management
Function units
Assign I/O signals,
import data ......
IEA Interconnection and
file parameter
Copy and description
parameterize ......
model
Import/
export
log
Update
planning system
Overview
Working with process tag types and models involves the following topics:
• Requirements and Steps in Configuration
• Functions for Working with Process Tags and Models
• How to Create an Import File or Assign it to the Process Tag Type
• What Happens during Import?
• How to Import Process Tag Types and Models
• What Happens during Export?
• How to Export Process Tag Types and Models
• Restrictions with the IEA
Requirements
To work with the Import/Export Assistant, you must first create process tag types
and/or models in the master data library.
Steps in Configuration
Step Activity
1 Create process tag type/model
(Refer to the sections "How to Create a Process Tag Type" and "How to Create a Model")
2 Assign the import file to the process tag type/model - create the import file
(Refer to the section "How to Create an Import File or Assign it to the Process Tag Type" and
Section "How to Create a Model")
3 Edit the import file with the IEA file editor
(Refer to the section "Creating/Editing Import Files with the IEA File Editor")
4 Import process tag types/models
(Refer to the section "How to Import Process Tag Types and Models")
5 (Supply process tags and replicas with actual parameters.
Only if the data was not already added with the IEA file editor.)
Model X
Further information
• Online help on the PH, IEA, and PO
Note
When working with the "import/export" functions of the Import/Export Assistant,
further hierarchy folders may be contained in the model. If the picture hierarchy is
based on the PH, there must only be one picture per hierarchy folder.
If the model includes nested hierarchical folders, these must not be renamed.
Further Functions
Note
To make the charts clearer to read, you can switch block I/Os of the blocks of the
models 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 if necessary correct them. The same applies to selections in
models.
Note
An interconnection is deleted when the signal name (symbol or textual
interconnection) consists of the codeword "---" (three dashes).
An interconnection remains unchanged, if no interconnection name (symbol or
textual interconnection) is specified.
4. Check out the data types of the I/Os for signals and assign them to the
interconnections. The rule for interconnections with shared addresses is as
follows: If the Option "Include signal in the symbol table" is set, look for the
names in the symbol table of the resource of the model. For PCS 7, it is
recommended not to set this option, since the entries are made in the symbol
table when you assign the hardware addresses with HW Config.
If the symbol name exists in the symbol table:
- Symbol name exists: The data type must be the same, the symbol name
must only exist once. The data type is set according to the block/chart I/O,
the absolute address overwritten and the symbol comment (if it exists in
the import file) is entered for the symbol. Only the information that has
changed will be overwritten, existing attributes are retained.
- If the symbol name does not exist: the interconnection is created and
the data type set according to the I/O, the absolute address and symbol
comment (if they exist in the import file) are created for the symbol.
5. The message text is imported for each message.
6. Points 1 to 5 are repeated for each line in the import file.
If you have selected a hierarchy folder that contains more than one model, the
input files appear in the list along with the model. You can still edit the list.
Following this, the import is started for all models in the list as described above.
You will receive error messages in the import log in the following situations :
• The hierarchy path contains a replica that does not belong to the model; in
other words, input/output flags are missing or there are too many and/or the
block is not or is incorrectly marked as a signaling block.
• There is a model in the hierarchy path
• The settings in the plant hierarchy do not match the imported hierarchy path
• Signals in the symbol table are not unique or will be written with incorrect data
types.
Overview
Using the Assistant for process tags or models, you import 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 and the data is then imported. According to the
entry in the import file, you can create any number of process tags.
When you import, you can decide whether or not the imported signals will be
entered in the symbol table (option: "Include 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.
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.
• of the model.
The model is copied from the master data library to the specified target project
as a replica and the data is then 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: "Include 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 in "English", the
German message texts will be written into the English text file.
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 are lost.
Procedure
1. Select the required hierarchy folder, project node or process tag library
(hierarchy folder in the master data library) or the process tag type.
Note
If you have selected a replica, a prompt is displayed, and you change to the
corresponding model in the master data library.
Note
The selected export files are completely overwritten during the export or are newly
created if they do not yet exist.
Multiple Export
By exporting the model(s)/process tags more than once, you can create several
export files (copies). Each time you export, you must modify the file name of the
assigned export file (see above). If you do not change the file names, the export file
is overwritten.
Preview
The following sections explain how to create and edit the import/export files (IEA
file) with the IEA file editor. This involves the following topics:
• Creating/Editing Import Files with the IEA File Editor
• How to Exchange Data with Excel/Access
• Structure of the IEA File
Project
Plant
hierarchy
Import file
Hierarchy Parameter Parameter Signal Message
interconn.
H\: PI: SI: SI: MI
V12\RA1\P01 Valve open Interrupt 1
V12\RA1\T01 V12\RA1\P01.V Heating on Interrupt 2
Situations for using the Editor (based on the example of a "process tag" /
"model")
The IEA File Editor is intended for the following situations:
• You have created a process tag type/model and created the import file with the
IEA. With this import file, you want to create replicas of the model or process
tags. The number of rows in the import file must be increased according to the
number of replicas/process tags you want to create (for example by copying
and editing).
• You have created a process tag type/model and created the import file with the
IEA. You want to change this model, for example by including further I/Os and
need to extend the import file by adding these columns.
• You do not have a tool for creating an import file and want to use the IEA File
Editor as a planning tool to structure the columns, column groups and rows of
the import file and the corresponding values.
• You want to compare an import file with an export file (or vice versa). By
opening two windows and arranging them in the IEA File Editor window, you
will have no difficulty in making the required comparison.
Further information
• Online help on PH, IEA, PO, IEA File Editor
Introduction
The import/export data (IEA file) is available as text files in the CSV format. The
CSV format is supported by many applications (Excel, Access, ...) and is therefore
suitable as a general data interface between any planning tool and the ES. In the
IEA, these files are expected with the extension ".IEA"; in other words, you may
need to modify this extension.
CSV stands for "Comma Separated Value" and is an ASCII text format in which
tabular data are saved. The separator of the cells is a semicolon, a new row is
created by pressing the Enter key.
You can create and edit a CSV file with table programs (for example Excel) or as
an export file from a database (dBase, Access, ...). You can also edit the file (with
the extension .IEA) conveniently 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.
Rows Meaning
0 There can be a comment line before the first header row (starting with "#" or "//") containing for
example 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. It is not necessary to enter all keywords, only the first one is
obligatory.
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.
The IEA file can be displayed and edited as a table formatted with the IEA File
Editor.
• Chart
The "Chart" column group is optional for models, but if used it always follows
the "Hierarchy" column group, or, if they exist, after the general column groups.
Any name can be used for the title. The column group contains the name and
comment of the CFC or SFC chart. The name of the chart in the replica of the
model is changed with the keyword ChName. The chart comment is changed
with the keyword ChComment.
• Other Column Groups
The following column groups identify the I/Os to be imported. Each of these
I/Os is described by a text string (in quotation marks) separated by ";"
(semicolon) from the next I/O. Within the text string, the data is separated by "|"
(pipe character).
Further information
• Online help on the 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. The symbolic
names of the inputs and outputs are also exported or imported (as long as you
have not changed the default setting).
Applications
• Data import from hardware planning tools
• Can be distributed using electronic media (for example E-mail)
• An export file can be printed out with word processing systems or can be
edited for documentation purposes.
A further important application of the import of a station configuration is when you
have identical or almost identical configurations in different parts of the plant. 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 is exported/imported.
The following are not included:
• 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 exchange)
Note
If your configuration contains modules from older optional 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
import.
Caution
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.
Procedure
1. Select the required station in the component view.
2. Select the menu command Edit> Open Object.
Result: The station configuration is opened in HW Config.
3. Select the menu command Station > Export.
4. Enter the path and name of the export file, formats and other options in the
dialog (refer to the section "Importing/Exporting the Hardware Configuration").
5. Confirm your settings with "OK".
Result: The station configuration is exported and stored in the selected path in
the form of a CFG file.
Further information
• Online help on HW Config
CFG File
The export of a station configuration as described in "How to Export a Station
Configuration" produces an ASCII file that you can read and edit with an editor
such as "Notepad" or "WordPad".
This file (CFG file) contains all the data of the hardware configuration including the
parameter assignments from the dialogs 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
Further information
• Online help on HW Config
Expansion
CFG files should always be created based on an existing, exported station
configuration (refer to the section "How to Export a Station Configuration").
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
suitably adapted (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".
With this as a basis, you can edit the individual sections of the file to suit your
purposes (copy, paste, edit).
Caution
You should be familiar with the content of the sections of the CFG file in detail
since editing is not supported by the system. Any errors made 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. Identifying the Area
Further information
• Online help on HW Config
Procedure
Recommendation: do not import an exported station configuration from the same
project. In this case, PCS 7 cannot handle the network assignment. Select a
different or new project for the import.
1. With an empty station configuration open (in HW Config), select the menu
command Station > Import.
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. In the dialog, navigate to the CFG file you want to import.
3. Confirm your settings with "OK".
Result: 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.
Further information
• Online help on HW Config
7.11.12.5 How to Import an Expanded Import File (Extra Remote I/O, Field
Device, Module)
Further information
• Online help on HW Config
Note
If you only overwrite the changed parts, the import is much quicker.
2. If errors are reported, save the error log. You can then eliminate any errors
based on the log.
3. Then confirm saving of the imported data with "Yes".
If you select "No" here, the import is aborted. The station configuration then
remains unchanged.
Further information
• Online help on HW Config
Introduction
Configuring the operator station involves several steps. Here you make the settings
using several PCS 7 tools:
• In the SIMATIC Manager
• In the WinCC Explorer
The entire configuration of the PCS 7 OS is done 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 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 OS" if you have made subsequent
changes in 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
Further information
• Configuration Manual Process Control System PCS 7; Operator Station.
Introduction
With the OS function "Lifebeat monitoring", it is possible to monitor the functions of
the CPUs and operator stations connected to the plant bus in the SIMATIC PCS 7
control system. This means that you always have an up-to-date overview of the
state of your plant.
The monitoring function is executed by 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.
New edit lifebeat monitoring in the WinCC "Lifebeat Monitoring" editor.
Further 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 SIMATIC PCS 7 program package with which discontinuous
processes, known as batch processes, can 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
• Permission management
• 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, unit classes, user data types, units of
measure etc.).
Permission Management
SIMATIC BATCH uses the central user management of PCS 7.
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 released 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.
Further information
• Online help on SIMATIC BATCH
• Manual Process Control System PCS 7; SIMATIC BATCH
Introduction
@PCS 7 is software based on @aGlance used to access the process data
acquired by PCS 7. @PCS 7 has access to the following PCS 7 data:
• WinCC archives (message, measured value and user archives)
• WinCC data management
Each @aGlance-compliant client application of MIS/MES is therefore capable of
accessing the data of PCS 7.
Configuration
Configuration involves the system settings and the server configuration of the
@PCS 7 system.
Once the @PCS 7 system has been configured, you can start, stop or restart it.
The system messages of the @PCS 7 environment since the last cold start are
also displayed.
Further information
• Manual @PCS 7; Interface to the Management Level
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
• How to Merge Subnets from Different Projects into a Multiproject
• How to Merge Cross-Project Connections
• How to Configure New Cross-Project Connections between AS and OS
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. Open the project on the distributed engineering station from the central
engineering station with the menu command File > Open in the SIMATIC
Manager and click the "Browse" button.
3. In the "Browse" menu in the "Find in directory" field, enter the path of the
project you want to move in UNC notation and select "Start Search".
Result: the project is displayed in the "User projects" tab.
4. Select the required project in this tab and confirm with "OK".
Result: The project is opened.
5. Select the menu command File > Save As ...
Make the following settings:
- Disable the "With Reorganization (slow)" option.
- Enable the "Insert in multiproject" option.
- Select "Current multiproject" in the drop-down list box.
- Enable the "Replace current project" option.
6. Confirm the dialog box with OK.
Result: An identical copy of the project of the distributed engineering station is
Note
Before the copied project can be copied back to its old location (same folder
name), this backup must be deleted or renamed (refer to the section "How to Move
Projects to the Distributed Engineering Stations").
Note
You can also move a project back to the central engineering station after it was
moved out with the "Remove to edit..." function and if it is obtainable over the same
path as when it was removed:
1. Select the "project removed for editing" on the central engineering station
(grayed out).
2. Select the File > Multiproject > Reapply after editing... menu command
Result: The project is reinserted from the distributed engineering station into
the multiproject on the central engineering station.
Further information
• Section "How to Move Projects to Distributed Engineering Stations"
If you use cross-project networks in the multiproject, the networks in the projects
must still be merged in the multiproject.
Requirement
To be able to merge subnets, you must have write access to the projects involved
and their subnets.
Procedure
1. Select the required multiproject in the SIMATIC Manager
2. Select the menu command File > Multiproject > Synchronize Projects
Result: The "Compare and Match up Projects in Multiproject" dialog opens.
3. In the left-hand window, select the Ethernet networks you want to connect up
and click "Execute".
Result: The dialog for merging or branching subnets is opened.
4. In the left-hand field, select the subnet and click the "->" button.
Result: The selected subnet is merged in the selected entire networ.
5. Change the default name of the cross-project network according to the
requirements of your project (click on the name twice).
6. Follow the same procedure for all the subnets you want to merge.
7. Click the "Apply" button followed by "Close" to exit the dialog.
In the same dialog, you can separate networks again that have already been
merged.
In this dialog, you can also create new cross-project subnets ("New" button).
Note
After merging the subnets and prior to downloading, you should use NetPro to
check that there is consistency throughout the multiproject (menu command
Network -> Check Interproject Consistency).
Procedure
Cross-project connections can be merged
• During the synchronization of projects in a multiproject in the SIMATIC
Manager with the menu command: File > Multiproject > Adjust Projects.
• In NetPro with the menu command Edit > Merge Connections
Functionality
There are differences in the functionality as explained below:
Further information
• Online help of STEP 7
• Section "How to Merge Cross-Project Connections".
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 and the multiproject level:
Refer to the section "How to Merge Subnets from Different Projects into a
Multiproject"
• The AS/OS assignment is fixed:
Refer to the section "How to Specify the AS/OS Assignment"
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", you select a connection partner in a different project.
Introduction
The functions for compiling and downloading are available in the following editors:
• HW Config
Compiling and downloading the hardware configuration (refer to the section
"Configuring the Hardware")
• NetPro
Compiling and downloading the network and connection configuration and the
hardware configuration (refer to the section "Creating Network Connections")
• CFC
Compiling and downloading the CFC configuration (refer to the section
"Creating CFC Charts")
• SFC
Compiling and downloading the SFC configuration (refer to the section
"Creating SFC Charts")
• SIMATIC Manager
Compiling and downloading individual or all objects of a multiproject
Note
Downloading the OS server data to the OS clients only needs to be performed
once after the first download. 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 updating server data: 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 recompliled and remember that
the server data must be downloaded once from the new computer (computer
name) or storage location.
The compilation 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.
To test the program, in other words, the CFC and SFC configuration, initially you
only need to compile and download the AS data.
Overview
• Compiling and downloading for PCS 7 includes the following topics:
• Requirements for Compiling and Downloading
• Downloading to All CPUs
• Options for Compiling and Downloading
• Change Log
Procedure
1. Select the OS client in the SIMATIC Manager.
2. Select the menu command Options > Assign OS/OS Server.
Result: The OS server data is downloaded to the OS client. The OS client then
knows the assigned OS servers.
Further information
• Configuration Manual Process Control System PCS 7; Operator Station
Introduction
A project is downloaded in the SIMATIC Manager with the central menu command
"Compile and Download Objects". PCS 7 provides the "Compile and Download
Objects" dialog for this task. The display of the objects in this dialog corresponds to
the component view in the SIMATIC Manager, i.e. you are shown all automation
systems, operator stations and SIMATIC PC stations that you have created in the
SIMATIC Manager.
The required settings for compiling and downloading are made in this dialog. In this
dialog, you can also specify whether you want to compile and download the entire
project or, for example only individual operator stations.
Requirements
• The PC station and AS station are configured and have been downloaded to
(from NetPro so that the connections are also loaded)
• The CFC and SFC configuration is completed.
• You have selected one of the following objects in the SIMATIC Manager:
- Multiproject
- Project
- STATION
Rules
• When downloading the entire program of an AS, in contrast to downloading
from one of the editors (for example CFC), the CPU always changes to STOP.
• Downloading the entire program to an OS is possible only when the OS
servers have been shut down (are not in process mode).
• Downloading changes to an OS is possible only if the OS is in process mode.
Procedure
Note
You should also refer to the section "Options for Compiling and Downloading"
1. In the SIMATIC Manager selects the object that you want to compile or compile
and download.
2. Select the SIMATIC Manager menu command PLC > Compile and Download
Objects.
Result: the "Compile and Download Objects" dialog opens.
3. Open the tree and activate the corresponding check boxes in the "Compile" or
"Download" columns for all objects that you wish to compile or download.
4. Select the objects you want to compile/download in the "Compile" and
"Download" columns. Your selections are indicated by a check mark.
5. With the "Status" and "Operating Mode" buttons you can check the statuses
(changed, compiled, downloaded ...) and modes of your objects (RUN,
activated, ...), so that you can make the correct settings for compiling and
downloading.
6. Select the object you want to compile and/or download and click the "Edit"
button. Make the settings for the compilation and/or download (for example
compiling and downloading the entire program or changes only).
Note
When you have completed the settings for compiling an operator station, it takes
some time for the compilation settings to be saved and for the download dialog to
be opened! The target path of the OS should already be entered here, otherwise
you should enter this in your station.
Note
Do not use the "Compile and Download Objects" function for PLCSIM
downloading.
Note
If the "Marked parameters" option is selected, only the block I/Os with the "Can be
read back" attribute (S7_read_back = true) are read Back. This setting must first
be made at the I/Os of the block type. The attribute cannot be modified in the block
instances.
Further information
• Online help on the "Compile and Download Objects" dialog box
• Section "Options for Compiling and Downloading"
Option Description
Settings for Compilation/Download
"Edit" button Opens a dialog in which the compiling and downloading settings
can be changed for objects selected in the "Objects" column.
"Check" button Checks the compiling and downloading properties of objects
selected for compiling and downloading in the "Objects" column.
This button is not active for block folders. The button is only active
when 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)?
• Is a password required (i.e. is a password assigned) and has a
password been entered? The password is entered after
pressing the "Edit" button for a selected block folder CPU.
Update
"Status" button Click the "Status" button to update 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 Click on the "Operating Mode" button to update any changed
operating modes in the display.
Status on opening When the option is deactivated (default), the "Compile and
Download Objects" dialog opens immediately with the menu
command CPU > Compile and Download Objects. "undefined" is
however entered everywhere in the "Status" column. To update for
the first time, click the "Status" button.
When the option is activated, expect a long delay before the dialog
opens regardless of the number of objects.
Select Objects
Select All With this button, you can select or deselect all objects in the
Deselect All "Compile" and "Download" columns. If the "Compile Only" check
box is selected, the button only affects the "Compile" column. If the
"Compile Only" check box is cleared, the "Select All " and "Deselect
All" buttons select or deselect all objects in both columns.
Compile only Activate this option if you only want to compile the selected objects.
The objects will not be downloaded to the CPU and the "Download"
column is hidden.
Option Description
Do not load if compilation error is If the option is activated, a compilation error (for example a time
detected stamp conflict) means that no object is downloaded.
If the option is not activated, all objects are downloaded that were
compiled without error. Objects that caused an error during
compilation are not downloaded.
Take connections into consideration Activate this option if you want to compile or download configured
connections of the project or multiproject. This option can only be
activated when a project or multiproject is the initial object selected.
A multiproject is especially suited as an initial object because all
partners in cross-project connections can be automatically
downloaded from this object.
When this check box is activated, displayed "hardware" and
"connection" objects are automatically activated for compiling
(setting cannot be altered).
When the "Compile only" check box is deactivated as well, all
"hardware" and "connection" objects are also automatically
activated for downloading (setting cannot be altered).
Note: Because the hardware configuration is always loaded as well
through this dialog, you can only perform a download when the
CPU is in STOP mode. Individual connections can be downloaded
using NetPro.
Further information
• Online help for "Compile and Download Objects" (Station properties)
Requirement
• The SIMATIC Logon Service is installed.
• The change log is activated for the currently selected chart folder.
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 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 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 of the chart folder. You can only activate
and deactivate the log in this dialog.
Logging
Logging is performed in the "Logs" dialog area in the "Change 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 change 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) is 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 CFC: • Configuration of the connections
• Activation/deactivation of sequence groups
In SFC: • Configuration of constants in steps
• Configuration of constants in transitions
• Configuration of constants in sequence properties
Test Options
The process object view provides a test mode, with which you can test and
commission process tags and CFC charts online on the CPU: Refer to the section:
"How to Test in the Process Object View"
You can document changes made in test mode with the change log
dokumentieren (which user, when, on which CPU, what change was made ...). This
is only possible if the SIMATIC Logon Service is installed and the change log for
the current chart folder is activated: Refer to the section "Change Log".
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: Refer to the section "How to Test CFC Charts"
• SFC
Testing the SFC configuration: Refer to the section "How to Test the SFC
Program"
Overview
The following procedures should be distinguished for testing:
• How to Test a Plant During Operation
• How to Test S7-PLCSIM
• How to Test Field Devices
Further information
• Manual Process Control System PCS 7; Getting Started – Parts 1 and 2
Introduction
S7-PLCSIM is an optional software package for simulation of an AS. It is included
in the installation of PCS 7 and can be started from the SIMATIC Manager.
S7-PLCSIM allows you to edit and test your program on a simulated programmable
controller installed on your computer or programming device. Since the simulation
is implemented completely by the PCS 7 software, you do not require any S7
hardware (CPU or signal modules). You can test programs 47-400 CPUs using a
simulated automation system. This allows you to test operator control and
monitoring of the simulated CPU (OS runtime) 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 can monitor and
modify variables with the variable table.
Note
• S7-PLCSIM operates with an MPI connection in contrast to the usual network
configuration for PCS 7 over Industrial Ethernet.
• The simulation of I/O modules is not performed with S7-PLCSIM; it is carried
out by the blocks CH_DI, CH_AI etc. within the CFC charts.
• S7-PLCSIM is not suitable for the simulation of large-scale configurations in
the PCS 7 environment.
Installing PLCSIM
PLCSIM is not installed automatically when PCS 7 is installed. You will find the
software on the 3rd CD. To run the software, you require a separate authorization.
Principle 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 menu command Options > Simulate Modules.
Result: S7-PLCSIM is started and a "CPU" subwindow is opened (with the
preset MPI address).
3. Select the object "Charts" in the tree.
4. Download all of the required data to the simulated AS (for example, hardware
configuration, blocks) with the menu command PLC > Download.
5. Configure S7-PLCSIM for the test (for example, create subwindows for
monitoring the AS) and ensure that the program can be executed.
6. Set the simulated CPU to RUN and test your program.
7. Open the SFC and CFC charts and select the menu command Test > Test
Mode.
8. Test the program exactly like you would with a real CPU.
Further information
• Online help for S7-PLCSIM
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 an operating plant is not fundamentally different from the test described in
the section "How to Test with S7 PLCSIM" or the test with a test setup with an AS.
The number of obtainable automation systems and operator stations is, however,
normally far larger than possible with a test setup.
There are higher requirements for safety during ongoing operation and the number
of persons involved is greater. The warning above should make this clear.
Another concern is that the test should limit any disruption or interruption in the
operation of the plant to a necessary minimum. The plant operator should be
usually consulted beforehand.
Further information
• Online help on the SIMATIC Manager
• For more detailed information, refer to the documentation for SIMATIC PDM.
Start > SIMATIC > Documentation > English
Introduction
The Version Cross Checker is a separate application you can order as an option.
The Version Cross Checker (VXC) allows you to quickly and reliably compare two
S7 programs in order to find differences relevant to downloading. This feature
allows you to recognize any changes in the S7 program.
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 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.
Introduction
Automation solutions are configured 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 accept
the project).
This project will be changed over time, errors will be corrected and additions will be
made, for example. If acceptance has to be performed again, the Version Cross
Checker (VXC) can be used as proof of everything that has changed.
One S7 program (current program) and a second S7 program (for comparison) are
selected in the VXC. The comparison is started automatically by selecting the
object for the comparison.
What is compared?
The VXC compares objects (including all objects contained within) and their
attributes and displays the differences in graphical form. This requires that the
objects being compared have already been structured hierarchically or at least can
be displayed in the form of a tree.
The object trees that are compared are processed simultaneously, each object pair
is compared attribute for attribute and assembled in a "results tree" in RAM. The
results tree of the comparison is similar to superimposing two transparencies.
The common comparison results tree is assembled according to the following
rules:
• All objects with the same identity are collected in a node in the comparison
results tree.
• In the comparison results tree, all additional existing objects contained in the
first or second object tree are handled as separate nodes.
A state is displayed in color for each node of the comparison results tree. The
following information can be derived from this color coding by comparing the object
attributes:
• The object is in the first and second object tree (identity) / only in the first or
only in the second object tree.
• Both objects (with the same identity) are identical / different.
• The objects contained within the two objects (with the same identity) are
identical / different.
Further information
• Online help for VXC
Procedure
1. Select the menu command Start > SIMATIC > STEP 7 > VXC – Compare
Versions.
Result: The SIMATIC Version Cross Checker is started.
2. Select the menu command File > Open....
3. Select the desired object type in the "Open" dialog.
4. Click on the "Browse..." button and open the original project.
5. Select the desired object. The VXC reads the selected object including all of
the objects within and displays it.
6. Select the menu command File > Compare with...
7. Open the changed project and select the desired object. The VXC reads the
second selected object including all of the objects within and compares it to the
first selected object.
The two objects are superimposed in a comparison tree. The deviations are
displayed with color coding.
8. Navigate in the hierarchy or detail window to the objects for which you require
detailed change information.
9. If you only wish to see specific objects, select the menu command Options >
Filter and set the filter as needed.
10. Select the menu command View > Filter on/off.
This activates the filter.
11. Print and/or export the comparison results.
Update
If the project data has been changed in the meantime with a PCS 7 application,
you can update the comparison data. To do this press the function key "F5" or
select the menu command View > Update.
The VXC then deletes the internal management structures and reads both objects
again - including all of the objects contained within - and performs a full comparison
of the objects one more time.
Printing
You can print the differences found in the comparison (menu command: File >
Print Differences...).
• All objects also contained in a project are printed on one sheet.
• All differences between objects are printed on another sheet.
Further information
• Online help for VXC
Caution
Be sure to make a backup copy of your project.
You should keep at least five older backup copies of the project. If there is a
network failure, hard disk crash or network disruption, you can always revert to a
backup of your project.
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 (such as a Zip disk).
If parts of the multiproject are stored on network drives, you can use the following
file compression tools to create an archive for multiproject data:
• PKZip
• ARJ32
• JAR
Procedure:
1. Select the multiproject in the SIMATIC Manager.
2. Select the SIMATIC Manager menu command File > Archive.
3. Confirm the selected multiproject in the subsequent dialog and click "OK".
4. In the next dialog, select the name and path of the archive and the archiving
program (for example, PKZip)
5. Confirm the dialog with "Save".
Further information
• Online help for SIMATIC Manager
• Manual Process Control System PCS 7; Service Support and Diagnostics
Procedure
1. Select the SIMATIC Manager menu command File > Retrieve.
2. In the next dialog, select the multiproject archive.
3. Confirm the dialog with "Open".
4. In the "Select destination directory" dialog that appears, select the target
directory for unpacking the archive files.
5. Confirm the dialog with "OK".
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.
Note
All directories are located on the same level below the destination directory
following retrieval.
Further Information
• Section "Requirements for Compiling and Downloading"
• Online help for SIMATIC Manager
• Manual Process Control System PCS 7; Service Support and Diagnostics
Recommendation
Save various project states.
You should always perform a backup:
• After changing the configuration
• Before and after upgrading system components
• Before and after upgrading configuration software
Further 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.
11.2 Documentation
Overview
Once you have created a project, the entire mass of project data must be
documented clearly to allow an overview of the whole system. 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 allows the project data to be structured flexibly in
standardized technical documentation that can then be printed in a uniform format.
Further information
For more information, refer to the manual DOCPRO; Creating Documentation and
the DOCPRO online help.
Introduction
DOCPRO can generate documentation to an electronic manual (PDF format).
There is no automatic conversion function in PCS 7!
Requirement
To perform this task, you require a full license for the Adobe Acrobat program from
Adobe Systems Incorporated.
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 using the print to file option in
the Windows Print dialog.
3. Open the Acrobat Distiller and drag all the files created by DOCPRO from the
Explorer to the Distiller.
The Distiller then creates a PDF file for each individual 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 Help menu command.
Further information
• Manual DOCPRO; Creating Documentation
• Online help for DOCPRO
Maintenance Station
With the maintenance station, PCS 7 allows you to call up information on the status
of all PCS 7 components in hierarchically structured diagnostic pictures. The data
of a component is analyzed with the existing online functions of the corresponding
tool. From within the diagnostic pictures, it is possible to access the ES data (can
be controlled by protection mechanisms).
Pictures for process control diagnostics can be generated automatically for the
entire plant and made available graphically on the maintenance station. The
highest level is a picture with an overview of the entire plant.
Requirements
• The cross-project consistency check was successful (for example names of the
S7 programs unique throughout the multiproject)
• Block from a PCS 7 library V6.1 or higher were used.
• The module drivers were generated and interconnected with the signal-
processing blocks in the CFC charts.
• The diagnostic blocks were set to "OCM possible".
• In the settings in the PH; the option "Derive diagnostic pictures from the plant
hierarchy" was activated.
Diagnostic Options
Area Components
PC stations Operator stations
Archive server
WinAC slot
Industrial PC
Standard PC
Automation Systems CPU
External I/Os, such as ET 200M, ET 200S, input and output
modules
HART Modules
Third-party components
Network Ethernet components such as ESM, OSM
PROFIBUS components DP interfaces
Redundancy Master standby configurations
Additional information I&M information, such as MLFB, name, identification
number
Further 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; Operator Station Process
Control.
ss
Modem Modem
Further information
For more detailed information on working with PC-Anywhere, refer to the manual
Process Control System PCS 7; Service Support and Diagnostics.
Further information
In the Manual Process Control System PCS 7; Service Support and Diagnostics,
you will find a detailed description of the further diagnostic options available with
PCS 7 and what to do if service becomes necessary.
This manual contains information that supports in the following situations:
• When taking measures to ensure the availability of a PCS 7 plant.
• When 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.
Overview
This appendix contains information about the following topics:
• Installation Guidelines for PCS 7
• Lightning Protection
• Electrical Installation
• Basics of EMC-Compliant Installation of PCS 7
• Degrees of Protection (Housing Protection)
Introduction
The installation guidelines must be followed to ensure correct operation of a PCS 7
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).
Introduction
The configuration method is largely determined by the components used in
SIMATIC PCS 7:
• Operator stations
• SIMATIC NET (Fast Ethernet, 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 I/O.
Note
ET 200M is used as an example of distributed I/O in the following. Refer to the
relevant product manuals for more information about installing other ET models.
Cabinet installation
The cabinets made up of system and I/O units and modules that do not belong to
the system (basic cabinets, supply units and optional packages) provide reliable
protection against unauthorized manipulation, 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 SIMATIC PCS 7 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 SIMATIC PCS 7 system consisting of the system units, I/O
units, basic cabinets, power supply units and optional packages are CE compliant.
This means that the cabinets and the SIMATIC PCS 7 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 (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 a plant or
system. Normally, however, only signal and bus cables in the vicinity of
transformers and signal and telecommunication lines are at risk.
The lightning protection for a process control system can be roughly divided into
external and internal lightning protection.
Further information
The rules for bridging the interfaces between the lightning protection zones and a
sample circuit for networked SIMATIC 400 stations are explained in "S7-400
Programmable Controllers; Hardware and Installation".
Introduction
To operate correctly, PCS 7 components depend to a large extent on adherence to
certain rules regarding electrical installation. This involves the following aspects:
• Equipotential bonding (VDE 0100)
• Grounding
• Overvoltage protection
• Shielding
• Cabling
Equipotential bonding
According to 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 must be installed directly on the inductor.
Shielding
Cables are shielded to reduce the effects of magnetic, electrical, and
electromagnetic disturbances on the cables. The interference currents induced in
the shields are discharged direct to ground via low-impedance connections.
Braided shields are preferred to foil shields since foil shields can be damaged
easily, reducing the efficiency of the shield. Grounding shields via long, thin wires
also makes the shield ineffective. Due to the high inductance, interference currents
cannot flow to ground.
If the shielding effect of the cable shield is inadequate, the cables should be pulled
into metallic conduits that are grounded at both ends.
With high-frequency disturbances, it is advisable to contact the shield at both ends
of the cable, whereas for low-frequency interference, the shield should be
contacted at the start or end of the cable. The effectiveness of the shield with low-
frequencies is determined by the ohmic resistance (shield cross section), while with
high frequencies the inductance and therefore the structure of the sheath (closed
conduit better than braid etc.) decides the effectiveness.
To prevent coupling in magnetic fields, shields should, whenever possible, be
connected to an equipotential bonding system at both ends. Indoors, this is often
not done due to fears of violating specifications for the current load on the foil
shields that can be caused by power-frequency interference currents.
Grounding both ends of a shield is not permitted when strong magnetic inference
fields are present (generators, conductor bars). Connecting the shields at both
ends would form a loop into which power-frequency interference voltages could be
coupled.
To avoid the effects of induced voltages resulting from magnetic fields, signal
cables are twisted. The twisting results in a positive induces voltage in one half of
the twist and a negative voltage in the other. These voltages cancel each other out
over the length of the full twist.
Transmitter Receiver
L+
usually
Signal cable
impermissible
L-
Transmitter Receiver
L+
L-
L-
L-
L-
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.
• 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.
Cabling
The aim of cabling is to reduce the field of interference current between the culprit
and the signal cable to a minimum by laying the cable directly on the conductor
carrying the interference current.
Signal and bus cables should be laid next to cables with a large diameter since the
field strength is lower here than with cables with a smaller diameter.
If the conductor carrying the interference current is a plate (for example belonging
to the building structure) lay the signal cable in the middle of the plate where the
field strength is at its lowest. The cable should be fixed to the side of the plate with
the least noise. This also applies to angles and girders.
Field lines
Cable
Field lines
Cable
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 no interference carrying part of the
equipotential bonding system is within 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.
Further information
For more detailed information on the electrical installation, refer to the installation
manual S7-400 Programmable Controllers; Installation and Hardware.
Introduction
Measures to counteract noise are usually only taken when the system is already in
operation and problems are encountered receiving signals.
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 installation and possible sources of noise identified.
Mechanisms
Interference arising from various coupling mechanisms can affect the PCS 7
system. The type of coupling mechanism depends on the distance between the
source of the interference and the PCS 7 system and the transmission medium.
Further information
For further information about plant installation, refer to the manual S7-400
Programmable Controllers; Installation and Hardware.
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
@PCS 7 3-62, 3-64 Backup 11-3
interfacing to the IT world 3-62 Balanced signal circuits 13-7
Basic Concepts of Engineering 5-1
A Basic configuration 4-1, 7-11
configuring hardware 7-11
Access to the PCS 7 OS over Web Client in PCS 7 process cells 4-1
3-65 Basics 7-104
Acknowledgment concept 5-26 BATCH stations 7-15, 7-16
Acknowledgment-triggered reporting (ATM) configuring 7-15
5-29 inserting 7-15
Acknowledgment-triggered reporting (ATR) Block 7-48
7-125 setting the language 7-48
Acoustic signaling 5-30 Block icons 5-23, 7-49
acoustic signaling device 5-30 creating/updating automatically for OS
Additional PH Functions in a Multiproject pictures 7-49
7-34 generating block icons and operator texts
Adopting the data from the plant 5-23
engineering 7-266 Block type 5-11, 5-12
Advantages and uses of SFC charts and Blocks 7-45, 7-165, 7-166
SFC types/SFC instances 7-209 inserting in CFC charts 7-165
Archiving 11-1 project-specific adaptation 7-45
archiving/documenting 11-1 Blocks for 7-188
AS 3-71, 3-78, 3-79, 3-80, 3-81, 3-85, different connection types 7-188
4-12, 7-10, 7-87, 7-185, 7-186 FDL
components 3-71 ISO/TCP connections 7-188
configring SIMATIC stations 7-10 FMS connections 7-188
configuration 4-12 S7 connections 7-188
configuration of fail-safe systems 7-87 Braided shields 13-7
configuration of fault-tolerant systems Branching and merging charts of a project
7-87 5-8
configuring runtime measurement 7-185
fail-safe components 3-79
C
fault-tolerant components 3-77
possible uses in H systems and F Cable laying 13-6
systems 3-85 Cable shielding 13-6
AS functions 7-153, 7-157 Cable shielding at cabinet inlet 13-6
configuring 7-157 Catalog profile 7-66, 7-67
configuring cross-AS functions 7-153 defining for specific projects 7-66
ASI-BUS 3-56 Central
interface into PROFIBUS DP 3-56 plantwide engineering 5-1
Assembly instructions 4-16 CFC charts 7-179, 7-181, 7-183
special features compiling 7-180
differences 4-16 download to the CPU 7-181
Assigning objects in the PH 7-31 testing 7-183
Assignment 7-27
ATR 7-125
How to assign an import file to the process How to Export a Station Configuration
tag type (create an import file) 7-200 7-292
How to Assign Parameters and How to find 3-3
Interconnect the Blocks 7-167 systems to use 3-3
How to assign symbols to input and output How to Generate Module Drivers 7-193
addresses 7-77 How to Import an Expanded Import File
How to change 7-122 (Extra Remote I/O
parameter settings of a channel 7-122 Field Device
How to check 7-32, 7-138 Module) 7-298
consistency of the network 7-138 How to insert 7-7, 7-10, 7-12, 7-28, 7-74,
consistency of the PH 7-32 7-75, 7-165
How to compile 7-179 blocks in a CFC chart 7-165
CFC charts 7-179, 7-181 communications processors in the
How to configure 7-95, 7-96, 7-101, 7-144, stations 7-12
7-215, 7-216, 7-218 first import of an entire station 7-297
communication between two SIMATIC modules in a SIMATIC station 7-73
stations 7-144 objects in a hierarchy folder 7-28
diagnostic repeater 7-96 project in a multiproject 7-7
HART devices with SIMATIC PDM 7-101 SIMATIC stations in the projects of the
PA devices 7-95 multiproject 7-10
sequencer properties 7-215 How to lock 7-47
SFC steps 7-216 message attributes against changes in
transitions 7-218 the block instance 7-47
How to configure and download the PC How to make the settings for the PH 7-25
stations 7-18 How to merge 7-155, 7-311, 7-312
How to create 7-195 cross-network connections 7-155
your own driver blocks 7-195 cross-project connections 7-312
How to create a master data library 7-41 cross-project networks in a multiproject
How to Create a New SFC Chart 7-212 7-311
How to create and assign parameters How to modify 7-45, 7-136, 7-198, 7-228
7-135 a process tag type 7-198
a network attachment 7-135 attributes of the block I/Os 7-45
new subnet 7-134 SFC types centrally 7-228
How to create and assigned parameters the node address 7-136
7-134 How to move 7-63, 7-310
How to create your own blocks 7-49 projects edited on distributed stations to
How to Define CFC Chart I/Os 7-177 the central engineering station 7-309
How to display 7-133 projects to distributed engineering
networked stations 7-133 stations 7-62
non-networked stations 7-133 How to program the SIMATIC connections
How to document library objects 7-56 7-189
How to download 7-126, 7-127, 7-181 How to remove a project from the
CFC charts to the CPU 7-181 multiproject 7-8
configuration changes in CPU-RUN How to retrieve a multiproject 11-3
7-127 How to save 7-137
configuration to the CPU 7-126 network configuration 7-137
How to edit 7-64, 7-251, 7-254, 7-257, How to set 7-4, 7-90
7-259, 7-261 defaults 7-4
measured value archives 7-261 time-of-day synchronization
messages 7-257 on the AS 7-90
parameters 7-251 How to specify the AS-OS assignment
picture objects 7-260 7-30
projects on distributed stations 7-64 How to store shared declarations 7-9
signals 7-254 How to Store the Projects of the
How to Edit the General Data 7-249 Multiproject 7-61
How to Expand a Project by Adding Further How to test 7-56, 7-183, 7-234
Components 7-8 CFC charts 7-183