SIMATIC PCS 7 Training Overview
SIMATIC PCS 7 Training Overview
4. Creating a multiproject
The reproduction, transmission or use of this document or its contents is not per-
mitted without express written authorization. Violation of this rule can lead to
claims for damages.
© Siemens 2023. All rights reserved, in particular the right to register and be
granted patents and/or other commercial property rights.
Published by: Siemens AG, Digital Industries, Customer Services, P.O. Box 31 80,
91050 Erlangen, Germany
1. You will become familiar with the system concept and • You obtain information from descriptive slides and
the basic plant structure of PCS 7. course documentation on PCS 7.
2. You will learn how to process digital and analog signals • You configure the automation hardware and
in PCS 7. digital/analog signals with PCS 7 and test the function
using the signal box to which the distributed I/O is
connected.
3. You will learn how to work with PCS 7 engineering tools • You configure the fictitious "Johnsson" plant step-by-
based on examples and exercises. step and you commission it virtually.
Day 1 2 3 4 5
Week 2
Course roadmap
Archiving system
Alarm and process value archiving,
WinCC Controls
Day 6 7 8 9 10
Example:
References
See [103] PCS 7 V9.1 Engineering System, section 9.1 for an overview of the configuration
steps.
Overview of the accompanying documentation
Manual
The following figure shows you how to access the accompanying documentation collection:
You will create the automation program modularly so that an extension is possible at a later
time.
Control room
Material tanks
Dosing
Reactors
Buffer tanks
The designations of the process tags and signals, as well as limits and switchover times, can be
taken from the P&ID flow chart.
The plant to be configured consists of 3 material tanks, which are filled with liquids. The liquids
are fed via one valve and one feed pump each to four possible dosing tanks, which are used for
quantity control. Three inlet valves, one for each liquid, are assigned to each dosing tank. After
dosing, the liquids pass through one transfer valve each into one of the four reactors.
The liquids are mixed and temperature-controlled in the reactors. The reaction products are
transferred to one of the two buffer tanks via a drain valve and a feed pump. The two buffer
tanks are used to temporarily store the products before they are transferred to the shipping
area.
1.6 Schematic
Schematic structure
structure of of antraining
an example example training environment
environment
SCALANCE XC208
AS x
Controller
CPU 410-5H
IM 152-1 ET 200iSP
Fieldbus PB (PROFIBUS DP) (PROFIBUS)
1.7 Appendix
1.7.1 Digital inputs (DI)
Operation level
Terminal bus
PROFINET, redundant
PROFIBUS DP ET 200SP HA
PROFIBUS PA
Operation level
In most plants, you find the operator control level in the control room. From here, the process is
centrally monitored and controlled with a PC architecture specifically designed for this purpose.
The engineering of the overall process control system also takes place centrally from this level -
in most cases, however, on special computers in rooms only accessible to personnel
designated for that purpose.
Server level
The server level is optional. It is required only after the process control system reaches a certain
size. The servers are usually located in the immediate vicinity of the control room. In most
cases, the servers themselves naturally have display screens. However, these are not displayed
via the hierarchy representations in order to highlight, that the process itself is controlled only
from the operator stations in the operation levels.
Control levels
Just as with the servers, the controllers are in the immediate vicinity of the operator stations in a
marked off area.
Field level
The field level is the closest to the process to be controlled. It contains the sensors and
actuators required for operator control and monitoring. There is a wide range of options for
connecting to the control level.
Process plants
Central operation andusually have a central control room. Detailed operator control and monitoring of
archiving
the entire process as well as individual parts of the plant is possible from there.
Central archiving
EX
Process Historian
• Scalable high-performance archiving system in SIMATIC PCS 7
• No restriction regarding single stations, servers or server pairs that can be archived
• May be combined with Information Server for the generation of reports
Due to the size of many process plants, central diagnostics plays an important role. The
distances from the control room to the actuators and sensors at the field level may be several
hundred meters in some cases.
For this reason,
Central parameter the processdiagnostics
assignment, control systemand
mustmaintenance
enable communication from the control room
through all levels down to the lowest field level.
• Intelligent I/O
Terminal bus
• Device calibrations
PCS 7 OS server Engineering Station /
Maintenance Station
Plant bus Diagnostics of...
PCS 7 AS • PC stations
S7-410-5H
• Network components
PROFINET, redundant
• Servers
PROFIBUS DP Routing ET 200SP HA
• Controllers
Y switch
ET 200M
4..20 mA/HART
• Distributed I/O
• Field devices
Integrated drives ET 200M
PROFINET, fiber-optics
SIMOCODE Readback of...
SINAMICS
ET 200iSP
MTA
• Local parameter assignments
4..20 mA/HART
CFU PA
4..20 mA/HART
• Actual states
EX • Programs
PROFIBUS PA
Depending on the size of the process plant, specially equipped computer work stations can
even be provided for maintenance and diagnostics purposes.
Routing
Routing is the transfer of data beyond network boundaries. You can send information from a
transmitter to a recipient across several networks.
The data sent by data record routing includes the parameter assignments of the participating
communication devices and device-specific information (for example, setpoint values, limit
values, etc.). The field devices themselves do not have to support data record routing, since
they do not forward the information received.
Maintenance station
When a maintenance station is configured in the SIMATIC PCS 7 process control system,
SIMATIC PDM is integrated into it and transmits parameter data, diagnostic information and
processing information.
Configuration of...
Terminal bus
• PC stations
PCS 7 OS server Engineering station
• Servers
Plant bus
• Controllers
PCS 7 AS
S7-410-5H
PROFINET, redundant
Central data management
EX
PROFIBUS PA
Central engineering of a PCS 7 plant plays a very important role. The PC stations and
controllers may be a long way apart. By networking the stations with a so-called engineering
station, practically all steps for setting up, commissioning and maintaining the control system
can be performed centrally.
The software licenses provided for the engineering system can be used to configure two system
variants for different applications areas:
• Conventional, dedicated engineering station allows a 2-hour OS test mode in addition to
engineering, but no productive operation as an operator station
• Combined engineering/operator station for small applications allows process control in
productive operation in addition to engineering for small plants
• Basis for function blocks in the user program • Control Module Types (CMTs) or process tag types as a
basis
• Takes into account the latest NAMUR recommendations
and PNO specifications. • All instances can be compared and synchronized with
the type at any time.
• Well-engineered functionality as well as visually
attractive, easy-to-use user interfaces • Bulk data engineering possible via native tools or
external spreadsheet software.
• Type-instance synchronization over the entire plant
V1 V2 V3 Valve
Type (CMT)
Safety functions
Y switch
• Components with diagnostic
4..20 mA/HART
ET 200M capability
EX
PROFIBUS PA
In process plants, it is possible for extreme physical conditions to arise. Process control systems
must be able to handle these conditions and, in case of doubt, alleviate them.
For example, due to the nature of the process, high pressures or temperatures may occur. In
addition, sudden changes of physical or chemical conditions must not pose a danger to humans
or the environment.
The monitoring and control of dangerous states in a process plant are referred to as safety
functions in process control systems. These include the entire chain from the sensor via the
controller to the actuator including the communications paths used.
All components of this safety function must meet special requirements relating to self
diagnostics and error detection. The entire chain is only as strong as its weakest link.
To this end, even controllers in process control systems must be capable of monitoring their
program execution themselves after each processing cycle. To do this, a controller specifically
intended for the safety functions is used, which calculates every program cycle twice in different
ways and then analyzes both results for consistency. The results are only output in error-free
condition, and the plant remains in safety mode. An error detected in this way leads to the
triggering of the safety function: the actuator(s) assume the safe state. Due to the process,
valves are normally closed for this purpose and motors stopped (cooling circuits, for example,
are an exception to this).
Click here for more information on functional safety in the process industry.
Depending on the process, long and costly start-up procedures may be required in process
A process plant and its control system consist of electrical and mechanical parts that can cause
different types of errors.
© SiemensTo
2022 | SITRAIN
ensure | System
that individual overview
errors in the process control system itself do not lead to loss of
production, every level of the system architecture must be designed in such a way that there are
fallback strategies available.
In a car with a faulty speed indicator, a driver would theoretically have to look for a repair shop
while driving at a moderate speed.
In process plants, there must always be an alternative for the entire transmission path from the
speed sensor (installation of a second sensor) to the signal transmission (redundant
transmission path) up to the tachometer (further operator station) so that one error in this chain
does not necessarily lead to an unplanned interruption of the journey.
Regardless of the options provided by a process control system in this regard, the actual plant
configuration naturally depends on the effects of a possible process interruption for the
operating company and their budget.
Redundant system components cost more to purchase, but pay off very quickly depending on
the process.
References
See [511] PCS 7 V9.1 High-availability Process Control Systems - Function Manual
Manual
Modular systems of the S7-400 series Embedded systems with software controller
Type reduction
2.4.1 to a single
The modular CPU
CPU – The modular CPU 410-5H
410-5H
Characteristics
Exchangeable System
Expansion Card
Scalable performance
The performance range of the CPU 410-5H can be individually scaled according to the size and
type of the PCS 7 applications. This is done by means of the PO volume, which is determined
by the System Expansion Card (SEC). The volume extends from 100 PO to unlimited, at which
point other performance data of the CPU acts as the limiting factor.
The PO configuration limits of an SEC can be conveniently extended as of PCS 7 V8.1 by
means of CPU 410 Expansion Packs. It is not necessary to uninstall the CPU or the SEC. There
are CPU 410 Expansion Packs available for 100 POs and 500 POs. You have the following
options when ordering CPU 410 Expansion Packs:
• Online via [Link]
• Through your Siemens contact person ([Link]/automation/partner)
Communication
The CPU has two 10/100 Mbps PN/Ethernet interfaces that can be configured as follows:
– 2x PROFINET, e.g. for redundant configurations without the use of external CPs
– 1x Industrial Ethernet and 1x PROFINET, e.g. for connecting to the plant bus and the
process bus without the use of external CPs.
– 2x Industrial Ethernet, e.g. to set up the plant bus redundantly
The CPU also has a PROFIBUS interface up to 12 Mbps and allows up to 96 nodes to be
connected. The distributed process I/O can be linked either directly (PROFIBUS DP) or via a
subordinate process bus (PROFIBUS PA).
The PROFINET interfaces can be used for connecting or expanding the I/O devices. 250
devices can be connected for each PROFINET interface.
References
See [1028] Application example "Process automation with the CPU 4105H, for more
information on the CPU 410-5H"
References
See [513] PCS 7 CPU 410-5H Process Automation - System Manual, section 3 and 6 for
more information on the structure and basic functions of CPU 410-5H.
Manual
The cost-effective CPU 410E is available for applications with a small number of process
objects. For these applications, it provides the same benefits as the CPU 410-5H in terms of
• Flexibility
– Standard, high-availability and fail-safe applications
– Same hardware as CPU 410-5H
• Ruggedness: Conformal coating, extended temperature range up to 70 °C
• Secure investment: 1 PROFIBUS and 2 PROFINET interfaces, innovations via firmware
updates
References
Click here for more information about the modular automation systems CPU 410-5H and CPU
410E.
See also
[1028] Application example "Process automation with the CPU 4105H
[513] PCS 7 CPU 410-5H Process Automation - System Manual
References
See [404] SIMATIC NET Industrial Communication with PG/PC Volume 1
– Basics, section 2.3 for further information.
Manual
Use of TCP/IP: ES
Terminal bus / IE
• Special case: Plant bus and terminal bus together on one bus
• Routing via subnets OS server TCP/IP protocol
• CPU with integrated PN/IE interface
ISO protocol
• NTP for time synchronization TCP/IP protocol
• Asset management for network components on the plant bus
Plant bus / IE
• Gateways on the plant bus (third-party coupling of an AS)
Use of ISO:
• Recommended with separate plant bus and terminal bus Automation systems
• Use of H machines with FW < V5
(S7 high-availability) only with ISO
• SIMATIC procedure for time synchronization
Plant bus:
The CPs of the stations involved (AS and PC stations) must be connected to the plant bus to be
able to be loaded. For process communication on the plant bus, the ISO or TCP/IP protocol for
Industrial Ethernet can be used.
In multiple station systems, we recommend installation of a terminal bus separate from the plant
bus. Small systems (single-station systems), on the other hand, can be designed with a
common plant and terminal bus. Various functions are executed via this bus, e.g. loading the
configuration data onto the target systems, testing the system and process mode.
Topology options
The plant bus and terminal bus can be configured as follows:
• As Industrial Ethernet (10/100 Mbps and Gigabit)
• In line, tree, ring, star or redundant ring structures
References
See [121] PCS 7 Compendium Part A - Configuration Guidelines, sections 4.3.5 to 4.3.7 for
more information about when ISO or TCP/IP should be used.
Manual
In PC stations:
• Standard network adapters (BCE*)
• CP 1623 or CP 1628
As network coupler:
• Switches of the SCALANCE series
• Switches of the RUGGEDCOM series
• OSM/ESM
In the AS:
• CPU with integrated PN/IE interfaces
• CP 443-1
Each Ethernet module (CP, network adapter) has a unique MAC address. Generally, this
address is preset in the module by the vendor.
• The MAC address is permanently implemented when standard network adapters are used
for communication instead of a CP. Office networks are a typical use case. If a network
adapter is replaced, the network administration must take the new MAC address into
account.
• Automation systems in plants are equipped with CPs. The MAC address can be configured
using HW Config (Hardware Configuration) in the PCS 7 project. By loading the AS, the CP
is initialized with the new MAC address.
The advantage of the configurable MAC address is the fast maintenance, because the
replacement part (replacement CP) can be given the same MAC address as the defective CP.
Apart from the standard network adapters, CPs are also available for the PC stations. Using
such CPs can have further advantages:
• Higher number of communications partners
• Configuration of high-availability connections (redundancy)
• Time-synchronizable
Note When using several standard network adapters, the card for the terminal bus must in the first
position. Any network adapters plugged in without any functionality must be deactivated.
After PCS 7 is installed, a dialog box appears in which the network adapter for the terminal bus
must be selected.
The address of the network node is specified in the object properties of the Ethernet CP. The
following properties are specified:
• MAC address
• Also in the IP protocol: IP address/subnet mask/address of the gateway
With more recent CPs, a check box allows you to decide if you want to set the MAC address
and use the ISO protocol. You only need to enter a MAC address if you intend to use the ISO
protocol (use case: plant bus).
You do not need to activate the MAC address if you only configure types of communication that
require the TCP/IP protocol (TCP connections, ISO-over-TCP connections, UDP connections).
In this case, the field remains disabled; the address assigned to the CP in the factory is then not
overwritten when you download the configuration data (use case: terminal bus).
References
For more information, refer to:
[102] PCS 7 V9.1 PC Configuration, section 3.9
Manual
[103] PCS 7 V9.1 Engineering System, section 9.13
[121] PCS 7 Compendium Part A – Configuration Guidelines, section 4.3.5 to 4.3.7
Note The PCS 7 documentation often distinguishes between "Network connections" (relates to
physical connections) and "connections" (relates to logical SIMATIC connection types).
Scalable Flexible
redundancy architecture
Horizontal and
Simple
vertical
handling
integration
Distributed I/O devices such as remote I/O stations with their I/O modules, transmitters, drives,
valves or operator terminals communicate with the automation systems at field level through a
powerful real-time bus system.
The universal PROFIBUS covers all of the requirements of the process industry and has already
proven itself as a rugged and reliable communication medium at the field level.
Field instrumentation is connected using PROFIBUS PA, which, in addition to communication,
also enables power supply via the fieldbus. This standard can be integrated seamlessly into the
SIMATIC PCS 7 process control system either via PROFINET or PROFIBUS DP as a link.
Click here for more information on communication in the field with PROFINET.
PROFIBUS DP
• Designed for data transmission rates of up to 12 Mbps and low response times of up to 1
ms
• Based on IEC 61158 and IEC 61784 standards
• Proven ruggedness and reliability in countless projects worldwide
• Can be implemented in electrical or optical transmission technology
• Optionally redundant
• Via fieldbus isolating transformer also as intrinsically safe fieldbus up to Ex zone 1 or 21
Use of fiber-optics
Optical networks are more expensive than electrical RS 485 networks, but are insensitive to
electromagnetic interference. In addition to purely optical networks, combinations of electrical
and optical networks, in particular, have been proven in practice. These merge the advantages
of the two transmission technologies.
Optical Link Modules (OLM) permit the construction of optical and hybrid (electrical/optical)
networks in linear bus, ring or star topologies.
Suitable for the OLM, fiber-optic cables (FOC) made of glass with 2 multi-mode fibers are
preferably used for optical PROFIBUS networks indoors and outdoors.
PROFIBUS PA
The advantages of distributed field automation using the PROFIBUS PA profile include low
hardware overheads, cost-effective engineering, increased operational safety and problem-free
maintenance. These advantages are underlined by the following features:
• Modularity and uniformity from the sensor all the way to the control level enable new plant
concepts
• Implementation of intrinsically safe applications through use of the fieldbus in hazardous
areas
• Redundant PROFIBUS PA architectures (ring and line topologies with coupler redundancy)
support Flexible Modular Redundancy (FMR) from the automation system (controller) down
to a PA field device
• Safety-related and high-availability applications with low device and cabling requirements
• Reduced configuration costs through simple, central engineering of the field devices
(PROFIBUS PA and HART with SIMATIC PDM, also cross-vendor)
• Simple installation using two-wire cable for both power supply and data transmission
• Reduced commissioning costs through simplified loop check
• Low servicing costs thanks to simple wiring and wide-ranging diagnostics options
Features of PROFINET
When used as a fieldbus, PROFINET meets all the requirements of process automation, offers
many advantages compared to PROFIBUS DP and, therefore, forms a future-proof platform for
plants in the process industry.
As an open standard for fieldbus communication, PROFINET combines the advantages of the
proven PROFIBUS DP fieldbus standard with those of the Industrial Ethernet network standard.
This integrated communication forms the basis for horizontal and vertical integration and is thus
the cornerstone for the implementation of digitalization.
Line
The line is the simplest network structure. It is characterized by a network backbone to which
the individual nodes are connected directly or via individual branches in which each branch
contains only one node.
• Advantages of line topology: Simple structure, low hardware investment.
© Siemens 2022 | SITRAIN | System overview
• Disadvantages:
– No optimal resource deployment: Depending on their position, the backbone may need
to take long detours which may, in turn, lead to problematic frame delay times.
– Lack of redundancy: A cable break at any point cannot be bridged.
Star
The star topology differs from the line in that one switch functions as a "middle point" of a
network from which cables branch off to the individual terminal nodes.
• Advantages:
– Higher network performance
– Higher failure safety. If a cable to one node fails, all other network components remain
unaffected.
Tree
When multiple star topologies are connected to one another, we call this a tree topology. These
star structures are then typically arranged hierarchically. Larger networks have this structure,
especially when several topologies are combined with one another.
Ring
If the two ends of a line are closed by an additional connection, a ring topology is created. A
special redundancy mechanism ensures that the ring structure remains a logical line in normal
circumstances and therefore prevents any message frames from circulating. If a section of the
ring fails, the mechanism allows a substitute path in the ring to become available quickly:
Instead of the message traveling via the direct path, which is now interrupted, it travels the long
way round via the intact network section and reaches its recipient via "detours". The network
does not split into two segments.
System redundancy
• All S1 devices (e.g. IE/PB Link, Sinamics, etc.) can be integrated only as "one-sided
connected" IO devices in an H-CPU. The interruption of the communication connection to
the configured IO controller results in device failure.
• An S2 device has the ability to communicate with two controllers in the H-system in parallel
via an interface module. Each device with S2 capability can also be operated one-sided on
a single AS; the reverse is not possible.
• In the case of an R1 device, each of its two interface modules communicate with one IO
controller each. This means that each IM works, so to speak, as an S1 device.
Terminal bus
Concept used for providing incoming events
(e.g. signal changes in distributed I/O) with
ES OS server a very precise timestamp (accuracy up to
Central 1 ms).
system clock /
• All operator stations and automation
NTP server Plant bus
systems used in the plant must be
TIME NET synchronized with the same current time
of day
AS S7 410-5H
• The time master supplies the time of day
that serves as the basis for time stamping
• TIME NET = Separate plant bus for
PROFINET central system time
ET 200SP HA
The change of state of a process signal is an event in automation technology. If time information
is assigned to the event, this is regarded as time stamping.
In contrast, the goal of time synchronization is to ensure that the clocks of several components
match as exactly as possible.
Accurate time stamping is a concept used for providing incoming events (e.g. signal changes in
a distributed I/O) with a very precise timestamp (accuracy up to 1 ms). The time synchronization
of the nodes is a basic prerequisite for time-stamping.
The abbreviation of the term: Sequence of Events – SoE is used for symbolism.
High-precision time-stamping finds its application, for instance, in the event of a message
overload in the system. If a large number of messages occur within one second, it is only
possible to identify the first message and therefore also its cause by means of the timestamp.
For unrestricted use in process automation, IO devices must support at least the following
functionalities:
• Simple S2 system redundancy
• Media Redundancy Protocol (MRP)
PROFINET IO – Symbols and description
• Configuration in Run (CiR)
Siemens uses the PA ready symbol to identify the IO devices which meet the requirements of
process automation with regard to availability and changes during operation.
Symbol Description
Configuration in Run
Configuration in Run (CiR) is a function that enables the system and configuration to be changed during
operation.
Description
1
1. AS 410 with CPU 410-5H and CPU 410E:
the only controllers that support all PROFINET functions
(S1, S2, R1, CiR and SoE)
2. Recommended SCALANCE switches will support all
PA-ready functions in the future.
3. SIMATIC ET 200SP HA:
preferred choice for the distributed I/O
2 4. SIMATIC CFU PA:
Field distributor for process-oriented, distributed
connection of digital I/O signals and PROFIBUS PA field
devices to the PROFINET fieldbus.
3 4
5. IE/PB LINK PN IO:
Gateway between Industrial Ethernet and PROFIBUS for
seamless integration of PROFIBUS devices into the
PROFINET fieldbus.
See SIOS entry ID: PROFINET in Process Automation with SIMATIC PCS 7.
2.6.7 Distributed process I/O and field devices in hazardous gas and dust
Distributed process I/O and field devices in hazardous gas and dust
atmospheres
atmospheres
0/ 20:
Permanent, long-term or frequent presence of
explosive gas or dust atmosphere
1/ 21:
Occasional presence of explosive gas or dust
atmosphere
2/ 22:
Rare or short-term presence of explosive gas or
dust atmosphere
Fieldbuses can also be operated in potentially explosive atmospheres when physical changes
are made.
Real world
Virtual
world
emens 2022 | SITRAIN | System overview SIMIT is a simulation platform that can be used to implement both the virtual commissioning of
automation technology for systems, machines and processes, and realistic training
environments for plant operators.
This can easily be done directly at the workplace, even without available equipment and in-
depth simulation know-how.
Click here for more information about the SIMIT Simulation platform.
PROFINET/IE
PROFIBUS DP
To test the configuration and the automation program and to perform the validation, there are 2
emens 2022 | SITRAIN | System overview
configuration options:
• Deployment of a real automation system (HiL: "Hardware in the Loop")
• Deployment of a virtual automation system (SiL: "Software in the Loop")
2.8 system
Which Checkpoint
components are provided for PCS 7?
A. Engineering station ES
B. Automation system AS
C. Operator station OS
D. Fieldbus with PROFIBUS and/or PROFINET
8 Installing additional services for SIMATIC BATCH Required for PCS 7 Web Server,
Information Server, PDM Server
9 Setting the color scheme and font size
10 Creating a backup Windows or Windows 10
Supported
Supportedoperating
operatingsystems
systems
Always 64-bit
The selection of the computer name is crucial for the project configuration. You specify the
computer name when installing the operating system on the computer.
Specifications:
• The computer name starts with a letter.
• The computer name only contains letters and numbers.
• The computer name has a maximum of 15 characters (limited by the operating system).
After installation of PCS 7, the computer name must not be changed. If the computer name is
Note nevertheless changed, you need to reinstall (Restore DVD).
Windows
Windows components
components and
and settings settings
Properties
Propertiesfor
fordescription
descriptionof of
license
license
A license gives the user a legal right to use products. This right is represented by the following:
• CoL (Certificate of License): The CoL is the proof of the license. The product may only be
used by the license owner or authorized persons.
• License key: The license key is the "technical representative" of the license (also called an
"electronic license stamp").
Note You can use the PCS 7 Engineering Toolset software package for up to 14 days as a trial
version. You can activate trial mode when you first use the software (installation by the setup
program).
References
See also [100]
for more information about licensing PCS 7 software.
Manual
If the plant grows, SIMATIC PCS 7 simply grows along with it!
Solution: Concept of cumulative software licenses for configured and loadable process objects
Licensing
Licensingofofprocess
processobjects
objectsforfor
thethe
automation system
automation system
Life cycles
Maintain overview
Architecture
© Siemens 2022 | SITRAIN | Before engineering begins
Architecture
ES with
SIMATIC Management Console Central SIMATIC PCS 7 SIMATIC PCS 7 Client Station 1 SIMATIC PCS 7 Client Station N
Software administration
…
Central SIMATIC PCS 7
Management Agent Plant inventory Management Agent Management Agent
Terminal bus
Engineering station SIMATIC PCS 7 Server Station 1 SIMATIC PCS 7 Server Station N
Plant bus
AS 410
PA/FF link
ET 200M AFDiS
AFD
A process control system includes numerous heterogeneous components, each with specific
parameter assignments and settings. It is also subject to a dynamic change process due to
updates, upgrades as well as modernization measures and expansion. As the plant gets older,
it becomes more difficult to keep track of the current state of hardware and software.
[Link]
SID
Unique key for identifying a particular PCS 7 system
based on:
• End customer
• Location
• Plant
• Production unit
References
See [103] PCS 7 V9.1 Engineering System, section 4.1 System ID, for more information about
the system ID and how to create and edit a system ID.
Manual Click here to go to the registration page for Siemens process control systems.
Wizards Language
Storage Archiving
locations
Message numbers
References
See [126] PCS 7 Compendium Part F – Industrial Security, section 7.3 for more information
on managing computers and users.
Manual
Procedure
1. Open the SIMATIC Manager and select the menu command "Options > Customize..."
2. Check the path information under "Storage location for projects/multiprojects" and "Storage
location for libraries" in the "General" tab.
If you want to use a specially configured project drive instead of the default path,
"SIEMENS\STEP7\S7Proj" under "Storage location for projects/multiprojects", specify the
new path.
– "D:\PCS7_Projects"
3. In the "Language" tab, set the language and the mnemonics with which you want to work.
– National language, including mnemonics (German or English)
4. In the "Date and Time of Day" tab, set the desired format and specify if the module should
show the local time of the programming device / PC (for UTC system time -> convert to
local time).
– This is not relevant in the case of the virtual training environment.
5. In the "Wizards" tab, check if the "PCS 7" option is set.
This setting is required to be able to later start the "New Project" and "Expand Project"
PCS 7 wizards.
6. In the "Message numbers" tab, select "Always assign CPU-oriented unique message
numbers".
7. In the "Archive" tab, you can select the archiving program you want to use (for example,
PKZip) and the paths for archiving/retrieval.
– "D:\PCS7_Archive"
8. Click on the "OK" button.
Result
You have adapted the basic settings in the SIMATIC Manager to meet the requirements of the
next exercises.
4 Creating a multiproject
4.1 Learning objectives
Learning objectives
OverviewOverview
4.2 of the configuration steps
of the configuration steps for AS and OS
AS
Configuration 1 2 3 4 5 6 7
steps
OS
Configuration 1 2 3 4 5 6 7
steps
Configure the hardware Insert picture objects (SIMATIC Individual objects (Editors in
(SIMATIC Manager, Manager, plant view or process WinCC Explorer: OS Project
component view, HW Config) object view) Editor, Graphics Designer, etc.)
References
See [103] PCS 7 V9.1 Engineering System, section 9.1 for an overview of the configuration
tasks.
See [104] PCS 7 V9.1 Operator Station - Configuration Manual, sections 4.1-4.3 for an
Manual overview of configuring the OS.
Plant SIMATIC
Graphics SIMATIC S7 SIMATIC
Libraries Automation HW Config CFC / SFC Route
Designer BATCH F Systems PDM
Accelerator Control
SIMATIC Manager
General database
The PAA expands the functionality for the plant configuration and documentation. For more
efficient plant engineering, the PAA supports quotation preparation with a plant topology
diagram and the bills of materials. It also supports automatic generation of SIMATIC PCS 7 data
from electrical and functional engineering plans.
If planning tools from other manufacturers were used for electrical planning, this data can be
imported in Microsoft Excel format with the help of signal or process tag lists – same as in the
predecessor Advanced Engineering System (AdvES).
The PAA is thus the enhanced successor of the PCS 7 Advanced Engineering System. It offers
the same functionalities and, in addition, serves as a project execution and documentation tool.
References
See [103] PCS 7 V9.1 Engineering System, section 8.7 for more information on PCS 7
applications and how to use them.
Manual
Library Z • Projects contain the data for at least one station (application-
specific programmable/configurable devices).
• Libraries contain pre-defined functions for use in projects.
Stations in
4.4.2 a PCS 7in
Stations project
a PCS 7 project
© Siemens 2022 | SITRAIN | Creating a multiproject
AS AS
(S7-410-5H) (S7-413-3)
ES OS OS
(PC station (PC station (PC station with
with with WinCC) WinCC)
engineering
software)
Libraries are used for storing reusable program components. These program components can
Variousbe
library types
copied from an existing project to a library, or they are created independent of a project
directly in the library.
specific
PCS 7 Library PCS 7 libraries
(standard)
Water Library
Drive ES Library
Faceplates/
block icons
SITRANS Library
The available program functions for creating an S7 program are the same for a library as for a
© Siemens 2022 | SITRAIN | Creating a multiproject
project, with the exception of testing and debugging functions.
Libraries are organized in the same folder structure as a project:
Libraries can contain S7 programs. An S7 program contains exactly one "Blocks" folder, one
"Charts" folder, one "Sources" folder and one "Symbols" object (symbol table).
The "Sources" folder contains files with the source code of user-specific function blocks created
in various programming languages.
References
For more information on upgrading PCS 7 libraries, see
[208] PCS 7 Software update to V9.1 with utilization of new functions
Manual and [209] PCS 7 Software update to V9.1 without utilization of new functions
Library X
Project B
Project A
Multiproject
Library Y Library Z
Multiproject
At a minimum, a PCS 7 multiproject consists of one user project and one library (the master
data library), but it can also contain more than one project and library.
SIMATIC Manager shows all the components of a multiproject in a tree structure:
Multiproject – Basic elements
Multiproject
HMI components
Project library
(Green book)
• Project-specific structure:
Each individual project contains at least one AS or one OS or all AS and OS that a
configuring engineer is to work on.
• Station-specific structure:
In contrast to the project-specific structure, all AS and OS here are stored separately in their
own projects.
Distributed engineering
Multiprojects offer a major advantage: The individual projects can be distributed among different
project team members and worked on by them. The computers used can be regarded as a
distributed engineering system.
PCS 7 provides the corresponding system functions for managing, distributing and merging the
projects. The projects can remain in the multiproject or be removed for the duration of the work.
Note Distribution of the multiproject on a station-specific basis, i.e. one user project per station, is
generally recommended in PCS 7. This provides the maximum flexibility during the
configuration/commissioning phase.
This applies in particular to automation systems and the OS server. The stations for OS
clients can also be created in a user project.
References
See [103] PCS 7 V9.1 Engineering System, section 7.3 for more details.
Manual
Although use of the wizard is the recommended and most efficient method of creating a
multiproject, you must also be able to individually create components of a multiproject in
SIMATIC Manager in order, for example, to add subprojects or stations to an existing
multiproject.
The "New Project" dialog is available for creating an empty multiproject:
Creating a multiproject manually – The "New Project" dialog
"New Project" dialog
3 2
1. Open the corresponding tab to create a new user project, library or multiproject.
2. If you have selected the "User project", "Libraries" or "Multiprojects" tab, the correct object
type is preset by default. However, you can change the object type using the list field. The
new object is then added in the appropriate tab.
3. Enter the name of the new user project, library or multiproject here. Do not use lengthy
names. You can also select and edit an existing name from the list located above.
4. The storage location of the new project, library or multiproject is displayed here.
The "New Project" dialog is displayed again but without the "Multiproject" tab. An empty user
project is created in the multiproject and you can add stations to the user project in a later step.
© Siemens 2022 | SITRAIN | Creating a multiproject
The "New Project" or "Insert into Multiproject…" dialog is typically used for integrating additional
AS/ES/OS user projects in a basic multiproject that was created beforehand with the PCS 7
"New Project" wizard.
© Siemens 2022 | SITRAIN | Creating a multiproject
A project is divided into stations. These can be AS stations and/or PC stations that serve as an
ES, OS server, OS clients, etc. The stations contain the configuration information.
Note A PCS 7 multiproject should always contain a PC station as an engineering system (ES).
Never directly select "OS" or "OS (client)" from the "Insert New Object" menu in the SIMATIC
Manager. OS servers, OS clients and all other OS station types are always inserted as PC
station.
In addition, each project requires network information that will be provided via subnet objects.
Networks are configured with the HW Config and NetPro tools.
Note Subnet objects are required for configuring the plant bus and fieldbus. By contrast, information
on the terminal bus is not configured in SIMATIC Manager.
Shared declarations contain information about enumerations, units and equipment properties
that will be used in the PCS 7 project.
You can use enumerations to define textual representatives for parameter values in block and
chart I/Os with the possible data types "BOOL", "BYTE", "INT", "DINT", "WORD" and
"DWORD".
Several values can be assigned to each enumeration.
Equipment properties are parameters of a unit, e.g. jacket material, volume. The type of an
equipment property is defined as a "shared declaration". Instances of this type are individually
adapted in SIMATIC BATCH and its attributes.
The "New Project" wizard provides step-by-step support for creating a new project and includes
preassigned default settings. The PCS 7 wizard automatically creates various objects according
to the default settings or the settings you make specifically.
The following figures provide an overview of each step of the wizard for creating a new PCS 7
multiproject:
PCS 7 "New Project" wizard – Starting the wizard
1. Start the PCS 7 "New Project" wizard in SIMATIC Manager.
Click "Next" to continue step-by-step…
2. Select the CPU type you need in the project and then one of the associated bundles.
The list shows detailed information on the selected CPU.
PCS 7 "New Project" wizard
If you cannot – Selecting
find your exact CPU,ayou
bundle and
can edit theCPU MLFBconfiguration data later in the
inaccurate
HW configuration.
Youofcan
Merging / configuration use the "Find" button to search for a desired MLFB number (order number).
AS bundles: With
• Online via the catalog
"Number of communication
of Siemens Industry Mall: modules", you specify the number of PROFIBUS CPs.
[Link]
Select the desired configuration objects for AS and OS. If you want to create an OS object in
your multiproject, you must also select its type (the basic architecture).
Note All created stations (automation systems and OS stations) are placed in one user project
because the automatically created multiproject always consists of just one user project.
If this multiproject structure does not meet your requirements, it is recommended not to select
any OS object. If you do not select an OS object, the resulting multiproject contains no PC
station.
In subsequent steps, you can add additional user projects and the stations within these user
projects to the multiproject.
PCS 7 "New Project" wizard – Storage location
4. Name the new multiproject ("Directory name") and select the storage location.
When you click "Finish", the wizard creates a multiproject containing an AS station, an OS
station (if selected) and a master data library. The wizard automatically creates the necessary
project structures so that you can start immediately on the actual engineering of the plant.
Note The wizard does not automatically create the subnet object for Industrial Ethernet. You must
© Siemens 2022 | SITRAIN | Creating a multiproject
insert it yourself before you can configure the assignment of networks and addresses with
other tools:
Right-click project > Insert New Object > Industrial Ethernet
5. Open the desired PCS 7 library (in this example, the APL).
6. Enable the detailed view to have the symbolic names and other details of the blocks in the
library displayed.
7. Copy the needed blocks of all libraries used for the configuration to the block folder of the
master data library. Remember to transfer the blocks that are called as multi-instances of
other blocks into the master data library.
The PCS 7 wizard creates a basic configuration that you can expand with additional objects
based on the requirements of the plant. You can use the same dialogs that were previously
described in the section for creating a multiproject "step by step" for the expansion.
– Create in Multiproject... (other user projects or libraries)
– Insert into Multiproject... (other user projects or libraries)
– Insert New Object… (stations, subnets, shared declarations)
The PCS 7 "Expand Project" wizard is also available.
If no AS stations
are inserted
OS selection similar to
"New Project" wizard
References
For more information on expanding a multiproject, see also:
[103] PCS 7 V9.1 Engineering System, section 9.4.4 for inserting empty projects.
[121] PCS 7 Compendium Part A – Configuration Guidelines, section 5.4 for integrating other
Manual ES/OS projects.
[103] PCS 7 V9.1 Engineering System, section 7.2.2 for inserting pre-configured stations.
Mergingsubnets
Merging subnets/ cross-project
/ cross-project connections
connections
Merged and therefore cross-project networks have the same subnet type and identical S7
subnet IDs. They are represented in NetPro by the name extension "Part of: Ethernet
© Siemens 2022 | SITRAIN | Creating a multiproject
Interproject".
References
See [103] PCS 7 V9.1 Engineering System, section 9.13.8 for more information on cross-
project networking.
Readme
Synchronizing shared declarations
Synchronizing shared declarations
Best practice: Manage the shared declarations in the
master data library and export them to the projects within
the multiproject
LanguageLanguage
4.6 for display devices
for display devices
Select the languages for the display devices in an early phase of configuring.
When the OS is compiled, the texts to be displayed on the OS (for example, measured values,
operator input limits, units and operator texts of the blocks) are transferred to the OS in the
selected
© Siemens 2022 | SITRAIN languages.
| Creating a multiproject
You can select several languages from the list of available languages for your project and
define one of them as the default language.
If you have not selected the desired language, the message texts are transferred to the wrong
column of a text library and do not appear in process mode.
Note This setting always relates to individual projects and libraries within a multiproject and must be
made for each project and library individually!
• Back up data:
– At least once a day
– After every download of the AS (complete download and changes only)
– After configuration changes
– Before and after an upgrade of system components
– Before and after an update of configuration software (PCS 7)
• Keep at least the last three versions of your PCS 7 project to hand as backup copy.
• Use different backup media for archiving your data. You can then restore your data even if
one device fails.
– LAN hard disk
– USB hard disk
– MOD
– CD/DVD
• You can also back up your data on hard disks of PCs in the network. A simultaneous hard
disk failure on two PCs is very unlikely.
• If necessary, perform a readback of parameters from the CPU before archiving.
• A new subdirectory is created in the selected directory, and the entire project directory
structure of the unpacked multiproject is transferred to the new subdirectory.
The multiproject is retrieved in the destination directory with an additional subdirectory. The
system derives the name of this subdirectory from the multiproject name (this prevents an
existing
© Siemens 2022 | SITRAIN multiproject
| Creating a multiproject of the same name from being overwritten).
Task
Create a new multiproject as the starting point for the training.
• Use the PCS 7 wizard to create the multiproject.
– Bundle without additional communication modules
– Plant hierarchy with 4 levels
– No CFCs or SFCs
– OS as single station system
• Postprocessing:
– Rename objects
– Insert object for Industrial Ethernet as plant bus
– Include course library in the multiproject
– Setting the language for display devices
Procedure
1. Use the PCS 7 "New Project" wizard to create a multiproject. Follow the instructions of the
wizard and keep the following information in mind.
– For the AS, use a bundle without additional communication module CP443-5.
– Select 4 levels for the plant hierarchy.
– Do not allow any CFCs or SFCs to be inserted.
– Select a single-station system as the OS object.
– The multiproject gets the directory name Johnsson_xx (xx corresponds to the first
letters of your name).
– Click "Finish" on the last page of the wizard to create the multiproject. The software
requires a few minutes for this.
2. Show all levels of your multiproject
3. Rename the following objects:
– SIMATIC 400 station: ASxx
– S7 program folder of the AS: ASxx_program
– SIMATIC PC station: ESxx
– Project folder OS(1): OSxx (the process requires a few seconds until the change is
applied)
– S7 program folder of the master data library: LIBxx_Program
4. Retrieve the "Course Library V ..." library into the pre-defined storage location.
5. Insert the additional library into the multiproject.
6. Delete the network "MPI(1)". It is not required. You can find it in the folder of the user
project.
7. Add an object for Industrial Ethernet in the user project "Johnsson_xx_Prj", which you
rename to "Plant bus".
8. Select "English and German" as the language for display devices both for the project and
for both libraries. English is the default language.
Result
You have created a multiproject with a user project, a master data library and a course library.
The user project contains an AS and an ES/OS. The master data library is empty for the time
being, but will be filled from the standard libraries and from the course library in the course of
the training.
What are the possibilities and constraints of creating PCS 7 projects in multiple
languages
What arefrom the start? and constraints of creating PCS 7 projects in multiple languages from the
the possibilities
start?
A. If PCS 7 is installed in multiple languages, up to 5 project
languages can be selected in the SIMATIC Manager.
B. A project can only be created in one language at a time.
© Siemens 2022 | SITRAIN | Creating a multiproject
C. Depending on the selected project language, the corresponding
message texts are generated during OS compiling.
D. If a selected language is removed from a project, all display texts in
this language are lost in the project.
Terminal bus
ES
OS server OS server
Plant bus
AS AS AS
Fieldbus
Different systems are available in PCS 7 which are connected to each other in different
networks.
Loading the configuration data of the automation systems as well as the communication
between AS and OS servers takes place on the plant bus.
The configuration of PC stations as well as the communication between OS servers and
OS clients takes place on the terminal bus.
The fieldbus connects the automation systems with the distributed I/O.
ES
01 IE General [Link] Plant network
00-0C-29-5E-83-97
The term "configuring" refers to arranging racks, modules, distributed IO devices and interface
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
Parameterization
5.2.3
in the classic STEP 7 way
Parameterization in the classic STEP 7 way
Programming device
PG/PC interface:
[Link].1 [Link].1
[Link].1 [Link].1
Intel LM CP1623
ISO TCPIP
TCPIP ISO TCPIP
TCPIP
PLCs
In the conventional
© Siemens 2022 | SITRAIN | 05 Configuration way,
the "Set PG/PC interface" dialog on the programming device (PG) is
of stations and networks
used to select a defined communications module with which the PG can communicate with the
target station.
However, this "PG operation" requires a permanent manual adaptation of the "PG/PC interface"
if different target stations have to be parameterized.
The programming device and its PG/PC interface are not part of the project, it simply serves as
a "loading station".
The interface must be set individually for every connection type to be able to reach the relevant
station.
Softbus
Intel LM CP1623
ISO TCPIP ISO TCPIP
PLCs
References
See [102] PCS 7 V9.1 PC Configuration, section 5.7.7 for further details of using the SIMATIC
NET Configuration Console.
Manual
The interaction of your PC station with the various bus systems used to network the automation
systems (e.g. Industrial Ethernet, etc.) requires specialized interfaces. Each of the installed and
integrated interfaces is represented by a corresponding interface parameter set.
"PC [Link].1" is activated in the SIMATIC Manager via the following dialog: "Options >
Set PG/PC Interface...".
Subsequently, the selected interface is displayed in the status bar of the SIMATIC Manager.
[Link] Communication
SIMATIC SHELL – Selection settings
of the terminal bus
The configuration of the network cards that provide the connection to the terminal bus is
performed solely using Windows tools.
The PC stations can, however, have multiple network cards with the TCP/IP protocol. Therefore,
you must inform PCS 7 which network card is responsible for the connection to the terminal bus.
This is done by using the SIMATIC Shell application. You can perform the settings by means of
the SIMATIC NET communication settings or Windows Explorer.
Select the communications module for the connection to the terminal bus through which you will
configure the PC stations.
Configuration of stations
5.2.6 Configuration of stations
Download to
station (1:1
mapping)
Fieldbus
Plant bus
Download to
station (1:1
mapping) Distributed I/O
Configured mode:
• Cooperation of PC [Link].1 and Station Configuration Editor
• No manual switchover of the access point necessary depending on the driver/protocol
internal
PCS 7 software
PC
S7 Online
Configuration
Softbus
Station
Editor
Plant bus 2
Plant bus 1
AS1 AS2 AS3
(ISO) (TCP/IP) (ISO)
In the first step the central ES must be loaded with all the information to be able to load the
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
other stations of the PCS 7 project (AS and OS). The configuration data is checked when it is
loaded. As a requirement for successful loading, the PCS 7 project and the Station
Configuration Editor must have the same configuration information.
To this purpose, the Station Configuration Editor indicates information about the successful or
unsuccessful loading procedure.
After successful loading, the ES has access to the Industrial Ethernet network (IE) and therefore
access to all connected stations.
AS and PC stations (e.g. servers) can be reached via the CP of the ES and its network. The ES
received the information required for this via the PCS 7 project!
After successfully loading the ES, the AS hardware configuration can be downloaded to the AS
station. The configuration data is checked when it is loaded.
LEDs on the front of the CPU show status information about a successful/unsuccessful load
procedure.
Note The following explanation can serve as an aid to help you understand:
The CPU of the AS requires a partner on the PC station: a "CPU of the visualization" for the
OS. This is the task of the "WinCC application". If you follow this analogy, the WinCC
application must be placed in a "slot" of the hardware configuration of the PC station like a
CPU in the real rack of the AS.
Specialized WinCC applications are available for the different types of PC station (OS, OS
server or client, batch, etc.).
ForDie
a single-user
ErweiterungOS, einer
for example,
ES zurthe WinCC–application is required.
ES/OS
Accordingly,
Einfügenifeiner
you also want to useinyour
Applikation dieES as a single-user OS (combined ES/OS), you need
PC-Station
to expand the configuration of your ES with a WinCC application for a single-user OS.
Communication connections (for short: connections) must always be configured when data
exchange between automation systems themselves or between automation systems and a PC
station is necessary.
The figure above illustrates the relationship between communications partners:
• The "true communications partners" are the CPU of the AS on the one hand and the WinCC
application (see "CPU of the visualization") of the OS on the other. They are the end points
of a "logical connection" (→ red dots in the figure).
• The CPs are the physical interface to the network (> green line) and therefore the end points
of a "physical connection".
After the stations have been created and configured, the connections between the ES/OS
station and the automation system and between automation systems themselves can be
configured as a 1:1 image and downloaded to the stations involved just as when configuring a
station.
Note In terms of software, a connection is configured in NetPro and then downloaded to every
communications partner.
As long as the PC station is only used as an engineering station, it is adequate when it is
physically connected to the stations to be loaded. As soon as a PC has the function of an OS
single-user system or (redundant) server, a connection to the AS stations with which the OS
will communicate needs to be configured. Do not forget to download these connections on
both sides.
References
See [103] PCS 7 V9.1 Engineering System, section 9.10 for further details.
Manual
Inserting a PC station in the Adding and parameterizing Saving and compiling the
SIMATIC Manager a network interface configuration
1 2 3 4 5 6
Before starting the configuration, you require some relevant information with regard to the
network interfaces and network addresses.
In the PCS 7 project, only the network adapter for the plant bus (S7 protocol) must be
configured. At the terminal bus, communication takes place with the standard TCP/IP protocol
and does not have to be configured.
You can use a CP or a standard network card to communication on the plant bus. You can, for
Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
example, read the information of the network addresses with the software "Communication
Settings".
Determining network
[Link] addresses
Standard networkwith
card a standard network card
1. Open the "Communication Settings" program and, under "Modules", select the network card
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
Parameterization of the IP address takes place with Windows tools in the network settings.
A CP 16xx is not detected as the network adapter under Windows by default. During the
installation of SIMATIC NET, a virtual network adapter (NDIS) is set up with which the CP 16xx
is available as a Windows network card.
The CP 16xx therefore has two internal MAC or IP addresses for the following communication:
• Industrial Ethernet address for S7 communication
Determining/setting network addresses with a CP
• NDIS address for Windows communication
1 2
1. First select the CP in the communication settings and check whether the configured mode is
set at the CP.
2. In the "Address" folder, you can set the MAC address and the IP address for the Industrial
Ethernet.
The configuration of the SIMATIC Miniport CP1623 adapter takes place with Windows standard
resources in the network settings.
The TCP/IP addresses for the Industrial Ethernet and the NDIS side of a CP must not lie in
Note the same subnet.
You parameterize the settings of standard network cards or the SIMATIC Miniport CP1623
dows network parameters
adapter (NDIS address) in the network settings of Windows.
1 2
All PC stations in the project must be parameterized with the Windows computer name of the
PLC. This can deviate from the station name, if necessary.
5 4
1 3
2
In the hardware configuration, you configure the network interfaces and the software modules of
the system.
1. Rack of the PC station
2. Configured modules
3. Hardware catalog
4. Properties of the network interface
5. Saving and compiling the hardware configuration
All relevant components for the configuration can be found in the catalog. The filter "PCS7_V91"
must be activated, so that only modules which were released for PCS 7 V9.1 are displayed.
Required modules, e.g. network interfaces such as the CP1623 or IE general, can be found in
the hardware catalog and placed in the rack of the PC station.
The software modules determine the function of the PC station.
The following components have to be inserted for the combined engineering and operator
station with a single network connection:
• A network interface for Industrial Ethernet (a CP16xx or "IE general") for the plant bus. In
addition, this must be supplied with the correct addresses and network assignments.
• A WinCC application.
You can select the slot freely (see "Index" column) since this only involves a "virtual rack" of
your PC.
At the same position as in the Station Configuration Editor in HW Config, an Industrial Ethernet
interface (CP16xx or IE general) for the plant bus must be inserted and supplied with the correct
addresses and network assignments.
The Station Configuration Editor of the ES must be configured so that the ES has access to the
Industrial Ethernet network and thus also to all connected devices. This can be done manually,
orConfiguration
© Siemens 2022 | SITRAIN | 05 by transferring the configuration from the HW Config.
of stations and networks
Note In the event of connection problems, check the communication settings (see section 5.2.5).
As of PCS 7 V7.0, the function "Configure PLC" provides a convenient way to configure PC
stations. You no longer need to edit the configuration twice (in the project on the ES and in the
Station Configuration Editor of the local station).
Important requirements are, however:
• The PCS 7 software is installed on the station to be configured,
• The station to be configured must be reachable in the network via the terminal bus.
Configuring and loading the PLC
Task
Configure the SIMATIC PC station of your ES both in the project and in the Station
Configuration Editor.
Notes:
• Note the network adapter used in the PC.
Ensure that the network addresses and subnet masks are correct.
• Please use the "Communication settings" application.
Procedure
1. Deactivate the "Computer name identical with PC station name" option in the properties of
your SIMATIC PC station and insert the Windows computer name.
2. Check the communication settings for the modules used in your computer. Which goes on
the plant bus and which on the terminal bus?
See section: 5.3.2 Determining and setting network addresses
3. In the component view of the SIMATIC Manager, the hardware configuration of your PC
station is already equipped with a WinCC application.
4. From the hardware catalog, insert a used Ethernet interface module in this hardware
configuration and network it with the plant bus already created.
5. Save and compile the HW configuration.
6. Configure and download the Station Configuration Editor.
7. Check the result in the Station Configuration Editor.
Result
The PC station is configured and loaded. As an ES/OS, it can either be used for engineering or
Result later as an OS for operator control and monitoring.
5.4.2 Checkpoint
Which additional components can you insert in a PC station?
Which additional components can you insert in a PC station?
A. If the PC station was created with the wizard, I cannot
add further components.
B. For the connection to the plant bus, I can insert a
network card CP16xx or an onboard card.
C. I can insert an "Application" component.
D. If the PC station is to operate as an OS client, I only
need to insert the WinCC Appl Client locally in the
Station Configuration Editor.
Inserting a preconfigured
Configuring object properties Saving and compiling
station in the SIMATIC
of CPU and CP the configuration
Manager
1 2 3 4 5 6
Downloading configuration
Opening HW Config Inserting and configuring
to AS (if applicable, fully
distributed stations
reset AS memory)
When you create an automation system, you require a SIMATIC 400 station with a power
supply, a CPU and an Ethernet communications processor (can be omitted when you use a
CPU with an integrated Ethernet interface).
Adding an automation system
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
3
1
You have two options to create automation systems in the PCS 7 project: manually or by means
of the PCS 7 wizard.
1. Manual creation (shortcut menu command: "Insert New Object > SIMATIC 400 Station")
2. Start of the PCS 7 wizard (shortcut menu command: "Insert New Object > Preconfigured
Station...")
3. Selection and preview of a preconfigured station
During manual creation of the station, you have to configure the rack as well as all existing
modules independently. It is significantly more efficient to configure a preconfigured station.
Opening theOpening
HW Config of the
an ASHW Config
station of an AS station
1 2 3
7 6
5
The configuration of an AS station must include all really plugged in components and modules.
1
2
Versions
Many modules are available in different versions (often the firmware version).
During operation of a system in the course of maintenance, you may be forced to replace an
older module with a new one with a higher version. In this case, the old module remains
configured in HW Config and the new module is plugged in.
Consistency check when saving and compiling
Consistency check when saving and compiling
Downloading
If this check has run without errors, the blocks required for the communication of the process
data are created without the user taking any action and can then be downloaded to the AS.
The AS then has all the information necessary to check whether the real setup corresponds to
the configured setup.
Numerous precautionary measures, invisible to the user, are taken for the error situation, for
example automatic sending of suitable alarms and interrupts.
PCS 7 uses optimized default settings for a CPU so that only a few parameters have to be
adapted
Parameterizing to the project
properties of thecircumstances.
CPU
• No acknowledgment-triggered reporting
• Time synchronization
In the startup properties, this depends particularly on the enabled setting for "Warm restart".
Note As a result of this setting, the current process parameters are not reset to their initial values
on startup.
Startup properties
In PCS 7, it is important that process signals in a specific cycle are processed synchronously
with the module to be read. To achieve this, the same process image partition as the module to
be read in must be assigned to the processing cyclic interrupt OB.
Organization blocks (OBs) form the interface between the operating system and the user
program. OBs are called from the operating system and control cyclic and interrupt-driven
program execution, the startup behavior of the automation system, and the handling of errors.
Start events triggering an organization block call are known as interrupts. Cyclic interrupts
interrupt the free cyclic program processing OB1 at specified intervals. They are represented by
OB30 – OB38. OBs also decide the order of the processing of individual parts of the program.
The processing of an OB can be interrupted by calling another OB (depends on the priority).
Before each program execution cycle, the CPU loads the signal states of the input modules into
a memory, the process image input (PII). Due to the PII, the signal state of the inputs remains
constant during program execution within a cycle. During execution of the user program, a
process output image PIQ is created. On completion of a cycle, the signal states of the PIQ are
written to the output modules.
Since, however, it cannot be certain in program execution within a cyclic interrupt that the PII
was updated at the start of every cyclic interrupt or the PIQ at the end of every cyclic interrupt, it
is necessary to assign separate process image partitions to the cyclic interrupts used.
Note In process automation with PCS 7, the use of cyclic interrupts (OB 30 - 38) and the assignment
of process image partitions is important.
The process image partitions are required during configuration of the signal modules while the
configured automation functions are "integrated" in the organization blocks responsible for the
cyclic interrupts with the aid of runtime properties.
5.5.6
Configuring Configuring
the network the network connection
connection
3 4
In the hardware configuration, all modules which were also created by the wizard are contained
in the catalog. If necessary, you can add new modules to the station or exchange or delete
available modules.
For the AS, you first need to configure the network interface which is connected to the plant bus.
You have the option to use an integrated interface of the CPU or the interface of an additional
CP. Note, however, that not all interfaces support communication via the ISO protocol.
Note Depending on the interface being used, the input boxes in the properties dialog may differ.
The device name is not relevant if the module is only used for the plant bus.
The connection to the plant bus is made by selecting the relevant subnet object in the properties
of the Ethernet CP.
When a multiproject is created with the wizard, this does not contain a subnet object for
Industrial Ethernet by default. You can, however, create the required subnet in the properties of
the Ethernet interface.
On a plant bus operated with the ISO protocol, each MAC address may only be used once.
1 2
3
4 5
When using a CPU 410 in single mode as of firmware version V8.2 you obtain this selection
dialog as default when downloading.
To be able to make system modifications during operation with CiR, however, further hardware
or firmware requirements must be met.
Note In some situations, it is possible to download the hardware configuration during operation
(CPU in RUN). To find out which configuration changes you can make in RUN (CiR), refer to
the section "Final steps in configuration" of our course.
References
See [513] PCS 7 CPU 410-5H Process Automation - System Manual, section 11.1 for more
information on the hardware or firmware requirements for a system change during operation
Manual with CiR.
4. The target module is the CPU. Confirm your entries with "OK".
5. Select the desired communication protocol for the download operation (only possible when
you have enabled both TCP/IP and ISO in the properties of the Ethernet interface).
6 7
6. The dialog box appears when you want to download a configuration or when you want to
delete system data on the target module and at least one of the following online-offline
differences has been detected:
– The configured target module does not match the module that is plugged in; this can be
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
recognized by the different order number online and offline.
– The configured target module is newer than the module that is plugged in; this can be
recognized by the different operational status/firmware version online and offline.
– Configured station name, module name or configured plant designation or location
identifier are different online and offline.
7. The download begins but is interrupted if the CPU is still in Run mode…
8. Confirm with "OK" if you accept that the CPU changes to Stop. The download is then
resumed.
9. After downloading is complete, you can switch the CPU back to Run. Confirm this with the
"Yes" button.
If the configured network addresses deviate from the network addresses of the PLC, the
respective procedure for the solution you are using should be checked:
– Usage of PLCSIM as AS
– Usage of a CP443-1 for the plant bus
– Usage of a CPU-internal Ethernet interface for the plant bus
Usage
Usage of of PLCSIM
PLCSIM as AS
1. Open PLCSIM.
Usage of PLCSIM
When PLCSIM is opened, the PG/PC interface is automatically switched to
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
[Link].1. You can check the setting via "Options > Set PG/PC Interface...".
2. Open the hardware configuration and perform the download. Download in STOP and select
Usage of PLCSIM
the desired CPU.
3. In the "PLC" menu, select the "Edit Ethernet Node" command. The dialog is opened.
4. Click the "Browse" button and select your CP.
3. If you do not know the IP of your CPU or assign a new IP to the CPU, you can temporarily
modify IP addresses in the PCS 7. To do this, open the "Edit Ethernet Node" dialog via the
Usage of a CPU-internal
"PLC" menu. ClickEthernet
the "Browse"interface
button to have the accessible nodes displayed.
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
4. You can use the "Flash" function to have the selected CPU flash and thus find your CPU.
When you have found your CPU, you can modify the IP address. With the button "Assign IP
Usage of a CPU-internal
Configuration",Ethernet interface
you temporarily assign your configured IP configuration to the CPU. To
change the IP address permanently, the configuration has to be loaded.
Usage of a
5. CPU-internal Ethernet
Open the hardware interface
configuration and perform the download. Download in STOP and select
the desired CPU. In the next dialog, you select the PLC and confirm the dialog.
6. After downloading is complete, you can switch the CPU back to Run.
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
When using a virtual machine (VM) in combination with hardware, remember to set the
Note network card of the VM to Bridged.
Note In some situations, it is possible to download the hardware configuration during operation
(CPU in RUN). To find out which configuration changes you can make in RUN (CiR), refer to
the section "Final steps in configuration" of our course.
References
See [513] PCS 7 CPU 410-5H Process Automation – System Manual Section 11.1 for more
information on the hardware or firmware requirements for a system change during operation
Manual with CiR.
Note:
The softbus ("PC internal local") is not supported by PLCSIM. For this reason, a change to
the PG mode with access point "PLCSIM(TCP/IP)" takes place at this point. This is done
automatically when the PLCSIM starts.
Procedure
1. Open the HW configuration of the automation system.
2. The AS created with the PCS 7 Wizard currently consists of only one rack with power
supply, CPU and, if necessary, a CP for connection to the plant bus. Check whether the real
modules match your hardware configuration and correct your configuration, if necessary.
3. At an Ethernet interface of the AS rack, parameterize the network address and connect the
interface with the "Plant bus".
4. Open the properties for the CPU and switch to the "Cyclic Interrupts" tab.
5. Parameterize the process image partition "PIP2" at OB32.
6. Parameterize the process image partition "PIP3" at OB33.
7. Save and compile the HW configuration of the AS.
8. Download the hardware configuration into the PLC.
If the network addresses differ and the loading is not successful, the respective procedure
for the solution you are using should be checked:
– Usage of PLCSIM as AS
– Usage of a CP443-1 for the plant bus
– Usage of a CPU-internal Ethernet interface for the plant bus
See the section "Node initialization" as required.
5.6.2 is the
Where Checkpoint
scope of the IO address ranges for the used CPU
defined?
Where is the scope of the IO address ranges for the used CPU defined?
A. Each CPU has 16834 bytes in the process image input and just
as many outputs.
B. The size of the process image input and output can be found in
the properties of the CPU in the HW Config of the AS.
C. The size of the process image input and output can be found in
the device data of the corresponding CPU in the manual.
D. Each input and output that is defined in the symbol table can
be used as a HW address.
1 2 3 4 5 6
Connecting to a subnet
Setting the operating mode Download and diagnostics
3 4
5
1
1. Internal PROFIBUS interface of the CPU: created by default with a DP master system.
2. External PROFIBUS interface: is implemented by the CP 443-5 Ext. This allows additional
DP master systems to be created.
3. Subnet: Object for a PROFIBUS network. In its properties, you can specify the transmission
rate and the PROFIBUS profile. Always assign a meaningful name for the PROFIBUS
network.
4. DP master system: All devices assigned to a master form a master system along with the
master. A master system is part of a PROFIBUS subnet.
5. Distributed I/O or field devices are assigned to a DP master system with the aid of the
devices. In the case of an ET200M, this can be, for example, an interface module IM 153-2
that is used to connect to the PROFIBUS.
A PROFIBUS address (0...125) is assigned to every node (both masters and devices). The
address 126 is reserved for the delivery state.
6. Insert a new DP master system in the shortcut menu of the interface.
A segment can have up to 32 nodes (master/devices) and the total network up to 126 nodes.
The start and end of each segment must be fitted with a cable termination that is either
Note already integrated in the device (e.g. repeater) or is available as an active RS 485 terminating
element. Although repeaters are electrical participants on PROFIBUS, they do not have a
node address assigned since they do not communicate.
3
4
When assigning node addresses, only the addresses available in a subnet can be used.
• PROFIBUS interfaces which are not created as a master system can also be networked
with a subnet. In this case, the node address of this interface counts as being assigned.
Note • Regardless of the disconnection of a master system, you may need to disconnect the
networking of the PROFIBUS interface with the subnet before you can assign this
address to another node (e.g. another PROFIBUS interface).
[Link]
Setting the operating mode
Properties of the PROFIBUS interface
In the properties dialog of the PROFIBUS interface in the "Operating Mode" tab, ensure that the
DP mode "DPV1" is used.
Note With the setting DPV1, DP devices that do not support DPV1 can also be connected/operated.
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
A special situation arises when an already completely configured distributed I/O exists for a
DP master system, but the master system itself is to be moved to a different DP interface
(e.g. from an internal PROFIBUS interface of a CPU to an additional CP 443-5 Ext).
In this and
Disconnecting case, the master
installing DPsystem
mastercan be disconnected from one interface and is then an
systems
"orphaned" master system. The configuration of the distributed I/O is retained.
2 3
Orphaned master systems are entered in a list that is displayed if you want to insert a master
system for a PROFIBUS interface. In this way, you can move an existing master system
including
Disconnection of DPthe configuration
master systems of a distributed I/O it contains simply to another PROFIBUS interface.
4
1
2
5
2
1
Channel-specific settings
A channel of a module should only be activated when the relevant actuator, sensor or a
substitute resistor is connected. This avoids unnecessary diagnostics messages in the PCS 7
OS in runtime.
For some modules, channels are grouped together in channel groups, e.g. the AI8x12Bit
module with 8 channels is made up of 4 channel groups with 2 channels per channel group. In
this case, a group is activated as soon as a signal is connected to one of the two channels. In
this case as well, at least an equivalent substitute resistor must be connected.
3
2
1 5 6
Why
Why is is everyone
everyone talking
talking about
about PROFINET?
PROFINET?
• With the future demands placed on performance and data quantities, the fieldbus is reaching its limit.
• Vertical integration offers previously unutilized productivity potential through connection of the office and
automation worlds.
• Ethernet is the undisputed standard for installation technology and protocols in the office world.
In PCS 7, the diagnostics interrupt should be activated and hardware interrupts be deactivated
for all modules. Here is an example of the setting on the analog input module.
Vertical integration requires Ethernet!
During startup, the IO controller identifies all IO devices via their configured device names and
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
automatically assigns them the IP address.
The Discovery and Configuration Protocol (DCP) that is used for assigning the IP addresses to
the device names is used for the name assignment. The IP addresses are generated by the
configuration tool and downloaded to the IO controller. The automatic assignment of the
configured IP addresses takes place during system startup of the IO controller.
PRONETA
PRONETA is a free tool for analysis and configuration tasks in PROFINET networks with
special support for the ET 200 distributed I/O. The IO test enables a quick and convenient check
and documentation of the wiring of a system.
PROFINET IO system
PROFINET IO controller with • Subnet PROFINET IO device with
• Interface properties (device name, • Interface properties (device name,
• Connected nodes with IP address)
IP address) update times
• Connection to the subnet • Connection to the subnet
• Topology information
• PROFINET properties (send clock, PN IO properties
IO communication allocation) • PROFINET properties (send clock,
• Settings for media redundancy IO communication allocation)
• Settings for media redundancy
Ports with
• Topology information
Ports with
(neighbor)
• Topology information (neighbor)
• Line information
• Line information
• Transmission properties
• Transmission properties
A minimum PROFINET IO system consists of at least one IO controller, which controls one or
more IO devices.
The IO controller is a device via which the connected IO devices are addressed. This means:
The IO controller exchanges input and output signals with field devices. The IO controller is the
controller on which the automation program runs.
The IO device is a distributed field device that is assigned to one of the IO controllers, e.g.
Distributed IO, valve blocks, frequency converters, switches with integrated PROFINET IO
functionality.
PROFINET devices of the SIMATIC product family have a PROFINET interface (Ethernet
controller / interface) with one or more ports (physical connection possibilities).
PROFINET devices with multiple ports (two or more) are devices with an integrated switch.
Every PROFINET device can be uniquely identified on the network via its PROFINET interface.
For this purpose, each PROFINET interface has:
• A MAC address (factory setting)
• An IP address
• A device name
Interfaces and ports for all modules and devices in the PROFINET system are identified with the
following characters:
• Interface X In ascending order starting from number 1
• Port P In ascending order starting from number 1 (per interface)
• Ring port R
Insert a PROFINET IO
Set an IP address Configure the topology
controller
1 2 3 4 5 6
3
Necessary that the IO controller
name is communicated via the
configured topology when a device
is replaced
1. Select the PROFINET IO interface (X5 PN-IO) and open the properties.
2. Enter the desired device name on the "General" tab.
3. So that future IO devices in the PROFINET IO system can obtain their device names from
the IO controller via the configured topology and neighborhood relations, the "Support
device replacement without exchangeable medium" option must be set.
Set an IP address
Independent of the device name, every PROFINET node also requires an IP address. This is
required
Configuration forcontroller
of IO TCP/IP communication
– IP settingsin the case of diagnostics and configuration.
1
3
1. In the properties dialog of the PN IO interface of the PROFINET IO controller, click the
properties of the interface.
2. Modify the IP address of the IO controller there and connect it to a subnet.
3. With the "New..." button, you can create a new subnet, if necessary.
4. On the "PROFINET" tab, you make the settings for the send clock and the communication
Configurationallocation for PROFINET
of IO controller [Link]
– PN IO
The send clock is the time period of two consecutive intervals (IRT and RT communication) and
corresponds to the send interval for data exchange.
If there is not enough capacity for the acyclic communication, the communication allocation can
be reduced, taking the update time into account.
Result
1. In the hardware catalog, open the most recent PCS 7 profile to display the approved
PROFINET IO devices.
PROFINET IO device
© Siemens 2022 | SITRAIN – Properties
| 05 Configuration of stations and networks
2. Drag-and-drop the required IO device, e.g. ET 200SP HA, to your PROFINET IO system.
3. Open the properties of the IO device by right-clicking or double-clicking and enter a unique
device name.
4. In the properties of the Ethernet interface, enter the IP address of the PROFINET node.
Update time
An update time is automatically calculated from the existing hardware configuration, the
resulting cyclic data traffic, the module properties and the communication allocation for
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
PROFINET IO. Within this update time, new data is transmitted from the IO controller to all
IO devices with outputs in the IO system and all IO devices with inputs are queried.
The sequence of the cyclic data exchange, such as the timing of the data transmission or the
distribution of the data, is calculated automatically by PCS 7 and downloaded to the
IO controller along with the other configuration data.
You obtain a complete overview via the properties of the PROFINET IO system. Here you can
modify the update time for a selected node using the "Edit…" button.
The update time can only be set in accordance with the specified values and applies to all
devices of the IO system. PCS 7 determines the possible values from the properties (i.e. from
the GSD files) of the PROFINET devices involved.
Preset default
values
3 ms x 128 = 384 ms
You can also set the update time in the individual PNIO properties dialogs of the nodes in the
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
PROFINET IO system.
The "Fixed update time" is set to a value that is less than the fastest process image partition
update (PIP). The watchdog time is the product of the "Update time" and "Number of accepted
update cycles with missing I/O data" parameters. It should be greater than 200 ms for a ring
configuration (reconfiguration time).
Advantages
PROFINET IO systems can be topologically configured with the SIMATIC Topology Editor. This
means that you connect the interfaces and ports of the PROFINET IO nodes with each other.
Typically the AS station acts as an IO controller of the PROFINET fieldbus system. To assign
the device name, the IO controller uses the configured topology and the neighborhood
relationships determined from the IO devices.
By configuring a topology, the PROFINET IO system or the IO controller will make known the
neighbor relationships of all the PROFINET devices located in the PROFINET IO system.
If you now replace a defective device with a replacement device which at this point in time is set
to the factory settings, the IO controller can identify the replacement device without name and
then assign it the configured name and the IP address. It is then automatically included in the
user data traffic again.
The topology editor has the following functions and properties:
• Display of all PROFINET devices in the project and their ports
• Cable length and type as well as transmission time for each port
• Connection data with location information for each individual port
• Diagnostics information of PROFINET devices for each individual port
• Troubleshooting is made easier by the online/offline comparison of connection data
• Call of the diagnostics (module information) from the graphic view
• Import of the network topology
Filter
2. If you confirm with "Yes", the topology editor applies the data configured up to now.
3. For configuring the topology, the graphic configuration is recommended in PCS 7. Change
to the graphic view for this. You see both the IO controllers and the IO devices in the
screen.
4. Select both interfaces at which the PROFINET cable is plugged in and connect them
graphically.
5. The "Interconnection Properties" dialog box for the selected port now opens.
If you wish to change the default values for the cable data, either click the "Cable length"
radio
Editing topology button and select the desired value from the drop-down list or click the "Signal delay
graphically
time" radio button and enter the desired value.
As a result, a continuous line is drawn between the two devices in the screen.
Repeat this for all connections and close the Topology Editor with "OK".
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
Note The actual plugged-in hardware and the hardware configured in the topology must match.
Topology
Topology in moduleinproperties
information the module properties
The information relating to the topology can also be found and edited in HW Config in the
properties of the relevant device ports.
Note You can also create documentation of your PROFINET IO network with the "Topology
Reporter". You can use the following link to download the tool:
PROFINET in Process Automation with SIMATIC PCS 7
In order for "automatic commissioning" to be performed later, the PROFINET IO device must
first be reset to factory settings if it is not currently in delivery state.
Afterwards, all settings for the PROFINET IO controller (AS station) and the PROFINET IO
device (ET 200M) can be made directly in HW Config and then downloaded to the CPU after
being saved and compiled. The laborious assignment of a device name for the ET200M is no
longer necessary.
1. Set the PG/PC interface of the PC for the plant bus to the communication protocol that is
being used.
2. Open the dialog with the Ethernet properties using
PLC > Edit Ethernet Node…
3. With "Browse", all addresses attached to the plant bus are displayed.
4. Select the row with the addresses for the IO device. If you press the "Flash" button, the
corresponding station reacts and flashes for a set time.
5. With "Reset", the selected PROFINET IO device is reset to factory settings.
5.9Hardware
Hardware diagnostics
diagnostics and troubleshooting
and troubleshooting
Brief description of the online view in HW Config:
1. In the element bar, click the Offline <-> Online button. This allows you to switch between
the online and offline window without closing the previous window. Diagnostics symbols
show the status and operating state. Here 4 examples to illustrate:
2. The CPU operating modes Stop and Run. Run mode is active in this window.
3. No match between the configured and the actual configuration: The configured slots are
either empty or different modules were placed in them.
4. Diagnostics not possible: No online connection, or the module does not return diagnostics
information.
5. Error: The module has an error.
Possible causes: Diagnostics interrupt, I/O access error or lit error LED was detected.
1. The diagnostic events are displayed in the diagnostic buffer in the sequence in which they
occur. The first entry contains the most recent event.
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
2. When you select an event in the list, you obtain detailed information:
– Event name and event number.
– Additional information depending on the event, such as the address of the command
that caused the event and the resulting operating state change of the CPU.
– Event statuses that have come in or have already gone out.
1
1
2
1. Status of the CPU: Stop. There is a diagnostics interrupt that cannot be intercepted in the
status shown by special "error OBs" (OB 8x).
Note If there is a CPU STOP due to failure of I/O components, use the SUBNET block. When an
error OB (for example, OB 86, rack failure) is called, the SUBNET block allows only the driver
blocks that signaled the error to be processed. This reduces the processing time necessary.
Note PCS 7 provides the required blocks in libraries. The interfaces to the hardware including test
functions are implemented in these blocks.
As soon as a CFC is compiled with the option "Generate module driver", which is enabled as
default, all required error OBs are placed in the user program in the background. After such a
program has been loaded on the CPU, this is capable of intercepting I/O errors without Stop.
2. The interface module (IM) of the ET200 M station connected to the PROFIBUS DP master
system indicates an external error.
3. The configuration table of the DP device indicates a disrupted module in slot 4.
4. The module status of the disrupted module provides further information about the type of
disruption.
Task
Configure the distributed I/O and load the configuration to the PLC.
Procedure
1. The AS created with the PCS 7 Wizard currently consists of only one rack with power
supply, CPU and a CP for connection to the plant bus. Check whether the real modules
match your hardware configuration and correct your configuration, if necessary.
2. You need a fieldbus, e.g. PROFIBUS DP or a PROFINET IO, to connect distributed I/O.
Use what you find on the training device as a guide. For a PROFIBUS DP, the CPU-internal
interface X1 is used. The PROFINET is either plugged on the interface X5 or X8 on the
CPU.
3. Equip the PROFIBUS or PROFINET station according to the modules available in reality.
The best way to do this is to refer to the data sheet that you will find at your training site.
4. Use the preset standard address ranges and process image partitions. The digital signals of
the signal box start with 0, the analog ones at 512. Select PIP2 (OB32) for the analog
signals and PIP3 (OB33) for the digital signals.
5. Note the measuring ranges of the analog signal module groups and disable channels that
you do not use.
6. Activate the possible diagnostics alarms and group diagnostics with all used IO modules.
7. Make all the required settings on the CPU, such as warm restart after power-on or the
corresponding cyclic interrupts for the process image partitions.
8. Connect your AS with the plant bus.
9. Save and compile the hardware configuration.
10. Download the hardware configuration of your AS to the CPU.
Result
You have configured your AS and downloaded the HW configuration. The AS is in RUN state
and can be reached via the ES.
Where is the scope of the IO address ranges for the used CPU defined?
A. Each CPU has 16384 bytes in the process image input
and just as many outputs.
B. The size of the process image input and output can be
found in the properties of the CPU in HW Config of
the AS.
C. The size of the process image input and output can be
found in the device data of the corresponding CPU in
the manual.
D. Each input and output that is defined in the symbol
table can be used as a HW address.
Do you have to activate support of the TCP/IP protocol in the network adapters on the plant
busDo
foryou
connection of thesupport
have to activate distributed I/O to the
of the TCP/IP fieldbus
protocol in theofnetwork
the CPU via PROFINET?
adapters on the plant bus for
connection of the distributed I/O to the fieldbus of the CPU via PROFINET?
A. Yes, definitely. Both are Industrial Ethernet.
B. PROFINET is a fieldbus with TCP/IP protocol. During
operation, it is directly connected with the interfaces on
© Siemens 2022 | SITRAIN | 05 Configuration of stations and networks
the CPU.
C. Only if one of the two PROFINET interfaces is used on
the CPU.
D. If the number of the connected ET200 stations is
larger than 256.
Learning objectives
6.1 Learning objectives
Component viewhas been opened or created, its component view is displayed in the SIMATIC
After a project
Manager. All data is assigned to physical stations and components.
4
1
The names of the S7 programs are used as the name of the connection in the WinCC project
Note after the OS compiling. Therefore, you should use meaningful names (e.g. name of the
associated AS).
5. Symbol table: Each S7 program (each CPU, each AS) has a unique symbol table for
storing the relationship between symbolic names and addresses or blocks.
Note Stations and components must first be inserted before they can be edited. Subnet objects are
only displayed here. They are edited in HW Config.
In the plant view, you structure the project according to technological aspects. In doing so,
divide the automation as well as operator control and monitoring functions hierarchically into the
Plant view
hierarchy levels plant, unit or function. You name the relevant hierarchy folders based on their
technological meaning.
Level 1
Level 4 1
1 4
2 5
3 6
Prohibited special
[.][%][/][\]["]
characters
Conversion of The special characters
special characters ['][.][%][\][*][?][:]
[space]
are converted into a substitute
character $ when compiling the
OS.
Number of When the OS is compiled, texts
characters with a maximum of 255
characters are transferred.
Therefore, shorten the length of
the name for the hierarchy folder.
The position of the configured process tags (charts) in the plant hierarchy is one of the ways by
which they are identified. This results in a "Plant designation" (HID) together with the chart
name, which is later used in the OS as "origin" of a message sent by the automation system.
© Siemens 2022 | SITRAIN | Creating the plant hierarchy
The remaining setting options in this editor are for the display in the operator system and are
Note explained at the appropriate place in this documentation.
6.5 Assignments
Configuration objects such as CFCs and pictures are created in the plant view of the project.
The individual units are assigned to particular automation systems (AS) and particular operator
stations (OS), which are created in the component view.
Plant view – Assignments
The assignment can be made via the properties of the hierarchy folder. This assignment is
optionally also transferred to the lower-level hierarchy folders.
Plant
© Siemensview – Assignments
2022 | SITRAIN | Creating the plant hierarchy
Alternatively, you can also open a dialog for the assignment directly via a shortcut menu:
AS project
OS project
The figure above shows how PH folders can be assigned if the AS station and the OS station
are located in different user projects of the multiproject, for example to enable parallel
processing.
CreateTask
a starting point for the plant hierarchy.
Create the plant hierarchy:
Johnsson
Signal_box
Materials M-General
M110
Storage
B410
Reactors
R310
Dosing
Mixing
Heating
Draining
Procedure
© Siemens 2022 | SITRAIN | Creating the plant hierarchy
1. Create new hierarchy folders or rename existing ones to create the following plant
hierarchy according to the task requirements:
– Observe the syntax rules for naming hierarchy folders.
2. Check the assignment in the SIMATIC Manager.
– The program that is created in all these hierarchy folders should only run in the AS that
is in the multiproject at the given time.
Result
The plant hierarchy reflects the structure of the Johnsson plant. The creation of the programs for
the individual process tags is now performed in this structure.
6.7.2 Checkpoint
Compare the arrangement of the folders on your ES with the arrangement as
listed in the exercise!
Compare the arrangement of the folders on your ES with the arrangement as listed in the exercise!
A. The hierarchy folders are arranged alphabetically in the plant
view.
B. The hierarchy folders in the plant view are arranged exactly as
entered.
C. The sorting of hierarchy folders depends on the number of
process objects in each branch.
D. The final order of the plant hierarchy folders does not
necessarily have to correspond to the order in which they were
entered.
7.2 Overview
Each unit in a plant is represented by a chart with blocks in the ES and a block icon/faceplate
on the OS. Pre-defined block types are kept in a library.
1 4
Blocks
In the modularly constructed user program of process control software, control functions are
implemented with the help of technological blocks. The inner workings of such a block remain
hidden to the user.
DB x DB y DB z
In the CFC editor, the automation program is created in the form of charts or CFCs. Blocks are
placed, configured and interconnected in the CFC. The libraries contain ready-made blocks for
a variety of tasks, e.g. mathematical functions, logical operations or blocks for controlling
technical equipment such as drives or valves. Many functions also include a block icon and a
faceplate for visualization at the operator station.
Sheet 1 Sheet 4
Sheets
Sheet 2
Sheet 5
Chart partitions,
at least one chart
partition, starting
with A, max. 26 to Z
Sheet 3 Sheet 6
• You can change between the sheet view and the overview by clicking the button in the
toolbar or by double-clicking on the white background in a sheet.
• Alternatively, you can expand the list box.
• The sheet bars contain cross-references to interconnections outside the sheet.
• Use a text box to enter comments. You can insert a text box in the chart like a block.
1 3 5 7
2 4 6 8
Using the catalog in the CFC, you have access to all blocks and installed libraries in use. The
catalog contains the 3 tabs: Blocks, charts and libraries.
Via the tab bar of the catalog, you can choose between 4 different catalog views.
• The "Blocks" tab displays all blocks that are already used in the block folder of the current
S7 program. The blocks are sorted in block families.
• The "Charts" tab shows all configured CFCs and they can be opened from there.
• The "Libraries" tab shows all libraries installed on the system and also the master data
library of the project. You can also insert blocks from these libraries into the open chart.
References
See [302] PCS 7 V9.0 CFC for SIMATIC S7 - Function Manual, section 8.2.2 for more details.
Manual
7.3.3 Templates
Templates are prepared charts for device control functions. They can be found in the chart
folder (called "Templates") of a PCS 7 library.
To insert function blocks into the charts, you can drag-and-drop the blocks from the catalog into
the CFC. For function blocks (FB), this procedure reserves the number of an instance data
block. The instance data block is used to store the data of the block instance inserted in the
chart. Functions (FC) like the logical OR have no instance data block and therefore no memory.
PCS 7 AP Library
Dosage
Drives
Interlock
MotL Intlc MotL
VlvL DB64 DB65
Generator
Interlock
Run
Intlk02
Or
Intlk04
Math
Logic OR logic
And
Or
When you drag blocks from the catalog into the CFC, the blocks are assigned to an OB
according to the runtime group of the chart currently being edited (in the figure below for
example in OB35).
Block comment
Insert position of the
runtime group (CFC) in
the OB
• Block name (name of the block instance): CFC assigns the block a number as a name
when it appears in the chart. The name can be changed in the dialog of the block
properties.
Note The block name must not exceed 16 characters and is displayed in the block header.
Prohibited characters are: / \ ." %.
Block properties
Block parameter
Messages
Additional calls of the
block
• The name box has a simple number entered in it. This is normally replaced by a more
meaningful name.
• The comment box contains a brief description. The content can be changed.
• Some boxes in this dialog do not apply to block types. These objects are then grayed out.
Block I/Os
A table lists the properties of all inputs and outputs of the block:
1 2
3
7.4.4 Interconnections
Blocks can be linked by interconnecting the I/Os. Only one output can be connected to one or
more inputs of the same data type. To do this, you can draw lines between the I/Os or select an
output and an input one after the other.
Textual interconnection
Textual interconnections are interconnections to a target that does not yet exist at the time of
configuration.
To be able to configure a textual interconnection, the name of the subsequent CFC, the block
name and the I/O name must be known. An open textual interconnection is visualized by a
yellow triangle.
If the target I/O is available, the textual interconnection can be closed.
Hidden interconnections
If interconnected block I/Os are hidden, this is indicated by a light blue triangle in the block
header.
The graphic representation of blocks in the CFC editor was revised. The use of different colors
at the block I/Os and their labeling provide a better overview of changes since loading the last
time.
• Gray value at the I/O • Color black for
means: • Runtime group in the block
header
Preset default value
• Parameter in the block
means:
Block or values were downloaded to
• Color change for the AS
• Runtime group in
the block header
• All parameter
labels in the block • Color change for parameter labeling
means: • Blue value at the I/O means:
New block instance means: Changed parameter assignment or
since the last download Parameter assignment by user interconnection since the last
download
After creating the required functions in the charts, these are sent to the CPU in 2 steps:
Block
library
Block instances CFCs
CFC editor
Block types Parameter
Compile
Code generation
SCL source
Compilation
S7 user program
Download
S7 target system
Machine code
7.5.2 Compile
The CFC program is compiled in two steps. In the first step, a temporary source program, "SCL
source", is created and this is directly further compiled into an executable program in the form of
blocks in MC7 machine code and stored offline in the block container.
With the Scope option, you can determine whether the entire program is to be compiled or only
changes are compiled. When compiling the AS program for the first time, only the "Entire
program" option is available.
1
2
7.5.3 Download
Programs created in CFC must also always be downloaded to the target system from within
CFC since only the download function of CFC guarantees the consistency of the configuration
data with the target system data.
Exception:
In the SIMATIC Manager, the CFC download function is also available in the following
situations:
• With a chart folder selected with the menu command PLC > Download
• With a (multi)project or a station selected with the menu command PLC > Compile and
Download Objects.
If you click the "Download" button without first compiling the program, a message window opens
and after confirming it you can compile and download in one session:
1
2
References
See [302] PCS 7 V9.0 CFC for SIMATIC S7 - Function Manual, sections 13.3 and 13.4 for
further details on how the system supports avoidance of a CPU STOP.
Manual
In PCS 7, it is possible to download individual CFCs from the CFC folder of the S7 program, or
individual plant sections from the plant hierarchy.
Selection of CFC to be
selectively downloaded
• CFC changed
• CFC loaded
• CFC compiled
• Dependent CFC
With the selective downloading of individual CFCs, you can select which of the configured
changes are transferred to the target system and activated. This makes it possible to configure
several units on a target system at the same time because precisely the changes to a unit can
be compiled, downloaded and tested.
References
See [302] PCS 7 V9.0 CFC for SIMATIC S7 - Function Manual. section 13.6 for further details
on "Selective Download".
Manual
For test mode, you can still make some settings in the CFC editor in the "Test" menu.
• Test settings: Here you determine how often the values at the visible I/Os are updated.
Minimum cycle is 1 second.
• Process mode: Here, the communication of the online dynamization is limited. The
monitoring of blocks and I/Os must be explicitly enabled.
• Laboratory Mode: All I/Os registered for monitoring are displayed immediately after test
mode is started. Online dynamization is not limited and may have a considerable influence
on the communication load.
Use the "Test mode" button to start the connection to the AS.
The "Watch on" and "Watch off" buttons are only needed in process mode.
You can log on and off individual I/Os for monitoring. To do this, open the properties of an I/O
and set the "For test" parameter.
Alternatively, you can also click on the I/O during test mode while holding down the CTRL key or
right-click on the I/O to have the value displayed continuously.
You can change values at non-switched inputs online. Note, however, that you can then directly
influence productive operation.
If a value is not displayed in test mode, use the "Tooltip" function to display the value in a field.
You have the option of configuring a dynamic display to analyze process values.
In this window, the values of I/Os from different CFCs of a CPU can be displayed, monitored
and changed. The relevant CFC does not need to be open for this.
You can open the editor with the menu command "View > Dynamic Display".
To add values to the display, drag-and-drop individual I/Os into the table and select whether the
complete structure is to be monitored or only a single element within it.
You can create and manage several value tables.
The trend display offers you the possibility to display process values graphically.
You open the display with the menu command "View > Trend Display". Again, you can create
and manage several trend displays. A maximum of 12 channels, i.e. 12 trends, are available to
you for each trend display.
Drag-and-drop I/Os to free channels and configure the limits of the channel. You can also set
the displayed time range.
Recording of values must be started explicitly in addition to test mode.
Task
Configure a logical function in CFC.
Procedure
1. Create a new hierarchy folder "Demo" (level 1) in the project.
2. Create the "Logic" CFC in this folder.
3. Insert the following blocks from the "PCS 7 AP Library V91" library into the chart:
– "LogicDI > And04"; Name "And"
– "LogicDI > Or04"; Name "Or"
– "LogicDI > FlipFlop"; Name "SR" I/O "Mode" = 0
– "LogicDI > FlipFlop"; Name "RS" I/O "Mode" = 1
4. Interconnect the blocks as shown in the figure. Ensure that the blocks are in the correct run
sequence.
5. Move the chart to OB33 (execution every 500ms).
6. Compile and download the program in PLCSIM.
7. Start test mode in CFC.
8. Test the function by changing the values at the inputs of the OR and AND blocks.
Result
In test mode, you can observe the behavior of the differently configured FlipFlops.
7.7.2 Checkpoints
To understand how the program of an automation system is organized, you need to get an
overview of how a CPU works.
The CFC and its blocks are called by organization blocks from the operating system of the CPU.
Organization blocks are processed depending on a certain event and its priority. Higher-priority
OB interrupts the processing of lower-priority OB.
• OB1 is permanently called cyclically with lowest priority, if no other OB is being executed.
• In PCS 7, the AS program is mainly configured in the cyclic interrupt OBs. These interrupts
are called cyclically at an interval of between 10 ms and 5 sec.
• The startup OBs are called once when the CPU starts up. Blocks with certain startup
characteristics are automatically inserted there.
• The error OBs are called on corresponding hardware errors.
When the CPU is started, the startup OB100 is called once at the beginning with high priority.
The program in OB32 is executed cyclically at 1 second intervals.
OB1 is then called until it is the turn of another OB with higher priority.
OB1 - Cyclic
OB32
OB32 -- Interval
Interval 1s
1s
OB100
OB100 -- CPU
CPU startup
startup
Our most important group of OBs are the cyclic interrupts OB30…OB38. They represent cyclic
execution on a defined time base.
OB10 OB20
... 17 ... 23
OB1 OB30
... 38
S7
OS
OB121, OB40
122 ... 47
OB100, OB80
101 ... 87
Inserting a PCS 7 block in one of these cyclic interrupt OBs achieves a defined time response of
the block.
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
bit memory are reset. All data blocks and their contents are retained.
CAUTION Do not perform a cold restart when restarting the CPU; the default is a
warm restart.
If a cold start takes place for a CPU restart, important process data is lost.
Default setting for PCS 7 and standard application: Restart = warm restart
In some situations, the block behavior at startup must differ from the normal cyclic behavior. For
example, it may be necessary to suppress certain alarms and messages for a number of cycles
after startup.
In this case, the block must not only be called in the cyclic interrupt OB but also in a startup OB
(OB100) so that its startup code can be processed. Its placement is performed automatically.
When you restart (warm restart) an S7-400 CPU (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 (OB32 - OB38). By default, all the PCS 7 blocks that have a
special startup behavior are incorporated in OB100.
The run sequence determines the data flow of the signals in the program. If possible the
processing of a signal should always be done from input to output to avoid potential dead times.
In the worst case, e.g. if the last block in the row is executed first, the program needs several
cycles to calculate the result. A small black symbol in the I/O indicates when the input is
processed before the connected output.
If the processing is performed in the correct order, the result can be calculated within one cycle.
Unfavorable configuration
4 3 2 1
The program needs 4 cycles to
process the signal.
The runtime editor (a view in the CFC editor) can be opened as follows:
Task (corresponds to
OB)
Current insertion
position pointer
Runtime groups can be moved by dragging them with the mouse, both within an OB and to
another OB.
You can change the run sequence according to which the program code of the blocks is
executed.
Manual configuration
Automatic optimization
Manual configuration
You can move blocks and charts in the runtime editor to the desired position or also to another
OB with a pressed mouse button.
The Optimize Run Sequence option is available for all blocks of all charts of the relevant chart
folder.
Individual charts or even entire tasks can be excluded from the optimization:
By selecting and deselecting the check box, the runtime group can be activated/deactivated for
processing as long as it is not interconnected. An interconnection always has priority.
In the details window of the runtime editor, the mode of the runtime group is displayed in the
"Inactive" column.
• The name corresponds to the runtime properties box of a block.
• The "!" character indicates that the relevant runtime group is inactive.
• The "?" character indicates that the "EN" parameter of the runtime group is interconnected
to a CFC or that the "EN" parameter is accessed by a CFC. For this reason, the runtime
group is not in the static process mode (can be active or inactive).
You can select or clear the option for the selected runtime group without needing to call up the
object properties with the shortcut menu commands:
Switching runtime groups on and off
References
See [103] PCS 7 V9.1 Engineering System, section [Link] for further information about
adapting runtime properties.
Manual
Introduction
During configuration, the blocks of a CFC are automatically installed in a cyclic task for the so-
called standard program. In addition to this, the blocks are installed in the relevant runtime
groups according to the task list of the block type.
The CFC and runtime groups are defined separately from each other because the runtime
groups in which the block calls are programmed have no unique reference to a CFC.
This non-unique reference applies even when during creation of a CFC a corresponding runtime
group is generated automatically and a so-called insertion pointer is set to this runtime group or
to a block in this group.
With the so-called chart-based runtime group management, the blocks of a CFC are managed
automatically chart-based in their own runtime groups. This means that the blocks of this CFC
are organized in runtime units that are assigned permanently and exclusively to this CFC.
Rules
With the "Chart-based runtime group management"... Naming the runtime group of a CFC
The blocks of a CFC are automatically managed in their own runtime The runtime group of the standard program in the cyclic task is
groups based on the chart. given the name of the CFC.
The blocks of this CFC are organized in runtime units that are The runtime groups of the acyclic tasks are given the name of the
assigned permanently and exclusively to this CFC. standard program with the next free number added, e.g. "(1)".
The runtime group for the so-called "standard program" has the
same name as the CFC. The name of the assigned CFC is shown in
brackets in the runtime group in the runtime editor. When a CFC integrated in the chart-based runtime group
management is renamed, the runtime groups belonging to it are
No block of another CFC can be contained in the runtime groups of also renamed.
this CFC.
The runtime group of the CFC in OB100 automatically receives the
The runtime groups belonging to it are generated depending on the next free name based on the name of the CFC.
blocks used in the CFC.
Coexistence
In a project, CFCs integrated in the chart-based runtime group management can coexist with
CFCs that are not integrated.
• In PCS 7 projects created with V8.1 or higher, the option "Chart-based insertion" is enabled
automatically in the properties of the chart folder.
• With an upgraded project created with an earlier version than V 8.1, this option only affects
charts newly created after the option was enabled. Enabling the option does not influence
existing charts and their configuration.
To enable this function, select the relevant chart folder of the S7 user program in the component
view of the SIMATIC Manager and select the shortcut menu Object Properties >
Advanced.
References
See [302] PCS 7 V9.0 CFC for SIMATIC S7 - Function Manual,
section 10.11.8 for more information on adapting the runtime groups.
Manual
Task
Configure the calculation of an average value with subsequent smoothing of the calculated
value.
Procedure
1. Set the insertion position pointer for new runtime groups at OB32 (1000 ms).
2. Create the "Average" CFC in the "Demo" folder. Insert the following blocks from the "PCS 7
AP Library V91" library into the chart:
– Math > Add04; Name "Add" (The I/Os "In3" and "In4" are not needed)
– Math > Div02; Name "Div"
– Math > Lag; Name "PT1"
3. Interconnect the blocks as shown in the figure.
4. Configure the "Div.In2" I/O with the value "2" to create the average.
5. Configure the "[Link]" I/O with the value "5".
6. Add the following I/Os to a new trend display:
– Add.In1
– Add.In2
– [Link]
– [Link]
7. Compile and download the program in PLCSIM.
8. Start test mode in CFC.
9. Start the acquisition in the trend display.
10. Test the function by changing the values at the "Add.In1" and "Add.In2" inputs.
7.12.2 Checkpoints
How can you change the run sequence in the user program?
A. By manual moving in the runtime editor.
B. By automatic optimization in the runtime editor
C. By using the "Avoid implicit dead times" function in the CFC
editor.
D. By graphical overlapping of blocks in the CFC editor.
OS server
Plant bus
Input drivers
... read the values from the process image input (PII) and make these process values available
at their outputs prepared for further processing by other blocks.
Signal processing
Processing of values without intervention from the outside.
Output drivers
... write the values (resuLIAs of signal processing, process commands) to the process image
output (PIQ).
Process images
The process image input (PII) and process image output (PIQ) form the interface between the
signals of the I/O modules and the user program of the CPU of an AS.
Updating
The transfer of the process values between the I/O modules and the process image is defined
by the settings in the properties of the CPU and the I/O modules.
The updating of the process values should be adapted to the speed of the signal processing.
Drivers form the interface between the process signals and the application. They are an
important part of a control loop.
Driver blocks
ES OS client OS client
OS server
Plant bus
Chart
PII PIQ
Pcs7DiIn MotL Pcs7DiOu
4 5 6 7
PV_In PV_Out FbkRun Start PV_In PV_Out
3 8
M
2 1
1. The control signal of a channel of the output module is wired to the motor (or its control
logic).
2. The feedback signal of the motor (or its control logic) is wired to a channel of the input
module.
3. The signals of the input module are transferred to the process image input (PII) on the
CPU.
4. The input driver reads the signal from the PII and transfers it to the chart in order to be
evaluated by technological blocks. It converts it to a process value.
5. A control block (technological block) receives the process value from the input driver. The
logic of the control block generates one or more control signals.
6. The output driver receives the control signal from the control block.
7. The output driver writes the control signal to the process image output (PIQ) on the CPU.
8. The control signals are transferred to the output module. The output module converts them
to suitable electrical signals.
Channel driver blocks are used in PCS 7 to process process signals from the plant in the AS
program. They are the interface between the hardware and the automation program and ensure
that input signals can be processed by the input modules in the AS program and output signals
Digital and analog input and
are transported fromoutput driver blocks
the AS program to the output modules.
A distinction is hereby made between digital and analog input and output driver blocks.
Simulation
Process value
Substitute value in including signal status
case of poor signal
status
Simulating signals
The block has the standard function "Simulate signals".
The output driver block "PCS7DiOut" is used to set control signals in the plant. It has the
following important I/Os:
Process value
including signal
status
Invalid process signal
Simulation
Simulating signals
The block has the standard function "Simulate signals".
Flutter suppression
This block provides the standard function flutter suppression for channel blocks.
12.96 mA 16#3C7B
16#6C00
12.96 mA
5m 16#3C7B 16#3C7B 2.8 PV
(15483) IW512=
2.8 m
16#3C7B
2.8 m
m Unit
16#0000
4 mA
0m 5m
16#0000 16#6C00 [Link] [Link]
0m
(0) (27648)
The physical quantity is determined using a transducer; which in this case has a measuring
range of 4 to 20 mA. The analog input module converts the electrical signal to a raw data value
© Siemens 2022 | SITRAIN | 08 Connection to the process
from 16#0 to 16#6C00 (unipolar measuring range). The input driver block, in turn, scales the
raw data value into a process value.
Depending on the module used, the Mode parameter is parameterized accordingly during the
compiling (e.g. 16#203 → measuring range 4-20 mA). In the measuring type, the I/O value for
4 mA is output for PV_In =[Link] and for 20 mA for PV_In = [Link].
The block writes input parameter Scale directly to the output parameter ScalOut and then
directly interconnects with a technological block. This can be the input parameter MV_Opscale
of a controller block, for example.
The normal value (physical quantity) is formed from the raw value using the parameters Scale
and Mode. Specify two scale values for the structured parameter Scale:
• High scale value ([Link])
• Low scale value (Scale Low)
The settings of the parameter Scale are copied to the output parameter ScaleOut. The output
parameter can be interconnected with a suitable input parameter of a technological block (e.g.
PV_OpScale).
The normal value is obtained using a linear characteristic curve. [Link] is the lowest
physical value the process variable can adopt, [Link] the highest.
If you set DeLIAaVal > 0, the last PV_Out (k - 1) or one before last PV_Out (k - 2) valid output
value is output. PV_Out (k) is the current value, k the current time.
With the parameter DeLIAaVal you can specify a permitted process value change (PV_Out)
between two calls. The following options are available:
• For invalid raw values and DeLIAaVal > 0:
– When |PV_Out (k - 1) - PV_Out (k - 2)| > DeLIAaVal, then PV_Out = PV_Out (k - 2)
(one before last valid output value is output)
– When |PV_Out (k) - PV_Out (k - 1)| ≤ DeLIAaVal, then PV_Out = PV_Out (k - 1) (last
valid output value is output)
• For valid raw values and DeLIAaVal > 0:
– When |PV_Out (k) - PV_Out (k - 1)| > DeLIAaVal, PV_Out = PV_Out (k - 1) is output
for one cycle, i.e. DeLIAaVal is used to limit changes to the valid raw value. The signal
status at the output parameter PV_Out is additionally set to 16#60 and the output
parameter Bad is set to = 0.
The value of DeLIAaVal should be selected carefully. If it is too low, the signal status
can jump back and forth between 16#80 and 16#60 aLIAhough the raw value is OK.
Simulating signals
The block has the standard function "Simulate signals".
LowCutOff
The output value PV_Out is set to the lower value of the measuring ranger if the value falls
below the value set at the interface LowCutOff.
This function is released by Feature bit 5.
Process value
including signal
status Invalid process signal
Simulation
Scaling and unit of
measure for further
processing
I/Os for automatic
interconnection with
the module drivers Module out of service
Simulating signals
The block has the standard function "Simulate signals".
Flutter suppression
This block provides the standard function "Flutter suppression" for channel blocks.
References
For more information on the signal status of PCS 7 channel blocks, see
[113] PCS 7 V9.1 Advanced Process Library, section [Link].
For more information on simulating signals, see
Manual
[113] PCS 7 V9.1 Advanced Process Library, section [Link].
Signal interconnection
The interconnections provide the channel driver block with diagnostic information that can be
evaluated in the user program.
The content of runtime groups created by the driver generator ("Generate module drivers"
function) (@......) is 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
Note
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 "Generate module
drivers" check box is selected).
Signal status
Description
© Siemens 2022 | SITRAIN | 08 Connection to the process
Priority Code OS symbol
Good 6 16#80
Note that, after changes to the parameter assignment of signal groups in the hardware
configuration (e.g. measuring range), the Mode input of the channel driver block requires a
Note new value. In such cases, the driver generator needs to be run through again when compiling
© Siemens 2022 | SITRAIN | 08 Connection to the process
charts.
Signal status
You will find a table with the list of all possible mode settings for signal modules in the following
manuals:
• [112] PCS 7 V9.1 Basic Library, appendix 9.2
• [113] PCS 7 V9.1 Advanced Process Library, section 16.20
The symbol table is the central location of the symbolic names of all objects. In addition to the
hardware addresses, these can also be the symbols for block types, functions and user data
types.
You can also edit symbolic addresses directly in the symbol table. However, to do this, you
© Siemens 2022 | SITRAIN | 08 Connection to the process
need to know the hardware address and data type of the connection.
8.6Process
Process
image image partitions
partitions –
Examples of settings
T PIP2
I
AQ4
AI8 1
Chart OB32 (1 s)
5 5
PIP3 Pcs7DiIn VlvL Pcs7DiOu PIP3
Pcs7DiIn
DI16 DQ16
2
Chart OB33 (0.5 s)
1. Assuming that a chart for a temperature control is to be processed with a cycle of 1 second.
The chart is installed as a runtime group in OB32.
2. Assuming that a chart for opening/closing a valve is to be processed with a cycle of
0.5 seconds. The chart is installed as a runtime group in OB33.
3. In the properties of the CPU, settings must be made to enable a process image partition
PIP2 in OB32 and a further PIP3 in OB33.
4. The process image partition PIP2 must be activated in the properties of the input and output
modules whose signals need to be transferred from and to the process image triggered by
PIP2 (linked to OB32).
5. The process image partition PIP3 must be activated in the properties of the input and output
modules whose signals need to be transferred from and to the process image triggered by
PIP3 (linked to OB33).
OB1
The time sequence diagram above indicates, with the same colored arrows as the picture
before, the time at which the values are transferred between the I/O modules and the process
image.
© Siemens 2022 | SITRAIN | 08 Connection to the process
Setting
Process forimage
CPU and I/O modules
partitions –
Setting forThe
CPU and I/O
following modules
figure shows the settings affecting the process image partition that need to be
made in the properties of the CPU and the I/O modules in HW Config.
References
See [103] PCS 7 V9.1 SP2 Engineering System, section [Link] for more details.
Manual
The CFC editor has a buiLIA-in tool for representing trends. It allows the recording of short-term
trends during commissioning and troubleshooting.
Trend display
A maximum of 12 values can be recorded within a trend display.
1. Select the View > Trend Display menu command in the CFC editor.
© Siemens 2022 | SITRAIN | 08 Connection to the process
2. The window for the trend display shares the working area of the CFC editor with the
windows for the charts. Add, delete or rename a trend display. Arrange a suitable layout of
the windows.
3. Select suitable recording parameters: Number of values (10... 16000), recording cycle
(1...9 sec, 10...90 sec) and recording mode.
4. Drag the desired block I/Os with the mouse onto one of the 12 channels in the trend display.
You can assign values from different blocks and from different charts.
5. You can set the high limit and low limit for the display parameters (y axis) for each selected
channel with a numerical data type. If Boolean values need to be recorded, a pre-defined
area of the vertical axis is reserved per channel to display the values "False" and "True".
You specify the number of the measuring points to be displayed (x axis) for each specific
channel.
6. The "Start" button is only available in test mode. After starting, this button is replaced by a
"Hold" button. With this, you can stop the recording at any time.
7. Export the recorded data to a CSV file. Check the export settings with the menu command
Options > Customize > Export Trend Data.
Similar to the trend display, the dynamic display can also be used in CFC test mode. It is a table
Dynamic with
display
values of I/Os of blocks from different charts of a CPU. In the window, the values can be
displayed and monitored, and values of non-interconnected I/Os can be changed.
1. Select the View > Dynamic Display menu command in the CFC editor.
2. The window for the dynamic display shares the working area of the CFC editor with the
windows for the charts. Arrange the windows suitably and drag each of the desired block
I/Os
© Siemens 2022 | SITRAIN | 08 with
Connection to thethe
processmouse to a line in the dynamic display.
Procedure
1. Open the hardware configuration for the automation system.
2. Select the I/O rack (e.g. ET 200M, ET 200SPHA) containing the modules whose symbolic
addresses you want enter.
3. Select the relevant signal module and select the "Edit Symbols" command in the shortcut
menu.
4. Refer to the following tables:
Results
You have assigned symbolic names for hardware addresses. You can now connect driver
blocks to the signal without having to know the exact hardware address.
8.8.2 Exercise: Configuring driver bocks for acquiring signals and process values
Task
ask Create CFC with the driver blocks for acquiring signals and process values.
SignalboxDiIn SignalboxDiOu
SignalboxAnIn SignalboxAnOu
10. In the "Test" menu of the CFC editor, activate Laboratory mode and set a watch cycle of
1 second.
11. Enable CFC test mode.
12. Test the new functions using the signal box or PLCSIM.
(See: 8.8.3 Optional exercise: Signal simulation with PLCSIM)
13. Create a dynamic display in the CFC editor with the name "Digital signal box" and add the
following signals of the digital I/O drivers to it:
– PV_Out of the input driver
– PV_In of the output driver
14. Observe the input signals in the value table and modify the values to be output.
15. Create a new trend display and add process values of the two potentiometers, as well as
the average value formed from these values. Observe the values while changing the
process values via the potentiometers.
Results
You have configured the first CFC and tested it. You used the associated engineering tools and
test options in this process. Here we have created the CFC charts ourselves, but there are also
ready-made templates for motors, valves, controllers, etc. We will use these for the process
tags in our Johnsson plant.
If you use the PLCSIM as an aLIAernative AS to test the program, you do not have the option of
working with real signals.
However, PLCSIM also offers the possibility to display or set process values and signals directly
using different input/output fields.
Task
Task
Simulate process signals and process values using PLCSIM.
1. Insert some input and output fields and enter the address range that is to be displayed. The
view changes depending on the address entered. For example:
– IB 1 → Input Byte 1 → Address: I1.0 to I1.7
–
Siemens 2022 | SITRAIN | 08 Connection to the process
QB 0 → Output Byte 0 → Address: Q0.0 to Q0.7
– IW 512 → Input Word 512 → Address: I512 to I513 (2 bytes)
– QW 512 → Output Word 512 → Address: Q512 to Q513 (2 bytes)
2. For process values, you can customize the display of the value. For example: Binary,
hexadecimal, integer or integer with slider.
Process values are always processed as raw data values in the process image of the
PLCSIM.
3. ALIAernatively, bits can also be displayed vertically. The advantage of this display is that
the symbolic name of the signal can be displayed.
4. You can read the symbolic names using the "Find Symbols" function. Navigate to the
symbol table of the project and confirm the selection.
Start the CFC test operation, change the process signals and process values of the inputs in
PLCSIM and compare the values on the input driver blocks.
In CFC test mode, change the values at the output driver blocks (PV_In) and compare them
with the displayed values in PLCSIM.
Results
You can now adapt and display process signals and process values with PLCSIM.
Why8.8.4
do @(..)Checkpoints
charts appear in the chart folder?
For various reasons, we cannot provide a real process for training purposes. Instead, we offer a
process simulation for the inputs and outputs that simulates the process characteristics of a
plant.
The following figure shows the relationship between the user program running on the
automation system, the inputs and outputs of the process and the simulation replacing the real
Positioning
[Link] process simulation in the course
Hardware Software
I/O modules Driver blocks
Process image
AI
Controller
Pcs7AnIn block
AQ
Process Pcs7AnOu
DI
Process value
Name Pcs7DiIn Motor
DQ
block
Pcs7DiOu
Johnsson
Process
simulation
Symbol table
The process simulation (running as a function block on the CPU) uses the original process
image as interface to the user program on the AS. This allows you to configure the AS functions
© Siemens 2022 | SITRAIN | 08 Connection to the process
with the aid of channel driver blocks in exactly the same way as with real applications.
The symbol table contains the signal names for the process values in the process image and
their addresses. These addresses should not overlap with those of the real hardware.
CFC: @Johnsson 1
Johnsson
4
YS311
YS311_FBO
YS311_FBC
CFC: YS311 2 3
YS311_C
Pcs7DiIn VlvL Pcs7DiOu
YS311
Pcs7DiIn
Task
Task
© Siemens 2022 | SITRAIN | 08 Connection to the process
1. CFC with the name "@Johnsson", which contains the "Johnsson" simulation block. The
block calculates all process values (fill levels, temperatures, valve motor positions) of the
system. The chart exists only in the chart folder of the AS project, not in the technological
hierarchy.
2. A chart with the minimum number of blocks to monitor and operate the valve. This chart is
located in the plant hierarchy.
3. Control signal to the valve. The simulation block reads the value of the control signal
"YS311_C" and calculates the current position of the valve.
4. The simulation block writes the resuLIA to the input signals of the valve feedback
monitoring:
– "YS311_FBO" = open
– "YS311_FBC" = closed
8.9.2 Overview
The number of inputs/outputs (I/Os) is based on the process devices (process tags) and their
required signal supply in the plant. The following table provides an overview of the process tags
and the corresponding I/Os:
Number DI DQ AI AQ
Open/close valves 25 50 25
Status valves 5 5
Motors/drives 11 11 11
Fill level 13 13
measurements
Temperature 4 4
measurements
Control valves 4 4 4
Total 62 66 36 21 4
Number of channels 16 16 4 4
per module
Number of modules 5 3 6 1
Task
Implement the process simulation for the Johnsson facility in this training session.
Procedure
1. Copy the "@Johnsson" chart from the chart folder of the course library into the chart folder
of your AS.
2. Apply the symbols of the Johnsson plant into your project. Copy them from the course
library and don't forget to save your new symbol table.
The symbols with the following addresses are required:
– "I100.0" to "I116.3"
– "IW 208" to "IW406"
– "Q100.0" to "Q109.3"
– "QW 208" to "QW 238"
Results
Our process simulation is installed and now we can configure the automation functions for
the plant.
• You know the basic functions of APL modules as well as the chart templates that
are available as a basis for creating the basic automation.
• You can parameterize APL blocks in their most important properties and carry out
initial tests of the basic automation in CFC test mode.
• You can configure and test the functions of the basic automation for the process
tags on the basis of the APL templates.
Timer
Counter Monitoring
Motors
Valves Alarming
Advanced
Process Library
PID Locking
Control
Dosing Operating
The APL contains blocks of the following categories (list not exhaustive):
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
APL functions
The APL contains some general functions to enable consistent configuration and operability.
For this purpose, standardized functions have been implemented in the blocks of the APL.
The general functions include:
• Operating modes (manual, automatic, local, out of service)
• Evaluation of the signal status
• Evaluation of feedback signals
• Interlock functions (Interlock, Permit, Protect)
• Configurable block behavior (Feature bits)
• Parameterization of units of measure according to standard
• Output of alarms and messages
• Processing of external errors
The PCS 7 Advanced Process Library (APL) is a block library for PCS 7 that was introduced
with PCS 7 Version 7.1. It covers all blocks and functions of the earlier PCS 7 Standard Library,
while of
Compatibility adding
the additional
librariesfunctions
in PCS to 7 blocks
V9.1 and completely new blocks.
The PCS 7 Standard Library is still available, however. It is also possible to use both libraries
simultaneously in a project (e.g. in a chart).
PCS 7 Advanced
PCS 7 Library V7.1 Diagnostic drivers Process Library V9.1
e.g. MOD_1 (version 9.5)
Because the PCS 7 Standard Library and the PCS 7 APL can be used individually as well as
together, shared functions are contained in a PCS 7 Basis Library. These shared functions are
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
primarily the module drivers.
With the release of PCS 7 V8.2, however, the PCS 7 Standard Library is not available in
Version 8.2 but rather only in its last version V7.1.3. As of PCS 7 V8.0, the standard library is no
longer installed automatically. If needed, it must be additionally installed manually.
Structures are a new feature of the APL. Every interconnectable parameter of a block is a
structure-type parameter. As a structural element, a structure contains the value of the signal
(Value) and the associated Signal Status (ST). Depending on the data type of the signal, the
structure consists of a certain number of bytes (at least 2 bytes).
Analog value
Binary value
0 16#60 Simulation
For technological blocks, a group status is formed from input parameters (see description of the
corresponding blocks) according to a table.
This group status is shown in the status bar of the faceplate and the block icon.
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
Priority "0" has the highest priority. Priority "6" has the lowest priority.
If "Keep last value" or "Substitute value" was configured for the channel driver and a channel
Note error occurs, the signal status receives the value 16#60 instead of 16#00. The operator then
sees the symbol for "Simulation" instead of "Bad, device related" on the OS.
If process values are directly connected to the technological function block (e.g. MotL) via a
channel driver (Pcs7AnIn, Pcs7DiIn, Pcs7DiOu, etc.), the signal status is displayed directly in
the faceplate.
For other blocks, such as And04 or Or04, the signal status is inherited at the output according to
a logic.
The formation of the signal status of the outputs is based on the following premise:
• If any input at a gate causes a signal change at the output, the worst signal status of the
input must be taken, because every signal can influence the output.
• If several inputs equally ensure that the output cannot change, the best signal status from
these is taken because the output is definitively fixed by this signal.
Formation of the signal status of the outputs on AND and OR logic blocks
Formation Logic
of theblocks
signal status
have of the priority
a changed outputs on AND and
arrangement ORsignal
of the logicstatus
blocksat the output. The signal
status "Simulation" moves back two places.
Changed priority of logic blocks Comparison of signal status between AND and OR
1 16#28
In1 In2 In3 In4 Out AND Out OR
2 16#60 0 0 0 0 0 0
16#80 16#80 16#28 16#00 16#80 16#00
3 16#68
1 1 1 0 0 1
16#80 16#80 16#80 16#28 16#28 16#80
4 16#78
0 0 0 1 0 1
5 16#A4 16#80 16#80 16#80 16#28 16#80 16#28
Lowest priority, 1 1 1 1 1 1
6 16#80 16#80 16#80 16#28 16#00 16#00 16#80
best status
AND operation
If the signal state of the output is "1", the signal status of the output receives the worst status of
all inputs.
If the signal state of the output is "0", the signal status of the output receives the best status of
all inputs with the value "0".
OR operation
If the signal state of the output is "1", the signal status of the output receives the best status of
all inputs with the value "1".
If the signal state of the output is "0", the signal status of the output receives the worst status of
all inputs.
Inputs which are not interconnected are not taken into account.
Best status
The result is "1" → The best status of all inputs with a value of
"1" determines the status of the output.
Worst status
Special cases
For the Trip parameter and the three interlock parameters (Permit, Intlock, Protect), the signal
status has a direct effect on the function of the technological block.
If a bad signal status (16#00 or 16#28) exists in these cases, it has the same effect as a
process value = 0.
See [113] PCS 7 Advanced Process Library V9.1, section 2.1.5 for more details on the
formation of the signal status.
In the APL, most of the technological blocks have the Feature input parameter. This parameter
allows the manufacturer to implement different industry-specific customer requirements and to
© Siemens 2022 add functional
| SITRAIN | 09 Basicenhancements later.
automation with the APL
The parameter is a structure and contains 32 Boolean elements that can be used to set different
technological behavioral patterns and enable additional block functions. Not all elements of the
Feature parameter are assigned at present. The unassigned reserve bits can be assigned for
functional enhancements later by the manufacturer (Siemens).
The parameter assignment of the individual bits of the Feature parameter is done by double-
clicking the Feature input of the block (offline/online, see figure above). It is recommended that
the "Feature" bits in the templates be configured in the master data library to ensure
consistency within the multiproject.
See [113] PCS 7 Advanced Process Library V9.1, section 2.1.9 for
Parameterizable behavior via the feature connection (assignment of feature bits).
The feedback messages from devices can be issued via one or more binary signals, or via an
analog signal, such as the setting position of a valve. For this purpose, corresponding inputs are
provided at the technological blocks. Through these inputs, the block can recognize the
effectiveness of a switching command and react accordingly.
Deactivation of monitoring
You can activate or deactivate the feedback monitoring. Monitoring is parameterized via the
"Monitor" input.
Monitor = 0 -> Monitoring disabled
Monitor = 1 -> Monitoring enabled (default setting)
Static and dynamic errors are reset by deactivating the monitoring (Monitor = 0). If you
reactivate the monitoring while the plant is running, only the dynamic monitoring
("MonTiDynamic") will be performed.
Deactivating feedback
You can operate a block without feedback.
You can set the "NoFbkRun = 1" parameter for the "MotL" block.
You can parameterize the two feedback signals "NoFbkOpen = 1", "NoFbkClose = 1"
independently for the "VlvL" block.
The operating status ("Stop" or "Run", "Opened" or "Closed") is then tracked according to the
control signal.
Ctrl = 1
0
FbkOpen = 1
0
Feedback error
FbkClose = 1
0
MonTiDynamic 5 s
0s
The monitoring of the startup behavior for motors or the runtime of valves is implemented via
the "MonTiDynamic" parameter. The monitoring time specifies the period in which the
corresponding feedback value, e.g. "FbkRun" for the motor, must be present on a control signal.
If this is not the case, an error message is triggered on the block.
The block then goes to its safe position. For motors, this is always the stop state. For other
blocks, it is a safe position specified by you ("SafePos" parameter). The block signals this at the
relevant output parameter of the error message with 1, e.g. for the motor with "MonDynErr = 1".
The parameters are assigned in seconds and apply to the opening and closing of the valve. If
required, the monitoring time for the "MonTiDynamic" startup and the "MonTiDyStop" outlet can
be set separately for the motor.
?
Valve position Open
Close
Ctrl = 1
0
FbkOpen = 1
! Signal failure Feedback error
FbkClose = 1
0
MonTiStatic 5 s
0s
The monitoring of the running behavior for motors or the holding of valve positions is
implemented with the "MonTiStatic" parameter. The monitoring time specifies the period in
which the feedback value can briefly change its value without an error message being output.
The feedback signal should be static according to the control.
If the value change takes longer than the set value, an error is output and the block then goes to
its safe position. For motors, this is always the stop state. For other blocks, it is a safe position
specified by you (SafePos parameter). The block signals this at the relevant output parameter of
the error message with 1, e.g. for the motor with "MonStaErr = 1".
The parameter is assigned in seconds.
Channel blocks and technological blocks have an error handling function. The following areas
must be differentiated here:
• Error numbers
• External control system fault (CSF)
• Process-related errors
Error handling
• Invalid signal states
• Mode switchover errors
• Errors in channel blocks
Group error
External control
system fault
External alarms
External error
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
External errors are hardware errors at the field and control level, such as motor torque or
overtemperature. These errors are usually detected via a signal at the I/O and connected to the
"FaultExt" input. If there is an external error, the safe position is triggered.
A message is not output. However, if required, this can be generated and parameterized via the
inputs "ExtMsg1", "ExtMsg2" and "ExtMsg3".
Error numbers
Most blocks have output parameter ErrorNum, which is used to output the possible block-
internal error states as an error number.
If the block algorithm recognizes invalid combinations of input signals, an error number
(ErrorNum) is output as a function of the block type.
This error is output if inconsistencies between associated I/Os occur. In this way, for example, a
valve will not simultaneously receive the commands for opening and closing.
1038 L liters
1077 Hz Hertz
1088 kg Kilograms
For a complete list of available units, see the online help "Select unit of measure"
The procedure for setting the unit for analog signals will be explained using an example with the
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
If the PV_Unit input of MonAnL is configured with 0, the unit can also be specified using the
conventional method ("S7_unit", or in the CFC in the block properties ("I/O" tab) of the
Note MonAnL in the "Unit" column for this input). This method can be used for units that are not
listed.
Customer-specific units
It is possible to use units that differ from the IEC 611582 standard. You can specify your own
units in the range between 1 to 199 in an XML file. The name of the XML should be
[Link] and should be stored in the project path in the "GraCS" folder on both
the server and the client.
See [113] PCS 7 Advanced Process Library V9.1, section [Link] for more details on units of
measure in the APL.
Alternative:
For information on data type and possible code numbers, see help for the "MonAnL" block
and then use search term "Select unit of measure".
How it works
The MonAnL block is used for monitoring an analog process tag with monitoring for limits. In
addition, the increase of the signal is monitored. If limits are violated or if the signal increase
does not conform to requirements, messages are generated and output.
Warning times
Warning times can be configured for the function block for motors. Using the WarnAct output, a
signal light or a horn can be controlled, for example. These warning signals enable operators to
be informed about the impending start of the corresponding drive.
Warning times can be configured separately for manual and automatic modes:
• Manual operation: Input parameter WarnTiMan (in unit of seconds)
• Automatic mode: Input parameter WarnTiAut (in unit of seconds)
If WarnTiMan or WarnTiAut is configured with 0, the WarnAct output is not controlled in the
corresponding operating mode and thus no warning is output.
The configuration of warning times delays the actual start command by the configured warning
time.
The VlvL block is used to control a valve in two positions (OPEN/CLOSED) with configurable
safety position.
This valve is open or closed using a control signal. The control is monitored by means of the
position signals OPEN/CLOSED (feedback). If feedback is not available, it can be derived from
the control in the block.
Some of the block I/Os of the valve block are described below.
Safety position
The safety position (open or closed) can be configured using the SafePos parameter:
• SafePos = 0: When Ctrl = 0, the valve drive closes, and when Ctrl = 1, the valve drive opens
(de-energized position "Closed").
• SafePos = 1: When Ctrl = 0, the valve drive opens, and when Ctrl = 1, the valve drive closes
(de-energized position "Open").
Note It is contrary to the philosophy of PCS 7 to place other blocks between the drive block and
the output driver.
If you deviate from this principle, you must ensure that all blocks that influence the control
signal that are located between the control output of the drive block and the channel driver
are also in the same OB.
PIDConL
Logic for
internal/external
setpoint setting
Deadband
External Gain
SP_Ext TI
Internal TD
SP_Int
…….
+
PV PID
- Auto MV
Man Manual
SP_LiOp ModLiOp
SP_ExtLi AutModLi
S S
SP_ExtOp AutModOp
1
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL 1
SP_IntLi ManModLi
R R
SP_IntOp ManModOp
Feature.Bit4: Feature.Bit4:
0 = Pushbutton operation 0 = Pushbutton operation
1 = Switch operation 1 = Switch operation
"Large" blocks offer the full range of functions, but "Small" building blocks have fewer functions and
require more resources. require fewer resources.
See [113] PCS 7 Advanced Process Library V9.1, section 5.1 for more details on the
comparison of large and small blocks.
9.5 Templates
Templates (standard types, standard solutions) support you when configuring recurring
technological functions in a PCS 7 system.
The PCS 7 libraries (PCS 7 Advanced Process Library, PCS 7 Basis Library) contain templates
Templates
for basic technological functions (e.g. motor control, valve control, standard PID controller) as
well as for advanced closed-loop control functions (PID controller with safety logic and control
loop monitoring).
A template is a prepared chart that contains all the blocks required for a process tag, i.e. not
only the technological block for a control function but also the driver blocks and additional
processing logic.
© Siemens 2022 | SITRAIN | 09 Basic automation with the APL
ValveLean example
9.5.1 ValveLean example
"Out of service"
status
Textual
Logic for generating a control
interconnection system fault
ChartName\BlockName.I/Oname
Log file
A log is generated in which all closed and all still open textual interconnections are listed. You
can open the log from the CFC editor with:
Logs > "Textual interconnections" tab
If one or more textual interconnections are not closed, a corresponding note is made in the log.
You see the note using the menu command
Logs > "Compile" tab
The compilation takes place and a substitute value is generated for the relevant input (default
value of the block type). An interconnection at the output is ignored.
See [302] PCS 7 CFC for SIMATIC S7 V9.0 SP7 - function manual, section 10.8.8 for more
details.
In PCS 7, process messages are always generated in the AS. For this reason, they are also
acknowledged centrally in the AS, i.e. an OS acknowledgment is sent to the triggering block,
which accepts the acknowledgment and sends the acceptance to all logged-on operator
stations.
Ready-made alarm blocks are provided as SFBs (system function blocks) in both the PCS 7
APL and the PCS 7 Standard Library.
Alarm blocks
The message generation and acknowledgement behavior and the transfer of associated values
is specified in the CPU properties ("Diagnostics/Clock" tab, "Acknowledgment-triggered
reporting of SFB 33-35") and on the integrated alarm block.
Message numbers
The message number is unique within the CPU for PCS 7. When the OS is compiled, the
numbers required for the individual messages for the PCS 7 OS are derived from this message
number. It is automatically assigned at the MsgEvId input, which is not visible, interconnectable,
or parameterizable in the CFC.
Alarm-enabled Alarm-enabled
block type A block instance
DB x
ALARM_8P ALARM_8P
Alarm-enabled Alarm-enabled
block type B block instance
DB y
ALARM_8P ALARM_8P
For blocks with code that call other blocks (multi-instance blocks), the applicable version of
these lower-level blocks must also be copied. Missing lower-level FBs can be identified later
Note by the engineering. Missing FCs, however, cannot be detected during compiling or
downloading.
Configure the following automation functions in the AS for material tank M110 based on
templates from the library:
YS112
4s
NS113
2s
Procedure
1. Open "PCS 7 AP Library V91" in the SIMATIC Manager and go to the "Templates" folder
(Component View).
2. Copy 4 process tag types to the "Process tag types" folder of your master data library (plant
view):
– AnalogMonitoring
– Motor_Lean
– PIDControl_Lean
– Valve_Lean
3. Close the window with the library.
4. Before copying the charts to your user program, you need to make some adjustments to
these charts in the master data library that deviate from the standard:
5. Close all charts and switch to the plant view to copy the following 3 charts into your
multiproject:
– Ensure that the charts are included as runtime groups in OB32.
– From the "Process tag types" folder of the master data library
– Into the hierarchy folder of the plant hierarchy: "Johnsson\Materialtanks\M110"
– Charts: AnalogMonitoring, Motor_Lean, Valve_Lean
6. Since we initially want to use simple CFCs, remove the "Process tag" property from these 3
copied charts.
– Use the "Properties CFC chart" dialog box and click the "Clear" button in the "Process
tag type" tab.
9.8.2
Why are thereCheckpoint: APLtemplates?
OR gates in the Templates
• You are familiar with the process object view in SIMATIC Manager as well as advantages and
limits for engineering in this view.
• You can adapt and filter the representation of the data in the process object view in order to
efficiently perform spreadsheet-based engineering.
• You can edit signals and parameters on APL blocks in the process object view.
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
In the process object view, all data of the basic automation can be displayed throughout the
project in a process-oriented view. A multiproject then comprises the data of all projects it
contains.
The process object view is mainly used during FAT and commissioning. These tasks require
efficient editing of a large amount of data at a central location. The process object view offers
the advantage that all editable process tags/values of an object (displayed on a white
background) can be edited centrally.
When process tags and CFCs are edited, all aspects (automation, I/Os, messages, operator
control and monitoring) can be consistently displayed and documented. By jumping to CFCs,
SFCs, hardware configuration and the OS, you can edit process tags/values that cannot be
edited in the table (e.g. picture content, etc.).
The process object view is opened in SIMATIC Manager using the menu command:
ProcessView
object viewobject view
> Process
The green checkmarks indicate that the current data has been read in according to the selection
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
in the hierarchy tree.
Configuring columns
In SIMATIC in can
Manager, you theuseprocess
the followingobject viewto open a dialog where you
menu command
can select and arrange the desired columns of the process object view: Options > Settings >
Columns.
3
2
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
1. Click in the area of the column header.
2. Use drag-and-drop to move the selected object to the desired location.
You can use the View > Define Columns… menu command to define other separate columns
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
on the "General", "Blocks", "Parameters" and "Signals" tabs of the process object view.
In this way, you can add important supplemental information, such as the operator name or
maintenance interval, to the following objects:
• Process tags
• CFCs/SFCs
• Parameters and signals of process tags and CFCs
10 Spreadsheet-based engineering with the process object view 10-4 SITRAIN
SIMATIC PCS 7 System Course
In the CFC, you specify whether a block I/O is displayed in the process object view as a
parameter or signal (see below).
Parameters are block I/Os for which parameter configurations or interconnections between the
process tags or CFCs have been selected.
SpecifyingSignals
the contents
are blockofI/Os
thethat
"Parameters"
are or will be and "Signals"
connected tabsoutside of CFCs/SFCs (CPU
to signals
memory, but mostly inputs and outputs of the AS).
2
2
2. Selection in a filter dialog of SIMATIC Manager under Options to set the desired filters
To avoid having to open the individual CFCs, the I/Os for the project object view can be
selected from the process object view itself (see above and below). Here you open a dialog box
that lists all I/Os of the selected hierarchy folder. From this list, you can select the parameters
and signals that you would like to edit in the process object view.
Specifying the
A dialog boxcontents of the
for the filter settings can"Parameters" and
be opened via the dialog box"Signals" tabsYou
for the I/O selection.
can use this filter to limit the data set for particular columns and thus the time required for
reading (example: display "BOOL" data type only).
I/O in tab
Make "Signals" available
I/O in tab
Make "Parameters" available
10.2.4 Defining
Defining the "Parameters"
the "Parameters" or "Signal"
or "Signal" attribute
attribute for multiple
for multiple I/Os I/Os
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
Through the use of suitable filter and sorting settings, you can group the block I/Os in such a
way that you can select an I/O area and completely set/reset this area. In the above example,
only the block I/Os whose name begins with "SimOn" will be displayed, and therefore only these
will be set up as parameters for the process object view.
plitting tables
You can split the window in half (left and right) with each half having its own scroll bar. You may
mens 2022 | SITRAIN | 10 Spreadsheet-based engineeringwith
be familiar with the process
this object view
function from
other programs such as Excel.
10.2.6 Filters
Filters
The filters for limiting the data in the table are freely programmable.
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
You can configure up to four filter criteria and link them logically with the AND or OR operators.
A space character has a special meaning: the empty rows in this column will be displayed.
The process object view also has functions for managing and activating filters:
Button Description
Use this button to filter the data with the configured filter criteria. The filter criteria are
only applied when you click this button.
This button is only enabled when the current filter is configured.
Use this button to clear all filter settings.
Use this button to load previously saved filter settings.
Use this button to save the current filter settings to a file.
Use this button to show the next filter setting below the current one.
This button is only enabled when the current filter is configured.
Use this button to hide all filter settings except the first one.
This button is only displayed when multiple filter settings are configured.
The filter settings made on the "General" tab affect other tabs (exceptions: hierarchy folders,
equipment properties, shared declarations):
Note Only the objects displayed on the "General" tab are then displayed on the other tabs. This
filter setting remains visible for the other tabs under "Filter general" (see the example at the
top left in the figure).
1 2
Data from the engineering system can be exported using copy & paste, duplicated, edited in an
external program (such as MS Excel) and then imported back to the engineering system. This
functionality allows you to optimize the configuration of recurrent or similar plant information.
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
See [103] PCS 7 V9.1 Engineering System, section [Link] for further information on
exchanging data with MS Excel or Access.
10.2.8 Importing and exporting data using the process object view
By exporting and importing attributes, you can perform the following actions on parameter,
signal and message information: export to a file, edit with standard applications and re-import.
These functions are especially useful when you want to edit large amounts of data. You do not
have to edit the individual charts with the CFC editor in order to modify the I/Os because the
I/Os of all charts in the hierarchy folder are automatically imported.
Charts in the selected hierarchy folder and all subordinate hierarchy folders are edited
(according to the selection in the process object view).
Importing and exporting data using the process object view
Selected hierarchy
folder
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
See [103] PCS 7 V9.1 Engineering System, section [Link] for further information on
importing/exporting blocks, I/Os and messages.
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
Configure the basic automation (manual mode) for all process tags of D210, R310 and B410.
YS211
YS212 TICA YC315
YS213 315 21 s
0.25 s NS316
M 2s
LIA
214
D210 TT
400 kg LIA
315 414
R310
LIA B410
700 kg
314 12000 kg
YS311
4s
YS312 YS411
5s 5s
NS313
2s
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
Procedure
1. Delete the temporary charts "tempYS211".
2. Open the "PIDControl_Lean" process tag type in your master data library to make a few
adjustments.
3. Copy a PCS7AnIn driver block into the free area at the bottom left of sheet 1 of this chart
and rename it "Rbk".
– Change the text of the interconnection with the PV_In input to "Read back".
– Correct the PV_InUnit parameter to the value 1342 for "%".
4. Interconnect the PV_Out output of the new driver block with the "Rbk" input of the controller
block.
5. Make the two "Or04" blocks at the "In2" input visible and add the correct interconnections to
the new driver block.
6. Now close the chart and copy it from the master data library into the plant hierarchy:
Johnsson\Reactors\R310\Heat.
7. Rename it to TICA315.
8. Open the "Properties" dialog for this chart and click the "Clear" button in the "Process tag
type" tab.
9. In the TICA315 chart, interconnect the following I/O addresses:
– Input for PV: TT315_PV
– Input for Rbk: YC315_FB
– Output: YC315_C
10. Assign the controller block parameters.
– Set the TI input parameter to the value 30 on the controller.
– Scale the process value to the range 0 ... 200.
11. Close the TICA315 chart.
12. Open the process object view in SIMATIC Manager and use the tree structure in the left
window pane as well as the "General" tab in the right window pane to create copies of the 3
charts from the M110 hierarchy folder:
…Storage\B410\LIA414
…Storage\B410\YS411
NS113 …R310\Mixing\NS316
…R310\Draining\NS313
13. In the right window pane, switch to the "Signals" tab and divide the table so that the "Chart"
and "Signal" columns are arranged next to each other.
14. In the "Signal" column, change the I/O addresses to the correct values. To do this, select
hierarchy folders B410, Dosing, Draining and Mixing.
15. Go to the "Blocks" tab in the right window pane.
16. Select the Johnsson folder in the left pane (tree view).
17. Enter the value 2 in all white fields of the Block icon column.
18. Filter the table contents according to the "Block icon" column with the value 2 and sort by
charts ("Chart" column) in ascending order.
– There should now be 15 rows.
19. Open the symbol table of your AS in the SIMATIC Manager and sort the contents according
to symbols in ascending order.
20. Copy the content of the "Comment" field of suitable I/O addresses from the symbol table
and insert it into the "Block comment" field in the process object view to obtain
representative names for the operator control and monitoring blocks. These names appear
later in the OS.
21. Adapt the Scale input parameter on the input driver block to the correct measuring range for
the 3 new LIA... charts.
22. Finally, do not forget to optimize the runtime properties before you transfer the changes to
the AS.
23. Test each individual device. Use the TICA315 as a "TICA315" trend display.
Why10.3.2 Checkpoint
are all parameters in the "Parameters" tab not displayed
in the process object view?
Why are all parameters in the "Parameters" tab not displayed in the process object view?
A. The number of all block I/Os in a project is so large that it would be
too slow to form the view.
B. The number of displayed parameters depends on the licensing of
the PO view.
C. Only the I/Os marked as parameters are displayed in the
"Parameters" tab of the PO view.
D. The clarity and efficiency of editing in the PO view would otherwise
be limited.
© Siemens 2022 | SITRAIN | 10 Spreadsheet-based engineering with the process object view
• You understand the importance of the OS-AS connections and the plant hierarchy
• You are familiar with the mechanism for creating/updating block icons
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
11.2
ngineering Tools for OS engineering
WinCC is used together with several WinCC options and supplementary tools in SIMATIC
Manager to form a key component of a PCS 7 configuration: the operator station.
Motor ON
Valve closed
Gate closed
Alarm logging
(alarm system) number ()
float cou
begin
Process
Tag logging visualization Programming
(archiving) interface
Logging
Standard
interfaces
OS OS OS
OS terminals 1 client … client 40 client
Terminal bus
ES
OS server OS OS
1 18
server server
Plant bus
• The servers are responsible for communication with the AS, for screens and for archiving
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
tags and messages.
• The client(s) provide the user interface.
Central engineering
Whatever the system architecture looks like, the engineering station is always the source for the
complete configuration. All configuration data is downloaded from the ES to the target system.
OS simulation
The OS runtime of a server must not be activated on an ES! To ensure the possibility of testing
an OS configuration on the ES in runtime without disturbing the active OS server, an OS can be
simulated on the ES.
Single-station system
An OS can be configured as a single-station system.
OS
Terminal bus
ES
Plant bus
AS01 AS64
© Siemens 2022In
| SITRAIN | 11 Basic functions
a single-station for operator
system, control & monitoring
all operator control
and monitoring functionality for a project
(plant/unit) is concentrated in one station. This OS single station can be operated on the plant
bus together with other single-station 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).
Terminal bus
ES/OS
Plant bus
AS01 AS64
The single-station system is the smallest possible configuration. A PC station that represents
both the ES and the OS is created in the PCS 7 project.
If the OS and ES are operated on one computer, you do not have to download the OS because
all the necessary data is already available. Here it's enough to run the "Compile OS" function.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
For small and medium-sized plants, implementation is now also possible in a very flat system
configuration without an OS server. In this case, only OS single-station systems are used, and
the number can be expanded up to a maximum of 8 single-station systems.
• The normal separation into a plant bus and terminal bus in an OS server/OS client structure
does not happen in this case, which means that each single-station station is connected
directly to the AS.
Flat system architecture
• With such a configuration, configuring can be streamlined by duplicating a basic project.
1 2 3
….. ES
Plant bus
Process Historian
S7-400H
The "flat system architecture" was previously released for PCS 7 Version V8.0 SP1 for small to
medium-sized project sizes with up to 8 OS single-station systems and including a redundant
OS single station system.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
This architecture can be expanded to include a web server and web clients (up to 3 web
clients), OPC communication (with OpenPCS 7 license) and SIMATIC Batch.
Terminal bus
MS server OS server
ES
AS
Max. 64 per
OS server
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Terminal bus
ES OS server
MS server
OS Max. 12,000 PO
server
Approx. 7,000 tags
Max. 200,000 configurable
messages
Plant bus
AS
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
After insertion of a PC station with a WinCC application into the multiproject, the OS project is
stored in a subfolder of the project path, as shown in the figure:
Storage location of the OS project
All pictures of an OS
project are located here.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Note The GraCS subfolder contains all process pictures as well as all graphics of an OS project.
Custom graphics can be created and managed in the folder "GraCS >
PCS7CustomPictures".
To enable use of graphics from different multiprojects in your own current OS project, these
must first be copied to the GraCS folder! Process pictures can be copied into the OS project
of the SIMATIC Manager.
To edit the contents of an OS, the OS must be opened from the component view of the
Opening an OS project
SIMATIC Manager: WinCC Explorer then starts.
SIMATIC Manager WinCC Explorer
List of editors:
Each editor opens its own
application window or is part of
the Configuration Studio
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Editor Description
Graphics Designer In the Graphics Designer, you create process pictures that are
displayed for the plant operator on the operator station and
that are used for controlling the process.
PCS 7 provides a function for use when creating process
pictures that automatically inserts all the block icons into the
process picture. Block icons are clear, graphical
representations of a PCS 7 block for which operator control
and monitoring is enabled.
You can insert and dynamize additional graphics objects.
Tag logging The "Tag Logging" editor is an important tool for archiving
measured values.
You can change the parameters for the system archive in Tag
Logging. You can create new archives individually and assign
the process values that you want to archive to these archives.
In this way, you can define a process of archiving that is
tailored precisely to your needs.
The archived values can also be displayed in process mode.
Picture Tree Manager In the Picture Tree Manager, you calculate or update the
hierarchy of the group displays again.
User Administrator In the "User Administrator" editor, you define higher-level user
groups and individual users for which you can define certain
rights.
You define these rights for the OS areas that you have
specified in the plant hierarchy in SIMATIC Manager.
Block list editor The block list editor shows you all blocks that you inserted into
CFCs during ES configuration. Requirements: The OS is
compiled.
You can assign a special picture to a block in the block list
editor. This enables the plant operator to switch directly from
the message list to this picture via the "Loop-in-Alarm"
function.
If you do not assign a special picture, the corresponding
faceplate is automatically called in the "Loop-in-Alarm"
function.
"Process Historian" You can select the data required for the Process Historian.
editor Use the "Process Historian" editor in the WinCC Explorer for
this function.
The "Process Historian" editor is only available if the "Process
Historian Ready Component" is installed.
A WinCC application is preset as a multiple station project in the original state, just as it was
inserted in the PC configuration.
Setting the project type
If the system is to be used as a single-station system, this change must be made in the project
properties:
Note Only members of the SIMATIC HMI user group can edit WinCC projects.
References
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 7.3.2 for more details
on OS project properties.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Manual
The settings for the plant hierarchy affect the content and display of data in the OS. They are
Settingsrelevant
in thetoSIMATIC
the structureManager
of the picture hierarchy and the tag names.
You can select which levels are to be included in the HID through their hierarchy folder names.
Only the hierarchy folders marked for inclusion in the HID have their names included in the HID.
Hierarchy folders that are not selected for inclusion in the name can be used to create additional
"drawers" (for example for supplementary documents such as plant descriptions, process tag
sheets, etc.).
With separator
With this option, you insert a separator in the HID after the names of hierarchy folders of this
level. Separators are used in the textual representation of the hierarchy path to better
differentiate between the names of the hierarchy folders. The "\" character is used as the
separator.
Note: the last hierarchy folder included in the HID is always followed by a separator that cannot
be deselected.
OS area
With this option, you can decide which hierarchy level is to be regarded as the OS area level.
Only the top 3 levels can be OS area levels. The default setting is the 1st level. The definition of
an OS area is necessary for area-specific messages in process mode.
Note When assigning the name, ensure that the tag name does not exceed 128 characters. This
is a requirement for compiling the OS. The name consists of the following elements:
"HID\ChartName\BlockName.I/OName".
The manner in which pictures are arranged within the OS areas (picture hierarchy) can be seen
in the Picture Tree Manager. This tool is a component of WinCC Explorer and is integrated in
WinCC Configuration Studio as of PCS 7 V9.0.
The "Picture tree" is generated during OS compiling, depending on the selected settings of the
plant
Picture Tree hierarchy.
Manager
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
The area buttons are also defined in the settings of the plant hierarchy. The OS area can be
selected from levels 1 to 3. The OS area defines the area buttons.
Effects of the plant hierarchy on the OS areas
OS area
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
The picture hierarchy as is seen in the Picture Tree Manager is reflected in the layout of
selection buttons within the OS areas.
The names of structure tags (blocks) and tags contain the plant designation (HID):
Derivation of the tag structure
Components of the tag name
2
3
1 2 3 4
HID CFC name Block name I/O name
M110/LIA114/MonAnalog.PV_Out#Value
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
When the OS project is compiled, the tags that are required for the data exchange between
AS and OS are created. The resulting tag names are composed of the following elements:
1. Plant designation (HID). This can optionally be defined in the settings of the PH and can be
composed of one or more levels of the PH.
2. The name of the CFC in which operator control and monitoring blocks are configured.
3. The name of the operator control and monitoring block.
4. The name of the operator control and monitoring I/O.
The connection that contains all tags is given the name of the S7 program of the automation
system.
References
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 6.4.3 for more
details.
Manual
Terminal bus
ES
OS
server
Plant bus
AS01 AS02
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
1
2
3
4
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Connections are always configured between WinCC applications (OS) and the CPU modules
(AS).
1. Select the object of the WinCC application.
2. Select the connection partner. If you have begun with a WinCC application, the CPU of the
desired AS is the connection partner.
3. Named connection: Instead of the default connection ID, assign a symbolic name as a
placeholder for network parameters of the connection between the OS and AS. Use a
descriptive name.
4. All connections of the object are displayed in the connection table.
Named connection
This principle is referred to as the "named connection". It is also relevant to redundant OS
servers and OS simulation operation.
Recommendation: Assign the name of the AS involved to the connection. Once the OS has
been compiled, the name appears in the "SIMATIC S7 Protocol Suite" of the WinCC Tag
Management.
References
For further details, see:
[103] PCS 7 V9.1 Engineering System, section 9.14.3 and
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 6.2.2
Manual Information configuration of an OS network connection:
SIMATIC Process control system PCS 7 Operator Station
- How to configure an OS network connection
11.6.2
CompilingCompiling andconnections
and loading loading connections
Download
1. Use the "Save and Compile" button in the element bar of NetPro to start compiling the
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
network configuration.
2. You can load new connections without stopping the AS, select the command "Connections
and Gateways". When the whole HW configuration is loaded, the CPU goes to stop.
3. For OS stations, the loaded connections are displayed in the Station Configuration Editor.
Assign an S7 program
to an OS server.
• Area-oriented: With this setting, you can assign an OS area from the plant hierarchy to an
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
OS server. The advantage of this approach is that PCS 7 itself checks which data pertains
to the corresponding OS server and only compiles this data. Starting with PCS 7 V6.1, this
setting is the default setting.
• AS-oriented: With this setting, you can assign an S7 program to an OS server. In this way,
you specify which OS is supplied with data of which AS. In this mode, all the data of an AS
is assigned to an OS server. This was the default setting in PCS 7 V6.1 and earlier.
References
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 6.5.3 for more
details.
Manual
A large part of the OS data structure is specified in SIMATIC Manager and the configuration
tools for the charts. This data is stored in the project database.
A compile operation transfers all the data that is relevant for the OS to its own OS database:
References
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 6.5.3 for more
details.
Manual
Wizard for compiling the OS
1. Start the wizard for compiling the OS for the desired OS.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
2. The assigned plant areas are displayed.
3. Select the AS program to be compiled.
4. Open the "Select Network Connection" dialog. Select the WinCC unit "Named connection"
in the dialog.
However, the wizard needs additional information for the compilation scope:
References
See [121] PCS 7 Compendium Part A – Configuration Guidelines, section 9.4 for more details.
Manual
Based on the configuration in the plant hierarchy, the technological relationships between the
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 selected
for this purpose. Changes affecting the block icons can be updated directly in the plant
hierarchy. block icons
Deriving / updating
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
1. In the properties of the process picture, you can define whether block icons are created in
this picture.
2. Start the "Create/Update Block Icons" function in the shortcut menu of a hierarchy folder.
3. You make the following settings in the dialog:
– Generation of the displayed process tag name at the block icon. You have various
options for versioning.
– Number of included lower-level hierarchy levels. If CFCs with blocks that can be
operated and monitored are configured on lower levels, these icons are also created in
the picture.
– The zoom factor determines the displayed size of the icon.
– With automatic positioning, icons are arranged on the top left. If the option is disabled,
positions of already existing icons are preserved.
Bild R310
Die Pläne liegen in
der 4. TH-Ebene.
In the "Lower hierarchy levels included" combo box, you set the number of AS hierarchy levels
to be taken into consideration when creating/updating block icons.
The background to this setting is the different description depths between the AS and OS.
On the AS side, the charts are configured at the level of the process tags. The charts are
therefore inserted at the lowest level and only contain the control blocks with the drivers for
process interfacing. In our example, the charts are at level 4.
On the OS side, the objective is different. The pictures do indeed describe the plant for the
lower levels in increasing detail, but not as far as the process tag level. In our project, the lowest
level of the pictures is level 3.
As there are no pictures on the 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.
In a distributed PCS 7 system, OS projects are created on the ES, transferred to the OS
computer after completion and then OS runtime is started there. By default, activating OS
runtime on the ES is not allowed, because this can have an undesired effect on the OS project.
You can find the settings in the WinCC Explorer in the properties of the OS project.
However, if you want to start OS runtime on the ES for test purposes, the "Start OS simulation"
option is available in the SIMATIC Manager. This creates a copy of the OS project and then
starts it. The copy is deleted again after closing.
For combined ES/OS stations, the "Allow activation on ES" option is active by default and
cannot
Starting OS be disabled.
runtime on the ES
Activation of an OS
runtime copy on the ES
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
MessageMessage
line line
Overview area
Button area
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Note The name of the start screen (the first screen after runtime starts) is @[Link].
Button area
Two sets of buttons with standardized operator buttons are defined for process control from the
OS. When you start process mode, button set 1 is displayed. You switch between the button
sets using operator buttons.
References
See [231] PCS 7 V9.1 OS Process Control, section 3.8 for a description of the operator
control functions in the button area.
Manual
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 6.3.8 for global
adaptation of the button sets in a PCS 7 OS.
If you change the setting for the WinCC design, check the
appearance of customized objects and adapt them if
necessary.
Define your
project color
palette.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Select the following design for the appearance of the user interface in process mode:
WinCC 3D.
The following WinCC designs are not supported by PCS 7:
• WinCC Classic
• WinCC Glass
• WinCC Simple
• WinCC Dark
Ensure a uniform setting for the design for all projects of a plant. If you change the setting of the
design, check the display of custom objects and adapt them if necessary.
Keep the setting in the case of a software update. If the setting for the appearance of the user
interface in process mode is changed when a software update is performed, this can cause
more extensive changes.
Note The central color palette and the global design settings can alternatively be called directly in
the Graphics Designer under "Menu > Options" as of PCS 7 V9.0.
Note Always deactivate these settings when the project is used in real operation.
You can make additional settings for the display in the "OS project editor".
As long as different settings are not made in the individual object properties, the global design
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
settings act on all graphic objects in the project.
Note As long as an attribute is determined by the global design, it is static and can no longer be
dynamized. Only a previously made dynamization is preserved and not affected by the
global design.
References
See [104] PCS 7 V9.1 Operator Station – Configuration Manual, section 7.3 for an overview of
the global and specific settings of a PCS 7 OS.
Manual
Block icons
Block icons represent AS functions in the OS.
Generally, the main information (operating states, process values) of a function/process tag
(motor, valve, etc.) is displayed in a block icon. For this reason, PCS 7 provides corresponding
block icons for technological blocks (blocks for which operator control and monitoring is
possible).
The block icons are automatically installed in the process pictures according to the plant
hierarchy and interconnected with the relevant process tags.
Faceplates
Faceplates are used for operator control and monitoring of process values with uniform
visualization.
With a single mouse click on the block icon, a faceplate appears to show more details and to
DF((CSCKK56
enable operations (input of setpoints, limits, etc.).
Faceplates are displayed in a separate window in process mode and can be opened using
Bausteinsymbole – OS Runtime
picture selection buttons, the process tag list, block icons, etc.
Sichtenauswahl
Bausteinsymbol
Faceplate
The faceplates are shown in full on the screen with a resolution of 1280 x 1024. The full-screen
mode (press the F11 key) must also be activated on the Web client.
Status displays
Interlocks
Operating area
13 2 4 6 8 14 12
Views
Standard view
1 3 5 9 10 11 Alarm view
7
Limit view
1. Group display
2. Alarm interlock via faceplate Trend view
3. Alarm suppression via function block (FB) Right-click to open
view in a new Ramp view
4. Alarm acknowledgment
5. Worst signal status window Parameter view
6. Batch display
7. Not used Preview
8. Maintenance request and release
Memo view
9. Memo display
10. Open block views Batch view
11. Back to block icon
12. Pin block
13. Name of block instance
14. Help button
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Status displays
In this area, the status (motor, valve symbol, etc.) is displayed in symbolic form at the top.
Below this, there is additional information and there are jump functions (buttons to call a
faceplate of a different block).
The additional information is intended to help the operator and provides information about the
status of the process instrumentation, for example whether a motor is being simulated or is
undergoing maintenance.
Interlocks
Here, the various interlock types are displayed.
Associated values
In the default view of some technological faceplates, up to two additional auxiliary analog values
can be displayed. For example, these can be used to display the motor current and winding
temperature for a motor.
Scaling of faceplates
You can scale the faceplates from 50% to 200%. The value to be scaled is specified with
internal tag "@APLFaceplateScaleFactor", type: 32-bit value without sign. The default scaling
value is 100.
You can scale the faceplates from 101% to 200% by defining a value in the range from 101 to
200 for the internal tag. You can also scale the faceplates from 50% to 99% by defining a value
in the range from 50 to 99 for the internal tag.
The reference for the calculation is the preset faceplate size of 100%.
References
See [113] PCS 7 V9.1 Advanced Process Library, section 2.3 for more details on the
faceplates.
See [120] PCS 7 V9.1 APL Operator Guide for a description of the main functions of the APL
block icons and faceplates.
Manual
This description is also available by pressing the Help button of an APL faceplate in OS
runtime – appropriate for the open faceplate.
In @[Link]
Normal operation,
alarm high limit Malfunction, with
violation additional status
information
Faceplates
Commands – Commands / Operating
/ Operating mode selection
mode selection
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
The setting for one of the two variants (with or without confirmation) is made project-wide via the
properties of the internal WinCC tag @APLCommandExecutionSteps, which is available in
"Split Screen Manager" category under "Internal tags" of the Tag Management of the OS.
Operation possible
Value bad
Value passivated
External simulation
Message can be
disabled/enabled by the
operator.
Message locked. Internal simulation
Message temporarily disabled.
Operation is enabled.
The operation is not enabled based on the configuration (OS_Perm). Operation not possible
Operation based on the process state is not enabled. (no authorization)
Values, limits, etc. can be changed in faceplates. An APL-specific function is the graphic display
of enabled operations and access control. The operator can distinguish between values that can
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
and cannot be changed. The following can be distinguished:
• Whether operator control is generally disabled for the block
• Whether operator control is disabled for process-specific reasons
• Whether an operator has the required authorization
The value is also input in a separate operating area below the faceplate. You can open this
operating area by clicking on a modifiable value (value with white background). The value can
be changed in the operating area in three ways:
• The value can be changed in discrete increments (e.g. -2.5) via direct operator input with
the buttons.
• A desired value can be set with the slider.
• A value can be directly entered in the entry field. The modified value takes effect at the
block with "OK".
Level 2
Assigned to the
operator function
"Higher process
control"
Level 1
Assigned to the operator function
"Highest process control"
Level 3
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
The following operator authorization levels from User Administration are used in the APL:
• Operator authorization level = 0
No process control, only monitoring.
• Operator authorization level = 1 (level 5 in the User Administrator)
Process control (e.g. switching between "Manual"/"Automatic", change setpoints and tags).
• Operator authorization level = 2 (level 6 in the User Administrator)
Higher process control (e.g. changing limits, control parameters and monitoring times).
• Operator authorization level = 3 (level 1100 in the User Administrator)
Highest process control (simulation of process values). The operator authorization enables
the following inputs:
– Turning the simulation on and off in the parameter view, simulation of values already
requires Operator authorization level 1
– Turning the release for maintenance on and off in the parameter view
• Operator authorization level = 4 (level 1101 in the User Administrator)
Advanced operation 1 (user-defined project-specific operator authorization)
• Operator authorization level = 5 (level 1102 in the User Administrator)
Advanced operation 2 (user-defined project-specific operator authorization)
Instance-specific authorizations can be assigned depending on the user management and the
access authorization. For example, controllable blocks have the input parameter "OS_Perm",
which enables you to implement customized control strategies for operators by specifying
enabled operations for them.
References
See [113] PCS 7 V9.1 SP2 Advanced Process Library, section 2.3.3 Operator control
permissions.
Manual
From a faceplate, it is possible to open other faceplates. Buttons are available for this purpose
(in the standard view and preview). The relationship between the button and faceplate is
established using input parameters "SelFp1" (button in the standard view) and "SelFp2" (button
in the preview). The buttons are visible and activated as soon as these input parameters are
interconnected with any output parameter of the faceplate to be opened. The labeling is done
for input parameter "SelFp1" or "SelFp2" in the CFC.
In the standard view of some faceplates, you can have up to two auxiliary values displayed,
e.g. motor speed. The value that is to be displayed on the OS must be interconnected with input
"UserAna1" or "UserAna2" in the CFC. The signal status of the associated values is used to
control the visibility of the display fields.
Associated values
You specifyand direct jump
the labeling in the to
CFCother
in thefaceplates
object properties (I/Os > Identifier) of the
[Link] units of the associated values have their own input parameters.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Specification of source,
label and unit of the associated
value
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
References
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
See [120] PCS 7 V9.1 APL Operator Guide for more details on operator control of APL
faceplates and block icons.
Manual
Block icons are installed in the process pictures with the help of the "Create/Update Block
Icons" function.
You can call this function as:
• A sub-step when compiling the OS
• An independent function from the plant hierarchy
Create/update block icons –
A brief description of the sequence of this function:
sub-steps of this function
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
@PCS7Typicals: "Library of block icons"
The "Create/Update Block Icons" function creates copies of block icons whose originals are
contained in the following template picture:
"Typicals" @[Link]
file
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
The OS compiler (more precisely: the "Create/Update Block Icons" function) finds the right
block icons based on their number.
When block icons are created/updated automatically, all block icons in a process picture that
exist in template picture @[Link] but are not derived via the plant hierarchy
are deleted.
For this reason, the same set of ready-made block icons is provided in a @[Link]
file. In this case, the "Type" property is assigned differently in these block icons. From here, you
can copy
@PCSTypicals and the@PCS7Templates
block icons yourself into any picture and connect them to a structure tag (AS block
instance) using the "Connect faceplate to process tag" dynamic wizard.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Procedure
1. Create an OS-AS connection based on MAC- or TCP/IP-addresses.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Result
The OS now reflects the plant and you have familiarized yourself with its creation and operation.
Task
Creating the "M120"
Configure and
the AS and"M130" areas
OS functions for the "M120" and "M130" areas based on a copy of
"M110".
Procedure
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
Result
The AS and OS functions of the M120 and M130 areas are now available and fully functional.
Task
Configuring the level indicators of the tanks
Configure correctly interconnected bar graphs ("Smart Objects > Bar") to visualize the levels in
the tanks.
Procedure
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
1. Open the process pictures "MaterialTanks, Reactors, StorageTanks, M110, M120, M130,
R310 and B410" one after the other.
2. Enable the display of the "Tags" toolbar:
View > Toolbars
3. In the left window pane, open the tree structure of the "ES tags" until folders, charts and
blocks whose values are to be interconnected are displayed. For the bar graph of the
dosing tank "D210", this is the process tag "LIA124".
4. Find a tag with the name "PV_Out#Value" in the right window pane and drag it to the
desired bar graph.
5. Repeat the same procedure for all other bar graphs in the process pictures.
Result
Now the fill level is correctly displayed on the bar graphs.
Which properties
11.12 of an operator system should only be configured at a later
Checkpoints
time?
Which properties of an operator system should only be configured at a later time?
A. Managing the process operators in the User Administrator.
B. Settings for the message and process value archive.
C. Settings from the OS project editor regarding layout.
D. For a multiple-station system, we do not need any clients at this
point in time.
© Siemens 2022 | SITRAIN | 11 Basic functions for operator control & monitoring
If "ModLiOp = 0", the operator can set the operating mode on the faceplate.
Control logic (Open/Close command for a valve)
Selection of the operating mode by the operator
Control logic (Open/Close command for a valve)
VlvL
OpenAut
S CtrL
OpenMan
1
Output driver
CloseAut
R
CloseMan
PIQ
ModLiOp
AutModLi
S
AutModOp
1
ManModLi
R
ManModOp
Feature.Bit4:
0 = Button mode
1 = Switch mode
When selecting the operating mode through the I/Os on the function block, a distinction is made
between button mode and switch mode. This is defined by the "Feature.Bit4".
© Siemens 2022 | SITRAIN | 12 Implementation of manual and automatic operation
The "OpenMan" and "CloseMan" I/Os are used to control the valve in "Manual" operating mode.
These I/Os are not visible by default. They are set by the operator via the corresponding keys
Demonstration
on the OS faceplate. with buttons and switches
YS311 YS312
VlvL OB33 VlvL OB33
Valve - large 4 / 1 Valve - large 5 / 1
T3 OpenAut S4 OpenAut
T4 CloseAut CloseAut
S1 ModLiOp S2 ModLiOp
T1 AutModLi S3 AutModLi
T2 ManModLi ManModLi
T = Button S = Switch
In "Automatic" operating mode, the "OpenAut" and "CloseAut" I/Os (button mode) or only
Examples
"OpenAut" (switchfor
mode)operating mode
are used to control selection
the valve. (manual/automatic)
These I/Os are usually connected with a by the p
program logic or addressed via a sequencer.
0 ModLiOp
2 Based on
AutModLi
switch mode
1 ModLiOp
AutModLi
3
ModLiOp
1 AutModLi
4
ModLiOp
AutModLi
5 6 7 8
1
0
1
0
t
Task
Configure a central manual and automatic switchover for several pumps and drives. The
actuators of the "Material tanks" area should be able to be switched between manual and
automatic mode via a common switch by the operator.
Preparation
Exersice: Configuring a logic to switch between manual and automatic mode of
Make sure that the "Feature.Bit4 = 1" (switch mode) is set for all drives and valves.
all actors
CFC "M-General"
OperatingMode ModLiOp
[OpDi03] [Or04]
Out1 In1 Out
Out2 In2
Out3 In3 YS112 YS122 YS132
In4
ModLiOp ModLiOp ModLiOp
FbkIn1
FbkIn2 AutModLi AutModLi AutModLi
FbkIn3
Procedure
1. Create a new "M-General" folder in the Material tank hierarchy folder. Add an "M-General"
© Siemens 2023 | SITRAIN | Die Implementierung von Hand- und Automatikbetrieb
chart and an "M-General" picture to this new folder.
2. Incorporate the "OpDi03" block from the PCS 7 APL into the master data library.
3. Insert the following blocks into the "M-General" chart and rename them:
– "OpDi03" block, rename to "OperatingMode"
– 2x "Or04" blocks, rename to "ModLiOp" and "AutModLi"
4. Interconnect the outputs "Out1" and "Out3" of the "OperatingMode" operator block as
follows:
– "Out1" with an input of the first "Or04" block, which was renamed "ModLiOp". Invert the
input at the "Or04" block.
– "Out3" with an input of the second "Or04" block, which was renamed "AutModLi".
5. The function block has inputs for feedback ("Fbk1In", "Fbk2In" and "Fbk3In"). Connect the
outputs "Out1", "Out2" and "Out3" to the inputs for feedback.
6. Open the I/O table in the properties of the "OpDi03" block. Search for the following I/Os and
enter the corresponding text in the "Text 1" column.
– "SetOp1" = "Operator"
– "SetOp2" = "Manual"
– "SetOp3" = "Automatic"
7. Interconnect the "Out" outputs of the two "Or04" blocks with the corresponding inputs for
operating mode switching on the "VlvL" and "MotL" blocks of "M110", "M120" and "M130".
8. Compile and load the AS program. Compile the OS.
Result
The "M-General" process picture now contains a block icon that you can use to switch the
operating mode for all actuators in the "Material tanks" area.
You can choose from the following switch settings:
• Operator = The operator can select the operating mode separately on each block.
• Manual = All actuators are in manual mode.
• Automatic = All actuators are in automatic mode.
Task
Implement a logic in the program to automatically transfer material from one of the three
material tanks to the "D210" dosing tank of the "R310" reactor.
The three feed valves of the dosing tank are each to control the valves and pumps of the
corresponding material tank, if these are in automatic mode.
In addition, a textual interconnection is to be created to the future valves of the reactors "R320",
"R330" and "R340" which are currently not yet configured.
Dosing R310
Result
If the actuators in the "Material tanks" area are in "Automatic" mode, the transfer from the
material tanks to the "D210" dosing tank can be started by opening one of the valves "YS211",
"YS212" or "YS213".
Which statements
12.4.3 regarding manual and automatic operation are true?
Checkpoint
• You can control your devices based on the states of other devices.
• You are familiar with the various operating modes and their sequential control.
• You can realize additional sequencers in an SFC with different start conditions.
A sequential control system is a controller with a step-by-step sequence that advances from one
state to the next depending on conditions.
The SFC (Sequential Function Chart) is a sequential control system used to control and
selectively execute basic automation functions (typically created with CFC) by operating state
and operating status changes.
Creating SFCs
You can insert SFCs in the "Charts" folder of the S7 program, or in any folder of the plant
hierarchy. The SFC is automatically inserted in the cyclic interrupt OB that has the "Predecessor
for Insert Position". In the runtime editor, the SFC can be moved like a block or chart.
See [304] PCS 7 V9.0 SP5 SFC for SIMATIC S7 – Programming and Operating Manual
Manual
Tools
Step
Information texts
Transition
Sequencers of an SFC
A newly created SFC initially consists of exactly one sequencer. You create each sequencer in
its own work window.
For each work window, a tab with the name of the sequencer (e.g. RUN or SEQ1) is created at
the bottom edge. You switch between the individual sequencers with these tabs.
A newly created sequencer (menu command Insert > Sequencer > ...) is inserted in its initial
state, consisting of a start step, transition and end step, at a selected position in the SFC.
Structure ofEach newly created SFC already contains a sequence with a start and end step, as well as a
the sequencers
transition in between. You can expand this sequence with the following functions:
Step/transition Simultaneous branch Alternative branch Loop Jump
Step / transition
This inserts a pair consisting of a step and a transition together into the sequencer. The order of
the two elements is determined by the selected installation position.
© Siemens 2022 | SITRAIN | 13 Sequential controls with SFC
Simultaneous branch
If the execution is to be split into two or more sequencers that are to be executed at the same
time, the simultaneous branch is used.
A simultaneous branch consists of at least two sequencers that are processed at the same time.
A simultaneous branch is always preceded by a transition or an alternative branch. The
simultaneous branches end in a simultaneous convergence that is always followed by a
transition or alternative branch.
The successor transition executes only when all actions of the steps at the end of every
associated sequencer have been executed (apart from the "termination" action) and the step
enabling condition is fulfilled (synchronization).
Alternative branch
Behind the selected step for the installation position, there is an alternative of two branches,
each of them has a transition. There is a built-in step behind the alternative branch. Each of
these alternative transitions can be extended again with step/transition elements. In this case,
the branch whose initial transition is fulfilled first is passed through later.
In alternate or simultanious branches, more than two alternative or simultanious branches can
be used at a time.
However, a maximum of 255 steps and 254 transitions can be used in a sequence chain.
Loop
The loop is a special form of an alternative branch, in which the alternative branch branches
upwards to a step that has already been completed, which is thus processed repeatedly.
Jump
The jump is another form of alternate branching that branches out to distant step in the
sequencer.
References
See [304] PCS 7 V9.0 SP5 SFC for SIMATIC S7 –Programming and Operating Manual,
section 12.2 for further details on the topology of sequencers.
Manual
Sequencers work in close cooperation with CFCs. In steps, block inputs in the CFC are mainly
accessed for writing.
Control
Process devices are controlled using the corresponding technological blocks in the CFC.
Generally, automatic mode and the associated input parameters are used for this.
For example, the "OpenAut" input must be used for control of the "VlvL" block. The "VlvL" block
Processing
in turnsteps
receives its connection to the process via the input and output driver.
In transitions, states at block outputs are queried and compared with a target state.
Monitoring
The monitoring of the process (generally as feedback from a preceding command) is via a block
for measured value monitoring, which is interconnected with the associated input driver. This
technological block provides the scaled process value, which is queried in the transition and
Processing transitions
compared to the achievement of the desired value.
Logical operation
of the conditions
Operator
Block I/O to be Value which is
monitored checked
You can configure up to 16 conditions per transition. The conditions can be linked with the
logical operators "AND, NAND, OR, NOR".
You can insert block I/Os as follows:
• Select the block I/O via the selection dialog by double-clicking in an instruction field.
• Drag-and-drop a block I/O from the CFC into the step editor.
• Enter the block I/O manually. You can also create a textual reference in this way.
13.2.6
SwitchingInterconnecting
of block I/Os withblock I/Os with
the Browse the Browse dialog
dialog
1. Open the properties of the step (or those of a transition) with a double-click. You can set the
name in the "General" tab.
2. Switch to the "Processing" tab and double-click on an empty field.
3. In the selection dialog, find the desired tag and select the "Open Structure" command in the
shortcut menu.
4. Select the process value of the structure and close the dialog.
1. Open the properties of the transition (or a step) with a double-click. You can set the name in
the "General" tab.
2. Arrange the properties window and the CFC so that both are visible together on the
desktop.
3. Drag-and-drop the desired connection into a free operand field. You do not have to explicitly
select the structure element here. The first element of the structure is used automatically.
Existing SFC interconnections can also be moved by holding down the ALT key. Note,
Note
however, that all SFC access operations to this I/O are moved.
Since PCS 7 V8.2, the SFC editor has supported the execution of calculations in steps,
transitions or start conditions of the sequencers. For verification, the calculations with current
values are displayed in test mode.
As a result, both simple and complex operations are performed directly in the SFC and no
longer have to be exported to a CFC.
The "Calculation for SFC" dialog box in the SFC editor is used for the configuring. The dialog
box is opened using the "f(x)" button of an instruction row.
References
The objects for the operators (ADD, SUB, MUL, etc.) are created in the chart folder of the
master data library. The functions are listed in [304] PCS 7 V9.0 SP5 SFC for SIMATIC S7 –
Manual Programming and Operating Manual, section [Link].
Note These objects are used only for the calculations in SFC and are not identical to the library
blocks that are available in the CFC Editor, for example.
For configuring a calculation, the corresponding field in the statement line must be empty.
Otherwise, the "f(x)" button is disabled.
Calculations in an SFC
Example
In the following example, an analog value calculation is performed in a step-enabling condition.
3
1 4
2
2. As described previously, select the block output in the left part of the transition. In this case,
a process value output of a temperature controller.
3. A calculation is needed on the right side of the condition. Click on the formula character for
this.
4. Right-click on "Enter the function" to open the "Insert Function" shortcut menu containing a
selection of available functions.
5. In our example, the "SUB" function for subtraction is selected.
7
8
The function has two inputs. Additional inputs can be added for some functions (e.g. Addition,
Multiplication).
6. To interconnect the first input, select this input.
7. Click the "Browse..." button.
8. The valid setpoint of the temperature controller is to be selected as the minuend. Because
the block output is of data type "Structure", another dialog for selection of the structure
element is displayed.
Calculations in an SFC
9. Select the structure element "Value".
Change name
11
10
10. The value 10 is entered as a constant in our example as the subtrahend. The sequencer
© Siemens 2022 | SITRAIN | 13 Sequential controls with SFC
advances when the actual temperature value of the controller has approached within 10
degrees of the setpoint during the heating operation.
11. As the final step, you can change the name of the calculation.
In the properties of a step, you will find three tabs in which you can specify actions/commands:
Initialization
If you configure actions here, they will only be executed once (i.e. for one cacle): At the
transition from the previous step to this step.
Processing
The actions configured here are executed in each program cycle as long as the conditions in
the transition for the transition to the next step are not yet fulfilled - If actions have been
configured in initialization, the configured actions are executed from the cycle after initialization.
Termination
Initialization, processing
If you configure and
actions here, termination
they will only be executed once: At the transition from this step to
the next step.
Cycle
Start Trans 2
Step active
Stop Trans 2
In SFC test mode, a toolbar and status bar are displayed to enable monitoring and control. The
various step control modes influence the behavior of the SFC at the transition from the active
step to the successor step:
SFC in test mode
O Confirmation by operator
Active operating
mode
Acknowledgment button
Operator
commands
Task
Configure a logic so that the operating mode of the actuators of the entire "R310" plant area can
Exercise: be
Preparing
switched manual
over in aand automatic
simple mode
way using for the "R310" reactor
a sequencer.
YS211 YS212 YS213
ModLiOp ModLiOp ModLiOp
AutModLi AutModLi AutModLi
D210
R310-Gen
ModLiOp
YS311
ModLiOp AutModLi
Or04 ModLiOp TICA YC315
In01 Out ModLiOp AutModLi 315
M NS316
AutModLi
AutModLi R310
Or04
In01 Out
ModLiOp
YS312
AutModLi
ModLiOp NS313
AutModLi 2s
Procedure
1. Create a "R310-Gen" CFC in the R310 hierarchy folder and place two digital "Or04" logic
blocks in this chart. Rename these blocks "ModLiOp" and "AutModLi". Switch the "In2" to
"In4" I/Os of the blocks "invisible". These are not required.
2. Connect the "Out" outputs of the "ModLiOp" and "AutModLi" OR blocks to the
corresponding inputs of all valves and drives, and of the controller.
The "YC315" control valve is not created in this project. It is controlled directly via the
Note "MV.PV_Out" and "RBK.PV_In" I/Os of the "TICA315" controller.
Result
All actuators in the "R310" area can now be switched to manual or automatic mode via the
"In01" I/Os of the "ModLiOp" and "AutModLi" OR blocks.
Task
Exercise: Create an initial
Configuring theshort
firstsequencer
sequencerfor dosing a material.
R310-Gen YS211
OpenAut AutAct
ModLiOp ManAct
Or04 Opened
Closed
In01 Out
LIA
PV_Out
214
AutModLi
Or04
In01 Out
Procedure
1. Create a "R310-Seq" SFC in the "R310" hierarchy folder and create a sequencer according
to the following description:
Use the "In1" inputs of the corresponding OR blocks for the interconnection with the SFC to
Note realize the operating mode switchover for the entire reactor area with the commands
"ModLiOp" and "AutModLi".
Table 13-1
Step/transition Description Process tags
No configuration.
No configuration.
Arrange the SFC window in front of the "R310" process picture of the OS runtime so that you
Note can observe the effects of the sequencer.
13.3.3 Checkpoint
What must be changed in the sequencer if a valve is to be controlled in button
Whatinstead
mode must beofchanged in the sequencer
switch mode if a valve is to be controlled in button mode instead of
(Feature Bit.4)?
switch mode (Feature Bit.4)?
A. The valve must be opened with "OpenAut" and closed with
"CloseAut".
B. The "Feature.Bit4" parameter of the valve must first be set to "0".
C. To be able to change the operating mode, 2 I/Os are required:
"AutModLi" (automatic mode) and "ManModLi" (manual mode).
D. You must add further steps to the sequencer.
1 2 3 4
1. Select the area you want to copy and then the "Copy" (Ctrl + C) command in the shortcut
menu.
2. Execute the shortcut menu command "Paste" (Ctrl + V) on a free area of the SFC.
3. Position the cursor between the transition and the step where you want to paste the copied
sequence. The cursor then shows a hand with a green line instead of a crossed-out circle.
4. The names of the newly inserted steps and transitions are automatically given a number or
incremented by one.
Task
Exercise: Expand
Expandthe
thesequencer
sequencerfor the "R310" reactor for dosing, mixing and heating 3 materials.
R310-Gen YSxxx
OpenAut D210
AutAct LIA
ModLiOp ManAct 214
Or04 Opened
Closed YS311
In01 Out
NSxxx TICA
StartAut YC315
AutAct 315
ManAct M NS316
Run
AutModLi Stop LIA
Or04 314
In01 Out TICA AutAct R310
SP_LiOp
SP_ExtLi xxx ManAct
SP_Ext PV_Out
RbkOut
YS312
LIA PV_Out
xxx NS313
2s
Procedure
1. Complete the instructions of the sequencer using the following table.
In the "Automatic" step, the controller must also be switched to external setpoint.
For recurring sequences, you can use the copy and paste function. For example, copy the
Note steps and transitions from "Dosing 1" to "Trans End 1" to the clipboard and paste them once
after the "IsMixing" transition. The steps and transitions are renamed automatically but you
have to adapt the relevant process tags. Repeat the procedure for the 3rd material.
Table 13-2
Step/transition Description Process tags
No configuration.
No configuration.
What happens
13.5.2 in a dosing step if the Hold command is executed?
Checkpoint
Legend
Ready
Operating states
Start
Start
Completed
Cancel
The sequencer OSL is run through independent of the SFC OSL when a sequencer is
© Siemens 2022 | SITRAIN | 13 Sequential controls with SFC
processed. As a result, the sequencer has a state that must be differentiated from the state of
the SFC. For example, the SFC OSL can be in "Holding" state, whereas the sequencer OSL is
in "Run" state (due to processing of the sequencer for the "Holding" state). The processing of
the sequencer OSL is subordinate to the SFC OSL. This means that a status change in the SFC
OSL generally causes a status change in the sequencer OSL.
Legend
Events: Commands/operations/external
signals/internal signals
Event: Error
The current operating state of the SFC OSL can be changed by the following events:
• Commands (e.g. Start, Resume, Hold) in "MANUAL" operating mode
• External signals (e.g. inputs of the SFC or commands from another SFC in "AUTO"
operating mode)
• Internal signals (e.g. commands of own sequencers, from test mode or from SFC
visualization)
• Implicit status change
Operating mode
selection, enabled by
EnAut and EnMan
Provision of the
operating states
Commands in
automatic mode
Enables, external
interlocks and
sequence options in
automatic mode
In the external view, you can configure and interconnect the interface of the SFC for "AUTO"
mode so that the status of the SFC can be determined in test mode and control signals can be
derived from it for the SFC. This allows you to influence the processing of the SFC by the user
program. If the SFC is used in "MANUAL" mode, only the I/Os of the external view that are also
processed in "MANUAL" mode are relevant. The I/Os of the SFC can be interconnected with
other block I/Os or accessed with sequencer instructions.
Ready
Start condition
"Holding"
Start
Start condition (command)
"Starting" Starting Holding
Start Start
End End
Automatic
transition Start condition
Automatic "Held"
transition Hold
Active (command) Resuming Held
Start Start
Start
Start condition Resume
End End
End
"Run" Automatic (command)
transition
Start condition
"Resuming"
1. Add another sequencer to the SFC. Select the "Insert Sequencer at End" command in the
© Siemens 2022 | SITRAIN | 13 Sequential controls with SFC
shortcut menu.
2. Double-click the new sequence. Assign a name in the "General" properties dialog. Switch to
the "Start condition" tab.
3. Insert the corresponding I/O of the sequencer into an empty field. You can do this by drag-
and-drop from the outer view of the SFC, or you can use the tag selection dialog.
4. You can select the value (e.g. Starting) in the right field. The displayed text always stands
for a "1" signal.
Task
Exercise: When
Add the
the"Holding"
sequencer and "Resuming"
is stopped, sequence
all valves are to be closed and all drives to be stopped. If the
sequencer is resumed, the state that was current when it was stopped is to be restored.
The custom "ReacComd" function block is used for buffering the device states. The function
Note block can be taken from the course library.
Procedure
1. Open the "R310-General" CFC and insert the "ReacComd" block. Rename the block
"R310_Comd".
2. Set the invisible input "EN" to "0". Editing of the block is not required.
3. Open the "R310-Seq" SFC and add a new sequence with the name "Holding" and
"Resuming" respectively.
4. Configure the "HOLDING" and "RESUMING" start conditions for this sequence.
5. In the "Holding" sequencer, configure the following steps:
– "Save Commands" – The currently applied values at the I/Os "StartAut" (NS313) and
"OpenAut" (YS211, YS212, YS213, YS311, YS312) are written to the inputs of the block
"R310_Comd".
– "Close Stop All" – The values at the "StartAut" and "OpenAut" I/Os are set to "0".
The transition does not have to be configured.
6. In the "Resuming" sequencer, configure the following step:
– "Resume All" – The temporarily stored values at the "R310_Comd" block are written
back to the "StartAut" and "OpenAut" I/Os of the valves and pumps.
The transition does not have to be configured.
7. Compile and load the AS program. Test the function.
13.8.2
What Checkpoint
can additional sequencers be used for in an SFC?
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
In order to visualize SFC, the OS must be compiled at least once with the "SFC Visualization"
option. All required tags, messages and block icons of the configured SFC are generated in this
process. Subsequently, icons can be created later with the "Create/update block icons" function.
Compiling the OS
When compiling the OS, the "SFC Visualization" option must be selected. The block icons are
transferred to the corresponding process picture depending on the plant hierarchy.
Creating block icons
2 OS runtime
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
1. In the shortcut menu of the SFC, you can open the properties and enter an icon variant.
2. When compiling the OS, ensure that the "SFC Visualization" option is selected.
If you subsequently set another icon variant, it is sufficient to call the "Create/update block
icons" function in the plant hierarchy.
Reference
See [304] PCS 7 V9.0 SP5 SFC for SIMATIC S7 – Programming and Operating Manual
Manual
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
You can configure additional SFC functions at any objects in the process picture. The following
wizards are available for this purpose:
14.2.3 Controls
Controls for for sequential
sequential control systems
control systems
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
Ready-made, pre-defined controls are available for PCS 7 that you can use to display and
control SFC. The controls are "PCS 7 SFC Control" and "PCS 7 SFC MultiChart Control".
Configuring
14.2.4 SFC Multichart
Configuring Control
SFC Multichart Control
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
1. Drag the "OCX Control" object from the Graphics Designer catalog into the process picture.
2. The "Insert a Control" dialog then appears. Select "PCS 7 SFC MultiChart Control" and
confirm your selection.
3. The control then appears in the process picture. Adapt the size and position.
Configuring SFC Multichart Control
5
6
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
SFC-Typ
SFC CFC
An SFC type is created in a chart folder as a function block (e.g. in a library or directly assigned
to the AS).
Steps and transitions access a dedicated interface of the SFC type. The SFC type only receives
the connections to the desired measure points by initiation in a CFC plan.
Instances
An SFC instance is derived from an SFC type and has identical properties to the SFC type
SFC-Typ
initially. executableSFC-Instanz
AnSFC sequentialplatziert
controlinCFC
einem CFC-Plan
system is produced only after the SFC instance is
interconnected with block parameters of the basic automation in CFC.
© Siemens 2022 | SITRAIN | Die Implementierung von Hand- und Automatikbetrieb
By© default,
Siemens 2022the interface
| SITRAIN of an SFC
| Die Implementierung type
von Hand- corresponds to the external view of an SFC, expanded
und Automatikbetrieb
to include several parameters specific to the SFC type. However, you can configure additional
parameters in order to create an application-specific interface (i.e. features).
BATCH
Correspondingly configured SFC types can represent an "Equipment Phase" in a SIMATIC
BATCH application.
References
See [304] PCS 7 V9.0 SP5 SFC for SIMATIC S7 - Programming and Operating Manual,
section 5.5.2 for more details.
Manual
Task
Expand the SFC already completed in the AS program with a visualization on the OS with the
standard symbol. You also create the possibility in the overview screen of the reactors to clearly
SFC visualization
display the previously created SFC together with the SFC of the reactors "R320" to "R340",
which will be generated later.
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
Procedure
1. Select variant 2 as the block icon for the SFC.
2. Compile the OS with the activated option for SFC visualization.
3. Add a PCS 7 SFC MultiChart control in the overview picture of the reactors, "[Link]",
to get an overview of the SFCs of all reactors in the future. (Only one SFC can be inserted
into the control at this time, the other three will be added later).
– Select a "Control" object in the "Standard > Smart Objects" palette of the Graphics
Designer.
– When you click in the process picture, a dialog with a large selection of registered
ActiveX controls opens. It is sorted alphabetically.
– Once you have inserted the PCS 7 SFC MultiChart, double-click to open the properties.
– You use a button to open an SFC browser to select the desired SFC.
4. Test the SFC control in the PCS7 SFC MultiChart Control after activating the runtime mode
of the OS.
Result
Now you have different possibilities to open the operating window of the SFC in runtime. You
can see the status of the SFC in the SFC Multichart Control. The control can be extended later
with additional SFC.
Task
Optional: Configuring additional SFC buttons
Configure an additional control and button functions for visualization of the SFC.
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
Procedure
1. Insert a PCS7 SFC control in the picture of "[Link]". Double-click again to open the
properties and select the desired SFC using the "Assign SFC" button.
2. Create a button with the label text "SFC" in the picture of "[Link]".
3. Use the appropriate Dynamic Wizards to assign the following two mouse click actions:
– Left click: Open the SFC "R310-Seq"
– Right click: Open the SFC browser
Result
You have configured additional options for monitoring and controlling the SFC in runtime.
14.4.3
Which Checkpoint
possibilities do you have to operate an SFC if you have not configured
optional functions?
Which possibilities do you have to operate an SFC if you have not configured optional functions?
A. A block icon is available in the process picture, which displays a
faceplate when clicked.
B. An "SFC MultiChart Control" is created by the OS compilation.
C. The SFC browser is available in the button bar by default.
D. If you want to operate the SFC in runtime, you have to configure
corresponding functions in the Graphics Designer.
© Siemens 2022 | SITRAIN | 14 Monitoring and control of the sequential control systems
Attachment A – Documentation
and Online Support
A 1. Documents available after PCS 7
installation
A 1.1. Manuals supplied
Pre-installed manuals
In section 3.1 "General", the PCS 7 readme file "[Link]" has a full list of all PCS 7 electronic manuals that are
available locally after installing PCS 7.
The following PCS 7 documentation is available on the computer after the installation of PCS 7:
A-1 SITRAIN
SIMATIC PCS 7 - Attachment A
Start > All Programs > Siemens Automation > SIMATIC > Documentation > English
Start > All Programs > Siemens Automation > SIMATIC > Product Info > English
The "PCS 7 Documentation Portal Setup" required for this is available for download from Industry Online Support under
the entry ID 109479444:
Updating the SIMATIC PCS 7 online help system and the system documentation
The PCS 7 help system that can be called up from the SIMATIC Manager is updated at regular intervals as of PCS 7 V8.0
This allows service packs of PCS 7 and the products to be registered in the system documentation and published.
You need to implement the PCS 7 help system manually using Copy&Paste in the PCS 7 installation:
1. Download the zip file of the help system from the Service & Support portal.
2. Extract the help files to a folder.
3. Copy all help files into the installation of PCS 7 in the folder
Siemens > STEP7 > S7BIN.
When you then reopen the PCS 7 help system it is updated.
A-2 SITRAIN
SIMATIC PCS 7 - Attachment A
Access to the PCS 7 System documentation via the online help
As of PCS 7 V6.0 SP3, you can access the entire PCS 7 system documentation in the format of the online help from the
SIMATIC Manager.
• You open the online help for the "PCS 7 Basic Documentation" with the menu command "Help > Contents...".
A-3 SITRAIN
SIMATIC PCS 7 - Attachment A
[Link]
• Is the most important readme file in PCS 7.
[Link]
• Contains information and additions to the manuals of the PCS 7 system documentation, and is more up-to-date due to
the editorial deadlines for the electronic manuals.
[Link]
• "What's new in PCS 7?" contains an extract of all new features and changes in the current PCS 7 version.
A-4 SITRAIN
SIMATIC PCS 7 - Attachment A
process control manual tailored to the concrete PCS 7 plant for the operator on the customer
side
A-5 SITRAIN
SIMATIC PCS 7 - Attachment A
1
2
Integration of documents
To integrate or update documents, the user must have administrator rights and the hidden folders must be visible.
Follow the instructions below to integrate/update the documentation:
1. The downloaded package (ZIP file) must be stored in the following directory path:
ProgramData > Siemens > PUDManager > Public > BaseSnippetsRepository > PendingUpdates
NOTE The storage location may differ if you using other PuD versions. You'll find detailed instructions and
information in our download entry.
2. Select the PUD Manager Help Viewer and click on "Open as administrator" in the shortcut menu.
3. Select "Settings" in the menu.
4. In the document overview panel, select all the documents you want to add and click the "Update selection" button.
NOTE You will receive a message as soon as all documents have been integrated. Make sure that you wait
for this message. The integration takes several minutes and depends on the number of documents in
the package.
A-6 SITRAIN
SIMATIC PCS 7 - Attachment A
5. Restart the PUD Manager Help Viewer.
Language-dependent
availability of documentation
Click the following link for further information on PUD Manager Help Viewer and the available documentation packages
for SIMATIC PCS 7:
Plant and User Documentation Manager for SIMATIC PCS neo and SIMATIC PCS 7 - The modular help portal
A-7 SITRAIN
SIMATIC PCS 7 - Attachment A
The compendium directly reflects the recommended method of configuration, while evaluating numerous practical
experiences. The description does not go into the application itself but relates to handling the project and the parameter
settings of the components it contains.
The compendium is divided into several parts:
• SIMATIC Process Control System PCS 7 Compendium Part A - Configuration Guidelines (V9.1)
• SIMATIC Process Control System PCS 7 Compendium Part B - Process Safety (V9.1)
• SIMATIC PCS 7 Process Control System Compendium Part C - Equipment Phases with SFC Types (V9.1)
• SIMATIC Process Control System PCS 7 Compendium Part D - Operation and Maintenance (V9.1)
• SIMATIC Process Control System PCS 7 Compendium Part E – Hardware Installation (V9.1)
• SIMATIC Process Control System PCS 7 Compendium Part F - Industrial Security (V9.1)
Selecting versions
You can download the documents as entries in the Product Support of Industry Online Support. Search for
"Compendium".Some parts contain additional checklists that support documented project processing.
A-8 SITRAIN
SIMATIC PCS 7 - Attachment A
Add-on catalog ST PCS 7 AO, Add-ons for the SIMATIC PCS 7 Process Control System
For PCS 7, numerous extra add-on products were developed by Siemens or external partners. These software
packages and hardware components released by the system manufacturer allow a cost-effective
implementation of SIMATIC PCS 7 for special automation tasks.
NOTE You can find ordering data for SIMIT and the virtual controller in the catalog ST PCS 7 T.
A-9 SITRAIN
SIMATIC PCS 7 - Attachment A
Come into the world of SIMATIC PCS 7 with an interactive system overview.
A-10 SITRAIN
SIMATIC PCS 7 - Attachment A
• Manuals
• FAQs
• Application examples
• Multimedia content
In Industry Online Support convenient functions bring you directly to the required information. Online support - always
the first step - 24 hours a day, 365 days a year.
SIEMENS Industry Online Support
Detailed how-to videos demonstrating the benefits and use of the Industry Online Support can be found here:
A-11 SITRAIN
SIMATIC PCS 7 - Attachment A
A 3.1. Overview
12 10 2
3
4 5 6 7
Always available 9
(top right):
11
1. Registration: You want to use the complete information offer of Online Support and profit from the options for
personalization in mySupport?
Then register for Online Support and log in before you use it. And this is all free of charge. Make the most of your
Industry Online Support!
2. Global search: The input box of the global search is always available at the top right. The global search searches all
entries of Industry Online Support and presents the results clearly on a separate results page.
In all specific filter areas, there is a further input box available to start the search. This search works with the filters,
and searches only entries that match the filter values you have selected.
3. Direct selection of the basic parts of the portal:
Product support, application examples, services, the online support forum and the personal working area mySupport.
4. Search for product information: Product support is the central contact point for all information on the industrial
products of Siemens. Most of the information in product support is stored in the form of entries. Depending on the
type of entry you find different information and data. You can use filters to reduce the displayed list of entries to the
required information.
Many functions and areas of product support are only available to you if you have logged in to Online Support. These
include, for example, saving and loading filter settings or downloading software packages.
5. Overview of our services: You would like to get information about the service offer from Siemens, find contacts or find
concrete instructions on the procedure for the individual services? The Service catalog provides you with the
possibility of getting comprehensive information.
You call up the Service catalog via the "Services" navigation point that you will find on every page.
A-12 SITRAIN
SIMATIC PCS 7 - Attachment A
6. Forum – communication platform for products from Siemens Industry.
In the Technical Forum, you will meet a strong community that exchanges information about products from Siemens
Industry. The community discusses questions, for example relating to configuration, commissioning and product
details. Naturally, non-registered users can also view the contents and search through them. If you want to use other
functions of the Technical Forum, log in with your user name. Then you can also ask a question and take part in the
discussion.
7. mySupport is your personal working area in Industry Online Support. Here, you can put together information that is
important in performing your daily tasks. mySupport provides you with a series of tools that support you in this.
To make your important information simply and efficiently accessible at all times, structure the contents according to
your ideas. You can create folders and name them freely, for example, according to your projects or products. You can
also use your own tags for indexing and add personal notes – completely according to your needs.
8. The mySupport Cockpit is located on every page in Online Support on the right-hand side of the page. If you are
logged in, here you will find direct links at all times to your favorites or to the last entries you viewed in Online
Support.
The mySupport Cockpit also informs you about new personal messages, status changes of support requests or with
completed jobs of the CAx Download Manager. At the relevant entry, a number in brackets shows how many new or
modified objects there are.
9. Copying a link and printing an entry: You can copy the address of the selected entry to the clipboard or print the
entry.
10. Queries to Technical Support (support request)
You have a technical question and want to receive support finding the right answer?
With the support request form in Online Support, you can put the question to our Technical Support directly without
detours. To do this, describe your question in a few steps and you will immediately receive proposed solutions. If your
question is still not answered after this, a specialist for your topic will make contact with you within the briefest period
of time.
11. Mobile use with an app - make sure you have Siemens support when you are on the move! With our Industry Online
Support app you have access to more than 300,000 documents anywhere and at all times. Regardless of whether you
have a problem implementing a project, require support to eliminate problems, want to expand or replan your system.
12. You will find instructions on working with the app and a guide to the most important innovations in the HelpCenter.
A-13 SITRAIN
SIMATIC PCS 7 - Attachment A
• Certificates
Approvals for marketing in other countries, certificates relating to the successful test of nominal data according to a
specific standard or for special use scenarios (documents in PDF format).
• Application examples
Application examples help you solve your automation tasks. To achieve this, you have examples and tools,
background knowledge, functional descriptions, handling instructions, performance data etc. available. It is not the
individual product that is in the foreground but rather the system-wide interaction of the products.
• Characteristics
Pictorial representation of characteristics, for example, the current/time behavior of causes of overcurrent (documents
in PDF format).
• Product news
Product-related current information from marketing and sales e.g. sales and delivery releases for new products.
• Technical specifications
Technical operating figures of the selected product in a clear table form.
A-14 SITRAIN
SIMATIC PCS 7 - Attachment A
Filter functions (1)
With the filters in product support, you can find all required information about your question quickly, simply and
conveniently or simply only for one product. Use the filters to reduce the large amount of information available to the
content that is of interest to you.
Depending on what you are looking for, the following filters are available:
• Product tree
• (Individual) product
• Entry type
• Date
You can, however, also simply enter one or more terms in the search box. As soon as you have made the settings for a
filter, the entry list provides you with all suitable results. You can add filters or change existing filters at any time to
narrow down your search even further.
To remove individual or all filters, click the "X" beside a set filter or click on the button "Clear all filters".
A-15 SITRAIN
SIMATIC PCS 7 - Attachment A
A so-called PCS 7 quick start (start page, landing page) allows you to find all PCS 7 relevant topics, technical information
and solutions quickly.
SIMATIC PCS 7 Overview
This start page has many advantages:
- PCS 7 films, interactive demonstrations, FAQs, new application examples and much more are listed and ordered at
a glance.
- All available solution examples and unit templates are listed and briefly described in a PDF document.
- Icons simplify the classification of documents, e.g. contains archived projects/code, step-by-step instructions,
performance data, etc.
- The desired PCS 7 version can be selected directly so that all entries are then filtered for this version.
A-16 SITRAIN
SIMATIC PCS 7 - Attachment A
To be able to query the compatibility statements you require, in the first step you need to decide on a "main component"
(WinCC, PCS 7, STEP 7, etc.).
A-17 SITRAIN
SIMATIC PCS 7 - Attachment A
You can add further components to this "main component" (e.g. operating systems, virus scanners, etc.).
Once you have selected the desired component, you can display the compatibility statement by clicking the "Show
compatibility" button.
A-18 SITRAIN
SIMATIC PCS 7 - Attachment A
By setting up individual notifications and newsletters for yourself, you will stay up to date regarding
Note your Siemens products. The how-to videos of the Industry Online Support show you how to store
personal messages in MySupport.
A-19 SITRAIN
SIMATIC PCS 7 - Attachment A
To distinguish the types of information, mySupport is divided into so-called information categories (e.g. personal
messages, filters, tags). Each category provides specific functions; however, the operating concept is uniform so that you
can work quickly and simply.
All contents in the individual categories of mySupport are only accessible to you personally.
For this reason, you must log in to Online Support before using mySupport. You must register before the first login. To
access your personal information in the most efficient way, you can opt to remain logged in (see registering and login).
Without logging in, only general information on the individual categories is visible.
Favorites
Favorites are your personal bookmarks in Online Support. Similar to the favorites or bookmarks of your browser (e.g.
Internet Explorer), you have access to your preferred entries quickly – and from anywhere.
You can select your favorites in Product Support, Forum and Service area and save them in mySupport, organize them in
your own folder structure, call them up at any time and apply tags to them (keywords). You can access your saved
favorites either via the "Favorites" category in mySupport or via the "Favorites" link in the mySupport Cockpit in the right-
hand navigation area.
Tags
If you have marked an entry as a favorite, you can also apply your own keywords to it ("tag"). From these keywords, a "tag
cloud" is generated automatically in the mySupport Cockpit the individual terms in the tag cloud serve at the same time as
links. The more often you use a term as a tag, the larger it is displayed. If you click on a tag, your favored entries are
filtered - you cannot access your information more quickly.
A-20 SITRAIN
SIMATIC PCS 7 - Attachment A
Manage notification
You want to be informed when there is something new relating to your points of interest? Then let Online Support notify
you automatically.
If you are interested in numerous entries, identify these with a filter. If you are interested in only a single entry, mark this
as a favorite. Both in mySupport filters and in favorites, you can set how you want to receive notifications. To do so, select
the "Set options" item in the toolbar According to your configuration, the "Notifications" category lists all active
notifications – this gives you a quick and easy overview.
NOTE The previous newsletter from the "old" Online Support portal has been replaced with the new function
of notifications. The newsletters you subscribe to are automatically continued as new notifications.
A-21 SITRAIN
SIMATIC PCS 7 - Attachment A
|A h A|D i d O li S
You want to bundle documents that are particularly important for you?
In mySupport you can create your own personal document library in the "Documentation" category. You can use this
library online in mySupport, or also generate it in different formats for offline use.
Naturally, you can also share your personal library in mySupport with other mySupport users. This allows you to efficiently
create a collection of relevant documents for your topics that you can share with colleagues. Regardless of whether you
are alone in the office or together with colleagues, work at different locations or need to take trips, you have access to
your personal document collection from anywhere.
NOTE This function was previously available in MyDocumentationManager for configurable manuals. Due to
the integration in mySupport it will be even simpler for you to include entries in your library. In
addition to this, the total range of entries is now available to you. You can include all entries of
Industry Online Support in your library, i.e. also FAQs or product notifications.
And if you have already worked with MyDocumentationManager all the libraries you have created
naturally remain available in mySupport – None of your work will be lost.
A-22 SITRAIN
SIMATIC PCS 7 - Attachment A
Setting up a personal library
1
4 2 3
In your personal library you can create your own folder structure as familiar to you from the folder structure used for file
storage. You can save the entries from Online Support in the folders and therefore set up your own personal collection of
documents. You can structure the library to meet your exact requirements e.g. according to the structure of your plant or
projects.
You can adopt entries directly from the entry list or from the entry display into your personal library.
By adopting an entry into your personal library, you create a copy of the original entry for your own use. This copy is then
available to you until you delete it again. This applies even if the original entry has been revised or deleted in Online
Support.
1. After you have created a library, you can change it again at any time in "mySupport Documentation". With the
"Configure" function in the shortcut menu, in addition to the content area, the structure of your personal library is
shown in a second area. This allows you to make considerable changes very conveniently using drag and drop.
The fully configurable manuals represent a special feature. If you insert a manual of this type in a folder, not only the
entry appears in your folder but the entire chapter structure along with the content is entered in your folder. This
makes it simple to navigate through the manual. And if you only require parts of a manual, you can enter these parts
only in your library. You can modify and restructure an entered chapter structure later to any extent you require.
2. You can be informed automatically of changes to the entries contained in your personal documentation. With the
"Settings" button, you can enable and adapt the automatic update service. You select the language, the interval (day,
week, month, quarter) and the standard according to which warning notices of pending updates will be given (ISO,
ANSI).
3. Using the update function, you can synchronize your personal documentation with the current version of the entries.
In this way, your documentation always remains up-to-date. With the "Update" button you can adopt or discard
pending updates.
4. My exports: When you export, the content of the selected folder and all subfolders is transferred to a file that you
save and edit further. You can carry out this export from each folder of your library - regardless of whether you
yourself created the folder or transferred it from a standard document. (In MyDocumentationManager, this function
was available with "Generate".)
A-23 SITRAIN
SIMATIC PCS 7 - Attachment A
A 5. Support request
• Here, select your product and use case as precisely as possible; avoid selecting the item "Other" if possible. In this way
you guarantee optimum support by our experts and suitable proposed solutions.
• Have other users already had a similar problem? Common questions and solutions are made available to you here.
Have a look at it – it will certainly be worth it!
• Describe your problem in as much detail as possible. Pictures or explanatory attachments give our experts the
opportunity to narrow down your problem and to work out solutions. Several attachments up to a size of 10 MB per
file can be uploaded.
• Each time you send, check your personal contact information and the data you have entered. When complete you also
have the option of printing out the summary.
As a logged in user you can track the status of your requests online. To do this, go to "My requests" in the "Requests"
category in mySupport.
A-24 SITRAIN
SIMATIC PCS 7 - Attachment A
• A scan function for quickly capturing the product you are searching for
• Access to the global community for knowledge sharing
• A wide variety of entries and products available offline
• A convenient way to send queries to Technical Support (Support Request)
Support Requests
Support Requests to to
Technical Support
Technical Support
Search
Search function function
Scan function
Scan function for for
Siemens products
Siemens products
A-25 SITRAIN
SIMATIC PCS 7 - Attachment A
1
2
1. On the left-hand side you will find the so-called Conference tree. Here, you can navigate through the individual
discussion areas.
2. With the Conference overview, you are in the central discussion area of the Technical Forum. The community meets
here to exchange information about technical questions about all the products from Siemens Industry.
A-26 SITRAIN
SIMATIC PCS 7 - Attachment A
3. In the Forum Management, you will find your personal control center for the Technical Forum. Here, you can manage
your specific profile data and filters.
Conference filters
Add conferences to your personal filter of preferred conferences. With this you can activate a notification that always
informs you when new topics are started in these conferences.
There is a Quicklink in the Technical Forum to an overview page that contains all the topics of your preferred conferences.
Managing a profile
In the profile management, you will find interesting information and functions:
• You can see your rank and any special rights as well as your progress in the ranking.
• You can store a signature and a personal description for your profile in the Forum.
• You have direct access to the quicklinks to obtain an overview of all topics to which you have contributed.
User filters
In the Technical Forum, you have found a user who contributes particularly interesting entries? Then add this user to the
list of your "preferred users".
With this you can activate a notification that always informs you when the user has created a new entry.
There is a Quicklink in the Technical Forum to an overview page that contains all the topics of your preferred users.
A-27 SITRAIN
SIMATIC PCS 7 - Attachment A
Create a new
entry for the topic
Respond
to an entry
A-28 SITRAIN
SIMATIC PCS 7 - Attachment A
Creating a new entry
You want to create or format a new entry? The entry editor provides you with all the necessary functions.
To prepare your entry optically, there are many functions available. By using pictures you increase the understandability
of your entry.
• With "Add attachment" you can upload a file from your hard disk and publish it to the forum.
• You want to check how your entry will actually appear prior to publication? For this, there is an entry preview
available.
• You would like to consider the topic again for which you are creating an entry? Please use the link via the input area
(right mouse button -> open in a new tab or window).
• Use the link "Answer" to open the entry editor to write an answer without quoting the entry.
• If you want to quote the entry or just a part of it, use the "Quote" link. The content of the quoted entry is then
displayed in the entry editor.
A-29 SITRAIN