WCA Faceplate Analog en

Application example  05/2016
TIA Portal Example Block

“ANALOG“
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.
ANALOG (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 .......................................................... 15
4.3 Screen window ................................................................................... 17
4.4 Components of the screen window .................................................... 19
4.4.1 Faceplate “Analog_1_Overview” ........................................................ 21
4.4.2 Faceplate “Analog_2_Messages” ...................................................... 21
4.4.3 Faceplate “Analog_3_Graphs” ........................................................... 22
4.4.4 Faceplate “Analog_4_Limits”.............................................................. 23
Faceplate “Analog_5_Service” ........................................................... 24
4.4.5
4.5 Interfaces of the screen window ......................................................... 25
4.6 Tags of the UDT ................................................................................. 26
4.6.1 Process............................................................................................... 26
4.6.2 Process_Limits ................................................................................... 28
4.6.3 Process_Values ................................................................................. 31
4.6.4 Static properties of the screen window .............................................. 31
4.7 Alarms and messages ........................................................................ 32
4.8 Control and status signals .................................................................. 34
4.8.1 Processing of switching commands in the controller ......................... 34
4.8.2 Evaluating process states and displaying them in
WinCC Advanced ............................................................................... 35
4.8.3 Defining the range of values .............................................................. 38
4.8.4 Limit monitoring .................................................................................. 39
4.8.5 Enabling/disabling the simulation ....................................................... 41
4.8.6 Resetting errors .................................................................................. 43
5 Commissioning the Application ..................................................................... 45
5.1 Configuring the STEP 7 block ............................................................ 46
5.2 Configuring the WinCC Advanced faceplates .................................... 47
5.2.1 Opening the global library .................................................................. 47
5.2.2 Integrating the library elements into the project ................................. 48
6 Operating the Application ............................................................................... 55
6.1 Navigation .......................................................................................... 56
6.2 Faceplate icon .................................................................................... 59
6.3 Screen window ................................................................................... 60
6.3.1 Menu system und “Close” button ....................................................... 60
6.3.2 Faceplate “Analog_1_Overview” ........................................................ 60
6.3.3 Faceplate “Analog_2_Messages” ...................................................... 62
6.3.4 Faceplate “Analog_3_Graphs” ........................................................... 63
6.3.5 Faceplate “Analog_4_Limits”.............................................................. 64
6.3.6 Faceplate “Analog_5_Service” ........................................................... 65

Entry ID: 66839614, V1.0, 05/2016 3
Table of contents
7 Block Interfaces ............................................................................................... 67

7.1 Input parameters ................................................................................ 67
7.2 Output parameters ............................................................................. 68
8 Additional Information .................................................................................... 69
9 Links & Literature ............................................................................................ 70
10 History............................................................................................................... 71

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 faceplates 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 “ANALOG” example technology
block (FB 640) as well as the configuration and operation of the associated
faceplates.
They are used to visualize and control an analog signal.
The blocks offer the following functions:

 Scaling peripheral values (unipolar/bipolar) in integer format
 Signal processing alternatively in integer or real format
 Setting limits for alarm triggering
 Setting a hysteresis for the limits (percental or absolute)
 Simulating the signal
The following (associated) values of the signal to be monitored are displayed:

 Range limit values
 Instantaneous value (numerically and as a trend)
 Limits (numerically and as trends)
 Hysteresis (absolute and percental)
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
“ANALOG” (FB 640) for the controller family S7-1200/S7-1500 and the respective
screen objects for WinCC Advanced.
These are intended for visualizing an analog value and its limits.
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.

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 modifying and monitoring analog
signals.
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.
Standard 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_SP1_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
 Contains no language-dependent objects
 Has a defined interface
Parameters
Table 4-1
No. Path Usage
1. Properties > Miscellaneous > Name Analog_001_Icon
2. Interface > State Analog_001_UDT.QdwState
3. Interface > Unit Analog_Unit
4. Interface > Value Analog_001_UDT.QOUT

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 “Analog_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 “State”,
“Unit” and “Value” for displaying the analog values and all other objects.
 The “QdwState” tag of the controller is connected at the “State” property of

the faceplate instance. It is required for displaying the status signals.
 The “Analog_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.
 The “ScaledInput” tag of the controller is connected at the “Value” property
of the faceplate instance and is used for displaying the analog value.
3. Note
Please note that the process tag is an element of the UDT used, in this case
“Analog_001_UDT”, and hence, the tag name has the according prefix:
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 13
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 “Analog_001_Button” button, the “ShowPopupScreen” event must be
configured in “Events > Release” for the “Analog_001_Pop-up” pop-up screen.
Set the “Visibility” tag to “1” to display the “Analog_1_Overview” faceplate after
opening the screen window as start screen.

Entry ID: 66839614, V1.0, 05/2016 14
4 Mode of Operation
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.
State
The “State” property is used to display the different states in the WinCC Advanced
process display.
Table 4-3
Tag used
Symbolic name Analog_001_UDT.QdwState
Data type DWord
Access type %DB640.DBD308
Length 4 bytes
Acquisition cycle 100 ms
Acquisition mode Cyclic in operation

Entry ID: 66839614, V1.0, 05/2016 15
4 Mode of Operation
The following table shows the setup of the “QdwState” tag.
Table 4-4 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
QERR_HIGHRANGE
QERR_LOWRANGE
QERR_OVERRUN
LIM_ULW_Enable
LIM_LLW_Enable
LIM_ULA_Enable
LIM_LLA_Enable
LIM_HYS_Set
QERR_WIRE
QERR_EXT
IN_MODE
QALARM
QWARN
QLOCK
Signal
QERR
LOCK
Wert QSIM
The “Value” property is used to acquire the analog value at the block output.
Table 4-5
Tag used
Symbolic name Analog_001_UDT.QOUT
Data type Real

Length 4 bytes
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-6
Tag used
Name Analog_Unit
Data type String
Access type Internal tag
Length 10

Entry ID: 66839614, V1.0, 05/2016 16
4 Mode of Operation
4.3 Screen window
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:

Entry ID: 66839614, V1.0, 05/2016 17
4 Mode of Operation
4.3 Screen window
Table 4-7
No. Function, tag Usage
1. SetTag X1Pos Position of the toolbar at the tab
2. SetTag Visibility Indicator for selecting a tab
Explanation
Table 4-8
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}
2. The identifier of the currently activated tab is stored in the INT tag “Visibility”:
Visibility = {1, 2, 3, 4, 5 }

Entry ID: 66839614, V1.0, 05/2016 18
4 Mode of Operation
4.4 Components of the screen window
No. Explanation
3. Click on the “X” to close the screen window. The screen shows the system
function stored.

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

Entry ID: 66839614, V1.0, 05/2016 19
4 Mode of Operation
The following options are available:
Table 4-9
No. Tab Faceplate Function
1. Overview Analog_1_Overview Overview of the current analog value, the
limits set and the status and error displays
2. Messages Analog _2_Messages Display of messages (warnings and errors)
3. Graphs Analog _3_Graphs Graph display for graphic visualization of the
limits and of the analog value
4. Limits Analog _4_Limits Limit settings
5. Service Analog _5_Service Settings for process input, hysteresis and
simulation mode
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.
Table 4-10
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.

Entry ID: 66839614, V1.0, 05/2016 20
4 Mode of Operation
4.4.1 Faceplate “Analog_1_Overview”
The “Analog_1_Overview” faceplate is used for displaying current process values

as well as possibly pending error messages.
Figure 4-5
4.4.2 Faceplate “Analog_2_Messages”
The “Analog_2_Messages” faceplate is used for displaying messages.

It is intended to display warnings and errors with the filter prefix “Analogue_” in the
message text. Alternatively, instance-related filtering of the messages is possible.
Figure 4-6

Entry ID: 66839614, V1.0, 05/2016 21
4 Mode of Operation
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)
4.4.3 Faceplate “Analog_3_Graphs”
The “Analog_3_Graphs” faceplate is used for displaying graphs. It contains a graph

view.
Figure 4-7

Entry ID: 66839614, V1.0, 05/2016 22
4 Mode of Operation
4.4.4 Faceplate “Analog_4_Limits”
The “Analog_4_Limits” faceplate is used to set the limits for displaying the analog
value.
Figure 4-8
Note  Write access to the values of this tab is possible only in simulation mode.
 The hysteresis can be entered either as an absolute value or as a percentage value.
For the respective settings, please go to the “Service” tab.

Entry ID: 66839614, V1.0, 05/2016 23
4 Mode of Operation
4.4.5 Faceplate “Analog_5_Service”
The “Analog_5_Service” faceplate is used to set the process input, the hysteresis
as well as the simulation mode. Moreover, the name of the corresponding instance
is displayed.
Figure 4-9

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 “Analog_001_UDT” screen objects, the defined data structure
“Analog_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: “Analog_001_UDT” (1):
Figure 4-10
1 2
When creating a new tag, e. g. “Analog_002_UDT” of the “Analog_UDT” data type,

the following structure elements will be defined automatically for each structure tag:
 Name
 PLC data type
 Address
 Start value
 Comment

Entry ID: 66839614, V1.0, 05/2016 25
4 Mode of Operation
4.6 Tags of the UDT
Note The name of the instance automatically defines the tag prefix of the individual
structure elements (e. g. “Analog_001_UDT”.
 In the project, the tag prefix must precede each location of usage of the
structure elements, e. g. “Analog_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 Process
The HMI tags of this group have a process connection and constitute the basic
interface between controller and operating panel.
Command
The “Command” property is used to transmit commands from WinCC Advanced 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-11
Tag used
Symbolic name Analog_001_UDT. OPdwCmd
Data type DWord
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 “OPdwCmd” tag.
Table 4-12 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
Wa_Lower_Limit
Wa_Upper_Limit
HYS_Percental
Al_Lower_Limit
Al_Upper_Limit
HYS_Absolute
SIMULATION
PeripheryVal
PROCESS
RealVal
RESET
Signal
State
The “State” property is used to display the different states in the WinCC Advanced
process display.
Table 4-13
Tag used
Symbolic name Analog_001_UDT.QdwState
Data type DWord

Length 4 bytes

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
QERR_HIGHRANGE
QERR_LOWRANGE
QERR_OVERRUN
LIM_ULW_Enable
LIM_LLW_Enable
LIM_ULA_Enable
LIM_LLA_Enable
LIM_HYS_Set
QERR_WIRE
QERR_EXT
IN_MODE
QALARM
QWARN
QLOCK
Signal
QERR
LOCK
QSIM

Entry ID: 66839614, V1.0, 05/2016 27
4 Mode of Operation
4.6 Tags of the UDT
4.6.2 Process_Limits
The HMI tags in this group have a process connection and can be operated and
monitored in the “Overview” or “Limits” tab.
The “Graphs” tab clearly shows the relevant values as trends and lines. However,
the tags can only be monitored in this tab.
The tags are used to define the upper and lower limit of an analog value and to
define limits for message triggering.
HighLimit
The “HighLimit” property indicates the upper limit of the analog value.
Table 4-15
Tag used
Symbolic name Analog_001_UDT. OP_HI_LIM
Data type Real
Length 4 bytes
LowLimit
The “LowLimit” property indicates the lower limit of the analog value.
Table 4-16
Tag used
Symbolic name Analog_001_UDT.OP_LO_LIM
Data type Real
Length 4 bytes
AlarmUpperLimit
The “AlarmUpperLimit” property indicates the upper limit of the analog value for
which an alarm is triggered. The deactivation of the alarm depends on the selected
hysteresis (limit minus hysteresis).
Table 4-17
Tag used
Symbolic name Analog_001_UDT.OP_LIM_ULA
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 28
4 Mode of Operation
4.6 Tags of the UDT
Tag used
Acquisition mode Cyclic continuous
WarningUpperLimit
The “WarningUpperLimit” property indicates the upper limit of the analog value for
which a warning is triggered. The deactivation of the warning depends on the
selected hysteresis (limit minus hysteresis).
Table 4-18
Tag used
Symbolic name Analog_001_UDT.OP_LIM_ULW
Data type Real
Length 4 bytes
WarningLowerLimit
The “WarningLowerLimit” property indicates the lower limit of the analog value for
which a warning is triggered. The deactivation of the warning depends on the
selected hysteresis (limit plus hysteresis).
Table 4-19
Tag used
Symbolic name Analog_001_UDT.OP_LIM_LLW
Data type Real
Length 4 bytes
AlarmLowerLimit
The “AlarmLowerLimit” property indicates the lower limit of the analog value for
which an alarm is triggered. The deactivation of the alarm depends on the selected
hysteresis (limit plus hysteresis).
Table 4-20
Tag used
Symbolic name Analog_001_UDT.OP_LIM_LLA
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 05/2016 29
4 Mode of Operation
4.6 Tags of the UDT
Hysteresis_Abs
The “Hysteresis_Abs” property indicates the hysteresis of the analog value.
Table 4-21
Tag used
Symbolic name Analog_001_UDT.OP_LIM_HYS_Abs
Data type Real
Length 4 bytes
Hysteresis_Perc
The “Hysteresis_Abs” property indicates the hysteresis value (in percent) of the
analog value.
Table 4-22
Tag used
Symbolic name Analog_001_UDT.OP_LIM_HYS_Perc

Data type Real
Length 4 bytes
Note Hysteresis
The hysteresis influences the deactivation of a warning or an alarm that was
triggered due to a limit violation.
Depending on the mode of the hysteresis, it can be specified either as an
absolute value or as a percentage value. Both values are converted and
displayed simultaneously.
The upper limit and the lower limit of the analog value are the basis for the
calculation.

Entry ID: 66839614, V1.0, 05/2016 30
4 Mode of Operation
4.6 Tags of the UDT
4.6.3 Process_Values
The tags in this group have a process connection and can be operated and
monitored in the “Overview” tab.
The table below shows the significance of the analog value at the block output in
the event of an error or a limit violation:
Table 4-23
Error Analog value
General error The analog value corresponds to the lower limit.
Overrun (for integer format only) The analog value corresponds to the upper limit.
Exceeding the upper limit The analog value corresponds to the upper limit.
Falling below the lower limit The analog value corresponds to the lower limit.
Wire break (for integer format only) The analog value corresponds to the lower limit.
Value
The “Value” property is used to acquire the analog value at the block output.
Table 4-24
Tag used
Symbolic name Analog_001_UDT.QOUT
Data type Real
Length 4 bytes
SimValue
The “SimValue” property is used to influence the analog value at the block output
in simulation mode.
Table 4-25
Tag used
Symbolic name Analog_001_UDT.OP_SIM_Value
Data type Real
Length 4 bytes
4.6.4 Static properties of the screen window
Static properties cannot be changed during runtime, this is why they never have a
process interface.

Entry ID: 66839614, V1.0, 05/2016 31
4 Mode of Operation
4.7 Alarms and messages
Process_Trends_Value
The properties of this group define the individual trends of the screen window.
Trends
The “Trends” property is a “SimpleCoreCollectionWrapper” and defines the graphs
of the “Graphs” tab. To edit the graphs, select the “Trends” property. The graph
editor is opened using the displayed “…” button.
Figure 4-11
Figure 4-12

This application uses the bit message procedure to display messages in
WinCC Advanced. The messages must be configured as bit messages in the
message editor of WinCC Professional.
In the sample configuration, all bit messages for the used faceplate instances have
already been created, just like their trigger tags.
Message tag
Table 4-26
Tag used
Symbolic name Analog_001_UDT.QwAlarm
Data type Word
Access type %DB640.DBW354
Length 2 bytes
The following table shows the setup of the tags. The message texts are preceded
by the “Analog_001” filter attribute for the first instance of the analog screen
window.

Entry ID: 66839614, V1.0, 05/2016 32
4 Mode of Operation
Table 4-27 Setup of the “QwAlarm” tag

Bit Signal Message text
2
0 QALARM_LL Analog_001: Alarm lower limit undercut
1
1 QALARM_UL Analog_001: Alarm upper limit exceeded
2 Analog_001:
3 Analog_001:
4 QLOCK Analog_001: Interlock, value locked
5 Analog_001:
6 QERR_EXT Analog_001: External error
7 QERR Analog_001: Group error
1
8 QWARN_LL Analog_001: Warning lower limit undercut
1
9 QWARN_UL Analog_001: Warning upper limit exceeded
10 Analog_001:
11 Analog_001:
12 LOCK Analog_001: Interlock pending
13 Analog_001:
14 Analog_001:
15 QSIM Analog_001: Simulation ACTIVE
2
Message includes the associated value of the limit that was up to date when the message was generated.

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

4.8.1 Processing of switching commands in the controller
The WinCC Advanced control tag “OPdwCmd” of a block is used to transmit

commands from WinCC Advanced 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”.
Further notes for the use in WinCC Advanced can be found under the “Command”
property.
Figure 4-13
“Analogue” (FB 640)
EN ENO
LOCK QdwState
ERR_EXTERN QOUT
LIOP_SEL QHI_LIM
L_SIM QLO_LIM
L_RESET QLIM_ULA_Enable
IN_MODE QLIM_ULA
BIPOLAR QLIM_ULW_Enable
IN_INT QLIM_ULW
IN QLIM_LLW_Enable
IN_SIM QLIM_LLW
HI_LIM QLIM_LLA_Enable
LO_LIM QLIM_LLA
LIM_ULA_Enable QLIM_HYS
LIM_ULA QALARM_UL
LIM_ULW_Enable QWARN_UL
LIM_ULW QWARN_LL
LIM_LLW_Enable QALARM_LL
LIM_LLW QSIM
LIM_LLA_Enable QLOCK
LIM_LLA QERR
LIM_HYS_Set QERR_EXT
LIM_HYS QERR_OVERRUN
INSTANCE QERR_HIGHRANG
RESTART QERR_LOWRANG
VISIBILITY QERR_WIRE
OPdwCmd QwAlarm

Entry ID: 66839614, V1.0, 05/2016 34
4 Mode of Operation
The following table shows the setup of the “OPdwCmd” tag.
Table 4-28 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
Wa_Lower_Limit
Wa_Upper_Limit
HYS_Percental
Al_Lower_Limit
Al_Upper_Limit
HYS_Absolute
SIMULATION
PeripheryVal
PROCESS
RealVal
RESET
Signal
4.8.2 Evaluating process states and displaying them in WinCC Advanced
The technology block of this application uses the output “QdwState” (DWORD) to
show the different states in the WinCC Advanced process display.
Further notes for the use in WinCC Advanced can be found under the “State”
property.
Figure 4-14
EN ENO
LOCK QdwState
ERR_EXTERN QOUT
LIOP_SEL QHI_LIM
L_SIM QLO_LIM
L_RESET QLIM_ULA_Enable
IN_MODE QLIM_ULA
BIPOLAR QLIM_ULW_Enable
IN_INT QLIM_ULW
IN QLIM_LLW_Enable
IN_SIM QLIM_LLW
HI_LIM QLIM_LLA_Enable
LO_LIM QLIM_LLA
LIM_ULA_Enable QLIM_HYS
LIM_ULA QALARM_UL
LIM_ULW_Enable QWARN_UL
LIM_ULW QWARN_LL
LIM_LLW_Enable QALARM_LL
LIM_LLW QSIM
LIM_LLA_Enable QLOCK
LIM_LLA QERR
LIM_HYS_Set QERR_EXT
LIM_HYS QERR_OVERRUN
INSTANCE QERR_HIGHRANG
RESTART QERR_LOWRANG
VISIBILITY QERR_WIRE
OPdwCmd QwAlarm

Entry ID: 66839614, V1.0, 05/2016 35
4 Mode of Operation

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
QERR_HIGHRANGE
QERR_LOWRANGE
QERR_OVERRUN
LIM_ULW_Enable
LIM_LLW_Enable
LIM_ULA_Enable
LIM_LLA_Enable
LIM_HYS_Set
QERR_WIRE
QERR_EXT
IN_MODE
QALARM
QWARN
QLOCK
Signal
QERR
LOCK
QSIM
Switching over inputs
To switch over the inputs, the following signals are used:
Figure 4-15
EN QdwState
LOCK QOUT
ERR_EXTERN QHI_LIM
LIOP_SEL QLO_LIM
L_SIM QLIM_ULA_Enable
L_RESET QLIM_ULA
IN_MODE QLIM_ULW_Enable
BIPOLAR QLIM_ULW
IN_INT QLIM_LLW_Enable
IN QLIM_LLW
IN_SIM QLIM_LLA_Enable
HI_LIM QLIM_LLA
LO_LIM QLIM_HYS
LIM_ULA_Enable QALARM_UL
LIM_ULA QWARN_UL
LIM_ULW_Enable QWARN_LL
LIM_ULW QALARM_LL
LIM_LLW_Enable QSIM
LIM_LLW QLOCK
LIM_LLA_Enable QERR
LIM_LLA QERR_EXT
LIM_HYS_Set QERR_OVERRUN
LIM_HYS QERR_HIGHRANG
INSTANCE QERR_LOWRANG
RESTART QERR_WIRE
VISIBILITY QwAlarm
OPdwCmd ENO
 “IN_MODE”
The “IN_MODE” input defines whether the “IN_INT” input or the “IN” input is
active.
“IN_MODE” = 0  “IN_INT” input active
“IN_MODE” = 1  “IN” input active

Entry ID: 66839614, V1.0, 05/2016 36
4 Mode of Operation
 “BIPOLAR”
The “BIPOLAR” input defines whether the scaling of the “IN_INT” input signal
is unipolar or bipolar.
“BIPOLAR” = 0  nominal range from 0 to +27648
“BIPOLAR” = 1  nominal range from -27648 to +27648
 “IN_INT”
The input is processed for the analog value display of an analog input module
in the 4-20 mA measuring range. The nominal range is defined from 0 to
+27648 (unipolar) or from -27648 to +27648 (bipolar).
For information on the analog value display of analog modules, please refer to
the following document:
https://support.industry.siemens.com/cs/ww/de/view/67989094
 “IN”
The value of the “IN” input is processed directly and passed on to “QOUT”
within the specified limits.

Entry ID: 66839614, V1.0, 05/2016 37
4 Mode of Operation
4.8.3 Defining the range of values
The range of values is defined by the “HI_LIM” and “LO_LIM” inputs. When
monitoring the process value of an analog input module, the nominal range is
scaled to this range depending on the “BIPOLAR” parameter.
Figure 4-16
EN QdwState
LOCK QOUT
ERR_EXTERN QHI_LIM
LIOP_SEL QLO_LIM
L_RESET QLIM_ULA
BIPOLAR QLIM_ULW
IN QLIM_LLW
HI_LIM QLIM_LLA
LO_LIM QLIM_HYS
LIM_ULA QWARN_UL
LIM_ULW QALARM_LL
LIM_LLW_Enable QSIM
LIM_LLW QLOCK
LIM_LLA_Enable QERR
LIM_LLA QERR_EXT
RESTART QERR_WIRE
VISIBILITY QwAlarm
OPdwCmd ENO
“HI_LIM”  upper range of values

“LO_LIM”  lower range of values

Entry ID: 66839614, V1.0, 05/2016 38
4 Mode of Operation
4.8.4 Limit monitoring
The limit monitoring is used to trigger a warning or an alarm if the signal to be

monitored exceeds or falls below one or several limits.
Figure 4-17
EN QdwState
LOCK QOUT
ERR_EXTERN QHI_LIM
LIOP_SEL QLO_LIM
L_RESET QLIM_ULA
BIPOLAR QLIM_ULW
IN QLIM_LLW
HI_LIM QLIM_LLA
LO_LIM QLIM_HYS
LIM_ULA QWARN_UL
LIM_ULW QALARM_LL
LIM_LLW_Enable QSIM
LIM_LLW QLOCK
LIM_LLA_Enable QERR
LIM_LLA QERR_EXT
RESTART QERR_WIRE
VISIBILITY QwAlarm
OPdwCmd ENO
 “LIM_ULA_Enable”
Enables the monitoring of the “LIM_ULA” limit for exceeding the limit to trigger
an alarm. The enable of the limit monitoring is indicated at the
“QLIM_ULA_Enable” output, the triggering of the alarm is displayed at the
“QALARM_UL” output. The “LIM_ULA” limit is mirrored to the “QLIM_ULA”
output irrespective of “LIM_ULA_Enable”.
“LIM_ULA_Enable” = 0  limit monitoring inactive
“LIM_ULA_Enable” = 1  limit monitoring active

Entry ID: 66839614, V1.0, 05/2016 39
4 Mode of Operation
 “LIM_ULW_Enable”
Enables the monitoring of the “LIM_ULW” limit for exceeding the limit to trigger
a warning. The enable of the limit monitoring is indicated at the
“QLIM_ULW_Enable” output, the triggering of the warning is displayed at the
“QWARN_UL” output. The “LIM_ULW” limit is mirrored to the “QLIM_ULW”
output irrespective of “LIM_ULW_Enable”.
“LIM_ULW_Enable” = 0  limit monitoring inactive
“LIM_ULW_Enable” = 1  limit monitoring active
 “LIM_LLW_Enable”
Enables the monitoring of the “LIM_LLW” limit for falling below the limit to
trigger a warning. The enable of the limit monitoring is indicated at the
“QLIM_LLW_Enable” output, the triggering of the warning is displayed at the
“QWARN_LL” output. The “LIM_LLW” limit is mirrored to the “QLIM_LLW”
output irrespective of “LIM_LLW_Enable”.
“LIM_LLW_Enable” = 0  limit monitoring inactive
“LIM_LLW_Enable” = 1  limit monitoring active
 “LIM_LLA_Enable”
Enables the monitoring of the “LIM_LLA” limit for falling below the limit to
trigger an alarm. The enable of the limit monitoring is indicated at the
“QLIM_LLA_Enable” output, the triggering of the alarm is displayed at the
“QALARM_LL” output. The “LIM_LLA” limit is mirrored to the “QLIM_LLA”
output irrespective of “LIM_LLA_Enable”.

“LIM_LLA_Enable” = 0  limit monitoring inactive
“LIM_LLA_Enable” = 1  limit monitoring active
 “LIM_HYS” and “LIM_HYS_Set”
The “LIM_HYS” value supplies the limit for deactivating a limit monitoring
message with a hysteresis. Depending on the “LIM_HYS_Set” parameter, the
value can be specified as an absolute value or as a percentage value.
“LIM_HYS_Set” = 0  “LIM_HYS” interpreted as a percentage value
“LIM_HYS_Set” = 1  “LIM_HYS” interpreted as an absolute value
“LIM_HYS” interpreted as a percentage value depends on the range of values
defined by the “HI_LIM” and “LO_LIM” parameters and is converted
accordingly.
The value of the hysteresis is mirrored to the “QLIM_HYS” output and
influences the deactivation of the triggered limit monitoring messages:
– Messages indicating that the value has exceeded a limit: these messages
are deactivated only after the limit minus the hysteresis has been reached.
– Messages indicating that the value has fallen below a limit: these
messages are deactivated only after the limit plus the hysteresis has been
reached.

Entry ID: 66839614, V1.0, 05/2016 40
4 Mode of Operation
4.8.5 Enabling/disabling the simulation
The “Simulation ON” mode enables the simulation of the analog signal. This
function is important, for example, if automatic functions shall be tested already
during the configuration phase, although a process interface does not yet exist.
Without simulating the feedbacks, many automatic functions (e. g. step sequences)
cannot be successfully executed since the feedbacks are frequently requested in
step enabling conditions or cause errors.
Figure 4-18
EN QdwState
LOCK QOUT
ERR_EXTERN QHI_LIM
LIOP_SEL QLO_LIM
L_RESET QLIM_ULA
BIPOLAR QLIM_ULW
IN QLIM_LLW
HI_LIM QLIM_LLA
LO_LIM QLIM_HYS
LIM_ULA QWARN_UL
LIM_ULW QALARM_LL
LIM_LLW_Enable QSIM
LIM_LLW QLOCK
LIM_LLA_Enable QERR
LIM_LLA QERR_EXT
RESTART QERR_WIRE
VISIBILITY QwAlarm
OPdwCmd ENO

Entry ID: 66839614, V1.0, 05/2016 41
4 Mode of Operation
 “IN_SIM”
When the simulation is enabled, the “IN_SIM” input is active, otherwise the
“IN_INT” or “IN” input is enabled, depending on the set mode (“IN_MODE”).
 “LIOP_SEL”
If the “LIOP_SEL” input is set, the simulation is switched on/off via the control
input “L_SIM”.
If the “LIOP_SEL” input is not set, the simulation is switched on/off by the
operator (“OPdwCmd [bits 20 and 21]”).
 “L_SIM”
“LIOP_SEL” = 1 AND “L_SIM” = 0  simulation OFF
“LIOP_SEL” = 1 AND “L_SIM” = 1  simulation ON
 “OPdwCmd”
The operator commands of the control word “OPdwCmd” are only effective, if
the “LIOP_SEL” input is not set.
3
“LIOP_SEL” = 0 AND “OPdwCmd [bit 20]” = 1  simulation OFF
4
“LIOP_SEL” = 0 AND “OPdwCmd [bit 21]” = 1  simulation ON
 “QSIM”
The “Simulation” mode is indicated at the “QSIM” block output.
“QSIM” = 0  simulation OFF
“QSIM” = 1  simulation ON
 “QdwState”
The current “Simulation” mode is indicated in the status word by means of
bit 18.
5
QdwState [bit 18] = 0  simulation OFF
3
QdwState [bit 18] = 1  simulation ON
3
Bit 20 = “PROCESS”
4
Bit 21 = “SIMULATION”
5
Bit 18 = “QSIM”

Entry ID: 66839614, V1.0, 05/2016 42
4 Mode of Operation
4.8.6 Resetting errors
The following situations cause the block to go to the “Error” state and the “QOUT”
output to take on the value of the “LO_LIM” lower limit:
 Interlock (“LOCK” = 1)
 External error (“ERR_EXT” = 1)
 Wire break (“QERR_WIRE” = 1)
The following situation causes the block to go to the “Error” state and the “QOUT”
output to take on the value of the “HI_LIM” upper limit:
 Overrun (“QERR_OVERRUN” = 1)
If there is an error at the block (QERR = 1), it can be reset using the “L_RESET”
input or by the “OPdwCmd” operator. This error status can only be reset, if there
are no other errors pending.
Figure 4-19
EN QdwState
LOCK QOUT
ERR_EXTERN QHI_LIM
LIOP_SEL QLO_LIM
L_RESET QLIM_ULA
BIPOLAR QLIM_ULW
IN QLIM_LLW
HI_LIM QLIM_LLA
LO_LIM QLIM_HYS
LIM_ULA QWARN_UL
LIM_ULW QALARM_LL
LIM_LLW_Enable QSIM
LIM_LLW QLOCK
LIM_LLA_Enable QERR
LIM_LLA QERR_EXT
RESTART QERR_WIRE
VISIBILITY QwAlarm
OPdwCmd ENO

Entry ID: 66839614, V1.0, 05/2016 43
4 Mode of Operation
 “L_RESET”
When setting the “LIOP_SEL” input parameter and a positive edge at the
“L_RESET” input, the “QERR” output is reset.
 “OPdwCmd”
Pressing the “DELETE” button in the “Analog_1_Overview” faceplate sets [Bit
6
24] in the “OPdwCmd” control word. The controller evaluates this bit and
resets the “QERR” output. The “LIOP_SEL” input parameter must not be set
when doing this.
6
Bit 24 = “RESET”

Entry ID: 66839614, V1.0, 05/2016 44
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 “Analog _001_Icon”
faceplate icon and the faceplates belonging to the “Analog” 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 45
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
“Hardware catalog”. 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 “Analogue” (FB640) function block from the “Master copies >
ANALOG” folder in the project tree to the “Program blocks” directory of

the controller.
 Optional: Drag the “Analogue_DB” instance data block from the “Master
copies > ANALOG” 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 “Analogue_DB” instance data block from the library. Select the
desired instance data block and click “OK”.

Entry ID: 66839614, V1.0, 05/2016 46
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 47
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 48
Step Procedure
3. Copying library elements
 Drag and drop the following library elements from the “Master copies > ANALOG” folder
of the global library into the corresponding folders in the project tree:
– “Analog_001_Tags”  “HMI tags”
– “Analog_001_Messages”  “HMI alarms”
– “Analog_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 49
Step Procedure
4. Integrating the messages
 Within the library, select the “Master copies > ANALOG” category.
 Drag and drop the “Analog_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 10049.
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 50
Step Procedure
5. Creating the HMI screen
 Drag and drop the “Analog_001_Icon” faceplate icon and the “Analog_001_Button” button
for calling the “Analog_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 51
Configuring by means of types

Table 5-4
Step Procedure
1. Opening the project and library
Open your project and the global library as described in Table 5-2.
2. Copying library elements
Drag and drop the “ANALOG” 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 52
Step Procedure
3. The “ANALOG” folder contains the faceplates of the screen window:
 “Analog_1_Overview”
 “Analog _2_Messages”
 “Analog _3_Graphs”
 “Analog _4_Limits”
 “Analog _5_Service”
Moreover, it contains the faceplate of the faceplate icon and the HMI UDT:
 “Analog_001_Icon”
 “Analog_UDT”
4. A complete configuration requires the following elements from the
“Master copies > ANALOG” folder:
 “Analog_001_Tags” (HMI tags)
 “Analog_001_Messages” (HMI alarms)
 “Analog_001_Button” (button)
Furthermore, you need the tags from the “MenuControl” tag table from the “Master copies >
MenuControl” folder:
 “Analog_Unit”
 “Visibility”
 Optional: “Close”
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 faceplate icon:

Entry ID: 66839614, V1.0, 05/2016 53
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”  “Analog_001_UDT”
– “Property > Visibility”  “Visibility”
– “Property > Unit”  “Analog_Unit”
7. Integrating the messages

 Within the library, select the “Master copies > ANALOG” category.
 Drag and drop the “Analog_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 10049.
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 54
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 55
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 56
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 57
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
Table 6-5
Figure Explanation
1 Close
The screen window can be closed via this button.
2 Tabs
The individual faceplate windows can be called via the tabs.

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

Overview
Figure 6-5
Features
 Simplified status display
 Opens the relevant faceplate by mouse-click
 Contains no language-dependent objects
Functionality
 Displayed operating states:
– Current analog value
– Limit violation (warning/alarm)
– Simulation feedback
– Interlock

Displayed errors:
– General error
 Operation:
– Activation of the screen window
Possible operating states:

Table 6-6
Mode QdwState Icon Flashing
Normal Bit 24 = 0 No
Error Bit 24 = 1 Yes
Possible status displays:

Table 6-7
State Icon
Interlock OFF
Interlock ON
Interlock triggered
Alarm limit OFF
Alarm limit ON
Warning limit OFF
Warning limit ON
Simulation OFF
Simulation ON

Entry ID: 66839614, V1.0, 05/2016 59
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 “Analog_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
 Select an analog value (only in simulation mode)
 Select limits (only in simulation mode)
 Reset error states

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

Table 6-8
Mode QdwState Icon Flashin
g
Normal Bit 8 = 0 and No
Bit 9 = 0
Warning Bit 8 = 1 No
(limit violated)
Alarm Bit 9 = 1 No
(limit violated)

Table 6-9
Display State State Flashing
Off Active
Simulation Yes
Overrun No
Upper Limit No
Lower Limit No
Wire break No
External error No
Interlock No
General error No

Entry ID: 66839614, V1.0, 05/2016 61
6.3 Screen window
6.3.3 Faceplate “Analog_2_Messages”
Click the “Messages” tab to call the faceplate.
Overview
Figure 6-7
Executable actions
 Display of alarms and messages
 Acknowledge alarms
 Filter for instance-related messages and alarms

Entry ID: 66839614, V1.0, 05/2016 62
6.3 Screen window
6.3.4 Faceplate “Analog_3_Graphs”
Click the “Graphs” tab to call the faceplate.
Overview
Figure 6-8
Executable actions
 Display limits (warning and alarm)
 Display the analog value

Entry ID: 66839614, V1.0, 05/2016 63
6.3 Screen window
6.3.5 Faceplate “Analog_4_Limits”
Click the “Limits” tab to call the faceplate.
Overview
Figure 6-9
Executable actions
 Enable / disable the limit messages
 Define the limits
 Define the hysteresis for deactivating the limit messages
Note  Write access to the values of this tab is possible only in simulation mode.
 The hysteresis can be entered either as an absolute value or as a percentage value.
For the respective settings, please go to the “Service” tab.

Entry ID: 66839614, V1.0, 05/2016 64
6.3 Screen window
6.3.6 Faceplate “Analog_5_Service”
Click the “Service” tab to call the faceplate.
Overview
Figure 6-10
Executable actions
 Toggle S7 periphery / real value
– An analog value is scaled depending on the limits in the “Overview” tab.
– The scaling of an analog value can be both unipolar and bipolar.
 Hysteresis changeover: percental/absolute
 Toggle simulation/real process mode.
Note The hysteresis only influences the deactivation of the limit messages.
It does not influence the scaling of the analog value or the triggering of a limit
message.

Table 6-10
Display Left button Right button
Process input
(real value)
Process input
(process value)
Hysteresis entry as an
absolute value
Hysteresis entry as a
percentage value

Entry ID: 66839614, V1.0, 05/2016 65
6.3 Screen window
Display Left button Right button

Simulation OFF
Simulation ON

Entry ID: 66839614, V1.0, 05/2016 66
7 Block Interfaces
7.1 Input parameters
7 Block Interfaces
7.1 Input parameters
Table 7-1
Parameters Data type Default setting Description
EN BOOL FALSE Release
LOCK BOOL FALSE 1= interlock pending
ERR_EXTERN BOOL FALSE 1= external error
LIOP_SEL BOOL FALSE 0= operator, 1= interconnection
L_SIM BOOL FALSE 0= process, 1 = simulation
L_RESET BOOL FALSE Reset errors (pos. edge)
IN_MODE BOOL FALSE 0= S7 periphery, 1= real value
BIPOLAR BOOL FALSE 1= scaling bipolar
IN_INT INT 0 I/O value
IN REAL 55.0 Real value
IN_SIM REAL 55.0 Simulation value (real value)
HI_LIM REAL 100.0 Upper scaling limit
LO_LIM REAL 0.0 Lower scaling limit

LIM_ULA_Enable BOOL FALSE 1= upper alarm limit active
LIM_ULA REAL 90.0 Upper alarm limit
LIM_ULW_Enable BOOL FALSE 1= upper warning limit active
LIM_ULW REAL 80.0 Upper warning limit
LIM_LLW_Enable BOOL FALSE 1= lower warning limit active
LIM_LLW REAL 20.0 Lower warning limit
LIM_LLA_Enable BOOL FALSE 1= lower alarm limit active
LIM_LLA REAL 10.0 Lower alarm limit
LIM_HYS_Set BOOL FALSE 0= percentage, 1= absolute
LIM_HYS REAL 0.0 Hysteresis (message limits)
INSTANCE STRING[16] Analog_001 Filter attribute for messages,
labeling of title bar
RESTART BOOL FALSE Initializing at restart
VISIBILITY BYTE 0 Representation of
screen window
OPdwCmd DWORD 0 Control tag (HMI)

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

Table 7-2
Parameters Data type Default setting Description
QdwState DWORD DW#16#0 Status tag (HMI)
QOUT REAL 0.0 Analog value
QHI_LIM REAL 100.0 Upper scaling limit
QLO_LIM REAL 0.0 Lower scaling limit
QLIM_ULA_Enable BOOL FALSE 1= upper alarm limit active
QLIM_ULA REAL 90.0 Upper alarm limit
QLIM_ULW_Enable BOOL FALSE 1= upper warning limit active
QLIM_ULW REAL 80.0 Upper warning limit
QLIM_LLW_Enable BOOL FALSE 1= lower warning limit active
QLIM_LLW REAL 20.0 Lower warning limit
QLIM_LLA_Enable BOOL FALSE 1= lower alarm limit active
QLIM_LLA REAL 10.0 Lower alarm limit
QLIM_HYS REAL 0.0 Hysteresis (message limits)
QALARM_UL BOOL FALSE 1= alarm for upper limit
pending
QWARN_UL BOOL FALSE 1= warning for upper limit
pending
QWARN_LL BOOL FALSE 1= warning for lower limit
pending
QALARM_LL BOOL FALSE 1= alarm for lower limit
pending
QSIM BOOL FALSE 0= process, 1 = simulation
QLOCK BOOL FALSE 1= interlock error
QERR BOOL FALSE 1= error
QERR_EXT BOOL FALSE 1= external error
QERR_OVERRUN BOOL FALSE 1= overrun error
QERR_HIGHRANGE BOOL FALSE 1= high range error
QERR_LOWRANGE BOOL FALSE 1= low range error
QERR_WIRE BOOL FALSE 1= wire break (underrun)
QwAlarm WORD W#16#0 Alarm tag
ENO BOOL FALSE Release

Entry ID: 66839614, V1.0, 05/2016 68
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/en/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 69
9 Links & Literature
9 Links & Literature

Bibliographic references
This list only represents a selection of relevant information.
Table 9-1
Topic Title
\1\ Download page of the entry https://support.industry.siemens.com/cs/ww/en/vie
w/66839614
\2\ Siemens Industry Online https://support.industry.siemens.com
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/vie
ET 200MP, ET 200SP, w/67989094
ET 200AL, ET 200pro,
ET 200eco PN Analog value
processing
\7\ Faceplates for the https://support.industry.siemens.com/cs/ww/en/vie
Visualization of SENTRON w/67318600
PAC Power Meters for
WinCC Runtime Professional
\8\ SITOP UPS1600: https://support.industry.siemens.com/cs/ww/en/vie
Faceplates and STEP 7 w/78817848
communication blocks
\9\ Measuring and Visualizing https://support.industry.siemens.com/cs/ww/en/vie
Energy Data w/86299299
\10\ Configuration instruction for https://support.industry.siemens.com/cs/ww/en/vie
creating faceplates for w/68014632
Comfort Panels and
WinCC Runtime Advanced

Entry ID: 66839614, V1.0, 05/2016 70
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 71

WCA Faceplate Analog 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 Analog 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

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

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

7 Block Interfaces ............................................................................................... 67

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

with the faceplates of WinCC Professional: The connection to the controller

Topics not covered by this application

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

Description of the automation task

The blocks offer the following functions:

The following (associated) values of the signal to be monitored are displayed:

NOTICE It might be necessary to make some adjustments.

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

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

2.1 Overview of the overall solution

The screen window consists of a pop-up screen

ANALOG (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:

also be simulated with PLCSIM.

Standard software components

Example files and projects

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

3.1 Library objects

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

Types and instances

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

4.1 Faceplate icon

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

 The “QdwState” tag of the controller is connected at the “State” property of

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

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

4.2 Interfaces of the faceplate icon

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

The following table shows the setup of the “QdwState” tag.

Table 4-4 Setup of the “QdwState” tag

Data type Real

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

4.3 Screen window

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

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

4.4 Components of the screen window

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

The following options are available:

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

4.4.1 Faceplate “Analog_1_Overview”

The “Analog_1_Overview” faceplate is used for displaying current process values

4.4.2 Faceplate “Analog_2_Messages”

The “Analog_2_Messages” faceplate is used for displaying messages.

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

The message view is divided into six columns:

4.4.3 Faceplate “Analog_3_Graphs”

The “Analog_3_Graphs” faceplate is used for displaying graphs. It contains a graph

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

4.4.4 Faceplate “Analog_4_Limits”

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

4.4.5 Faceplate “Analog_5_Service”

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