ST Pcs7sys

1 Introduction
2 PCS 7 Documentation and Support
Requirements and functional process

3
description
System design and component

4
specification
SITRAIN
Training for Industry 5 Project setup
6 Station and network configuration
SIMATIC PCS 7 7 Connection to the process

System Course
8 Basics control functions
Course ST-PCS7SYS
9 Basics Operating and Monitoring
10 Basics Automatic Mode Control
11 Customizing the OS
12 Archiving System
Name:
13 Locking functions and operating modes
Course from: to:

14 Mass data engineering
Trainer:
15 Final steps of configuration

Training site:
This document was produced for training purposes. 16 User block – attributes and visualization
SIEMENS assumes no responsibility for its contents. The
reproduction, transmission, communication or use exploitation
of this document or its contents is not permitted without
express written consent authority. Offenders will be liable to 17 Demonstration Server-Client System
damages. Non-compliances with this prohibition make the
offender inter alia liable for damages.
Copyright © Siemens AG 2011. All rights, including

particularly the rights created by to file a by patent and/or 18 Syntax Rules
other industrial property right application and/or cause the
patent and/or other industrial property right to be granted
grant or registration of a utility model or design, are reserved.
19 Exercises
SITRAIN courses on the internet: www.siemens.com/sitrain
Course folder Version: V8.0 (for PCS 7 Version 8.0) 20

PCS 7 System Course
Content 1
1 Introduction ............................................................................................................. 3
1.1 Learning targets (this chapter)................................................................................................3
1.2 Concept of this course ............................................................................................................3
1.3 Road map of this course.........................................................................................................4
1.4 Additional documentation .......................................................................................................4
1.5 Training equipment .................................................................................................................5
1.6 Access to systems of other students ......................................................................................5
SIMATIC PCS 7 – Introduction

Training Documentation, V1.00, ST-PCS7SYS 1-1
PCS 7 System Course

1-2 Training Documentation, V1.00, ST-PCS7SYS
PCS 7 System Course
1 Introduction
1.1 Learning targets (this chapter)
The participant will learn about

• The general way this training is
running
• The difference between workflow
of real-life PCS 7 configuration and
the workflow in this training
1.2 Concept of this course
General workflow of a PCS 7 project This course
Text
Lists Requirements You create your own
Diagrams Automation of a plant with training project following
4 reactors predefined tasks during
Functional process the course
description
independent from PCS 7 System design Decentralized Process Control Determined by the available
System based on SIMATIC PCS 7, training equipment
using 1 ES/OS, 1 AS with
distributed I/O and Industrial The process behavior is
depending on PCS 7 simulated in the CPU of
Component specification Ethernet as System Bus
the AS
Hardware and Software

Configuration and Implementation
programming
Tasks on different levels using the Getting familiar to the
Test main components of the SIMATIC Engineering Tools by
PCS 7 Engineering Toolset explanations and examples
Commissioning
Including In brief, is main subject to the

Maintenance
optimization PCS 7 service course

PCS 7 System Course
1.3 Road map of this course
First week Second week

Setting up the multiproject Customizing the OS
Creation of the stations and basic framework User administration, Time synchronization,
Dynamization of process pictures, Alarms
Setting up the automation system and operator station

Station Configuration for ES/OS and AS Archiving system
Distributed periphery connected by Profibus and Profinet Alarm and tag logging, WinCC Controls
Connection to the process Locking functions and operating modes

Basics of the automation of the connected Signal box Interlocks, Local mode, Evaluation of signal status
Drivers, charts and test of the signals
Process simulation for the training project Mass data engineering
Creation of the Plant Hierarchy Multiplying process tags with the import export assistent
Basics of automation with APL

Final steps of configuration
Creating the basics of automation for a part of the plant
Communication between automation systems
Configuration changes during operation using CiR
Forcing on ES level
Basics of Operating and Monitoring Block simulation also on the operator level
OS-AS connections
Creating the OS
Creation of user blocks
Block Attributes and visualization
Implementing manual and auto mode control
Controlling the operating mode Demo Multiproject with multiple station OS
Creating a sequential control AS, ES, OS Server / Clients
1.4 Additional documentation

Additional to this training manual you will have available a selection of the current
system documentation. References are made using the number in brackets.
Example:
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 2.1.2 for more details
Below you find the way the available documentation is represented

PCS 7 System Course
1.5 Training equipment

Equipment is made available for practicing to support you in getting familiar to the
system.
SITRAIN expects you to use the equipment for that reason only.
The use of external storage devices (memory stick etc.) or disks is only allowed with
permission of the trainer.
1.6 Access to systems of other students

A local network allows you to have access to PC and AS of other students.
Please, only do so with permission of the related persons.

PCS 7 System Course
Content 2
2 PCS 7 Documentation and Online Support........................................................... 3
2.1 Learning target........................................................................................................................3
2.2 Documents available by PCS 7 Installation............................................................................3
2.2.1 Delivered Manuals ..................................................................................................................3
2.2.2 Delivered Readme Files .........................................................................................................4
2.2.3 PCS 7 help system .................................................................................................................5
2.2.4 Template for a plant-specific process control manual for operators.......................................6
2.3 Additional sources of information............................................................................................7
2.3.1 PCS 7 Compendium ...............................................................................................................7
2.3.2 PCS 7 on Tour (PoT) ..............................................................................................................8
2.3.3 PCS 7 Catalogs ......................................................................................................................9
2.3.4 PCS 7 in internet...................................................................................................................10
2.4 Industry Online Support Internet Portal ................................................................................11
2.4.1 Product Support....................................................................................................................12
2.4.2 Applications & Tools .............................................................................................................13
2.4.3 Multimedia-based Demonstration Systems ..........................................................................14
2.4.4 Compatibility Tool .................................................................................................................14
2.4.5 Services ................................................................................................................................15
2.4.6 Marketing Information ...........................................................................................................16
2.5 Functions of the Industry Online Support Internet Portal .....................................................17
2.5.1 Search...................................................................................................................................17
2.5.2 mySupport.............................................................................................................................18
2.5.3 My Documentation Manager.................................................................................................18
2.5.4 Online Support App (for Apple and Android Smart Phones) ................................................20
2.6 Communication in the Industry Online Support Internet Portal ............................................21
2.7 Checkpoint ............................................................................................................................23
SIMATIC PCS 7 – Documentation and Online Support

PCS 7 System Course
SIMATIC PCS 7 –Documentation and Online Support

PCS 7 System Course
2 PCS 7 Documentation and Online Support

2.1 Learning target

• What types of PCS 7
documentation are available
• Navigation through the Industry
Online Support
• All functions and possibilities of
the Industry Online Support
2.2 Documents available by PCS 7 Installation

2.2.1 Delivered Manuals
The PCS 7 Readme File “pcs7-readme.rtf” contains in section 2.1 “General information”
a complete overview list with PCS 7 Manuals locally available after PCS 7 installation.
Pathways to installed manuals

Once you have installed PCS 7 including the PCS 7 documentation on your computer,
you can open this documentation with
Start > SIMATIC > Documentation > English

PCS 7 System Course
Manuals on SIMATIC PCS 7 DVD

If you do not wish to install this documentation, you can also view it at any time on the
SIMATIC PCS 7 DVD in the following folders:
"_Manuals\English" or "_Product_Information\English".
All the manuals are stored in PDF format. You require Acrobat Reader to open the files.
If necessary, you can install it from the SIMATIC PCS 7 DVD.
 Programming Instructions for creating driver blocks and with the title "SIMATIC
Programming Instructions Driver Blocks" can be ordered separately. These
Programming Instructions help the advanced SIMATIC PCS 7 user to create system-
conform driver blocks, which can be placed like standard blocks on system plans and
automatically parameterized and interconnected in HW Config.
2.2.2 Delivered Readme Files
Pathways to installed Readme files

Once you have installed PCS 7 including the PCS 7 documentation on your computer,
you can open any Readme file with
Start > SIMATIC > Information > English
Reason to have attention to the Readme files
 ATTENTION
Each of the PCS 7 related products come with product-specific information in the
form of readme files.
Readme files contain information which is not included in manuals due to the degree
of topicality.
The information given in Readme files takes precedence over all the PCS 7 manuals.

PCS 7 System Course
pcs7-readme.rtf
• Most important Readme file of PCS 7
• Containing information also relevant before PCS 7 installation:
− Licensing of software to be installed
− Hardware pre-requisites and compatibles
− Software requirements regarding the operating system or system settings and the
software to be installed
− Compatibility to 3rd party products (software)
− Required installation steps/ required upgrade steps
− Basic information for update of PCS 7 projects
− Notes on usage of the product
− Summary of changes compared to the former product version
pcs7sysdocu-readme.pdf
• Contains information and additions to the manuals of the PCS 7 system
documentation with higher topicality due to the deadline for generation of electronic
manuals.
• Known misprints in delivered manuals are cleared here.
pcs7new.pdf
• “What’s new in PCS 7?” contains an extract of all new features and changes in the
current PCS 7 version.
• Summarized information given in first section “What’s new” in each product /
operation manual.
2.2.3 PCS 7 help system
Implementation of the PCS 7 help system

The PCS 7 help system, which can be called from SIMATIC Manager, will be updated
regularly as of PCS 7 V8.0. Service packs for PCS 7 and the products in the system
documentation will also be compiled and published.
You have to implement the PCS 7 help system manually in the PCS 7 installation with
copy and paste as follows:
1. Download the zip files of the help system from the Service & Support portal by
clicking .
2. Unzip the help files into a folder.
3. Copy all help files into the folder Siemens > STEP7 > S7BIN in the PCS 7
installation.
When you open the PCS 7 help system again, it will be updated.

PCS 7 System Course
Access to PCS 7 System documentation by online help

Since PCS 7 V6.0 SP3, you can also open the complete system documentation for PCS
7 in the online help format within the SIMATIC Manager through the help topics.
• You can open the "PCS 7 Basic Documentation" online help with the menu command
“Help > Topics in the SIMATIC Manager.”
2.2.4 Template for a plant-specific process control manual for operators

You can create a process control manual for the operator derived from a source
document of the actual PCS 7 OS Process Control Manual.
 „PCS 7 - Operating Instructions Operator Station Process Control.doc “

 Derived from a source document of the actual PCS 7 OS Process Control Manual
 Covering the well-proven main structure of a control manual for operators
 Available in the "_Manuals\<language*>" folder on your PCS 7 Toolset DVD.
(* Select your regional <language>.)
 Edit the source document with MS Word

PCS 7 System Course
2.3 Additional sources of information

2.3.1 PCS 7 Compendium
Subject of the manual

On the one hand:
• SIMATIC PCS 7 is as a distinctly open system to be flexibly adapted to a wide range
of customer needs.
• Great deal of freedom in terms of the project configuration, as well as in the design of
the program and the visualization.
On the other hand:
• Experience has shown that subsequent modernization or plant expansion work is
made much easier if the project is configured "in conformance with PCS 7" as far as
possible right from the start.
• Certain basic rules absolutely must be adhered to in order to ensure that the system
functions provided will offer optimum usability in the future.
The compendium directly reflects the recommended method for configuration, which is
based on the results of a great deal of practical experience. The description does not
cover the application itself; rather, it relates to handling the project and the parameter
settings of the components it contains.
Links to the Compendium

The compendium is divided into several parts:
• Part A: Configuration Guidelines
http://support.automation.siemens.com/WW/view/en/35016996
• Part B: Process Safety
• Part C: Technical Functions with SFC Types
• Part D: Operation and Maintenance
• http://support.automation.siemens.com/WW/view/en/43410843
• Part E: IT Plant Security (coming soon)
• Part F: Hardware Setup (coming soon)

PCS 7 System Course
You can download the documents on the website of SIEMENS Industry Automation and
Drives Technologies Service & Support, product support. Search for “Compendium” as
shown in the figure below.
2.3.2 PCS 7 on Tour (PoT)
Subject of the manual

PCS 7 on Tour is a compact manual with the intend to provide fundamental basics on
the system functions and an approach to engineering and configuring automation tasks.
It covers major components (hardware and software) of the system and intends to
deliver a systematic approach right from the start when you begin to know or use the
system.
Link to supplier
The manual PCS 7 on Tour can be ordered via the Siemens Sales Support Process
Automation I IA AS S SUP PA. Please contact your local Siemens promoter or sales
department.
The manual is in the following languages available:
German, English, Spanish, Portuguese, French (coming soon)

PCS 7 System Course
2.3.3 PCS 7 Catalogs

The catalogs list those products of the Siemens automation product spectrum which are
released for the process control system SIMATIC PCS 7.
The products contained in this catalog can also be found in the e-Catalog CA 01.
Catalogs are available in print and for download on the Product Support Portal.
Industry Online Support New Website:
Navigate in the
product tree to
SIMATIC PCS 7
SIMATIC PCS 7 Standard catalog ST PCS 7 for V8

The catalog lists the PCS 7 hardware and software products structured in following
sections:
Industrial Workstation, Engineering system, Operator system, Maintenance Station,
Automation systems, Communication, Process I/O, SIMATIC PCS 7 Software and,
System documentation, Technology components, Batch automation, Route control,
Safety Integrated for, Process Automation, IT Security, Connection of IT systems, Other
Compact systems, Basic Packages, Previous versions, Update/upgrade packages
The products are introduced by detailed descriptions and specifications.
Catalog ST PCS 7.1, Add-ons for the SIMATIC PCS 7 Process Control System
Many supplementary add-on products for SIMATIC PCS 7 have been developed by
Siemens as well as by external partners. These software packages and hardware
components authorized by the system manufacturer enable cost effective
implementation of SIMATIC PCS 7 for special automation tasks.
Catalog ST PCS 7.2, Migration solutions for the SIMATIC PCS 7 process control system.
The migration of own process control systems to SIMATIC PCS 7 is a matter of course
for Siemens, and a significant component of the continued supplier/ customer
relationship. Siemens is additionally able to offer migration solutions for process control
systems from other vendors.

PCS 7 System Course
2.3.4 PCS 7 in internet
Link to PCS 7 Website

The PCS 7 site provides convenient access to the complete PCS 7 documentation – the
latest news about hardware and software components released for PCS 7:
http://www.siemens.com/simatic-pcs7
Get into the world of SIMATIC PCS 7 with the interactive system overview.
The PCS 7 portal contains links also to following sections:

• Presales information
• Online catalog and ordering system
• Technical information
• Support
• Training
• Contact & Partners (Local and Solution partners)

2 - 10 Training Documentation, V1.00, ST-PCS7SYS
PCS 7 System Course
2.4 Industry Online Support Internet Portal
Guided Tour
You are here for the first time or you would like to get to know all functions and
possibilities? Then you are right at the "Guided Tour":
http://support.automation.siemens.com/support/GuidedTours/start.htm?lang=en
Overview
The Online Support offers you a comprehensive information system for all Industry
Automation and Drive Technologies Service & Support subjects at any time.
Do you wish to extend your Know How, read up on services or exchange experiences
with users of automation systems?
Convenient functions in the online support lead you directly to the desired information.
Online Support always the first step - around the clock on 365 days of the year.
http://support.automation.siemens.com

Training Documentation, V1.00, ST-PCS7SYS 2 - 11
PCS 7 System Course
2.4.1 Product Support

The "Product Support" provides a wide range of all information concerning the products
and solutions of Siemens Industry Automation and Drive Technologies:
What does "Product Support" offer you?
• FAQs
• Updates/Upgrades, Service Packs & Support Tools for downloading
• Manuals and operating instructions
• Approvals and certificates
• Test certificates and curves

PCS 7 System Course
Example of a product view of SIMATIC PCS 7 V8.0

2.4.2 Applications & Tools

"Applications & Tools" supports you with functional and non-branch-specific solutions.
The main focus is not only on the individual product but on the interaction of the entire
system.
Your advantages:
• Realization reliability
− Functional solutions for defined tasks
− Creative ideas for further customer-specific applications
• Planning reliability
− Verified communication times
• Saving time
− Program examples can serve as a basis for your individual user program
− Compact presentation of the underlying technological principles
− Entries are tested and free of charge
Application Examples to SIMATIC PCS 7:
http://support.automation.siemens.com/WW/view/en/20806759/136000

PCS 7 System Course
2.4.3 Multimedia-based Demonstration Systems

A demonstration system is an automatically running or interactive operable animation.
Complex technical contexts, products, functional correlations and user instructions are
presented as Flash films.
This enables you to expand your know-how quickly, conveniently and easily.
http://support.automation.siemens.com/WW/view/en/34677186/136000&cspltfrm=0&css
w=0&csbinh=7
2.4.4 Compatibility Tool

The compatibility tool allows you to put together a compatible selection of software
products or to check the compatibility of the existing configuration.
https://support.automation.siemens.com/kompatool/pages/main/index.jsf

PCS 7 System Course
• Workflow through the Compatibility Tool:
Product tree
also for 3rd
party products
• Result:
2.4.5 Services
The service covers all areas of the product life cycle. We offer you the appropriate
service - starting from planning a plant up to its modernization and optimization.
Your advantages:
• Clear presentation of all services according to product life cycle
• When using the tree structure, you can find our service offers topic-related
• The index enables an alphabetic search for important service terms
• Always the latest information on the service

PCS 7 System Course
2.4.6 Marketing Information

To give you an overview of the performances, facts & figures and processes of Service
& Support in the worldwide network, we have put several advertising brochures at your
disposal.
Your advantages:
• Fully edited advertising material for your presentations
• Clear arrangement of all Service & Support performances
• A concise summary of marketing arguments for facilitating your own marketing

PCS 7 System Course
2.5 Functions of the Industry Online Support Internet Portal

2.5.1 Search
The Industry Online Support offers three different functions for your search. Additionally
there are filtering functions, search in hit lists and further functions available.
Free Text Search Navigation in the tree structure Alphabetic Index
• Free Text Search: When searching via free text, the complete Portal will be searched
according to the entered term. The employed search algorithm can automatically see
similar or related terms.
− Product designation
− Order number (MLFB)
− Entry-ID
− General Terms
• Alphabetic Index: When looking for firmly defined terms, the alphabetic index will
support you.

PCS 7 System Course
2.5.2 mySupport
To provide a better overview and to make the use easier, all your personal data and
information is summarized in a separate area.
• Creating of new and viewing of existing queries to the Technical Support via Support
Request
• Subscribing to and changing Service & Support Newsletter
• Changing or supplementing personal data (e.g. e-mail address)
• Calling My Documentation Manager to compile personal documentation
• Personal functions from the Technical Forum (e.g. personal messages)
• Setting up of navigation filters – with myTree
To the free registration:
2.5.3 My Documentation Manager

My Documentation Manager (MDM) offers you to compile your own documentation from
our standard documents (manuals) available in the Product Support section.
Documentations compiled in one language can easily be output in any other language
available in the system.
Function
In the My Documentation Manager you may define a customized structure for the
storage and management of your compiled documents. The following steps provide you
with a quick and easy introduction to the My Documentation Manager.

PCS 7 System Course
Main steps
1. Select a document - All manuals available in the Product Support section and
marked as "Manuals/Operating Instructions, configurable" are suitable for
processing with My Documentation Manager. You can find these manuals also by
using the search function and selecting "Manuals/Operating Instructions ->
Configurable documents only".
2. Retrieve a document in the My Documentation Manager - Click the "Display and
Configure" link in the relevant manual entry to open the My Documentation Manager
and to add this manual to the "Last visited" selection list.
3. Create/extend your own library - In the middle part of the My Documentation
Manager (my library) you may create your own folders (by clicking this area with
your right mouse button) or delete and rename previous folders. These folders
correspond to the relevant chapters of your individual compilation (library).
4. Transfer selected manuals into your individual compilation - Now you can "drag &
drop" (click and drop with your mouse) selected manuals from the "last visited" list
to your own folder tree (library).
5. Export - In your individual library, you may export selected manuals in different
formats (PDF, XML, RTF) and to any desired destination. To do so, click the
function "Create generation output" with your right mouse button at the relevant
position in your library.
Link
https://www.automation.siemens.com/mdm/default.aspx?GuiLang=en
User registration is required to use the full range of functionality offered by the
Automation and Drives Web.

PCS 7 System Course
Example: PCS 7 V8.0 Manual Collection within the MDM

2.5.4 Online Support App (for Apple and Android Smart Phones)
The Online Support App enables you to access more than 300,000 documents on all
Siemens Industry products, anywhere and anytime. No matter whether you face
problems implementing your project, need help with troubleshooting, want to expand
your facility or newly plan one.
You have access to FAQs, the latest firmware or software version downloads, manuals,
certificates, characteristic curves, application examples and tools, product news (e.g.
announcement of new products), information on successor type in case of product
phase-outs.
To the overview:

PCS 7 System Course
2.6 Communication in the Industry Online Support Internet Portal
Technical Forum
To complete the comprehensive range we support the direct dialog between specialists.
With the Technical forum you get an attractive discussion platform in German and
English where users and experts can exchange their experience.
https://www.automation.siemens.com/WW/forum
Support Request
You can send your request directly from the Internet to a specialist in Technical Support.
What does the “Support Request” offer you?
• Solution suggestions from the Online Support before sending your request.
• Adoption of your personal data already provided in the personalization "mySupport".
• Your request is directly forwarded to the specialist in charge.
What are your benefits?
• You can solve your problems even easier using the Knowledge Base on the Internet.
• You can use the "Support Request" around the clock, every day of the year.
• As all relevant data are forwarded directly to the specialist, you will be contacted
even quicker when you make use of the Support Request.

PCS 7 System Course
Own suggestions for FAQ (only available in Intranet)

You came across a problem, solved it and want to share the solution with other users?
So, just post your idea in our FAQ Discussion Board:
https://workspace.automation.siemens.com/content/10004288/default.aspx
Feedback to planned Application examples (only available in Intranet)

On the Application Sharepoint, we will regularly post the planned application topics. We
would appreciate your input and feedback.
• What topics do you consider important, what topics have a lower priority?
• Do you miss any planned applications?
• Would you be able to support us with your know-how or with previously created
solutions?
https://apps02.industry.siemens.com/content/10002594/PlannedApplications/default.as
px
Newsletter
The newsletters inform you precisely of the components and platforms you are
interested in - to the point and free of commercials. Determine for yourself what you
want to be informed about.
Using the newsletter requires a registration under mySupport.

PCS 7 System Course
Twitter
Starting immediately, information on Siemens industrial products and services is also
available via Twitter.
2.7 Checkpoint
Let‘s think about this:

• Name some reasons for
registration in MySupport.
• What do you think is the best way
to have always the latest version
of the required manuals for your
job with you?

PCS 7 System Course
Content 3
3 Requirements and functional process description .............................................. 3
3.1 Learning target........................................................................................................................3
3.2 In brief .....................................................................................................................................3
3.3 Process diagram .....................................................................................................................4
3.4 Functional process description ...............................................................................................5
3.5 Connection to a Signal box.....................................................................................................6
3.5.1 Overview .................................................................................................................................6
3.5.2 Layout .....................................................................................................................................7
3.5.3 Function diagram of digital signals .........................................................................................8
3.5.4 Function diagram of analog signals........................................................................................8
3.6 Checkpoint ..............................................................................................................................9
SIMATIC PCS 7 – Requirements and functional process description

PCS 7 System Course

PCS 7 System Course
3 Requirements and functional process description

3.1 Learning target

• The functions of the plant to be
controlled
• The type of devices that are used
• The features of the Signal box used as
additional training equipment to realize
hardware related process signals
3.2 In brief
Johnsson & Co, a company supplying products for the food industry, wants to
modernize their plant to increase the production to 230 percent in the next 5 years.
Material Tanks Reactors Buffer Tanks
Storage Shipping
Office and
Control Building
Johnsson
& Co
In three stages, with two years between them, the automation system is to be updated
using a scalable decentralized control system.

PCS 7 System Course
This training
The first stage is to cover the grey part in the plant overview above.
Later…
The other parts of the plant are covered in stage 2 and 3.
3.3 Process diagram

Next picture represents the process diagram.
(V131) flow
(V121)
(V111)
Material
M110 M120 M130
LT114 LT124 LT134 Tanks
6000 kg 6000 kg 4000 kg
4s V112 V122 V132

flow
2s P113 P123 P133
V211 V221 V231 V241

0,25 s
V212 V222 V232 V242
V213 V223 V233 V243
LT214 LT224 LT234 Dose LT244
D210 D220 D230 D240
Tanks
flow
4s V311 V321 V331 V341
TT315 200 °C TT325 200 °C TT335 200 °C TT345 200 °C
LT314 CV315 LT324 CV325 LT334 CV335 LT344 CV345

700 kg R310 21 s 700 kg R320 1100 kg R330 1100 kg R340
M316 M326 M336 Reactors M346 steam
2s
ambient
5s V312 V322 V332 V342
2s P313 P323 P333 P343
5s V411 V421 flow
LT414 LT424
12000 kg 18000 kg Buffer
B410 B420 Tanks
(V422)
(V412) flow

PCS 7 System Course
3.4 Functional process description

In four different reactors, up to three components are to be dosed, mixed and heated
up.
Material Tanks M110, M120 and M130

The components are coming from three material tanks, two with a capacity of 6000kg
and a third with a capacity of 4000kg. The outlet to the dose tanks is done through a
valve and a pump for each tank.
The filling and refilling of the material tanks is not part of this project. It is done through
valves, which states are offered to the control system for displaying.
Dose Tanks D210, D220, D230 and D240

Controlling the amounts of the components to be mixed and heated, dose tanks are
used. Dosing is done for one component at a time. The capacity of each of the dose
tanks is 400kg.
A dose tank contains 3 inlet valves, one for each component.
The outlet valve will be the inlet for the related reactor.
Reactors R310, R320, R330, R340

Four reactors are used for mixing en heating the components. R310 and R320 can
contain 700kg each; R330 and R340 have a capacity of 1100kg. The inlet valve is the
same as the outlet valve of the related dose tank.
Each reactor has a single direction, single speed mixer.
Heating is done by steam piping in the inside of the reactor. A control valve is controlling
the steam flow. There is no cooling circuit.
The outlet of the reactors is done through a valve and a pump, with destination one of
the two buffer tanks.
Buffer Tanks B410 and B420

Two buffer tanks, one of 12000kg and another one of 18000kg are there for storing the
product, before it is transferred to the shipping area. Each of the buffer tanks has a inlet
valve.
The transfer from the buffer tanks to the shipping area is not part of this project. It is
done through valves, which states are offered to the control system for displaying.
Operation
• Each of the individual devices in the process is to be monitored and operated
manually by the decentralized control system.
• There must be an automatic mode to optimize the production quantities.
• Every reactor is to be used up to 90 percent of its capacity.
The mixture of the components in percentages and the heating temperature is to be
entered in the system and is valid for the entire production using all reactors.

PCS 7 System Course
3.5 Connection to a Signal box

3.5.1 Overview
Extra to the simulated process to be controlled, a Signal Box is available as a part of
your training equipment:
AS
DI16 AI8
Industrial
Ethernet
S7-400
DO16 AO4
ET 200M
PN DP
Process
signals
Signal Box
Wiring has been made up to the front connector of the IO modules on the DP ET 200M
rack, containing both a digital and analog input and output module.
The signals can be used in various situations in later tasks.

PCS 7 System Course
3.5.2 Layout
The components of the Signal Box have been assigned short names. Initially these
names will be used as the so called “symbolic names”. The names may be modified for
specific use of the signals in later tasks.
Emergency
H1 S1
Off
H2 S2
Display 1 Display 2
H3 S3
Source for Source for

Display 1 Display 2
H4 S4
(AO0 or AI0) AI0 (AO1 or AI1) AI1
Wire break Shortened to M No Power

T1 T3 Relay DI#0 DO#0 DI module
Normally Opened
Relay
T2 T4 Normally Closed
(Relay controlled by DO#0)
• S1 … S4 are switches to be used as operator input for binary input signals.

• T1 … T4 are buttons also to be used as operator input for binary input signals.
• H1 … H4 are lamps indicating binary output signals.
• AI0, AI1 are potentiometers to be used as operator input for analog input signals.
• The displays 1 and 2 are analog measurements indicating analog output signals or
the current input signals as set by the potentiometers.
• The switches below the displays are used to select what the display is indicating: the
analog output or input signal.
• The relay LEDs indicate a valve position simulated by a relay. The relay is controlled
by the digital output signal DO 0.0.

PCS 7 System Course
3.5.3 Function diagram of digital signals

Please do realize: this is not a wiring diagram. This drawing supplies you with an
overview of the digital signals of the Signal Box and their connection to the IO modules.
Digital Output – Output address # (DP ET 200M slot 5)

Q 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7
spare
H1 H2 H3 H4
T1 T2 T3 T4 S1 S2 S3 S4
Relay
Emergency
Off
spare
I 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7
Digital Input – Input address # (DP ET 200M slot 4)
3.5.4 Function diagram of analog signals

Please do realize: this is not a wiring diagram. This drawing supplies you with an
overview of the analog signals of the Signal Box and their connection to the IO modules.
Analog Output – Output address # (DP ET 200M slot 7)

#0 #1 #2 #3
QW 512 QW 514 QW 516 QW 518
AO0 AO1 AO2 AO3
Display 1 Display 2
AI0 AI1 AI2 AI3 spare
#0 #1 #2 #3 #4 #5 #6 #7
IW 512 IW 514 IW 516 IW 516
Analog Input – Input address # (DP ET 200M slot 6)

PCS 7 System Course
3.6 Checkpoint
Let‘s think about this:

• What is the minimum of
information that should be
available in a Process and
Instrumentation Diagram to create
the basic functionality of the
Process Control System?

PCS 7 System Course
Content 5
5 Project setup............................................................................................................ 3
5.1 Learning targets ......................................................................................................................3
5.2 Overview about configuration steps for AS and OS ...............................................................3
5.3 SIMATIC PCS 7 Engineering Toolset.....................................................................................4
5.4 What is a Multiproject? ...........................................................................................................5
5.4.1 Projects and libraries ..............................................................................................................5
5.4.2 Different types of stations .......................................................................................................5
5.4.3 Different types of libraries .......................................................................................................6
5.4.4 Multiproject..............................................................................................................................7
5.4.5 Master Data Library ................................................................................................................8
5.5 Initial settings of SIMATIC Manager .......................................................................................9
5.6 Setting up a multiproject .......................................................................................................10
5.6.1 Organizing a multiproject ......................................................................................................10
5.6.2 Setting up the projects “Step by Step“..................................................................................10
5.6.3 Setting up the project with the „New Project“ Wizard ...........................................................14
5.6.4 Expansion of Multiprojects....................................................................................................16
5.6.5 Multiproject-wide information to be synchronized.................................................................18
5.7 Language for Display Devices ..............................................................................................19
5.8 Archiving and retrieving a project, library or multi project.....................................................20
5.9 Task and checkpoint.............................................................................................................21
SIMATIC PCS 7 – Project setup

PCS 7 System Course

PCS 7 System Course
5 Project setup
5.1 Learning targets

• The main configuration steps for
an automation project
• The role of SIMATIC Manager and
ist relevant settings
The participant will be able to

• Set up a Multiproject for
configuring the training
application
5.2 Overview about configuration steps for AS and OS

Configuration steps AS Configuration steps OS
Select block libraries to be used. Create a new project-
specific library.
Create hardware resources: PC Stations (SIMATIC

Create Multiproject. (SIMATIC Manager) Manager, Component View)
Create hardware resources:SIMATIC S7-400 Stations Configure hardware (SIMATIC Manager, Component
(SIMATIC Manager, Component View) View)
Configure hardware (SIMATIC Manager, Component Basic settings in WinCC Explorer and OS Project Editor
View)
Create Plant Hierarchy Create OS object (SIMATIC Manager, Plant View or

(SIMATIC Manager, Plant View) Process Object View)
Assign hardware resources (SIMATIC Manager) Edit individual objects (WinCC Explorer, Graphics
Designer)
Configure Software (CFC, SFC, SCL, messages, Compile and Downwload OS (SIMATIC Manager)
archive tags)
Test + commissioning (configuration tools) Test + commissioning (configuration tools)
Documentation ( DOCPRO ) Documentation

PCS 7 System Course
5.3 SIMATIC PCS 7 Engineering Toolset

SIMATIC Manager is the central part of the STEP 7 programming and configuring
software for STEP 7 applications. Together with an additional number of tools and
options it is released as the SIMATIC PCS 7 Engineering Toolset.
One way
Using the SIMATIC PCS7 Engineering Toolset is the only way to program and configure
a SIMATIC PCS 7 configuration.
The figure below gives an overview of the main components of the toolset.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 7.7 for more information about
the PCS 7 applications and how they are used.

PCS 7 System Course
5.4 What is a Multiproject?

5.4.1 Projects and libraries
In common
Projects and libraries have some in common. They are:
• an organized amount of data
• stored in a particular folder including files and lower level folders
• managed by SIMATIC Manager and its related tools
Different
Differences between projects and libraries:
• Projects contain the data for at least one station (application specific programmable /
configurable device). Projects contain always hardware-related data.
• Libraries contain predefined functions for being used in projects. These data are
always only software related.
5.4.2 Different types of stations

In a SIMATIC PCS 7 project a station can be:
• A PC (SIMATIC PC Station) for engineering or operating
• An Automation System (SIMATIC 400 Station)
Windows Network ( TCP/IP )
Terminal Bus
ES (PC) Engineering System ( ES )
OS OS
(PC with WinCC) (PC with WinCC) Operator System ( OS )
Industrial Ethernet
System (Plant) Bus
AS AS
(S7-417-4) (S7 414-3) Controller ( AS )
Stations
PROFIBUS-DP
Field Bus
IM DP (ET 200M) IM DP (ET 200M) Distributed I/O
Sensors and
actuators

PCS 7 System Course
5.4.3 Different types of libraries

Libraries are used for storing reusable program components. The program components
can be copied to a library from existing projects or created directly in the library
independently of projects.
Standard frame of delivery of SIMATIC PCS 7 V8.0 PCS 7 BRAUMAT PCS 7

CEMAT
Standard installation of Optional PCS 7
SIMATIC PCS 7 V8.0 installation Water Library
PCS 7 PCS 7 Advanced PCS 7 Library PCS 7
Basic Library Process Library (Standard) Industry Library Customized
Libraries
Control Control Control
@System Driver Channel

AS blocks
Faceplates/
Blockicons
The functions available for creating S7 programs in a library are the same as for
projects, with the exception of debugging.
Libraries are structured in a hierarchical fashion in the same way as projects:
• Libraries can contain S7 programs.
• An S7 program can contain exactly one "Blocks" folder, one "Charts" folder, and one
"Symbols" object (symbol table).
• The "Blocks" folder contains the blocks which can be downloaded to the S7 CPU.
• The "Source Files" folder contains the source files for the programs created in the
different programming languages.
• The "Charts" folder contains the CFC charts.
PCS 7 Library
The PCS 7 (Standard) Library has its final update up to V7.1.3. It is not part of the
general setup of PCS 7 V8.0 and later. For mixed applications the library is to be
installed afterwards.
 For more information about Upgrade of PCS 7 Libraries see

[208] PCS 7 Software upgrades from V7.1SP3 to V8.0 with utilization of new
functions - 12_2011 and
[209] [209] PCS 7 Software update from V7.1SP3 to V8.0 without utilization of new
functions - 12_2011

PCS 7 System Course
5.4.4 Multiproject
For configuring SIMATIC PCS 7, always use a multiproject. It binds several projects and
libraries together:
Library X
Project B
Project A
Multiproject
Library Y Library Z
Multiproject Library X Y Z A B Project
Multiproject
A PCS 7 multiproject consists as minimum of only one project and one library (master
data library), but it can also include more than one project and several libraries.
The SIMATIC Manager shows all elements of a multiproject in a tree view:
Multiproject
Project
AS Station
S7-Program
SIMATIC PC-Station (here: ES/OS)
Chart folder
Project library
(green book)
Master Data Library

(blue book)

PCS 7 System Course
5.4.5 Master Data Library

In a PCS 7 multiproject, one library has to be defined as the Master Data Library.
The Master Data Library is automatically added, if the PCS 7 „New Project“ Wizard was
used to create a multiproject.
The Master Data Library contains the multiproject specific standards and supports a
central update of the following items for the Multiproject:
• block types
• SFC types
• Shared Declarations
Filling the Master Data Library with block types
1
2
1. Open the desired PCS 7 library (in this example the APL).
2. Activate the detail view to get displayed the symbolic names and other details of the
blocks in the library.
3. Copy all required blocks from all libraries used for the configuration to the block
folder of the master data library. Make sure to also copy the blocks that are called
as a multi-instance by other blocks.
Role of the Master Data Library for bulk engineering

The Master Data Library is a prerequisite for efficient engineering (Import-/Export of
process tags and models). It contains all process tag types and import files, which are
relevant for the multiproject.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.7 for more details

PCS 7 System Course
5.5 Initial settings of SIMATIC Manager

The following global settings are valid for any PCS 7 project opened with the SIMATIC
Manager. To take on the changed settings, the SIMATIC Manager has to be closed and
restarted.
Message
Wizards numbers
Storage
location
Language Archiving
• Wizard: activate PCS 7 related wizards

• Message numbers: make CPU-oriented unique message numbers the default
setting for new projects and libraries
• Language: select the language used in the project (GUI of SIMATIC Manager and
representation of the project).
• Archiving (of the PCS 7 project): Select the archiving program and the storage
location of the archived project
• Storage location for projects/multiprojects (and libraries):
Default setting is: C:\SIEMENS\Step7\S7proj
All necessary access rights for this path are set by default already during the PCS 7
installation. If you use another storage location, then it is a must, to use the
SimaticRights.exe tool to set the required rights. The desired project path must exist
already. Start the program on the SIMATIC PCS 7 DVD in the folder.
PCS 7 V8.0

PCS 7 System Course
5.6 Setting up a multiproject

5.6.1 Organizing a multiproject
Project specific setup Each individual project contains only one AS and one OS, or all AS
and OS which a project engineer is meant to edit.
ES
Multiproject
Project 01 Project 99 Master Data
Library
AS ES/OS AS
Station granular setup As opposed to the project-specific setup, all AS and OS are filed
separately (granular) in an individual project.
ES
Multiproject
Project 1 Project 2 Project 3 Master Data
Library
AS OS ES
Distributed Engineering
With the use of several projects on different computers as a distributed engineering
system, several persons can work independently of each other on their project.
PCS 7 offers the appropriate system functions for managing, distributing and merging
the projects. The projects in this scenario can remain in the multiproject network or can
be checked out for the duration of the editing.
 We generally recommend organizing the multiproject in PCS 7 based on stations, i.e.

one subproject with one station. This setup provides the maximum flexibility during
the configuration / commissioning phase.
This applies to all automation systems and OS servers. The stations for OS clients
can also be created in one subproject.
5.6.2 Setting up the projects “Step by Step“

The recommended and most efficient way for the creation of a multiproject is to use the
“New Project” wizard. However, you should be able to create the single elements of a
PCS 7 System Course
multiproject in the SIMATIC Manager, for instance to expand an existing multiproject by

projects or stations.
To create an empty multiproject there exists also a “New Project” dialog:
“New Project” Dialog
3 2
1. Select the appropriate tab to create a new user project, library or multiproject.
2. When you select the "User Projects", "Libraries" or "Multiprojects" tab, the correct
object type is prepared by default. You can also change the type of the new object
in the drop-down list. The new object will then be automatically added to the tabs in
the correct order.
3. Enter the name of the new project, library or multiproject here. Do not use an
extended name. You can also select an existing name from the list above and
change it as necessary.
4. The path in which the project or library will be created is displayed here.

PCS 7 System Course
Insertion of an empty user project

Create a new empty project as part of an already existing multiproject in the SIMATIC
Manager by selection of the multiproject and the menu command:
Multiproject > Create in Multiproject…
Again the “New Project” dialog is displayed (without the “Multiproject” tab).
An empty user project is created in the multiproject, which you can later add stations to
Insertion of already created user projects
The typical use case for „New project“ or „Add to Multiproject“ dialogs is the integration
of additional AS/ ES/ OS subprojects into a basic multiproject, which was created using
the PCS 7 „New project“ wizard.

PCS 7 System Course
Addition of components to an existing project
Empty AS station, to be
configured by HW config
Empty PC station as ES and/or

OS, to be configured by HW config
Subnet objects for

Plant bus / Field bus
Expanding the Project with the

PCS 7 "Expand Project" Wizard
Enumerations, Units and

Equipment Properties
A project is structured into stations containing the configuration information for AS

stations and/or PC stations used as ES, OS Servers, Clients etc.
 A PCS 7 Multiproject should always consist in a PC station used as Engineering

System (ES).
Never select directly “OS” or “OS (Client)” from the “Insert New Object” menu in the
SIMATIC Manager! OS Servers, OS Clients and all other OS station types have to be
inserted always as SIMATIC PC Station.
Furthermore, each project needs network information, provided by subnet objects. The
network configuration is using the tools HW config and NetPro.
 Subnet objects are required for configuration data of the Plant bus and the Field bus,
Terminal bus information is not configured in the SIMATIC Manager.
Shared declarations contain information about enumerations, units and equipment

properties used in the PCS 7 project.
You can use enumerations to define textual representatives for the parameter values of
the block or chart I/Os with data types "BOOL," "BYTE," "INT," "DINT," "WORD," and
"DWORD". A suitable text is assigned to each value of an enumeration and this is
displayed at the I/O. Several values can be assigned to each enumeration.
Equipment properties are parameters of a unit, such as shell material, volumes etc. The
type of equipment property is defined as a "shared declaration". Instances of this type
are used in SIMATIC BATCH and its attributes are individually adapted.

PCS 7 System Course
5.6.3 Setting up the project with the „New Project“ Wizard

The "New Project" wizard supports you step-by-step in creating a new project and offers
default settings. The PCS 7 wizard automatically creates various objects according to
the default settings or the specific settings that you make.
The following pictures give you an overview about the steps of the wizard.
1. Start the PCS 7 "New Project" wizard in the SIMATIC Manager
Click „Next“ to continue step by step…

PCS 7 System Course
2. Select the CPU bundle that you are using in your project.
Detailed information about the selected CPU bundle is displayed beneath the list. In
case your CPU is not listed there, you can adjust the configuration data in the HW-
config later.
Use the button „Find“ to search for a desired MLFB number.
The „Number of communication modules“ selects the CPs for Profibus DP.
3. Define the depth of the Plant hierarchy.

Select the required configuration objects for AS and OS. Regarding the OS object
you must specify the type (main architecture).

PCS 7 System Course
4. Define the storage location and the name of the multiproject.
5. After clicking the button “Finish” the multiproject is created and contains one project
as shown in the preview, containing one AS, one OS (if selected) and one master
data library. The wizard creates the required project structure ready to continue with
the engineering.
 The subnet for Industrial Ethernet is not created by the wizard. You have to insert it
manually.
From the project icons context menu:
Insert new Object -> Industrial Ethernet
5.6.4 Expansion of Multiprojects

The PCS 7 wizards create the basic configuration, which you can expand with additional
objects based on the requirements of your plant.
For the expansion the same dialogs have to be used as already described above in the
section „Setting up the projects „Step by Step“:
• Create in Multiproject… (other projects or libraries)
• Insert into Multiproject… (other projects and libraries)
• Insert new object…(stations, subnets, shared declarations)
Furthermore, there is a PCS 7 "Expand Project" wizard available…

PCS 7 System Course
Expansion of an existing project with a Preconfigured Station

The PCS 7 "Expand Project" wizard is using similar steps as the “New Project” wizard.
1. Addition of an AS station (if required).
If AS station has
not to be inserted
Station selection
similar to the „New
Project“ wizard
2. Addition of an OS (single station, multiple station, redundant OS stations).
Plant hierarchy and

charts are not affected
by this wizard
OS type selection
similar to the „New
Project“ wizard
3. The storage location is displayed, but cannot be changed.
 For more information about expansion of multiprojects see:

[103] PCS 7 V8.0 Engineering System - 12_2011, 8.4.4 for insertion of empty projects
[121] PCS 7 Compendium part a - Configuration Guidelines - 03_2009, 2.4 for
integration of additional ES/OS-projects.
[103] PCS 7 V8.0 Engineering System - 12_2011, 6.2.2 for insertion of preconfigured
stations.

PCS 7 System Course
5.6.5 Multiproject-wide information to be synchronized

The update of multiproject-wide information is necessary typically after expansion of a
multiproject by additional projects /libraries and after insertion of subnets.
Merge Subnets / Cross-project connections:
2 3
Synchronize Shared Declarations:

PCS 7 System Course
5.7 Language for Display Devices
The language for the display devices has to be selected in a very early project
engineering phase.
Messages and texts will be transferred to the OS in selected languages during OS
compilation.
The dialog window above shows the default setting.
 The required setting is related to individual projects and libraries in a multiproject.

PCS 7 System Course
5.8 Archiving and retrieving a project, library or multi project
Archiving
• Always back up the data in the following cases:

− At least once a day
− After downloading the AS
− After configuration changes
− Before and after system component upgrades
− Before and after the software update of the configuration software
• Keep at least the three most recent versions of your PCS 7 project.
• Use different storage media for backing up the data.
− LAN hard disk
− USB hard disk
− MOD
− CD/DVD
This retains availability of your data even after failure of a device.
• You can also backup your data on hard disks of PCs in a network. Simultaneous hard
disk failures on more than one PC are very unlikely.
• If necessary, upload FBs and DBs from the controller
• If necessary, perform a "Read back" before archiving

PCS 7 System Course
Retrieving
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.
5.9 Task and checkpoint
Task: Multiproject
Goal
A Multiproject as the starting point for implementing the training application.
Checkpoint
What do you think …

• Is the advantage of using the New
Project wizard?

PCS 7 System Course
Content 6
6. Station and Network configuration........................................................................ 3
6.1 Station and network configuration – Principles and relationships ..........................................3
6.1.1 The “classic” way in STEP 7...................................................................................................3
6.1.2 The PCS 7 “fashioned” way....................................................................................................4
6.1.3 Extension of ES by a single OS..............................................................................................8
6.2 PC Station Configuration ......................................................................................................10
6.2.1 PC Station Configuration on the PC .....................................................................................10
6.2.2 PC Station Configuration in the project ................................................................................11
6.2.3 Function “PLC Configure” .....................................................................................................13
6.2.4 Task and checkpoint.............................................................................................................14
6.3 AS Station Configuration in the project.................................................................................15
6.3.1 Basic Steps ...........................................................................................................................15
6.3.2 Inserting a SIMATIC S7-400 Station ....................................................................................15
6.3.3 Editing the station configuration of a SIMATIC S7-400 Station............................................16
6.3.4 Configuring the CPU.............................................................................................................20
6.3.5 Configuring the Ethernet interface ........................................................................................22
6.3.6 Configuring the DP master ...................................................................................................23
6.3.7 Configuring the DP slaves ....................................................................................................28
6.3.8 The final Download ...............................................................................................................31
6.3.9 HW Config - Diagnostics.......................................................................................................32
6.3.10 Task and checkpoint.............................................................................................................33
6.3.11 Comparing PROFIBUS DP and PROFINET IO....................................................................34
6.3.12 Configuring the IO Controller ................................................................................................35
6.3.13 Configuring the IO Devices...................................................................................................37
SIMATIC PCS 7 – Station and network configuration

PCS 7 System Course

PCS 7 System Course
6. Station and Network configuration

6.1 Station and network configuration – Principles and
relationships
6.1.1 The “classic” way in STEP 7
IE PG/PC Interface:
e.g. MPI or
DP
ISO Industrial Ethernet
Image 1:1
Project ES
Typical field of application

Service and maintenance on the AS hardware configuration.
Steps of classic way

1. Configure of the AS in the project on the Field PG as an image 1:1 of the real
hardware.
2. Connect the Field-PG to the AS and set the corresponding PG/PC interface.
3. Download of configuration data to the AS.
4. Disconnect the Field PG from AS.
The Field-PG respectively its PG/PC interface is not part of the project, but it works only
as "loading station".
The interface has to be set individually for the selected connection type to be able to
reach the target station.

PCS 7 System Course
6.1.2 The PCS 7 “fashioned” way
Overview about ES tools to configure stations and networks
Station Configurator
AS ES „virtual“ rack
real existing CP
Plant bus, IE
real existing rack

„virtual“ interface:
PC internal (local)
Image 1:1 PG/PC Interface Image 1:1
PCS 7 Project, administrated in the Engineering System
AS in HW Config NetPro PC-Station in HW Config
Inserting an separate station for the ES

For every AS or PC to be used in a PCS 7 project, a station configuration is to be made.
In contrast to a Field-PG, the ES is involved into the project and into the common
network of all stations. Thus, all downloads can be handled with one PG/PC interface.
Configuration of stations:
• Make an “image” 1:1 to the real existing hardware of every station in the project.
• Configuration conforming to slots:
AS hardware is structured by slots in a rack. Each slot is allocated by a hardware
component like power supply, CPU, CP…
Properties of the component in a slot include type, addresses…
Since there is no real existing slot orientation of components in a PC station, a structure
with slots similar to an AS rack is simulated by the Station Configurator.
From this follows, that the PC hardware has to be described in 2 different localizations:
• Hardware of the station, represented by the Station Configurator of the PC station
• Hardware description in the HW config of the PCS 7 project

PCS 7 System Course
Configuration of network and communication connections:

• You specify the network assignment of components capable of communication during
hardware configuration of a station in the HW Config.
• The SIMATIC Manager tool NetPro graphically displays all configured stations and
networks of a project. All bus systems and stations have their own representatives.
PG/PC Interface
The interaction of your PC Station with various bus systems for networking of
automation systems (e.g., MPI bus, Industrial Ethernet,…) requires specialized
interfaces. Each of your integrated and installed interfaces is represented by an
interface parameter assignment.
“PC internal”
"PC internal" is a centrally configurable interface, which can be loaded with project-
specific settings for all stations on the plant bus. The settings are made on the ES in the
PCS 7 multiproject and downloaded from the ES.
As soon as "PC internal" is activated, the network adapter begins working in
"configured mode", otherwise it is in "PG mode".
Field-PG
MPI
working in „PG mode“

CP1613 ISO
PG/PC-interface:
target system DIRECT Selection of a „driver-instance“
(CPU) Download
for STEP 7 communication (S7ONLINE)
3COM ISO
ES/PC station
Working in „Configured mode“
MPI
PG/PC-interface: Download
INDIRECT Selection of „driver-instance“
CP1613 ISO
target system for STEP 7 communication (S7ONLINE)

(AS-CPU or
other PC stations)
PC internal
3COM ISO
Target system?
Own or other PC „virtual rack“
or AS-CPU?? (Station Configurator)
PC station
configuration

PCS 7 System Course
Activating PC internal
Activate the “PC internal” interface via the Dialog “Set PG/PC Interface” in SIMATIC
Manager:
Configuration Console
All communication modules, on this station available for PCS 7, are listed here.
All access point and their assignments are listed here and can be changed
 See [102] PCS 7 V8.0 PC Configuration and Authorization - 12_2011, 4.7.7 for more
details about use of SIMATIC NET configuration console as possible alternative
procedure.

PCS 7 System Course
Download to ES
ES
AS
„virtual“ interface:
PC internal (local)
PG/PC Interface
Plant bus, IE
real existing rack
Image 1:1 Image 1:1

AS in HW-Config NetPro PC-Station in HW-Config
The central ES has to be loaded at first with all information to get the capacity for
download to all other station (AS and OS) involved in the PCS 7 project.
The configuration data are checked during the download. Both the configuration in the
PCS 7 project and the configuration in the Station Configurator have to contain the
same information as precondition for a successful download.
Status information about "download successful / unsuccessful" is displayed in the
Station Configuration Editor.
After successful download, the ES has access to the IE network, and within access to
all connected stations:
AS and PC stations (e.g. server) can be reached and loaded via ES-CP and “its
network".
The ES got this information by configuration data of the PCS 7 project!

PCS 7 System Course
Download to AS
ES
AS „virtual“ interface:
PC internal (local)
PG/PC Interface
Plant bus, IE real existing CP
real existing rack
Image 1:1 Image 1:1

After successful downloading to ES the AS hardware configuration can be downloaded

to the AS station. The configuration data are checked during the download. LEDs on the
front side of CPU give status information about "download successful / unsuccessful".
6.1.3 Extension of ES by a single OS
Insertion of an application for a PC station

Each PC station requires additional information for what purpose it is applied in the PCS
7 project (e.g. OS, OS server or client, Batch…).
The desired software component is represented as an object of type “WinCC
Application” and has to be placed like a hardware component:
• in the virtual rack of the Station Configurator
• in the HW config of the regarding station in the PCS 7 project
 The following phrase may give a hint:

The CPU of AS needs a partner on the PC: a "CPU of visualization" for the OS. This
is the job of the "WinCC Application". Following this analogy, the WinCC application
is placed in the hardware configuration of a PC station like a CPU in the AS rack.
Several WinCC Applications are available being specialized for different types of PC
stations (e.g. OS, OS server or client, Batch…)
An example for single OS stations is the application WinCC Application.

PCS 7 System Course
If you want to use the ES also as OS Single Station, then you have to extend the PC
configuration of ES by a WinCC application for single OS stations:
Configuration of network and connections
AS OS ES
Plant bus, IE
Image 1:1
Communication connections (connections, for short) must always be configured, when

data exchange between the automation systems or the automation system and a PC
station (for example, an OS station) is required.
The figure above illustrates the relation between communication partners.
• The "true communication partners" are CPU of AS at the one side and the CPU of
OS / WinCC at the other side ( red point): they are the end of a "logical
connection".
• The CPs are interface of the network ( green line): they are the end of a "physical
connection".
Once the stations have been arranged and configured, the connections between the
ES/OS station and the automation systems, as well as those between the automation
systems themselves, are configured (as 1:1 image) and downloaded to the concerned
stations – just like the configuration of stations.

PCS 7 System Course
6.2 PC Station Configuration

6.2.1 PC Station Configuration on the PC
Select the PCinternal interface in your ES via the Dialog “Set PG/PC Interface” in
SIMATIC Manager:
Options -> Set PG/PC Interface
For a combined Engineering / Operator Station with a single network connection

• a network interface for Industrial Ethernet (CP or IE General)
• the WinCC Application
have to be added. You are free choosing a slot (see column "Index"), because it is "only
a virtual rack" for the PC.

PCS 7 System Course
6.2.2 PC Station Configuration in the project

In the project a SIMATIC PC Station is to be inserted:
It is to be renamed to the computer name.

This applies to all PC stations. The name of the PC station must match the station name
in the Station Configuration Editor, which already has the preset computer name.
 Rename the PC station so that its name matches that of the computer.
To do this, you can activate the "Computer name identical to PC station name"
option, which means you do not have to make as many entries and the potential for
typing errors is reduced.
A yellow arrow then appears on the PC station icon in the SIMATIC Manager to indicate
the capability of the ES to establish a connection to the plant bus via the "PC internal"
interface.
After renaming its configuration is to be opened:

PCS 7 System Course
On the same position as in the Station Configuration Editor an IE interface is to be

inserted and supplied with the proper addresses and network assignment:
After completing the configuration, it is to be saved and compiled and downloaded.
6 4
7 5
Main components:
1. CPs for high performance applications:
− higher number of communication partners;
− redundant connections
− time synchronization
2. standard network adapter
3. standard object for single or multi user system
4. object for OS Client
5. object for referenced OS client
6. object for central archive server
7. (stby) stands for redundant partner

PCS 7 System Course
6.2.3 Function “PLC Configure”

From PCS 7 V7.0, the function „PLC configure“ provides a comfortable approach for
configuration of SIMATIC PC stations. With this function, you must no longer twice work
on the configuration (in the project on the ES and in the station configuration editor on
the local PC station).
However, there are important prerequisites:
• The PCS 7 software is installed on the station to be configured.
• The station has to be accessible in the network.
Procedure for configuration of PC station of the ES

1. Configure the SIMATIC PC station of the ES in the project (ending with a Save and
Compile, not a Download)
2. In SIMATIC Managers Component view, transfer the PC configuration of the project
to the PC by the function “PLC configure“. The virtual rack of Station Configuration
Editor is overtaking the PC configuration already prepared in the project.
3. Download of the configuration.

PCS 7 System Course
6.2.4 Task and checkpoint
Task: Station Configuration PC
Goal
A configured SIMATIC PC Station, both in the project and the Station Configurator.
Checkpoint
Two questions …
• What additional components can
be added in the Station
Configuration Editor?
• What makes these components to
be listed here?

PCS 7 System Course
6.3 AS Station Configuration in the project

6.3.1 Basic Steps
Inserting a preconfigured station into SIMATIC Manager
Opening HW Config
Setting the object properties of the CPU and CP
Inserting and configuring decentral stations
Saving and compiling the configuration
Downloading the configuration into the AS
6.3.2 Inserting a SIMATIC S7-400 Station

To represent the automation system, a SIMATIC S7-400 station is inserted into the
project:
1. In this “empty“ station, all components are to be inserted using the HW config tool
2. Alternative: After creating a multiproject with the wizard, a project with a
preconfigured S7-400 is available then.
Adjusting is always possible using HW Config.

PCS 7 System Course
6.3.3 Editing the station configuration of a SIMATIC S7-400 Station

To open the HW Config tool, select the object of the AS station in the component view
of SIMATIC Manager:
The configuration of an AS station must contain all real placed components and
modules:

PCS 7 System Course
User interface
1 2 3
5
6
Main elements:
1. Switching between Offline and Online window
From the HW Config you can read information from modules directly (e.g. for
diagnostics)
2. Save and Compile
After configuration of the components, the data can be saved and compiled.
3. Download to station
After compilation the data can be downloaded to the station.
4. Station window
This area is filled with racks as the main parts of a station. Also objects for
distributed IO and field devices and the required master systems (networks for IO).
5. Window for hardware catalog
To select the required components: e.g. racks, modules, interface modules.
6. Object for distributed IO device
7. Configuration table
Represents the racks and their modules, offers a certain number of slots in the
same way the real racks do.

PCS 7 System Course
Working with the Hardware Catalog

When the window “Hardware Catalog“ is not display, select the menu command:
View -> Catalog
1
2
Main areas
1. Find field
Entrance possibilities:
− In the Find field you can enter any text, catalog info or order number.
Not case sensitive
− wildcards (*, ?,….) are supported
− you can also enter a part of an key word (e.g. 331)
2. Using the pull down list “Profile“ you can select several catalog profiles.
You can adapt the profiles to your needs.
3. Object for the required module (in this case with a firmware version).
4. Information of the selected component
Versions
Many modules are available in different versions (Firmware versions).
During operation of a plant it may happen that you are forced to replace an older version
of a module by a new one with a higher version. In that case the old version remains in
the HW Config and the new module is placed.

PCS 7 System Course
Save and compile

At Save and Compile a consistency check is performed, e.g.:
• Do all modules fit to each other?
• Are addresses assigned twice?
This is the case in the result window below:
Download
When the consistency check is error free, the required system blocks are created,
without any user interference. After that they can be downloaded into the AS.
The AS contains all the required information to test if the real configuration fits to the by
HW Config created configuration.
I will be hidden for the user that many additional features are activated, so that in the
events of failures the related messages and alarms will be generated.
To download the HW Config data into the AS, the entire communication path from the
ES PC up to the Ethernet CP in the AS must be configured properly.
For the initial download into the AS, a number of configuration steps are to be done
using the tool NetPro. It will be explained in a later stage.

PCS 7 System Course
6.3.4 Configuring the CPU

SIMATIC PCS 7 uses default optimized settings for a CPU, so just a limited number of
properties are to be adjusted to the project conditions.
Startup properties
In the Startup properties the most important is the activated option “Warm restart“.
This causes the actual process values not to be reset to the initial values.
It is a default setting for PCS 7 that is not to be changed!
 Please note, that a PCS 7 AS is always to be equipped with a buffer battery and a
RAM memory card.

PCS 7 System Course
Organization blocks, cyclic interrupts and Process image partitions
1 2 3
1. List of OBs assigned to cyclic interrupts (grayed out = not available fort his CPU)
2. Interval of the cyclic interrupt
3. Assigned Process image partition (PIP)
Organization blocks (OBs) form the interface between the CPU operating system and
the user program. OBs are called by the operating system and control the cyclic and
acyclic program sequence, the startup behavior of the automation system and the
processing of faults.
Start events triggering some groups of OBs are called interrupts.
Cyclic interrupts do their job with predefined time interval. They are represented by
OB30 – OB38.
OBs also control the sequence of processing the individual program blocks. The
processing of one OB can be interrupted by another OB (determined by the priority).
Before any program run, the CPU loads the signal values of the input modules into a
memory, the Process Image Inputs (PII). Because of this PII, the signal values will be
constant during the program run. During the execution of the user program, output
values are assigned to the Process Image Outputs (PIQ). At the end of the program run,
the values of the PIQ are transferred to the output modules.
To control the update of the PII at the start of a program run triggered by a cyclic
interrupt, and the update of the PIQ at the end of a program run, the so called Process
Image Partitions (PIP) are assigned to the cyclic interrupts in use.
 In process automation with PCS 7, the Cyclic Interrupts (OB30-OB38) are to be used
with an assignment to a Process Image Partition.
The Process Image Partitions are required at the configuration of the signal modules.
Automation functions are “inserted” into the run sequence of an (Cyclic Interrupt) OB.

PCS 7 System Course
6.3.5 Configuring the Ethernet interface

An S7-400 automation system can include a CP443-1 as an interface to the plant bus.
Both the ISO protocol and the TCP/IP can be used.
1
2
4
5
1. Device name is not relevant when this module is used for the plant bus only.
2. ISO connections
3. TCP connections, ISO over TCP connections, UDP connections
4. Creating a new subnet object
5. List of available subnet objects
The connection to the plant bus is made by selection of the related subnet object in the
properties of the Ethernet CP.
When a multiproject has been created by the wizard, the project does not contain a
subnet object for Industrial Ethernet. The required subnet can be created in the
properties of the Ethernet interface.
On a with ISO protocol running plant bus, every MAC address can be assigned only
once.

PCS 7 System Course
6.3.6 Configuring the DP master
Objects
3 4
1
1. Internal Profibus interface of the CPU, default set with a DP Master system.
2. External Profibus interface: is realized by the CP 443-5 Ext.
The module can be placed to have additional DP master systems.
3. Subnet: object for a Profibus net. In its Properties you can adjust the transmission
rate and the profile. Always assign a useful name (default: PROFIBUS(1)).
4. DP master system: All slaves assigned to a master form together with the master a
master system. A master system is a part of a PROFIBUS subnet.
5. Object for a Profibus slave. Distributed IO devices or field devices are assigned a
master system as a slave object. In case of a ET200M it can be the IM 153-2, for
connecting to the Profibus.
Every node (master and slave) is assigned a Profibus address (0…126)

PCS 7 System Course
Adding (inserting) and disconnecting, orphaned master systems

The internal Profibus interface is default assigned a DP master system. When more
Profibus CPs are available, then additional master systems are to be assigned.
1. External Profibus interface

2. Already existing DP master system
It may happen, an already completely configured master system is to be assigned to
another DP interface (e.g. from the internal Profibus interface of the CPU to the
additional CP 443-5 Ext).
In that case the master system is disconnected from the interface, and will be available
as an “Orphaned” master system. The configuration of the distributed IO will remain
unchanged.
1. Already completely configured master system

2. Internal Profibus interface as Profibus master
3. Orphaned master system

PCS 7 System Course
Orphaned master systems are put into a list that will appear when you want to assign a
master system to a Profibus interface. In that way you can connect an existing master
system, including the included configuration of distributed IO to another Profibus
interface.
1. Orphaned master system

2. External Profibus interface as Profibus master
Connecting with Profibus subnet and assigning the address to the interface
1
2
3
4 5
1. For diagnostics: assign useful name

2. Available Profibus addresses
3. Disconnecting from the subnet
4. Connecting to the subnet
5. Adjusting Profibus properties.

PCS 7 System Course
For assigning Profibus addresses, only the for that subnet available addresses can be
used.
 A Profibus interface must not be assigned as a master system, but can still be
connected to a subnet. I that case the Profibus address is still in use.
Independent from separating the master system, you must disconnect the Profibus
interface from the subnet, before the address can be used by another node (another
Profibus interface).
Operating mode of the Profibus interface

Check in the Properties dialog, in tab “Operating mode”, if the DP mode “DPV1”is used.
The DP mode “DPV1” contains extensions for process automation.

More specific: acyclic data exchange for parameter settings, operating, visualization,
and interrupt control of intelligent automation devices, parallel to the cyclic data
exchange.
 With the setting DPV1 also DP slaves, not supporting DPV1 can be connected and
operated.

PCS 7 System Course
Properties of a Profibus subnet
1. The default Profile “DP” should not be changed for PCS 7.

2. Set the Transmission Rate dependent of the connected DP slaves and the segment
length. The default Transmission Rate of 1.5 Mbit/s can be increased to 12 Mbit/s in
individual cases, to achieve shorter cycle times.
3. Using the button “Options” you can enter your cable configuration, to have the DP
bus parameters optimized for your process.
 See [403] Source name, for more details on configuring PROFIBUS hardware.

PCS 7 System Course
6.3.7 Configuring the DP slaves
Placing the modules
1
2
3
7
5
1. Finding using an order number

2. Profile with released modules
3. open the tree under the field bus
4. DP slave “family”
5. Select the interface module as a DP slave. Drag & Drop it on top of the DP master
system. The dialog “Properties – PROFIBUS interface …”opens, where you can set:
− Properties of the PROFIBUS subnet (transmission rate etc.)
− the address of the DP slave
6. Profibus address. The address must fit to the address set on the module (for
ET200M Dip switches are used).
7. Configuration table of the DP slave. A symbol for the DP slave is connected to the
line representing the DP master system. In the lower window pane a table is
displayed with the available slots.
8. Signal module: Drag & Drop the modules in the Configuration table. For modular
DP slaves, the usable modules are organized in the “Hardware catalog” in lower
level folders representing the DP slave “family”. For the family ET200M S7-300
modules are used.

PCS 7 System Course
Configuring the ET200M interface module
Be sure, there is a check mark at “Replace modules during operation”.
 For use in PCS 7 the racks of ET200M should be equipped with active bus modules.
Configuring signal modules
2
1
1. Select useful names (diagnostics)

2. Select a Process Image Partition (PIP). It should have been set in a earlier stage in
the CPU properties of a cyclic interrupt OB. Doing so, the IO signals are
synchronized with the Process images due to the cyclic interrupt OBs.
This setting affects all channels of the module.

PCS 7 System Course
Diagnostics enabled
Modules with diagnostic recognize internal and external module faults and generate
diagnostic alarms.
With the enabling of the diagnostic interrupt, the diagnostic alarms will be generated
automatically through the PCS 7 drivers after an OS compilation.
Channel specific settings

In general, a channel of a module should only be activated, when the related sensor,
actuator or replacement resistor has been connected.
That is to prevent unwanted diagnostic messages on the PCS 7 OS in Runtime.
At some modules, channels are grouped to channel groups. In that case the settings are
common for the channels of the channel group, e.g. for the AI8x12Bit module: 4 groups
of 2 channels each. The group is to be activated when a signal is connected to 1
channel. Then a resistor is to be connected to the other channel.
Example: Configuring an Analog Input module
5 6
2 3
1. Measuring type must fit the Position of Measuring Range Selection Module.
2. Active channels
3. Inactive channels
4. Channel group specific Diagnostics settings
5. Enabling the diagnostic alarms for the entire module
6. Not to be set for PCS 7. This function is covered by the channel drivers.

PCS 7 System Course
6.3.8 The final Download
1 2
5
6 7
1. In HW Config, perform a Save and Compile. There should be no error.

2. Initiate the download procedure, using the button Download to Module.
3. The target module should be the CPU, click on OK.
4. Select the protocol for downloading (only when both TCP/IP and ISO have been
selected at the properties of the Ethernet interface module).
5. The download will start, but will be interrupted when the CPU is in Run mode …
6. Click on OK when you agree to put the CPU in Stop mode, the download will
continue then.
7. After completing the download, you can have the CPU in the Run mode again.
Therefore, click the Yes button.

PCS 7 System Course
6.3.9 HW Config - Diagnostics

In brief the Online view of HW Config:
1. In the tool bar, click on the Offline <-> Online button. This will switch between the
Offline and Online window, not closing the earlier window. Icons represent states
and modes. To have an impression 4 examples:
2. The CPU Stop and Run mode. Run mode is active now in the window.
3. Mismatch between preset and actual configuration: the configured module does not
exist or a different module type is inserted.
4. Diagnostics not possible: No online connection, or the module does not return
diagnostic information.
5. Fault: module has a fault.
Possible causes: diagnostic interrupt, I/O access error, or error LED detected
More diagnostic information is available after double click on the regarding module. The
Module information window allows to read the diagnostic buffer:
3
1

PCS 7 System Course
1. Status of the module from the viewpoint of the CPU

2. In the diagnostic buffer the diagnostic events are displayed in the order they occur.
The first entry contains the newest event.
3. If you select an event in the list, a detailed description will appear in this box:
− Name of the event and event number
− Additional information, depending on the event, such as the address of the
command that caused the event and the mode transition that was caused by the
diagnostic event.
− Event state being entered or left
Task: Station Configuration AS
Goal
A configured SIMATIC S7-400 Station, to be used as the AS in the training application.
Checkpoint
Find out:
• What IO address ranges are in use,
set by HW Config?
• Be sure the address range 100 …
299 is not used, it will be used by
the process simulation.
• If used, please modify the
addresses now !

PCS 7 System Course
6.3.11 Comparing PROFIBUS DP and PROFINET IO
Why PROFINET IO?

Future requirements regarding system performance and sizing will have field busses
reach their limits.
Because of continuous technological development Ethernet provides future-proof
communication platform with high performance.
Merging the areas office and automation, vertical integration offers productivity
improvement potential.
In the office sector, Ethernet is the unchallenged standard in the fields of installation
technology and protocols.
PROFIBUS DP Attribute PROFINET IO
PROFIBUS / RS 485 Network type Ethernet
DP-Mastersystem Subsystem Name IO-System

Designation of System
DP-Master IO-Controller
Controller
DP-Slave Field Device Name IO-Device
Master Classe 2 Administrative Services IO-Supervisor
PROFIBUS DP Name at Hardware Catalog PROFINET IO
Address Assignment of
PB-Adr. 0...127 Device Name
Equipment
Stations-Nummer Number allocation Device Number
PROFIBUS DP Functionality PROFINET IO

Several data channels between
Only an exactly defined data channel
between Master and Slave Data Channel Controller/Supervisor and Device can be
realized
Possible, through flexible
Same priority of data traffic Data Priorization parameterization of actualization rate.
Maximum 256 participants per Controller.
Amount of
Maximum 126 participants Unlimited throughout the Network
Participants segment.
Not allowed IT Services It can be integrated without restrictions.
From several participants, possible only Access to Data of a From several participants, possible
reading Field Equipment reading and writing
Only one priority possible Alarms and Diagnosis Can be differently prioritized
Simple designation of Address/Name of
the device at the project (through
Over DIP-Switch or by Telegram Addressing set up Controller with support from Engineering-
Tool)
Max. 12 Mb/s (Token) Baud rate 100 Mb/s (full duplex, i.e. 200 Mb/s)
Typically Line structure; Tree or Ring
Line, Star, Tree, Ring and mixed
possible with restrictions; terminal Topology configuration possible
resistance at the last participant needed

PCS 7 System Course
6.3.12 Configuring the IO Controller
Addressing
Profinet IO: Simple name designation
Profibus DP: Individual
through Controller with support of
addressing in each station
Engineering System
Before the distributed IO can be used by the central station it must have an address:
• For DP slaves: a number: 0 …126
• For IO devices: a device name
The device name can be assigned in different ways, e.g. by the HW Config tool of
STEP 7.
Initial Steps
Open the Properties of the Ethernet interface:

PCS 7 System Course
Then proceed with the following steps:
5
1
4
6
1. Enter the required Device name.

2. Notice that the interface is not assigned an Ethernet subnet yet. Continue with the
Properties button.
3. Enter the required IP address and subnet mask fort the new Ethernet subnet.
4. Click the New button to actually create the subnet.
5. Enter the required name of the subnet.
6. After closing the last window, notice that a subnet has been created and assigned
to the interface module.
Inserting the PROFINET IO System
1
2
1. In the Ethernet interface module, select in the context menu:

Insert PROFINET IO System
2. The PROFINET IO System is displayed now, based on the connected subnet.

PCS 7 System Course
6.3.13 Configuring the IO Devices
Inserting the ET200M Interface module
1. Select in the catalog: the PROFINET IO tree, the required “family” and the Interface
module.
2. Open the device properties
3. Enter the required name. Press the Ethernet button to continue.
4. Enter the required IP address.
After closing the windows the modular IO device is ready to accept the modules.

PCS 7 System Course
Inserting the IO modules
1 2
1. Select the IO Device. The Configuration tables lists the possible slots.
2. Open the tree under the placed ET200M interface module.
3. Open the folder representing the type of modules.
4. Place the required module on the proper slot.
Assigning the Device name to the real IO device

PCS 7 System Course
1. From SIMATIC Managers Options menu, open the Set PG/PC Interface
dialog window, to change the S7ONLINE access point to TCP/IP on the ES
Ethernet interface in use.
2. Create a physical cable connection from your ES to the unused port of the
PROFINET interface module, to be able to access the IO device.
Then, continue in HW Config:
1 3
5
7
4
1. After selecting the desired device, activate from the menu:

PLC > Ethernet > Assign Device Name …
2. In the dialog window, have the device name in the Device name pull down list.
3. The table Available devices should display the accessible devices on the
network.
4. You can use 2 predefined filter settings.
5. When you have eye-contact with the IO device, use the Node flashing test
feature to improve the identification of the device.
6. After highlighting the desired device, click on the Assign name button.
7. Put back the cable connector to where it come from.
8. For the PG/PC interface, select the PC internal mode.

PCS 7 System Course
Content 7
7 Connection to the process ..................................................................................... 3
7.1 Learning Targets.....................................................................................................................3
7.2 Component View and Plant View ...........................................................................................4
7.2.1 Component View ....................................................................................................................4
7.2.2 Plant View ...............................................................................................................................5
7.2.3 Assignments ...........................................................................................................................5
7.3 Task and Checkpoint ..............................................................................................................6
7.4 Basics for charts and blocks ...................................................................................................7
7.4.1 Device control functions..........................................................................................................7
7.4.2 Charts .....................................................................................................................................9
7.4.3 Catalog for libraries, blocks and charts ................................................................................11
7.4.4 Inserting a block into a chart.................................................................................................13
7.4.5 Block properties ....................................................................................................................14
7.4.6 I/O Properties........................................................................................................................15
7.4.7 Interconnections ...................................................................................................................15
7.4.8 Compile and Download.........................................................................................................16
7.4.9 Test mode .............................................................................................................................19
7.5 Organization blocks ..............................................................................................................20
7.6 Run Sequence ......................................................................................................................22
7.6.1 How to Adapt the Run Sequence .........................................................................................22
7.6.2 Runtime properties ...............................................................................................................24
7.6.3 Optimization of the Run sequence .......................................................................................24
7.6.4 Runtime properties for experts: Activating/Deactivating runtime groups..............................26
7.6.5 Runtime properties for experts: Switching runtime groups on and off during operation ......27
7.7 Different groups of blocks .....................................................................................................28
7.8 Driver Blocks.........................................................................................................................29
7.8.1 General .................................................................................................................................29
7.8.2 Digital Input and output.........................................................................................................30
7.8.3 Analog Input and Output.......................................................................................................30
7.8.4 Module drivers ......................................................................................................................31
7.8.5 Process Image Partitions......................................................................................................33
7.8.6 Symbolic Addresses .............................................................................................................35
7.8.7 Pcs7DiIn in brief....................................................................................................................36
7.8.8 Pcs7AnIn in brief...................................................................................................................37
7.9 Trend Display........................................................................................................................39
7.10 Dynamic Display ...................................................................................................................40
7.11 Task and Checkpoint ............................................................................................................40
7.12 Connection to the Process simulation in this training ...........................................................41
7.12.1 Method in this training...........................................................................................................41
7.12.2 Overview ...............................................................................................................................42
7.12.3 Digital Inputs .........................................................................................................................43
7.12.4 Digital Outputs ......................................................................................................................44
SIMATIC PCS 7 – Connection to the process
PCS 7 System Course
7.12.5 Analog Inputs ........................................................................................................................45

7.12.6 Analog Outputs .....................................................................................................................45

PCS 7 System Course
7 Connection to the process

7.1 Learning Targets

• the use of the Component view and the
Plant view in a Multiproject
• The basics of charts and blocks and
how to work in the CFC editor
• The use of symbolic names to every IO
signal
• The features for testing IO signals

• Configure charts containing drivers to
all signals of the Signal Box,
representing some live process signals
• have the Johnssons process simulation
installed and tested as a preparation for
creating the automation functions to the
training application

PCS 7 System Course
7.2 Component View and Plant View

7.2.1 Component View
After opening and creating a project, its Component View will be displayed. All data will
be assigned to physical stations and components.
1
4
2
5
1. Stations
2. Subnet objects: only renaming is possible here.
3. Shared declarations contain the elements Enumerations, Units and Equipment
Properties. They can be used by several tools and editors.
4. S7 Program folder: it is recommended to assign a unique and proper name to
prevent mistakes when identifying the station using this name. Blanks are not
permitted.
5. Symbol table: for every S7 Program (every CPU, every AS) there exists a unique
symbol table, for storing the relation between Symbolic names and addresses or
block types.
 Stations and components are to be inserted first before data can be edited. Subnet
object are inserted here only, they are edited by HW Config and NetPro.

PCS 7 System Course
7.2.2 Plant View

For PCS 7, another view is important: the Plant View for displaying the Plant Hierarchy.
The Plant Hierarchy shows the hierarchical relationships of your plant (units, equipment
modules …) in a tree of hierarchy folders. The folder names have to identify the
components of the plant.
Different Representation of the Master data library

• In the component view: An S7 program with the folders for
− Source files
− Blocks
− Charts
− and one folder for shared declarations
• In the plant view: The folders for
− Process tag types
− Models
− Shared declarations
7.2.3 Assignments
Configurable objects like charts and pictures are created in the Plant View window of
the project. An assignment to a station in the Component View will organize its real
target station (AS or OS).

PCS 7 System Course
7.3 Task and Checkpoint
Task: Plant Hierarchy
Goal
The starting point of the Plant Hierarchy
Checkpoint
Compare …
• the arrangement of folders on your
ES to what is listed in this task.

PCS 7 System Course
7.4 Basics for charts and blocks

7.4.1 Device control functions
Every device in the plant will be represented by a chart with blocks in the engineering
station, and a block icon/faceplate on the operator station. Predefined blocks are
available in a library.
1 3
4 5
1. Drive in the plant

2. Chart in the engineering station
3. Block representing the drive
4. Controlling, monitoring, interlocking …
5. Control signal to the drive
6. Block type in the library
7. Operating and monitoring
The control of motors, valves and other process devices (process tags) in process
control systems is done by device control functions.
They offer the control, monitoring, operating from devices by supplying the connection
to control devices and their feedback. They also include parameter setting and
diagnosing faults.
Blocks
In modular designed user applications in process control software, device control
functions are realized by technological blocks. The inner side of these blocks is hidden
for the users.

PCS 7 System Course
Block types and block instances

Predefined device control functions are offered in process control libraries.
For example, the control of a motor can be done in PCS 7 using a motor block MOTOR
from the standard library or the MotL from the Advanced Process Library (APL).
They differ in the scope of control features and their graphical representation for
monitoring and controlling.
Block types: Block instances:
• Type name • Are generated from the block type

• Data interface (input and • Many block instances possible
output parameters) • In chart connectable and parameterizable
• Algorithm • Central update of all instances with the
• Available in libraries related block type
• Central management/update
in the Master Data Library
DB x DB y DB z
Instance data blocks:

• Created for every block instance

PCS 7 System Course
7.4.2 Charts
Charts are the placeholders of blocks. Each chart has a name that is unique within a
CPU. Charts will hold the blocks using a graphical representation in the CFC editor. In
general a chart contains several block, which are connected to each other.
Sheet view and navigation

Each chart consists of up to 26 chart partitions each with 6 sheets. You can see all of
the sheets in the Overview:
Overview
Sheets
sheet 1 sheet 4
sheet 2 sheet 5
chart partitions,
initially one,
can be A … Z
sheet 3 sheet 6
Sheet view Pull down list to

select a sheet
Text box for

chart comments
Sheet bar Sheet bar

PCS 7 System Course
• After inserting a new chart into the Charts folder, and opening, the chart starts with
one partition, containing 6 sheets.
• You can switch between the sheet view and overview by clicking the button in the
tool bar, or double click in a sheet (on the white background).
• As an alternative, you can use the pull down list.
• The sheet bars are used for references of connections outside of the sheet.
• Use the text box to enter a chart comment. You can position a text box in the chart
just like blocks.
CFC editor tool bar:
1 3 5 7 9
2 4 6 8
1. Show the CFC catalog

2. Show the chart I/O view
3. Show the run sequence view
4. Show the technological I/O view
5. Compile charts
6. Download the S7 program
7. Switch to the CFC test mode
8. Open the Chart Reference Data
9. Zoom in/out the sheet view

PCS 7 System Course
7.4.3 Catalog for libraries, blocks and charts
Using the toolbar button Catalog, you can toggle the display of the catalog.
3 tabs
3 tabs at the bottom separate the catalog into 3 areas:
1 2 3 4
1. Libraries, where preinstalled and later added libraries can be displayed. In this view
the block folder of the library shows its content. When each block is assigned to a
family, blue books represent the families. Libraries contain blocks of the type FB
and FC. In general blocks of the PCS 7 libraries are used.
2. A library may contain a subfolder “Templates”, displaying the available templates:
predefined charts for control functions.
3. Blocks, initially containing a series of blue books, representing the so called Basic
Operations of CFC. They origin from the use of CFC for PLC programming. In
general the content is not used for PCS 7.
During the progress of the configuration of an AS, more blue books will appear
here, containing the block types that are used in the AS charts, grouped into
families.
The folder at the bottom of the list (in this picture “AS08”) will contain the same
series of blocks that has been copied into the blocks folder of that AS because of
the use in the charts.
4. Charts, listing the charts present in the charts folder of the AS (not the system
charts). The opened blue folder represents the active chart in the CFC editor.

PCS 7 System Course
Templates
Templates are predefined charts for control functions. They are available in the chart
folder (called “Templates”) of the PCS 7 library.
They can be used in an application in different ways:

• by copying into a project (plant hierarchy folder) and the adjusting the signals and
parameters.
• by copying into the Master Data Library of a Multiproject. Then it is to be used as a so
called “Process Tag Type”. More details later.
 See [302] PCS 7 CFC for SIMATIC S7 - Function Manual - 04_2012, 7.2.2 for more
details

PCS 7 System Course
7.4.4 Inserting a block into a chart

When you insert a block in your CFC chart, you generate an instance of this block type.
In this context, “instance” refers to an instance of the selected block type.
Block
1 header
2
4
3
Drag
You can drag blocks from the catalog (library) into a chart. The installed blocks are
assigned to the OB where the Runtime Group of the chart belongs to (this example:
OB35).
1. Block name (name of a block instance): CFC assigns a number as a name to a
block instance when it appears in a chart. The name should be changed using the
Block Properties dialog window.
 The name has a maximum length of 16 characters and is displayed in the block
header. Illegal characters: / \ ." %.
Remember when assigning names that the variable name must not be longer than
128 characters for transfer to the OS. This includes not only the block name but also
hierarchy path, chart name, separator and I/O names.
2. Name of the block type: This name cannot be changed in the CFC Editor.
3. Block comment: The comment, a user-specific text, appears in the block header.
The block header can display up to 14 characters of comment. Small blocks do not
display the comment.
4. Predecessor for blocks: One block per chart will have a light green colored
Runtime properties area in the block header (instead of dark green). This indicated
the block is de predecessor block. A new inserted block for this chart will be
inserted behind it in the run sequence.

PCS 7 System Course
7.4.5 Block properties
General
1
1. After a double click in the block header, the Properties dialog window appears, with
the General tab opened.
2. The name field is preset by just a number. Usually it is replaced by a more useful
name.
3. The comment field is preset by a brief block description. It can be changed.
4. Some areas in this dialog window may not be valid for a block type. The objects are
grayed out then.
I/Os
A second tab lists the properties of the individual inputs and output:
1
2
1. Inputs of a block
2. Outputs of a block
3. Several settings, initially with their default values. White fields can be changed.

PCS 7 System Course
7.4.6 I/O Properties
1 2
1. After a double click on a block input field, the Properties dialog window of the input
will appear. When an input has been designed as a structure, first the Select
Structure Element window appears.
2. The I/O Properties dialog window is displayed.
3. The main field is the Value field. When there is no connection configured to this
input, a value can be assigned.
Other settings are explained later.
7.4.7 Interconnections
For transferring a value from a block output to a block input, an interconnection can be
configured.
In general:
• To make an interconnection, you can click at the output and then at the input (or in
opposite order).
• Alternative you can drag from the output to the input (or in opposite order).
• An output may have several connections to several inputs.
• An input can have only one connection to an output.

PCS 7 System Course
Display of instances with invisible interconnected block I/Os
Indicator for an invisible

block I/O still being
interconnected
If interconnected block I/Os are made invisible, this is shown in the instance header
using a cyan triangle.
7.4.8 Compile and Download
Data flow of configuring in CFC

After creating the required functions in the charts, they are to be send to the CPU:
Block library
Block instances CFC Charts

CFC Editor Block types Parameters
Code generation
SCL source Compile
Compilation
S7 User Programm
S7 target system Download
Machine code

PCS 7 System Course
Compile
1. The Compilation process converts the functions in the charts into blocks, and
stores them in the offline blocks folder.
2. With the Scope, you select if the program is to be compiled entirely (only option for
the first time) or with changes only (compared to an earlier compilation).
Download
1. With Download, the blocks are copied to the CPU.

2. With the Download mode, you select if the entire series of block are copied to the
CPU (only option for the first time) or only the changed (new) ones (compared to an
earlier download).

PCS 7 System Course
Compile and Download

When the download button is clicked, without performing a compilation beforehand, a
message box appears, prompting that you can do both in one session:
1
2
3 4
1. Click on the Download button

2. A message box prompts you about compilation
3. Check the settings for compilation
4. Check the settings for Download
What you should know about downloading changes

In cases where plants change during operation but must not be set to STOP mode
under any circumstances, the possibility of downloading changes to them must be
ensured.
 If you want to ensure that your program retains its ability to download changes, you
should generate a backup copy after each completed download.
 See [302] PCS 7 CFC for SIMATIC S7 - Function Manual - 04_2012, 11.3 and 11.4
for more details about the system support for avoiding causes of CPU STOP
Downloading a modified program to a test CPU

With the option "Download to test CPU" in the S7 download dialog, you can download a
changed program for testing to a different CPU or to PLCSIM. The ability to download
changes is not lost.

PCS 7 System Course
7.4.9 Test mode
General settings for blocks
3
4
1. Toggle button for Test mode

2. Watch cycle, minimum is 1 second.
3. Switch to Watching on mode for the whole block
4. Switch to Watching off mode for the whole block
• Process mode: After switching on the Test mode, all blocks are in Watching off
mode.
• Laboratory mode: After switching on the Test mode, all blocks are in Watching on
mode.
General settings for I/Os
When a value is not Or click on the right to

displayed in test mode… perform an Add I/O…
…use the „mouse over“ to …to have the current value

have an info box displayed displayed continuously.
with the current value.
You can watch

In fact you are controlling a setting in the I/O properties. and alter the
setting there
You can also toggle the Watched status of a block I/O by “Ctrl + click”.

PCS 7 System Course
7.5 Organization blocks

Function Blocks (FBs) in a chart represent functions with a program. The program code
is to be executed in a regular way.
Organization Blocks (OBs) form the interface between the operating system of the CPU
and the application. Different OBs (numbers) can be used. To every OB belongs a
trigger from the operating system.
Blocks are to be assigned to at least one OB.
Every OB represents a Start Event, controlled by the operating system of the CPU.
Tasks
Our main group of OBs is the OB30s: OB30 … OB38.
They represent cyclic execution (on a regular time base).
OB Start event Priority

1 Free cycle 1
10...17 Time-of-day interrupt 2
OB10...17 OB20...23 20...23 Time-delay interrupt 3...6
30...38 Cyclic interrupt 7...15
40...47 Process interrupt 16...23
55...57 DPV1 interrupts 2
OB1 * OB30...38 60 Multi-computing 25
70...73 Red. error (H-CPU) 25
80...87 Async. error al. 26,28
S7 100,101 Startup 27
OS 121,122 Synchr. error al. like error-
generating
OB121,122 * OB40...47 OB
(See system software for S7-300/400,

System and Standard Functions)
** OB100,101 ** OB80...87
* User-/process-specific start event
** CFC-/block-specific start event
By assigning PCS 7 blocks to these Cyclic Interrupt OBs (settings for a Runtime group),
a designed time interval is achieved.
Startup behavior
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.
 ATTENTION!
Warm restart = Default setting for PCS 7 and normal applications
In some situations, the block behavior at startup must differ from the normal behavior. It
may e.g. be required to suppress alarm for a number of cycles after startup.
In that case, a block must additionally be assigned to a startup OB (OB100). Due to
settings on the level of block attributes, this kind of blocks will be installed in OB100 at
creation.

PCS 7 System Course
When you restart (warm restart) an S7-400 (for example by changing the mode selector
from STOP to RUN or by turning the power ON) organization block OB100 is processed
before cyclic program execution begins (OB 32 - OB 38). As default, all the PCS 7
blocks that have a special startup behavior are installed in OB100.
Cyclic interrupt OBs

The properties of the Cyclic Interrupt OBs can be watched via CFC’s Options menu:

PCS 7 System Course
7.6 Run Sequence

7.6.1 How to Adapt the Run Sequence
Principle of the run sequence

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.
Chart Installation Pointer
Task (OB)
Runtime
groups
2
1
3
1. For every chart a Runtime group (blue folder) is created in the Run Sequence,
containing the individual blocks per chart. It is assigned a cyclic OB. This is
important in PCS 7, because it ensures that the channel drivers and technological
blocks will be executed in the same cycle in a run sequence.
2. The green background color represents a pointer, controlling the position (after this
one) for the next new chart.
3. The pointer can be moved using the indicated menu option.
4. Runtime Groups can be moved by dragging, within an OB or to another OB.

PCS 7 System Course
Setting Installation Pointers

Installation pointers determine the installation position for the next unit of the run
sequence. These are the different pointers:
• Chart installation pointer
• Block installation pointer
Chart installation pointer Block installation pointer
Before defining as After defining as

predecessor predecessor
You can modify the installation pointers as follows:

• Chart installation pointer (default OB 35)
In the run sequence editor select the required OB or a block from the OB level (not
within a runtime group) or a runtime group within the OB.
Select the runtime editor menu command
Edit > Predecessor for Installation Position.
• Block installation pointer
You cannot set the block installation pointer in the runtime editor.
In the CFC editor select the block after which all other blocks are to be installed.
In the chart, select the menu command
Edit > Predecessor for Insertion Position.
If the block specified as the predecessor for installation is deleted, the block
installation pointer is set to the block installed before the deleted block. This also
applies if the block is moved to a different chart. The block installation pointer in the
destination chart is not changed. The moved block retains the installation position it
had in the previous chart.

PCS 7 System Course
7.6.2 Runtime properties

At inserting of a block into a chart, the block is assigned Runtime Properties. The block
will be installed in a Runtime group that is part of an OB sequence (Task).
Runtime groups are there to structure and split the tasks of an OB. They are
automatically created at the creation of a chart.
Every block header in CFC contains a green rectangle showing the runtime properties.
A double click in this rectangle shows the block position in the Run sequence (using the
Runtime editor).
7.6.3 Optimization of the Run sequence

Changes can be made to the order of program code execution of blocks:
Manual
Change the position of the block by dragging to the new position (installs behind the
block you are pointing to):

PCS 7 System Course
Automatic
This function is used to optimize the program run sequence according to the data flow in
order to reduce dead times to a minimum during program runtime in the CPU: so based
on connections between blocks. Tasks and runtime groups are optimized separately.
Uncheck the optimization

The option Optimize Run Sequence is valid for all blocks of all charts of the related
chart folder.
Single charts can be unchecked for this optimization process:
Optimize the full task,
including all enabled
runtime groups
Optimize only the

enabled runtime
groups of a task
Exclude the full task

- including its
runtime groups -
from optimization
Single charts can

be unchecked for
optimization

PCS 7 System Course
7.6.4 Runtime properties for experts: Activating/Deactivating runtime groups
Result in the CFC

Uncheck this box if editor: indication that
you don't want the the instances aren't
blocks installed within executed
this runtime group to
be executed
Result in the run

sequence editor:
indication that the
instances aren't executed
You can select/deselect the check box in order to enable/disable the runtime group for
processing, if it is not interconnected. An interconnection always has priority.
In the detail window of the runtime editor in the column "Inactive", the mode of the
runtime group is displayed.
• The name corresponds with that of the runtime properties field of a block.
• The character "!" means that the relevant runtime group is inactive.
• The character "?" means that the "EN" of the runtime group is interconnected or
accessed by SFC. Therefore the runtime group is not in static process mode (may be
active or inactive).
You can select or deselect the option for the selected runtime group, without initiating
the object properties using the shortcut menu commands:
Switch on Runtime Group and Switch off Runtime Group
Process Object view

It is also possible, to activate/ deactivate runtime groups in the PO-View in the SIMATIC
Manager. You can do this in the Tab „General“

PCS 7 System Course
7.6.5 Runtime properties for experts: Switching runtime groups on and off
during operation
Indication in the run

sequence editor
Indications in the
Indications
CFC editor in
the CFC editor
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.3.9 for more information
how to adapt the run sequence.

PCS 7 System Course
7.7 Different groups of blocks

The picture below shows the main groups of blocks that will appear in charts:
ES OS
Plantbus
Automation system (CPU)
PII Monitoring and PIQ

Controlling
Process Image Outputs

Process Image Inputs
Signal
Input drivers processing Output drivers
Input module Actuator

Output module
Process
Sensor
Input drivers Read values from the PII as process feedback, and offer them to outputs
to be read by other blocks inputs for processing.
Signal processing Processing values without users interference.
Monitoring and Controlling Monitoring and Controlling functions, including an interface to the
Operator Station. Block Icons and Faceplates in the OS offer information
about states and modes and allow process operations.
Output drivers Write values to the PIQ as the commands to the process.
Process Images
The Process Image Inputs (PII) and Process Image Outputs (PIQ) form the interface
between the signals from the I/O modules and the user program in the CPU of an AS.
Update
The transfer of values between the I/O modules and the Process Images is controlled
by properties (settings) on the CPU and the I/O modules.
The update of the information should be in the same rate as the signal processing.

PCS 7 System Course
7.8 Driver Blocks

7.8.1 General
Drivers form the interface between the process signals and the application.
They are a relevant part of the control loop:
ES OS
Plantbus
Chart
PII PIQ
Pcs7DiIn MotL Pcs7DiOu
4 5 6 7
PV_In PV_Out FbkRun Start PV_In PV_Out
8
3
M
2 1
1. The control signal from a channel of the output module is wired to the (control logic
of the) motor.
2. The feedback signal from the (control logic of the) motor is wired to a channel of the
input module.
3. The signals from the input module are transferred to the Process Image for Inputs
(PII), situated on the CPU.
4. The input driver reads the signal from the PII, and brings it into the chart to be
used by control blocks.
5. A control block reads the process value from the input drivers. Its logic will
generate one or more control signals.
6. The output driver reads the control signal from the control block.
7. The output driver writes the control signal to the Process Image for Outputs (PIQ),
situated on the CPU.
8. The control signals are transferred to the output module. The output module
converts them to proper electrical signals.

PCS 7 System Course
7.8.2 Digital Input and output
Process value
to be used by
control blocks
Signal from PII

(representing the input Input
from the process) driver
Control signal Signal to PIQ

from control block (representing the
output to the process)
Output
driver
7.8.3 Analog Input and Output
Signal from PII Process value

(representing the input to be used by
from the process) control blocks
Input
driver
Signal to PIQ
(representing the
output to the process)
Control signal
from control block
Output
driver

PCS 7 System Course
7.8.4 Module drivers

Module drivers are blocks created by the driver generator. This generator is activated by
default at the compilation of charts:
The driver generator …

• Finds an I/O module that belongs to the I/O address connected to the channel drivers
• Creates charts “@(1) … @(7)” with blocks (module drivers) for diagnosing
information when errors appear in the I/O circuits
• Makes connections between module drivers and channel drivers to supply the
channel drivers with information about the I/O modules.
Indicated above is one of the connections to the channel drivers.

This “line” offers diagnostic information to the channel driver, to be used in the
application.

PCS 7 System Course
 ATTENTION!
No changes are allowed to the system charts since these involve system functions
(indicated by "@"). This also applies to changes to the installation in OBs or runtime
groups.
 The content of runtime groups, created by the driver generator ("Generate Module
Drivers" @......) are not optimized since the correct order is already set here.
If optimization is executed after creating the module drivers, there is no guarantee
that the runtime groups of the driver blocks are in the order specified by the driver
generator. Therefore the module driver is restarted during the next compilation (the
"Create module driver" check box is activated).
Channel driver and Signal Status

After the generation of the module drivers, every channel driver will have connections to
a module driver. Through the connections diagnostic information is offered to the
channel driver.
The main output of the input driver, PV_Out is set up as a so called “structure”. It is
bundling the actual Process Value and the related Signal Status.
The Signal Status may have different values, and may finally result in icons displayed
on the Operator Station:

PCS 7 System Course
7.8.5 Process Image Partitions

The picture below shows an example of settings concerning the Process Image
Partitions.
3 CPU: OB32 > PIP2 OB33 > PIP3

4
4 PII Pcs7AnIn PIDConL Pcs7AnOu PIQ PIP2
T PIP2
I
AO4
AI8 1
Chart OB32 (1s) 5
5
PIP3
PIP3 Pcs7DiIn VlvL Pcs7DiOu
Pcs7DiIn
DO16
DI16
2
Chart OB33 (0,5s)
1. Assuming the function in the chart for a temperature control is to be processed

every 1 second. The chart is installed in the run sequence of OB32.
2. Assuming the function in the chart for a open/close valve control loop is to be
processed every 0,5 seconds. The chart is installed in the run sequence of OB33.
3. Setting has been made to the CPU, activating the PIP2 by OB32 and PIP3 by
OB33.
4. PIP2 is set in the properties of the input and output modules, whose signals are to
be transferred to and from the process images, triggered by PIP2 (related to OB32).
5. PIP3 is set in the properties of the input and output modules, whose signals are to
be transferred to and from the process images, triggered by PIP3 (related to OB33).
OB1
OB32 300ms 100 300ms 100

1000ms
OB33 200ms 200ms 200ms 200ms

500ms
0ms 500ms 1000ms time 1500ms 2000m
The time sequence diagram above indicates with the same colored arrows as the
picture before, on what moment the transfer is done of the signals from the I/O modules
to and from the Process Images.

PCS 7 System Course
Settings for CPU and I/O module

Below the settings concerning the Process Image Partitions, to be made on the CPU
and I/O module.
 ATTENTION!
Each change to the cyclic interrupt time of a CPU requires compilation of the program
and a download with STOP of the CPU.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.9.4.8 for more details

PCS 7 System Course
7.8.6 Symbolic Addresses

All I/O signals will be assigned absolute addresses at the moment the modules are
positioned in the station configuration of the AS (tool HW Config).
In general Symbolic addresses (short: Symbols) will be assigned to every I/O address. It
is stored per every AS in the so called Symbol table:
• Entering via HW Config:
1. Select the I/O rack containing the module whose
symbolic addresses you want enter. The editing
table will show the modules.
1 2. In the editing table, select the module and open the
context menu.
3. Select Edit Symbols …
4. Enter the Symbols and optionally the Comments.
When ready, click OK.
5. The symbolic names are added to the symbol table.
2
4
3
• Connection to the channel driver: It is strongly recommended to use symbolic names

for all I/O signal. This is the way how to connect to the channel drivers:
1. In this example a digital output channel driver is to be connected to an

address. Click right on the output PV_Out and select
Interconnection to Address …
2. A table shows the existing boolean

2 symbols. Select the required symbol.
3. The connection is displayed in CFC

as a line to the sheet bar, with all
3
information from the symbol table in
the table column.

PCS 7 System Course
7.8.7 Pcs7DiIn in brief
Obtaining the standard value

The digital value of the process image (partition) is sent to output parameter PV_Out
with the signal status 16#80.
Holding the last value if raw value is invalid

If the module is to hold the most recent valid value when the raw value is invalid, you
must activate this function on Feature bit 30 (Issuing last valid value if raw value is
invalid).
Output substitute value if raw value is invalid

If the module is to output a substitute value SubsPV_In when the raw value is invalid,
you must activate this function on Feature bit 29 (Issuing substitute value if raw value
is invalid).
Output of invalid value if raw value is invalid

If the module is to output an invalid value (PV_Out = PV_In), you must activate this
function on Feature bit 28 (Output invalid raw value).
This function is pre-selected.
Signal status for PCS7 channel blocks

The block provides the standard function "Forming and outputting signal status for
blocks".
Simulating signals
The block provides the standard function "Simulating signals".
 For more information on the signal status for PCS7 channel blocks, see
[113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.1.6.9
For more information on simulating signals, see

PCS 7 System Course
7.8.8 Pcs7AnIn in brief
Obtaining the standard value

The standard value (a physical quantity) is obtained from the raw value using
parameters Scale and Mode. Set two scale values on the structured parameter Scale.
• High scale value (Scale.High)
• Low scale value (Scale.Low)
The settings of the parameter Scale are copied to the output parameter ScaleOut.
The output parameter can be interconnected to a corresponding input parameter of a
technological block (e.g. PV_OpScale).
The standard value is obtained using a linear characteristic. Scale.Low is the lowest
physical value that the process variable can take and Scale.High is the highest.
If Scale.Low = 0 and Scale.High = 100 a percentage is obtained.
Holding the last value if raw value is invalid

If the module is to hold the most recent valid value when the raw value is invalid, you
must activate this function on Feature bit 30 (Issuing last valid value if raw value is
invalid).
You can also influence this function via the input parameter DeltaVal.
• DeltaVal ≤ 0: the last value is retained and is not influenced
• DeltaVal > 0: the last or the next to last value is output
If you set the parameter DeltaVal > 0, the last PV_Out(k-1) or next to last
PV_Out(k-2) valid output value is output (PV_Out(k) is the current value, k is the
current time).
At parameter DeltaVal you can preset a permitted process value change (PV_Out)
between two calls. You have the following options:
• For invalid raw values and DeltaVal > 0:
− If |PV_Out(k-1) - PV_Out(k-2)| > DeltaVal, then PV_Out =
PV_Out(k-2) (last but one valid output value is output)
− If |PV_Out(k) - PV_Out(k-1)| ≤ DeltaVal, then PV_Out = PV_Out(k-
1) (last valid output value is output)

PCS 7 System Course
• For valid raw values and DeltaVal > 0:

|PV_Out(k) - PV_Out(k-1)| > DeltaVal, so for one cycle PV_Out =
PV_Out(k-1) is output, i.e. DeltaVal is used to limit the change made to the valid
raw value. In addition, the signal status at the output parameter PV_Out is set to
16#60 and the output parameter is set to Bad = 0.
The value of DeltaVal should be selected with due care. If the value is too low, the
quality code may flutter between16#80 and 16#60, regardless whether or not the raw
value is OK.
Output substitute value if raw value is invalid

If the module is to output a substitute value SubsPV_In when the raw value is invalid,
you must activate this function on Feature bit 29 (Issuing substitute value if raw value
is invalid).
Output of invalid value if raw value is invalid

If the module is to output an invalid value (PV_Out = PV_In), you must activate this
function on Feature bit 28 (Output invalid raw value).
This function is pre-selected.
Value acceptance delay

After a restart, or if the output parameter Bad changes its value from 1 to 0, the signal
status and the value of output parameter PV_Out are not updated until the number of
cycles for delayed acceptance of the value (input parameter CountLim) have elapsed.
During the value acceptance delay the signal status at the output parameters is PV_Out
= 16#00 and Bad = 1. The last value is retained during the value acceptance delay. If
CountLim = 0, the function is deactivated.
Signal status for PCS7 channel blocks

The block provides the standard function "Forming and outputting signal status for
blocks".
Simulating signals
The block provides the standard function "Simulating signals".
 For more information on the signal status for PCS7 channel blocks, see
For more information on simulating signals, see

PCS 7 System Course
7.9 Trend Display

The CFC editor has a build in tool for trending. It is available for short term trending
during commissioning and trouble shooting.
A maximum of 12 values can be recorded at one time.
7
2
1. From CFC’s View menu, select Trend Display.

2. The Trend Display window will share the work area of CFC with the chart windows.
Add, delete and rename a Trend Display. Make a proper arrangement of the
windows.
3. Choose suitable recording parameters: number of values (10 …16000), acquisition
cycle (1 …9 s, 10 … 90 s) and Recording mode.
4. Use dragging to assign any input or output of a block to each of the up to 12
channels of a Trend Display. Values from several blocks and from several charts
can be assigned.
5. Set the High and Low limit values to fit the vertical axis (for each channel).
When Boolean values are used, a predefined range in the vertical axis is used per
channel to display the values false and true. Determine the number of values to be
displayed in the horizontal direction.
6. The "Start" button is active only in test mode. After starting, the start button changes
into a “Hold” button and is relabeled accordingly. You can then use it to stop
recording at any time.
7. Export the stored data to a file. You should check the settings for export using the
menu command
Options > Customize > Export Trend Data

PCS 7 System Course
7.10 Dynamic Display

Similar to the Trend Display, the Dynamic Display can be used in CFC test mode. It
offers a table that can have values of several blocks of several charts. All values can be
watched, and values of inputs without connection can be changed.
1. From CFC’s View menu, select Dynamic Display.

2. The Dynamic Display window will share the work area of CFC with the chart
windows. Make a proper arrangement of the windows and use dragging to assign
any input or output of a block to a line of a Trend Display.
3. Add, delete and rename Dynamic Displays.
Task: Drivers for the Signal Box
Goal
4 charts containing drivers for the I/O signals of the Signal Box.
Checkpoint
Let us summarize …
• Why have the @(..) charts
appeared in the Charts folder?
• What is the use of it?

PCS 7 System Course
7.12 Connection to the Process simulation in this training

7.12.1 Method in this training
There are several reasons that we do not offer you a real process for practicing.
A suitable process simulation will replace it, offering you I/O to represent a process in
work.
The picture below gives you an impression of the relationship between process I/O and
the application running in the automation system, and the simulation representing the
process.
Hardware Software
I/O Modules Driver blocks
Process
AI
images
Control block
Pcs7AnIn
AO
Process Pcs7AnOu
DI
Process value
Motor block
Name Pcs7DiIn
DO
Pcs7DiOu
Johnsson
Process
simulation
Symbol table
The process simulation (running in the CPU as a Function Block) is using the original
Process Image as an interface to the application software in the automation system.
This makes it possible for you to configure functions with channel drivers, similar to real
applications.
The symbol table contains the corresponding signal names for the process values in the
Process Image and their addresses. These addresses should not overlap the addresses
of the real hardware.

PCS 7 System Course
Example for V311

Here you see the simulated valve V211 (D210 Dose tank inlet valve 1) as an example
and a part of the process simulation:
4
Johnsson
V311_O Pcs7DiIn VlvL block Pcs7DiOu
V311 3
1 V311_C Pcs7DiIn
2 V311
Process
images
1. Simulation of V311, as a part of the Johnsson plant simulation. It is running in a

single function block on a chart called “@Johnsson”. This chart should only be
present in the Charts folder of your AS.
2. Control signal to the valve, using the valve tag name as the symbolic name
3. Feedback signals formed by limit switches:
− “V311_O” = opened
− “V311_C” = closed
4. A chart with a minimum of blocks to control and monitor the block. This chart is to
appear in the plant hierarchy.
7.12.2 Overview
The number of I/O is based on the devices in the plant.
The following table gives an overview of the number of devices and the related I/O:
number DI DO AI AO
open-close valves 25 50 25
status valves 5 5
motors 11 11 11
level measurement 13 13
temperature measurement 4 4
control valve 4 4 4
total 62 66 36 21 4
number of channels per module 16 16 4 4

number of modules 4,125 2,25 5,25 1
lowest address I 100.0 Q 100.0 IW 208 QW 208

highest address I 110.5 Q 105.1 IW 258 QW 214

PCS 7 System Course
7.12.3 Digital Inputs
signal address data type description

name
V111_O I100.0 BOOL M110 Material tank Inlet valve Feedback Opened
P113_O I100.1 BOOL M110 Material tank Outlet pump Feedback On
V112_C I100.2 BOOL M110 Material tank Outlet valve Feedback Closed
V112_O I100.3 BOOL M110 Material tank Outlet valve Feedback Opened
V211_C I102.0 BOOL D210 Dose tank Inlet valve 1 Feedback Closed
V211_O I102.1 BOOL D210 Dose tank Inlet valve 1 Feedback Opened
V311_C I106.0 BOOL R310 Reactor Inlet valve Feedback Closed
V311_O I106.1 BOOL R310 Reactor Inlet valve Feedback Opened
P313_O I106.2 BOOL R310 Reactor Outlet pump Feedback On
V312_C I106.3 BOOL R310 Reactor Outlet valve Feedback Closed
V312_O I106.4 BOOL R310 Reactor Outlet valve Feedback Opened
M316_O I106.5 BOOL R310 Reactor Stirring motor Feedback On

PCS 7 System Course
signal address data type description

name
V411_C I110.0 BOOL B410 Buffer tank Inlet valve Feedback Closed
V411_O I110.1 BOOL B410 Buffer tank Inlet valve Feedback Opened
V412_O I110.2 BOOL B410 Buffer tank Outlet valve Feedback Opened
V421_C I110.3 BOOL B420 Buffer tank Inlet valve Feedback Closed
V421_O I110.4 BOOL B420 Buffer tank Inlet valve Feedback Opened
V422_O I110.5 BOOL B420 Buffer tank Outlet valve Feedback Opened
7.12.4 Digital Outputs

signal name address data type description
P113 Q100.0 BOOL M110 Material tank Outlet pump
V112 Q100.1 BOOL M110 Material tank Outlet valve
V211 Q101.0 BOOL D210 Dose tank Inlet valve 1
V311 Q103.0 BOOL R310 Reactor Inlet valve
P313 Q103.1 BOOL R310 Reactor Outlet pump
V312 Q103.2 BOOL R310 Reactor Outlet valve
M316 Q103.3 BOOL R310 Reactor Stirring motor
V411 Q105.0 BOOL B410 Buffer tank Inlet valve
V421 Q105.1 BOOL B420 Buffer tank Inlet valve

PCS 7 System Course
7.12.5 Analog Inputs

signal name address data type description low range high range unit
LT114 IW208 WORD M110 Material tank Level 0 6000 kg
LT214 IW216 WORD D210 Dose tank Level 0 400 kg
LT314 IW224 WORD R310 Reactor Level 0 700 kg
TT315 IW226 WORD R310 Reactor Temperature 0 200 degr C
CV315_X IW228 WORD R310 Reactor Temperature control valve feedback 0 100 %
position
position
position
position
LT414 IW256 WORD B410 Buffer tank Level 0 12000 kg
LT424 IW258 WORD B420 Buffer tank Level 0 18000 kg
7.12.6 Analog Outputs

signal name address data type description low range high range unit
CV315 QW208 WORD R310 Reactor temperature control valve 0 100 %

PCS 7 System Course
Task: Installing the process simulation
Goal
A running process simulation of the Johnsson plant.
After this task the functions for the plant can be configured.
Checkpoint
Consider …
• What is the use of channel driver
blocks, why not just connecting to
the I/O addresses?

PCS 7 System Course
Content 8
8 Basics control functions......................................................................................... 3
8.2 Introduction to APL blocks ......................................................................................................4
8.2.1 Structures and Signal Status (ST) ..........................................................................................5
8.2.2 Interconnecting structured and elementary parameters (REAL or BOOL).............................8
8.2.3 Inverting interconnected structured input parameters ............................................................9
8.2.4 Feature Parameters..............................................................................................................10
8.2.5 Monitoring the feedbacks......................................................................................................11
8.2.6 Error handling .......................................................................................................................12
8.2.7 Units in the APL ....................................................................................................................13
8.2.8 MonAnl – Monitoring of an analog process tag (Large) .......................................................14
8.2.9 MotL – Motor (Large) ............................................................................................................15
8.2.10 VlvL – Valve (Large) .............................................................................................................18
8.2.11 PIDConL – Continuous PID controller (Large) .....................................................................20
8.2.12 Comparison of Large and Small blocks................................................................................24
8.2.13 Templates .............................................................................................................................24
8.3 Textual interconnections.......................................................................................................26
8.5 Alarm blocks in PCS 7 ..........................................................................................................29
8.6 Process Object View.............................................................................................................31
8.6.1 Efficient engineering with the Process Object View .............................................................31
8.6.2 Configuration of the columns in the Process Object View....................................................32
8.6.3 Order of the columns ............................................................................................................33
8.6.4 Defining your own columns...................................................................................................33
8.6.5 Defining the contents of the "Parameters" and "Signals" tab ...............................................34
8.6.6 Setting the "Parameter" or "Signal" attribute for multiple I/O's .............................................35
8.6.7 Dividing a table .....................................................................................................................35
8.6.8 Filtering .................................................................................................................................36
8.6.9 Export and import data using the Process Object View .......................................................37
8.6.10 Copy and Paste in the PO View ...........................................................................................38
8.6.11 Copy and Paste to and from Microsoft Excel .......................................................................38
8.6.12 Open exported Data in Microsoft Excel ................................................................................39
8.6.13 Task and Checkpoint ............................................................................................................39
SIMATIC PCS 7 – Basics control functions

PCS 7 System Course

PCS 7 System Course
8 Basics control functions


• The templates that are available as
a base for setting up the basic
automation tasks
• The manual control mode for the
initial testing of every loop

• Configure and test basic control
functions to devices in the plant,
based on the templates of the
PCS 7 AP Library

PCS 7 System Course
8.2 Introduction to APL blocks

The PCS 7 Advanced Process Library (APL) is a block library for PCS 7 being
introduced in PCS 7 Version 7.1.
It principally contains all blocks and functions of the former PCS 7 Standard Library.
It also offers additional functions in existing blocks as well as completely new blocks.
The PCS 7 Standard Library, however, is still available. It is also possible to use both
libraries at the same time (i.e. use blocks from both libraries in a CFC).
PCS 7 Basis Library V8.0
Diagnostic Drivers
e.g. MOD_1
PCS 7 Advanced
PCS 7 Library V7.1 Process Library V8.0
Only correct
versions are
able to
cooperate!
Technological functions Technological functions
ChnBlocks for PCS 7 V8 Channel Drivers Version 7
Operation and Control Operation and Control
• Because the PCS 7 Standard Library and the PCS 7 APL can be installed either
separately or together, shared blocks are stored in the PCS 7 Basis Library. This
consists largely of driver blocks.
The PCS 7 Library is not available anymore as V8.0 with the release of PCS 7 V8.0.
The PCS 7 Library V7.1.3 is also no longer installed automatically via the frame
setup. It is provided in the directory "Additional Products" on the PCS 7 V8.0 DVD
and can be installed manually by the user if required.
• Only a single interconnection for transfer of process value and signal status is still
required.
In the PCS 7 Standard Library, the signal quality is provided as a quality code along
with the process values. This also had to be connected to the signal.
In the PCS 7 Advanced Process Library this philosophy was implemented
consistently in the form of structures. Almost every connectable parameter of an APL
block is a structure. In this way, the signal status could be carried via
interconnections of the process signals. Only a single interconnection is still required.
The operator can recognize the signal status (i.e.quality) of the signals by means of
the symbols in the APL block icons and APL faceplates.
• Configurable response using the Feature I/O
The PCS7 APL introduces what is known as the feature parameter. This parameter is
available to most blocks as an input feature and allows various block behaviors to be
set. For example, application-specific startup characteristics of motors can be set.
Using the feature parameter, industry and customer-specific requirements can be
implemented flexibly and subsequently adjusted.

PCS 7 System Course
8.2.1 Structures and Signal Status (ST)

A new feature of APL is the use of structures. Each process interconnectable parameter
of a block is of the Structure type. This structure consists at least of 2 bytes, whereby at
least one byte determines the actual value (e.g. type BOOL) and one byte characterizes
the signal status (ST) of the transferred signal.
Analog Value [STRUCT]: Value [REAL] +1 Byte Signal Status (ST) [16#...]
Binary Value [STRUCT]: Value [BOOL] + 1 Byte Signal Status (ST) [16#...]
The following figure shows interconnectable parameters in the CFC and their structure.
Analog value
Binary value
The following figure compares how the Signal Status is implemented in the PCS 7
Standard Library and the PCS 7 APL:
PCS 7 Standard Library

Value
Quality
code
Structure
PCS 7 APL • Value
• Status

PCS 7 System Course
The Signal Status Concept (symbol, value status, priority…) fulfils the standard
specification according to PA – Profile PROFIBUS & PROFINET international.
The Signal Status (ST) is displayed in different locations as symbols or hexadecimal
values:
Symbol Priority Hexadecimal value Value status
0 16#60 Simulation
1 16#00 Bad, device-related
2 16#28 Bad, process-related
3 16#68 Uncertain, device-related
4 16#78 Uncertain, process-related
5 16#A4 Maintenance request
6 16#80 Good
In technological blocks, a group status is formed from the input parameters (see
description of the relevant blocks) according to the priority table below.
Note: Priority „0“ is the highest priority, “6” the lowest.
This group status is displayed in the status bar of the faceplate and of the block icon.
 ATTENTION!
If “Last valid value” or “substitute value” has been configured at the channel driver
and a channel error occurs, the signal status (ST) receives the value 16#60 instead of
16#00. I.e. the symbol for “Simulation” instead of “bad device-related” is displayed on
the PCS 7 OS.
Structures and effect of the Signal Status

If process values are connected via a channel driver (Pcs7AnIn, Pcs7DiIn, Pcs7DiOu,
etc.) directly with the technological function block (e.g. MotL), the Signal Status is
displayed directly in the faceplate.
For other blocks such as And04 or Or04 the Signal Status is passed on to the output
according to a logic.
When the Signal Status of the outputs is formed the following is taken into
consideration:
• If any input of a gate causes a signal change at the output, the worst Signal Status of
the input must be taken as every signal can influence the output.
• If several inputs have equal priority with the effect that the output cannot change,
these inputs will take the best Signal Status as the output is clearly defined by this
signal.

PCS 7 System Course
The result is based on the following rules:
Worst Signal Status,

Symbol Priority
but highest priority
Rule for Operation AND:
• If the actual value of the binary output is "1", the Signal Status of the output gets 0
the worst Signal Status of all interconnected inputs.
the best Signal Status of all interconnected inputs, which have a value of 0.
2
And04 In1 In2 In3 In4 Out
Value 0 0 0 0 0 3
ST 16#80 16#80 16#28 16#00 16#80
Value 1 1 1 0 0
ST 16#80 16#80 16#80 16#28 16#28 4
Value 1 1 1 1 1
ST 16#80 16#80 16#28 16#00 16#00 5
Best Signal Status,

6
but lowest priority
Worst Signal Status,

Symbol Priority
but highest priority
Rule for Operation OR:
0
• If the actual value of the binary output is "1", the Signal Status of the output gets
the best Signal Status of all interconnected inputs, which have a value of 1.
the worst Signal Status of all interconnected inputs.
2
Or04 In1 In2 In3 In4 Out
Value 0 0 0 0 0 3
ST 16#80 16#80 16#28 16#00 16#00
Value 0 0 0 1 1
ST 16#80 16#80 16#80 16#28 16#28 4
Value 1 1 1 1 1
ST 16#80 16#80 16#28 16#00 16#80 5
Best Signal Status,
but lowest priority 6
The Signal Status has a direct effect on the function of the technological block with the
parameters Trip and the three interlocks (Permit, Intlock, Protect). If there is a bad
Signal Status (16#00 or 16#28), it has the same effect like a process value = 0.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.1.6 for more details on
formation of the Signal Status.

PCS 7 System Course
8.2.2 Interconnecting structured and elementary parameters (REAL or BOOL)

For the interconnections between structured and elementary parameters (e.g. blocks
from the Standard Library), so-called conversion blocks are available in the APL. This
involves blocks for converting:
StruAnIn separating an analog structured StruAnOu creating an analog structured variable

variable
StruDiIn separating a digital structured StruDiOu creating a digital structured variable
variable
StruScIn separating a display area into two StruScOu merging two variables into a display
variables area
STIn separating the signal status into STOu merging individual binary signals into
individual binary displays a signal status
MSTIn separating the maintenance status MSTOu merging individual status displays into
into individual status displays a maintenance status
PCS7 V7.1 (APL V7.1 and APL V7.1 + SP1)
Structure BOOL and ST

(BOOL + ST) Parameter
PCS7 V8.0 / V7.1 + SP1 (APL V7.1 + SP3)
Structure Only BOOL

(BOOL + ST) Parameter

PCS 7 System Course
8.2.3 Inverting interconnected structured input parameters
PCS7 V7.1 (APL V7.1 und APL V7.1 + SP1)
PCS7 V8.0 / PCS7 V7.1 + SP1 (APL V7.1 + SP3)
New as of PCS7 V7.1 + SP1

Interconnected inputs of the data type STRUCT with the element "Value" of the data
type BOOL and the second element "ST" of the data type BYTE can be inverted directly
at the connection, such as inputs with the elementary data type BOOL.

PCS 7 System Course
8.2.4 Feature Parameters
In the APL most blocks have a Feature input parameter. This input can be used to
influence the way in which the block works. The Feature parameter enables the
manufacturer to realize sector-specific customer requirements as well as adjust them
afterwards. Furthermore, function expansions can be integrated retrospectively via this
parameter.
It is a structure which consists of 32 Boolean elements which can be used for setting
various behaviors at the block. For the 32 Boolean elements there are pre-assigned bits
and reserve bits. The reserve bits can be assigned by the manufacturer (Siemens) at a
later point in time.
The configuration of the individual bits of the feature parameter occur by double-clicking
the "Feature" input at the block (offline/online) as displayed above. Normally, the feature
bits should be configured in the Master Data Library in order to achieve consistency in
the multi-project.
 Any change of settings on the feature parameter does not influence the block
interface. This allows modifying the block behavior without CPU stop. Advantages of
the reserve bits: Block changes can be loaded without CPU stop. The original block
behavior can further be used.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011,

1.1.10 for configurable functions with the Feature I/O (Assignment of Feature-Bits).

PCS 7 System Course
8.2.5 Monitoring the feedbacks

The effectiveness of control signals is not of course known to a technological block.
Feedback input parameters allow to include the effectiveness of the control signal into
the internal logic of a technological block.
You can use the following monitoring functions:
Monitoring the start-up and stop characteristics for motors or the runtime of valves
Monitoring of the startup characteristics is implemented using the parameter
MonTiDynamic.
The monitoring time specifies the period within which the feedback value, for example,
FbkStart with motors, must be available in response to a control signal. If this is not
the case, the text "Feedback error" is displayed in the standard view of the faceplate. An
error message is generated at the same time.
The block then goes to its neutral position. In the case of motors, this is always the stop
state. With other blocks, this is an neutral position you have specified (SafePos
parameter). The block signals this at the corresponding output parameter of the error
message with 1, for example, with MonDynErr = 1 for motors.
Parameters are set in seconds.
Monitoring the operation of motors or the maintenance of the position of valves

Monitoring of the operation or the maintenance of the position of valves is implemented
using the parameter MonTiStatic. The monitoring time specifies the period in which
the feedback value can change its value briefly without an error message being output.
An example would be a running motor with the feedback via the input parameter
FbkStart. This parameter should be static in accordance with the control function.
Parameters are set in seconds.
 Please note that

MonTiDynamic ≥ MonTiStatic and MonTiDynamic ≥ SampleTime
have to be configured. If something is set outside these limits, the block always
returns the respective limit at the input.
Disabling the monitoring

You can enable/disable monitoring of the feedback.
This monitoring function is enabled via the Monitor = 1 input.
Static and dynamic errors are reset by disabling the monitoring (Monitor = 0). If you
reactivate monitoring during the plant runtime, only dynamic monitoring
(MonTiDynamic) will be performed.
Disabling feedback
You can operate a block without feedback. To do this, set the NoFbkxxx = 1 parameter,
whereby xxx stands for the respective function, for example, NoFbkOpen for the valve.
This means, for example, that you do not have any feedbacks for the opened state of
the valve. Monitoring is thus disabled for this feedback. The feedback at the block is
adjusted according to the control signal.

PCS 7 System Course
8.2.6 Error handling

The channel and technologic blocks feature error handling routines. A distinction must
be made between the following areas:
• Error numbers
• External process control fault (CSF)
• Process-specific errors
• Invalid signal states
• Mode switchover error
• Errors in channel blocks
External process control fault (CSF)

An external process control fault always lies outside the process - it exists in the form of
device or other hardware faults. If, for example, a run-time error occurs at a valve, there
is an error or fault in the pneumatic system.
A process control fault is output if an external fault is set at the input CSF. You can
enable this output function, for example, by interconnecting output Bad of the channel
block with input CSF of the technologic block.
The error does not affect the internal logic of the technological block. Several sources
(e.g. Bad outputs of several channel driver blocks) may be included by digital logic
blocks (e.g. OR04).
Error numbers
Most blocks have an output parameter ErrorNum that can be used to output internal
error states of the block as error numbers.
If the block algorithm detects inconsistencies between associated I/Os, an error number
is output that depends on the block type. The close and open commands cannot be
output simultaneously to the valve, for example.
Outputting group errors

The GrpErr output parameter assembles the faults of a block and makes them
available to you. A group error is compiled from the following error information:
• Feedback errors (static or dynamic feedback monitoring)
• External errors
• Motor protection (only for motors)
• Module errors (only for hardware controllers)
• I/O access errors (only for hardware controllers)
• Parameter assignment errors (only for hardware controllers)
How the signal is formed for the group error at the GrpErr output parameter, depends
on the corresponding block.
 The signal status of the individual signals is not taken into consideration for forming
the group error. The outputs therefore always have the status, 16#80.

PCS 7 System Course
8.2.7 Units in the APL
See online help for a complete list of available units
Unit output for

interconnecting
with other blocks
The APL-specific procedure for setting the unit for analog signals shall be illustrated at
the example of both blocks “Pcs7AnIn” (channel driver) and “MonAnL” (limit value
block).
The unit is represented by means of an identification number at the input PV_InUnit.
 Data type, possible identification numbers see Help on the “MonAnl” block under the
keywords “Functions of MonAnl, select unit”.
Number “1342” for example represents the unit “%”. The input channel driver forwards
the unit of "PV_InUnit" to its output "PV_OutUnit". By interconnection to the
"PV_Unit" connection of the limit block the unit “%” is then displayed in the
visualization of the limit value block.
 If PV_Unit input of the “MonAnl” is configured with 0, the unit can also be specified
according to the current method (attribute “S7_unit” of this connection or in the CFC
the “Unit” column of this connection in the Properties table of the “MonAnl”
connections). Not listed units can be used this way.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.1.13.5 for more
details.

PCS 7 System Course
8.2.8 MonAnl – Monitoring of an analog process tag (Large)
The block is used for the following fields of applications:

• Monitoring an analog process process value, e.g. from a channel driver block
• Monitoring of the gradient of an analog process value
How it works
The MonAnL block is used to monitor an analog process tag and the corresponding
limits. It also monitors the gradient of these signals. The block generates and outputs
corresponding messages if limits are violated or if a signal gradient does not meet
requirements.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.1.4.1 for more
information about Process value monitoring and 3.3.3 for more information about
Gradient monitoring

PCS 7 System Course
8.2.9 MotL – Motor (Large)

The functionality of the motor block MotL can be compared with the motor block FB66 of
the PCS7 standard library. It is used to control motors with one control signal
Manual mode/automatic mode changeover

The changeover can be carried out either by the operator on the OS or automatically via
the connection in CFC/SFC. The inputs "ModLiOp - AutModLi - and ManModLi" are
available at the MotL block for the changeover in CFC/SFC.
The selected mode is displayed in the faceplate on the OS. The block outputs AutAct
and ManAct are available for requesting the mode in a logic CFC/SFC.

PCS 7 System Course
ON - OFF control in the automatic mode

If the automatic mode was preselected (AutAct =1) the drive can be switched on or off
with a logic in CFC or via the SFC. The two block inputs StartAut and StopAut are
available for control. Whether either inputs are used or only the input StartAut is used
for the control is determined via the Feature Bit 4 "Switch or button mode":
• Switch mode (Feature Bit 4=1)
In the switch mode the drive is switched on and off via the input StartAut. The input
StopAut has no function in the switch mode.
• Button mode (Feature Bit 4 = 0)
In the button mode the motor is switched on via the input StartAut = 1. The motor
is switched off via the input StopAut = 1. Both inputs must not have the actual value
"1" at the same time. A 1 at both inputs will be displayed on the OS and indicated at
the MotL block at the output ErrorNum with "51".
Switching the drive on and off can only be carried out though if the respective enables
exist and/or no interlocks are active (Permit, Interlock, Protect).
Warning times
Warning times for motors can be parameterized at the function block. The output
WarnAct can be used, e.g. to control a signal lamp or a horn. Workers can be warned
about the imminent start of the respective drive with these warning signals.
Warning times can be configured separately for the hand mode and the automatic
mode:
• Hand mode Input parameter WarnTiMan (unit is second)
• Automatic mode Input parameter WarnTiAut (unit is second)
If WarnTiMan or WarnTiAut have been configured with 0, the output WarnAct will not
be activated in the respective mode and therefore no warning will be given then.
The configuration of warning times causes a time delay of the actual start command by
the parameterized warning time.
Idle Time
The input parameter IdleTime is used as waiting time (in seconds) for a restart of the
motor block. If a running motor is switched off, it will only be possible to restart it after
this time has elapsed. This switch-on interlock is active in the hand mode and automatic
mode and with StartForce.
If in the local mode the drive is controlled via the block and not directly via the switching
station, the switch-on interlock is active here as well.
 If the value "0" has been parameterized for the IdleTime, the respective functions
are deactivated.

PCS 7 System Course
Monitoring times
For the blocks of the Drives family of blocks there are two independent monitoring times
available for the feedbacks:
• MonTiDynamic
If a command for motor control is given and there is no feedback within the
parameterized time, an error message will be generated. The block output
MonDynErr will assume the actual value "1".
• MonTiStatic
If the feedback FbkRun of the motor changes during runtime, e.g. through vibrations
of the limit switch and if this interruption exceeds the set time, an error message will
be generated. The output parameter MonStaErr will assume the actual value "1".
Block outputs for drive control

There are 4 outputs available at the MotL block for motor control and warning device
control. The signal curves of the block outputs are shown in the following diagram as an
example.
The following time values have been parameterized at the MotL block:
WarnTiMa = 3s, WarnTiAu=3s and IdleTime = 20s
AutAct
StartAut
WarnAct
Start
P_Start
P_Stop
IdleTime
Forcing of the ON or OFF state

Adverse process states (e.g. overpressure) can require that drives are switched on or
off even if there are no enables or against the interlocks. There are two Force inputs
available for this.
• Forcing motor ON StartForce = 1
• Forcing motor OFF StopForce = 1
 With the PCS 7 it is not intended that other blocks will be inserted between the plant
block and the output driver.
If you deviate from this principle, ensure that when interconnecting the block, that
from the outputs of the plant block until the output driver, that all blocks that form the
output signal are installed in the same OBs.

PCS 7 System Course
8.2.10 VlvL – Valve (Large)
The VIVL block serves to control a valve in two positions (OPEN/CLOSE) with
adjustable safety position.
The valve is opened or closed via a control signal. The control is monitored through the
position signals OPEN/CLOSED (feedbacks). Non-existing feedbacks can be derived
from the control in the block.
Some block I/Os of the valve block are described in the following.
Manual mode/automatic mode

The changeover of the operating mode is equivalent to the motor block. The inputs
"ModLiOp - AutModLi - and ManModLi" are available in CFC/SFC.

PCS 7 System Course
Open - Close control

The two block inputs OpenAut and CloseAut are available for control in the automatic
mode. Whether both inputs are used or only the input OpenAut is used for the control is
determined via the Feature Bit 4 (button mode or switch mode) like with the motor
block.
Opening or closing the valve can only be carried out though if the respective enables
exist and/or no interlocks are active (Permit, Interlock, Protect).
Warning times and monitoring times

Warning times can be configured for the valve block like for the drive blocks separately
for the hand mode and automatic mode:
• Hand mode: Input parameter WarnTiMan (unit is second)
• Automatic mode: Input parameter WarnTiAut (unit is second)
If WarnTiMan or WarnTiAut has been configured with 0, the output WarnAct will not
be activated in the respective mode and therefore no warning will be given then.
The configuration of warning times causes a time delay of the actual command by the
parameterized warning time.
The monitoring times which are already known from the motor block are also available
for the valve.
Forcing of operating states

Like with motors it may become necessary with valves to open or close them against
enables or interlocks. There are two Force inputs available for this:
• Forcing valve OPEN OpenForce = 1
• Forcing valve CLOSE CloseForce = 1
Safety position
The safety position (open or closed) can be parameterized through the parameter
SafePos:
• SafePos = 0: With Ctrl = 0 the valve drive closes and with Ctrl = 1 it
opens (power-off position "Close")
• SafePos = 1: With Ctrl = 0 the valve drive opens and with Ctrl = 1 it closes
(power-off position "Open").
 With the PCS 7 it is not intended that other blocks will be inserted between the plant
block and the output driver.
If you deviate from this principle, ensure that when interconnecting the block, that
from the outputs of the plant block until the output driver, that all blocks that form the
output signal are installed in the same OBs.

PCS 7 System Course
8.2.11 PIDConL – Continuous PID controller (Large)

The block is a PID controller with continuous output signal (manipulated variable). It is
used to activate a final controlling element with continuous action input.
The block functions following the PID algorithm with a delayed D action and an
integrator with double precision.
“Main circuit”
PIDConL
Logic for
Internal / External
setpoint mode
Deadband
Gain
SP_Ext TI
External
SP_Int TD
Internal
…….
+
PV PID
- Auto MV
Manual
Man
Logic for
Manual / Auto
mode
Logic for Internal / External Logic for Manual / Auto mode

setpoint mode
SP_LiOp ModLiOp
SP_ExtLi AutModLi
S S
SP_ExtOp AutModOp
1 1
SP_IntLi ManModLi
R R
SP_IntOp ManModOp
Feature.Bit4: Feature.Bit4:
0 = Button mode 0 = Button mode
1 = Switch mode 1 = Switch mode

PCS 7 System Course
"Manual" and "Automatic" modes for control blocks

In "manual mode", the control settings for the device are made manually by the
operator. The operator decides how to change the block's manipulated variable (output
signal). The manipulated variable can be analog or binary.
In "automatic mode", the control settings for the controller are made automatically as
calculated by the control algorithm.
Changing between operating modes

The switchover between manual and automatic modes takes place as shown in the
following schematic:
• Switchover initiated in the faceplate (ModLiOp = 0): The changeover between
operating modes is carried out in the standard view of the faceplate. In the function
block, the parameters ManModOp for "manual mode" and AutModOp for "automatic
mode" are used.
If both signals (ManModOp =1, AutModOp = 1 ) are set, ManModOp = 1 has priority.
• Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1): The
switchover between the operating modes is carried out with an interconnection on the
function block. The parameters ManModLi for "manual mode" and AutModLi for
"automatic mode" are used in pushbutton operation. In switch mode (requirement:
Feature Bit 4 = 1) connection ManModLi is used exclusively.
If both signals (ManModLi =1, AutModLi = 1 ) are set, ManModLi = 1 has priority.
Setpoint specification internal & external

First you define whether the setpoint specification is to be carried out by means of a
CFC/SFC program or by means of the faceplate. In the next step you specify whether
the internal or the external setpoint is to be used.
• Setpoint specification by means of faceplate or interconnection:
With the SP_LiOp parameter, you define whether the setpoint will be set by a
CFC/SFC program or using the faceplate.
− Parameterize Sp_LiOp with 0 so that the setpoint specification is carried out by
means of the faceplate.
− Parameterize SP_LiOp with 1 so that the setpoint specification is carried out by
means of a CFC / SFC program.
• Setpoint specification internal & external:
You have to set the corresponding parameters depending on how the setpoint
specification is to be carried out.
If the setpoint is set in the faceplate (SP_LiOp = 0), you have to set the parameter:
− SP_IntOp = 1 in order to achieve an internal setpoint specification by means of
the faceplate.
− SP_ExtOp = 1 to have an external setpoint set in the faceplate.
If both signals are set, SP_IntOp = 1 has priority. If the setpoint is set by a CFC /
SFC program (SP_LiOp =1), you have to set the parameter:
− SP_IntLi = 1 to have an internal setpoint set by a CFC / SFC program.
− SP_ExtLi = 1 in order to achieve an external setpoint specification by means
of a CFC / SFC program.
If both signals are set, SP_IntLi = 1 has priority.

PCS 7 System Course
Program mode for closed-loop controllers - interface for higher-level control functions
The interface for primary controller functions (external Advanced Control software
package) provides primary controller functions, which run on an external PC as an OPC
client, the option of using the control from the controller function block and specifying
the setpoint or manipulated variable from a remote location. This procedure is called
program mode.
You can use the Feature bit 19 (Enabling program mode) to specify whether or not the
controller block is intended for program mode.
Program mode requires an enable signal (input parameter AdvCoEn = 1) from a central
control block. If this enable signal goes from 1 to 0, for example, due to errors in the
OPC communication, the controller block returns to the operating mode it had before
program mode.
Selecting the type of program mode

There are two types of program mode:
• Program mode with setpoint (in automatic mode only).
If you set the input parameter AdvCoModSP = 1, the analog value provided by the
OPC client (AdvCoMV) is used as an external setpoint for the controller. The
controller and faceplate otherwise react as they do with automatic mode and an
external setpoint. Refer to section Setpoint input - internal and external for more
about this.
Requirements for program mode with setpoint:
− AdvCoModSP = 1,
− AdvCoEn = 1,
− The controller is in automatic mode.
• Program mode with manipulated value (in manual mode only, not for step
controllers without position feedback).
If you set the input parameter AdvCoModSP = 0, the analog value provided by the
OPC client (AdvCoMV) is used as an external manipulated value for the controller.
The algorithm of the PID controller is bypassed. The controller and faceplate
otherwise react as they do with tracking (MV_TrkOn = 1).
Requirements for program mode with manipulated value:
− AdvCoModSP = 0,
− AdvCoEn = 1,
− The controller is in manual mode.

PCS 7 System Course

PCS 7 System Course
8.2.12 Comparison of Large and Small blocks
• Small blocks save memory and runtime resources in comparison to the large block.
• Small blocks are available for monitoring, motor and valve control.
8.2.13 Templates
Templates (standard types, standard solutions) are provided to support you in the
configuration of a PCS 7 plant in case of recurring technological functions.
The PCS 7 libraries (PCS 7 Advanced Process Library, PCS 7 Basic Library) contain
templates for base control functions (e.g. motor control, valve control, Standard PID
control loop) as well as for advanced control functions (e.g. PID control loop with control
performance monitoring).
A template is a prepared chart containing already all blocks necessary for the process
tag, in other words not only technologic blocks for the control function, but also driver
blocks and additional logic.

PCS 7 System Course
Example ValveLean (PCS 7 APL V8.0)
Bad process „Maintenance

value release“ status
Textual
interconnection
Valve block
Output driver block for the
control signal
Input driver blocks Interlock blocks
for feedback
„Out of service“
status
Textual
interconnection Logic to form the control
system fault
Logic to merge the
„Out of service“ status
One possible procedure how to work with templates:
1. Copy the desired template into the master data library of your multiproject. Make
there your adoptions to your specific requirements.
2. Drag the customized template from your master data library into the hierarchy
folder, where the process tag has to be placed.
3. Open the resulting chart and replace all opened textual interconnections by
references to I/Os from the symbol table to connect the chart with hardware signals.

PCS 7 System Course
8.3 Textual interconnections

A textual interconnection is a connection on a block input that:
• is not yet existing, or
• is existing in a chart that has been moved to chart folder of another AS (S7 program)
???
Interconnection target
is not existing…
How does it look like and format
.
chart name\block name I/O name

PCS 7 System Course
When the block has appeared…
You cannot close single interconnections.
Log file
The log generated lists all closed textual interconnections and any that are still open.
Call this log in the CFC editor with the menu command
Options > Logs > "Textual Interconnections" tab
If one or several textual interconnections are not closed, a corresponding log entry is
generated. You can view this entry with the menu command
Options > Logs > "Compile" tab.
The data is compiled and a substitute value is generated for the corresponding input
(default value of the block type). An interconnection at the output is ignored.
details.

PCS 7 System Course
Task: Material Tank M110
Goal
AS functions for Material Tank M110. Measuring and monitoring the level of the tank
and controlling and monitoring the valve and the pump, based on templates from the
library.
Checkpoint
Why …
• are the OR gates present in the
charts?
• are connections made to the left
chart bar, with a yellow triangle?

PCS 7 System Course
8.5 Alarm blocks in PCS 7
Monitoring of a signal with 1 to 10 associated

ALARM SFB 33
values with acknowledgment display.
Monitoring of up to 8 signals with

ALARM_8 SFB 34
acknowledgment display.
Monitoring of up to 8 signals with 1 to 10

ALARM_8P SFB 35 associated values with acknowledgment
display.
Monitoring of a signal with 1 to 10

NOTIFY SFB 36 associated values without acknowledgment
display.
Monitoring of up to 8 signals with 1 to

NOTIFY_8P SFB31 10 associated values without acknowledgment
display.
The process messages for PCS 7-compliant blocks are always generated in the AS.
They are therefore also acknowledged centrally in the AS, i.e. an OS acknowledgment
is sent to the triggering block, this accepts the acknowledgment, and sends acceptance
to all the OS that are logged on.
Ready-made alarm blocks are provided as SFBs both in the PCS 7 APL V8.0 and in the
PCS 7 Standard Library.
The message and acknowledgment behavior as well as the transfer of associated

values is determined by the CPU properties ("Diagnostics/Clock" tab/"Acknowledgment-
triggered reporting") and the integrated alarm block.
 Typically, only the ALARM_8P and NOTIFY_8P blocks are used in PCS 7.
Message number
The message number for PCS 7 is unique within the CPU. When the OS is compiled,
the numbers required for the individual messages for the PCS 7 OS are derived from
this message number. So that the value assigned by the system cannot be changed
inadvertently, the MsgEvId input is not be visible, interconnectable, or parameterizable
in the CFC.

PCS 7 System Course
Integration in multiple instance blocks

Functions can consists of different partial functions. Blocks used to perform the partial
functions can be added together to form a multiple instance block which carries out the
entire function. This could be for example, a control block which functions as an internal
block and contains both an alarm block.
Message-capable Message-capable
block type A block instance
DB x
ALARM_8P
ALARM_8P
Message-capable Message-capable
block type B block instance
DB y
ALARM_8P
ALARM_8P
 If blocks contain code used for accessing other blocks (multiple instance blocks), the
applicable version of these lower-level blocks must also be copied. Lower-level FBs
that are missing can be determined later by engineering. Missing FCs, however,
cannot be detected during compiling or downloading.
The alarm behavior of technologic blocks in PCS 7 is basing on the ready-made alarm
blocks as the ALARM_8P being already integrated into a technologic block, in some
cases, two ALARM_8P blocks are included.
AV - displaying and monitoring additional value

The APL provides the AV block to integrate an additional ALARM_8P instance into a
technologic block instance.
The block is used for monitoring an additional analog value at a technologic block (for
example, motor, valve).
Interconnect the AV_Tech output parameter of the AV block to the input parameter AV
of the technologic block in the CFC.
For the AV block, the Advanced Process Library contains process tag type templates;
these serve as examples by providing various application scenarios for this block.

PCS 7 System Course
8.6 Process Object View

8.6.1 Efficient engineering with the Process Object View
In the process object view, all the data of the basic control can be displayed in a
process control oriented view throughout the project. This means that a multiproject
encompasses the data of all the projects within it.
The process object view is mainly used during the FAT and commissioning. These tasks
involve working efficiently with great amount of data at a centralized location. The
process object view has the advantage that all changeable tags/values of an object
(white background) can be centrally edited.
When editing process tags and CFCs, all aspects (automation, I/O connection,
messages, operation, and monitoring) can be consistently displayed and documented.
Jumps to CFCs, SFCs, HW Config, and to the OS enable you to edit tags/values, which
cannot be edited in the table (e.g. parameter definition of the models, picture contents,
etc.).
The Process Object View can be opened via SIMATIC Managers menu:
View  Process Object View
Undo
function!
Undo function
Important to notice is that the process object view has an undo function.
Requirements:
• The selection in the hierarchy tree was not changed.
• No filter changes were carried out.
• No updates (F5) were carried out.

PCS 7 System Course
Efficient engineering
The process object view allows you to edit mass data. This involves the following topics:
• Displaying general data
• Editing Blocks
• Editing Parameters
• Editing Signals
• Editing Messages
• Editing Picture Objects
• Editing Archive Tags
• Editing Hierarchy Folders
• Editing Equipment Properties (SIMATIC Batch/ SIMATIC Route Control)
• Editing the Shared Declarations
• Testing in the Process Object View
... without opening individual objects (CFC charts, pictures...). This can be done directly
in the process object view, or in other tools, such as Microsoft Excel, by exporting,
editing and importing the edited data.
In the following section you can find some tips and tricks about the process object view.
8.6.2 Configuration of the columns in the Process Object View

Via SIMATIC Manager Options menu, you can open the Customize dialog windows, and
then select the tab Columns to select and arrange columns for every tab:
2
3
1. Select the desired tab of the Process Object view.

2. Use the check boxes to control the visibility of a column.
3. Edit the position of a column.

PCS 7 System Course
8.6.3 Order of the columns

The order of the columns in the process object view can be changed as described
above or just be selecting the complete column and dragging the column to the desired
position (see below).
3
1
1. Click in the area of the column header.

2. Drag & drop the selection to the desired position
3. The green checkmark indicates that the current data were read in according to the
selection in the hierarchy tree.
8.6.4 Defining your own columns
Use this feature to define additional separate columns in the "General", "Blocks",
"Parameters", and "Signals" tabs of the process object view.
This allows you to add important supplementary information, for example, operator,
maintenance interval, etc., to the following objects:
• process tags
• CFC/SFC charts
• parameters and signals of process tags and CFC charts

PCS 7 System Course
8.6.5 Defining the contents of the "Parameters" and "Signals" tab

In CFC you define whether a block I/O is visible in the process object view as a
parameter or a signal in the properties of the block I/O (See below).
Parameters are block I/O's for which parameter configurations or interconnections
between the process tags or CFC charts were selected.
Signals are block I/O's which are or will be connected to signals outside CFC/SFC
(memory of the CPU, but in most cases inputs and outputs of the AS)
In the Block properties:
3
1
1. Selection for a single block I/O in CFC

2. Using this item from the SIMATIC Manager Options menu …
3. … to make your filter settings
To avoid having to open the individual CFC charts, it is possible to select the I/O's for
the process object view from the process object view itself (see above and below).
Use this menu command to open a dialog box that contains a list of all I/Os of the
selected hierarchy folder. From this list, you can select the parameters and signals you
want to edit in the process object view.
A dialog box for the filter settings can be opened via the dialog box for selecting I/Os.
With this filter, you limit the amount of data for certain columns, and thus the runtime for
reading in (for example, if only the "BOOL" data type is to be displayed, etc)
Make the I/O

Make the I/O available in the
available in the Signals tab
Parameter tab

PCS 7 System Course
8.6.6 Setting the "Parameter" or "Signal" attribute for multiple I/O's
Group I/Os by
sorting
By applying an adequate filter and sort setting, you can group block I/O's in such a way
that you can select a range of I/O's and set/reset this range completely. In the example
above, only the block I/O's with a name starting with "SimOn", of block type “PCS7DiIn”
and on charts with names starting with a “P” are shown and, by consequence, can be
set as a parameter for the process object view.
8.6.7 Dividing a table
You can divide the window into two halves (left and right), so that each has an individual
scroll bar. This is a function which you may recognize from Excel, for instance.

PCS 7 System Course
8.6.8 Filtering
2
1
1. A second filter can be displayed.

2. The filter setting of the General tab can be active as well.
Using the second level of the filter, you can further limit column contents that are
relevant for processing.
A blank has a particular meaning: The rows in which this column is empty are displayed.
A filter with a variety of criteria is shown in the top left corner as an example:
• Chart name starting with a “P”
• Block type equal “Pcs7DiIn"
• I/Os name equal “SimOn”
 The filter settings set in the "General" tab have an effect on other tabs (except for
hierarchy folders, equipment properties, shared declarations):
Only the objects displayed in the "General" tab are then displayed on these other
tabs. This filter setting remains visible in the other tabs under "Filter general" (See
example in the top left corner of the image).

PCS 7 System Course
8.6.9 Export and import data using the Process Object View
Selected
hierarchy
folder
By exporting and importing attributes, you can do the following with parameter, signal,
and message information: export it to a file, edit it using standard applications and re-
import it.
These functions are particularly beneficial if you want to edit large amounts of data. You
do not need to open the individual charts with the CFC editor in order to edit the I/Os, as
the I/Os of all charts in the hierarchy folders are imported automatically.
Charts located in the selected hierarchy folder and all lower-level hierarchy folders are
edited (in accordance with the selection made in the process object view).
 Filters are ignored during import/export. All data are always exported when they are
displayed in the current view without filter.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.7.6.8 for more info on how to
Import/Export Blocks, I/O's and Messages

PCS 7 System Course
8.6.10 Copy and Paste in the PO View
1
3
1. Copy the interconnection.

2. Select a range of interconnections and paste the copied interconnection.
3. Result: the interconnection is copied for all selected block I/O’s.
Apart from copying names, constants, parameters etc. it is also possible to copy
interconnections in the process object view. In the example above, the interconnection
between the "Out" parameter of an "OpDi01" and the "SimOn" parameter of the input
driver of a Motor is copied to the "SimOn" of all input drivers in the selected plant
folders.
8.6.11 Copy and Paste to and from Microsoft Excel
1 2
Data from the engineering system can be exported as a template, be effectively

duplicated and adapted in an external program (such as MS Excel) and then be
imported back into the engineering system. This allows the configuration of repeated or
similar plant information to the optimized.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 9.5.3 for more information on
how to exchange data with MS Excel or Access

PCS 7 System Course
8.6.12 Open exported Data in Microsoft Excel

The best way to open an export-file (e.g. exported messages) is to create a new Excel
spread sheet and import the external data.
Start the
data import
Define per column the data format

(e.g. General, Text, Date, etc.)
8.6.13 Task and Checkpoint
Task: Everything of D210, R310 and B410
Goal
All devices of D210, R310 and B410 monitored and controlled in manual mode.
Checkpoint
Why …
• are not all parameters displayed in
the Parameter tab of the Process
Object View

PCS 7 System Course
Content 9
9 Basics Operating and Monitoring .......................................................................... 3
9.2 General ...................................................................................................................................3
9.2.1 Overview .................................................................................................................................3
9.2.2 Single station and multiple station systems............................................................................4
9.2.3 WinCC Explorer / Location of the OS Project.........................................................................6
9.3 Plant Hierarchy Settings .........................................................................................................7
9.4 OS-AS Connection ...............................................................................................................11
9.5 Project type ...........................................................................................................................15
9.6 Compilation ...........................................................................................................................16
9.6.1 Overview ...............................................................................................................................16
9.6.2 Settings .................................................................................................................................16
9.6.3 Create/ update block icons ...................................................................................................19
9.7 Layout ...................................................................................................................................21
9.7.1 Skin & Design .......................................................................................................................21
9.7.2 Settings for WinCC RT Design .............................................................................................22
9.8 Block Icons and Faceplates..................................................................................................24
9.8.1 Difference between Block Icons and Faceplates..................................................................24
9.8.2 Faceplates of APL in general................................................................................................25
9.8.3 Block Icon Representation....................................................................................................27
9.8.4 Operation in Faceplates and Block Icons .............................................................................27
9.8.5 User permission levels..........................................................................................................29
9.8.6 Create/Update Block Icons ...................................................................................................31
9.9 Tasks and Checkpoints ........................................................................................................35
SIMATIC PCS 7 – Basics Operating and Monitoring

PCS 7 System Course

PCS 7 System Course
9 Basics Operating and Monitoring


• the general function of the OS
• the role of OS-AS connections and
of the Plant hierarchy
• the mechanism of the create/
update block icons function

• have the OS running for basic
operating and monitoring
functions, using a minimum of
configuration steps (using default
settings for operating, layout,
windows etc.)
9.2 General
9.2.1 Overview
The OS of SIMATIC PCS 7 is based on SIMATIC WinCC.
SIMATIC PCS 7 - Operator Station =

WinCC + Options
Process visualization
number ()
float cou
begin
if value > 0
start
cou = cou + 1
Motor ON end
end
Valve closed
Gate closed
Programming
Alarm Logging interface
(message system)
Standard
interfaces
Tag Logging
(archiving) Logging
ReportSystem Process
(reporting) communication
Together with a number of WinCC options and additional tools in SIMATIC Manager it is
used as one of the main components of a PCS 7 configuration: the Operator System.

PCS 7 System Course
9.2.2 Single station and multiple station systems

An OS can be configured as a:
Multiple station system
OS Terminals
ES OS OS
Client 1 Client 32
Terminal bus
OS Servers (TCP/IP)
Server 1 Server 12
Plant bus (ISO)

AS1 ASx
Servers contain communication to the AS, pictures, logging of tags and messages.
Clients offer the user interface.
With a multi-user system, one or more (up to 12) OS Servers supply up to 32 operator
stations (OS clients) with data (project data, process values, archives, and messages)
via a terminal bus. The terminal bus can share the transmission medium with the plant
bus or it can be designed as a separate bus (Ethernet with TCP/IP).
In this architecture, redundant OS servers may be set up to meet higher availability
requirements. Critical applications are monitored by health check for software faults. If a
fault is detected, switchover to the redundant system is triggered. Synchronization of the
redundant OS servers takes place automatically and at high speed.
The broad colored arrows in the figure above symbolize the exchange of information
between the AS and OS resp. between servers and clients.
The OS Runtime is executed on the OS servers.
Central Engineering
Whatever is the configuration of system components, it is always the Engineering
Station to be the source of everything. All configuration data are loaded from the ES to
the target system. The figure above indicates this by thin black arrows.
OS Simulation
The OS runtime of servers must not be started on an ES station! To provide the
opportunity to test OS configurations on the ES in runtime without disturbing the running
OS server, the OS can be simulated on the ES.

PCS 7 System Course
Single station system
ES OS
Terminal bus
(TCP/IP)
Plant bus (ISO)

AS1 AS99
In single station system architecture, all operator control and monitoring functions for a
complete project (plant/unit) are concentrated in one station. This OS single station can
be operated on the plant bus together with other single-user systems or in parallel with a
multiple station system. Redundant operation of two OS single stations is also possible
(SIMATIC PCS 7 Single Station Redundancy).
Special case: Combined ES/OS
ES
Terminal bus
(TCP/IP)
Plant bus (ISO)

AS1 AS99
The PC station configuration of the ES contains the WinCC application for the OS
project. This is the only case, where the OS Runtime is executed on the ES.

PCS 7 System Course
9.2.3 WinCC Explorer / Location of the OS Project

After insertion of a PC Station with WinCC Application in the multiproject, you will find
the OS-project as you can see in the picture below:
Path to the storage location

depends on the multiproject
structure and how it was created.
All pictures of the

OS project are
located here.
 The subfolder GraCS contains all pictures of the OS project.

You have to place pictures from other multiprojects in this folder first before you can
integrate them in your current OS project!
For editing the contents of an OS, the OS project is opened from the Component View
of the SIMATIC Manager: WinCC Explorer will be launched.
SIMATIC Manager
WinCC Explorer
Content window,
showing objects
related to some
of the editors
List of editors:
Every editor will use its

own application window
(also appearing on the
Windows task bar)
SITRAIN

PCS 7 System Course
9.3 Plant Hierarchy Settings

Settings on the Plant Hierarchy level will control content of data on the OS systems.
Plant Hierarchy settings are relevant to the structure of pictures and names of tags:
HID (Higher level Item Designation)

Hierarchy folders that are included in the designation enter their names in the HID.
Hierarchy folders not included in the designation can be used to create additional
"drawers" (for example, for additional documents such as plant descriptions, process-
tag sheets, etc.).
 When assigning names, please note that when you compile the OS, the tag name
must not be longer than 128 characters. The name consists of the folder names in the
hierarchy path, the chart name, the block name, the delimiter, and the I/O name.
With delimiter
A delimiter is appended in the HID to the name of the hierarchy folder. Delimiters are
used in the textual representation of the hierarchy path for clearer distinction between
the names of the hierarchy folders. The hierarchy path is the sequence of names of the
hierarchy folders through the hierarchy levels to the current object. The "\" character is
used as the delimiter. Note: There is always a delimiter after the last hierarchy folder
that is included in the designation, which means this option cannot be modified.
OS area
This defines which hierarchy level is to be valid as the OS area level. Only the top three
hierarchy levels are available as OS area levels. The default is level 1.

PCS 7 System Course
The way, how pictures are arranged, can be displayed in the Picture Tree Manager.
The tool is part of the WinCC Explorer.
In OS Runtime, the overview buttons and the content of the Picture Tree Navigator
represent the way pictures are arranged:

PCS 7 System Course
Tag Structures and Tags

Tag Structure (blocks) names and Tag names contain the HID:
• Tags:
R310 LIA214 MonAnalog PV.Value
PH Level Chart name Block name I/O name

PCS 7 System Course
• Structure tags:
R310 LIA214 MonAnalog
PH Level Chart name Block name
See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.4.3 for
 more details

PCS 7 System Course
9.4 OS-AS Connection

What are the arrows in the figures below standing for?
Multiple Station OS
ES
OS Clients
Terminal bus
OS Servers (TCP/IP)
System bus (ISO)

AS1 ASx
Single Station OS
ES OS
Terminal bus
(TCP/IP)
System bus (ISO)

AS1 AS99
Special case: Combined ES/OS
ES
Terminal bus
(TCP/IP)
System bus (ISO)

AS1 AS99

PCS 7 System Course
The answer: Communication

Before it is possible to have communication between an OS and an AS, a connection is
to be set up between both stations.
It is done by NetPro:
The connection is configured between
• the WinCC Application on the PC (starting point of Insert New Connection dialog) and
• the CPU as its connection partner on the AS.
Named
connection
4
1. Select the WinCC Application object.

2. Because this object is capable to have a connection, the connection table is
displayed. Insert there a new connection.

PCS 7 System Course
3. Select the connection partner. If you started with a WinCC Application, then the
CPU of the desired AS should be the partner.
4. Named connection: Assign a symbolic name to the connection between OS and
AS instead of the default connection ID as substitute for the connection parameters.
Use a meaningful name.
Named connection
This method of procedure is also designated as a "Named Connection". It is also
important for redundant OS server and OS simulation mode.
We recommend to use the name of the connected AS. Once the OS has been
compiled, this name will appear in the "SIMATIC S7 Protocol Suite" of WinCC tag
administration.
 For more details see

[103] PCS 7 V8.0 Engineering System - 12_2011, 8.10.4 and
[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.2.2 for more
details
Save/Compile and Download
Color indicates a
configuration still
not being compiled
1. Use the button „Save and Compile“in the tool bar of NetPro to start the compilation
of the network configuration.
2. We recommend always including the configuration check.
3. After the configuration was compiled you have to download the new OS-AS-
connection.

PCS 7 System Course
No stop required
By download the connections only the AS will not be stopped.
Other download options

But there are also some other options for download:
• Download by "Selected Stations (and Partner)" is loading not only

connection(s), but also configuration data > that needs CPU-STOP!
• Download by "Selected Connections and Gateways" is loading only
connections, but no configuration data > that needs NO STOP!
Configuration data have to be loaded before.
Result in the Station Configuration Editor (Station Configurator)

The Station Configurator Editor shows as result of connection download:

PCS 7 System Course
Connection status in NetPro
9.5 Project type

From origin, a WinCC Application as it is inserted into a PC station configuration is set
as a Multi-User Project.
Single User
If the system is to be used as a Single User Project, have it adapted in Project
Properties:

PCS 7 System Course
9.6 Compilation
9.6.1 Overview
A lot of settings to the OS data structure are done in SIMATIC Manager and the tools for
configuring the charts. It is stored in the Project database.
This OS relevant data is transferred into the OS database by a compilation process:
 See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 5.5.1 for
more details.
9.6.2 Settings
Settings for the compilation process are offered to you in dialog windows of a wizard:
Assign an OS area of the PH to an OS server.
Assign an S7 program to an OS server.

PCS 7 System Course
• Area-oriented: With this setting, you assign an OS area of the PH to an OS server.

The advantage is that PCS 7 checks which data are relevant to the OS server. Only
these data are transferred. Default setting for PCS 7 projects from PCS 7 ≥ V 6.1.
• AS-oriented: With this setting, you assign an S7 program to an OS server. This
allows you to specify which OS accesses data on which AS. All the data of an
automation system is assigned to an OS server. This is the default setting for all
projects created with a PCS 7 Version < V 6.1.
more details.
Start the compilation
1
3
1. Start the compilation wizard for the selected OS.

2. Select the S7-program to be compiled.
3. Open the dialog „Select Network Connection“.
4. Select the “Named connection”.

PCS 7 System Course
Scope of the compilation

• Tags: The tags are created under the named connection, which has been set up for
communication between the OS and AS.
• Messages: Event texts of messages are stored in the text library. The number of
columns set up in the text library is based on the "Language for Display Devices"
setting.
• Units of measure, etc.: The character strings for units of measure, identifiers,
strings, and block comments are located in "Internal tags".
• Structure types: Corresponding to the use of specific block types in CFC charts,
these are created in the OS as structure types. The instances of these block types
are also managed at a lower level.
To define the scope of compilation the wizard needs some parameter more:
2
Runtime mode must be
stopped for a complete
download of the OS. 4
1
The OS servers (or single
OS station) can remain in
runtime mode during the
download procedure.
1. Delete all AS data from an operator station.

2. This function enables the picture jump function in WinCC-Runtime. The OS
comments will be amended by their interconnection partners. This function may
result in much longer mapper runtimes.
The box will only be visible if SFC visualization was enabled.
3. The "Minimum acquisition cycle" setting allows you to specify the shortest
acquisition cycle for archiving analog variables. For a new archive tag, AS-OS
engineering derives the following acquisition cycle from the processing cycle of the
block and the "Minimum acquisition cycle".
4. "Generate server data"
Select this radio button if you want to compile the variables of a server.
− The radio button is not selected as standard for compilation of changes. This
setting is not saved when you select the radio button.
− The radio button is selected automatically and cannot be deselected when you
compile the entire program.
Check your settings before you finish the wizard to start the compilation. The result of
the compilation is summarized in a log file.
 See [121] PCS 7 Compendium part a - Configuration Guidelines - 03_2009, 8.1,

8.1.3.2 and 8.1.3.3 for more details
PCS 7 System Course
9.6.3 Create/ update block icons

As one of the steps of the compilation process, the block icons are created/ updated.
Separate task
It can also be done as a separate task from the Plant View window of the project:
Precondition
Picture M110
Define how the tag

name is composed
As comparison…
Thanks to configuration in the plant hierarchy, the technological relationships between

AS and OS components are already known. This information can be used in the plant
hierarchy to automatically place and interconnect the ready-made block icons in the OS
pictures which have been selected for this purpose. Likewise they can be updated when
the block icons are changed.

PCS 7 System Course
Included levels
Picture R310
The charts are in
the 4th level
PH level: 1 2 3 4
The picture is in
the 3rd level
PH level: 1 2 3 4
In the Lower hierarchy levels included combo box, set the number of AS hierarchy
levels to be taken into consideration when creating/updating block icons.
The need for this setting is based on the different description depth between the AS and
OS.
On the AS side the charts are configured at process tag level. The charts are therefore
inserted at the lowest level and only contain the control modules with the drivers for
process connection. In our example the charts are at level 4.
On the OS side, the aim is different. The pictures do indeed describe the plant for the
lower levels in increasing detail, but not as far as process tag level. In our project the
lowest level for the pictures is level 3.
As there are no pictures at chart level, no block icons would be inserted by the
Create/Update Block Icons wizard either. This problem can be solved by setting
Lower hierarchy levels included to 1. The block icons are then simply inserted in the
pictures that are one level up.
The default setting is 1.

PCS 7 System Course
9.7 Layout
9.7.1 Skin & Design
In OS Runtime, the screen is divided into three parts:
Overview area
Work area /
process picture
Key set
 The name of the start picture (the first picture being opened after start of OS-
Runtime) is @screen.pdl

PCS 7 System Course
9.7.2 Settings for WinCC RT Design
Global design settings for the project:
Define your
project color
palette
Select a WinCC
skin design
Ensure that all projects in a plant have uniform settings for the design. If you change the
setting of the design, check the visualization of self generated objects and adapt these if
necessary. You can define the appearance of the user interface in process mode by
selecting one of the two designs: WinCC 3D; WinCC Classic
 The WinCC designs "Glass" and "Simple" are not supported by PCS 7.
• Design restrictions in Computer properties:
Some restrictions to the global design effects can be activated on the "Runtime" tab in
the "Computer Properties" dialog. You can improve the computer's reaction time by
switching off certain elements of the global design.
The settings made on this tab apply for all WinCC projects run on this computer.

PCS 7 System Course
Settings at the objects properties
Object properties of
the selected button
Individual color
setting
If nothing else is set in the object properties, the settings of the selected global design
apply to all graphic objects in the project.
 As soon as an attribute is determined by a global design, it remains static and can no

longer be made dynamic. Even a dynamization that has already been performed
remains without effect.

PCS 7 System Course
9.8 Block Icons and Faceplates

9.8.1 Difference between Block Icons and Faceplates
Block Icons are there to represent AS functions in the OS.
In general, the main information (states and modes) of a device/function (motor, valve,
etc) is displayed in the Block Icon. PCS 7 therefore provides the corresponding block
icon for each technological block.
The block icons are automatically added to process pictures according to the plant
hierarchy and connected to the relevant process tag.
After a single mouse click on the Block Icon, a Faceplate may appear for:
− Showing more details in several views
− Operation to values (limits, suppression, etc) by several input fields, buttons…
• Example for the PCS 7 Standard Library
Faceplate,
showing a
standard view View
selection Block Icon
Loop display,
showing all views
in one window
• Example for Advanced Process Library:
Block Icon
Faceplate,
showing a
standard view View
selection

PCS 7 System Course
9.8.2 Faceplates of APL in general

Compared with the PCS 7 Standard Library the design of the faceplate in the APL has
changed and expanded considerably. This change is also due to the extended
functionalities of the APL.
Display and
operation
Commands and
Status operating modes
displays
Interlocks
Button for
additional
faceplate
Auxiliary
Operating values (max. 2)
area
Displays and operator controls
The faceplate provides the following display and operator controls:

Use right mouse
1. Group display Icon Meaning button to open the
2. Lock alarms via faceplate Standard view view in an
3. Suppress alarms via FB additional window
Alarm view
4. Acknowledge alarms
5. Worst signal status Limits view
6. Batch display Trend view
7. Not used
8. Maintenance request and release Ramp view
9. Memo display Parameter view
10. Open views of the block
Preview
11. Return to block icon
12. Pin block Memo view
13. Instance name of the block
Batch view
• Left mouse click: Exchange of the current view.

• Right mouse button click: Additional opening of the desired view.

PCS 7 System Course
Status displays
This area shows at the top the status (motor, valve icon,...) in the form of an icon or
symbol. Additional information and step functions are shown below it (buttons for
opening a faceplate of another block).
The additional information serves as support for the operator and it informs about the
status of the process instrumentation, e.g. whether a motor is simulated or maintenance
is carried out on it.
Buttons for additional faceplates

Additional faceplates can be opened via two freely assignable buttons in the faceplate.
Commands and operating modes

Modes and commands are displayed in this area and there they can be changed if the
required authorizations exist.
The following modes can be selected depending on the block:
• Manual
• Automatic
• Program mode
• Local mode
• Out of service
The commands can be "Start", "Stop", "Open", "Close", etc.
The selection of the mode and of the command is made through a separate operating
area which is displayed below the faceplate. This operator control can be made either
with or without confirmation, depending on the setting.
Interlocks
The different interlock functions are displayed in this section
Auxiliary values
Up to two additional analog auxiliary values can be displayed in the standard view of
some technological faceplates. They can be used e.g. with motors for displaying the
motor current and the coil temperature.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.3 for more details
about the faceplates

PCS 7 System Course
9.8.3 Block Icon Representation

Compared with the PCS 7 Standard Library the design of the block icons in the APL has
changed and expanded considerably.
A huge stock of icons per block type is provided in @PCS7TypicalsAPLV8.pdl:
Analog monitoring block Valve block

MonAnL VlvL
in @PCS7TypicalsAPLV8.pdl
in OS Runtime Normal Operation, Normal Operation,

valve opened
Normal Operation,
High alarm violated Disturbed, with additional
status information
9.8.4 Operation in Faceplates and Block Icons
Faceplate – Commands / mode selection

Mode selection with @APLCommandExecutionSteps = 3
Mode selection with @APLCommandExecutionSteps = 2
• Value 3: Operating step with

acknowledgement (presetting) Start command with @APLCommandExecutionSteps = 3
• Value 2: Operating step without
acknowledgement
Start command with @APLCommandExecutionSteps = 2
The setting for one of both variants (without / with acknowledgement) can be made
throughout the project via the internal WinCC variable @APLCommandExecutionSteps
being available in the category “Split Screen Manager” of the internal variables in the
Tag Management of the OS.

PCS 7 System Course
Value Representation
Message
locked Sufficient
Operation via
FB enabled authorization level
Operation via Insufficient

FB disabled authorization level
(OS_Perm)
Value disabled
(e.g. PV_AH_En)
Internally
simulated
Operation due Externally
to process simulated
not possible
Value
faulty
Values, limits, etc can be changed from faceplates. A feature available only in APL is
that the operator enables and operator authorization can be graphically displayed. The
operator can distinguish which values can be changed and which can not be changed. It
can be distinguished whether:
• The operation at the block is generally blocked.
• The operation is blocked process-related.
• An operator does or does not have the appropriate authorization.
The value input also happens via a separate operating area below the faceplate. You
open this operating area by a mouse click on an adjustable value (white background
color). The value can be changed in the operating are in three ways:
• Via the direct operation, a value can be changed discretely using buttons (e.g. -2.5).
• Using the slider control, the value can be set to the desired value.
• Via the input field a value can be entered directly.
Via acknowledgement with “OK” the changed value is sent to the block.

PCS 7 System Course
9.8.5 User permission levels
Level 1
Depending on the user management
and access protection the operator has different
rights to operate a block in a plant/system area.
Level 2
Level 3
The following operator authorization levels from user management are used in the APL:
• Authorization level = 0
No process controlling, only monitoring.
• Authorization level = 1 (Level 5 in the "User administrator")
Process controlling (e.g.manual / automatic switchover, changing setpoint and
manipulated variables)
Higher process controlling (e.g. changing limit values, control parameters and
monitoring times).
Highest process controlling (e.g.switching simulating on and off). This operator
authorization enables the following operation:
− Switching the simulation on and off in the parameter view
Simulating the values is authorization level 1
− Switching the release for maintenance on and off in the parameter view
Advanced operation 1 (free project-specific operator authorization)
Advanced operation 2 (free project-specific operator authorization)
Depending on the user management and the access authorizations instance-specific
authorizations can be assigned. E.g. all controllable blocks have the OS_Perm input
parameter, which allows you to implement individual operator control strategies by
setting the operator control permissions.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, chapter 1.3.2 Operator
permissions

PCS 7 System Course
Associated values and direct jump to other faceplates

In the faceplates, additional faceplates can be called. Two assignable buttons are
available for this, in standard view and preview. The relationship between the buttons
and the faceplates is established via the inputs SelFP1 and SelFP2. The buttons
become visible and active if there is any connection to the block to be called. The
inscription is made on the block icon.
In several blocks' faceplates, up to two additional auxiliary values can be displayed, e.g.
motor speed. On the block, the value to be displayed in the faceplate can be switched to
the input UserAna1 or UserAna2. The visibility of the output fields is controlled via the
signal status.
The value identifier is defined as an indicator of the inputs, while the units possess their
own inputs.
Associated
value with unit
User button for
direct jump Label of the
associated value
Properties of input
UserAna1
Defining source, label and

unit of the associated value
Defining the target

of the jump

PCS 7 System Course
Operation directly from the Block Icon
Open the faceplate

(left mouse click
anywhere on
Value operation from the block icon)
block icon (right
mouse click on the
corresponding value)
 See [1003] Application description 50249288 APL Operator Guide - 01_2012, 5.5.3
for more details about operation of APL faceplates and block icons.
9.8.6 Create/Update Block Icons

Block Icons are installed in pictures by the wizard „Create/Update block icons”.
This wizard can run:
• as one of the stages of the OS compilation
• separately from the Plant Hierarchy
In brief what the wizard is doing:
Finding OS relevant blocks in charts.
Identifying the Typicals file to be used as „icon library“
Finding the related block icons in the “icons library”
Copying the block icons in the picture
Assigning specific information to the block icon

PCS 7 System Course
@PCS7Typicals: “Icons Libraries”

The wizard Create/Update Block Icons makes copies from block icons as they are
present in “typicals” file as standard block icons:
@PCS7TypicalsAPLV8.PDL
• APL Versions before PCS 7 V8.0 delivered another Version of the APL “typicals” file:
@PCS7TypicalsAPL.pdl
• To remain the compatibility to former APL versions this older typical file is also
delivered in PCS 7 Version 8.0 under another name:
@PCS7TypicalsAPLV7.pdl
Each additional library also provides a template picture of this type with the required
block icons. The name of this template picture starts with "@PCS7Typicals" and also
contains a short library designation at the end. The template picture of the standard
library is called "@@PCS7Typicals.pdl".
The Create/Update Block Icons function uses these template pictures to insert the
block icons. All pictures whose names start with "@PCS7Typicals" are identified. These
are sorted alphanumerically in descending order and the top 11 template pictures are
used. A possible processing sequence might therefore be:
• @PCS7TypicalsRC.pdl
• @PCS7TypicalsBATCH.pdl
• @PCS7TypicalsAPLV8.pdl
• @PCS7TypicalsAPLV7.pdl
• @PCS7TypicalsAPC.pdl

PCS 7 System Course
Variants of block icons

Make your selection and specification of a Block Icon via the AS block's properties
dialog in CFC (Tab General”).
Block properties „Icon library“:
The OS compiler
(more exactly: the wizard “Create / update Block
Icons”) finds the related block icon by this number:
@TemplateAPL.pdl
In the case of automatic creation, all block icons in the picture which also appear in
@PCS7TypicalsAPLV8.pdl but were not generated via the plant hierarchy are
deleted. For manual configuration and when post-processing pictures, therefore, use
picture @TemplateAPLV8.pdl as the template for block icons, as the type property is
pre-assigned differently in this case.
Note the character @

in the type property.

PCS 7 System Course
Consistent Plant hierarchy

In order for this mechanism to work, the charts with the blocks that can be operator-
controlled and monitored must be located in the same path of the plant hierarchy as the
corresponding pictures.
If there are automation and PC stations in the same project, this should be an automatic
condition.
This is not the case if the components are distributed over several user projects. Here it
must be ensured that the paths within the various plant hierarchies are identical.
To compare the plant hierarchies in different projects, it is best to use menu command:
Options > Plant Hierarchy > Synchronize in Multiproject
The same series of block icons are present in the picture @Template, from where the
block icons can be copied freely to any picture, and have a connection to a tag structure
(AS block) using the Dynamic Wizard “Connect picture block to tag structure”.

PCS 7 System Course
9.9 Tasks and Checkpoints
Task: Launch of the OS
Goal
A running OS based on the AS functions configured up to now.
Checkpoint
What items …
• of the OS system do you think
should be customized in a later
stage to fit the best to this plant?
Task: M120 and M130
Goal
AS and OS function for M120 and M130 based on a copy of M110.
Checkpoint
Did we …
• forget anything for the level of
M130?
Task: Level bar object in tanks
Goal
Properly connected Level bars in the process pictures.
Checkpoint
For what …
• purpose is a bar graphic useful?

PCS 7 System Course
Content 10
10 Basics Automatic Mode Control ............................................................................3
10.1 Learning targets ..................................................................................................................... 3
10.2 Setting the Auto/Manual mode by program ........................................................................... 4
10.2.1 Logic for control output (open/close command to valve)....................................................... 4
10.2.2 Demonstration with push buttons and switches .................................................................... 5
10.2.3 Examples for controlling the Auto / Manual mode by program.............................................. 5
10.3 Task and checkpoint.............................................................................................................. 6
10.4 Sequential control with SFC .................................................................................................. 7
10.4.1 SFC Charts ............................................................................................................................ 7
10.4.2 Elements of a Sequence........................................................................................................ 9
10.4.3 Close cooperation................................................................................................................ 10
10.4.4 Interconnections between CFC and SFC ............................................................................ 11
10.4.5 Initialization, Processing and Termination ........................................................................... 14
10.4.6 Example ............................................................................................................................... 15
10.4.7 SFC in test mode ................................................................................................................. 15
10.4.8 Task and checkpoint............................................................................................................ 16
10.4.9 Operating state logic for sequencers (sequencer OSL) ...................................................... 16
10.4.10 Operating state logic for a SFC (SFC OSL) ........................................................................ 17
10.4.11 External View ....................................................................................................................... 18
10.4.12 Task and Checkpoint ........................................................................................................... 18
10.4.13 Add a new sequencer into the chart and setup the properties ............................................ 19
10.4.14 Default behavior of an SFC ................................................................................................. 19
10.4.15 Sequencers reacting on changes of state ........................................................................... 21
10.5 Sequences on the OS.......................................................................................................... 22
10.5.1 Preparation in the ES........................................................................................................... 22
10.5.2 Steps of SFC operation in Runtime ..................................................................................... 23
10.5.3 SFC MultiChart Control........................................................................................................ 24
10.6 SFC type .............................................................................................................................. 27
10.7 Task and checkpoint............................................................................................................ 28
SIMATIC PCS 7 – Basic Automatic Mode Control

PCS 7 System Course

PCS 7 System Course
10 Basics Automatic Mode Control


• the general concept of automatic
mode control

• have devices controlled
dependend of states of other
devices
• have devices controlled by
sequential controls

PCS 7 System Course
10.2 Setting the Auto/Manual mode by program

10.2.1 Logic for control output (open/close command to valve)
The diagrams below show the logic of a VlvL block regarding the control signal Ctrl
and the Auto / Manual mode.
In these simplified diagrams the influence of other signals like Local mode, Out of
Service, forcing, interlocks and feedback error are ignored.
The red arrows represents the Boolean value “true” (digital: 1) that is send from the OS,
by clicking the related button (with OK) to the related input of the block in the AS.
After processing this value by the block program, the input value is put back to “false”
(digital: 0).
VlvL
Logic for
Auto / Manual
mode
OpenAut
S CtrL
OpenMan
1
Output driver
CloseAut
R
CloseMan PIQ
Feature.Bit4: Output module

0 = Button mode
1 = Switch mode
Simplified diagram for explaining the logic
Logic for Auto / Manual mode
ModLiOp
AutModLi
S
AutModOp
1
ManModLi
R
ManModOp
Feature.Bit4:
0 = Button mode
1 = Switch mode
Simplified diagram for explaining the logic

PCS 7 System Course
10.2.2 Demonstration with push buttons and switches

Below 2 VlvL blocks of R310 with connections to signals from the Signal Box:
T = push button V311 Button mode V312 Switch mode

VlvL VlvL
S = Switch
T3 OpenAut S4 OpenAut
T4 CloseAut CloseAut
S1 ModLiOp S2 ModLiOp
T1 AutModLi S3 AutModLi
T2 ManModLi ManModLi
10.2.3 Examples for controlling the Auto / Manual mode by program
0 ModLiOp
AutModLi
2
1 ModLiOp
AutModLi 3
ModLiOp
1 4
AutModLi
ModLiOp
AutModLi
5 6 7 8
1
0
1
0
t
1. The gray rectangles represent any block offering one or two outputs that can be
used to control the mode.
2. When ModLiOp has value 0, then the mode can only be controlled by operator on
the OS.
3. The mode is controlled by the source of the connection
4. When the source changed from 0 to 1: Auto mode, operator can not change to
Manual.
When the source changed from 1 to 0: remains in Auto mode, but operator can
change to Manual.
5. Operator controls the mode.
6. Auto mode, can not change to Manual
7. Switching back to Manual mode, operator can not change to Auto.
8. Operator controls the mode.

PCS 7 System Course
Task: Auto mode for the material tanks
Goal
One common switch on the OS to set the outlet valves and outlet pumps of the material
tanks in Auto mode.
When in Auto Mode, then the outlet valve and outlet pump of a material tank must follow
up the demand for the material: opening and starting when a dose valve has opened.
Checkpoint
Consider …
• a way to have the Auto mode of all
devices of D210 and R310 set by a
single operation, leaving the
devices in such a state, that the
operator can switch back to
Manual mode if required.

PCS 7 System Course
10.4 Sequential control with SFC

The sequential function chart (SFC) is a sequential control system executed in stages
which, depending on certain conditions, advances from one state to the next.
A sequential control system controls functions, such as CFC charts, via mode and state
changes, and processes them selectively.
SIMATIC Manager
PH PO IEA
SFC Visualization
CFC SFC
STEP 7 - tools
ES
STEP 7 WinCC
AS OS
10.4.1 SFC Charts
Configuration limits of the SFC

• Sequencers per SFC chart ≤ 8
• Steps per sequencer 2 - 255
• Instructions per action ≤ 50
• Transitions per sequencer 1 - 255
• Conditions per transition / start
condition ≤ 16
A SFC chart consists in maximum 8 sequencers for different states of the sequential
control system (e.g. default: Run, Hold, Resume, Abort...or customized: Heating,
Cooling, Dosing, Draining, etc.). An SFC chart is assigned uniquely to a CPU and is
also executed completely on this CPU.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.8 for more detail

PCS 7 System Course
Run Sequence
The runtime properties of an SFC chart or SFC instance determine how the SFC is
included in the chronological execution sequence within the overall structure in the
CPU. These properties determine the behavior of the target system with respect to
response times, dead times, or the stability of time-dependent structures, such as
control loops.
The insertion in the Run Sequence is done using the Predecessor for Insert Position.
The SFC chart is represented by a single object like a chart or as a part of a runtime
group like a block:
Single object
like a chart
Part of a
runtime group
like a block
It depends on the structure of your project!
 Insufficient runtime properties of an SFC chart are a typical beginner’s mistake

caused by a wrong default position „Predecessor for Insert“.
The cyclic operation interval of blocks controlled by an SFC must not be larger than
the cyclic operation interval of the SFC itself.

PCS 7 System Course
10.4.2 Elements of a Sequence

A newly created sequencer (menu command Insert > Sequencer > ...) is inserted at a
selected position in the SFC in its initial state consisting of an initial step, transition and
final step.
In its initial state, the new SFC consists of one sequencer. You create each sequencer
in its own working window.
A tab is created for every working window at the bottom of the screen. The tab shows
the name of the sequencer (for example, RUN or SEQ1). You can switch to the
individual sequencers using these tabs.
A toolbar “Element bar” offers the elements to build up a sequence.
Step and Transition
Upper
branch line
Loop
backwards
Element bar
Step
Transition Parallel
branch
Step Lower
branch line
Transition
Step
Transition
Tabs represent
sequencers Alternative Jump
branch
See [304] SFC for SIMATIC S7 - Programming and Operating Manual - 12_2011,
 11.2 for more details about the sequencer topology.

PCS 7 System Course
10.4.3 Close cooperation

There is a close cooperation between SFC and CFC:
• Sequences will not have access to the process signals by their own.
• Every access is to be configured in relation to existing function in CFC charts.
Controlling
Controlling devices in the process is to be done through the control blocks in CFC.
In general the Auto mode and its related input to control is being used.
For a VALVE block the input to be used is AUTO_OC. The VALVE block will have the
actual connection to the process through the output driver.
Monitoring
Monitoring the process (in general as a feedback from an earlier step) is done through a
block for monitoring the value, using a connection to the related input driver.
SFC CFC
Open command
in Auto mode
Valve is
closed
Process value of
level monitoring
Move
In CFC, an SFC access can be moved using ALT-drag.

PCS 7 System Course
10.4.4 Interconnections between CFC and SFC
Interconnection to APL blocks in a Transition
3
5 4
1. Open the Transition properties (Double click). There is a (possibly empty) list of
conditions arranged in boxes.
Each line represents a condition. A maximum of 16 conditions per transition are
possible. They are logically linked (default logic: AND).
Each condition consists of a left address, an operator (that you can select from a list
box), and a right address.
 By clicking the "Go To" button, you can jump to the point of use of the address in
whose edit box the text cursor is located (for example, to the CFC chart with the block
I/O that is the address of this statement.
2. The "Browse..." button opens a dialog box where you can select an address for the
edit box of the condition where the text cursor is located.
3. Navigate to the required block to get the corresponding I/Os displayed.
4. Select the desired block I/O.
5. In case of APL blocks with structures as I/O data type, it is necessary to open the
structure. Only a single structure element can be linked. An additional dialog offers
you the structure element to be selected.

PCS 7 System Course
Interconnection to APL blocks in a Step
3
5 4
1. Open the Step properties (Double click). There is a (possibly empty) list of
commands arranged in boxes.
Each line represents one statement. You can make up to 50 statements.
Each statement line consists of the following elements:
− The button with the line number for selecting the line
− The radio button that you can use to select the statement as an OS comment
− An edit box for the left address, the operator, and the edit box for the right
address
If the text cursor is located in an address box, the shortcut menu displays only the
functions needed for editing the contents.
2. The "Browse..." button opens a dialog box where you can select an address for the
edit box of the statement where the text cursor is located.
3. Navigate to the required block to get the corresponding I/Os displayed.
4. Select the desired block I/O.
5. In case of APL blocks with structures as I/O data type, it is necessary to open the
structure. Only a single structure element can be linked. An additional dialog offers
you the structure element to be selected.
 Accesses to CFC blocks can also be modified in the relevant CFC chart. This
modification, however, is restricted to "rewiring" SFC accesses; in other words,
moving the access to another block I/O (with <Alt> + Drag-and-Drop).
Do not write any values to outputs of blocks and charts (CFC and SFC). Generally,
these are overwritten again by the processing of the block or chart.

PCS 7 System Course
Options for to editing addresses in a step

• Drag the block inputs/outputs from CFC charts directly to the address box. Resize
and arrange the windows of CFC / SFC charts for this purpose.
• In the addresses, you can enter accesses to CFC block inputs/outputs whose block
does not yet really exist in the CFC chart. These statements are displayed in the
statement line on a yellow background and are set up as textual interconnections.
• Regardless of the selection and application of changes, all completed lines can be
copied and reinserted in any type of actions of other steps at another line.
Statement as an
OS comment
Drop
Drag&
Line buttons with
context menu
Textual
reference
Filtering the I/Os in the Browse Dialog
Double click
to sort
Enter a text to
identify

PCS 7 System Course
10.4.5 Initialization, Processing and Termination

In the properties of a step, there are 3 sections where you can enter the
actions/commands:
Initialization
If actions have been configured here, they will be executed only once: at transition from
the previous step to this step.
Processing
If actions have been configured here, they will be executed during every program
cycle, as long as the condition for transferring to the next step is not completed.
Termination
If actions have been configured here, they will be executed only once: at the transition
from this step to the next one.
cycle
Transition fulfilled
Start Trans 2
Step active
Stop Trans 2
 See [304] SFC for SIMATIC S7 - Programming and Operating Manual - 12_2011,
15.3.6.2 for more details

PCS 7 System Course
10.4.6 Example
Next diagram can be used for a demonstration in configuring a SFC chart:
START Start step
SP_EXT Step enabling condition:

70 L33
PV_IN Process value PV_IN less than 33?
SP=70 Action:
50 Set setpoint SP_EXT to 70
30 H67 Step enabling condition:

t Process value PV_IN greater than 67?
SP=50
• Linear sequence L53
• Conditions in transitions
• Actions in steps SP=30
• Test
L32
END
10.4.7 SFC in test mode

In SFC test mode a operating/status bar is displayed for monitoring and controlling. The
various step control modes change the behavior of the SFC when passing control from
active steps to successor steps:
Step Control Modes

T Transition
T or C Transition or Confirmation by User
T and C Transition and Confirmation by User
C Confirmation by User
Operating T/T and C Step specific Control by operator
state
Selection of
the step
control mode
Control Operator
mode confirmation
button
Operator
commands

PCS 7 System Course
Task: First sequence for R310
Goal
A first short sequence for dosing one material and to learn proper switching between
manual and automatic mode.
Checkpoint
What has to be changed in the

sequence …
• if the valve would be in button mode
instead switch mode (Feature bit.4)?
10.4.9 Operating state logic for sequencers (sequencer OSL)

The operating state logic of the sequencer is defined by the diagram of the state
changes.
States exited due to

commands
Operator commands
Implicit state changes

triggered by SFC
15.2.5.5 for more details

PCS 7 System Course
10.4.10 Operating state logic for a SFC (SFC OSL)
Diagram of state changes

The diagram below shows the changes of states of a SFC.
Diagram of state changes
States that are exited

through events
Transition states that are

implicitly exited
States applied from OSL

for SFC V5.x
Events: Commands / Conditions /

External Signals / Internal Signals
Event: Error
Results applied from OSL

for SFC V5.x
Implicit transitions that are

triggered from SFC, if the active
sequencer has been processed to
completion or if there is not
sequencer to process.
The sequencer OSL is executed independent of the SFC-OSL when a sequencer is

processed. This means that the sequencer has a state which differs from the SFC state.
For example, the state of the SFC OSL can be "Holding", whereas the state of the
sequencer OSL is "Run" (due to the processing of the sequencer to the "Holding" state).
The processing of the sequencer OSL is subordinate to the SFC OSL. This means that
the state change in the SFC OSL usually effects the state change in the sequencer
OSL.

PCS 7 System Course
10.4.11 External View
Operating
modes
Commands Provide
and operating information
states about states
and modes to
other blocks
Execution
options
Every SFC has an external view that is displayed by the CFC editor.
• On the left parameters for controlling the states, modes and more by SFC steps and
connections to blocks in CFC charts.
• On the right parameters representing states, modes and more information to be used
in SFC transitions and for connections to blocks in CFC charts.
• The inputs need different types of values / static or dynamic (edges).
12.3.1 for more details
Task: Complete sequence for R310
Goal
A sequence for dosing and heating a mixture of the 3 materials
Checkpoint
What happens …
• during a dosing step, when the
command Hold is executed?

PCS 7 System Course
10.4.13 Add a new sequencer into the chart and setup the properties
Assign a priority for

the case that several
sequencers fulfill their
start condition at the
same time
Insert a new
sequencer at the
corresponding Define the start conditions
position basing on the SFC OSL
10.4.14 Default behavior of an SFC

By default a SFC contains a single sequencer with the default name RUN.
Start
The state RUN is the start

condition for the sequencer
called RUN.
• When the SFC is started (button Start) for the first time, the first state change will be
from IDLE to STARTING.
• When the RUN sequencer is the only one, nothing will react on the state STARTING,
so the next program cycle the state will change from STARTING to RUN.
PCS 7 System Course
Hold
When during the execution of the RUN sequencer, the SFC is held (button Hold), the
state change will be from RUN to HOLDING.
When the RUN sequencer is the only one, nothing will react on the state HOLDING, so
the next program cycle the state will change from HOLDING to HELD.

PCS 7 System Course
10.4.15 Sequencers reacting on changes of state

The following picture illustrates the relationship between sequences and operating
states.
Sequencer RUN
Start condition RUN
Sequencer Holding
Start condition Holding
Sequencer RUN
Start condition RUN
Sequencer Resuming
Start condit. Resuming

PCS 7 System Course
10.5 Sequences on the OS

10.5.1 Preparation in the ES
Block icons for SFCs are generated automatically during OS compilation always.
As an additional option to the OS you can use SFC Visualization.
It allows you to monitor and control SFCs on the OS in a very similar way as in SFC
editors test mode.
OS compilation
Block icon
for SFC
Create / update block icon mechanism
Compilation
At OS compilation, have the proper check box set, which will allow you to have all the
relevant information transferred to the OS, including the creation of the pictures:
Block icons
In a similar way to OS relevant blocks in CFC, there can be representatives of SFC
charts being installed in pictures.
User defined buttons

In Graphics designer: Use a Dynamic Wizard to link a button with an SFC visualization
object.
User-defined
button

PCS 7 System Course
10.5.2 Steps of SFC operation in Runtime
User-defined User-defined Predefined button

button button in the 2nd key set
Block icon
Faceplate
SFC browser
Section
Overview
Sequencer properties
and start condition in
runtime
Separate
windows

PCS 7 System Course
10.5.3 SFC MultiChart Control

A SFC MultiChart Control allows you to:
• overview several sequences in one picture
• browse to the Section and Overview window of a SFC
• operate a SFC using buttons on the control
Configuration in Graphics Designer
1. In the Object Palette, click the „Standard" tab.

Select the object “Control“ in the list.
2. Place the mouse pointer at the position in the picture where you want to insert the
control. The mouse pointer changes into a crosshair with an object symbol
attached.
3. Drag the control to the desired size with the mouse.
4. A list offering all registered ActiveX controls is opened.
Select the entry “PCS 7 SFC Multichart Control“.
The insertion process for the selected control is finished.
 If you do not stretch the frame to its complete size, not all the columns will be visible.
In this case, a horizontal scroll bar is inserted to enable you to scroll through the
contents in the visible area during runtime mode.

PCS 7 System Course
Double click
5
Open the
SFC browser
5. Double-click the SFC MultiChart Control. The "Properties" dialog box opens.
6. Open the "General" tab and assign the desired SFCs to the control or delete them
from it.
7. Open the SFC browser.
8. Select the desired SFC and then close the dialog box with "OK". Repeat this
procedure for every SFC that you want to include in the SFC MultiChart Control. A
row is inserted for each SFC. This row includes the columns that provide SFC
information in runtime mode.
In the Runtime Window
Direct jump to
the step in
the faceplate
Operating the Boxes for mode Access to the
selected SFC controlling selected SFC

PCS 7 System Course
SFC aborted
Waiting for Reset

or Start command.
 See [305] SFC Visualization - Programming and Operating Manual - 12_2011, 5.13
for more details

PCS 7 System Course
10.6 SFC type

The SFC chart is able to use direct access to addresses in CFC (block I/O).
SFC charts can be edited independently of each other.
SFC CFC
A SFC type is created beforehand in a chart folder (in library or directly related to AS
system).
Steps and transitions will have access to the SFC type its own interface.
Instances
An SFC instance is derived from an SFC type and initially has properties identical to
those of the SFC type. You have an executable sequential control system only after
interconnecting the SFC instance with blocks and signals of basic automation in CFC
charts.
SFC type SFC instance placed into a CFC chart

By default, the interface of a SFC type is the same as the SFC external view, extended
by a number of SFC type specific parameters. Additionally, the user can configure more
parameters to create the application specific interface (characteristics).
BATCH
SFC types can be configured to represent an Equipment Phase in a SIMATIC BATCH
application.
4.5.2 for more details

PCS 7 System Course
Task: Holding and resuming
Goal
Preventing material flow when the sequence is held
Checkpoint
What else…
• … could be done in probably more
sequencers to this SFC?
Task SFC Objects
Goal
Have additional ways to monitor and control the progress of the sequence changes of
state

PCS 7 System Course
Content 11
11 Customizing the OS ................................................................................................3
11.2 User administration................................................................................................................ 3
11.2.1 Basic User Authorization Concept ......................................................................................... 3
11.2.2 Extended User Authorization Concept .................................................................................. 5
11.2.3 WinCC Logon versus SIMATIC Logon .................................................................................. 6
11.2.4 Task and Checkpoint ............................................................................................................. 7
11.3 Picture navigation .................................................................................................................. 8
11.4 OS Project Editor ................................................................................................................. 12
11.4.1 Layout .................................................................................................................................. 12
11.4.2 Area ..................................................................................................................................... 13
11.4.3 Runtime window .................................................................................................................. 14
11.4.4 General ................................................................................................................................ 15
11.4.5 Message display .................................................................................................................. 16
11.4.6 Basic data ............................................................................................................................ 17
11.5 Task and Checkpoint ........................................................................................................... 17
11.6 Time synchronization........................................................................................................... 18
11.6.1 General principle.................................................................................................................. 18
11.6.2 PLC Clock Setting in OS Computer properties.................................................................... 19
11.6.3 Time Synchronization Settings in the WinCC Explorer ....................................................... 20
11.6.4 Settings in the HW configuration of the AS ......................................................................... 21
11.7 Lifebeat Monitoring .............................................................................................................. 23
11.9 WinCC Basic Objects and special additional for PCS 7...................................................... 26
11.9.1 WinCC objects and libraries ................................................................................................ 26
11.9.2 How to make object properties dynamic.............................................................................. 28
11.9.3 Tag Connection – Working with the Tag Selection Dialog .................................................. 29
11.9.4 Dynamic Dialog.................................................................................................................... 30
11.9.5 Direct Connection ................................................................................................................ 31
11.9.6 The Dynamic Wizards.......................................................................................................... 32
11.10 Group display....................................................................................................................... 34
11.10.1 Overview in Runtime............................................................................................................ 34
11.10.2 Settings for installing Group Displays.................................................................................. 35
11.10.3 Group Display to represent a single block........................................................................... 35
11.11 Alarms.................................................................................................................................. 36
11.11.1 Basic Concept of the Event-Signaling System .................................................................... 36
11.11.2 Names of limits .................................................................................................................... 37
11.11.3 Events in Alarm Logging...................................................................................................... 39
11.12 Read Back ........................................................................................................................... 40
11.12.1 Changes in CFC test mode ................................................................................................. 40
11.12.2 Changes by operation on OS .............................................................................................. 41
SIMATIC PCS 7 – Customizing the OS
PCS 7 System Course
11.12.3 Read Back ........................................................................................................................... 42

11.14 Suppressing and Locking of Messages............................................................................... 44
11.15 Smart Alarm hiding .............................................................................................................. 46
11.15.1 Overview .............................................................................................................................. 46
11.15.2 Automatic Alarm Hiding ....................................................................................................... 48
11.15.3 Manual Alarm Hiding ........................................................................................................... 50
11.15.4 Impact to runtime view of message display......................................................................... 51
11.16 Status Displays .................................................................................................................... 52
11.16.1 Use and main Features ....................................................................................................... 52
11.16.2 Insertion of Status Displays ................................................................................................. 53
11.16.3 Tag connections of Status Displays .................................................................................... 54
11.16.4 Graphics of Status Displays................................................................................................. 55
11.16.5 Example of a Status Display connected to a tag ................................................................. 56
11.16.6 Example of connection to a Status value containing several bits........................................ 57
11.16.7 Example of connection to the Group value (.EventState) added to the Status value ......... 58

PCS 7 System Course
11 Customizing the OS
• Possible mechanisms of operator authorization

and time synchronisation
• several ways to represent dynamics of values
and status in the AS
• The role and functions of the OS project editor
• The concept of the PCS 7 event-signaling system
and how to customize it
• configure operator authorization, picture

navigation, presentation of events and alarms
• make WinCC object properties dynamic
• configure an extended status display including
several status bits and the group value
11.2 User administration

11.2.1 Basic User Authorization Concept
User rights are administered in the "User Administrator" Editor of WinCC Explorer.
• Example: For an operator it is possible to operate valves Manual/Auto and
Close/Open, but changing the Monitoring Time is not possible (field is grayed out).
• Function: It is because this operator is not authorized for the related function.
Assigned to function
“Higher Process
Controlling”
Assigned to function
“Process
Controlling”

PCS 7 System Course
Setting User Administrator

You manage and supervise user access rights in the User Administrator. The main task
of the User Administrator in runtime is to monitor system login and access rights.
In the editor "user administrator" two possibilities are available for managing user rights:
• WinCC Logon: creation of user groups/users and authorization assignment
• SIMATIC Logon: activate check box "SIMATIC Logon"; creation of user groups and
authorization assignment
The different OS areas and the plant structure from the SIMATIC Manager are shown in
the User Administrator. Some of the authorizations can be assigned area specific.
Users with the authorization

User administration have the
permission to open this window
also in OS-runtime to make
changes on the authorizations.
OS area specific
authorization
As of PCS 7 V8.0, 2 new operation levels are pre-defined in the User Administrator
being freely configurable:
• Extended operation 1 (No. 1101)
• Extended operation 2 (No. 1102)
Name and password

Users are identified by a name (4 characters or more) and a password (6 characters or
more).

[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 7 and
[231] PCS 7 V8.0 OS Process Control - 12_2011, 5.4.7

PCS 7 System Course
11.2.2 Extended User Authorization Concept
Instance-specific parameterization
There is a new input field "Operation Level" (new attribute "Op_Level") at every relevant
operator-controllable input.
The numbers 1 to 5 are permitted inputs. They are assigned as follows:

• 1 = OperationLevel1_backup = Process Controlling (Preset in the block icon)
(corresponds to WinCC User Administrator „Level 5“)
• 2 = OperationLevel2_backup = Higher process Controlling (Preset in the block
icon) (WinCC „Level 6“)
• 3 = OperationLevel3_backup = Highest process Controlling (Preset in the block
icon) (WinCC „Level 1100“)
• 4 = OperationLevel4_backup = New: Extended operation 1
(WinCC „Level 1101“)
• 5 = OperationLevel5_backup = New: Extended operation 2
(WinCC „Level 1102“)
This permits instance-specific configuration that supports a detailed definition which
functions are available for a specific user (group).

PCS 7 System Course
11.2.3 WinCC Logon versus SIMATIC Logon
WinCC Logon workflow

Terminal bus
SIMATIC PC station 1 User SIMATIC PC station x

login
OS Client1 OS Client x
User User Administrator User Administrator

login
Checking the username and Checking the username and

password and calculating password and calculating
the authorization. the authorization.
SIMATIC Logon workflow

SIMATIC Logon is a central user administration system with access control for SIMATIC
PCS 7 system components, based on Windows 2000/XP and Windows Server 2003.
Checking the username and

password and calculating
Logon Computer the Usergroups.
or Domain
Terminal bus
Passing
SIMATIC PC station information
OS Client1 SIMATIC Logon

Service
User User Administrator
login Passing
information
Calculating the
authorizations of the user, if
the password was correct

PCS 7 System Course
Selection guide for WinCC Logon and SIMATIC Logon
SIMATIC Logon WinCC Logon
One time login is sufficient for several applications.

(OS, Automation License Manager, SIMATIC Manager, etc)
A client/server project with multiple OS clients is used.
One central administration for users/user groups is required. No central administration for users/user
groups is required.
Logon and logoff procedures are to be logged.
We generally recommend that SIMATIC Logon is used, as it provides more benefits

than WinCC Logon and is not associated with any additional costs.
 If you run SIMATIC Logon with a logon computer, this computer must be available at
all times and must not demonstrate any excessive peak loads; therefore, we do not
recommend using the ES as a logon computer.
 The names of the newly created user groups must be written in exactly the same way
in the Windows operating system and the OS User Administrator. These names are
case-sensitive.
Users are only created in the operating system of the logon computer. Once a user
has successfully logged on via the logon computer, authorizations are then assigned
to that user in the OS.
Task: Users
Goal
Different authorizations for different users
Checkpoint
Give a recommendation …
• What do you think how many
users should be configured on a
OS Client?

PCS 7 System Course
11.3 Picture navigation

The pictures in the OS should be arranged in a way as it is done in the Plant View
window of the project (in SIMATIC Manager).
You can navigate in the OS pictures using navigation buttons or, select the picture
directly from the overview area.
Level 2 in Plant
BufferTanks.pdl MaterialTanks.pdl Reactors.pdl
hierarchy
Level 3 in Plant
B410.pdl M110.pdl M130.pdl R310.pdl R340.pdl hierarchy
Plant Hierarchy Setting

Pictures in the OS should be arranged in a way as it is done in the Plant View window of
the project.
A general presetting for the Plant Hierarchy is provided as default to control the
automated generation of the picture tree.
Picture order
The order of pictures in the same level can be set in the specific Hierarchy folder
properties:

PCS 7 System Course
OS compilation
At OS compilation the options to generate the picture tree is to be set as well:
Picture Tree Manager

The Picture Tree Manager in WinCC Explorer shows the arrangement of pictures.

PCS 7 System Course
All of the pictures of the WinCC project that

are still not assigned in the hierarchy and the
picture of an empty container are found in the
selection window.
Picture Tree Manager returns the hierarchy levels you created in SIMATIC Manager
under the same names.
At the bottom of the Picture Tree Manager, you will find all of the pictures that are not
inserted in the plant hierarchy. In the PCS 7 environment, these are the pictures that
you create additionally, because, for example, you want to display them in a picture
window of the process picture.
Picture Tree Manager and user permissions

The hierarchy levels of the Picture Tree Manager are also available when you assign
user permissions. You must make or change user permissions settings in if you create
new areas in the plant hierarchy of SIMATIC Manager. You must set new user
permission for these new areas.
more details.

PCS 7 System Course
How to get the pictures into the hierarchy
PH Level 1
PH Level 2 Area Level 2
PH Level 3 Area Level 3
Areas Level 2
Pictures on the
BufferTanks.pdl MaterialTanks.pdl Reactors.pdl
same level
Areas Level 3
Pictures on the
B410.pdl M110.pdl M130.pdl R310.pdl R340.pdl same level
 ATTENTION!
Avoid any direct changes in the WinCC Picture Tree Manager, for example, do not
insert additional hierarchy levels or containers, or rename pictures. The data
visualized in Picture Tree Manager are derived from the configuration data of
SIMATIC Manager.
Subsequent changes can be overwritten when you recompile the OS, if you have
selected the "Derive picture hierarchy from the plant hierarchy" check box.

PCS 7 System Course
11.4 OS Project Editor

The OS Project Editor inserts pre-configured pictures, script actions, and tags in the
PCS 7 project. This editor also specifies the typical settings for a PCS 7 project:
There you make the settings for the user interface that the operator will use for
monitoring and controlling the plant in process mode. Following compilation of the OS,
the data you have already created in SIMATIC Manager will be transferred
automatically.
When an OS project is created in the PCS 7 ES, the OS Project Editor is called in the
background and initialized with default settings. If you want a configuration other than
the default configuration, start the OS Project Editor via WinCC Explorer and configure
your desired project settings.
You can conveniently transfer them to another OS using the Import/Export function in
the "General" tab.
You open the OS Project Editor in WinCC Explorer
Example
The overview area, on the top of the screen, contains a number of buttons representing
the areas of the plant. By default 16 buttons are present. The Project Editor can be used
to make adjustments to the buttons.
11.4.1 Layout
In the "Layout" tab, you configure the appearance of the runtime user interface.
To adapt a larger or smaller amount of areas, the number of buttons can be edited in
the "Layout" tab:

PCS 7 System Course
11.4.2 Area
In the “Area” tab, you configure the arrangement of the plant sections in the area
overview.
The “Area” tab of the Project Editor should be used to insert “empty buttons”.
Empty buttons can be used as placeholder for future extension or adapting a process
like arrangement of areas.
1
2
3
4
5
1 2
3 4
Access to areas missing authorization

In the User Administrator, you specify the area-specific access rights for users in
runtime. However, you can also allow users to select pictures and group displays of
areas for which they have no authorization.
Users without access rights to areas have the following access options:
• Picture selection is not possible. The user has no access to this area (standard
behavior)
• The picture can be selected using area button. The user can select the pictures of
these areas for monitoring purposes. Access to the group displays in the overview
and Picture Tree Navigator is not permitted. Area-specific messages are not visible.
Operator process controls with PCS 7 picture components are not possible, operator
inputs in process pictures depends on the configuration in the pictures.
• Picture can be selected using both the area button and the group display. The user
can select the pictures of these areas for monitoring purposes. Access to the group
displays in the overview and Picture Tree Navigator is permitted. Area-specific
messages are not visible. Operator process controls with PCS 7 picture components
are not possible, operator inputs in process pictures depends on the configuration in
the pictures.

PCS 7 System Course
11.4.3 Runtime window

In the „Runtime Window" tab, you configure the number and arrangement of the pre-
configured picture windows.
• Definition of the maximum number of windows which can be opened when calling
faceplates and trend displays.
• Definition of the maximum number of faceplates which can be opened on a monitor.
“Maximum number per picture module” means faceplates of the same instance. The
last faceplate opened is closed automatically when you open the next faceplate after
the maximum number is reached.
• Loop display mode for picture components. The windows are automatically adapted
to fit the size of the picture on opening. Their size cannot be changed. You can
configure the number and position of the windows. The loop display mode is not
relevant for faceplates of the Advanced Process Library but for the PCS 7 Standard
library.
• Group display mode for picture components and for windows in the function "Picture
by Name". The windows open with predefined dimensions which can be changed, if
you activated the "User defined" check box.
• Trend display mode for windows configured with the "Trend Online" function. The
windows are adapted to fit the size of the picture. Their size can be changed. The
configuration options are the same as for the loop display mode.

PCS 7 System Course
11.4.4 General
Activities when processed by project editor

In PCS 7 projects, you can change configuration data during operation using the
"Download changes" function ("Online delta download"). Every configuration change via
the user interface or programming interface is recognized by the runtime software and
accepted during operation.
You set this behavior for the OS Project Editor in the "General" tab. If the configuration
of the OS allows modification of data during operation, data that prevent a "Download
changes" function are brought into the project during the initial configuration. This
applies in particular for alarm configuration and the startup list. Each time the OS
Project Editor is run hereafter, only those configurations that do not prevent the
"Download changes" function are carried out.
In the case of a complete configuration, all settings are transferred again to the project.
Changes to configuration data during operation are lost in the process. You must
download the entire OS. After this, you can again switch on the delta mode of
"Download changes" in the "General" tab.
• Settings for the logs created in OS Project Editor

Printing or viewing the documentation of the current project configuration
• Execute the export/import of the current configuration settings in OS
Project Editor as a convenient way of integrating other Operator Stations in the
project

PCS 7 System Course
11.4.5 Message display

Settings for the following messages displays:
• Message filter
• Extended message line
• Authorization check of messages without area entry
• Manual hiding of messages (Smart Alarm Hiding)
• Sorting of message pages
• Creating the group display hierarchy
• Block comments of operating messages
Assignment of messages without defined area allocation:

Process control messages are not assigned to a specific OS area, for example. You can
select an OS area from the drop down list box to automatically assign these messages
to this area in for the active process.

PCS 7 System Course
11.4.6 Basic data

Definition whether to restore the factory state of the object. The list includes all project
objects which were changed after initialization of the basic data.
The default settings which were automatically activated in the course of ES engineering
configuration are displayed when you initially open the OS Project Editor.
The "Basic data" tab, however, forms an exception: The list entries change
automatically, depending on the picture and script configuration on the OS. You must
first confirm modified basic data picture files and actions in the "Basic Data" tab before
these data are accepted in the project.
Task: Project Editor – Area buttons and number of faceplates
Goal
Area buttons MT, R and BT on the left, area button Signal box on the right.
Checkpoint
What do you believe …
• What is the use of displaying
several copies of a faceplate of the
same block?

PCS 7 System Course
11.6 Time synchronization

11.6.1 General principle
Process data are only evaluable, if all components of a process control system are
using the same time of day. Because that, all subsystems like OS and AS should run
with time synchronization.
The synchronization is basing on a master / slave architecture.
Two general synchronization modes can be distinguished:
• The NTP mode is suitable for PC Stations without own time synchronization
functionality. By the NTP mode, network components fetch the time from an external
NTP server. SICLOCK TC 400 is recommended as NTP server in PCS 7 plants.
• The SIMATIC mode uses an internal time synchronization functionality provided by
WinCC Software on OS Server Stations. Those OS Servers are able to work as
cooperative time masters.
OS Client
Slave
Terminal bus
OS Server / Single station

Master
Plant bus
AS 1
CPU CP 443-1 CP 443-5Ext
Slave Transparent Slave
DP-Master (Profibus) DP-Master (Profibus)
 The CPU with integrated Ethernet interface can only be synchronized via the NTP
mode.
 For further information about several conceptions of time synchronization see

[141] PCS 7 V8.0 Time synchronization - Function Manual- 12_2011, 2.1 and
[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_201, 12.1.1

PCS 7 System Course
11.6.2 PLC Clock Setting in OS Computer properties
Operating with Local Standard Time and Coordinated Universal Time (UTC)
In PCS 7, UTC is used internally as a rule within the system. Time information displayed
to the operator in process mode can be converted from UTC to the respective local
time. This makes it possible to configure a system, for example, with the automation
system in a different time zone than the operator station. If necessary, the plant operator
can also switch back and forth between coordinated universal time display and local
time display in runtime.
See the OS Computer properties below with its preferred settings:

PCS 7 System Course
11.6.3 Time Synchronization Settings in the WinCC Explorer

Time synchronization via the plant bus requires one of the following settings in the
WinCC project of the OS Server / Single station.
These settings have to be done in the Editor “Time Synchronization” of the WinCC
Explorer.
Select here the

network adapter (CP)
for the plant bus
 In our training project we do not cover the OS server / client configuration.

The settings of an OS Single station are similar to those of an OS server.
An OS client needs also settings in its WinCC project. As described in the
introduction, an OS client has to be synchronized via Terminal bus as slave. In
SIMATIC mode the client uses the time from a connected OS server (WinCC server).
 See [141] PCS 7 V8.0 Time synchronization - Function Manual- 12_2011, 5.5 for
more details

PCS 7 System Course
11.6.4 Settings in the HW configuration of the AS
Settings in the AS-CP for the plant bus

The time message frames of the time master are forwarded to the automation systems
on the plant bus. The AS Communication Processor for Industrial Ethernet requires
settings:
Plant bus
AS 1
CPU CP 443-1 CP 443-5Ext
Slave Transparent Slave
DP-Master (Profibus) DP-Master (Profibus)
Settings in the AS-CPU
AS 1
CPU CP 443-1
Slave Transparent

PCS 7 System Course
Settings in an AS-CP for Profibus
AS 1
CP 443-1 CP 443-5Ext
Transparent Slave
DP-Master (Profibus)
Profibus
Station: here LAN: here

CP 443-5Ext Profibus Subnet
 See [141] PCS 7 V8.0 Time synchronization - Function Manual- 12_2011, 5.8 for
more details

PCS 7 System Course
11.7 Lifebeat Monitoring

The lifebeat monitoring function is used to monitor the functionality of all AS and OS of
the process control system. A process control message is generated if an AS or OS do
not respond to a lifebeat request.
Lifebeat monitoring is performed centrally from an OS that you have designated as the
lifebeat monitor. The lifebeat monitor monitors all OS servers, OS clients, and
automation systems.
You configure lifebeat monitoring in the "Lifebeat Monitoring" editor of the WinCC
explorer.
Requirements
• The hardware configuration and network connections for all automation systems and
operator stations have been configured in SIMATIC Manager.
• An OPC connection is created in WinCC Explorer for each operator station that you
wish to monitor.
Configuration of AS monitoring
Select device
Type in a name type and
e.g. AS08 connection
 The system provides a picture named @CONFIG.pdl for the Lifebeat Monitoring.
You can adapt this picture to your needs.

PCS 7 System Course
What you see in the OS Runtime

• No problem: If there is no problem on the level of communication between the OS
and the system being monitored, the Plant Network Configuration picture displays the
icon of the AS as shown below:
• AS in STOP mode
• AS in RUN again
 See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 13.1 for
more details

PCS 7 System Course
Task: Time synchronization and Lifebeat monitoring
Goal
Establish the time synchronization and AS lifebeat monitoring in your training project.
Checkpoint
What you think …

• How does the information flow
look beginning from a signal
change in a digital input channel
to the message on a OS client?

PCS 7 System Course
11.9 WinCC Basic Objects and special additional for PCS 7

WinCC is the platform for the visualization of your plant. WinCC is supporting you by
several types of objects and object libraries.
Graphics Designer
The Graphics designer (an editor in the WinCC explorer) is the entrance to the process
pictures. Here you can edit the process pictures of your plant as files of type .pdl. By this
editor you also find all pictures, you created before in the plant hierarchy of the SIMATIC
Manager as place holder (for instance Reactors.pdl).
11.9.1 WinCC objects and libraries

Process pictures consist in single objects beginning from simple graphic standard object
like circle, rectangle, polygon to individually preconfigured smart objects and controls
which are connected with the process and with interface for input / output of process
values.
In general we distinguish between static and dynamic objects.
 See [104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 8.8 for an
overview of dynamic PCS 7 standard objects.

PCS 7 System Course
The following figures give an overview about available graphic objects:
Standard
Objects
Controls
Access to ActiveX controls:

2 different ways to the same result
The graphic objects are assorted in a tree structure, controls collected in an own tab:
Standard e.g. line, polygon, ellipse, circle, rectangle, static text
Objects
Windows Selection of windows-like operation elements
Objects
Smart Objects e.g. application window, picture window, OLE object, I/O field, bars, status display
Tube objects Selection of typical connection elements required in a flow scheme. Since PCS 7 V7.1
the polygon function is available for tube connections.
Controls The 'Controls' tab contains as standard a selection of the most important ActiveX
controls provided by WinCC. Other controls can be linked.

PCS 7 System Course
11.9.2 How to make object properties dynamic

There are several options for dynamic updating of objects inserted in a process picture:
Tag connection VBS Action C Action
A script action is created by linking an event, such

Simply interconnect objects, for
as a change in a binary tag, to a function which is
example, with the I/O of a block
programmed in ANSI C or in Visual Basic. This
instance of a CFC chart.
function is activated by an event or cyclically.
A script action is normally linked directly to an
Options for object property which is also influenced by the
dynamization action. For example, a C action can be used to set
of object the color of an analog value, depending on a tag.
properties
Direct connection
Dynamic Dialog
A link is established between objects. You can formulate the dynamic

Parameters only have to be assigned updates using tags, functions and
for the source object; then connect this arithmetic operations in an expression.
source object to the target object. You can define specific value ranges.
Tag triggers and OS Runtime performance

Triggers are used to execute actions at runtime. To do this, a trigger is linked to an
action, forming the triggering event for calling the action. Actions without triggers will not
be carried out.
Cyclic triggers are a means of processing periodic actions in Value Trigger interval
WinCC. In the case of a cyclic trigger, the action is executed
when the trigger event occurs, e.g. every 20 seconds.
Move cyclic computing tasks into the AS and

Time
don't execute them on the OS!
Tag triggers consist of one or more specified tags. The action which Value Query interval
is connected to such a trigger is executed if a change in the value of
one of these tags was detected when the query was launched.
Tag triggers should be used for a high performance level. Time
Event-driven triggers: Actions which are connected to an event are Value Mouse action
executed whenever this event occurs. Events can be, for example,
mouse control, keyboard control, or changes in focus.
Extensive C / VBS actions increase the system load with a
Time
negative influence on picture-call times in runtime.
further information.

PCS 7 System Course
11.9.3 Tag Connection – Working with the Tag Selection Dialog

After the OS compilation, process values of the SIMATIC Manager database are
available in the WinCC Tag Management. You can link an attribute of the object
properties to a tag using the Tag Selection Dialog.
Application example
The bar display in a tank is to be linked with the process value of the tank level.
Call the Tag

Selection Dialog
Select the
tag trigger
Bar displays have a
reduced configuration dialog:
The attribute to be linked is
already predefined.
List of all the PCS 7 process

tags in the data window.
Process value
to be linked
Result:
further information about the Tag Selection Dialog and the Tag sources.

PCS 7 System Course
11.9.4 Dynamic Dialog

In Dynamic Dialog you formulate an expression by using tags, functions, and arithmetic
operands. The value of the expression, the status as well as the quality code of tags
used within the expression is used to form the object property value in Runtime.
The Dynamic Dialog may be used to map the value ranges of a tag into colors,
monitor/map single tag bits or Boolean tag value onto colors or texts or monitor tag
status or tag quality code.
Application example
Change the color of a bar level display depending on an activated simulation mode.
Open the object

properties and select the
attribute to be linked
Tag trigger
Tag Selection
Dialog
Bar color depending

on a boolean tag value
This includes
structure tags
and internal tags
Process value
to be linked
Structure
instance
Tag Selection Dialog with

another Data source view
Result of linked
Dynamic Dialog:

PCS 7 System Course
11.9.5 Direct Connection

Direct connection can be used as a reaction to events. If the event occurs in Runtime,
the 'value' of a source element (Source) is used for a target element (Target).
The advantages of direct connection are the simple configuration and the time response
in Runtime. Direction connection has the best performance of all dynamization types.
Application example
This example shows a configuration of a button to transfer a predefined setpoint to the
temperature controller as internal setpoint by one mouse click.
Source
Open the object
properties and switch Target
to Events tab
Open the Direct

Connection Dialog
Open the Tag

Selection Dialog
Predefined Direct: Update of the tags should

setpoint be done permanently
Indirect: Update only when called.
Result of Direct
Connection:

PCS 7 System Course
11.9.6 The Dynamic Wizards

With the Dynamic Wizards, you can make an object dynamic using C actions. When you
execute a wizard, preconfigured C actions and trigger events are defined and
transferred to the object properties. The C Actions are sorted in topics in the form of
tabs. The content of the individual tabs can vary depending on the selected object type.
PCS 7 specific
context
General
WinCC context
Provided in a tool box of

the Graphics Designer
BPC: in context of
Basic Process Controls
Application example
Mouse click on an object shall cause a picture exchange in the working area.
Select the object

to be dynamized Start the required
Dynamic Wizard
Result of
Wizard run:
SITRAIN

PCS 7 System Course
Task: PCS 7 compliant picture change
Goal
Configure a button in a process picture to allow an operator to perform change to
another process picture.
Checkpoint
Do you know …
• Is it possible and usefull to get rid
of the navigation buttons in the
toolbar at the bottom of the
screen?

PCS 7 System Course
11.10 Group display

11.10.1 Overview in Runtime
You created a hierarchy corresponding to your plant structure. Even in a process picture
that only displays a general overview of an entire plant, the operator requires
information from the process tags located in pictures from lower hierarchy levels. You
can map this information by means of group display: The group display outputs states in
color code (e.g. alarm, warning).
Collected information
from the pictures
R310 / R 320 / R330 / R340
Collected information of
all process tags in R310
Updating group displays

Group displays are updated:
• When the project is downloaded.
• When saving in the WinCC "Picture Tree

Manager" editor with "Recalculate the group
display hierarchy completely while saving"
check box selected.
You use this update when you simulate process mode from SIMATIC Manager on the Engineering Station.
• When starting the Project Editor with

the "Create/update group displays"
check box activated.
more details.

PCS 7 System Course
11.10.2 Settings for installing Group Displays

Setting in the OS project editor:
The Group Displays are to be placed in the pictures:

• invisible
• stacked in the left top of the picture
If you want them to be visible on a specific position in the picture, you must:
In the higher
level picture Change the attribute
Reactors.pdl: Display from No to Yes
Move them to the

desired position
11.10.3 Group Display to represent a single block

Extra to the Group Display as it is installed in Block Icons and Faceplates, you can
install a Group Display into a picture to represent a single block (tag structure).
From the Smart Select the object Start the

Object palette to be dynamized Dynamic Wizard
by double click
Result of the
Wizard run

PCS 7 System Course
Task: Project Editor – Message Display
Goal
Checkpoint
Let‘s think about …

• What may be the use of not having
visible the group displays in the
area pictures?
11.11 Alarms
11.11.1 Basic Concept of the Event-Signaling System
Origin of a message
Messages can originate in different locations within the control system depending on the
configuration. The time stamp of the message is influenced by where it originates.
The illustration below shows an example with a distributed I/O, ET 200M.
Single Station OS
1. Origin of a message in the operator station
Plant bus (Industrial Ethernet)
SIMATIC S7-400 AS 2. Origin of a message in the automation system
PROFIBUS DP
ET200M 3. Origin of a message in IM 153-2
Events which originate in the AS (2) or in the ET 200M (3) are transmitted as individual
messages to the OS via the plant bus. The message is transmitted along with the
corresponding time stamp. The messages appear in chronological order, with the time
they occurred, in the signal lists of the OS.

PCS 7 System Course
Event-signaling classes
Process control signals Process signals Operating messages
Detected errors in PCS 7 own Process signals indicate Operating messages are
components (AS, OS, etc.). process events that take place generated when an operator
Process control signals are in the automated process, such controls process variables, for
generated by the driver blocks as limit value violations and example, changes the
in PCS 7 and do not have to be event signals. operating mode of a controller.
configured. Events signals are a subgroup Operating messages are
Such errors range from failure of process signals. They signal generated automatically when
of a component to a wire-break process variables which serve you use the faceplates which
signal for a connected I/O to evaluate a technological are provided by the PCS 7
module. variable, such as an elapsed- Libraries.
time counter.
System messages
System messages are all messages that are generated by the SIMATIC PCS 7 system.
Loop in Alarm
Process and control technology messages from technological blocks which are
visualized on the OS feature the "loop-in-alarm" function. You can use this function to
select the faceplate for this process tag straight from the signal list.
 For further basic information see

[103] PCS 7 V8.0 Engineering System - 12_2011, 6.9.1,
[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 10.1 and
[231] PCS 7 V8.0 OS Process Control - 12_2011, 8.1
11.11.2 Names of limits

PCS 7 System Course
Naming convention in the PCS 7 Standard library:
HH Alarm active
LL Alarm active
H Alarm active
L Alarm active
MO_PVHR
U_AH = HH Alarm Limit
U_WH = H Alarm Limit (Warning)
U
U_WL = L Alarm Limit (Warning)

U_AL = LL Alarm Limit
MO_PVLR
Naming convention in the PCS 7 Advanced Process library:
AH Alarm active
WH Alarm active
TH Alarm active
TL Alarm active
WL Alarm active
AL Alarm active
Scale.High
PV_AH = High Alarm Limit
PV_AH = High Warning Limit
PV_TH = High Tolerance Limit

PV
PV_TL = Low Tolerance Limit
PV_WL = Low Warning Limit
Scale.Low PV_AL = Low Alarm Limit

PCS 7 System Course
11.11.3 Events in Alarm Logging
1 2 3 4 5 6
Event: Ack Ack
LIA 224 yes
PV > U_WH time
no
Incoming alarm list in out in out
Acknowledged alarm list in out
Outgoing alarm list in out
Journal list in in in in in in
Group Display
6
5
4
3
2
1

PCS 7 System Course
11.12 Read Back

11.12.1 Changes in CFC test mode
Changes made to parameters in CFC test mode will be consistent:
• It is updated in the chart
• It is updated in the instance data block offline (in the project)
• It is updated in the instance data block online (the AS)
ES –
CFC (Test mode)
3
OS – Faceplate
2
Block
properties
AS

PCS 7 System Course
11.12.2 Changes by operation on OS

Changes made to parameters as an operation on the Operator Station have different
consequences:
• It is updated in the instance data block online (the AS) only:
ES –
CFC offline
No change!
1 OS –
2
Faceplate
No change!
Updated!
AS
So there will be no consistency between the AS value and the value in the CFC chart
and the instance data block offline.
As soon there is made a complete compilation and download, the chart-version of the
value will be the actual value again.
This can be prevented by a Read Back…

PCS 7 System Course
11.12.3 Read Back

A Read Back can “repair” the inconsistency:
• Values are read from the AS and stored in the CFC charts.
ES –
CFC offline
OS – Faceplate
365
1
AS
Read back from
CFC Editor
Read back from

Simatic Manager
Context menu

PCS 7 System Course
Task: Alarms
Goal
Proper settings for the limit values and applying an external alarm.
Checkpoint

• In the PCS7 Message Configuation
dialog window of the MonAnl block,
why are not all fields editable?

PCS 7 System Course
11.14 Suppressing and Locking of Messages
Suppressing messages in CFC

The MsgLock = 1 parameter is used to selectively suppress the following messages
depending on Feature bit 25:
• All messages at the block or
• All messages at the block, except for process control messages, the message class
of which is disabled by default (for example, CSF, motor protection, feedback error)
and external messages.
Messages already queued received the "outgoing" status with MsgLock = 1.
Locking messages in the faceplate

The "Lock/unlock messages" function for individual message-capable blocks and all
message-capable blocks in an OS area is used when the plant operator wants to lock or
unlock all messages of a message-capable block or all messages of all message-
capable blocks in an OS area.
Messages generated at locked blocks in the automation system are neither displayed
nor archived in group displays in the process control.
The disable operation performed by the operator is recorded in the operator activities
log. The status of the disabled messages is visualized in the group display and in the
overview area using the group display hierarchy.
All queued messages are suppressed and are not displayed in the message window of
the faceplate. The "Lock message" icon in the toolbar of the faceplate changes to the
"Unlock message" icon. All four fields of the group display in the faceplate are displayed
with a white "X" on a gray background.
Pending messages for this faceplate are no longer displayed in the incoming alarm list
of the message system.

PCS 7 System Course
Operator authorization for the locking of messages

The required operation level for the locking of messages is pre-defined with:
• OperationLevel1_backup (in the WinCC User administration „Level 5“)
As of PCS 7 V8.0, the operator authorization for the button "Lock message" can be
defined with an internal variable @LockMessageAuthLevel). The configuration is made
with the numbers 1 to 5, applying to the respective Administration levels 5, 6, 1100,
1101, 1102. This setting applies for a complete OS project.
The configured operation level must also be defined in the block icon or in the faceplate
of the measuring point (e.g. higher-level process controlling) as otherwise operation will
not be possible.

PCS 7 System Course
11.15 Smart Alarm hiding

11.15.1 Overview
The alarm management in PCS 7 offers the “Smart Alarm Hiding” function from V7.0 on.
This function allows hiding of alarms to reduce the number of messages during process
operation (avoiding „flurry of messages“).
“Smart Alarm Hiding” offers the two following options to hide alarms:
• Hiding and showing alarms manually
• Hiding and showing alarms automatically
Behavior/Features
The behavior of the “smart alarm hiding” in process operation is implemented as follows:
• The messages are hidden in the following alarm lists: incoming alarm list, outgoing
list, acknowledged alarm list and one line (except alarm journal, process alarm list,
operation list) and the group displays.
• During process operation you can manually hide the following lists:
− incoming alarm list
− outgoing alarm list
− acknowledged alarm list
• Currently pending messages which are hidden are displayed in the “list of hidden
messages” (except: gone messages).
• The “messages to be hidden” list contains all messages to be hidden upon arrival.
• Hidden messages can be made to reappear in the incoming alarm list or outgoing
alarm list via the “list of hidden messages”.
• Hidden messages are archived.
• If operator stations are redundant, the message archive is updated.
• The acoustic signaling (horn) of hidden messages is suppressed /acknowledged.
• The status of hidden messages is not displayed in the group displays of the process
pictures and faceplates.
• Manually hidden alarms are redisplayed after a defined time.
• Manually hidden alarms are acknowledged automatically.
• Manual alarm hiding is OS server specific.
• An operator message is generated when the operator hides and shows alarms
manually.
• When hiding and showing a message, a message with the status show or hide is
generated.

PCS 7 System Course
Overview about configuration steps
Shared Declarations Process Object View

Enumerations Messages Checking Operating State for Hiding
Operating State
1
“Hiding Matrix”
2
Logic to determine State representation

the Operating state for a Block group
OS
STRep Rules
PIDConL
State1 (Filter)
MotL
State2
VlvL
State3
Alarms
AS
Blocks with
alarms Al
ar
m
s
STRep Archive
PIDConL
State1
MotL
State2
VlvL
State3
AS
Blocks with
alarms
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 6.9.4 for more details.

PCS 7 System Course
11.15.2 Automatic Alarm Hiding
Plant conditions
Operating states
for hiding
• The definition of plant conditions is using enumerations which are defined in the
Shared Declarations in SIMATIC Manager’s component view. To do this, an
enumeration with the name "Operating State" is configured. Values from 1 to 32 can
now be defined as plant conditions in this enumeration. The value "0" is the
presetting for a "normal" plant condition. In this state the plant is within normal
operating limits and no alarms are hidden. You can now assign any plant conditions
to the values 1 to 32.
• In a multiproject consisting of several subprojects, the operating states are created in
the global declarations in the master data library and then updated in the multiproject.
 The enumeration can of course also have a name different than "Operating State".
However, this enumeration must be explicitly selected in the properties of the
"StateRep" block. The enumeration "Operating State" on the other hand has been
preset.

PCS 7 System Course
Logic to determine the operating states: STRep block

The technological block STRep converts Boolean input signals into the corresponding
operating state. Interconnect the state inputs of the STRep block to a logic that
determines the desired operating state.
More than one

status is active
The STRep block features 32 "StateX" Boolean inputs. These inputs correspond to the
values of the enumerations you have created in the first configuration step.
Block group
STRep block
Other
technological
blocks that can
generate alarms.
One technological area is composed of several technological blocks that can generate
alarms. To hide alarms for sub plants, you must combine all technological blocks of a
sub plant as one block group under an identifier (e.g. “MT”, “MaterialTanks”…).
All the blocks which are combined in a group are controlled by a STRep block. This
means that several STRep blocks have to be used where necessary to represent
several sub plants.
If the technological blocks of entire technological areas of a block group are assigned,
then this assignment is best made in the PO view.

PCS 7 System Course
“Hiding Matrix”
Process states
In the next configuration step you configure the “Alarm Hiding Matrix” in the PO view.
Here you can define which alarms of the group’s message capable blocks to hide for
which plant condition of the corresponding block group.
 You facilitate the work by filtering the display in the process overview to the block
group currently to be configured. You filter according to “Column -> Block group” and
enter the name of the block group in “Display”.
Besides configuration in the process object view, you can also export the data to
CSV, edit (e.g. in Excel) and re-import them.
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.3.18 for more details.
11.15.3 Manual Alarm Hiding
Use this checkbox to

activate the button for
the manual alarm hiding
in the toolbar of the
incoming alarm list.
By hiding alarms manually, the operator can put those alarms out of sight which are
irrelevant for the present operating state.

PCS 7 System Course
Manual alarm hiding is OS server granular. If an alarm is hidden manually on an OS

client, this alarm will neither be visible on any client accessing the associated server.
 Both, the changing of the hiding time as well as the display of the button for manual
hiding are delta download-capable.
11.15.4 Impact to runtime view of message display

There are two new buttons in the
New button for
keyset to open two new controls
manual hiding in the
incoming alarmlist!
 Automatically hidden alarms are still displayed in the alarm list of the associated
faceplates. This allows you to see whether alarms are present for a measuring point
although automatic alarm hiding is active.
Task: Smart alarm hiding
Goal
Smart Alarm Hiding for the Material tanks
Checkpoint
What do you think…

• …is the difference between alarm
locking and alarm hiding?

PCS 7 System Course
11.16 Status Displays

11.16.1 Use and main Features
A way to represent dynamics in the AS (Process), is installing a display into an OS
picture:
OS
States AS
Modes
Events
Process
The display can be installed into a picture as an autonomic object or as a part of a Block
icon.
The displays have in common:

• covering a rectangular area on the screen
• switching between different graphics/colors controlled by values
What’s the difference?
Status Display Switching between different graphics, controlled by a status

value representing a single tag
Status Display (extended) Switching between different graphics, controlled by a status

value formed by up to 4 bits. Additional or alternately, bits of a
Group value (.EventState) can control the graphics.
Analog Display Decimal representation of an analog value. Its color and

(extended) flashing state is controlled by a Group value (.EventState)

PCS 7 System Course
11.16.2 Insertion of Status Displays
Symbolic placeholder
2
3
1. Select the object in the Object Palette / Smart Objects.

2. Move the object into the working area using a drag-and-drop operation.
3. This opens the configuration dialog box for the desired status display.

PCS 7 System Course
11.16.3 Tag connections of Status Displays

The Status Displays can have connections:
Status Display
• Current Status: To be connected to a 1 bit, 8 bit, 16 bit or 32 bit tag. Using the
configuration dialog, a status can be formed by selecting bits from these tags.
Extended Status Display

• Group value: To be connected to a 32 bit tag containing 16 status bits and 16
acknowledge bits. This is usually connected to the .EventState of a block (alarm
configuration using the ALARM_8P block)
• Status1…4: To be connected to a 1 bit, 8 bit, 16 bit or 32 bit tag. Using the
configuration dialog, a status can be formed by selecting bits from these tags.

PCS 7 System Course
11.16.4 Graphics of Status Displays

The Status Displays can display different picture elements depending on the status.
The graphics directory "GraCS" of the current OS project provides a wide choice of
standard graphics. The picture selection shows all pictures in the "GraCS" folder.
Graphics and pictures of the following formats can be inserted: BMP, DIB, ICO, CUR,
EMF, WMF, GIF and JPG.
User-defined pictures for a Status Display

You can create your own graphics as objects in a .pdl picture file using Graphics
Designer. These picture elements for a Status Display can be exported as metafiles
(with the extension .emf).

PCS 7 System Course
11.16.5 Example of a Status Display connected to a tag

Tag providing
State
Each bit of
Tag value
Result: Drag pictures
to State
Add a State
Status list
The status list shows the linked pictures and the specified flash frequency for all
configured states.
• States can be inserted and every setting can be changed with a pop-up menu.
• Pictures of the picture selection can be referenced by dragging them with the mouse
to the required position in the state list.
Bit Position
A state can also be assigned to a specific bit position on the tag.

PCS 7 System Course
11.16.6 Example of connection to a Status value containing several bits
Statusword1 := Status2 of APL motor block MotL: Status bit Parameter

20 Motor is stopped
21 The motor is stopping.
3 22 The motor is starting.
23 the motor is running
24 Error in motor
Bit selection for forming the status value: 24 23 20
Bit position Index Icon

4
24 23 20
0 0 0 0
0 0 1 1
0 1 0 2
0 1 1 3
1 0 0 4
Double click to
1 0 1 5
assign the picture
1 1 0 6
1 1 1 7
1. APL blocks provide output parameters Status1…4 offering 32-bit status words. The
bit allocation of these status words is described in the block help (section
“Description”, “Status word allocation for Status1 parameter”, etc…).
2. The Extended Status Display is equipped with the Attributes Status1…4 in the
theme Miscellaneous. These attributes can be linked dynamically to output
parameters of the block and give the status words 1…4.
3. The main feature of an Extended Status Display is to allow the formation of a status
value as result of a bit selection from the status words1…4. The bit selection has to

PCS 7 System Course
be defined in the Configuration Dialog, tab „General“, of the Extended Status

Display.
4. The tab “Assign pictures” shows an Index list, where you assign the graphics to the
possible values of the status value. The index list allows also the assignment of
flash pictures.
11.16.7 Example of connection to the Group value (.EventState) added to the

Status value
Bit selection from

the group value
Tip: Save the
configuration before
changing the tab

PCS 7 System Course
1. The group value is triggered by a tag which represents the message status. Other
dynamization types are not possible. The group value is usually interconnected with
a PCS 7 EventState. In PCS 7, this is usually the "EventState" tag of a process tag
(WinCC Tag Management, WinCC Tags).
2. The evaluation of the group value has to be activated in the Configuration dialog of
the Extended Status Display.
3. The alarm status results from the evaluation of the bits of the group value. If the
group value contains multiple bits, the priority determines which status is displayed.
4. Based on the evaluation of the group value above, pictures can be assigned:
Bit position Index Icon
24 23 20 3
0 0 0 0
Additional index positions

0 0 1 50

0 1 0 100

0 1 1 119
Index calculation
includes the selected
bits of the Group value.
For the bits of the group value, you assign pictures for the "Came In" (+), "Came In
Acknowledged" (+Q) and "Went Out Unacknowledged" (-) statuses.
Task: Status display of stirring motors
Goal
Status display of the stirring motors in the overview picture of the reactor
Checkpoint
What is your opinion…
• …why we recommend to export the
index table after changes?

PCS 7 System Course
Content 12
12 Archiving System ....................................................................................................3
12.2 Introduction ............................................................................................................................ 3
12.3 Archive configuration ............................................................................................................. 6
12.3.1 Preparing the OS for archiving .............................................................................................. 6
12.3.2 Alarm logging (of messages and alarms) .............................................................................. 7
12.3.3 Tag logging (of process values)........................................................................................... 10
12.4 Configuration of WinCC Controls......................................................................................... 13
12.4.1 Display of process value trends by the Online Trend Control ............................................. 13
12.4.2 Display of customized alarm lists in the process picture ..................................................... 20
SIMATIC PCS 7 – Archiving System

PCS 7 System Course

PCS 7 System Course
12 Archiving System

• The mechanism of logging alarms
and process values

• Configure the alarm and tag logging
• Customize the presentation of
events, alarms and the history of
process values
12.2 Introduction
AS block
OS Tag management
values and Alarm system
messages Archiving procedures
Tag Slow Tag Fast Messages
Tag Msg
Segments
Archives Backup

PCS 7 System Course
In PCS 7 there are two different types of archives:
Message archive System archive
• Storing alarms and messages • Storing archive tags

• Use the “Alarm Logging" editor for configuration • Use the “Tag Logging" editor for configuration
• The time stamp on archived messages is • PCS 7 creates this archive automatically the
always in standard UTC format first time you compile the OS with the "Archive
(Coordinated Universal Time). tags" option.
• A distinction is made between 2 archive types:
“Tag Logging Fast” archive type „Tag Logging Slow” archive type
• Acquisition cycles less than or equal to one • The Tag Logging Slow archive type is used when
minute. the acquisition cycle is longer than one minute.
• The default value of one minute can be
changed manually via the archive configuration
of the "Tag Logging Fast" archive type.
"Archiving" and "Long-term archiving"

By default, archiving is performed locally on the OS servers.
The local archives of OS servers are configured as recirculation archives: When the
archive has reached capacity limits, the oldest values are deleted to release space for
saving new values. This corresponds with "FIFO" (First-in first-out) principle.
If the external archive server is not available for a certain period of time, the OS server
will attempt to export at a later point in time. As long as the data is still in the
recirculation archive, this remains possible without loss of data.
Compression and
circular logging
The archive values associated with TagLogging Fast and
also with TagLogging Slow (as of PCS 7 V7.0) are saved
in the database in a compressed state, although this does
not impair the quality of the values.

PCS 7 System Course
Short-term archiving
Long-term archiving
More economical version for the High-performance version for Perspective

lower performance range modernization and expansion of high-performance version
plants with CAS
The following products are offered for OS long-term archiving:

• StoragePlus:
More economical version for the lower performance range; for archiving about 1 600
values/s from as many as four single stations, servers or pairs of servers
• Central Archive Server (CAS), can be configured as single or redundant version:
High-performance version for modernization and expansion of plants with CAS; for
archiving about 10 000 values/s from up to 11 servers or pairs of servers
• Process Historian
Perspective high-performance version
 Please refer to our SITRAIN course PCS 7 OS Engineering (ST-PCS7OSE) for more
information about the design and configuration of long-term archiving in PCS 7.

PCS 7 System Course
12.3 Archive configuration

12.3.1 Preparing the OS for archiving
When using the external archive server, the following property must be configured on
each operator station from which values are to be archived:
Archive configuration
The system always offers two criteria for specifying the archive size of a single segment
and the overall size of the circular log:
• Definition of a time period
• Physical size in bytes
If one of these two criteria is exceeded, this will lead to a switch to the next segment in
the case of a single segment, or to the overwriting of the first segment of the entire
circular log.
Archive configuration includes settings in following tools:
• Definition of size and storing location (Logging Editors in WinCC Explorer)
• Selection of values (tags) and messages to be archived (SIMATIC Manager)

[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 11.1 and
[121] PCS 7 Compendium part a - Configuration Guidelines - 03_2009, 7.4.2

PCS 7 System Course
12.3.2 Alarm logging (of messages and alarms)
Data transferred from SIMATIC Manager

Enter any necessary special message texts in SIMATIC Manager in the block properties
of a block instance in a CFC/SFC chart. You have also made the AS-OS assignment in
the plant view of SIMATIC Manager.
Mass data engineering in the process object view supports also editing messages.
Displays the message texts of the signaling blocks

belonging to the process tags and CFC/SFC charts
displayed in the "General" tab
Cells with white

background can be
edited directly

[103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.10.8 and
[104] PCS 7 V8.0 Operator Station - Configuration Manual - 12_2011, 10.3.1

PCS 7 System Course
Alarm Logging Editor
The messages with the corresponding message texts are automatically

applied in the "Alarm Logging" editor of the WinCC Explorer during the
compiling of the OS.
Archive size
Archive size definition consists in 2 inputs
• The maximum size of the overall archive (over all segments)
• The size of a single segment
Segment: The individual are initially grouped to

form small units, namely the segments.
Overall archive: formed by all the single segments
more details.

PCS 7 System Course
Storage location
Short-term archive files (System archive) are always stored so that they are local to the
computer in the associated WinCC project.
To ensure complete documentation of archive data without any gap, you have to
configure backups for your archive data:

PCS 7 System Course
12.3.3 Tag logging (of process values)
Data transferred from SIMATIC Manager

Definition of archiving type for archive-relevant process values:
• "Archiving" and "Long-term archiving", specify whether the process value should also
be saved for the long term if a Central Archive Server (CAS) or Process Historian /
Information Server is used.
• In the process object view:
Select the
archive type
• In CFC:
I/O properties
Block properties
2 ways in CFC
 Please note that in the process object view you only have access to tags intended for
representation in the Process object view.

PCS 7 System Course
Preparing the OS for archiving

Activate the “Create/update archive tags” checkbox in OS properties to create a system
archive during the OS compilation containing all archive tags.
Required for creation

of a system archive
during OS compilation
Only relevant if CAS

or PH is available in
the Multiproject
Only relevant if
PH is available in
the Multiproject
• System archive in the Tag Logging Editor:

PCS 7 System Course
Archive configuration
Configuration of archive size and storage location has to be done similar to the steps of
Alarm logging configuration in the “Tag logging” editor.
In contrast to archive type “TagLogging Slow”, the configuration of “TagLogging Fast”
consists in an additional tab “Archive contents”.
Calculation of the memory requirements of all segments for a specified time period
requires knowing, how many archive values are saved per second on average.
 As a rule, no more than 200 single segments (for the TagLogging Fast/Slow and
AlarmLogging archive databases) may be generated in total.
 See [121] PCS 7 Compendium part a - Configuration Guidelines - 03_2009, 7.4.2 for
more details.

PCS 7 System Course
12.4 Configuration of WinCC Controls

12.4.1 Display of process value trends by the Online Trend Control
In order to process data in graphic form, WinCC uses Online TrendControl to offer the
option of displaying the data as a trend. The trend display can be configured as you
wish. It offers the option to display within one trend control multiple trend windows, to
which interdependent or independent axes can be assigned.
The trends can display currently incoming values and archived values.
You define by the Trend Control

configuration (tab „Toolbar“), which
1 2 3 5 7 9 buttons will be available in Runtime.
This figure shows only a presetting.
4 6 8 10
11
1) Online parameterization of the display 7) Start/Stop the update of the display

2) Navigation in the data records 8) Ruler
3) Define a zoom area 9) Define statistics area
4) Move trend area 10) Calculate Statistics
5) Move axes area 11) Connection status
6) Original view
more details.
As of PCS 7 V7.1, the functionality of the WinCC OnlineTrendControl has been

expanded and the design has been changed.
The design of the WinCC OnlineTrendControl shown in the process picture is
dependent on the template that was chosen when the trend group was created.
• prior V7.1 (classic WinCC Online Trend): @TRG_Default.pdl
• from V7.1: @TRG_Standard.pdl
Both versions of the WinCC OnlineTrendControl can be used in PCS 7 as of version
7.1.

PCS 7 System Course
Access to the trend system in process mode
Standard case You open preconfigured trend groups using buttons in process
pictures. You can analyze the trends and also manipulate the
trend fields using specified functions.
Creating or loading You open a "Trends Online" dialog box on the working range.
trend groups in
process mode
Load/configure
trend groups
General procedure for configuration of the WinCC Online Trend Control

You configure the Online Trend Control in the Graphics Designer. Because the
elements time axis / value axis, trend, trend window the following general procedure is
recommended:
Create new trend window
Create new time axis / value axis

and assign them to trend window
Create new trend
Assign trend to trend window

and assign axes

PCS 7 System Course
Creating a new Online Trend Control
After you placed the object,

the "WinCC OnlineTrendControl Properties” dialog box opens.
One Trend window is already created as default.
Specify for each trend

Create more trend window, how much of
windows (if needed) the trend control will be
and rename them. taken up by it.
Example:
Proportional area: 2
Proportional area: 1
Trend Control area
If you create more than one trend windows in a Trend Control, then the property
„Proportional area“ allows to specify for each trend window how much of the trend
control will be taken up by it. It is a relational factor.
Example:
Trend window 1: Proportional area = 2
Trend window 2: Proportional area = 1
Result: The trend window 2 takes up twice as much space as the first trend window.

PCS 7 System Course
Each trend window needs for display of trends at minimum one time and one value axis.
Assign here the

trend window
Label visible
in Runtime
Trend windows contain the trends which are created separately in the tab „Trends“.
Assign the
trend window
Assign the
trend window
List of available
trends
Select the tag to

be connected
Graphical design
specifications

PCS 7 System Course
The trend specification consists especially in the configuration of the data connection.
You can choose between online tags and archive tags:
• 1 - Archive tags: This allows you to visualize tags written to the archive you created in
the "Tag Logging" editor.
• 2 - Online process tags: These are used to directly visualize measured values of the
process. This measured value is displayed to the operator as long as the Online
Trend Control is displayed in the process control. The measured value that is
displayed is not saved in the archive.
Tags from the archive and tags from the process can be displayed in a single Online
Trend Control.
Automatic value range
e.g. limits which have already

been defined in the block
instance in the CFC chart)
more details about automatic transfer of properties for the value axis.

PCS 7 System Course
Data export
Values displayed in a Trend Control can be exported into a .csv file.
Enable the
Export button
for the process mode
Enable here more

operating options for
the data export
 If you export only a selection of the available data you have to select the range via
the rulers of the statistic function.
Online configuration of the OnlineTrendControl

You can change the configuration of the WinCC OnlineTrendControl during the process
mode. Already in the offline configuration was specified, how to proceed with online
configuration changes in case of a picture change or after closing the OS Runtime.
Enable the following Toolbar button functions for the online configuration of the Trend
Control:
• Toolbar button function "Configuration dialog"
• Toolbar button function "Select data connection"
• Toolbar button function "Select trends"
• Toolbar button function "Select time range"
 Enable the Help button of the Trend Control to provide support for online
operation/configuration in Runtime.

PCS 7 System Course
Connection to the Ruler Control

Evaluated data and statistics are shown in a table in a ruler window, statistics window or
a statistics area window. These windows are configured in the WinCC RulerControl.
Moveable
ruler
Online
Trend
Control
Data Online
source Ruler
Control
i: measured
g: interpolated
Data source object

(Trend Control)

PCS 7 System Course
12.4.2 Display of customized alarm lists in the process picture

You can configure a customized alarm window in a process picture using the
WinCC Alarm Control available from PCS 7 V7.1.
• View messages without having to toggle to the message list in process mode.
• Choose what types of messages are displayed.
• Specify the information to be provided in the individual message blocks.
• Specify the exact contents of the message line.
1 3 5 7 9 11 12 13
2 4 6 8 10 14
15
You define by the Alarm Control configuration (tab „Toolbar“), which buttons will be available in
Runtime. This figure shows only a presetting.
1) Online parameterization of the display 9) Lock dialog

2) Message list 10) Data export
3) Short-term archive list 11) Autoscroll
4) Long-term archive list 12) Page navigation
5) Lock list 13) Time base dialog
6) Hit list 14) Copy rows
7) Emergency acknowledgement 15) Data connection status
8) Selection dialog
How to insert an WinCC Alarm Control
After you placed the object,

the "WinCC AlarmControl Properties” dialog box opens.
One Alarm window is already created with default setttings.
more details.

PCS 7 System Course
Properties of the Alarm Control

• General Layout of the alarm window:
Layout of the
alarm window Selection of
the desired
alarm list
• Layout of the alarm list:
Layout of the Select message

message blocks blocks for the list
The message blocks are created during the OS compilation.

PCS 7 System Course
• Layout of tool bar and status bar:
 See WinCC Information System for more details.

> Working with WinCC > Setting up a Message System > Display of Messages during
Runtime
Message Selection
The options available in the alarm control for the selection of messages are “Fixed
selection” and “Selections”. Both selection modes can be combined.
Userdefined Always used

in runtime
Result:

PCS 7 System Course
• Fixed selection
The fixed selection is permanently configured directly in the control, and is always
used in runtime. In addition to the fixed selection, various user-defined selections can
be configured.
• User-defined message selection
They can be enabled and disabled during runtime in the “Selections” dialog. The
selection criteria are saved for reuse: That is user defined message selections are
common WinCC project wide.
The selection dialogs created are not user specific but can be selected and
modified by all users.
The configured user-defined selections are only used in runtime if that selection is
enabled. It is possible to enable multiple user-defined selections simultaneously in
order to achieve a more precise, graduated selection.
The selection criteria created can also be made available on other clients by
configuring the standard server for SSM on one client.
It has to be considered that selection criteria which have been created on the
Engineering Station and which are transferred via a complete download to the OS
Station, will replace the existing criteria on the OS Station.
Data export
The system normally exports the data which are selected for display in the control. In
addition, the scope of data export can be defined in the “Export Data” dialog. The
options available are to export “All” or the “Selection”.
Enable the
Export
Copy selected
button
rows to clipboard
The “Copy rows” button allows to copy one or more selected rows of messages from the
control to the clipboard and then to paste them e.g. to an Excel table. The “Copy rows”
button can be enabled and disabled for selection in the “Toolbar” tab of the Control
Properties dialog.

PCS 7 System Course
Configuration options to change the behavior

• Changes of the acknowledgement behavior when the auto scroll function is disabled
The new version includes a change of the acknowledgement behavior when the auto
scroll function within the alarm control is disabled.
− Prior to V7.1: A group acknowledgement acknowledged all visible messages.
− From V7.1 on: A group acknowledgement acknowledges the selected
messages.
• Flashing message: When a message is shown flashing, the text displayed can still be
read.
• Behavior on double-click: The attribute “Action on double-click” in the “General” tab
defines the response to a double-click. The following options are available:
− None
− Loop in Alarm
− Open comments dialog
− Open Info Text dialog
− Column dependent
• Show message colors: The attribute “Show message colors” in the “General” tab of
the Properties dialog allows enabling (default setting in PCS 7) or disabling the
display of the message colors. When it is disabled, the message text is shown in
black font on white background.
Task: Archiving of the material tank levels
Goal
A Trend of the material tanks, to be accessed by a button in the Reactors picture
Checkpoint

• What is a usual storage-duration
for events, alarm and tags on an
OS server?

PCS 7 System course
Content 13
13 Locking functions and operating modes ..............................................................3
13.1 Learning target....................................................................................................................... 3
13.2 Interlock ................................................................................................................................. 3
13.2.1 Overview of the locking functions .......................................................................................... 3
13.2.2 Locking logic .......................................................................................................................... 5
13.2.3 The interlock blocks ............................................................................................................... 6
13.2.4 The interlock faceplate........................................................................................................... 7
13.2.5 Bypassing interlocks .............................................................................................................. 9
13.2.6 Interpretation of the status displays..................................................................................... 10
13.2.7 Evaluation of the signal status "Simulation" in the technological block ............................... 14
13.3 Local/Remote control and other operating modes............................................................... 16
13.3.1 Overview of the operating modes of APL ............................................................................ 16
13.3.2 Status diagram for the operating modes of APL.................................................................. 17
13.3.3 Operating mode "On"........................................................................................................... 18
13.3.4 Operating mode "Out of service" ......................................................................................... 18
13.3.5 Operating mode "Manual" and "Automatic"......................................................................... 19
13.3.6 Operating mode "Program mode" for controllers................................................................. 20
13.3.7 Operating mode "Local"....................................................................................................... 21
13.3.8 LocalSetting = 0 ................................................................................................................... 22
13.3.9 LocalSetting = 1 ................................................................................................................... 22
13.3.10 LocalSetting = 2 ................................................................................................................... 23
13.3.11 LocalSetting = 3 ................................................................................................................... 24
13.3.12 LocalSetting = 4 ................................................................................................................... 25
13.3.13 Deactivating interlocks......................................................................................................... 25
13.3.14 Forcing operating states ...................................................................................................... 26
13.3.15 Rapid stop for motors .......................................................................................................... 27
13.3.16 Priorities of operating modes and control functions............................................................. 28
SIMATIC PCS 7 – Locking functions and operating modes

PCS 7 System course

PCS 7 System course
13 Locking functions and operating modes

13.1 Learning target

• Interlock functions as opportunity to
avoid undesired control functions as the
start of motors or opening of valves
• Local operation mode for drives

• configure the locking of valves
• configure the local operation mode
for a motor
13.2 Interlock
13.2.1 Overview of the locking functions
"0" means: Lock active

"1" means: Lock not active,
everything OK
Permission:
Activation (On) enable
Interlock:
Interlock without reset
Protection:
Interlock with reset
For locking drives (e.g.: “MotL” = motor control) there are three connections for the
corresponding blocks:
• "Permit" Switch on enable (enable),
• "Protect" Locking with reset (protection),
• "Intlock" Locking without reset (lock),

PCS 7 System course
Locking type "Intlock"

The "Intlock" corresponds to the concept “lock” in the PCS 7 Standard Library. An active
interlock condition brings the block to the safe position (input Intlock = 0). After the
interlock condition has gone, the currently active control function becomes active again
in automatic or local mode. In manual mode the faceplate can be operated again after
the interlock condition has gone.
Locking types "Permit", "Protect"

These represent a new concept with two separate signals for enabling the “activation”
(leaving the safe position) and the forced “switch-off” (taking the safe position) for
drives.
• Permit
The activation enable (input Permit = 1) makes it possible to leave the safe position of
the block in response to operator input or a command from the program (CFC/SFC).
The activation enable signal has no effect if the block is not in the safe position.
• Protect
An active interlock condition brings the block to the safe position (input Protect = 0).
After the interlock conditions are cleared, the operator or an activation sequence must
reset the control functions again to match the input parameters (only in automatic mode)
Reset behavior of a block

Via the feature parameter: “Resetting the interlock via input signals”
(Feature Bit 9) you can define the reset behavior of the block:
• Feature bit 9 = 0
Reset is carried out either by operation in the faceplate, or using the interconnectable
input parameter (RstLi = 1) at the block.
• Feature bit 9 = 1
It is also possible to reset with a 0-1 edge change in the control signal in automatic
mode.
 The function “Resetting the interlock via input signals” can only be
used in case of a feedback error or an interlock of the type "Protect".

PCS 7 System course
13.2.2 Locking logic
The interlocking logic in the PCS7 APL is as follows:

A logic “0” means that the Interlock (e.g. “Permit“, “Protect” or “Intlock“) is active (i.e.
fail safe).
A logic “1” means that the Interlock is not active and everything OK is (Good state).
 ATTENTION!
The interlocking logic in the PCS7 standard library is the exact opposite:
A logic “0” means that the Interlock is not active and everything OK is (Good
state).
A logic “1” means that the Interlock is active (i.e. fail safe).

PCS 7 System course
13.2.3 The interlock blocks

This block makes it possible to create a user-configured, static binary logic (AND, OR,
NEGATION). The output parameters of the Interlock block can be interconnected with
the locking input parameters of the drive blocks ("Permit", "Protect", "Intlock").
1
2
3
4
5
6
7
1. InXX: locking input

2. InvInXX: "1" inversion of InXX
3. BypInXX: "1" bypasses InXX
4. AVXX: Analog value for InXX
5. AVXX_Uni: Unit for AVXX
6. Enable First active input
7. "Feature" parameter; Bit 31 : First out detection
The Intlkxx block is available in 4 versions, i.e. with 2, 4, 8 or 16 binary inputs. Each of
these inputs can be inverted. This is controlled by an associated input (e.g. "InvIn01")
for each binary input (e.g. "In01").
Each connection can be bypassed, if desired, from the logic (e.g. "BypIn01").
 Bypassing means that the signal is excluded from the logic. If all input parameters are
bypassed the output value is defined via the “DefaultOut” parameter.
AND or OR operation can be selected.

Interconnecting two Intlk04 and one Intlk02 is equivalent to the interlock block in the
PCS 7 Standard Library. The different sized Intlkxx blocks of the PCS 7 APL provide
more flexibility.
Monitoring analog values

For locking signals coming from an analog value monitoring block (e.g. MonAnL), it is
possible to display the analog value as well as additional texts in the interlock faceplate.
By interconnecting the input AVxx (e.g. AV02, see Figure above) the analog value is
displayed in the faceplate. The label text is configured in the properties of the respective
block I/O. There are separate parameters for the units of measure (e.g. AV02_Unit).

PCS 7 System course
13.2.4 The interlock faceplate
3
7 2
1
4
5 6
1. Open faceplate of locked object

2. First out detection: only if Feature Bit 31 = “1” and Enable First input active = “1”
3. Logic operator
4. Label text of AVXX
5. Value of AVXX
6. Unit of AVXX
7. Open faceplate of locking object
Views are only displayed in the faceplate for the respective drive if the appropriate
parameters are interconnected or have a value not equal to “FF” in the Signal Status.
In the example above the Intlock input of the motor is connected with an interlock
block. The "Intlock" lock is active (lock closed). The drive can't be started by the
operator (select “Command = Start”).
Colors in the interlock block, priorities

In the faceplate of the Interlock block the logic operation icon (AND, OR) is represented
with a variable background color. In the block icon one field is respectively displayed
with the same color.
The following prioritization applies (1 = highest priority)
Priority Color Description

1 Gray The Interlock block is set to “Not Used”. Parameter NotUsed = 1
2 Blue At least one signal of the Interlock block is bypassed and no request for color
gray.
3 Yellow The output of the Interlock block has the signal status 16#60 (Simulation, yellow
hand) and no request for color gray or blue.
4 Red The output of the Interlock block has the signal value FALSE and no request for
color gray, blue or yellow
5 Green The output of the Interlock block has the signal status TRUE and no request for
color gray, blue or yellow

PCS 7 System course
 ATTENTION!
“NotUsed” is now used to change the color to gray. All other functions of the Interlock
block are not affected by this. This is meant to indicate to the user that this interlock
has currently no effect on the drive.
One possible application could be the interconnection of the “Motor runs” feedback
from the drive block to the NotUsed of the Interlock block which controls the enable.
If the motor runs the enable has no further meaning.
“Interconnected” faceplates can be called via the arrow keys in the Interlock faceplate.
For example, the faceplate of the MonAnL block which is interconnected with the
Interlock or the faceplate for “evaluating” MotL blocks.
Evaluation of first relevant signal

The PCS 7 APL Intlkxx block has First out detection:
At the "FirstIn" output the bit-coded number of the input, which caused the last signal
change of the output from 1 to 0 (Good state to Safe State), is displayed. The value of
this output is 2(N-1), where N equals the input number.
E.g. first out from input In03 means that FirstIn = 16#4 (2(3-1)).
You activate this function via the Bit31 feature "Evaluate first relevant
signal" and the input FirstInEn (see also Faceplate and Online-help on the block).

PCS 7 System course
13.2.5 Bypassing interlocks
Open bypass
operation
Open interlock
Valve is faceplate
locked
Result: valve is
Input is bypassed unlocked
Bypassing process signals

To force values for the interlock there are 3 possible procedures:
• Simulation of the process signal at the driver (connection "SimOn" = 1)
• Bypassing the Interlock (bypass, see faceplate)
• “Forcing”
The following is displayed in addition to the buttons:
• Interlock status:
If the locking signals are bypassed, the interlock status changes to unlocked.
• Signal Status:
If one of the interlock signals is bypassed, the signal status of the interlock block
changes to "Simulation".
• Bypass information:
If one of the interlock signals is bypassed, the signal status of the interlock block
changes to "Simulation" and the symbol for the bypass is shown instead of a signal
status.
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 6.9.8.2 VlvL standard
view and 7.1.3 Intlk02 functions for more details

PCS 7 System course
13.2.6 Interpretation of the status displays

The logic built with the Interlock blocks generates an output signal (Out) which tells the
drive block whether an interlock is active. This information is displayed for the operator
in the technological faceplate by the "padlock" symbol.
All the effective interlock states are combined and displayed in the block icon. The
interlock states are displayed with the following prioritization:
1. Function interlocked, shown in the block icon with a closed padlock
2. Function not interlocked, shown in the block icon as an open padlock
3. Function disabled, shown in the block icon as a crossed-out, closed padlock
Furthermore the Signal Status of the respective process signals is displayed in the
Interlock block and passed on to the technological block according to priority.
The block determines the signal status of the output signal, based on the signal status
of the input values from the configured logic operation according to the following table
(highest priority is 0):
Signal status - Icon Priority Value Meaning

0 16#00 Bad, device related
1 16#28 Bad, process related
2 16#60 Local functional check / simulation
3 16#68 Uncertain, device related
4 16#78 Uncertain, process related
5 16#A4 Maintenance request
No icon 6 16#80 Good

No icon - 16#FF Input is not interconnected.

PCS 7 System course
General rules
• The best/worst signal status is generated according to the priority table for
technological blocks.
• The signal status of the output is generated from the best (lowest priority) or worst
(highest priority) signal status of those input signals (highest priority is 0), which are
interconnected and not excluded (relevant input signals) in accordance with the logic
operation and its result.
• If all inputs are excluded or not interconnected, the signal status of the output is set to
simulation 16#60).
Logical AND operation

• If the output value is 1, it has the signal status with the highest priority of all interconnected input signals.
• If the output value is 0, it has the signal status with the lowest priority of all interconnected input signals,
which have a value of 0.
• If the output value is 1 and at least one input is bypassed, the signal status of the output is set to
simulation at best (16#60).
Logical OR operation
• If the output value is 1, it has the signal status with the lowest priority of all interconnected input signals,
which have a value of 1.
• If the output value is 0, it has the signal status with the highest priority of all interconnected input signals.
• If the output value is 0 and at least one input is excluded, the signal status of the output is set to
simulation at best (16#60).
Feature Bit 23
If the Interlock block passes on the Signal Status 16#28 (bad, process-specific, red
factory) or 16#00 (bad, device-specific, red wrench), the interlock will be evaluated as
bad in any case (padlock closed, interlock effective).
You can use the Feature bit 23 (Evaluation of signal status) to specify if the signal
status of the inputs is to be checked for the values 16#00 or 16#28. The signal status of
the inputs itself remains unchanged here.
The default setting is 0.
• Bit = 0: No evaluation of the signal status. The status display within the interlock
block is always shown as "0".
• Bit = 1: the signal status is determined, an input with ST = 16#00 or 16#28 is
forwarded with value = 0. The "Negate signal" function at the input of the block has
no influence on the reaction in this case.

PCS 7 System course
Logical AND operation ( Logic = 1 )

• If the output value is 1, it has the worst signal status (highest priority) of all relevant
input signals.
Example:
ST = 16#00
ST = 16#28
Worst signal state of all

relevant input signals
AND gate with

output value 1
ST = 16#00
Interlock active, despite

fulfilled condition
• If the output value is 0, it has the best signal status (lowest priority) of the relevant
input signals with a value of 0.
Example:
ST = 16#00
ST = 16#28
Best signal state of all

with value = 0
AND gate with
output value 0
ST = 16#28
• If the output value is 1 and at least one input is excluded (bypassed), the signal
status of the output is set to simulation (16#60).

PCS 7 System course
Logical OR operation ( Logic = 0 )

• If the output value is 1, it has the best signal status (lowest priority) of the relevant
input signals with a value of 1.
Example:
ST = 16#00
ST = 16#28
Best signal state of all

with value = 1
OR gate with
output value 1
ST = 16#28
Interlock active, despite

fulfilled condition
• If the output value is 0, it has the worst signal status (highest priority) of all relevant
input signals.
Example:
ST = 16#00
ST = 16#28
Worst signal state of all relevant

input signals
OR gate with
output value 0
ST = 16#00
• If the output value is 0 and at least one input is excluded, the signal status of the
output is set to simulation (16#60).

PCS 7 System course
13.2.7 Evaluation of the signal status "Simulation" in the technological block
Simulated signal with output value = 1

Output signal has status "Simulated" and
interlock condition fulfilled
Interlock condition is
regarded as a
bypassed signal
If the interlock signal has the status 16#60 ("Simulation") and the interlock condition is
fulfilled (e.g. Intlock = 1), the interlock is regarded as bypassed and displayed with
the icons for “bypassed” – in the faceplate.
Simulated signal with output value = 0
Output signal has status "Simulated" and

interlock condition not fulfilled
Interlock condition is
regarded as a
simulated signal
If the interlock signal has the status 16#60 ("Simulation") and the interlock condition is
not fulfilled (e.g. Intlock = 0), the interlock is regarded as simulated and displayed
with the icons for "simulated” – in the faceplate.

PCS 7 System course
 If the Interlock block is interconnected with a driver block and the Interlock block
displays a yellow hand as the signal status, this will not necessarily indicate a
simulation. If the process value is faulty at the channel driver and a substitute value
was parameterized, the driver will also pass on the signal status simulation to the
interlock block and the symbol will be displayed in the OS.
Task: Interlock for the dose valves
Goal
Preventing to have more than one dose valves opened
Checkpoint
Think about the interlocks in

your project…
• Make a list of all usefull interlocks
affecting the valves of the D210 and
R310 and the stirring motor.

PCS 7 System course
13.3 Local/Remote control and other operating modes

13.3.1 Overview of the operating modes of APL
The operating modes are mainly assigned to the block families (drives, channel,
convert, etc). Three categories are distinguished below:
1. Motors, valves and dosage feeders
2. Controls
3. Blocks without “manual” and “automatic mode” (e.g. MonAnL)
Basically the operating modes can be set directly by the operator in the faceplate. In
order to select a particular operating mode the respective conditions must also be
fulfilled (e.g. operator authorization, etc).
Motors, valves, and dosing units

Local operation
Automatic mode
Manual mode
Out of service
Controller
Automatic mode
Manual mode
Program operation
Out of service
Blocks without manual or automatic mode

On
Out of service

PCS 7 System course
13.3.2 Status diagram for the operating modes of APL
Used for Used for

controllers only motors, valves,
and dosing
units
Number in Condition for status change

graphic (top)
1 Manual (on)  Out of service
• Via faceplate ("OosOp" = 1) if "ModLiOp" = 0 or
• Via edge transition 0 → 1 of "OosLi" if "Feature" bit "Reaction to
the out of service mode" = 1
2 Out of service  Manual (on)
• Via faceplate ("ManModOp" = 1)
3 Local mode  Manual
• Via faceplate ("ManModOp" = 1) if "ModLiOp" = 0 and
"LocalSetting" = 3 or "LocalSetting" = 4 or
• Via "LocalLi" = 0 if "LocalSetting" = 1 or "LocalSetting" = 2
4 Automatic  Manual
• Via faceplate ("ManModOp" = 1) if "ModLiOp" = 0 or
• Via "ManModLi" = 1 if "ModLiOp" = 1 and "Feature" bit "Setting
switch or button mode" = 0 or
• Via "AutModLi" = 0 if "ModLiOp" = 1 and "Feature" bit "Setting
switch or button mode" = 1
5 Manual  Automatic
• Via faceplate ("AutModOp" = 1) if "ModLiOp" = 0 or
• Via "AutModLi" = 1 if "ModLiOp" = 1
6 Manual  Local mode
• Via faceplate ("LocalOp" = 1)
if "ModLiOp" = 0 and "LocalSetting" = 3 or "LocalSetting" = 4 or

PCS 7 System course
Number in Condition for status change

graphic (top)
7 Automatic  Local mode
• Via faceplate ("LocalOp" = 1) if "ModLiOp" = 0 and "LocalSetting"
= 3 or "LocalSetting" = 4 or
8 Local mode  Automatic
• Via faceplate ("AutModOp" = 1) if "ModLiOp" = 0 and
"LocalSetting" = 3 or "LocalSetting" = 4 or
• Via "LocalLi" = 0 if "LocalSetting" = 1 or "LocalSetting" = 2.
9 Program mode  Automatic
• Via faceplate ("AutModOp" = 1) if "ModLiOp" = 0 or
• Via "AutModLi" = 1 if "ModLiOp" = 1 or
• Via edge transition 1 → 0 of "AdvCoMstrOn" if automatic is set
before program mode.
10 Automatic  Program mode
Requirement for changeover in program mode: "AdvCoEn" = 1
• Via faceplate ("AdvCoOn" = 1) if "ModLiOp" = 0 or
• Via "AdvCoMstrOn" = 1
11 Manual  Program mode
Requirement for changeover from manual to program mode:
"AdvCoEn" = 1 and "AdvCoModSP" = 0
• Via faceplate ("AdvCoOn" = 1) if "ModLiOp" = 0 or
• Via "AdvCoMstrOn" = 1
12 Program mode  Manual
• Via faceplate ("ManModOp" = 1) if "ModLiOp" = 0 or
• Edge transition 1 → 0 of "AdvCoMstrOn" if manual is set before
program mode.
13.3.3 Operating mode "On"

The “On” mode signals that the block algorithm is being processed (output parameter
OnAct = 1). This mode is available for simple blocks which have faceplates but not the
“Manual mode” or “Automatic mode” or “Local mode”.
The operating mode “On” can only be activated via operation at the faceplate (input
parameter OnOp = 1). A requirement for this is that the block is in “Out of service” mode.
13.3.4 Operating mode "Out of service"

The “Out of service” mode is intended for maintenance and servicing purposes, for
example, to exchange a device. All messages and functions of the block are
suppressed or switched off and for motors and valves, for example, all outputs are
controlled to the safety position.
The “Out of service” is available for all blocks with a mode switchover and a direct
connection to the process (e.g. with a connection to a measuring point).
A requirement for the switchover to this mode is that the block is in “Manual” or “On”
mode. When leaving the “Out of service” mode via operation at the faceplate it can only
be switched to “On” or “Manual” mode.

PCS 7 System course
13.3.5 Operating mode "Manual" and "Automatic"

In "Manual mode" the device is controlled manually by the operator. The operator
decides how the manipulated variable (output signal) for the block is changed. The
manipulated variable can be analog or binary.
In "Automatic mode" the motors, valves and dosage feeders must be controlled by the
block algorithm via inputs which are interconnected or controlled by the SFC.
In "Automatic mode" the output signal of the control is automatically calculated by the
block algorithm.
Selection of manual/automatic operating mode with…
ModLiOp = 0 ModLiOp = 1
…Faceplate (or SFC) …CFC / SFC

Au 1
tM
od i = 0)
od Li =
Op L
=1 nM
Ma t Mod
(Au AutModLi = 1
ManModOp = 1
(ManModLi = 0)
Manual mode Automatic mode
• Switchover initiated in the faceplate (ModLiOp = 0):

The changeover between operating modes is carried out in the standard view of the
faceplate. In the function block, the parameters ManModOp for "manual mode" and
AutModOp for "automatic mode" are used.
If both signals (ManModOp =1, AutModOp = 1 ) are set, then ManModOp = 1 has priority.
• Switchover per interconnection (CFC or SFC instance) (ModLiOp = 1):
The switchover between the operating modes is carried out with an interconnection on
the function block. The parameters ManModLi for "manual mode" and AutModLi for
"automatic mode" are used in pushbutton operation.
In switch mode (requirement: Feature Bit 4 = 1) connection AutModLi is used
exclusively.
If both signals (ManModLi =1, AutModLi = 1 ) are set, then ManModLi = 1 has priority.
Changing the switchover behavior using Feature Bits

Using Feature Bits you can change specific properties of the switchover behavior:
• Enabling bumpless changeover to automatic mode for valves, motors, and dosing
feeders (Feature bit 17)
• Disabling bumpless changeover to automatic mode for controllers (Feature bit 18)
• Resetting the commands for changing the mode (Feature bit 2)

PCS 7 System course
13.3.6 Operating mode "Program mode" for controllers

For supervisory control functions which run on an external PC, (such as an OPC client
connecting an external Advanced Control Software package) provides the option to take
on the control of the control function block and to specify the setpoint value or the
manipulated variable from outside. This mode of operation is referred to as program
mode.
The program mode requires an enable signal (input parameter AdvCoEn = 1) from a
central control block. If this enable signal falls back from 1 to 0, for example due to
failures of the OPC communication, the controller block goes back to the mode it had
before being put into program mode.
Activate program mode in the standard view in the faceplate. Apart from the switchover
between manual and automatic mode, the program mode is provided to you as an
additional mode. Program mode is exited when either manual or automatic mode is
selected via operation from faceplate or via an interconnection/SFC.
A 0>1 edge change of the interconnectable input parameter AdvCoMstrOn the program
mode is activated depending on the conditions mentioned below. You can use this to
set an entire group of controller blocks simultaneously in program mode from a central
control block. The operable input parameter AdvCoOn as well as the interconnectable
input parameter AdvCoMstrOn can be used parallel, since the input parameter
AdvCoMstrOn only reacts to edges of the binary signal.
For a 1>0 edge change the program mode is deactivated again.
The output parameter AdvCoRdy = 1 indicates that the PID control is ready to change to
program mode. At a central control block you can use an AND operation of all
AdvCoRdy signals of the associated controls to enable a central switchover.
Output parameter AdvCoAct = 1 indicates, that the block is in program mode.

PCS 7 System course
13.3.7 Operating mode "Local"

This operating mode is used for motors, valves and dosage feeders. Control occurs
directly or via a “local” control station. Additionally, various behaviors can be set via the
LocalSetting parameter. Operating the block in the OS is not possible.
LocalOp/ LocalLi = 1 LocalOp = 1

LocalLi
Local setting 0 1 2 3 4
No Local Local Switchover Switchover

switchover switchover switchover via faceplate via faceplate
possible with control with control with control with control
via DI directly via via DI directly via
connected to the motor connected to the motor
the CFC control the CFC control
block block
Changing to local mode

Changing to local mode is only possible from the manual and automatic operating
modes. The change to this mode is initiated by:
• An operation on the faceplate (input parameter LocalOp = 1,
valid if LocalSetting = 3 or LocalSetting = 4 and ModLiOp = 0) or
• The interconnected input parameter (LocalLi = 1, valid if LocalSetting = 1 or
LocalSetting = 2).
Exiting local mode

You leave local mode using:
• An operation on the faceplate (LocalSetting = 3 or LocalSetting = 4 and
ModLiOp = 0) or
• The interconnected input parameter (LocalSetting = 1 or LocalSetting = 2).
• In order to exit local mode via the interconnected input parameter, you can configure
various reactions using Feature bit 10 (Exiting local mode).
 See [113] PCS 7 V8.0 Advanced Process Library - 12_2011, 1.1.10 for a description
of these „Feature“-Bits. Also check the online help.

PCS 7 System course
13.3.8 LocalSetting = 0
If the parameter LocalSetting has a 0 at the input, a changeover to Local mode is

not possible. Via the faceplate the motor can only be switched on and off in “Manual” or
“Automatic” mode.
Remote 0
Local 1 No operation
Off
On
No switchover
Motor control
For LocalSetting = 1 the control signals are from the field (remote, off, on) via
channel blocks to interconnectable parameters of the motor block.
The motor block forwards the start signal via channel blocks to the MCC (Motor-Control-
Center) which switches the motor on.
The feedback of the running motor is forwarded from the MCC at the motor block via the
interconnectable parameter FbkRun.
In Local mode, no operation is possible from the faceplate. Switching to other modes is
also not possible.

PCS 7 System course
Remote 0
No operation
Local 1
Off No switchover
Motor control
On
In this case the Local switch is directly connected with the MCC which can directly
switch the motor on or off.
The motor block is controlled via a tracking of the feedback message. The control of the
input signals StartLocal and StopLocal is ineffective in this case. Switching over
into another mode is not possible here, since it is switched over via LocalLi. I.e. the
Local mode is controlled from the field.
The output parameter LocalAct, which is connected to the MCC via a channel driver
Pcs7DiOu, sees to it that switching on and off locally is also only possible in Local
mode.

PCS 7 System course
No operation
Off
On
Motor control
In case of LocalSetting = 3 the control signals are coming from the field level
(on/off). This setting works as in LocalSetting = 1.
The difference is that the Local mode is selected via the faceplate.

PCS 7 System course
No operation
Off
Motor control
On
In case of LocalSetting = 4 the control signals are from the field (on/off).
This setting case works as in LocalSetting = 2. The difference is that the Local mode
is selected via the faceplate.
The output parameter LocalAct, which is connected to the MCC via a channel driver
Pcs7DiOu, sees to it that switching on and off locally is also only possible in Local
mode.
13.3.13 Deactivating interlocks
Via the input parameter BypProt (bypass protection) it can be specified whether
interlocks are taken into account in Local mode or not. This functionality applies for all
LocalSettings in Local mode. A “0” at the input means that interlocks are taken into
account in Local mode and a value “1” means that the interlock has no effect.
The interlock is displayed as a lock next to the Protection button in the faceplate. A
crossed-out lock refers to an interlock which is not in effect (BypProt = 1).
In case the control signals go directly to the MCC, an interlock to the MCC can become
effective through the output parameter LockAct at the motor block.

PCS 7 System course
13.3.14 Forcing operating states

The forcing of operating states function lets you set the function block into a different
operating state using interconnectable input parameters, regardless of the currently
active control. This can, for example, be:
• Forces tracking for closed-loop controllers and control values
• Enabling and disabling at motors
• Opening and closing of valves
Forcing of operating states is only possible in the manual and automatic modes. Forcing
operating states has the highest priority over both operating modes.
The input parameter xxxxForce = 1 (for example OpenForce and CloseForce at a

valve) is used for forced controlling of the function block and thus an intervention in the
function of the block, irrespective of currently active controls, interlock conditions and
monitoring errors. If the input parameters are inconsistent (for example OpenForce =
1 and CloseForce = 1 at valves), an error number is output at the parameter
ErrorNum and the control remains unchanged.
Display in the block icon and the faceplate

A forced operating state is indicated in the block icon and in the standard view of the
faceplate:
Block icon A forced operating state is shown in the block icon for motors,
valves and dose blocks by means of a red F and a crossed out
padlock.
There is no indication for controller blocks.
Faceplate In the standard view of the faceplate, an information text on the

forced operating state is displayed (e.g. "Forced open" in case
of a valve). In addition this is shown with a crossed out
padlock.

PCS 7 System course
13.3.15 Rapid stop for motors
Activated with
feature bit 14
Rapid stop has the highest priority in all operating modes (manual and automatic mode
as well as local mode) and operating states (such as the forcing of states). It is activated
via the faceplate. This depends on the setting at the Feature bit 14 (Enabling rapid
stop via faceplate).
You issue the command for rapid stop state using the RapidStp = 1 input parameter.
When you click on the "Rapid Stop" button in the faceplate, the drive stops immediately,
shown as follows in the faceplate:
The R_StpAct = 1 output parameter is set to implement the rapid stop function for
local mode. You need to interconnect this parameter to the corresponding driver block
and in the I/O to realize the rapid stop function in the hardware.
Rapid stop is unlocked for all operating modes with the "Reset" button in the faceplate
(ResetOp = 1); in CFC it is unlocked with the ResetLi = 1 input parameter.
Rapid stop can be selected even with the motor in stop state. In this case, the motor
start is prevented.

PCS 7 System course
13.3.16 Priorities of operating modes and control functions

To ensure that drives can assume a safe state with different modes and control
functions (Quick Stop/Forcing of operating states), the control commands or modes
must be assigned different priorities.
Thus a drive which is switched off, for example, by the operator at the local control must
not be switched on by an automatic mode command. The priorities for the modes and
functions of the motor are given in the following picture. The hand mode and the
automatic mode have the lowest priority here.
Out of Service
Rapid Stop Motor
BypProt = 0
Local mode LockAct
Priority
Localsetting = 2/4)
Forced operating
State
(Forcing)
Manual/Automatic always Active interlock
Operating modes Conditions/Parameterizing Functions/States
Task: Local operation of M316
Goal
Local operation of M316 using the Signal Box
Checkpoint
What is your opinion?

• Why does local operation mode has higher
priority than manual or automatic mode?

PCS 7 System Course
Content 14
14 Mass data engineering............................................................................................3
14.1 Learning target....................................................................................................................... 3
14.2 Chart Reference Data............................................................................................................ 3
14.3 The Import Export Assistant (IEA) ......................................................................................... 6
14.3.1 Process Tag Types: Overview of the procedures.................................................................. 7
14.3.2 Example: Level measurement for the reactor........................................................................ 8
14.3.4 Models ................................................................................................................................. 16
14.3.5 Tasks and Checkpoint ......................................................................................................... 16
14.4 New Type Model .................................................................................................................. 17
1.
SIMATIC PCS 7 – Mass data engineering

PCS 7 System Course
2.
3.
4.
5.
6.
7.
8.
9.
10.

PCS 7 System Course
14 Mass data engineering


• How PCS 7 supports an efficient bulk
engineering
• The new type concept of PCS 7 with
control modules and its types

• to configure Process Tag Types and Models
• to use the Import/Export Assistant (IEA) for
the generation of process tags and plant
hierarchy folders
• to use the chart cross reference for fast
navigation in an AS program
14.2 Chart Reference Data

Chart Reference Data tool supports you having overview of the AS program created
with CFC and SFC. Several “lists” and “tree structures” are offered with information
existing in all charts of a Charts folder. From there you can navigate tot the related
charts.
Opening can be done in two ways:
From CFCs toolbar
From the Charts folder

PCS 7 System Course
Different views
After opening you can select a view for one or more windows:
graphical representation of the entire Run Sequence
All global adresses and the chart elements using them
Adresses in CFC used by SFC
Connections between blocks in CFC
The appereance of SFC types I/Os in their stepsand transitions
What blockoutputs are controlling what Runtime Groups
All blocktypes and where they appear in the charts
Relation between elemets in charts and S7 resourcecs
All available OBs, with the calculated local data requierement,

what has been configured offline and what is available in the CPU
How blocks are related to each other ( multi instance )
Open textual interconnections
Several statistic data
All block I/Os for which forcing has been added
open a list of all AS-wide interconnections
Navigation
From several lists you can navigate to the related elements in the charts:

PCS 7 System Course
Application example: Forced Block I/Os

A total overview of all block inputs for which forcing has been added is available in the
chart reference data (“Forced Block I/O’s”. When selecting a specific line, you can jump
to the corresponding chart by double clicking on the line or via "Go to Point of Use".
The entries in the columns "Forcing active" and "Forcing value" have the following
meaning:
• "Active" = forcing is active for this I/O
• "Globally deactivated" = The function "Support forcing not set at the chart folder
• The column will remain empty if forcing is deactivated at this I/O.
Forcing is not activated

for these inputs
The function
"Support forcing” is not
set at the chart folder

PCS 7 System Course
14.3 The Import Export Assistant (IEA)
Prerequisite
A master data library is required to use the function of the IEA.
Principle
Create/Change = I/O point for parameters, signals and

Process Tag Type messages, to appear in the import file
Assign/Create File Template

Import File Tools: IEA editor
PTT
Notepad
Create File Template Copy,
Excel
Edit
…
PT
PT …
Import
Update PT
Import file
Export file
PT
Export PT
PT
When data has been changed in the Process Tags
Process tags are derived as a large number of individual instances from pre-defined
process tag types by use of the Import-Export assistant.
This tool allows to create and to edit a so-called import file. After edition (using IEA, or
any editor like Notepad, Excel), the re-import of the modified file results in automated
creation of a large numbers of process tags correctly placed in the plant hierarchy.

PCS 7 System Course
14.3.1 Process Tag Types: Overview of the procedures

Starting with an existing chart, you can create a Process Tag Type.
At the creation the chart will be copied to the Master Data Library, not affecting the chart
you used as a starting point.
From the chart, the desired I/O points (for parameters, signals and messages) have to
be selected to appear in the import file.
Only I/O points represented in the import file can be automated adjusted to the
instances, later derived from the process tag type.
Starting point is a Process Tag Located in chart folder.

(chart). The Process Tag has to be tested to avoid
multiplication of failures.
Create a Process Tag Type A wizard creates a Process Tag Type.

It is placed in the Master Data Library
(new folder ‘Process Tag Types’).
Create Importfile / File Template

The Importfile is a template in CSV format. Don’t
forget to save a backup before modification!
Modify Importfile Generate new process tag information by

multiplication and modification of rows in the
Importfile.
Import the modified Importfile

A wizard generates the new Process Tags (charts)
(create charts) following the information in the Importfile.

PCS 7 System Course
14.3.2 Example: Level measurement for the reactor
Starting point
Starting point is the existing chart Reactors\R310\LIA314.
Based on this one, new charts are to be created for the other 3 reactors.
After completing the procedure, level measurement for 4 reactors will exist.
They will differ from each other:
• Chart name and position in the plant hierarchy
• Signal from I/O
• Scaling of the signal
• Block comment
Creating the Process Tag Type

Based on the existing chart LIA314, we will create the Process Tag Type “LIA3x4”.
As I/O points we select:
The selecting as indicated above is not done in the opened chart, but as a part of the
creation procedure…

PCS 7 System Course

PCS 7 System Course
After the completion of this creation procedure, the Process Tag Type will be present in
the Master Data Library:
Import File
Next step is the creation of the Import File.
It will be based on a copy of the Template File, which can be created during this
procedure.
Starting point is the Process Tag Type LIA3x4 in the Master Data Library.

PCS 7 System Course
The column title for every I/O point can be edited.

After clicking on the button “Create File Template…” you can have generated a template
file that fits exactly to the Process Tag Type.
The file will have a default name based on the Process Tag Type name. The default
storage location is the Global folder of the library storage path.
After clicking on OK a dialog window will be displayed to allow you to specify details for
the layout of the column groups.
In the next screen copies you will find the default setting, but marked with circles, which
is actually being used in this demo.
After clicking on OK, the File Template will be created, and will be set as the current
Import File.

PCS 7 System Course
Because of the matching column title in the import file and process tag type, the
assignment between the I/O points in the import file and process tag type is made
automatically:
It is recommended to copy the template file

and continue with the copy.
Example: LIA3x400_First_Run
The resulting template file:
Benefit of the creation of a template file is that the table contains 1 filled up line
representing the data of the original chart the process tag type is based on.

PCS 7 System Course
The table now is to be edited with data representing the new charts you want to
generate (Process Tags):
I/O names for

1 row = 1 process tag
the new charts
R330 and R340 have a larger

content and therefore higher alarm
Settings for AS limites
import* assignment
New hierarchy New charts

folders
* To get this column displayed: insert it by

Edit > Insert Column Group > General > Import Mode
Import
The import procedure will make as many new copies of the chart, and to every copy
changes will be made due to data in the corresponding line in the import file:
Starting point is again the chart LIA3x4 in the Master Data Library:
(create cha

PCS 7 System Course
Select the proper import file to the process tag type. After clicking the Finish button in
the last window the import will actually start.
(create charts
1 2
1) The interconnection descriptions from the import files are not only written to the
assigned I/Os, but also to the symbol tables of resources for the relevant hierarchy
folders.
2) Any open textual interconnections are automatically closed during import.
A log will be displayed and saved in a file:

PCS 7 System Course
Final result
The final result:
• New hierarchy folder with new charts
• Data in the chart due to the data in the import file
Final Result
Changed symbol
for a process tag
Data due the

data import file
Task: Valves as Process Tag
Goal
New (temporary) charts for controlling the 5 valves of D220 and R320, based on a
Process Tag Type.
Checkpoint
• How to proceed if another person wants
to fill up the import file on an office PC?

PCS 7 System Course
14.3.4 Models
Models use a similar procedure as Process Tag Types, but there are differences:
Process Tag Type Model
Scope 1 single CFC chart 1 hierarchy folder that may contain

• several sublevel folders
• several CFC charts
• several SFC charts
• a picture in every hierarchy folder
Selection of Navigation tree for 1 large table with checkboxes for
I/O points blocks and parameters: the parameters and signals:
Connection Will be copied only for connections Will be copied, as long it is between the objects
between blocks in the single chart of the model, including CFC - SFC - picture
Create Model…
For creating a Model you can start with an existing hierarchy tree.
At creation it will be copied to the Models folder in the Master Data Library.
If pictures are part of the model, an OS will be created in the Component View of the
Master Data Library, to contain the pictures.
 Start the Create Model … procedure from the hierarchy folder displayed in the right
hand window pane!
14.3.5 Tasks and Checkpoint
Task: Model of the reactor and Chart Reference Data
Goal
All controlling and monitoring functions for D220/R320, D230/R330 and D240/R340,
based on a model.
Understand the use of the tool Chart Reference Data

PCS 7 System Course
14.4 New Type Model
Process Tags and Control Modules

In addition to process tag types and process tags, there are now control module types
and control module instances (from PC S 7 V7.1 SP2).
These support instance-specific changes in case of process tag synchronization and
several versions of process tag types. Data exchange with PCS 7 Advanced ES is also
possible.
A process tag type or a control module type is a CFC configured for a specific process
control function for the basic automation of a process engineering plant.
Process Tags from Control Modules from

Process Tag Types Control Module Types
Tool for the bulk engineering: Tool for the bulk engineering:
Import Export Assistant (IEA) Advanced ES (optional package)
Reimport of the Importfile using the IEA: Synchronization of type and instance:
Instance-specific changes are lost. Instance-specific changes are not lost.
Use of different Input blocks for same Use of Variants with optional Input blocks:
technological function:
Different instances are possible from the

Multiple Process Tag Types are required. same Control Module Type.
ISA 88 German ISA 88 English Acronym

(1) (1)
Einzelsteuereinheitstyp Control Module type CMT
Einzelsteuereinheit Control Module CM
(1)
Is typically a cluster of measuring devices, actuators and other control modules and
the associated processing devices operated as a single unit from the perspective of the
control system.
What is the Advanced ES?

The Advanced Engineering System (AdvES) prepares data for use in the PCS 7
engineering system (ES). It represents an application for data import and bulk
processing. Data is imported into AdvES from process tag or signal lists and adopted in
PCS 7. The technological hierarchy, signal and parameter settings as well as the
hardware configuration are adopted. In AdvES, object-dependent bulk processing and
queries are possible. AdvES provides enhanced functions for plant engineering in the
SIMATIC PCS 7 software.
 See [151] PCS 7 V8.0 Advanced Engineering System - Configuration Manual -

12_2011 for more details

PCS 7 System Course
Handling options
 For more details about Control Module Types please refer to

[103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.6 and
[302] PCS 7 CFC for SIMATIC S7 - Function Manual - 12_2011, 9.11
Checkpoint
Let‘s think about the following…

• Can you imagine a situation to implement a
model extra to this case in the training
application?
• What will be the most sufficient tool available
for the bulk engineering in 5 years?

PCS 7 System Course
Content 15
15 Final steps of configuration ...................................................................................3
15.1 Learning target....................................................................................................................... 3
15.2 AS-AS Communication .......................................................................................................... 3
15.2.1 Overview ................................................................................................................................ 3
15.2.2 Automatically configuration of AS-AS communication .......................................................... 4
15.2.3 Manually configured connection to a specified AS ................................................................ 7
15.2.4 Manually configured connection to an unspecified AS.......................................................... 8
15.2.5 Using manually configured AS-AS connections: Communication blocks in CFC charts....... 9
15.2.6 Task and Checkpoint ............................................................................................................. 9
15.3 Configuration in Run ............................................................................................................ 10
15.3.1 Existing configuration........................................................................................................... 10
15.3.2 Activate CiR capability ......................................................................................................... 10
15.3.3 Reservation.......................................................................................................................... 11
15.3.4 Check CiR Compatibility ...................................................................................................... 13
15.3.5 Adding modules ................................................................................................................... 13
15.3.6 Download ............................................................................................................................. 14
15.3.7 Save and Compile ............................................................................................................... 14
15.3.8 Workflow overview............................................................................................................... 15
15.4 Simulation ............................................................................................................................ 16
15.4.1 Block-external simulation..................................................................................................... 16
15.4.2 Block-internal simulation...................................................................................................... 17
15.5 Forcing block I/Os ................................................................................................................ 19
15.5.1 Preparation: Support forcing and Add forcing ..................................................................... 20
15.5.2 Forcing active and Force value............................................................................................ 21
15.5.3 Exit forcing ........................................................................................................................... 22
1.
2.
3.
SIMATIC PCS 7 – Final steps of configuration

PCS 7 System Course

PCS 7 System Course
15 Final steps of configuration


• Configuration steps required typically
before commissioning of a plant
• How PCS 7 supports testing and
simulation of blocks and IOs

• to configure an AS-AS connection
• to prepare later modifications of the
configuration on Profibus during
operation, without stop of the CPU
• to simulate a process signal via a
faceplate on the OS and via CFC on the ES
15.2 AS-AS Communication

15.2.1 Overview
For communication between AS systems, an AS-AS interconnection is required.
AS01 AS99
Connection
AS-AS Communication:
Exchange of information
between blocks
Use cases
• Plant expansion or changed customer requirements may result in an overload of an
AS-CPU. In such cases an additional AS system can be a sufficient solution.
• Already existing automation solutions have to be integrated into a plant. This may
require also an integration of already configured AS systems. Possible plant-wide
automation functions require AS-wide communication.

PCS 7 System Course
PCS 7 offers 2 different configuration procedures for the realization of AS-AS

interconnections:
Automatically configured Manually configured

AS-AS communication AS-AS Communication
• Automatical creation of an S7 connection in NetPro for • Manual creation of an S7 connection in NetPro

each AS pair, for which an AS-wide interconnection for each AS pair
has been created • Specialized communication blocks have to be
• No need for communication blocks in CFC configured in CFC charts
15.2.2 Automatically configuration of AS-AS communication
AS-wide interconnections
Since PCS 7 V7.1, cross-chart interconnections are now also possible if the CFC charts
exist in different AS’s. To accomplish this, simply open the CFC charts and arrange
them in such a way that the source can be connected with the destination. If the source
and destination are located in different AS’s, an AS-AS interconnection is automatically
configured in NetPro.
Prerequisite:
The AS stations have to be part of the same ethernet segment.

PCS 7 System Course
"First" cross-chart interconnection

When establishing the first cross-chart interconnection in which the source and
destination are located in different AS’s, a message is displayed.
Open and compile NetPro
Load connection in ASx and ASy
If the "first" cross-chart interconnection was established between ASx and ASy, then
this interconnection need to be loaded as follows.
1. Open and compile NetPro
2. Load connection in ASx and ASy
To load the interconnection in ASx and ASy, you have several options:
− PLC > Download to Current Project > Selected Stations
− PLC > Download to Current Project > Connections and Gateways
− Download selected connections
Only the function "Download selected connections" should be used to download
the connection, to avoid an AS stop or an initialization of the existing connections and
therefore a disturbance of the plant operation.
Select the corresponding AS (e.g. ASx) in NetPro and then the connection which you
want to load.
Result in NetPro

PCS 7 System Course
Merging Subnets
If the AS-wide interconnection is rejected with the "NETPRO error", the cause of the
error has to be corrected, e.g. by merging the subnets in NetPro:
Edit > Merge/Unmerge Subnets > Ethernet Subnets"
After having merged the subnets, the two CFC charts have to be opened again. In one
of the charts, click the connection to be interconnected and in the other chart on the
interconnection partner. An interconnection line to the side bar should now be
established automatically. In the small field on the side bar, the AS-wide interconnection
is marked by a green triangle.
Connection monitoring with the IK_STATE block

The status of an AS-wide interconnection can be queried in the CFC chart with the help
of the IK_STATE block (FC157). For that, the IK_STATE block is placed on a CFC chart
and the NETPRO_I input of this block is parameterized with the numerical value "local
ID" of the connection.
Local ID of the
Local ID Local ID connection
of AS08 of AS99
details

PCS 7 System Course
15.2.3 Manually configured connection to a specified AS

For communication between AS systems, an AS-AS connection is required.
Its manual configuration in the tool NetPro is similar to an OS-AS connection. The
communication partner is located inside of the current multiproject.
Starting
point
Connection
partner, specified
in the multiproject
After clicking the OK button, the properties of the connection are displayed:
After insertion of a new connection:

• Save and compile NetPro A Local ID is assigned
to the connection.
• Download selected connections
without CPU Stop

PCS 7 System Course
15.2.4 Manually configured connection to an unspecified AS

If a connection is to be made to a station, that is connected to the same network, but not
specified in the project, it can be configured as below.
AS06
08-00-06-9C-EA-F6
In the Partner column of the Address

Details dialog, you fill up the data, that is
set in the Local column on the Engineering
station of your partner that is configuring
the connection in his system.

PCS 7 System Course
15.2.5 Using manually configured AS-AS connections: Communication blocks

in CFC charts
After establishment of the AS-AS connection, special communication blocks have to be
placed in the charts of the involved AS stations.
The communication blocks are located in the PCS 7 Library (Standard library).
Chart in AS08
Chart in AS99
Task: AS-AS communication
Goal
Exchanging data between two AS stations
Checkpoint

• What the advantage/disadvantage of
using AS-AS communication for
duplicating an analog input signal,
compared to using an analog input
channel on both AS systems and routing
the same current signal?

PCS 7 System Course
15.3 Configuration in Run

By default, every change to an AS Station Configuration requires a stop of the CPU.
Settings to the Profibus DP can be changed to allow you to:
• Add slaves to the Profibus
• Add modules to existing modular slaves
Check the requirements for using this CiR functionality.
Example
As an example, here we will add 2 modules to an existing modular slave.
15.3.1 Existing configuration

The current AS configuration consist of:
• a central rack with PS, CPU and CP
• a modular DP slave with 2 I/O modules
See its representation in HW Config in the picture below.
What you see here is not yet using the CiR capability.
15.3.2 Activate CiR capability

The CiR capability is to be activated in HW Config, and after checking some setting it is
to be download to the AS station in STOP mode (for the last time). For activating, point
the mouse pointer to the Profibus DP network and select in the context menu:

PCS 7 System Course
15.3.3 Reservation
After the activation of the CiR capability there will be objects displayed to represent
reservation of address areas supported by the CiR function:
Address size for additional modules

By default, additional I/O modules in modular slaves have 16 bytes for input and output
available:
In this example we will not change this setting.

PCS 7 System Course
Address size for additional DP slaves

By default, additional DP slaves can be added using these settings:
The sum of the address ranges

should not exceed the available
size of the Process Images
These settings are to be downloaded in STOP mode.

PCS 7 System Course
15.3.4 Check CiR Compatibility

From now on, you can make changes to the station configuration, regarding the
decentralized I/O on the Profibus DP network.
Any time after making changes, you should check the compatibility, before you start the
download:
The result must be:
15.3.5 Adding modules
Drag them on top

of the CiR module
Address
ranges left
Check
compatibility

PCS 7 System Course
15.3.6 Download
The download can be

done now during RUN
mode of the CPU.
A general warning will be

prompted that an interrupt
(frozen) of the output signal
may last 1000ms.
A message on the OS will

show you how long it took
actually..
15.3.7 Save and Compile

After a successful download, you can make a Save and Compile.

PCS 7 System Course
15.3.8 Workflow overview

mplete workflow
System hardware configuration with CiR objects
Save and compile. Download in STOP mode
HW Config change
Check CiR function “CTRL+ALT+F”
Yes
Fault?
No
Download in RUN mode (CPU online check)
Yes
Fault?
No
Close HWConfig
WITHOUT saving ! !

[223] Configuration in Run - 03_2006 and
[103] PCS 7 V8.0 Engineering System - 12_2011, 8.9.7
Task: Configuration in Run
Goal
Modification of the configuration on Profibus during operation, without stop of the CPU
Checkpoint
Think about the time schedule

your project…
• What is the best moment during the
commission of an application to
activate the CiR functionality?

PCS 7 System Course
15.4 Simulation
Simulation means the manipulation of a signal regardless of the actual source of the
signal or logic that generates this signal.
Simulation is carried out either at the field device (externally from the control system)
itself or at a block (internally in the control system).
During the simulation, every block is considered in isolation. There are two different
forms of simulation here, namely:
• Block-external simulation and
• Block-internal simulation.
In either case the status of the signal is set to the simulation value (16#60)
 ATTENTION!
The process output is not influenced by the simulation. This means that the motor or
the valve will be operated. The only exception is the block-external simulation of the
output driver.
15.4.1 Block-external simulation

Block-external simulation is characterized by the fact that:
• The simulation function is not executed in the block itself and
• A signal whose status has the simulation state, for example, a simulation of the signal
at another block or directly in the I/O device, is applied at an input parameter.
Simulation is
displayed
Value can‘t be
changed in the OS
In the picture above, the process value has been set to simulation.
The block-external simulation has the following effects on the functionality of the block:
• The technological functions are not influenced
• All the process-relevant output signals do not receive the simulation status. In the
case of technologic blocks, process-related output signals are parameters that
actively affect the process, e.g. "Start" for block MotL.

PCS 7 System Course
• In the case of blocks with operator control or monitoring functions (for example
faceplates), these signals are identified in the faceplate with the status for the
simulation as follows:
• Blocks with one or more input parameters for signals with "Generate status from
individual status" receive a group status in accordance with the priority table. This
group status is displayed in the status bar of the block icon and of the operator block
with the simulation status as follows:
• The interlocking functions of the block are not influenced.
 For the output channel blocks, you need to specify the exact block response with
external simulation using the Feature bit 30 “Outputting a de-energized value for
block-external simulation”.
15.4.2 Block-internal simulation

Block-internal simulation is characterized by the simulation function being run in the
block itself.
With operator control and monitoring blocks, all process values which cannot be
controlled (e.g. PV, AV, In) can be simulated. This is used primarily as an aid for
commissioning and servicing of the system. For example, the control settings of a motor
can be simulated and the feedback values corrected without the monitoring functions
being active.
For blocks that can be operated and monitored, simulation can take place via the
faceplate as well as interconnectable inputs:
• SimLiOp = 0: The simulation is activated/deactivated via faceplate (parameter view)
at the input SimOn.
• SimLiOp = 1: The simulation is activated/deactivated via the input SimOnLi. The
interconnectable simulation values (e.g. SimPVLi, SimAVLi, and SimInLi) will
become effective in the process.
Simulation can also be carried out for blocks (such as channel blocks) that cannot be
controlled and monitored by the operator.
The control is simulated in the CFC by setting parameters directly in the block with the
input parameters SimOn = 1 and Simxxxx is set to the desired simulation value (e.g.
SimPV, SimAV or SimIn).
 With channel blocks, ensure that the Mode parameter is set correctly during
simulation. Otherwise this is displayed on the Bad = 1 output parameter with a higher-
level error.

PCS 7 System Course
Simulation takes place in runtime using operator input in the faceplate's parameter view
by clicking on the "Simulation" button.
Simulation is
displayed
Value can be
changed in the OS
This simulation is characterized by the fact that:

• The simulation can only be enabled / disabled with the operator authorization level for
system authorization.
• The technological functions are not influenced.
• All the process-relevant output signals receive the simulation status, for example,
signals for further processing in other blocks.
• In the case of blocks with operator control or monitoring functions (for example
faceplates), these signals are identified in the faceplate with the status for the
simulation as follows:
• The group status of the block is displayed in the status bar of the block icon and of
the operator block with the simulation status as follows:
• All the process values displayed in the faceplate that cannot be operated-controlled
in normal operation (e.g. PV).
• When the control function of the block can be manipulated, the read-back and
feedback values (for example Rbk, FbkSpd1) are adjusted according to the
manipulation of the control settings
• Associated values (for example UserAna1) cannot be simulated.
• The interlocking functions of the block are disabled and are displayed using the
corresponding icon in the faceplate and in the block icon as follows:

PCS 7 System Course
15.5 Forcing block I/Os
Introduction
During commissioning, you can simulate a variety of values for an interconnection by
permanently overwriting the value of an interconnection with a forced value.
During forcing, the interconnections between the blocks are temporarily removed and
force values are assigned to the corresponding inputs (IN or IN_OUT) of these
interconnections.
For reasons of performance, neither the chart folder nor the block inputs are activated
for the forcing. If a block input on a block is to be forced, first the chart folder and then
the desired block input(s) is/are to be released for the forcing.
You can activate and deactivate forcing at the input of the block instance at any time.
 A maximum of 8192 standard and 8192 F I/Os can be forced.

If you activate forcing at the chart folder, the program will need to be recompiled and
downloaded (compilation of the entire program).
 See [103] PCS 7 V8.0 Engineering System - 12_2011, 8.12.3.15 for more details
General procedure
Forcing is controlled by the following attributes:
Support forcing Chart folder in the component view of

the SIMATIC Manager.
Requires complete chart compilation.
Add forcing
Block I/O properties. Requires
compilation and download of changes.
Forcing active
Block I/O properties. Can be done in
Test mode
Force value Block I/O properties. Can be done in

Test mode

PCS 7 System Course
15.5.1 Preparation: Support forcing and Add forcing

1. In the object properties of the chart folder, select the "Advanced" tab and activate
the "Support forcing" check box. This will enable the Force function.
SIMATIC Manager CFC Editor, Block I/O Properties
An activated "Support forcing" requires a complete compilation and a download of

changes to the CPU. Therefore, a CPU stop is not necessary.
 In the case of forcing, a new system chart @FRC_CFC is automatically installed with
a runtime group of the same name in OB1 during compilation. The message block
FRC_CFC is added to this chart, as well as being added to the OB100.
If forcing is disabled, the block, the system chart, and the runtime group are removed
again from the program the next time you compile and download.
2. After having activated "Support forcing", "Add forcing" can be activated in the object
properties dialog box of the interconnected block inputs. Now only compilation and
download of changes are required.
The action in the CFC editor is done offline; therefore always a download of changes is
required, to make the changes active.
After the “Add forcing” action, the input parameter is marked by a green rectangle.

PCS 7 System Course
15.5.2 Forcing active and Force value
Forcing in CFC Editor
When the check box “Forcing active” is activated, the value of the interconnection is
permanently replaced by the force value. The value of interconnection becomes active
again when forcing is disabled. Use the "Force value" textbox to enter a value to be
applied to the block input.
After the “Add forcing" and "Forcing active" action, the input parameter is marked by a
red rectangle.
 A change in CFC Test mode does not require recompiling. The "force values" have a
blue background. The “force value” is valid just after activating the checkbox “Forcing
active”.
Forcing in the Process Object view

PCS 7 System Course
In the process object view, the block inputs which have been added for forcing are
displayed when the corresponding attribute (S7_edit) is set. In the process object view,
the user has the option to select block inputs via a filter. There are three filter settings
available for forcing:
• Add forcing
• Forcing active
• Forcing value
15.5.3 Exit forcing
• If you exit the test mode and further values have been added for forcing in this AS, a
corresponding message is displayed.
The "Forced block I/Os" list in the chart reference data provides an overview of all block
I/Os for which "Forcing active" is still activated.
• If "Support forcing" is deactivated in the chart folder, a message is displayed stating
that a complete compilation has to be performed.
Task: Simulation
Goal
Test the high warnings of LIA134
Checkpoint
There are so many different

simulation features…
• When shall I use what type of
simulation?

PCS 7 System Course
Content 17
17 Demonstration: Server-Client Systems .................................................................3
17.1 Learning target....................................................................................................................... 3
17.2 System architecture ............................................................................................................... 3
17.3 Configuration Steps ............................................................................................................... 6
17.3.1 Setting up the multiproject ..................................................................................................... 6
17.3.2 Configuring the functional information ................................................................................... 7
17.3.3 Distributing the configuration information .............................................................................. 8
17.3.4 Information flow chart ............................................................................................................ 9
1.
2.
3.
4.
5.
6.
7.
8.
9.
SIMATIC PCS 7 – Demonstration: Server-Client Systems

PCS 7 System Course

PCS 7 System Course
17 Demonstration: Server-Client Systems


• The PCS 7 System architecture in case
of Server-Client Systems
• Main configurations steps for a PCS 7
Server-Client System
17.2 System architecture
OS server
An OS server is connected to the automation systems and receives the process data.
By using more than one OS server, you have the option of distributing data over multiple
OS servers. For example, for a large plant, you can store a plant unit on each OS
server.
The advantages of distributed systems are:
• Good scalability
• Isolation of plant units
• Higher availability as a result of good scalability and isolation of plant units
PCS 7 supports simultaneous access of an OS server to several other OS servers
(Server- Server communication).
 An OS server can have also operator control and monitoring functionality only if a
maximum of four OS clients access this OS server.
OS clients
OS clients are used in process mode for operator control and monitoring. OS clients
access the data of the OS server, visualize this data and allow operators to control the
process. Data from several OS servers is displayed in a process picture that is
displayed on the OS client. You can connect up to four process monitors to OS clients.
This requires the use of multi-VGA cards.
ES
The engineering system is structured on matching applications, facilitating the central,
project-wide engineering of all the components on a PCS 7 plant. This includes also the
central configuration of OS servers and clients.

PCS 7 System Course
Representation in the multiproject:
Engineering
System Operator System
Client
4
2
6 Terminal Bus
Operator System 3
Server
Plant bus
5
Automation 1
System
Field
For comparison: Our multiproject Multiproject with multiple station

with ES/OS single station system for demonstration
1
5
2
4
3
Differences:
• AS- and OS stations are located in

different user projects (recommended)
• ES Station with an Application but Where is the
6
without OS object Terminal bus?
• Different WinCC Applications for OS
server and client
• Ethernet subnets have to be
merged in the multiproject
 It is not allowed, to activate the process mode of an OS server on your engineering

station. Use the OS simulation to test an OS on an engineering station in process
mode. There are some prerequisites:
- There is an ES – AS connection. This requires a WinCC application in the hardware
configuration of the engineering station. An OS object is not required.
- The symbolic names of each connection (OS - AS, ES - AS) are identical.

PCS 7 System Course
Plant hierarchy
CFC, SFC charts,

no pictures
AS project
Link symbol on pictures,

hierarchy folders no charts
OS project
The plant hierarchy is a powerful ES tool, to create a relation between automation

functions in the AS program and a hierarchic picture tree on the OS.
• The configured process tags (charts) are identified using their location in the plant
hierarchy. This results in the “Higher level item designation” (HID), used for instance
in the “Source” information for a message.
• Use the "OS area" setting to define the selected level as the OS area and to accept it
in the area identifier. The definition of an OS area is necessary for area-specific
messages in process mode.
• You insert process pictures in the plant hierarchy in respect to the structure of your
PCS7 plant. The picture hierarchy from the plant view is transferred to the PCS 7 OS
Picture Tree Manager.
• The “Create / update Block icons” function requires the plant hierarchy to identify the
correct picture where a block icon has to be inserted.
• The User administration in the WinCC Explorer is based on OS areas.

PCS 7 System Course
17.3 Configuration Steps

17.3.1 Setting up the multiproject
Windows, Create a shared folder with user authorization on each target PC

Local PC
Simatic Rights
Local PC Windows Configure network components (Terminal bus, Simatic Shell)
ES Simatic Manager Create a multiproject with an AS project („New project“ wizard)
ES Simatic Manager Create an OS Project in the multiproject
ES Simatic Manager Insert PC stations for ES, OS server and OS client
ES Simatic Manager Configure target path, computer names, symbolic names
ES Simatic Manager, Configure the stations (ES, AS, OS server and networks
HWKonfig, NetPro
ES Simatic Manager, Load stations (ES, AS, OS server) and networks

HWKonfig, NetPro
(ES-AS, OS-AS connections)
User authorization
You need a defined administrator account for the administration of the operating system
and the PCS 7 installation. The user account control is to be activated. It is
recommended for the productive operation of a PCS 7 system to operate the stations
with a user account without administrative rights.
Siemens TIA Engineer is a new user group required in Windows 7: It authorizes the
respective user without administrator rights to adapt the SIMATIC PG/PC interface
including CP16x3 .
Thus, the role "project engineer" under Windows 7 / Server 2008 needs the following
rights for the ES and the respective destination stations:
• User + Siemens TIA Engineer + SIMATIC HMI
or
• Administrator + SIMATIC HMI
Power user rights are still required under Windows XP /Server 2003.
Shared folder
• Target path = Path to shared folder on target PC.
• Full access for user groups listed above or for everyone if there are no security
considerations

PCS 7 System Course
Computer names
Computer names must not be changed after a PCS 7 installation. We recommend using
a PC stations name identical to the physical computer name of the corresponding
station. This concerns all PC stations (ES, OS server, OS client).
The PC station name of the OS client has no further functional relevance.
Symbolic computer name

The default symbolic name of an OS server is formed from the name of the user project
containing the OS and of the OS name.
It is recommended to replace the default name by a meaningful name, because this
name is used in several configuration steps.
PLC configure
The station configuration information has to be transferred from the project to the local
stations. This transfer occurs via a network connection using TCP/IP, in other words, in
most cases via the Terminal bus. OS clients cannot be configured.
Download of stations and networks

The PLC configure transfers only the information which component is expected to be
located in which slot position in HW config. Loading a station transfers also the
information of configured component properties and functions.
In this early configuration stage, there does not exist any information to be loaded to an
OS client.
17.3.2 Configuring the functional information
ES Simatic Manager Create the plant hierarchy and update it in the multiproject
ES Simatic Manager Assign AS and OS in the plant hierarchy
ES Simatic Manager, CFC, SFC Configure automation functions in the AS project
ES Simatic Manager Create pictures (place holder objects) in the OS project
ES Simatic Manager Compile the OS
ES WinCC Explorer Configure OS functions (OS project editor, other editors)
ES Simatic Manager Create Server data (if not already done during OS compilation)
ES Simatic Manager Assign OS servers to the clients
ES WinCC Explorer Define the standard server for the clients

PCS 7 System Course
Create Server data

The Server Data Package is a file generated from the OS Server project on the ES
computer. The Server data contain all information relevant for the OS clients, e.g. a
listing of all I/O tags and process graphics. The purpose of this file is to provide other
OS computers with the full network pathway to these tags and graphics on the physical
OS Server computer.
Server data are created automatically during OS compilation. If the OS project
configuration was changed without need for OS compilation, then Server data can be
created manually, to update the information of the package.
Assign Server Data

All PCS 7 OS applications that require access to a particular Servers data (Clients,
other OS Servers) need to have its Server Data Package assigned to them.
Standard server for OS clients

Each OS client has always own local configuration and runtime data. For instance, trend
groups can be created locally by an operator. Another example is local operator
messages. You configure a Standard server for alarms and for SSM for each client to
allow sharing of the local information with other clients.
17.3.3 Distributing the configuration information
ES Simatic Manager Load the OS server
ES Simatic Manager Load the OS clients
Local Windows Explorer Distribute customized graphic files (faceplates, meta graphics)
Local WinCC Explorer Activate the OS runtime on the OS server
Local WinCC Explorer Activate the OS runtime on the OS clients
Loading the OS server

If all OS configuration work is finished, then the OS project has to be load to OS server
(PLC download). The download occurs via the Terminal bus; therefore the involved
network adapter must be visible in the Simatic Shell. The first download is a complete
download.
Loading the OS clients

For OS clients only the complete download is possible. After later changes in the OS
configuration, the OS client update occurs automatically via the update of the Server
data package for the OS server.

PCS 7 System Course
Distribution of customized graphic files

If user specific graphic files are used (e.g. customized .emf files for Extended Status
Displays), then these files have to be copied manually from the GraCS folder of the OS
project to the local GraCS folders.
17.3.4 Information flow chart
Engineering
System Operator System
Client Defined by
Load OS server data
Client
Terminal Bus
ES-AS Operator System

connection Load OS
Server
Server
Plant bus
Automation
System OS-AS
connection
Shared folder with suitable access rights

Field OS server project, OS client projects
Server data packages

PCS 7 System Course
Content 18
18 Syntax Rules..............................................................................................................3
18.1 Special Characters ...................................................................................................................3
18.1.1 General Background Information..............................................................................................3
18.1.2 PC(s).........................................................................................................................................4
18.1.3 ES .............................................................................................................................................4
18.1.4 OS.............................................................................................................................................5
18.2 Maximum Length for Names.....................................................................................................6
18.2.1 ES – CFC..................................................................................................................................6
18.2.2 ES – SFC ..................................................................................................................................6
18.2.3 ES – Blocks...............................................................................................................................6
18.2.4 ES - General Naming in Project................................................................................................7
18.2.5 OS – Alarm Logging .................................................................................................................7
18.2.6 OS – Pictures and Variables.....................................................................................................7
18.3 Rules for Naming in the PH ......................................................................................................8
SIMATIC PCS 7 – Syntax Rules

PCS 7 System Course

PCS 7 System Course
18 Syntax Rules
18.1 Special Characters
This section provides information on which special characters should not be used in
your PCS 7 projects.
18.1.1 General Background Information

PCS 7 OS utilizes WinCC in its underlying software and structures the PC, ES, and OS
into common interrelated groups. Therefore the naming within all three of these groups
must follow standards different from typical WinCC standards. The standards apply
specifically to the use of Special Characters (signs).
Each of the three components (PC, ES, & OS) has its own naming requirements which
must be followed. The following Tables indicate the Special Characters (signs) which
should not be used. The underscore (_) is allowed for naming. Within the WinCC
portion of the OS, you may use the ASCII Character set (although, do not use National
special character sets). Avoid all special characters in object names, particularly, if the
object names are used in Scripts. The following tables show the characters which you
may not use in WinCC components, designations and specified names.
Additionally, Microsoft Excel interprets texts with special characters as formulas. For
this reason these characters should not be used as part of object naming schemes
(e.g., “=”, “+”, ‘-“) for group name, variables, texts, etc.

PCS 7 System Course
18.1.2 PC(s)
Component Do not use these characters Remarks

Computer name [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] Only capitalization is relevantly
[+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] First indication must be a letter.
[{}] [<] [>] [space]
DNS Hostname [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-]
[+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]]
[{}] [<] [>] [space]
path: [:] [?] ["] [/] [*] [<] [>]
Name of folders
Communication / OPC: [.] [:] [?] ["] ['] [\] [*] [%] [space]
used names
Web Client: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-]
used names [+] [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]]
[{}] [<] [>] [space]
18.1.3 ES

Hierarchy folder [.] ["] [/] [\] [%]
Global Symbols 0x00 and When using special characters
[‘] [.] [“] [%] [\] [*] [?] [:] [Space] the symbol must stand in
Double underscore quotation marks.
Local Symbols letters, numbers, [_] are allowed
Variables Space and [‘], [.], [%] [-] [/] [*] [+]
CFC-charts
Chartname with OS Space and [‘], [.], [%] [-] [/] [*] [+]
Chartname without OS [.] [%] [\] [“]
Chart comment whole ANSI code is allowed
Run time groups [.] [%] [\] [“]
Task [.] [%] [\] [“]
Blocktypes Made by Step 7
Parameter name Made by Step 7
First character can't be a
number
Parameter comment whole ANSI code is allowed
Name of the [.] [%] [\] [“]
blockinstance
Comment of the whole ANSI code is allowed
blockinstance
Global Variable [“]
S7-Program Space and [‘], [.], [%] [-] [/] [*] [+]
Names of WinCC-Projects [.] [,] [;] [:] [!] [?] ["] ['] [+] [=] [/] [\]
[@] [*] [%] [[]] [{}] [<] [>] [Space]
AS-OS -Interconnections [.] [:] [?] ["] ['] [\][*] [%] [Space] Relevant for OS-Compile
(Netpro)
Variables [‘] [.] [%] [\] [*] [?] [:] [Space] Will be changed into [$]
But [$] is not allowed???
SFC-chart / SFC-Type [/] [\] [.] [“] [%]

PCS 7 System Course
18.1.4 OS

WinCC-Project: [.] [,] [;] [:] [!] [?] ["] ['] [+] [=] [/] [\] Case sensitive
Names of WinCC projects [@] [*] [[]] [{}] [<] [>] [Space]
Variables: [:] [?] ["] ['] [\] [*] [$] [%] [Space] Not case sensitive
Variable names "@" is reserved for System
variables
The point is used as separator
for structure variables
Variables: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Names of process tags in Tag [=] [/] [\] [*] [%] [&] [§] [°] [[]] [{}] [<]
Logging [>] [Space]
Variables: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Names of archive variables in [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
Tag Logging [<] [>] [Space]
Variables: [?] ['] [\] [Space] Not case sensitive
Names of variable groups
Structure types: [.] [:] [?] ['] [\] [@] [*] [%] [Space]
Names of structure types,
structure elements, structure
instances
Graphics Designer: [:] [?] ["] [/] [\] [*] [<] [>]
Names of pictures (PDL-files)
Graphics Designer: Avoid using special characters if The name can be no longer
Names of objects in pictures the object name is used in scripts. than 180 characters.
For more detailed information, If you use special characters,
refer to the documentation on VBS the maximum number of
in the section Testing with the characters is further restricted.
Debugger > Action and Procedure
Names in the Debugger.
Graphics Designer: [;] Restriction with assigned and
Object type text list referenced texts
Graphics Designer: [%]
Names in Dynamic Wizard
Alarm Logging: ['] [enter] [linefeed]
Names of message blocks,
message class, type of
message, message texts
Tag Logging: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+]
Archive name [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
[<] [>] [Space]
Tag Logging / Trend control: single "&"-will not be displayed
Label of timeline and value line double "&"-will be displayed as
single.
Report Designer: [:] [?] ["] [/] [\] [*] [<] [>]
Names in page layout und line
layout
User Administrator: ['] [\] Not case sensitive
User names
User Administrator: ['] [\] Case sensitive
Password
User Administrator: ['] [\]
User rights
User Archives: [,] [;] [:] [!] [?] ["] ['] [^] [´] [`] [~] [-] [+] First character must be a letter
Names for archives, fields, [=] [/] [\] [*] [#] [%] [&] [§] [°] [[]] [{}]
views, rows [<] [>] [Space]
Server Data: [,] [/] [\]
Names of Packages National special signs, e.g. é

PCS 7 System Course
18.2 Maximum Length for Names

This section describes the allowable maximum length for naming used in various areas
of the ES and OS.
18.2.1 ES – CFC
CFC Chart naming is restricted to a length of 22 characters. Anything longer will be
truncated. Any object placed on the chart, such as a block, has a maximum character
length of 16 for naming.
Component Maximum length Remarks

Chart 22 Name of charts in plant view
Chart comment 7 resp. 14 out of 255 Depends on the size: from the
255, only 7 or 14 are displayed.
In the CFC properties in the
plant view
S7_String_0-1 16 In the block properties in CFC
S7_String_2-25 8 In the block properties in CFC
Textual interconnection 512 Between blocks in CFC
Runtime group 22 The several blocks can be
grouped in runtime groups
Parameter comment 80 In the block settings in the CFC
chart
Name of the block instance 16 In the block settings in the CFC
chart.
Picture.
Comment of the block instance 80 In the block settings in the CFC
chart.
Picture.
18.2.2 ES – SFC

SFC chart 22
SFC type 16
Sequencer name 16
Sequencer comment 80
Criteria 24
Instance name 8-24
Setpoint 16
Timer 16
Block contacts 10
18.2.3 ES – Blocks

Header 8
Author 8
Family 8
Version 4 0.0 up to 15.15
Block comment 16

PCS 7 System Course
18.2.4 ES - General Naming in Project

Library names 8 Longer than 8 character will be
cut off
Project names 8 Longer than 8 character will be
cut off
Symbols 24
Symbol comment 80 Via export as *.SEQ it will be cut
off after 40 characters
Variables 128 Attention for the OS: the
Variable name is shorter then
128 signs for some reason
Hierarchy folder 1 up to 12 Depending on the settings of the
Hierarchy 1 -24 but this can’t be
displayed on the OS
18.2.5 OS – Alarm Logging

In the OS, you will configure messages using the alarm logging editor. Using the editor,
you configure the length of texts for messaging. The following table provides the
maximum character lengths allowed.

User blocks 32 out of 255 Time correct alarms
User blocks for bit reporting 1-255 The length can be limited
procedure individually for the individual
colums
18.2.6 OS – Pictures and Variables

The OS Pictures and Variable naming lengths must also be considered at project start.
The following table provides the maximum lengths guidance.

Picture name 24 out of 255 After 24 characters the name is
cut off
Object name 128
Container name in the picture 255 Minus the number of characters
tree for the server prefix
Computer name 21
Archive variable 52
OPC text variable 160

PCS 7 System Course
18.3 Rules for Naming in the PH
Extending the Basic Structure

Use the PCS 7 wizard to create a maximum of 8 hierarchy levels without additional
nesting of hierarchy folders. You can further extend this basic structure during
configuration by adding further hierarchy folders and/or technological objects.
When doing this, remember the following rules for naming folders/objects in the plant
hierarchy.
Rules for Naming Folders/Objects

• The following special characters may not be used in the name of a hierarchy folder: [
.][%][/][\]["]
 Note
The characters [ ' ] [ . ] [ % ] [ \ ] [ * ] [ ? ] [ : ] [spaces] within a name are converted to
the substitute character $ when you compile the OS.
The ES separator [ \ ] is converted to the [ / ] character.
If, for example, you assign the name "TICA:1" for a CFC chart (this becomes
"TICA$1" on the OS) and the name "TICA*1" for another CFC chart, (also becomes
"TICA$1"), you will receive an error message when you transfer the second chart
because the chart name already exists.
• The maximum length of a tag name is 128 characters. Remember, however, that
many of the editing windows on the OS can not display 128 characters in their
entirety. You should therefore restrict the length of the HID.
• Remember that special characters associated with certain national languages take
up two characters, thus reducing the maximum name length accordingly.
• Remember that the length of the texts transferred depends on the maximum text
length of a target block in the OS (Tag Logging, for example, event 50 characters;
origin 32 characters). When compiling the "OS" texts up to a maximum length of 255
characters are transferred.
Remedy:
Increase the maximum character length of the user text field or select a shorter HID.
• The message texts of the transfer messages are made up of the hierarchy path, chart
name, and the block name (if you decided to include the names in the HID).

PCS 7 System Course
Content 19
19 Tasks ........................................................................................................................3
19.1 Multiproject............................................................................................................................. 3
19.2 Station Configuration PC ....................................................................................................... 5
19.3 Station Configuration AS ....................................................................................................... 6
19.4 Plant Hierarchy ...................................................................................................................... 7
19.5 Drivers for the Signal Box ...................................................................................................... 8
19.6 Installing the process simulation.......................................................................................... 10
19.7 Material Tank M110 ............................................................................................................. 11
19.8 Everything of D210, R310 and B410 ................................................................................... 14
19.9 Launch of the OS................................................................................................................. 16
19.10 M120 and M130 ................................................................................................................... 17
19.11 Level bar objects in tanks .................................................................................................... 18
19.12 Auto Mode for the material tanks......................................................................................... 19
19.13 First Sequence for R310...................................................................................................... 21
19.14 Complete Sequence for R310 ............................................................................................. 23
19.15 Holding and resuming.......................................................................................................... 27
19.16 SFC Objects......................................................................................................................... 28
19.17 Users.................................................................................................................................... 29
19.18 OS Project editor – Area buttons … .................................................................................... 30
19.19 Time Synchronization and Lifebeat Monitoring ................................................................... 31
19.20 PCS 7 compliant picture change ......................................................................................... 32
19.21 Project Editor - Message Display......................................................................................... 33
19.22 Alarms.................................................................................................................................. 34
19.23 Smart Alarm Hiding.............................................................................................................. 35
19.24 Status display for stirring motors ......................................................................................... 36
19.25 Archiving the Material Tanks levels ..................................................................................... 37
19.26 Interlock for the dose valves ................................................................................................ 38
19.27 Local operation of M316 ...................................................................................................... 39
19.28 Valves as a Process Tag ..................................................................................................... 40
19.29 Model of the reactor............................................................................................................. 41
19.30 AS-AS communication......................................................................................................... 43
19.31 Configuration in Run ............................................................................................................ 45
SIMATIC PCS 7 – Exercises

PCS 7 System Course
19.32 Simulation LIA134................................................................................................................ 46

19.33 New function block............................................................................................................... 47
19.34 New block icon..................................................................................................................... 49

PCS 7 System Course
19 Tasks
19.1 Multiproject
Goal
A Multiproject as the starting point for implementing the training application.
Main steps
1. In SIMATIC Managers Customize Dialog Window, check the storage locations for
projects / multiprojects, libraries and archives.
Your instructor may supply you with the current local information.
2. Check the settings for the Wizards and Language.
3. Create the Multiproject using the PCS 7 Wizard “New Project“.

4. Select 4 levels for the Plant hierarchy.

Do not have any CFC or SFS chart inserted.
5. At OS object, select the PCS 7 OS as a Single station system.
6. As a directory name for the Multiproject, select Teamxx, where xx is your team number.
7. After clicking the Finish button in the final page of the wizard, the Multiproject will be
created. This may take a few minutes.
8. After the creation, select the Multiproject icon in the Component view and activate Show
All Levels (View menu).
9. Rename the following objects (xx fits your team number):

• Multiproject: Teamxx
• Project: Projxx
• SIMATIC 400 station: ASxx
• S7 Program folder of the AS: ASxx
• SIMATIC PC Station: the computer name of your station
• OS: OSxx (takes a few seconds to adapt the new name)
• Library: Libxx
• S7 Program folder of the Lib: Libxx
10. Retrieve the Course Library_V.. to the storage location for libraries.
Do not open this library in its own window, but have it inserted into the Multiproject.
11. To the project, insert an Industrial Ethernet named “PlantBus“.

PCS 7 System Course
12. For the project and both libraries, select two different languages as the languages for
Display Devices, with English as the Default Language.

PCS 7 System Course
19.2 Station Configuration PC
Goal
A configured SIMATIC PC Station, both in the project and the Station Configurator.
Main steps
1. In the Properties of the SIMATIC PC Station, check the setting to have the Computer
name identical to PC Station name.
2. From the Start menu, activate:

Siemens Automation -> SIMATIC -> SIMATIC NET -> Configuration
Console
and identify in the Modules section the MAC and IP addresses (including Subnet
mask) and the module types to be used (note them on paper).
3. In the Component view, open the PC Station configuration. You will find the “WinCC
Appl.“ positioned at Index 2, because of the creation by the PCS 7 Wizard “New
Project“.
4. From the Catalog, insert the proper CP Industrial Ethernet into the Index 1 position.
Supply the module with the proper addresses (both MAC and IP) and have it
connected to the Ethernet network of your project.
5. For these changes, activate Save and Compile and close the HW Config editor.
6. From the SIMATIC PC Station icon, activate using its context menu the options for
configuring and download the station configuration.
7. Check the result in the Station Configuration Editor

PCS 7 System Course
19.3 Station Configuration AS
Goal
A configured SIMATIC S7-400 Station, to be used as the AS in the training application.
 The real available training equipment is dependent of the training site.

This task description assumes the use of the SITRAIN medium level equipment for
PCS 7 training purposes.
Main Steps
1. Ask your instructor for all relevant details concerning the training equipment for making
the proper configuration settings.
2. Check if the power supply for the AS is switched on.
3. Define all components and modules of your station.
4. Make all required properties settings for the CPU and network modules.
5. For all IO modules: use the default address ranges.
6. For the analog in and output modules: select signal range 0 … 10 V.
7. For the 8 channel analog input module: have channel 5-8 deactivated.
8. Select PIP 2 for OB32 and all analog IO modules
9. Select PIP 3 for OB33 and all digital IO modules.
10. After Save and Compile and Download, switch to the Online Diagnostics to check if
the configuration is OK.

PCS 7 System Course
19.4 Plant Hierarchy
Goal
The starting point of the Plant Hierarchy
Main steps
1. Create or rename existing hierarchy folders to achieve the following structure:
Johnsson
Material Tanks
M110
Buffer Tanks
B410
Reactors
R-General
R310
Dose
Mix
Heat
Level 1
Level 2 Drain
Level 3
Level 4
2. Check if the assignment of all hierarchy folders is to the Charts folder of your AS.
3. Insert another folder on the 2nd level called “Signal Box”.
4. Using HW Config of the AS, insert symbolic names for the 3 signals of the relay:
• output: “Relay”
• input: “Relay_NC” (normally closed)
• input: “Relay_NO” (normally opened)

PCS 7 System Course
19.5 Drivers for the Signal Box
Goal
5 charts containing drivers for the I/O signals of the Signal Box.
 The real available training equipment is dependent of the training site.

This task description assumes the use of the SITRAIN standard equipment for PCS 7
training purposes and the Signal Box.
Main steps
1. Assign symbols to some channels of the 4 modules of the ET 200M rack connected to
Profibus DP. Find the signals to use now in the table below. Check the 2 function
diagrams of the digital and analog signals to identify the used channels.
Type Symbol Comment

Digital in T1 Pushbutton T1 on the Signal Box
T2 Pushbutton T2 on the Signal Box
S1 Switch S1 on the Signal Box
Digital out H1 Lamp H1 on the Signal Box
H2 Lamp H2 on the Signal Box
Analog in AI1 Potentiometer 1 on the Signal Box
AI2 Potentiometer 2 on the Signal Box
Analog out AO1 Analog output 1 on the Signal Box
AO2 Analog output 2 on the Signal Box
2. Open the Plant hierarchy folder “SignalBox”.
3. In the “Signal Box” folder insert a new chart called “Relay”. Have it in the OB33 run
sequence.
4. Insert 1 digital output driver and 2 digital input drivers, and connect them to the
addresses of the Relay:
• Output: „Relay“
• Input: „Relay_NC“ (normally closed)
• Input „Relay_NO“ (normally opened)
5. In the “Signal Box” folder insert 2 new charts, installed in the run sequence of OB32,
called “SignalBoxAnIn” and “SignalBoxAnOu”. Have the proper Analog input and
output drivers inserted and connect them to the symbols you created earlier.

PCS 7 System Course
6. Make 2 charts, installed in the run sequence of OB33, called “SignalBoxDiIn” and
“SignalBoxDiOu”. Have the proper Digital input and output drivers inserted and connect
them to the symbols you created earlier.
7. Perform the Compile and Download procedure for the first time. You can only select
the Entire program at the Scope and Download mode.
8. In the CFC editor, set the Laboratory Mode in the Debug menu, and set the Watch
cycle to 1 second.
9. Activate test mode and check the update of the configured driver inputs and outputs:
• inputs of the Signal Box: just watch the outputs PV_Out of the drivers;
• output of the Signal Box: parameterize the inputs PV_In of the output drivers.
10. Make a Dynamic Display named “Digitals Signal Box” and add the signal from the
digital drivers:
• PV_Out from the Input drivers
• PV_In from the output drivers.
Watch the input values in the table and modify the values to the outputs.
11. In the chart “SignalBoxAnIn”, add some blocks to calculate the average of the two
analog inputs. Also insert a Lag block (family Math), connect its input In to the average
value and set the LagTime parameter to 10.
12. Make another Compile and Download, but from now on with the scope / Download
mode called Changes only.
13. Test the new functions.
14. Make a Trend Display named “Analogs Signal Box”. Use the first 4 channels for AI1,
AI2, the average value and the output of the Lag block. Connect channel 5 … 8 to the
signals of S1 … S4.
Watch the behavior of the Trend Display.
15. Connect the average and its lag version to the 2 analog outputs for displaying at the
Signal Box and have it tested.

PCS 7 System Course
19.6 Installing the process simulation
Goal
A running process simulation of the Johnsson plant.
After this task the functions for the plant can be configured.
Main steps
1. Copy the chart “@Johnsson” from the Course Library Charts folder to the Charts folder
of your AS.
2. Open both symbol tables of the Course Library and of your AS.
3. In the Symbol Editor, arrange both windows next to each other.
4. Sort the contents of the library table for the Address column in ascending order.
5. Copy the lines with the input and output addresses (by highlighting the line numbers)
and paste them in the symbol table of your AS (put your pointer in the Symbol field of
the last line before your perform the Paste).
You should have copied 127 lines.
6. Close both tables (save).
7. In the plant hierarchy, copy the chart “Relay” and paste it into the folder
Johnsson\Reactors\R310\Dose.
8. Rename the chart to “Temp_V311”.
9. Open the chart, and change the 3 addresses to the addresses of V311.
10. For the output driver, parameterize input Mode with the value 16#8000FFFE
11. For both input drivers, parameterize input Mode with the value 16#8000FFFF
12. Make a new Trend Display called “Temp_V311” and connect the 3 values from the
drivers.
13. Test the function in the chart, using the Trend Display and watch the behavior of the
control signal and both feedback signals.

PCS 7 System Course
19.7 Material Tank M110
Goal
Configure the AS functions for Material Tank M110. Measuring and monitoring the level
of the tank and controlling and monitoring the valve and the pump, based on templates
from the library.
Main steps
1. In SIMATIC Manager, open the Library “PCS 7 AP Library V80” and select its chart
folder “Templates” (Component View).
2. Copy 4 charts into the “Process tag types” folder of your Master Data Library (Plant
View):
• AnalogMonitoring
• MotorLean
• PIDControlLean
• ValveLean
3. Close the Library window
4. Before the charts will be copied into our application, we will first adapt some settings:
Chart\block I/O for Visible and Change parameter

Watched value
AnalogMonitoring\MonAnalog PV_AH_Act
PV_AH_En
PV_AH_Lim
PV_AL_Act
PV_AL_En
PV_AL_Lim
PV_WH_Act
PV_WH_En
PV_WH_Lim
PV_WL_Act
PV_WL_En
PV_WL_Lim

PCS 7 System Course
MotorLean\Motor AutAct Feature.Bit4 = 1

AutModLi MonTiDynamic = 7.0
ManAct
ModLiOp
MonDynErr
MonStaErr
RstOp
Run
StartAut
StartMan
Stop
StopMan
PIDControlLean\PID AutAct Feature.Bit4 = 1
AutModLi
AutModOp
Man
ManAct
ManModOp
ModLiOp
PV_AH_Lim
PV_AL_Lim
PV_WH_Lim
PV_WL_Lim
Rbk
SP_Ext
SP_ExtAct
SP_ExtLi
SP_ExtOp
SP_Int
SP_IntOp
SP_LiOp
ValveLean\Valve AutAct Feature.Bit4 = 1
AutModLi MonTiDynamic = 7.0
Closed
Closing
CloseMan
LockAct
ManAct
ModLiOp
MonDynErr
MonStaErr
OpenAut
Opened
OpenMan
Opening
RstOp
5. Close all charts and use the Plant view of your Multiproject to copy 3 charts:

PCS 7 System Course
• from the Master Data Library, folder “Process tag types”

• to the plant hierarchy of your project, folder “Johnsson\Material Tanks\M110
• charts: AnalogMonitoring, MotorLean, ValveLean
6. For each of the 3 charts, open the “Properties CFC chart” dialog, and active the “Clear”
button in the “Process tag type” tab.
7. Rename the charts:
AnalogMonitoring LIA114
MotorLean P113
ValveLean V112
8. Configure in chart LIA114:

• PV_In: Interconnection to Address: “LT114”
• Scale: 0 … 6000
• Unit of Measure: 1088 (kg)
9. Configure in chart P113:

• addresses: “P113_O” as the feedback, “P113” as the control output
10. Configure in chart V112:

• addresses: “V112_O” and “V112_C” as feedbacks, “V112” as the control output
11. Make a temporary chart “tempV211” in the hierarchy folder

“Johnsson\Reactors\R310\Dose”.
12. In this temporary chart, install a copy of the output driver from chart V112.
13. Connect this driver to address “V211” and set the value 1 for both inputs SimOn and
SimPV_In.
14. Bring the changes to the real AS (Compile and Download).
15. Open only the 3 charts of M110, have their windows arranged next to each other, and
active Test mode.
16. The content of the tank should start with 5700 kg, but when the valve is opened and
the pump in running, the content should decrease with about 3 kg per second.
17. Finish this task with the pump stopped and the valve closed.

PCS 7 System Course
19.8 Everything of D210, R310 and B410
Goal
All devices of D210, R310 and B410 monitored and controlled in manual mode.
Main steps
1. Delete the temporary chart “tempV211”.
2. In your Master Data Library, open the Process tag type “PIDControlLean” to make
some adjustments.
3. Copy the Pcs7AnIn driver into the lower left corner of sheet 1 of this chart, and rename
it to Rbk.
4. At input PV_In, change the Interconnection to Address to the text “Read back”.
5. Connect the output PV_out of the new driver to the input Rbk of the controller block.
6. From both Or04 block, have the input In2 set to visible, and make proper connections
to the new driver.
7. Close this chart now and copy it from the Master data Library to the plant hierarchy:
Johnsson\Reactors\R310\Heat and rename it to TICA315.
8. For this chart, open the “Properties CFC chart” dialog, and active the “Clear” button in
the “Process tag type” tab.
9. Open the chart TIC315 now and use the I/O addresses:
• input for PV: TT315
• input for Rbk: CV315_X
• output: CV315
10. Set the controllers input TI to a value of 30.
11. Scale the process value from 0 … 200.
12. Close the chart TIC315.

PCS 7 System Course
13. Open in SIMATIC Manager the Process Object View, and use the object tree on the left
window pane and the tab General on the right to make copies of the 3 charts in the
M110 folder:
Source chart Target path and new chart name

LIA114 …R310\Dose\LIA214
…R310\Drain\LIA314
…Buffer Tanks\B410\LIA414
V112 …R310\Dose\V211 (and delete the chart tempV211)
…R310\Dose\V212
…R310\Dose\V213
…R310\Dose\V311
…R310\Drain\V312
…Buffer Tanks\B410\V411
P113 …R310\Mix\M316
…R310\Drain\P313
14. In the right window pane, select the Signals tab, and devide the table in such a way,
that you have the columns Chart and Signal next to each other.
15. Change in the column Signal the I/O addresses to the proper ones. Do this by selecting
the folders B410, Dose, Drain and Mix one by one.
16. In the right window pane, select the tab Blocks.
17. In the left window pane (tree) select the Johnsson folder.
18. Sort the table to the content of the Block icon column in ascending order.
19. Scroll to the bottom of the table, and fill in the 15 empty Block icon fields the value 2.
20. Filter the content of the table by column Block icon with value 2 and sort using the
column Chart in ascending order.
21. There should be 15 lines now.
22. In SIMATIC Manager, also open the symbol table of your AS and sort the content to
symbols in ascending order.
23. Copy from the symbol table the content of the Comment field of some I/O addresses
and paste it in the Block Comment field of the Process Object View, to have a
representive name for the control and monitoring blocks. These names we will discover
later on the OS.
24. For the 3 new LIA… charts, adjust the Scale input of the driver to the measuring
range.
25. Don’t forget to perform at last a Optimize Run Sequence, before you send the changes
to the AS.
26. Test every single device. For the TICA315 use a Trend Display “TICA315”.

PCS 7 System Course
19.9 Launch of the OS
Goal
A running OS based on the AS functions configured up to now.
Main steps
1. Make an OS-AS connection based on MAC address.
2. Name the connection ASxx (xx = your team number)
3. Have the connection downloaded to both stations.
4. In the Component view, select the OS and if present, delete any existing picture.
5. Copy the 6 supplied (background) pictures from the Course Library (OSLib) to the Plant
Hierarchy / regarded folders (just by drag & drop).
6. In hierarchy folder Signal Box, insert a new picture and rename it to SignalBox.
7. For the 3 pictures in the third hierarchy level, the option Derive the block icons
from … in the property dialog window is to be checked.
8. Point to one of the hierarchy folders and select the option Plant Hierarchy >
Settings …
9. Select only level 3 to be included in the HID.
10. Select level 2 as the OS area.
11. Compile the OS
12. In the three 3rd level pictures, move the block icons to the proper position in the process
image.
13. Activate the OS (Runtime).
14. Get familiar to the general way of operation.

PCS 7 System Course
19.10 M120 and M130
Goal
AS and OS function for M120 and M130 based on a copy of M110.
Main steps
1. De-activate the OS.
2. In the Process Object View make two copies of the folder (including its content) M110,
on the same hierarchy level.
3. Rename the new hierarchy folders to the proper names (in the tree).
4. Rename the new charts and pictures (tab General).
5. Change the block comments for the new operating and monitoring blocks (tab Blocks)
6. Change the I/O addresses (tab Signals)
7. Compile and Download the charts.
8. Compile the OS (select at Scope: Changes).
9. In Graphic Designer, edit the static text in the pictures M120 and M130:
10. Close the pictures and Graphics Designer and watch the pictures in Run Time.

PCS 7 System Course
19.11 Level bar objects in tanks
Goal
Properly connected Level bars in the process pictures.
Main steps
1. Open 1 of the process pictures.
2. Have the toolbar “Tag” displayed.
3. In the left window pane, open the tree of “ES Variables”, up to the folders, chart and
block containing the value to be connected.
4. In the right window pane, find the tag element named “PV_Out#Value” and drag & drop
it into the bar element.
5. Do the same for all other bars in all other pictures.

PCS 7 System Course
19.12 Auto Mode for the material tanks
Goal
One common switch on the OS to set the outlet valves and outlet pumps of the material
tanks in Auto mode.
When in Auto Mode, then the outlet valve and outlet pump of a material tank must follow
up the demand for the material: opening and starting when a dose valve has opened.
Main steps
1. In hierarchy folder Material Tanks, make a new hierarchy folder M-General. In this new
folder insert a new chart M-General and a new picture M-General.
2. In the chart insert a block of type OpDi01, named AutoMode.
3. Connect the output Out of this operator block to both the inputs ModLiOp and
AutModLi of the VlvL and MotL blocks of M110, M120 and M130.
4. In each of the 3 charts for the Material tank outlet valve, insert a new OR04 block, and
connect its output Out to the input OpenAut of the VlvL.
5. Complete all connections, as summarized in the diagram on the next page.

PCS 7 System Course
V211
V112 OpenAut
VlvL Opened OR04 P113
VlvL Opened StartAut
M-General
ModLiOp MotL
OpDi01 AutModLi
Out
V212
V122
VlvL OR04 P123
VlvL
MotL
V213
V132
VlvL OR04 P133
VlvL
MotL
6. For the 3 new OR04 blocks, insert textual connections as a preparation for the valves
of the other 3 dose tanks that will appear later.
7. Compile and Download to the AS, compile the OS, and test.

PCS 7 System Course
19.13 First Sequence for R310
Goal
A first short sequence for dosing one material and to learn proper switching between
manual and automatic mode.
Main steps
1. In the folder R310, create a CFC “R310-Gen” and insert 2 digital logic blocks Or04.
Rename these blocks to “ModLiOp” and “AutModLi”.
2. Connect the output Out of the OR block “ModLiOp” to control the input ModLiOp of
V211. Make a similar connection for OR block “AutModLi” to the input AutModLi of the
same valve:
3. In the folder R310, create an SFC “R310” and build a sequence due to the following
description:
Start
blind empty condition
ModLiOp
Automatic Switch dose valve material 1 to Auto mode.
AutModLi
AutomaticModes Dose valve material 1 is in Auto mode V211
Dose 1 Open dose valve material 1 V211
Level 1 Amount of material 1 reached 50 kg LIA214
Close 1 Close dose valve material 1 V211
Dose closed 1 Get the feedback from dose valve material1 closed V211
Manual Switch dose valve material 1 to Manual mode AutModLi
ManualMode Dose valve material 1 is in Manual mode V211
END Let the operator control the mode ModLiOp
 Tip: Use the „In1“ of the regarding OR block for the interconnection to the SFC, to
control the operating mode of the valve by the commands ModLiOp and ManModLi.
This allows you to add more blocks to be controlled by these commands without
changing the SFC in a later stage.

PCS 7 System Course
4. Compile and download the AS.
5. Use OS Runtime to open V 411 in manual model. Have valve and pump of M110
(V112, P113) in Auto mode.
6. Test the new sequence by manual operation. Check, that the operator has full access to
switch the operating mode in the faceplate after complete run of the sequence.
 Tip: Resize the window of the SFC and CFC and activate test mode. Switch to the
OS runtime and after to the test mode windows of CFC and SFC to observe all
windows at the same time.

PCS 7 System Course
19.14 Complete Sequence for R310
Goal
Complete the sequence R310 for dosing and heating a mixture of the 3 materials
Main steps
1. Use the output Out of the blocks „ModLiOp“ and „AutModLi“ in the chart R310-gen to
control the Auto mode of devices of D210 and R310, in a similar way as you have
already done for valve V211. Make connections to the inputs ModLiOp and AutModLi
for the following charts:
• V212
• V213
• V311
• M316
• V312
• P313
• TICA315
2. For TICA315, also use the inputs SP_LiOp and SP_ExtLi to bring the PID controller in
external setpoint mode. For these interconnections do not use the OR blocks in R310-
gen. Instead of this, you have to insert additional command lines in the sequence R310.
3. Open the SFC “R310” and extend the already existing sequence due to the following
description:

PCS 7 System Course
Start
blind empty condition
ModLiOp
Switch all devices to Auto mode and the temperature
Automatic
controller in External mode
AutModLi
AutomaticModes All devices in Auto mode and temperature controller

in External setpoint mode
Dose closed 1 Get the feedback from dose valve material1 closed V211
Start Trans 1 Open reactor inlet valve V311
Empty 1 Dose tank is empty LIA214
Stop Trans 1 Close reactor inlet valve V311
TransClosed 1 Reactor inlet valve is closed V311
Start Stirrer Start stirring motor M316
Stirrer on Stirring motor is running M316
Dose 2 Open dose valve material2 V212
DoseClosed 2 Dose valve material 2 is closed V212

PCS 7 System Course
StartTrans2 Open reactor inlet valve V311
Empty 2 Dose tank is empty LIA214
StopTrans2 Close reactor inlet valve

V311
TransClosed2 Reactor inlet valve is closed V311
Level 3 LIA214
Amount of material 3 reached 30 kg
Closed 3 V213
Close dose valve material 3
Dose closed 3 V213

Dose valve material 3 is closed
Start trans 3 V311

Open reactor inlet valve
Empty 3 LIA214
Dose tank empty ?
Stop trans 3 Close reactor inlet valve

V311
Trans Closed 3 Reactor inlet valve is closed? V311
Start heat Set point temperatur controller to 70 °C TICA315
Temp = 70 °C Temperature is above 68 °C TICA315
Stop heat Set point temperature controller to 0 °C TICA315
Valve Closed Temperature control valve is closed TICA315
Open Outlet Open Outlet valve and stop stirring motor V312 / M316
VOpened Outlet valve opened V312
StartOutlet Start outlet pumpe P313
Empty Reactor is empty LIA314

PCS 7 System Course
Stop Outlet Stop outlet pump P313
Poff Outlet pump stopped P313
Close Outlet Close outlet valve V312
V Closed Outlet valve is closed V312
Manual Switch all devices to Manual mode AutModLi
ManualMode All devices in Manual mode
END Let the operator control the mode ModLiOp
5. Test the new sequence in SFC/CFC test mode and observe the process in OS runtime
at the same time.

PCS 7 System Course
19.15 Holding and resuming
Goal
Preventing material flow when the sequence is held
Main steps
1. In the chart R310-Gen, insert a block type ReacComd from the Course Library.
2. Change the block name to Storage.
3. Set the value of input EN to 0.
4. To the SFC of R310, add a Holding and a Resuming sequence, to prevent product
flow when the RUN sequencer is held.
5. At holding, store the commands in the input OpenAut of the valve blocks of V211,
V212, V213, V311, V312 and input StartAut of the block of pump P313 into the inputs
of the ReacComd block, before the commands are reset (set to 0).
6. At resuming, restore the commands stored in the ReacComd inputs into the OpenAut
or StartAut input of the 6 devices.
7. Have everything tested.

PCS 7 System Course
19.16 SFC Objects
Goal
Have additional ways to monitor and control the progress of the sequence
Main steps
1. Compile the OS with activated SFC visualization.
2. In the picture of R310, make a button with the text “SFC”.
3. Use the dynamic wizard “Configure SFC button” twice to assign an action to the left
mouse click and to the right mouse click:
• left mouse click: to pop up the Overview windows of the SFC
• right mouse click: to pop up the Section windows of the SFC
4. In the Reactors overview picture, insert a PCS7 SFC MultiChart Control to have an
overview of the 4 Sequences (only 1 SFC is existing now, the other 3 will be added
later).

PCS 7 System Course
19.17 Users
Goal
5 different operators with an increasing number of authorizations
Main steps
1. Make a user group with the name “Operators” and give the group the authorization for
function 1-5.
2. Make 5 users for operators, with settings due to the table below. The number in the
headers represents the No. of the Function.
User name password 1 2 3 4 5 6 7 1002 1100 1101 1102

(Login) PC HPC HHPC Adv1 Adv2
Operator1 111111 v v v v V
Operator2 222222 v v v v V V
Operator3 333333 v v v v V V V
Operator4 444444 v v v v V V V V
Operator5 555555 v v v v V V V V v
3. In OS Runtime, Log in as Operator1 and check if parameter values of the level

monitoring can be changed.
4. Repeat this for Operator2.

PCS 7 System Course
19.18 OS Project editor – Area buttons …
Goal
Optimized setting regarding area buttons, picture tree navigator and number of
faceplates
Main steps
1. Open the OS Project Editor, select in tab Layout Overview extended configuration
and reduce the number of areas (buttons in overview) to 6 (2 Horizontal, 3 Vertical).
2. In tab Area, make the following arrangement of the area buttons:
Material Tanks Signal Box

Reactors
Buffer Tanks
3. In tab Runtime window, Picture Tree Navigator: uncheck “Close window on picture
selection”.
4. In tab Runtime window, Faceplates: increase “Maximum number per monitor” to 6.
5. Close the Project Editor with the OK button.
 Pictures en objects will be updated. This process may take some time.
6. Check the changes on the OS.

PCS 7 System Course
19.19 Time Synchronization and Lifebeat Monitoring
Goal
Have all station clocks running synchronized, based on one master.
Monitoring of the AS lifebeat by the OS.
Main steps
1. Make the required settings for OS and AS to operate with Time Synchronization.
2. Make the required settings on the OS to monitor the accessibility of the AS.

PCS 7 System Course
19.20 PCS 7 compliant picture change
Goal
Configure a button in a process picture to allow an operator to perform change to
another process picture.
Main steps
1. In picture R310, insert two windows objects “Button“.
2. Rename these buttons to “Reactors” and „B410 not PCS7 like“.
3. Select the button “B410 not PCS7 like” and open the configuration dialog.
4. Enter the name of the target picture “B410.pdl” in the field “Change picture on Mouse
Click”. Alternatively, you can select the desired picture via the button right of this field.
5. Save the picture and test the function in Run Time. Have a look at the Picture
navigation button in the key bar.
6. Select the button “Reactors” and start the Dynamic Wizard “Picture exchange in
workspace“ (in tab “Picture Function”).
7. Do all the settings and finish the wizard.
8. Save the picture and test the function in Run Time. See the difference between both
solutions.

PCS 7 System Course
19.21 Project Editor - Message Display
Goal
Group Displays in the pictures
Main steps
1. In the OS Project Editor, select the Message display tab.
2. At Sorting of the message pages select Latest message at the top.
3. At Group display hierarchy, select Create / update group displays.
4. Close the OS Project Editor.
5. Edit the pictures “Material Tanks”, “Reactors” and “Buffer Tanks”:

• set the Display property of the group displays to yes
• move the group displays to the proper position
6. Test the group displays in Run Time.

PCS 7 System Course
19.22 Alarms
Goal
Proper settings for the limit values and applying an external alarm.
Main steps
1. Adjust the alarm limits of all level monitors and the temperature controller to proper
values, using OS Run Time.
2. In CFC test mode, disable the PV Low Warning and PV Low Alarm of the D210 and
R310 level monitoring, and the Rbk Low Warning and Rbk High Warning of TICA315.
3. After that, there should not be any W and A in the Overview area.
4. Perform a Read Back to save the latest OS changes in your charts.
5. Apply External Message 1, of LIA314 connected to switch 1 of the Signal Box.
6. In the PCS7 Message Configuration dialog window, edit the event text to:
“….. Switch 1 activated”.
7. Test the message by activating the switch.

PCS 7 System Course
19.23 Smart Alarm Hiding
Goal
Smart Alarm Hiding
Main steps
1. De-active the OS.
2. At the Shared Declarations of your project, add 3 values to the Enumeration “Operating
state”:
• 0 = normal
• 1 = hiding1
• 2 = hiding2
3. In the chart M-General, install a copy of an STRep block (family Maint), and assign the
Block group “MT”
4. Connect the first 2 inputs to 2 switches of the Signal Box (T3 and T4).
5. In SIMATIC Managers Process Object View, select in the tree the Material Tanks
folder.
6. In tab Blocks, find the blocks for level monitoring of the 3 Material tanks, and in the
Block group field enter “MT”.
7. In the Messages tab, filter by column Block group: “MT” and Event: “*- High”. You
should have 9 lines left now.
8. Check the column “hiding1” for the High messages of M110 and M130, and “hiding2”
for M120 and M130.
10. Compile the OS and activate again.
11. Test using the push buttons T3 and T4.

PCS 7 System Course
19.24 Status display for stirring motors
Goal
Status display of the stirring motors in the overview picture of the reactor
Main steps
1. Use the help on the MotL block of the chart M316 to find the status bits of status2 of
the block, and fill it up in the table below:
Status bit Parameter

Motor is stopped
Motor is running
Error in motor
2. In the picture Reactors, insert a Status Display (extended), position it near the first
reactor and resize it to 35 x 35 pixel.
3. Open the properties, and at the Properties tab, theme Miscellaneous, connect to the
attribute Status1: R310/M316/Motor.Status2.
4. Design the Status Display (extended), based on the table below:
Bit 2 Bit 1 Bit 0 Index Picture Flash picture

22 = 4 21 = 2 20 = 1
error running stopped
0 0 0 0 apl_bi_MotL_off.emf apl_bi_MotL_onM.emf
0 0 1 1 apl_bi_MotL_off.emf
0 1 0 2 apl_bi_MotL_onM.emf
0 1 1 3 apl_bi_MotL_err.emf
5. Test the Status Display (extended) and if OK, then duplicate 3 times to have the
representation for the other 3 stirring motors.

PCS 7 System Course
19.25 Archiving the Material Tanks levels
Goal
A Trend of the material tanks, to be accessed by a button in the Reactors picture
Main steps
1. In OS Runtime, have the sequence of R310 running in Cyclic operation mode (check if
all required devices are in Auto mode and if V411 is opened).
 This will make the levels “alive”.
2. Activate archiving of the 3 levels in CFC (Monitoring block, input PV).
3. Compile the OS.
4. In the OS, create a new Picture “TrendMT” (in the Component View only).
5. In the picture, install a WinCC Online Trend Control to display the 3 levels for the last
60 minutes, full screen.
6. In the Reactors overview picture, make a button “Trend MT” to change to the trend
picture, using the Dynamic Wizard “Picture exchange in workspace”.

PCS 7 System Course
19.26 Interlock for the dose valves
Goal
Preventing to have more than one dose valve opened
Main steps
1. Every dose valve should be able to open only, when both other dose valves are
closed. Make connections to the Interlock block with the proper conditions.
2. Disconnect for every dose valve the Permit block and the Protect block.
3. At the In01.Value and In02.Value parameter, fill in proper short texts in the Text0 and
Text1 field (for example: “V212 Not Closed” and “V212 Closed”).
4. Test the new interlock functions.

PCS 7 System Course
19.27 Local operation of M316
Goal
Local operation of M316 using the Signal Box
Main steps
1. In the control block for M316, make the following inputs visible:
• LocalSetting
• LocalLi
• StartLocal
• StopLocal
2. Set the parameter LocalSetting to 1 (switching to Local mode by local operation, and
control via CFC block).
3. Make the following connections from the inputs of the motor control block to the signals
of the Signal Box:
• LocalLi = S1 (switch)
• StartLocal = S2 (switch)
• StopLocal = not S2 (switch)
4. Compile and download the AS and test the function while watching the block icon and
faceplate on the OS.
5. Change the connections:

• StartLocal = T1 (push button)
• StopLocal = T2 (push button)
and test again.
6. Change LocalSetting to 3 (switching to Local mode by faceplate) and test again.

PCS 7 System Course
19.28 Valves as a Process Tag
Goal
New (temporary) charts for controlling the 5 valves of D220 and R320, based on a
Process Tag Type
Main steps
1. Open the current Process Tag Type “ValveLean” from the Master Data Library.
2. Change the textual interconnection at input In01 of the Interlock block to “Interlock01”.
3. Add a textual interconnection at input In02 of the Interlock block with the content
“Ïnterlock02”.
4. Close the chart.
5. For the import file only use these 6 Process tag connectors:
Process tag connector Block I/O name
FBC FbkClose PV_In
FBO FbkOpen PV_in
IL1 Interlock In01 !
IL2 Interlock In02 !
OUTOC Output PV_Out
VMON-TDYN Valve MonTiDynamic
6. As the import file name, use the default name and in the dialog window for defining the
columns for the column group, check the Textual interconnection in the Parameters tab.
7. Fill in the relevant data to generate the charts of V221, V222, V223, V321 and V322.
8. Fill in textual interconnection for interlocking the 3 dose valves to each other.

PCS 7 System Course
19.29 Model of the reactor
Goal
All controlling and monitoring functions for D220/R320, D230/R330 and D240/R340,
based on a model
Main steps
1. Deactivate the OS runtime and close the WinCC explorer.
2. Delete the hierarchy folder R320, including the 5 V… charts.
3. Create a model of the reactor, including dose tank, starting from the hierarchy folder
R310.
4. For the I/O points, select the signals from the I/O, and the parameter Scale.High of
the driver for monitoring the reactor level. Use the sorting function of the regarding
column.
• PV_In of Input driver blocks as IEA signal. Note that they have common the I/O
comment „Input value“.
• PV_Out of output driver blocks as IEA signal. Note that they have common the I/O
comment „Output value“.
• Scale.High of the analog input driver for monitoring the reactor level.
5. Make an import to create all functions in AS and OS for the other 3 reactors with dose
tanks.
6. After completing the import, use the Process Object View to:
• rename the new pictures
• change the comments to the OS relevant blocks
7. Compile and download the AS, and compile the OS.
8. Edit the new pictures (in every case the static texts).
 Because of the appearance of the 2nd, 3rd en 4th reactor, you can complete some of
the existing pictures and charts:
9. Connect the tags of the bars of D220, D230, D240, R320, R330 and R340 in picture
Reactors.
10. Extend the MultiChart control in picture Reactors with the 3 new SFCs.
11. Make visible and position the new Group Displays in picture Reactors.
12. Check the feedback signals of the 3 x 3 new dose valves to the control logic of the
valves of every Material tank (textual interconnections should be able to close now).

PCS 7 System Course
13. Use the chart reference to find typical errors like still open textual interconnections
14. Find the charts containing the PIDConL block. Open the charts using the context menu
option “Go to Point of Use”.
15. The M316 was configured for a Local mode to be switched by 2 buttons. Find the
process tags M326, M336, M346, and remove there the Local mode configuration.

PCS 7 System Course
19.30 AS-AS communication
Goal
Exchanging data between two AS stations
 This task contains 2 parts. You can perform one or both.

The first part is using the implicit connection. Therefore you need two stations in your
project. For running both stations you have to activate PLCSIM.
For the second part you need cooperation with another team, using communication
blocks and a real Ethernet network connection.
Part 1: implicit, using PLCSIM
1. De-activate the OS, close WinCC Explorer, and all other tools and make an archive of
your Multiproject.
2. Start PLCSIM and select in the PLCSIM toolbar the PLCSIM(ISO) connection.
3. In your project, insert a second SIMATIC 400 Station.
4. Rename the station to AS_AS_Com.
5. Open the HW-Config and insert the following components:

• Rack UR1
• PS 407/10A
• CPU416-2DP
• CP 443-1 (connected to Ethernet, MAC address 08-00-06-00-00-66)
6. Save and compile and download to PLCSIM.
7. Create a second instance of PLCSIM and download the original AS as well (HW Config
and charts).
8. Open the Plant View and insert a new hierarchy folder in level 2. Rename the folder to
AS_AS_com.
9. Change the AS assignment to the AS_AS_com.
10. Insert a new chart: AS_AS_com
11. Open in CFC the chart LIA214 of your original AS, and the chart AS_AS_com of the
new (simulated) CPU and arrange them vertically.
12. Insert in the new chart AS_AS_com a block Add04 (take care to use in both charts the
same OB).
13. Connect the Output PV_Out of the MonAnl of the LIA 214 to the input In1 of the
Add04 (just by mouse clicks).

PCS 7 System Course
14. Acknowledge the message, compile and download both AS stations.
15. Change to NetPro, compile both AS stations and download the new connection of both
AS stations.
16. Test the communication, by using the simulation mode of the input driver.
17. When ready with this part of the task, make “reverse” engineering to return to the real
AS situation.
Part 2: communication blocks and cooperation with another team
18. Create a connection to the AS of the team next to you. As a connection partner select
“Unspecified”.
19. At Address Details of the partner, enter the same values as your partner has in his
local area.
20. For downloading the connection, select your connection in the connection table, and
select the menu PLC – Download to Current Project – Selected Connections.
21. In the Reactors\R-General folder, create a chart “ASCommunication” and insert a

SEND_R and REC_R. Make agreement with the other team about the IDs to be used.
22. Test the communication, by entering values in CFCs test mode at the SEND_R block.
23. When ready with this part of the task, you may have the connection running for the
remaining time of the course.

PCS 7 System Course
19.31 Configuration in Run
Goal
Modification of the configuration on Profibus during operation, without stop of the CPU
 The possibility to practice with hardware changes depends of the available equipment
on the training site.
Ask your instructor what can be used for this purpose.
Main steps
1. In your AS station configuration, activate the CiR capability of the Profibus network.
2. Perform a Save and compile and Download (STOP mode required).
3. Add / change properties of a Profibus station. A new station must have a higher
address then the highest existing address.
4. Check the CiR consistency.
5. Download in Run.
6. Save and compile the latest changes of the station configuration.

PCS 7 System Course
19.32 Simulation LIA134
Goal
Testing the high warnings of LIA134
 Background:
The Johnsson process simulation will “refill” the material tanks when the content is
below 5%. A tank will be filled up to 95%. When alarms limits are set above this 95%,
the violation can not be tested.
That is why we use simulation now: block internal at the MonAnl and external via the
input driver.
Main steps
Block internal via the OS
1. On the OS, log in as a user with the Highest process controlling authorization.
2. Open the picture of M130 and open the faceplate of the level monitoring.
3. In the Limit values view, be sure the H-limits are set above 3800.
4. Open the Parameter view and activate the (block internal) simulation.
5. Open the Default view, and change the process value to a level above the H warning.
6. Check if the High Warning message is released.
7. In the Parameter view, de-activate the (block internal) simulation.
External via driver in CFC on the ES
8. Open the chart LIA134 and resize the window of CFC to only the Pcs7AnIn driver, so
you can overlap the OS picture of M130, keeping an eye on the level monitoring (block
icon, faceplate and bar graphic).
9. At the drivers input SimPV_In enter a value, higher then the H warning limit.
10. Switch on the simulation using the input SimOn.
11. Check if the High Warning message is released.
12. Switch off the simulation at the driver.

PCS 7 System Course
19.33 New function block
Goal
Adjustable parameters for the SFC
 A simple Function block has to participate in the sequence of R310.

You do not have to develop and enter the Source code for this block. It is already
available in the Course Library. You start making a copy of it.
OR Amount SFC “R310”
EN IDLE
COMPLETED
Percent1 Kg1
Percent2 Kg2
Program code
TotalKg Kg3
SP_In SP_Out
OKE ENSTART
Main steps
1. From the Sources folder of the Course Library, copy the SCL Source “Amount” into the
Sources folder of your Master Data Library.
2. Open this SCL Source, and from the SCL editors Options menu, open the Symbol
Table to enter the Block type name and FB number. As a comment enter “Parameters
for SFC”.
3. Have the source compiled.
4. In chart R310-General, insert an instance of the new block, and rename it to ParaSFC
5. Enter the following values at the inputs:

• Percent1 = 20
• Percent2 = 30
• TotalKg = 200
• SP_In = 60

PCS 7 System Course
6. Put on the left of the Amount block an OR04 block.
7. Make interconnections between the CFC chart and the External view of the SFC.
8. The dotted lines represent the access by the SFC steps and transitions to be
configured. They will replace the constant values.
9. The Amount output “SP_Out” is to be used in a step as the setpoint for the temperature
controller. The successor transition must check if the temperature has approached the
setpoint up to a difference of 2 degrees. Insert an additional library block in the CFC
chart to support this transition.
10. Have the block and the interaction with the SFC tested.
 Below the SCL Source of the Function block “Amount”:

PCS 7 System Course
19.34 New block icon
Goal
A block icon for the Amount block
 A simple Block icon is created, for display purposes only.

A faceplate call is not made.
Main steps
1. In the Graphics Designer, create a new picture “@PCS7TypicalsTraining.pdl”.
2. Create a new block icon, as @Amount/1 with the layout and objects as shown below:
tag
Kg1 0.000
Kg2 0.000
Kg3 0.000
SP_Out 0.000
3. After completing, make an OS compilation to see the block icon appearing in the R310
picture.
4. In chart R320-Gen, install another Amount block, with similar interaction with the SFC.
5. Make every required compilation and download, and test.


ST Pcs7sys

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ST Pcs7sys

Uploaded by

Copyright:

Available Formats

1 Introduction

2 PCS 7 Documentation and Support

Requirements and functional process

System design and component

6 Station and network configuration

SIMATIC PCS 7 7 Connection to the process

10 Basics Automatic Mode Control

Course from: to:

15 Final steps of configuration

Copyright © Siemens AG 2011. All rights, including

SITRAIN courses on the internet: www.siemens.com/sitrain

Course folder Version: V8.0 (for PCS 7 Version 8.0) 20

SIMATIC PCS 7 – Introduction

SIMATIC PCS 7 – Introduction

1.1 Learning targets (this chapter)

The participant will learn about

1.2 Concept of this course

General workflow of a PCS 7 project This course

Hardware and Software

Including In brief, is main subject to the

SIMATIC PCS 7 – Introduction

1.3 Road map of this course

First week Second week

Setting up the automation system and operator station

Connection to the process Locking functions and operating modes

Basics of automation with APL

1.4 Additional documentation

Below you find the way the available documentation is represented

SIMATIC PCS 7 – Introduction

1.5 Training equipment

1.6 Access to systems of other students

SIMATIC PCS 7 – Introduction

SIMATIC PCS 7 – Documentation and Online Support

SIMATIC PCS 7 –Documentation and Online Support

2 PCS 7 Documentation and Online Support

The participant will learn about

2.2 Documents available by PCS 7 Installation

Pathways to installed manuals

SIMATIC PCS 7 – Documentation and Online Support

Manuals on SIMATIC PCS 7 DVD

2.2.2 Delivered Readme Files

Pathways to installed Readme files

Reason to have attention to the Readme files

SIMATIC PCS 7 –Documentation and Online Support

2.2.3 PCS 7 help system

Implementation of the PCS 7 help system

SIMATIC PCS 7 – Documentation and Online Support

Access to PCS 7 System documentation by online help

2.2.4 Template for a plant-specific process control manual for operators

 „PCS 7 - Operating Instructions Operator Station Process Control.doc “

SIMATIC PCS 7 –Documentation and Online Support

2.3 Additional sources of information

Subject of the manual

Links to the Compendium

SIMATIC PCS 7 – Documentation and Online Support

2.3.2 PCS 7 on Tour (PoT)

Subject of the manual

SIMATIC PCS 7 –Documentation and Online Support

2.3.3 PCS 7 Catalogs

Industry Online Support New Website:

SIMATIC PCS 7 Standard catalog ST PCS 7 for V8

SIMATIC PCS 7 – Documentation and Online Support

2.3.4 PCS 7 in internet