WCA Faceplate PIDCtrlV2 en

Application example  05/2016
TIA Portal Example Block

“PIDCtrlV2”
WinCC Comfort/Advanced V13 SP1, STEP 7 V13 SP1, S7-1200/S7-1500
https://support.industry.siemens.com/cs/ww/en/view/66839614
Table of contents
Warranty and liability
Note The Application Examples are not binding and do not claim to be complete
regarding the circuits shown, equipping and any eventuality. The Application
Examples do not represent customer-specific solutions. They are only intended
to provide support for typical applications. You are responsible for ensuring that
the described products are used correctly. These Application Examples do not
relieve you of the responsibility to use safe practices in application, installation,
operation and maintenance. When using these Application Examples, you
recognize that we cannot be made liable for any damage/claims beyond the
liability clause described. We reserve the right to make changes to these
Application Examples at any time without prior notice.
If there are any deviations between the recommendations provided in these
Application Examples and other Siemens publications – e.g. Catalogs – the
contents of the other documents have priority.
We do not accept any liability for the information contained in this document.
Any claims against us – based on whatever legal reason – resulting from the use of
the examples, information, programs, engineering and performance data etc.,
described in this Application Example shall be excluded. Such an exclusion shall
not apply in the case of mandatory liability, e.g. under the German Product Liability
Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life,
body or health, guarantee for the quality of a product, fraudulent concealment of a
 Siemens AG 2016 All rights reserved
deficiency or breach of a condition which goes to the root of the contract

(“wesentliche Vertragspflichten”). The damages for a breach of a substantial
contractual obligation are, however, limited to the foreseeable damage, typical for
the type of contract, except in the event of intent or gross negligence or injury to
life, body or health. The above provisions do not imply a change of the burden of
proof to your detriment.
Any form of duplication or distribution of these Application Examples or excerpts
hereof is prohibited without the expressed consent of the Siemens AG.
Security Siemens provides products and solutions with industrial security functions that
informa- support the secure operation of plants, systems, machines and networks.
tion In order to protect plants, systems, machines and networks against cyber
threats, it is necessary to implement – and continuously maintain – a holistic,
state-of-the-art industrial security concept. Siemens’ products and solutions only
form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems,
machines and networks. Systems, machines and components should only be
connected to the enterprise network or the internet if and to the extent necessary
and with appropriate security measures (e.g. use of firewalls and network
segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be
taken into account. For more information about industrial security, please visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them
more secure. Siemens strongly recommends to apply product updates as soon
as available and to always use the latest product versions. Use of product
versions that are no longer supported, and failure to apply latest updates may
increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial
Security RSS Feed under http://www.siemens.com/industrialsecurity.
PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

Entry ID: 66839614, V1.0, 05/2016 2
Table of contents
Table of contents
Warranty and liability ................................................................................................... 2
1 Task ..................................................................................................................... 5
2 Solution............................................................................................................... 7
2.1 Overview of the overall solution ........................................................... 8
2.2 Hardware and software components ................................................... 9
2.2.1 Validity .................................................................................................. 9
2.2.2 Components used ................................................................................ 9
3 Basics ............................................................................................................... 10
3.1 Library objects .................................................................................... 10
3.2 Faceplates .......................................................................................... 11
4 Mode of Operation ........................................................................................... 12
4.1 Faceplate icon .................................................................................... 12
4.2 Interfaces of the faceplate icon .......................................................... 16
4.3 Screen window ................................................................................... 17
4.4 Components of the screen window .................................................... 19
4.4.1 Faceplate “PID_1_Overview” ............................................................. 20
4.4.2 Faceplate “PID_2_Messages” ............................................................ 21
4.4.3 Faceplate “PID_3_Graphs” ................................................................ 22
4.4.4 Faceplate “PID_4_Parameters” ......................................................... 22
Faceplate “PID_5_ActualValue” ......................................................... 23
4.4.5
4.4.6 Faceplate “PID_6_Setpoint” ............................................................... 23
4.4.7 Faceplate “PID_7_Limits” ................................................................... 24
4.4.8 Faceplate “PID_8_Service” ................................................................ 24
4.5 Interfaces of the screen window ......................................................... 25
4.6 Tags of the UDT ................................................................................. 26
4.6.1 Tags with function tasks ..................................................................... 26
4.6.2 General tags – Signal values ............................................................. 29
4.6.3 General tags – Controller parameters ................................................ 30
4.6.4 General tags – Limit values ................................................................ 33
4.6.5 Tags with function tasks without controller connection ...................... 37
4.7 Control and status signals .................................................................. 38
4.7.1 Processing of switching commands in the controller ......................... 38
4.7.2 Evaluating process states and displaying them in WinCC ................. 40
4.7.3 Actual value Real value / S7 periphery .............................................. 42
4.7.4 Calculating the manipulated variable ................................................. 44
4.7.5 Toggling between local and remote operating mode ......................... 46
4.7.6 Determining controller values ............................................................. 48
4.7.7 Manipulated variable limit ................................................................... 50
4.7.8 External error / block locked ............................................................... 53
5 Commissioning the Application ..................................................................... 55
5.1 Configuring the STEP 7 block ............................................................ 56
5.2 Configuring the WinCC Advanced faceplates .................................... 57
5.2.1 Opening the global library .................................................................. 57
5.2.2 Integrating the library elements into the project ................................. 58
6 Operating the Application ............................................................................... 65
6.1 Navigation .......................................................................................... 66
6.2 Faceplate icon .................................................................................... 69
6.3 Screen window ................................................................................... 71
6.3.1 Menu system und “Close” button ....................................................... 71
6.3.2 Faceplate “PID_1_Overview” ............................................................. 71

Entry ID: 66839614, V1.0, 05/2016 3
Table of contents
6.3.3 Faceplate “PID_2_Messages” ............................................................ 73

6.3.4 Faceplate “PID_3_Graphs” ................................................................ 73
6.3.5 Faceplate “PID_4_Parameters” ......................................................... 74
6.3.6 Faceplate “PID_5_ActualValue” ......................................................... 75
6.3.7 Faceplate “PID_6_Setpoint” ............................................................... 75
6.3.8 Faceplate “PID_7_Limits” ................................................................... 76
6.3.9 Faceplate “PID_8_Service” ................................................................ 77
7 Block Interfaces ............................................................................................... 78
7.1 Input parameters ................................................................................ 78
7.2 Output parameters ............................................................................. 80
8 Additional Information .................................................................................... 81
9 Links & Literature ............................................................................................ 82
10 History............................................................................................................... 83

Entry ID: 66839614, V1.0, 05/2016 4
1 Task
1 Task
Introduction
The example blocks for SIMATIC STEP 7 (TIA Portal) and SIMATIC WinCC
1
Advanced/Comfort (TIA Portal) enable the user to utilize various automation
functions or use these blocks as templates for the configuration of individual
blocks.
The example configuration shows how the technology blocks are called and
interconnected in STEP 7 and WinCC Advanced.
The advantages of using faceplates in WinCC will be illustrated:
 Making changes from a central location
– When changes are made to one faceplate, all other locations where this
faceplate is used can be updated automatically.
 Re-usability in other projects
– Filing the screen objects for WinCC Advanced in a global library enables
using them further in another project without problems.
 Reducing the configuration effort
– Frequently used automation components can be integrated quickly into a
configuration.
– The screen objects for WinCC Advanced are completely interface-

compatible with the faceplates of WinCC Professional: The connection to
the controller is made via identical control blocks.
– The faceplates are designed in such a way that they can be used as a
basis for creating your own faceplates without much difficulty.
Topics not covered by this application

 For this application, it is assumed that the user has basic knowledge of how to
use the TIA Portal.
 This document is not a user guide for the TIA Portal, but only discusses the
configuration steps necessary for commissioning the faceplates.
1
In the following referred to as “STEP 7” and “WinCC Advanced” for short.

Entry ID: 66839614, V1.0, 05/2016 5
1 Task
Description of the automation task

This application describes the configuration of the “PIDCtrlV2” example technology
block (FB 700) as well as the configuration and operation of the associated
faceplates.
They are used to visualize and control a configurable software-based PID controller
to control technical processes with continuous input and output variables.
The block offers the following functions:

 Local/remote operation
 Real / periphery value
 Setpoint specification
 Manual value specification
 PID algorithm
 Guided controller optimization via technology object
 Reversing the control direction
 Interconnection of external errors
 Interconnection of interlocks
 Message display
 Limit value configuration
The following errors are evaluated, displayed and saved in Alarm Logging:
 Limit violation: Exceeding the upper limit
 Limit violation: Falling below the lower limit
 External error
 Interlock
NOTICE It might be necessary to make some adjustments.

Before using the blocks in your own projects, check their proper functioning and
adjust them to your individual requirements where necessary. The blocks
described in this application are only intended as a template for creating your
own blocks.

Entry ID: 66839614, V1.0, 05/2016 6
2 Solution
2.1 Overview of the overall solution
2 Solution
The application describes the configuration of the example technology block
“PIDCtrlV2” (FB 700) for the controller family S7-1200/S7-1500 and the respective
screen objects for WinCC Advanced.
They are used to visualize and control a configurable software-based PID controller
to control technical processes with continuous input and output variables.
To calculate the controlled variables, the block uses the standard block
“PID_Compact” (version 2.2) from the “PID Control” standard library.
The graphics editor of the respectively used technology object can be used for
configuration and commissioning.
Note  A copy of the technology blocks for the controller is already contained in the
example project and connected to the faceplates. The control blocks of the
example project, however, are not maintained and possibly do not represent
the current state of development.
 The latest version of the technology blocks for the controller is available in
the separate project library
“66839614_STEP7_Example_Blocks_V13_SP1.zip” on the website of this
application.
 For simulating the control characteristic, in the example project, the
technology block “PIDCtrlV2” (FB 700) is interconnected with a PT1 element

"PROC_C" (FB 100). The PT1 element is not part of the library and is
therefore not required in real operation.

Entry ID: 66839614, V1.0, 05/2016 7
2 Solution

Schematic layout
The figures below show the block in the controller, the faceplate icon as well as the
screen window. The blocks are intended for operating and monitoring a PID
controller.
Table 2-1
Block Faceplate icon and screen window
Faceplate icon
Screen window
The screen window consists of a pop-up screen

containing a menu system and several faceplates.

Entry ID: 66839614, V1.0, 05/2016 8
2 Solution
2.2 Hardware and software components
2.2 Hardware and software components

2.2.1 Validity
This application is valid for

 STEP 7 V13 SP1 update 1
 WinCC Advanced V13 SP1 update 1
 S7-1200 and S7-1500
2.2.2 Components used
The application has been created with the following components:
Hardware components
Table 2-2
Component No. Order number Note
S7-1200 CPU 1 6ES721.-1….-0XB0 Alternatively, the controller can
also be simulated with PLCSIM
(as of TIA V13 SP1).
S7-1500 CPU 1 6ES751.-…01-0AB0 Alternatively, the controller can
also be simulated with PLCSIM.
Software components
Table 2-3
Component No. Order number
STEP 7 Professional V13 SP1 update 1 1 6ES7822-1..03-..
WinCC Runtime Advanced V13 SP1 update 1 1 6AV2104-….3-0
WinCC Advanced V13 SP1 update 1 1 6AV210.-….3-0
Example files and projects

The following list includes all files and projects that are used in this example.
Table 2-4
Component Note
66839614_WCA_Faceplates_Demo_V13_SP1.zip The zip file contains the example
project (STEP 7 and WinCC
Advanced) for the application.
66839614_WCA_Documents_V13_SP 1_de.zip The zip file contains the
documentation for all example
blocks of the application.
66839614_WCA_Faceplates_Library_V13_SP1.zip The zip file contains a library with
the WinCC blocks of the application.
66839614_STEP7_Example_Blocks_V13_SP1.zip The zip file contains a library with
the STEP 7 blocks.

Entry ID: 66839614, V1.0, 05/2016 9
3 Basics
3.1 Library objects
3 Basics
Introduction
Understanding this application requires knowledge of the following procedures:
 Managing library objects,
 Using faceplates and screen windows,
 Differences between faceplates and screen windows.
3.1 Library objects

The library provides two options for filing and using library objects. Depending on
this, they are managed in two different folders within the library and show a
different functionality:
 Types
When using the library objects of the “Types” folder in your project, you create
instances of these types. The instances, that is, the usage locations in the
project, are bound to their respective type.
If the type in the library changes, all instances within the project also change.
 Master copies
For creating independent copies of a library object, you use the master copies.
The copies of these master copies in the project have no correlation with each
other after copying.
If a master copy is processed in the library, these changes do not affect the
copies. The individual copies and their changes in the project are independent
of each other.
Note  “Project library” as well as “Global library” both contain the two folders
“Master copies” and “Types”.
 For changing the library types, the TIA Portal offers a sophisticated
management for managing several versions of a type and a specific release
of this version regarding the instances.
 The usage of types is restricted to the following objects:
– Faceplates
– Screens
– Scripts
– UDTs
– Style sheets
 Using master copies is principally possible for all objects with the exception
of faceplates.
 You can copy the library objects between a global library and a project
library. The following applies here:
– You only copy the master copies to the “Master copies” folder or any
subfolder of “Master copies”.
– You can only insert types in the “Types” folder or any subfolder of “Types”.
– As soon as you add a library object from a global library into a screen, this
object will also be stored in the project library.

Entry ID: 66839614, V1.0, 05/2016 10
3 Basics
3.2 Faceplates
3.2 Faceplates
Faceplates consist of a configured group of display and control objects which you
can manage and modify centrally in a library.
Usage
 Faceplates are used to create individually configured display and control
objects.
 A faceplate is used several times in the project or in several projects, as
required.
 The faceplates are stored in the library as types.
 A faceplate type can be edited in the “Faceplates” editor.
 All instances of a faceplate in the project are changed centrally. This reduces
the configuration effort.
 A faceplate supports faceplate-internal VB scripts.
 A faceplate is provided with a defined interface for the integration into a project
(e. g. tag connection).
Types and instances

To support central changeability, faceplates are based on a type-instance model.
 The faceplate type is stored in the project library. When using the faceplate
type in a screen, you create an instance of the faceplate type.
 In the faceplate type you specify the properties that can be changed at the
faceplate. When changing a property of a faceplate type, the property is stored
centrally and changed in all other instances as well.
 The instances represent local locations where the types are used and are
bound to the respective faceplate type.
 When configuring the properties at the faceplate instance, you overwrite the
properties of the faceplate type:
– For example, you assign the tag of your project to the faceplate.
– The changes at the faceplate are stored in the location of usage and have
no effects on the faceplate type.
Note  Please note that a faceplate is always configured for a certain class of
operator panels. You cannot, for example, use a faceplate type configured
for “RT Advanced” in a screen of the “RT Professional” operator panel.
 The number of instances of faceplates in a screen is not limited. Please note
that the performance when opening or updating a screen is affected by the
number of faceplate instances or the usage of scripts in the faceplate
instances.

Entry ID: 66839614, V1.0, 05/2016 11
4 Mode of Operation
4.1 Faceplate icon
4 Mode of Operation
Introduction
Here you will learn how faceplate and screen window interact, which functions they
have and how their connection with the controller is established.
Note The following chapter gives you a detailed insight into the blocks of this
application.
If you are only interested in operating the application example, you can directly
jump to the chapter “Operating the Application”.
4.1 Faceplate icon

Figure 4-1
Note The screen shows the faceplate in the configuration environment. The display
during runtime (RT) is described in the chapter “Operating the Application”.
Features
The faceplate icon has the following properties:
 Simplified status display
 Opens the respective screen window via mouse-click
 Has a defined interface
Parameters
Table 4-1
No. Path Usage
1. Properties > Miscellaneous > Name PID_001_Icon
2. Interface > Property > Unit PID_Unit
3. Interface > Process > Value PID_001_UDT

Entry ID: 66839614, V1.0, 05/2016 12
4 Mode of Operation
4.1 Faceplate icon
Explanation
Table 4-2
No. Explanation
1. The name “PID_001_Icon” has been selected randomly.
However, it is important that it is only assigned once in a screen.
2. As shown in the screen, the interface of the faceplate has the properties “Unit”
and “Value” for displaying the controller values and all other objects.
 The “DID_001_UDT” UDT tag of the controller is connected at the “Value”

property of the faceplate instance. It is required for displaying the status
signals and values.
 The “PID_Unit” tag of the controller is connected at the “Unit” property of the
faceplate instance and is used for displaying the unit of the values.

Entry ID: 66839614, V1.0, 05/2016 13
4 Mode of Operation
4.1 Faceplate icon
No. Explanation
3.
4. The tags connected at the properties in “Animations > Tag connections” are
references to the respective properties of the interface.
The tags can be connected and modified in either location; the entries mutually
affect each other.

Entry ID: 66839614, V1.0, 05/2016 14
4 Mode of Operation
4.1 Faceplate icon
No. Explanation
5. In order to make the screen window visible by clicking on the faceplate icon, for
the “PID_001_Button” button, the “ShowPopupScreen” event must be configured
in “Events > Release” for the “PID_001_Pop-up” pop-up screen.
Set the “Visibility” tag to “1” to display the “PID_1_Overview” faceplate after
opening the screen window as start screen.

Entry ID: 66839614, V1.0, 05/2016 15
4 Mode of Operation
4.2 Interfaces of the faceplate icon
4.2 Interfaces of the faceplate icon

In the interface of the faceplate icon, the dynamic properties are accessed.
A dynamic property is connected to a tag via the interface. In Runtime, the tag
supplies the dynamic property with values.
Figure 4-2
Process
The tags of this group have a process connection and constitute the basic interface
between controller and operating panel.
PID_001_UDT
The “PID_001_UDT” property is used to display the different states and values in
the WinCC Advanced process display.
Table 4-3
Tag used
Symbolic name PID_001_UDT
Data type PIDCTRLV2_UDT
Access type %DB700.DBX0.0
Length 642 bytes
Acquisition cycle 100 ms
Acquisition mode Cyclic in operation
Unit
The “Unit” property is used to display the unit of the analog value. The tag can be
provided with a process connection. In the example project, it is connected to an
internal HMI tag.
Table 4-4
Tag used
Name PID_Unit
Data type String
Access type Internal tag

Entry ID: 66839614, V1.0, 05/2016 16
4 Mode of Operation
4.3 Screen window
Tag used
Length 10
4.3 Screen window

The screen window consists of a pop-up screen containing a menu system and
several faceplates.
Note  For better understanding, the screen window is initially described in the
configuration environment.
 The following screens for describing the components then refer to the display
during runtime (RT), unless stated otherwise.
 The individual screens successively build on one another and therefore only
show parts of the screen window instead of the usual display during runtime
(RT).
Figure 4-3
Features
The screen window has the following properties:
 Comprehensive status display
 Parameterization is possible for service technician
 Contains language-dependent objects: German (Germany), English (USA)
 Permanent tag prefix for addressing a tag structure (UDT)
 Screen window cannot be moved
Events
The screen window is equipped with the following events called up while the
screen builds up:
Table 4-5
No. Function, tag Usage
1. SetTag X1Pos Position of the toolbar at the tab

Entry ID: 66839614, V1.0, 05/2016 17
4 Mode of Operation
4.3 Screen window
No. Function, tag Usage

2. SetTag Visibility Indicator for selecting a tab
Explanation
Table 4-6
No. Explanation
1. The INT tag “X1Pos” refers to the X position of the selection bar above the
currently called tab:
X1Pos = { 3, 104, 205, 306, 407, 508, 609, 710 }
2. The identifier of the currently activated tab is stored in the INT tag “Visibility”:
Visibility = {1, 2, 3, 4, 5, 6, 7, 8 }
3. Click on the “X” to close the screen window. The screen shows the system
function stored.

Entry ID: 66839614, V1.0, 05/2016 18
4 Mode of Operation
4.4 Components of the screen window

The screen window has several components which are graphically displayed here
during runtime (RT).
“Close” button
The button for closing the screen window is positioned in the top right corner
of the screen window.
Menu system
The menu system consists of several tabs which can be called via the different
faceplates.
Figure 4-4
The following options are available:

Table 4-7
No. Tab Faceplate Function
1. Overview PID_1_Overview Overview of the current values for actual value
and setpoint, status and error displays
2. Messages PID_2_Messages Display of messages (warnings and errors)
3. Graphs PID _3_Graphs Graph display for graphic visualization of actual
value and setpoint
4. Parameters PID_4_Parameters Settings of the values for proportional, integral
and differential fractions
5. Actual PID_5_ActualValue Warning messages upper and lower limit for
value process output
6. Setpoint PID_6_Setpoint Upper and lower limit of the process output
values
7. Limits PID_7_Limits Scaling the process input
8. Service PID_8_Service Settings for valve direction, process input and
local/remote operation
The “Visibility” property is used for influencing the display properties of the screen
window during runtime.
It influences the selection of the individual tabs. The value of the “Visibility” tag
corresponds to the number of the faceplate.
The process connection is optional.
Note The “Visibility” tag is pre-assigned with the value “1” when clicking on the hidden
button “PID_001_Button” with the mouse. This results in the respective screen
window being displayed with tab 1.

Entry ID: 66839614, V1.0, 05/2016 19
4 Mode of Operation
Table 4-8
Tag used
Name Visibility
Data type Integer
Address Internal tag
Note The tag can also be defined as PLC tag with controller connection.
If the tag has a controller connection, read and write access is possible from the
controller. Thus, besides the known screen selection, the respective faceplate in
the screen window can also be opened from the controller and a specific tab can
be selected.
4.4.1 Faceplate “PID_1_Overview”
The “PID_1_Overview” faceplate is used for displaying current process values as

well as possibly pending error messages.
Figure 4-5

Entry ID: 66839614, V1.0, 05/2016 20
4 Mode of Operation
4.4.2 Faceplate “PID_2_Messages”
The “PID_2_Messages” faceplate is used for the displaying messages.

It is intended to display warnings and errors with the filter prefix “PIDCtrlV2_” in the
message text. Alternatively, instance-related filtering of the messages is possible.
Figure 4-6
The message view is divided into six columns:

 Alarm class and message number (configured in “HMI alarms”)
 Time
 Date
 Status of the message
 Message text
 Alarm group (for acknowledgement)

Entry ID: 66839614, V1.0, 05/2016 21
4 Mode of Operation
4.4.3 Faceplate “PID_3_Graphs”
The “PID_3_Graphs” faceplate is used for displaying graphs.

It contains a graph view for graphic visualization of the tags.
 ActualValue = actual value (controlled variable)
 OutputValue = manually specified setpoint in local operating mode (manual
value)
 Setpoint = setpoint in remote operating mode (reference variable)
Figure 4-7
4.4.4 Faceplate “PID_4_Parameters”
The “PID_4_Parameters” faceplate is used for setting the values for proportional,
integral and differential fractions and for reversing the control direction.
Figure 4-8

Entry ID: 66839614, V1.0, 05/2016 22
4 Mode of Operation
4.4.5 Faceplate “PID_5_ActualValue”
The “PID_5_ActualValue” is used for setting the warning limits for monitoring the
actual value.
Figure 4-9
4.4.6 Faceplate “PID_6_Setpoint”
Figure 4-10

Entry ID: 66839614, V1.0, 05/2016 23
4 Mode of Operation
4.4.7 Faceplate “PID_7_Limits”
Figure 4-11
4.4.8 Faceplate “PID_8_Service”
The “PID_8_Service” faceplate is used to set the process input, the operating
mode and the type of signal processing. Moreover, the name of the corresponding
instance is displayed.
Figure 4-12

Entry ID: 66839614, V1.0, 05/2016 24
4 Mode of Operation
4.5 Interfaces of the screen window
4.5 Interfaces of the screen window

The tags used in this application are almost exclusively elements of so-called user-
defined PLC data types (UDT).
For the “PID_001_UDT” screen objects, the defined data structure
“PIDCTRLV2_UDT” (2) has already been stored in the library as a type. As already
described in the chapter “Library objects”, you only create instances of this
structure for UDT-type tags.
In the example project of this application, an instance has already been created for
each block as, for example, for the controller block: “PID_001_UDT” (1):
Figure 4-13
1 2

Entry ID: 66839614, V1.0, 05/2016 25
4 Mode of Operation
4.6 Tags of the UDT
When creating a new tag, e. g. “PID_001_UDT_002” of the “PIDCtrl_UDT” data

type, the following structure elements will be defined automatically for each
structure tag:
 Name
 PLC data type
 Address
 Start value
 Comment
Note The name of the instance automatically defines the tag prefix of the individual
structure elements (e. g. “PID_001_UDT”).
 In the project, the tag prefix must precede each location of usage of the
structure elements, e. g. “PID_001_UDT.QdwState”.
 An exception is only the higher-level screen window to which the tag prefix is
permanently assigned. Elements (also further screen windows) within this
screen window therefore only use the respective structure name with
preceding dot and without preceding tag prefix, for example “QdwState”.
Subdivision
The individual structure tags can principally be divided into three categories:
 Tags with function tasks
 General tags for signal values, controller parameters and limit values
 Tags with function tasks without controller connection
4.6 Tags of the UDT

4.6.1 Tags with function tasks
The tags of this group have a process connection and constitute the basic interface
between controller and operating panel.
QdwState
The “QdwState” HMI tag is used to display the different states in the process
display.
Table 4-9
Tag used
Name PID_001_UDT.QdwState
Data type DWord
Address %DB700.DBD398
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 26
4 Mode of Operation
4.6 Tags of the UDT
The following table shows the setup of the “QdwState” tag.
Table 4-10 Setup of the “QdwState” tag

Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
INVERT_CONTROL
WARNING_HIGH
PERIPHERY_ON
WARNING_LOW
ALARM_HIGH
ALARM_LOW
D_PART_ON
P_PART_ON
I_PART_ON
QMAN_AUT
QERR_EXT
QREMOTE
QLOCK
Signal
QERR
LOCK
QwAlarm
This application uses the bit message procedure to display messages in the
process display. The messages must be configured as bit messages in the
message editor of WinCC Professional.
In the example configuration, all bit messages have already been created for the
used faceplate instances, as well as their “QwAlarm” trigger tags.
Table 4-11
Tag used
Name PID_001_UDT.QwAlarm
Data type DWord
Address %DB640.DBW404
Length 4 bytes
The following table shows the setup of the tags. For the first instance of the PID
faceplate window, the filter attribute “PID_001” has been assigned to the message
texts as a selection criterion.
Table 4-12
Bit Signal Message text
0 SetpointLimit_L PID_001:Alarm lower limit undercut
1 SetpointLimit_H PID_001:Alarm upper limit exceeded
2
3
4 QLOCK PID_001:Interlock, value locked
5
6 QERR_EXT PID_001:External error
7 QERR PID_001:Group error
8 InputWarning_L PID_001:Warning lower limit undercut

Entry ID: 66839614, V1.0, 05/2016 27
4 Mode of Operation
4.6 Tags of the UDT
Bit Signal Message text

9 InputWarning_H PID_001:Warning upper limit exceeded
10 NOT QPERIPH PID_001:Actual value from external (Real)
11 QPERIPH PID_001:Actual value from I/O (Int)
12 NOT QREMOTE PID_001:Controller => LOCAL
13 QREMOTE PID_001:Controller => REMOTE
14 NOT QMAN_AUT PID_001:Manual value active
15 QMAN_AUT PID_001:Process value active
OPdwCmd
The “OPdwCmd” HMI tag is used to transmit commands from WinCC Professional
to the controller. The block in the controller analyzes the control command,
executes the desired action and then initiates a reset of the pending control
command. For this purpose, the value of the control tag is set to “0”.
Table 4-13
Tag used
Name PID_001_UDT.OPdwCmd
Data type DWord

Length 4 bytes
The following table shows the setup of the tags.
Table 4-14 Setup of the “OPdwCmd” tag

Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
PERIPHERY
EXTERNAL
PROCESS
REMOTE
MANUAL
INVERT
RESET
LOCAL
Signal

Entry ID: 66839614, V1.0, 05/2016 28
4 Mode of Operation
4.6 Tags of the UDT
4.6.2 General tags – Signal values
The HMI tags in this group have a process connection and influence the controller
signal.
ScaledInput
The “ScaledInput” tag displays the scaled actual value and can be read via WinCC.
Table 4-15
ScaledInput
Name PID_001_UDT.ScaledInput
Data type Real
Length 4 bytes
Output
The “Output” tag displays the output value in REAL format and can be read via
WinCC.
Table 4-16
Output
Name PID_001_UDT.Output
Data type Real
Length 4 bytes
QSetpoint
The “QSetpoint” tag displays the setpoint value of the PID controller in remote
operating mode and can be read via WinCC.
Table 4-17
QSetpoint
Name PID_001_UDT.QSetpoint
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 29
4 Mode of Operation
4.6 Tags of the UDT
OP_Setpoint
The “OP_Setpoint” tag specifies the setpoint value of the PID controller in remote
operating mode and can be read and written via WinCC.
Table 4-18
OP_Setpoint
Name PID_001_UDT.OP_Setpoint
Data type Real
Length 4 bytes
OP_ManualValue
The “OP_ManualValue” tag specifies the value in local operating mode and can be
read and written via WinCC.
Table 4-19
OP_ManualValue
Name PID_001_UDT.OP_ManualValue
Data type Real
Length 4 bytes
4.6.3 General tags – Controller parameters
The HMI tags in this group have a process connection and influence the behavior
of the controller signal in case of a control deviation.
OP_Cycle
The “OP_Cycle” tag specifies the value of the sampling time for the PID algorithm
and can be read and written via WinCC.
Table 4-20
OP_Cycle
Name PID_001_UDT.OP_Cycle
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 30
4 Mode of Operation
4.6 Tags of the UDT
OP_Gain
The “OP_Gain” tag specifies the value of the proportional gain and can be read
and written via WinCC.
Table 4-21
OP_Gain
Name PID_001_UDT.OP_Gain
Data type Real
Length 4 bytes
OP_Ti
The “OP_Ti” tag specifies the value of the integration time and can be read and
written via WinCC.
Table 4-22
OP_Ti
Name PID_001_UDT.OP_Ti
Data type Real
Length 4 bytes
OP_Td
The “OP_Td” tag specifies the value of the derivative time and can be read and
written via WinCC.
Table 4-23
OP_Td
Name PID_001_UDT.OP_Td
Data type Real
Length 4 bytes
OP_TdFiltRatio
The “OP_TdFiltRatio” tag specifies the value of the derivative time lag coefficient
and can be read and written via WinCC.

Entry ID: 66839614, V1.0, 05/2016 31
4 Mode of Operation
4.6 Tags of the UDT
Table 4-24
OP_TdFiltRatio
Name PID_001_UDT.OP_TdFiltRatio
Data type Real
Length 4 bytes
OP_PWeighting
The “OP_PWeighting” tag specifies the weighting of the P component and can be
Table 4-25
OP_PWeighting
Name PID_001_UDT.OP_PWeighting
Data type Real
Length 4 bytes

OP_DWeighting
The “OP_DWeighting” tag specifies the weighting of the D component and can be
Table 4-26
OP_DWeighting
Name PID_001_UDT.OP_DWeighting
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 32
4 Mode of Operation
4.6 Tags of the UDT
4.6.4 General tags – Limit values
The HMI tags in this group have a process connection and influence the limit
values of the controller signal.
OP_LMNUpperLimit
The “OP_LMNUpperLimit” tag specifies the upper limit of the output value and can
be read and written via WinCC.
Table 4-27
OP_LMNUpperLimit
Name PID_001_UDT.OP_LMNUpperLimit
Data type Real
Length 4 bytes
OP_LMNLowerLimit
The “OP_LMNLowerLimit” tag specifies the lower limit of the output value and can
Table 4-28
OP_LMNLowerLimit
Name PID_001_UDT.OP_LMNLowerLimit
Data type Real
Length 4 bytes
OP_MinimumOnTime
The “OP_MinimumOnTime” tag specifies the minimum switch-on time of the PWM
output value and can be read and written via WinCC.
Table 4-29
OP_MinimumOnTime
Name PID_001_UDT.OP_MinimumOnTime
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 33
4 Mode of Operation
4.6 Tags of the UDT
OP_MinimumOffTime
The “OP_MinimumOffTime” tag specifies the minimum switch-off time of the PWM
output value and can be read and written via WinCC.
Table 4-30
OP_MinimumOffTime
Name PID_001_UDT.OP_MinimumOffTime
Data type Real
Length 4 bytes
OP_SPUpperLimit
The “OP_SPUpperLimit” tag specifies the upper limit of the setpoint value and can
Table 4-31
OP_SPUpperLimit
Name PID_001_UDT.OP_SPUpperLimit
Data type Real
Length 4 bytes
OP_SPLowerLimit
The “OP_SPLowerLimit” tag specifies the lower limit of the setpoint value and can
Table 4-32
OP_SPLowerLimit
Name PID_001_UDT.OP_SPLowerLimit
Data type Real
Length 4 bytes
OP_PVUpperLimit
The “OP_PVUpperLimit” tag specifies the upper limit of the actual value and can be

Entry ID: 66839614, V1.0, 05/2016 34
4 Mode of Operation
4.6 Tags of the UDT
Table 4-33
OP_PVUpperLimit
Name PID_001_UDT.OP_PVUpperLimit
Data type Real
Length 4 bytes
OP_PVLowerLimit
The “OP_PVLowerLimit” tag specifies the lower limit of the actual value and can be
Table 4-34
OP_PVLowerLimit
Name PID_001_UDT.OP_PVLowerLimit
Data type Real
Length 4 bytes

OP_LowerPointIn
The “OP_LowerPointIn” tag specifies the lower limit of the I/O input and can be
Table 4-35
OP_LowerPointIn
Name PID_001_UDT.OP_LowerPointIn
Data type Real
Length 4 bytes
OP_UpperPointIn
The “OP_UpperPointIn” tag specifies the upper limit of the I/O input and can be
Table 4-36
OP_UpperPointIn
Name PID_001_UDT.OP_UpperPointIn
Data type Real

Entry ID: 66839614, V1.0, 05/2016 35
4 Mode of Operation
4.6 Tags of the UDT
OP_UpperPointIn
Length 4 bytes
OP_LowerPointOut
The “OP_LowerPointOut” tag specifies the lower limit of the scaled I/O input and
can be read and written via WinCC.
Table 4-37
OP_LowerPointOut
Name PID_001_UDT.OP_LowerPointOut
Data type Real
Length 4 bytes
OP_UpperPointOut
The “OP_UpperPointOut” tag specifies the upper limit of the scaled I/O input and
can be read and written via WinCC.
Table 4-38
OP_UpperPointOut
Name PID_001_UDT.OP_UpperPointOut
Data type Real
Length 4 bytes
OP_PVUpperWarning
The “OP_PVUpperWarning” tag specifies the upper limit for the warning when
exceeding the actual value and can be read and written via WinCC.
Table 4-39
OP_PVUpperWarning
Name PID_001_UDT.OP_PVUpperWarning
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 36
4 Mode of Operation
4.6 Tags of the UDT
OP_PVLowerWarning
The “OP_PVLowerWarning” tag specifies the lower limit for the warning when
falling short of the actual value and can be read and written via WinCC.
Table 4-40
OP_PVLowerWarning
Name PID_001_UDT.OP_PVLowerWarning
Data type Real
Length 4 bytes
4.6.5 Tags with function tasks without controller connection
The use of these HMI tags has already been explained in the chapter “Screen
window”. For completeness, they are shown once again in this table:
Table 4-41
Name Data type Start value

Unit String %
Visibility Int 1

Entry ID: 66839614, V1.0, 05/2016 37
4 Mode of Operation
4.7 Control and status signals

4.7.1 Processing of switching commands in the controller
The “OPdwCmd” control tag of a block is used to transmit commands from WinCC
to the controller.
The block in the controller analyzes the control command, executes the desired
action and then initiates a reset of the pending control command. For this purpose,
the value of the control tag is set to “0”.
Figure 4-14
“PIDCtrlV2” (FB 700)
EN QSetpoint
InvertControl ScaledInput
InputPerOn Output
InputUpperLimit Output_PER
InputLowerLimit Output_PWM
UpperPointOut SetpointLimit_H
LowerPointOut SetpointLimit_L
UpperPointIn InputWarning_H
LowerPointIn InputWarning_L
InputUpperWarning State
InputLowerWarning Error
MinimumOnTime ErrorBits
MinimumOffTime QGain
OutputUpperLimit QTi
OutputLowerLimit QTd
SetpointUpperLimit QdwState
SetpointLowerLimit QPERIPH
PIDManualEnable QMAN_AUT
Gain QREMOTE
Ti QLOCK
Td QERR
TdFiltRatio QERR_EXT
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 38
4 Mode of Operation
The following table shows the setup of the “OPdwCmd” tag.
Table 4-42 Setup of the “OPdwCmd” tag

Bit
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
PERIPHERY
EXTERNAL
PROCESS
REMOTE
MANUAL
INVERT
RESET
LOCAL
Signal

Entry ID: 66839614, V1.0, 05/2016 39
4 Mode of Operation
4.7.2 Evaluating process states and displaying them in WinCC
The technology block of this application uses the output “QdwState” to show the
different states in the WinCC process display.
Figure 4-15
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 40
Signal Bit
31
30
29
28
LOCK 27
4 Mode of Operation
QLOCK 26
QERR_EXT 25
QERR 24
23
Entry ID: 66839614, V1.0, 05/2016

22
Table 4-43 Setup of the “QdwState” tag
21
20
19
18

QREMOTE 17
QMAN_AUT 16
ALARM_HIGH 15
WARNING_HIGH 14
WARNING_LOW 13
ALARM_LOW 12
11
10
The following table shows the setup of the “QdwState” tag.
9
8
7
PERIPHERY_ON 6
INVERT_CONTROL 5
4
3
D_PART_ON 2
I_PART_ON 1
41
P_PART_ON 0
4 Mode of Operation
4.7.3 Actual value Real value / S7 periphery
The actual value can be interconnected in an I/O format (WORD) or as an external

value in floating point format (REAL).
Figure 4-16
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 42
4 Mode of Operation
 “Input_PER_ON”
The “InputPerOn” input is only effective, if the input “LIOP_SEL” has been set.
If the “Input_PER_ON” input is active, the interconnection in the I/O format at
“Input_PER” applies. Otherwise, the external value at “Input” applies.
“LIOP_SEL” = 1 AND “InputPerOn” = 0  „QPERIPH“ = 0
“LIOP_SEL” = 1 AND “InputPerOn” = 1  „QPERIPH“ = 1
 “OPdwCmd”
The operator commands of the control word “OPdwCmd” will be effective only,
if the “LIOP_SEL” input is not set.
2
“LIOP_SEL” = 0 AND “OPdwCmd [bit 7]” = 1  “QPERIPH” = 0
3
“LIOP_SEL” = 0 AND “OPdwCmd [bit 6]” = 1  “QPERIPH” = 1
 “QPERIPH”
The operating mode is displayed at the “QPERIPH” output:
“QPERIPH” = 0  “Input” is active
“QPERIPH” = 1  “Input_PER” is active
2
Bit 7 = “EXTERNAL”
3
Bit 6 = “PERIPHERY”

Entry ID: 66839614, V1.0, 05/2016 43
4 Mode of Operation
4.7.4 Calculating the manipulated variable
The manipulated variable can be specified via a setpoint or a manual value.

If the setpoint specification (QMAN_AUT = 1) has been configured, the
manipulated variable is calculated by means of the “Setpoint” value.
If the manual value specification (QMAN_AUT = 0) is configured, the value
“ManualValue” is written to output “Output_PER” as manipulated variable.
Figure 4-17
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 44
4 Mode of Operation
 “LIOP_SEL”
If the “LIOP_SEL” input is set, the operating mode will be determined via the
control input “L_AUT”.
If the “LIOP_SEL” input is not set, the operating mode is defined by the
operator (“OPdwCmd [bits 16 and 17]”).
 “L_AUT”
The “L_AUT” input will be effective only, if the “LIOP_SEL” input is set.
“LIOP_SEL” = 1 AND “L_ AUT” = 0  manual value active
“LIOP_SEL” = 1 AND “L_ AUT” = 1  process value active
 “OPdwCmd”
The operator commands of the control word “OPdwCmd” will be effective only,
if the “LIOP_SEL” input is not set.
4
“LIOP_SEL” = 0 AND “OPdwCmd [bit 16]” = 1  manual value active
5
“LIOP_SEL” = 0 AND “OPdwCmd [bit 17]” = 1  process value active
 “QMAN_AUT”
The operating mode is indicated at the “QMAN_AUT” block output.
“QMAN_AUT” = 0  manual value active
“QMAN_AUT” = 1  process value active
 “QdwState”
The current operating mode is transferred to WinCC in bit 16 of the “QdwState”

status word.
6
“QdwState [bit 16]” = 0  manual value active
5
“QdwState [bit 16]” = 1  process value active
4
Bit 16 = “MANUAL”
5
Bit 17 = “PROCESS”
6
Bit 16 = “QMAN_AUT”

Entry ID: 66839614, V1.0, 05/2016 45
4 Mode of Operation
4.7.5 Toggling between local and remote operating mode
In the “Local” operating mode, the control commands by the operator become
effective directly at the device.
In the “Remote” operating mode, the control signals of an automatic function (e. g.
control, step chain etc.) or the control signals of the operation are effective in
WinCC.
Figure 4-18
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 46
4 Mode of Operation
 “LIOP_SEL”
If the “LIOP_SEL” input is set, the operating mode is determined by the control
input “L_REMOTE”.
If the “LIOP_SEL” input is not set, the operating mode is defined by the
operator (“OPdwCmd [bits 18 and 19]”).
 “L_REMOTE”
The “L_REMOTE” input is only effective, if the “LIOP_SEL” input is set.
“LIOP_SEL” = 1 AND “L_REMOTE” = 0  local
“LIOP_SEL” = 1 AND “L_REMOTE” = 1  remote
 “OPdwCmd”
The operator commands of the control word “OPdwCmd” are only effective, if
the “LIOP_SEL” input is not set.
7
“LIOP_SEL” = 0 AND “OPdwCmd [bit 18]” = 1  local
8
“LIOP_SEL” = 0 AND “OPdwCmd [bit 19]” = 1  remote
 “QREMOTE”
The operating mode is indicated at the “QREMOTE” block output.
“QREMOTE” = 0  local
“QREMOTE” = 1  remote
7
Bit 18 = “LOCAL”
8
Bit 19 = “REMOTE”

Entry ID: 66839614, V1.0, 05/2016 47
4 Mode of Operation
4.7.6 Determining controller values
The source of the proportional, integral and differential fractions used for controlling
can be switched over.
Either the PID parameters of the technology object (e. g. for optimization) or the
PID parameters at the block input are effective.
The respectively active parameters are transferred to WinCC and there, they can
be manipulated in the “Remote” operating mode.
Figure 4-19
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 48
4 Mode of Operation
CAUTION If the controller values are changed during runtime, the danger of
destroying the actuators (e. g. motor, mechanism) in the controlled system
arises.
A manipulation of the control parameters during runtime should only be permitted
for expert staff familiar with optimization of controlled systems and setting up the
plant.
Note If the controller values are determined automatically via the technology object,
the PID parameters must not be overwritten during the optimization phase.
 Set the “PIDManualEnable” block input to “0” (false).
 Set the operating mode to “Local”, or avoid changing the controller values manually
via WinCC during the optimization phase.
If the PID parameters at the block input or the operating mode “Remote” is
activated, the values of the technology object are overwritten.
 “PIDManualEnable”
– The “PIDManualEnable” input is only effective, if the “LIOP_SEL” input is
set.
– If the input “PIDManualEnable” is active, the values of the block inputs

“Gain”, “Ti”, “Td”, “TdFiltRatio”, “PWeighting”, “DWeighting” and “Cycle” are
used as control parameters, and the existing control parameters in the
technology object of the controller are overwritten.
– If the input “PIDManualEnable” is not active, the control parameters
contained in the technology object of the controller are used.
“LIOP_SEL” = 1 AND “PIDManualEnable” = 0  technology object parameter
“LIOP_SEL” = 1 AND “PIDManualEnable” = 1  block input parameter
 “GAIN”
The “GAIN” input (proportional coefficient) indicates the controller gain.
 “TI”
The “TI” input (integration time) specifies the time behavior of the integrator.
 “TD”
The “TD” input (derivative action time) specifies the time behavior of the
derivative action element.
 “TdFiltRatio”
The “TdFiltRatio” input (derivative time lag coefficient) determines the
deceleration of the effect of the D component.
 “PWeighting”
The “PWeighting” input determines the weighting of the P component.
 “DWeighting”
The “DWeighting” input determines the weighting of the D component.
 “Cycle”
The “Cycle” input determines the sampling time for the PID algorithm and is a
multiple of the cycle time of the calling OB.

Entry ID: 66839614, V1.0, 05/2016 49
4 Mode of Operation
4.7.7 Manipulated variable limit
The following inputs are available for limiting the manipulated variable:
Figure 4-20
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 50
4 Mode of Operation
 “InputUpperLimit”
– With the “InputUpperLimit” input, the upper limit of the actual value is
determined.
– The upper limit of the actual value must be higher than the lower limit of
the actual value.
 “InputLowerLimit”
– The “InputLowerLimit” input specifies the lower limit of the actual value.
– The lower limit of the actual value must be lower than the upper limit of the
actual value.
 “UpperPointOut”
– The upper scaled limit value is specified via the “UpperPointOut” input.
– The two value pairs “UpperPointOut” and “UpperPointIn” as well as
“LowerPointOut” and “LowerPointIn” are used for converting the value
at “Input_PER” into a percentage.
– The upper scaled limit value must be higher than the lower scaled limit
value.
– Scaling is only active, if the “InputPerOn” input has been activated.
 “LowerPointOut”
– The lower scaled limit value is specified via the “LowerPointOut” input.

– The lower scaled limit value must be lower than the upper scaled limit
value.
 “UpperPointIn”
– The upper limit value of the analog signal at “Input_PER” is specified via
the “UpperPointIn” input.
– The upper limit value must be higher than the lower limit value of the
analog signal.
 “LowerPointIn”
– The lower limit value of the analog signal at “Input_PER” is specified via
the “LowerPointIn” input.
– The lower limit value must be lower than the lower limit value of the analog
signal.

Entry ID: 66839614, V1.0, 05/2016 51
4 Mode of Operation
 “InputUpperWarning”
– The upper warning threshold for the actual value is specified via the
“InputUpperWarning” input.
– If the actual value exceeds the entered value, the output parameter
“InputWarning_H” is set.
– If you enter a value higher than the upper actual value limit, the upper
actual value limit is used as the upper warning limit for the actual value.
 “InputLowerWarning”
– The lower warning threshold for the actual value is specified via the
“InputLowerWarning” input.
– If the actual value falls short of the entered value, the output parameter
“InputWarning_L” is set.
– If you enter a value lower than the lower actual value limit, the lower actual
value limit is used as the lower warning limit for the actual value.
 “MinimumOnTime”
– The minimal switch-on time of the pulse width modulation for the
manipulated variable “Output_PWM” is set via the input
“MinimumOnTime” (switch-on time pulse width modulation).
– If you have selected “Output” or “Output_PER” as the output value
instead of “Output_PWM”, specify 0.0 as value for “MinimumOnTime”.
 “MinimumOffTime”
– The minimal switch-off time of the pulse width modulation for the
manipulated variable “Output_PWM” is set via the input
“MinimumOffTime” (switch-off time pulse width modulation).
– If you have selected “Output” or “Output_PER” as the output value
instead of “Output_PWM”, specify 0.0 as value for “MinimumOffTime”.
 “OutputUpperLimit”
– The “OutputUpperLimit” input limits the upper limit of the output.
– The output value does not exceed this limit in any operating mode.
– The upper output value limit as a percentage value applies for the outputs
“Output”, “Output_PER” and “Output_PWM”.
 “OutputLowerLimit”
– The “OutputLowerLimit” input limits the lower limit of the output.
– The output value does not fall short of this limit in any operating mode.
– The lower output value limit as a percentage value applies for the outputs
“Output”, “Output_PER” and “Output_PWM”.
 “SetpointUpperLimit”
The “SetpointUpperLimit” input limits the upper limit of the setpoint value.
 “SetpointLowerLimit”
The “SetpointLowerLimit” input limits the lower limit of the setpoint value.

Entry ID: 66839614, V1.0, 05/2016 52
4 Mode of Operation
4.7.8 External error / block locked
The following inputs are available for blocking and error handling:
Figure 4-21
EN QSetpoint
InputPerOn Output
Gain QREMOTE
Ti QLOCK
Td QERR
PWeighting QwAlarm
DWeighting ENO
Cycle
Setpoint
Input
Input_PER
ManualValue
LOCK
ERR_EXTERN
LIOP_SEL
L_AUT
L_REMOTE
L_RESET
INSTANCE
RESTART
VISIBILITY
OPdwCmd

Entry ID: 66839614, V1.0, 05/2016 53
4 Mode of Operation
If a signal is pending at the “LOCK” input and the controller is in an active state,
an error message is generated and the controller switches to the
inactive state.
The state is displayed at the output “QLOCK” and “QERR”.
After the “LOCK” signal has disappeared again, the block continues to be in a
faulty state until it is reset with “L_RESET” or via HMI operation.
However, if the controller is in an inactive state and a signal is pending at the

“LOCK” input, only the state at output “QLOCK” is displayed.
As soon as the signal at “LOCK” disappears, the controller is released again.
Active controller:
“LOCK” = 1  “QLOCK” = 1  “QERR” = 1
Inactive controller:
“LOCK” = 1  “QLOCK” = 1
Operating the block is not possible, if a signal is pending at the “ERR_EXTERN”

input. The controller is switched inactive, if it was active before.
When the “ERR_EXTERN” signal disappears again afterwards, the block continues
to be in an incorrect state until it is reset with “L_RESET” or the HMI operation.
The state is displayed at output “QLOCK” and “QERR”.
“ERR_EXTERN” = 1  “QERR_EXT” = 1  “QERR” = 1
 “L_RESET”
When setting the “LIOP_SEL” input parameter and a positive edge at the
“L_RESET” input, the “QERR” output is reset. This only occurs, if no error is
pending anymore.
“LIOP_SEL” = 1 AND “L_RESET” = 1  “QERR” = 0
 “OPdwCmd”
By pressing the “Reset” button in the faceplate window, bit 24 is set in the
control word “OPdwCmd”. The controller evaluates this bit and resets the
“QERR” output. This only occurs, if no error is pending anymore and the input
parameter “LIOP_SEL” has not been set.
9
“LIOP_SEL” = 0 AND “OPdwCmd [bit 24]” = 1  “QERR” = 0
9
Bit 24 = “RESET”

Entry ID: 66839614, V1.0, 05/2016 54
5 Commissioning the Application

Introduction
Here you will learn how to integrate objects of the library of this application into an
empty or existing project.
This example uses the unconnected STEP 7 block, the “PID_Icon” faceplate icon
and the faceplates belonging to the “PID” screen window.
Note The application provides a properly functioning example project with connected
example blocks. You only need to perform the steps explained in this chapter, if
you wish to integrate the blocks into your own project.
If you are only interested in operating the application example, you can directly
jump to the chapter “Operating the Application”.
In this case, it is sufficient to unzip the file
“66839614_WCA_Faceplates_Demo_V13_SP1.zip” and to open it in the TIA
Portal.
NOTICE Process coupling has been configured for Industrial Ethernet.

Please adjust the settings for CPU, “HMI station” and “PG/PC interface”, if
necessary.

Entry ID: 66839614, V1.0, 05/2016 55
5.1 Configuring the STEP 7 block
5.1 Configuring the STEP 7 block

Table 5-1
Process Description
1. Creating a new project
 Create a new project with a S7-1200 or S7-1500 controller or open an
existing project.
For this, click “Devices & networks” in the project tree and then click the
“Hardware catalog” task card. Select the desired controller from the
“Catalog” palette and drag it into your hardware configuration.
Note
If you are using an existing project, it is advisable to create a backup before
performing the following steps.
2. Opening the library
 In the “Libraries” task card, click on the “Open global library” icon in the
“Global libraries” palette.
 To do this, navigate to the storage location of the
“66839614_STEP7_Example_Blocks_V13_SP1.al13” library
and open the library.
3. Inserting blocks
 Drag the “PIDCtrlV2” (FB700) function block from the “Master copies >
PIDCTRLV2” folder in the project tree to the “Program blocks” directory

of the controller.
 Optional: Drag the “PIDCTRLV2_DB” instance data block from the
“Master copies > PIDCTRLV2” folder in the project tree to the “Program
blocks” directory of the controller.
4. Calling the blocks
 Integrate the function block into the cycle of the controller. If you call the
function block in an organization block, you will be asked for the name of
the associated instance data block in the “Call options” dialog when
inserting the function block:
 You can automatically generate the associated instance data block or
use the “PIDCTRLV2_DB” instance data block from the library. Select
the desired instance data block and click “OK”.

Entry ID: 66839614, V1.0, 05/2016 56
5.2 Configuring the WinCC Advanced faceplates

5.2.1 Opening the global library
Table 5-2
Step Procedure
1. Opening the project
 Open the TIA Portal project.
2. Integrating the global library
 Open the “Libraries > Global libraries” task card.
 Via the context menu “Open library”, select the dialog to open a global library.
 Open the storage location of your global library

“66839614_WCA_Faceplates_Library_V13_SP.al13”.
 Select the global library.
 Confirm your selection by clicking “Open”.

Entry ID: 66839614, V1.0, 05/2016 57
5.2.2 Integrating the library elements into the project
The library offers two possibilities of integrating the faceplates into your project.
 The faster way of doing this is to use the elements contained in the “Master
copies” folder.
In this folder, you will find the pop-up screen containing the menu structure and
the faceplates as well as the faceplate icon, the invisible button associated with
the faceplate icon for calling the pop-up screen and the necessary tags.
For this configuration variant, please refer to Table 5-3.
 If you want to use the faceplates in a separate menu structure or you don’t
want to use any pop-up screen, you will find the individual faceplates in the
“Types” folder in the global library.
For this configuration variant, please refer to Table 5-4.
Configuring by means of master copies

Table 5-3
Step Procedure
1. Opening the project
 Open the TIA Portal project.

Add the desired HMI operator panel, if it is not available yet.

For this, click “Devices & networks” in the project tree and then click the “Hardware
catalog” task card. Select the desired HMI operator panel from the “Catalog” palette and
drag it into your hardware configuration.
 Open the HMI project of your HMI operator panel in the project tree.
2. Opening the global library
Open the global library as described in Table 5-2.

Entry ID: 66839614, V1.0, 05/2016 58
Step Procedure
3. Copying library elements
 Drag and drop the following library elements from the “Master copies > PIDCTRLV2”
folder of the global library into the corresponding folders in the project tree:
– “PID_001_Tags”  “HMI tags”
– “PID_001_Messages”  “HMI alarms”
– “PID_001_Pop-up”  “Screen management > Pop-up screens”
 Drag and drop the “MenuControl” tag table from the “Master copies > MenuControl” folder
of the global library into the “HMI tags” folder in the project tree.
Check the connection of the tags and restore it, if necessary.


Entry ID: 66839614, V1.0, 05/2016 59
Step Procedure
4. Integrating the messages
 Within the library, select the “Master copies > PIDCTRLV2” category.
 Drag and drop the “PID_001_Messages” folder into the “HMI alarms” folder in the project
tree.
Note
The message numbers of this application occupy the number range starting at 10065.
Before integrating the messages, check your existing project and, if occupied, release this
area.
Restore the connection to the associated trigger tag as well as the associated trigger bit.

Entry ID: 66839614, V1.0, 05/2016 60
Step Procedure
5. Creating the HMI screen
 Drag and drop the “PID_001_Icon” faceplate icon and the “PID_001_Button” button for
calling the “PID_001_Pop-up” screen window into the desired screen.
 Place the button above the faceplate icon.
Click the “Layout” task card and make sure that the button is assigned to a level with a
higher number than that of the faceplate icon.
6. Check the name of the HMI connection and correct it, if necessary.

Entry ID: 66839614, V1.0, 05/2016 61
Configuring by means of types

Table 5-4
Step Procedure
1. Opening the project and library
Open the global library as described in Table 5-2.
2. Copying library elements
Drag and drop the “PIDCTRLV2” folder containing the faceplates and the HMI UDT from the
“Types” folder of the global library into the “Types” folder of the project library.

Entry ID: 66839614, V1.0, 05/2016 62
Step Procedure
3. The “PIDCtrlV2” folder contains the faceplates of the screen window:
 “PID_1_Overview”
 “PID_2_Messages”
 “PID_3_Graphs”
 “PID_4_Parameters”
 “PID_5_ActualValue”
 “PID_6_Setpoint”
 “PID_7_Limits”
 “PID_8_Service”
Moreover, it contains the faceplate of the faceplate icon and the HMI UDT:
 “PID_001_Icon”
 “PIDCTRLV2_UDT”
4. A complete configuration requires the following elements from the “Master copies >
PIDCTRLV2” folder:
 “PID_001_Tags” (HMI tags)

 “PID_001_Messages” (HMI alarms)
 “PID_001_Button” (button)
Furthermore, you need the tags from the “MenuControl” tag table from the “Master copies >
MenuControl” folder:
 “PID_Unit”
 “Visibility”
 Optional: “Close”
Check the connection of the tags and restore it, if necessary.
Now, create your own menu structure of the individual faceplates and add the corresponding
values to the tags mentioned.
5. Interconnecting the faceplate icon
 Interconnect the dynamic properties of the individual faceplates of the screen window as
available at the respective interface:

Entry ID: 66839614, V1.0, 05/2016 63
Step Procedure
6. Interconnecting the faceplates of the screen window
 Interconnect the dynamic properties of the individual faceplates of the screen window, if
available, with the associated HMI tags:
– “Process > Value”  “PID_001_UDT”
– “Property > Visibility”  “Visibility”
– “Property > Unit”  “PID_Unit”
7. Integrating the messages

 Within the library, select the “Master copies > PIDCTRLV2” category.
 Drag and drop the “PID_001_Messages” folder into the “HMI alarms” folder in the project
tree.
Note
The message numbers of this application occupy the number range starting at 10065.
Before integrating the messages, check your existing project and, if occupied, release this
area.
Restore the connection to the associated trigger tag as well as the associated trigger bit.

Entry ID: 66839614, V1.0, 05/2016 64
6 Operating the Application

Here you will find out how to operate the example project and which options the
blocks provide to intervene in the process.
Table 6-1
Step Description
1. Unzip the “66839614_WCP_Faceplates_Demo_V13_SP1.zip” file into a directory
of your choice.
2. Open the project with TIA Portal V13 SP1 update 1 or higher.
3. Adjust the configured hardware according to your requirements at “Devices &
networks”.
4. Open the STEP 7 project and generate it again.
5. Load the STEP 7 project into the controller and start it.
6. Open the WinCC V13 Advanced project and generate it again.
7. Start the WinCC flexible Runtime or the WinCC Runtime simulation.

Entry ID: 66839614, V1.0, 05/2016 65
6.1 Navigation
6.1 Navigation
Overview of the user interface
Figure 6-1
2
4
Table 6-2
Figure Explanation
1 Start screen
Here you can choose between the application examples and the support
pages by means of the buttons in the bottom area.
2 Application example
Here you can reach the example blocks of this application.
3 Support
Here you will find out more about the Siemens Industry Online Support.
4 Navigation
You reach the navigation in each screen at the left window frame.
You reach the start screen via this button.
This button takes you to the preceding screen.
Close the application via this button.
This button enables you to change the language.

Entry ID: 66839614, V1.0, 05/2016 66
6.1 Navigation
Element selection
Figure 6-2
1
Table 6-3
Figure Explanation
1 Primary navigation
Here you can select the individual sets of the application via buttons.
The application consists of a total of two sets with four elements each.
2 Secondary navigation
Here, the individual elements (example blocks) of the selected set can be
accessed.

Entry ID: 66839614, V1.0, 05/2016 67
6.1 Navigation
Calling up the screen window

Figure 6-3
2
Table 6-4
Figure Explanation
1 When calling an element of this application, the faceplate icon becomes
visible.
2 When selecting the faceplate icon, the appropriate screen window containing
more detailed information opens.
Screen window operation

Figure 6-4
1
2
Table 6-5
Figure Explanation
1 Close
The screen window can be closed via this button.
2 Tab
The individual faceplate windows can be called via the tabs.

Entry ID: 66839614, V1.0, 05/2016 68
6.2 Faceplate icon
6.2 Faceplate icon

Overview
Figure 6-5
Features
 Simplified status display
 Opens the respective screen window via mouse-click
 Contains no language-dependent objects
Functionality
 Displayed operating states:
–
Setpoint value
– Actual value
– Manual setpoint value
– Enabled variable component
– Signal processing
– Operating mode
– Interlock
 Displayed warnings:
– Warning upper actual value limit
– Warning lower actual value limit
 Displayed errors:
– General error
 Operation:
– Calling up the assigned faceplate window

Entry ID: 66839614, V1.0, 05/2016 69
6.2 Faceplate icon
Possible operating states:
Table 6-6
State QdwState Icon Flashing
Actual value within Bits 12, 13, 14 and no
the limit values 15 = 0
Alarm lower limit Bit 12 = 1 yes
undercut
Warning lower Bit 13 = 1 no
warning limit
undercut
Warning upper Bit 14 = 1 no
warning limit
exceeded
Alarm upper limit Bit 15 = 1 yes
exceeded
Possible status displays:
Table 6-7
State Icon
P component OFF
P component ON
I component OFF
I component ON
D component OFF
D component ON
Upper warning limit actual value OFF
Upper warning limit actual value ON
Lower warning limit actual value OFF
Lower warning limit actual value ON
Signal processing of manual value

Signal processing of process value
Mode REMOTE
Mode LOCAL
Interlock OFF
Interlock ON
Interlock triggered
No error
Error pending

Entry ID: 66839614, V1.0, 05/2016 70
6.3 Screen window
6.3 Screen window

6.3.1 Menu system und “Close” button
Features
 Enables changes for service staff
Executable actions
 Tab selection (optionally via the controller)
 Open, close
6.3.2 Faceplate “PID_1_Overview”
Click the “Overview” tab to call the faceplate.
Overview
Figure 6-6
Features
 Detailed status display
 Provides the option of intervening in the process
Executable actions
 Specifying a setpoint (only in “Remote” operating mode)
 Specifying a manual setpoint (only in “Local” operating mode)
 Reset error states

Entry ID: 66839614, V1.0, 05/2016 71
6.3 Screen window
Possible operating states:

Table 6-8
State QdwState Icon Flashing
Actual value within Bits 12, 13, 14 and no
the limit values 15 = 0
Alarm lower limit Bit 12 = 1 yes
undercut
Warning lower Bit 13 = 1 no
warning limit
undercut
Warning upper Bit 14 = 1 no
warning limit
exceeded
Alarm upper limit Bit 15 = 1 yes
exceeded
Possible status displays:

Table 6-9
Displays State State
Off On
P component
I component
D component
Real value
Manual value
Remote operating mode
Inverted
External error
Interlock
General error

Entry ID: 66839614, V1.0, 05/2016 72
6.3 Screen window
6.3.3 Faceplate “PID_2_Messages”
Click the “Messages” tab to call the faceplate.
Overview
Figure 6-7
Executable actions
 Display of block-related alarms and messages
 Acknowledge alarms
 Filter for instance-related messages and alarms
6.3.4 Faceplate “PID_3_Graphs”
Click the “Graphs” tab to call the faceplate.
Overview
Figure 6-8
Executable actions
 ActualValue = actual value (controlled variable)

Entry ID: 66839614, V1.0, 05/2016 73
6.3 Screen window
 OutputValue = manually specified setpoint in local operating mode (manual

value)
 Setpoint = setpoint in remote operating mode (reference variable)
6.3.5 Faceplate “PID_4_Parameters”
Click the “Parameters” tab to call the faceplate.
Overview
Figure 6-9
Executable actions
 Setting parameters for the P component
– Gain
– Weighting
 Setting parameters for the I component
– Integration time
 Setting parameters for the D component
– Derivative action time
– Weighting
 Making further settings
– Sampling time
– Reversing the control direction
 Toggling the control direction
– Normal
– Inverted

Entry ID: 66839614, V1.0, 05/2016 74
6.3 Screen window
6.3.6 Faceplate “PID_5_ActualValue”
Click the “Actual value” tab to call the faceplate.
Overview
Figure 6-10
Executable actions
 Setting the upper warning limit of the actual value
 Setting the lower warning limit of the actual value
6.3.7 Faceplate “PID_6_Setpoint”
Click the “Setpoint” tab to call the faceplate.
Overview
Figure 6-11
Executable actions
 Setting the upper output value limit
 Setting the lower output value limit

Entry ID: 66839614, V1.0, 05/2016 75
6.3 Screen window
 Setting the minimal ON time of the PWM output signal

 Setting the minimal OFF time of the PWM output signal
6.3.8 Faceplate “PID_7_Limits”
Click the “Limits” tab to call the faceplate.
Overview
Figure 6-12
Executable actions
 Actual value scaling
– Setting the upper process value limit
– Setting the lower process value limit
– Setting the lower analog value limit
– Setting the upper analog value limit
 Actual value limits
– Setting the lower actual value limit
– Setting the upper actual value limit

Entry ID: 66839614, V1.0, 05/2016 76
6.3 Screen window
6.3.9 Faceplate “PID_8_Service”
Click the “Service” tab to call the faceplate.
Overview
Figure 6-13
Executable actions
 Switching over the process input
– I/O value (analog value)
– Real value
 Switching over the operating mode
– Local operating mode
– Remote operating mode
 Blocking and releasing of the manual parameterization
– Setting the values of the PID parameters and the manual value (menu item
“Overview”) is only possible in remote operating mode.
– If manual parameterization is blocked, the values of the PID parameters
from the process are applied.

Entry ID: 66839614, V1.0, 05/2016 77
7 Block Interfaces
7.1 Input parameters
7 Block Interfaces
Table 7-1
Parameters Data type Default setting Description
EN BOOL FALSE Release
InvertControl BOOL FALSE 1= Activate inversion of control
direction
InputPerOn BOOL FALSE 0= real value, 1= S7 periphery
InputUpperLimit REAL 120.0 Input of upper actual value limit
(%)
InputLowerLimit REAL 0.0 Setting the lower actual value
limit (%)
UpperPointOut REAL 100.0 Input of scaled upper actual
value (%)
LowerPointOut REAL 0.0 Input of scaled lower actual
value (%)
UpperPointIn REAL 27648.0 Input of upper value of
Input_PER
LowerPointIn REAL 0.0 Input of lower value of

Input_PER
InputUpperWarning REAL 200.0 Input of upper warning limit (%)
InputLowerWarning REAL -200.0 Input of lower warning limit (%)
MinimumOnTime REAL 0.0 Input of minimum switch-on time
(s)
MinimumOffTime REAL 0.0 Input of minimum switch-off time
(s)
OutputUpperLimit REAL 100.0 Input of upper limit of the output
value (%)
OutputLowerLimit REAL 0.0 Input of lower limit of the output
value (%)
SetpointUpperLimit REAL 100.0 Upper setpoint value limit
SetpointLowerLimit REAL 0.0 Lower setpoint value limit
PIDManualEnable BOOL FALSE 1= Enable controller parameter
Gain REAL 1.0 Enter the proportional gain
Ti REAL 20.0 Enter the integration time (s)
Td REAL 0.0 Enter the derivative time (s)
TdFiltRatio REAL 0.0 Enter the derivative time lag
coefficient
PWeighting REAL 1.0 Enter the weighting of the P
component
DWeighting REAL 1.0 Enter the weighting of the D
component
Cycle REAL 0.5 Enter the sampling time for the
PID algorithm (s)
Setpoint REAL 0.0 Setpoint of the PID controller in
remote operating mode
Input REAL 0.0 Actual value in REAL format

Entry ID: 66839614, V1.0, 05/2016 78
7 Block Interfaces
Parameters Data type Default setting Description

Input_PER INT 0 Analog actual value (I/O)
ManualValue REAL 0.0 This value is used as output
value in local operating mode
LOCK BOOL FALSE 1= interlock pending
ERR_EXTERN BOOL FALSE 1= external error
LIOP_SEL BOOL FALSE 0= operator, 1= interconnection
L_AUT BOOL FALSE 0= manual value active
1= process value active
L_REMOTE BOOL FALSE 0= local, 1= remote
L_RESET BOOL FALSE Reset errors (pos. edge)
INSTANCE STRING[16] PID_001_UDT Filter attribute for messages,
labeling of title bar
RESTART BOOL FALSE Initializing at restart
VISIBILITY BYTE 0 Representation of
faceplate window
OPdwCmd DWORD 0 Control tag (HMI)

Entry ID: 66839614, V1.0, 05/2016 79
7 Block Interfaces
7.2 Output parameters
7.2 Output parameters

Table 7-2
Parameters Data type Default Description
setting
QSetpoint REAL 0.0 Setpoint of the PID controller in
remote operating mode
ScaledInput REAL 0.0 Scaled actual value
Output REAL 0.0 Output value in REAL format
Output_PER INT 0 Analog output value
Output_PWM BOOL FALSE 1= pulse width modulation output
ON
SetpointLimit_H BOOL FALSE 1= absolute upper limit of setpoint
value reached
SetpointLimit_L BOOL FALSE 1= absolute lower limit of setpoint
value reached
InputWarning_H BOOL FALSE 1= upper warning limit of actual
value reached or exceeded
InputWarning_L BOOL FALSE 1= lower warning limit of actual
value reached or undercut
State INT 0 The State parameter indicates the
current operating mode of the PID

controller
Error BOOL FALSE 1= at least one error message
within the current cycle
ErrorBits DWORD DW#16#0 The ErrorBits parameter displays
the pending error messages
QGain REAL 0.0 Proportional gain used
QTi REAL 0.0 Integration time used
QTd REAL 0.0 Derivative time used
QdwState DWORD DW#16#0 Status tag (HMI)
QPERIPH BOOL FALSE 0= real value active, 1= S7
periphery active
QMAN_AUT BOOL FALSE 0= manual value active
1= process value active
QREMOTE BOOL FALSE 0= local, 1= remote
QLOCK BOOL FALSE 1= interlock error
QERR BOOL FALSE 1= error
QERR_EXT BOOL FALSE 1= external error
QwAlarm WORD W#16#0 Alarm tag
ENO BOOL FALSE Release

Entry ID: 66839614, V1.0, 05/2016 80
8 Additional Information
8 Additional Information
Further example blocks of this application
This document is part of an application which describes further technology blocks.
Within the framework of this application, the number of example technology blocks
is successively expanded.
The following table shows both the already available and the future example
technology blocks:
Table 8-1
Block Description
MOTOR Visualization and operation of a motor with fixed speed and rotational
direction
VALVE Visualization and operation of a binary valve
DIGITAL Visualization and operation of digital signals.
ANALOG Visualization and operation of analog signals
PIDCTRLV2 Visualization and operation of a software-implemented PID controller for
regulating technical parameters with continuous input and output values
SIMODIR Visualization and control of the motor management system SIMOCODE

Pro as direct starter
SIMOREV Visualization and control of the motor management system SIMOCODE
Pro as reversing starter
SINAG120 Visualization and control of the SINAMICS G120 frequency converter
Further example block applications

(TIA Portal / STEP 7 V5 / WinCC V7 / WinCC flexible)
Table 8-2
Topic Title
Example blocks for https://support.industry.siemens.com/cs/ww/de/view/68679830
WinCC V7 and
STEP 7 V5
WinCC V7 and
STEP 7 (TIA Portal)
WinCC flexible and
STEP 7 V5

Entry ID: 66839614, V1.0, 05/2016 81
9 Links & Literature
9 Links & Literature

Bibliographic references
This list only represents a selection of relevant information.
Table 9-1
Topic Title
\1\ Reference to the entry https://support.industry.siemens.com/cs/ww/en/view/66
839614
\2\ Siemens Industry https://support.industry.siemens.com
Online Support
\3\ STEP 7 Automating with SIMATIC S7-1200
SIMATIC S7-1200 Author: Hans Berger
Publicis MCD Verlag
ISBN: 978-3-89578-355-5
\4\ STEP 7 Automating with SIMATIC S7-1500
SIMATIC S7-1500 Author: Hans Berger
Publicis MCD Verlag
ISBN: 978-3-89578-403-3
\5\ STEP 7 Automating with STEP 7 in STL and SCL
STL and SCL Author: Hans Berger

Publicis MCD Verlag
ISBN: 978-3-89578-397-5
\6\ SIMATIC S7-1500, https://support.industry.siemens.com/cs/ww/en/view/67
ET 200MP, ET 200SP, 989094
ET 200AL, ET 200pro,
ET 200eco PN Analog
value processing
\7\ Faceplates for the https://support.industry.siemens.com/cs/ww/en/view/67
Visualization of 318600
SENTRON PAC Power
Meters for
WinCC Runtime
Professional
\8\ SITOP UPS1600: https://support.industry.siemens.com/cs/ww/en/view/78
Faceplates and STEP 7 817848
communication blocks
\9\ Measuring and https://support.industry.siemens.com/cs/ww/en/view/86
Visualizing Energy 299299
Data
\10\ Configuration https://support.industry.siemens.com/cs/ww/en/view/68
instruction for creating 014632
faceplates for Comfort
Panels and
WinCC Runtime
Advanced

Entry ID: 66839614, V1.0, 05/2016 82
10 History
10 History
Table 10-1
Version Date Modifications
V1.0 05/2016 New version TIA Portal V13 SP1 update 1

Entry ID: 66839614, V1.0, 05/2016 83

WCA Faceplate PIDCtrlV2 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WCA Faceplate PIDCtrlV2 en

Uploaded by

Copyright:

Available Formats

Application example  05/2016

TIA Portal Example Block

Warranty and liability

deficiency or breach of a condition which goes to the root of the contract

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

6.3.3 Faceplate “PID_2_Messages” ............................................................ 73

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

– The screen objects for WinCC Advanced are completely interface-

Topics not covered by this application

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

Description of the automation task

The block offers the following functions:

 Limit value configuration

NOTICE It might be necessary to make some adjustments.

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

technology block “PIDCtrlV2” (FB 700) is interconnected with a PT1 element

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

2.1 Overview of the overall solution

The screen window consists of a pop-up screen

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

2.2 Hardware and software components

This application is valid for

2.2.2 Components used

The application has been created with the following components:

Example files and projects

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

3.1 Library objects

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

Types and instances

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.1 Faceplate icon

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

 The “DID_001_UDT” UDT tag of the controller is connected at the “Value”

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.2 Interfaces of the faceplate icon

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.3 Screen window

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

No. Function, tag Usage

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4 Components of the screen window

The following options are available:

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4.1 Faceplate “PID_1_Overview”

The “PID_1_Overview” faceplate is used for displaying current process values as

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4.2 Faceplate “PID_2_Messages”

The “PID_2_Messages” faceplate is used for the displaying messages.

The message view is divided into six columns:

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4.3 Faceplate “PID_3_Graphs”

The “PID_3_Graphs” faceplate is used for displaying graphs.

4.4.4 Faceplate “PID_4_Parameters”

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4.5 Faceplate “PID_5_ActualValue”

4.4.6 Faceplate “PID_6_Setpoint”

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

4.4.7 Faceplate “PID_7_Limits”

4.4.8 Faceplate “PID_8_Service”

PIDCtrlV2 (WinCC Advanced V13 SP1, STEP 7 V13 SP1)