WCA Faceplate SimoDir en

Application Example  09/2016
TIA Portal Example Block

“SIMODIR”
WinCC Comfort/Advanced V13 SP1, STEP 7 V13 SP1, S7-1200/S7-1500
https://support.industry.siemens.com/cs/ww/en/view/66839614
Warranty and Liability
Warranty and Liability

Note The Application Examples are not binding and do not claim to be complete with regard to
configuration, equipment or any contingencies. The Application Examples do not
represent customer-specific solutions. They are only intended to provide support for
typical applications. You are responsible for the correct operation of the described
products. These Application Examples do not relieve you of the responsibility of safely
and professionally using, installing, operating and servicing equipment. 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 and without prior notice. If there are
any deviations between the recommendations provided in this application example and
other Siemens publications – e. g. catalogs – the contents of the other documents shall
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
deficiency or breach of fundamental contractual obligations (“wesentliche
Vertragspflichten”). The compensation for damages due to a breach of a
fundamental contractual obligation is, however, limited to the foreseeable damage,
typical for the type of contract, except in the event of intent or gross negligence or
 Siemens AG 2016 All rights reserved
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 Siemens AG.
Security Siemens provides products and solutions with Industrial Security functions that support
informa- the secure operation of plants, systems, machines and networks.
tion In order to secure plants, systems, machines and networks against cyber threats, it is
necessary to implement (and to maintain continuously) a holistic, state-of-the-art Industrial
Security concept. With this in mind, Siemens’ products and solutions are only part of such
a concept.
It is the client’s responsibility to prevent unauthorized access to his plants, systems,
machines and networks. Systems, machines and components should only be connected
with the company’s network or the Internet, when and insofar as this is required and the
appropriate protective measures (for example, use of firewalls and network segmentation)
have been taken.
In addition, Siemens’ recommendations regarding appropriate protective action should be
followed. For more information on Industrial Security, visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them even
more secure. Siemens explicitly recommends to carry out updates as soon as the
respective updates are available and always to use only the current 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.
In order to always be informed about product updates, subscribe to the Siemens Industrial
Security RSS Feed at http://www.siemens.com/industrialsecurity.
SIMODIR (WinCC Advanced V13 SP1, STEP 7 V13 SP1)

Entry ID: 66839614, V1.0, 09/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 ........................................................... 7
2.2 Hardware and software components ................................................... 8
2.2.1 Validity .................................................................................................. 8
2.2.2 Topics not covered by this application ................................................. 8
2.2.3 Components used ................................................................................ 9
3 Basics ............................................................................................................... 10
3.1 Library objects .................................................................................... 10
3.2 Faceplates .......................................................................................... 10
4 Mode of Operation ........................................................................................... 12
4.1 Faceplate icon .................................................................................... 12
4.2 Interfaces of the faceplate icon .......................................................... 15
4.3 Screen window ................................................................................... 16
4.4 Components of the screen window .................................................... 19
4.4.1 Faceplate “SimoDir_1_Overview” ...................................................... 21
4.4.2 Faceplate “SimoDir_2_Messages” ..................................................... 21
4.4.3 Faceplate “SimoDir_3_Graphs” ......................................................... 22
4.4.4 Faceplate “SimoDir_4_Diagnosis” ..................................................... 23

4.4.5 Faceplate “SimoDir_5_Statistics” ....................................................... 24
4.4.6 Faceplate “SimoDir_6_Service” ......................................................... 25
4.5 Interfaces of the screen window ......................................................... 26
4.6 Tags of the UDT ................................................................................. 27
4.6.1 Tags with function tasks ..................................................................... 28
4.6.2 Scaling the trend view ........................................................................ 31
4.6.3 Process values ................................................................................... 32
4.6.4 Diagnosis ............................................................................................ 32
4.6.5 Statistics ............................................................................................. 34
4.7 Alarms and messages ........................................................................ 40
4.8 Control and status signals .................................................................. 41
4.8.1 Processing of switching commands in the controller ......................... 42
4.8.2 Transmitting switching commands to the motor management
system ................................................................................................ 43
4.8.3 Evaluating and displaying process states in WinCC Advanced ......... 45
4.8.4 Manual/automatic mode ..................................................................... 46
4.8.5 Toggling between local and remote operating mode ......................... 48
4.8.6 Toggling between general operating mode Start/Stop ....................... 50
4.8.7 Simulation ON/OFF ............................................................................ 53
4.8.8 Displaying and resetting the interlock ................................................ 55
5 Commissioning the Application Example ..................................................... 57
5.1 Configuring the STEP 7 block ............................................................ 57
5.2 Configuring the WinCC Advanced faceplates .................................... 59
5.2.1 Opening the global library .................................................................. 59
5.2.2 Integrating the library elements into the project ................................. 60
5.3 Setting up the IP address ................................................................... 70
6 Operating the Application Example ............................................................... 71
6.1 Navigation .......................................................................................... 72
6.2 Faceplate icon .................................................................................... 75
6.3 Screen window ................................................................................... 76

Entry ID: 66839614, V1.0, 09/2016 3
Table of Contents
6.3.1 Menu system und “Close” button ....................................................... 76

6.3.2 Faceplate “SimoDir_1_Overview” ...................................................... 77
6.3.3 Faceplate “SimoDir_2_Messages” ..................................................... 79
6.3.4 Faceplate “SimoDir_3_Graphs” ......................................................... 80
6.3.5 Faceplate “SimoDir_4_Diagnosis” ..................................................... 81
6.3.6 Faceplate “SimoDir_5_Statistics” ....................................................... 82
6.3.7 Faceplate “SimoDir_6_Service” ......................................................... 84
7 Block Interfaces ............................................................................................... 85
7.1 Input parameters ................................................................................ 85
7.2 Input/output parameters ..................................................................... 85
7.3 Output parameters ............................................................................. 86
8 Additional Information .................................................................................... 89
9 Links & Literature ............................................................................................ 90
10 History............................................................................................................... 91

Entry ID: 66839614, V1.0, 09/2016 4
1 Task
1 Task
Introduction
1
The example blocks for SIMATIC STEP 7 (TIA Portal) and SIMATIC WinCC
2
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 to call and interconnect the example blocks
in STEP 7 and WinCC Advanced.
The advantages of using faceplates in WinCC shall also 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
– Storing the screen objects for WinCC Advanced in a global library enables
using them further in another project without any problems.
 Reducing the configuration effort
– Frequently used automation components can be integrated quickly into a
configuration.
– The faceplates for WinCC Advanced are interface-compatible with the
WinCC Professional faceplates: 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 example, 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 abbreviated as “STEP 7”.
2
In the following abbreviated as “WinCC Advanced”.

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

This application example describes the configuration of the “SIMODIR” example
technology block (FB 611) as well as the configuration and operation of the
associated faceplates.
These faceplates are used for the visualization and operation of motors with fixed
speed and rotational direction when using the motor management system
SIMOCODE pro.
The faceplates have the following functions:

 Start/Stop
 Manual/automatic mode
 Local/remote operating mode
 Simulation of operating states
 Display of interlock conditions via “LOCK”
The following operating modes of the motor are displayed:

 Stop
 Run
 Invalid status
The following errors are evaluated, displayed in the screen window and saved in
the Alarm Logging:
 Feedback ON/OFF
 Interlock error active
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, 09/2016 6
2 Solution
2.1 Overview of the overall solution
2 Solution
The application example describes the configuration of example technology block
“SimoDir” (FB 611) for the controller family S7-1200/S7-1500 and the respective
screen objects for WinCC Advanced.
These faceplates are used for the visualization and operation of motors with fixed
speed and rotational direction when using the motor management system
SIMOCODE pro.
Note  A copy of the control blocks of the application example is already contained
in the example project.
 The latest version of the control blocks of the application example is
available in the separate project library
“66839614_STEP7_Example_Blocks_V13_SP1.zip” on the website of this
application example.
Unlike the control blocks in the example project, the control blocks in the
library are always up-to-date.
2.1 Overview of the overall solution

Schematic layout
The following figures show the screen window, the faceplate icon as well as the
input and outputs of the control block “SimoDir” (FB 611).
Table 2-1
Screen window Faceplate icon
The faceplate icon consists of

a faceplate. It shows the most
important status values of the
The screen window consists of a pop-up screen which example block “SimoDir” (FB
contains a menu system and various faceplates. 611) in minimized format.

Entry ID: 66839614, V1.0, 09/2016 7
2 Solution
2.2 Hardware and software components
Table 2-2
Control block “SimoDir” (FB 611)
… …
…

2.2.1 Validity
This application example is valid for:

 STEP 7 V13 SP1 update 8 (and higher)
 WinCC Advanced V13 SP1 update 8 (and higher)
 S7-1200 and S7-1500
 SIMOCODE pro
2.2.2 Topics not covered by this application
The faceplates presented in this document are not compatible with WinCC
Professional. For WinCC Professional, a separate library and documentation are
available for download on the website of the application example. Both versions
use the same interfaces.

Entry ID: 66839614, V1.0, 09/2016 8
2 Solution
2.2.3 Components used
The application example has been created with the following components:
Hardware components
Table 2-3
Component Qty. Order number Note
SIMATIC S7-1200 1 6ES7214-1AG31- Alternatively: Another S7-1200
CPU 1214C 0XB0 CPU. The controller can also be
DC/DC/DC simulated with PLCSIM (as of TIA
V13 SP1).
SIMATIC S7-1500 1 6ES7516-3AN00- Alternatively: Another S7-1500
CPU 1516-3PN/DP 0AB0 CPU. The controller can also be
simulated with PLCSIM.
Motor management 1 3UF7011-1A.00-0 The block has been created
system especially for using the motor
SIMOCODE pro V PN management system
(firmware V1.2 SIMOCODE pro.
product version E05)
Operator panel for 1 Alternatively: A SIMATIC Comfort
WinCC RT Advanced Panel (FW V13 SP1)
(V13 SP1)
Standard software components
Table 2-4
Component Qty. Order number
STEP 7 Professional V13 SP1 update 8 1 6ES7822-1AE03-0YA5
WinCC Runtime Advanced V13 SP1 update 8 1 6AV2104-0KA03-0AH0
WinCC Advanced V13 SP1 update 8 1 6AV2102-0AA03-0AH5
Example files and projects

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

Entry ID: 66839614, V1.0, 09/2016 9
3 Basics
3.1 Library objects
3 Basics
Introduction
For a better understanding of this application example, you should know the
following procedures:
 Managing library objects,
 Using faceplates
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, i. e. 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, use the master copies.
If a master copy is edited in the library, these changes do not affect the copies
in the project. Moreover, the individual copies and their changes in the project
are independent of each other, because they are not related to each other.
Notes  “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 management functions
for managing several versions of a type and a specific release of these
versions 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 except for
faceplates.
 You can copy the library objects between a global library and a project
library. The following applies:
– 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 to a screen, this
object will also be stored in the project library.
3.2 Faceplates
Faceplates are a configured group of display and control objects which you can
manage and modify centrally in a library.

Entry ID: 66839614, V1.0, 09/2016 10
3 Basics
3.2 Faceplates
Usage
 Faceplates are used for creating 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 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.
Notes  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.
Further information on faceplates is available in the application example “Creating

faceplates with WinCC Runtime Advanced and Comfort Panels” (entry ID:
68014632).

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

The faceplate icon consists of the faceplate “SimoDir_Icon”.
The corresponding screen window is called via an invisible button above the
faceplate.
Figure 4-1
Note The screen shows the faceplate in the configuration environment. The runtime
(RT) display is described in the chapter “Operating the Application Example”.
Properties
The faceplate icon has the following properties:
 It shows a simplified status display.
 It contains no language-dependent objects.
 It has a defined interface.
Parameters
Table 4-1
No. Path Tag
1. Properties > Miscellaneous > Name SimoDir_001_Icon
2. Interface > Process > Value SimoDir_001_UDT

Entry ID: 66839614, V1.0, 09/2016 12
4 Mode of Operation
4.1 Faceplate icon
Explanation of the parameters

Table 4-2
No. Explanation
1. The name “SimoDir_001_Icon” has been selected randomly.
However, it is important that it is only assigned once in a screen.
2. The screen shows the page of the interface of the faceplate icon which is inside
the faceplate “SimoDir_Icon” and which can be edited in the faceplate editor.
As the screen shows, the interface of the faceplate icon has the property
“QdwState” for displaying the switch status and the property “QfCurrentP” for
displaying the current value taken by the motor (actual value) in relation to the
nominal motor current.
3. The screen shows the faceplate icon interface which is connected outside the
faceplate editor in the properties of the faceplate “SimoDir_Icon”.
The “SimoDir_001_UDT” UDT tag of the controller is connected to the “Value”

property of the faceplate instance. This is required for displaying the status
signals and values.

Entry ID: 66839614, V1.0, 09/2016 13
4 Mode of Operation
4.1 Faceplate icon
No. Explanation
4. The tags connected to the properties in “Animations > Tag connections” are
references to the respective properties of the interface.
The tags can be connected and modified both inside and outside the block
editor. The entries influence each other.
5. To display the screen window by clicking on the faceplate icon, the event
“DisplayPopupScreen” needs to be configured for the button
“SimoDir_001_Button” under “Events > Release” for the pop-up screen
“SimoDir_001_Pop-up”.
Set the “Visibility” tag to “1” to display the “SimoDir_1_Overview” faceplate as an
active screen after opening the screen window.

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

Via the configuration of the interface, you can define which properties and process
values of the objects included in the faceplate can be configured.
A dynamic property is connected to a tag via the interface. The tag supplies the
dynamic property with values during runtime.
Figure 4-2
Tag group “Process”

The tags of this group have a process connection and constitute the basic interface
between controller and operating panel.
Value
The tag “SimoDir_001_UDT” is used for displaying the different states and values
in the WinCC Advanced process image.
Table 4-3
Tag used
Name SimoDir_001_UDT
Data type SimoDir_UDT
Address %DB611.DBX0.0
Length 328 bytes
Acquisition cycle 100 ms
Acquisition mode Cyclic in operation
Information on the structure of the UDT “SimoDir_001_UDT” are available in the

chapters 4.5 “Interfaces of the screen window” and 4.6 “Tags of the UDT”.

Entry ID: 66839614, V1.0, 09/2016 15
4 Mode of Operation
4.3 Screen window
4.3 Screen window

The screen window consists of a pop-up screen which contains a menu system
and various faceplates.
Notes  For better understanding, the screen window is initially described in the
configuration environment.
 The following screens for describing the components refer to the display
during runtime (RT), unless stated otherwise.
Figure 4-3
Properties
 The screen window includes the following functions in the faceplates:
– Overview with status display and control elements
– Display of status and diagnostic data
– Display and input of statistical data
– Display of the instance name
– Message display with the option to filter for the instance name
– Trend view
– Activation of the simulation mode
 The screen window contains language-dependent objects: German (Germany),
English (USA).
 The screen window cannot be moved.

Entry ID: 66839614, V1.0, 09/2016 16
4 Mode of Operation
4.3 Screen window
Events
The buttons of the menu system (tabs) of the screen window are linked to the
following events. They are executed when the screen is called.
Figure 4-4
1
4* 5*
Table 4-4 Event-triggered functions of the tabs

No. Function, tag Usage
1. SetTag X1Pos Position of the toolbar at the tab
2. SetTag Visibility Indicator for selecting a tab
3. SetTag The tag value is a condition for the
SimoDir_DB_OP_VISIBILITY simple/continuous read command
 for diagnostic data
(SimoDir_DB_OP_VISIBILITY = 4)
 for statistical data
(SimoDir_DB_OP_VISIBILITY = 5)
4. SetTag SimoDir_DB_SE_TAB_DIAG_REQ = 1:
SimoDir_DB_SE_TAB_DIAG_REQ Simple read command for diagnostic data,
*(only for the “Diagnosis” tab), if SimoDir_DB_OP_VISIBILITY = 4
(see 3.)
5. SetTag SimoDir_DB_SE_TAB_STAT_REQ = 1:
SimoDir_DB_SE_TAB_STAT_REQ Simple read command for statistical data,
*(only for the “Statistics” tab), if SimoDir_DB_OP_VISIBILITY = 5
(see 3.)

Entry ID: 66839614, V1.0, 09/2016 17
4 Mode of Operation
4.3 Screen window
Explanation
Table 4-5
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}
2. The identifier of the currently activated tab is stored in the INT tag “Visibility”:
Visibility = {1, 2, 3, 4, 5, 6}
“Visibility” affects the visibility of the elements in the faceplates via the interface
of the respective faceplate.
3. The identifier of the currently activated tab is stored in the INT tag
“SimoDir_DB_OP_VISIBILITY”:
SimoDir_DB_OP_VISIBILITY = {1, 2, 3, 4, 5, 6}
 “Diagnosis” tab  SimoDir_DB_OP_VISIBILITY = 4  simple/continuous
read command for diagnostic data
Whether the read command is set to be continuous or simple depends on
the network selected in the FB611 “SimoDir” in the STEP 7 configuration.
– Network 11a – simple read command (condition 1 of 2)
– Network 11b – continuous read command
(For further information, refer to the note in chapter 4.6.4 Diagnosis)
 “Statistics” tab  SimoDir_DB_OP_VISIBILITY = 5  simple/continuous
read command for statistical data
Whether the read command is set to be continuous or simple depends on

the network selected in the FB611 “SimoDir” in the STEP 7 configuration.
– Network 14a – simple read command (condition 1 of 2)
– Network 14b – continuous read command
(For further information, refer to the note in chapter 4.6.5 Statistics.)
 Other tabs  SimoDir_DB_OP_VISIBILITY = {1,2,3,6}  deactivation of the
active continuous read command
4. Setting the BOOL tag “SimoDir_DB_SE_TAB_DIAG_REQ” fulfils the second
condition for sending a simple read command for diagnostic data, if network 11a
(simple read command) is active in the FB611 “SimoDir” in the STEP 7
configuration.
 Network 11a – simple read command (condition 2 of 2)
5. Setting the BOOL tag “SimoDir_DB_SE_TAB_STAT_REQ” fulfils the second
condition for sending a simple read command for statistical data, if network 14a
(simple read command) is active in the FB611 “SimoDir” in the STEP 7
configuration.
 Network 11a – simple read command (condition 2 of 2)

Entry ID: 66839614, V1.0, 09/2016 18
4 Mode of Operation
4.4 Components of the screen window
No. Explanation
6. Click “X” to close the screen window. The screen shows the system functions
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 via which various faceplates can be
called.
Figure 4-5

Entry ID: 66839614, V1.0, 09/2016 19
4 Mode of Operation
The following options are available:
Table 4-6
No. Tab Faceplate Function
1. Overview SimoDir_1_Overview Overview of the current switch status, set limit
values as well as status and error displays
2. Messages SimoDir_2_Messages Display of messages (warnings and errors)
3. Graphs SimoDir_3_Graphs Graph display for graphic visualization of actual
value and nominal value of the current
4. Diagnosis SimoDir_4_Diagnosis Display of status messages
5. Statistics SimoDir_5_Statistics Display and writing of statistical values
6. Service SimoDir_6_Service Settings for process input, delay time and
simulation mode
The “Visibility” property is used for influencing the display properties of the screen
window during runtime.
The value of the “Visibility” tag influences the selection of the individual tabs. It
corresponds to the number of the faceplate.
The process connection is optional.
Notes The “Visibility” tag is pre-assigned with the value “1” when clicking on the hidden
button “SimoDir_001_Button” with the mouse. This results in the respective
screen window being displayed with tab 1.
Table 4-7
Tag used
Name Visibility
Data type Integer
Address Internal tag
Note The “Visibility” tag can also be defined as PLC tag with controller connection.
If the tag has a controller connection, the controller can access it for reading and
writing. 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, 09/2016 20
4 Mode of Operation
4.4.1 Faceplate “SimoDir_1_Overview”
The “SimoDir_1_Overview” faceplate is used for displaying current process values

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

and errors are displayed.
Figure 4-7

Entry ID: 66839614, V1.0, 09/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)
As default setting, the messages of the message view are filtered for the type
(“SimoDir”).
By setting the filter, the displayed messages can be filtered for messages of the
instance belonging to the screen window.
The content of the instance tag is stored in the corresponding instance data block.
The content of the instance tag is displayed next to the filter.
4.4.3 Faceplate “SimoDir_3_Graphs”
The “SimoDir_3_Graphs” faceplate is used for displaying graphs.

It contains a graph view for graphic visualization of the tags
 Nominal motor current in A (“Nominal Value [A]”)
 Actual value of the nominal motor current in A (“Value [A]”)
Figure 4-8

Entry ID: 66839614, V1.0, 09/2016 22
4 Mode of Operation
4.4.4 Faceplate “SimoDir_4_Diagnosis”
The “SimoDir_4_Diagnosis” faceplate is used for displaying status and diagnostic

messages.
Figure 4-9
Note There is only a read access to the values of this faceplate.

While the “Diagnosis” tab is open, the displayed diagnostic values are
permanently updated via acyclic services. This leads to an increased network
load.
Alternative programming can be found in the comment field of network 11
(“Update data record 92 device diagnosis”). The alternative code updates the
diagnostic values only once when selecting the “Diagnosis” tab.

Entry ID: 66839614, V1.0, 09/2016 23
4 Mode of Operation
4.4.5 Faceplate “SimoDir_5_Statistics”
The “SimoDir_5_Statistics” faceplate is used for displaying and setting statistical

values of the motor management system.
Figure 4-10
Note There are two options to control the write access to the values. You can combine
both protective mechanisms.
 A SIMOCODE password protects the device against access throughout the

system. The password is transmitted via data record 224 (see below).
 The password protection on the HMI side via the user management protects
against access via the operator panel.
You can, for example, provide the “Enable Input” button with an HMI-side
access protection to control the write access of the users to the values.
Please note that writing is only possible, if the SIMOCODE password
protection has not been enabled or if the SIMOCODE password has been
transmitted successfully.
For more information: See system manual of the device under “Data formats and
data records > Data record 224 – Password protection” (entry ID: 61896631).

Entry ID: 66839614, V1.0, 09/2016 24
4 Mode of Operation
4.4.6 Faceplate “SimoDir_6_Service”
The faceplate “SimoDir_6_Service” is used for setting the simulation mode and for
displaying the corresponding instance name.
Figure 4-11

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

The tags used in this application example are almost exclusively elements of so-
called user-defined data types (UDT).
For connecting the HMI tag “SimoDir_001_UDT” to the faceplates, the user-
defined HMI data structure “SimoDir_UDT” (2) has already been stored in the
library as a type. As already described in chapter “3.1 Library objects”, with tags of
the UDT type you only create instances of this structure.
In the example project of this application example, an instance of the HMI UDT has
already been created for each faceplate. For the SimoDir faceplates, the instance
name is “SimoDir_001_UDT” (1), following the instance name in the “FB611”,
which is preassigned with “SimoDir_001” in the application example.
Figure 4-12
1 2

Entry ID: 66839614, V1.0, 09/2016 26
4 Mode of Operation
4.6 Tags of the UDT
When creating a new tag, e. g. “SimoDir_002_UDT” of the “SimoDir_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. “SimoDir_001_UDT”).
 In the project, the tag prefix must precede each location of usage of the
structure elements, e. g. “SimoDir_001_UDT.QdwState”.
4.6 Tags of the UDT

The individual structure tags can principally be divided into two categories:
 Tags with function tasks
– OpdwCmd – HMI control commands

– QdwState – status
– INSTANCE – instance name
 General tags for scaling, process values, diagnostics and statistics
– OP_TrendScale – max. value of the trend view scale
– QfCurrentA – current in amperes

– QfCurrentP – current in percent
– DPV1DEV_Qdw00 – diagnosis control functions

– DPV1DEV_Qdw04 – diagnosis protective functions
– IntMotOperHours – internal motor operating hours (read only)

– MotOperHours – motor operating hours
– IntOverlTrips – internal number of overload trips (read only)
– OverlTrips – number of overload trips
– IntNumbStarts_R – number of starts, right (read only)
– NumbStarts – number of starts
– IntNumbStarts_L – number of starts, left (read only)
– MotStopTime – stop time
– PermStarts – number of still permissible starts
– ConsumedEnergy – energy consumption

Entry ID: 66839614, V1.0, 09/2016 27
4 Mode of Operation
4.6 Tags of the UDT
– DeviceParameter – number of parameterizations

– DeviceOperHours – operating hours (read only)
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.
OpdwCmd – HMI control commands

The structure tag “OPdwCmd” is used for transmitting 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 “OPdwCmd” is set
to “0”.
Table 4-8
Tag used
Symbolic name SimoDir_001_UDT.OPdwCmd
Data type DWord
Address %DB611.DBD376
Length 4 bytes
The following table shows the setup of the “OPdwCmd” tag.
Table 4-9 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
STAT_REQ_WR
SIMULATION
STAT_REQ
DAIG_REQ
PROCESS
REMOTE
MANUAL
RESET
LOCAL
START
Signal
AUTO
STOP

Entry ID: 66839614, V1.0, 09/2016 28
4 Mode of Operation
4.6 Tags of the UDT
QdwState – status
The structure tag “QdwState” is used for displaying the different states of the
frequency converter (e. g. operating modes, interlock, simulation mode) in the
WinCC Advanced process screen.
Table 4-10
Tag used
Name SimoDir_001_UDT.QdwState
Data type DWord
Length 4 bytes
The following table shows the setup of the “QdwState” tag.
Table 4-11 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
DPV1STAT_WR_QbBUSY
DPV1DEV_QbBUSY
QGENWARN
QMAN_AUT
QERR_EXT
QREMOTE
QGENFAIL
QPREO
QSTOP
QLOCK
QLOCT
Signal
QRUN
QERR
LOCK
QSIM

Entry ID: 66839614, V1.0, 09/2016 29
4 Mode of Operation
4.6 Tags of the UDT
INSTANCE – instance name

The structure tag “INSTANCE” is a text string with a field length of up to 254
characters and has two usage locations:
 The structure tag serves as filter criterion for the alarm display of the faceplate
window. This ensures that only alarms that relate to this faceplate window are
displayed.
 The structure tag is displayed in the “SimoDir_6_Service” faceplate to
distinguish between the individual faceplate instances.
Table 4-12
Tag used
Name SimoDir_001_UDT.INSTANCE
Data type String
Address %DB611.DBX8.0
Length 254 bytes
Figure 4-13
Note The structure tag contents have to be adjusted for each instance of a faceplate.
The structure tag contents are specified as a start value in the declaration section
of the respective function block (FB). Make sure that the alarms in the discrete
alarms editor of WinCC Advanced contain the same text string in addition to the
actual alarm text.

Entry ID: 66839614, V1.0, 09/2016 30
4 Mode of Operation
4.6 Tags of the UDT
Figure 4-14
4.6.2 Scaling the trend view

The tags of this group are used for controlling the display properties of the trend
view.
OP_TrendScale – max. value of the trend view scale

The structure tag “OP_TrendScale” is used for scaling the maximum value of the
scale to the 1.25-fold of the nominal motor current.
Table 4-13
Tag used
Symbolic name SimoDir_001_UDT.OP_TrendScale
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 09/2016 31
4 Mode of Operation
4.6 Tags of the UDT
4.6.3 Process values
The tags of this group have a process interface and are used for monitoring the
current consumption of the motor connected to the SIMOCODE pro.
QfCurrentA – current in amperes

The structure tag “QfCurrent” displays the current consumption (actual value) of the
motor in amperes [A].
Table 4-14
Tag used
Symbolic name SimoDir_001_UDT.QfCurrentA
Data type Real
Length 4 bytes
Acquisition mode Cyclic continuous
QfCurrentP – current in percent

The structure tag “PfCurrentP” displays the current consumption (actual value) in
relation to the nominal motor current in percent [%].
Table 4-15
Tag used
Symbolic name SimoDir_001_UDT.QfCurrentP
Data type Real
Length 4 bytes
4.6.4 Diagnosis
The tags in this group have a process connection and can be monitored in the
“Diagnosis” tab.
They are updated acyclically as long as the “Diagnosis” tab is open (permanently)
or if the “Diagnosis” tab is activated (once). They display the state of the
SIMOCODE pro and of the connected motor.
The following table lists an excerpt of the diagnostic parameters used in the
faceplate. A complete list of readable diagnostic parameters is available in the
system manual of the device in the section “Data formats and data records > Data
record 92 – Device diagnostics” (entry ID: 61896631).

Entry ID: 66839614, V1.0, 09/2016 32
4 Mode of Operation
4.6 Tags of the UDT
Table 4-16 Diagnostic parameters in the “SimoDir_4_Diagnosis” faceplate

Interface tag Bit no. in the Byte.bit Meaning
in the faceplate faceplate Data record
92
Value.DPV1DEV_Qdw00 7 3.7 Operational protection
OFF
Value.DPV1DEV_Qdw00 9 2.1 ON <
Value.DPV1DEV_Qdw00 10 2.2 OFF
Value.DPV1DEV_Qdw00 11 2.3 ON >
Value.DPV1DEV_Qdw00 13 2.5 Start active
Value.DPV1DEV_Qdw00 14 2.6 Interlock time active
Value.DPV1DEV_Qdw00 16 1.0 General fault
Value.DPV1DEV_Qdw00 17 1.1 General warning
Value.DPV1DEV_Qdw00 18 1.2 Device OK
Value.DPV1DEV_Qdw00 19 1.3 Bus OK
Value.DPV1DEV_Qdw00 20 1.4 PLC/PCS in RUN
Value.DPV1DEV_Qdw00 21 1.5 Motor current flowing
Value.DPV1DEV_Qdw04 25 4.1 Emergency start
executed
Value.DPV1DEV_Qdw04 26 4.2 Cooling-down period
active
Value.DPV1DEV_Qdw04 27 4.3 Pause time active
Value.DPV1DEV_Qdw04 28 4.4 Device check active
Value.DPV1DEV_Qdw04 29 4.5 Phase sequence 1-2-3
Value.DPV1DEV_Qdw04 30 4.6 Phase sequence 3-2-1
DPV1DEV_Qdw00 – diagnosis control functions

The structure tag “Diagnosis_DW0” includes status messages concerning control
functions of the motor management system.
Table 4-17
Tag used
Symbolic name SimoDir_001_UDT.DPV1DEV_Qdw00
Data type DWord
Length 4 bytes

Entry ID: 66839614, V1.0, 09/2016 33
4 Mode of Operation
4.6 Tags of the UDT
DPV1DEV_Qdw04 – diagnosis protective functions

The structure tag “Diagnosis_DW4” includes status messages concerning
protective functions of the motor management system.
Table 4-18
Tag used
Symbolic name SimoDir_001_UDT.DPV1DEV_Qdw04
Data type DWord
Length 4 bytes
Note While the “Diagnosis” tab is open, the displayed diagnostic values are
permanently updated via acyclic services. This leads to an increased network
load.
(“Update data record 92 device diagnosis”).
The alternative code updates the diagnostic values only once when selecting the
“Diagnosis” tab.
4.6.5 Statistics
The tags in this group have a process connection and can be monitored in the
“Statistics” tab.
 They are read acyclically as long as one of the following conditions is fulfilled:
– The “Statistics” tab is permanently open.
– The “Statistics” tab is activated once.
– The “Read” button is clicked once.
 Activating the “Enable Input” button prevents the display from being updated
until this same button (“Disable Input”) is deactivated by clicking it again.
They display the operating values of the SIMOCODE pro and of the connected
motor.
After the input fields have been enabled by clicking the “Enable Input” button, some
of the tags can be sent to the SIMOCODE pro motor management system by
clicking the “Write” button.
The following table lists an excerpt of the statistical data used in the faceplate. A
complete list of readable statistical data is available in the system manual of the
device in the section “Data formats and data records > Data record 95 – Service
data/statistical data” (entry ID: 61896631).
Table 4-19 Statistical data in the “SimoDir_5_Statistics” faceplate
Interface tag Data Byte.bit Meaning
in the faceplate type Data
record
95
Value.DPV1STAT_PermSt Byte 4.0 Permissible starts (actual value)
arts

Entry ID: 66839614, V1.0, 09/2016 34
4 Mode of Operation
4.6 Tags of the UDT
Interface tag Data Byte.bit Meaning

in the faceplate type Data
record
95
Value.DPV1STAT_Device Word 8.0 Number of parameterizations
Parameter
Value.DPV1STAT_OverlTri Word 10.0 Number of overload trips
ps
Value.DPV1STAT_IntOverl Word 12.0 Internal number of overload trips
Trips
Value.DPV1STAT_MotSto Word 14.0 Stop time
pTime
Value.DPV1STAT_MotOpe Real 40.0 Operating hours (motor)
rHours
Value.DPV1STAT_IntMotO Real 44.0 Internal operating hours (motor)
perHours
Value.DPV1STAT_Device Real 48.0 Operating hours (device)
OperHours
Value.DPV1STAT_NumbS DWord 52.0 Number of starts
tarts
Value.DPV1STAT_IntNum DWord 56.0 Number of internal starts (right)
bStarts_R
Value.DPV1STAT_IntNum DWord 60.0 Number of internal starts (left)

bStarts_L
Value.DPV1STAT_Consu Real 64.0 Energy consumption
medEnergy
Note Writing is only possible, if the SIMOCODE password protection is not enabled.
See system manual of the device under “Data formats and data records > Data
record 224 – Password protection”.
IntMotOperHours – internal motor operating hours

The structure tag “IntMotOperHours” displays the internal operating hours of the
motor.
Table 4-20
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_IntMotOperHours
Data type Real
Length 4 bytes

Entry ID: 66839614, V1.0, 09/2016 35
4 Mode of Operation
4.6 Tags of the UDT
MotOperHours – motor operating hours

The structure tag “MotOperHours” displays the operating hours of the motor.
Table 4-21
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_MotOperHours
Data type Real
Length 4 bytes
IntOverlTrips – internal number of overload trips

The structure tag “IntOverlTrips” displays the internal number of overload trips.
Table 4-22
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_IntOverlTrips
Data type Word
Address %DB611.DBW324
Length 2 bytes
OverlTrips – number of overload trips

The structure tag “OverlTrips” displays the number of overload trips.
Table 4-23
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_OverlTrips
Data type Word
Length 2 bytes

Entry ID: 66839614, V1.0, 09/2016 36
4 Mode of Operation
4.6 Tags of the UDT
IntNumbStarts_R – number of starts (right)

The structure tag “IntNumbStarts_R” displays the internal number of starts in the
running direction “right”.
Table 4-24
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_IntNumbStarts_R
Data type DWord
Length 4 bytes
NumbStarts – number of starts

The structure tag “NumbStarts” displays the number of starts (regardless of the
running direction).
Table 4-25
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_NumbStarts
Data type DWord
Length 4 bytes
IntNumbStarts_L – number of starts (left)

The structure tag “IntNumbStarts_L” displays the internal number of starts in the
running direction “left”.
Table 4-26
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_IntNumbStarts_L
Data type DWord
Length 4 bytes

Entry ID: 66839614, V1.0, 09/2016 37
4 Mode of Operation
4.6 Tags of the UDT
MotStopTime – stop time

The structure tag “MotStopTime” displays the downtimes of the motor.
Table 4-27
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_MotStopTime
Data type Word
Length 2 bytes
PermStarts – number of still permissible starts

The structure tag “PermStarts” displays the number of starts still permitted.
Table 4-28
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_PermStarts
Data type Byte
Address %DB611.DBB318
Length 1 byte
ConsumedEnergy – energy consumption

The structure tag “ConsumedEnergy” displays the energy used by the motor.
Table 4-29
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_ConsumedEnergy
Data type Real
Length 4 bytes
DeviceParameter – number of parameterizations

The structure tag “DeviceParameter” displays the number of configurations.
Table 4-30
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_DeviceParameter
Data type Word
Length 2 bytes

Entry ID: 66839614, V1.0, 09/2016 38
4 Mode of Operation
4.6 Tags of the UDT
DeviceOperHours – operating hours

The structure tag “DeviceOperHours” displays the operating hours of the device.
Table 4-31
Tag used
Symbolic name SimoDir_001_UDT.DPV1STAT_DeviceOperHours
Data type Real
Length 4 bytes
Note While the “Statistics” tab is open, the displayed statistical values are permanently
updated via acyclic services. This leads to an increased bus load.
(“Update data record 95 statistical data”).
The alternative code updates the diagnostic values only once when opening the
“Diagnosis” tab or when clicking the “Read” button.

Entry ID: 66839614, V1.0, 09/2016 39
4 Mode of Operation
4.7 Alarms and messages
4.7 Alarms and messages

This application example uses the discrete alarm procedure to display alarms in
WinCC Advanced. The messages must be configured as discrete alarms in the
alarms editor of WinCC Advanced.
In the sample configuration, all discrete alarms for the used faceplate instances
have already been created, just like their trigger tags.
Alarm tag
Table 4-32
Tag used
Symbolic name SimoDir_001_UDT.QwAlarm
Data type Word
Length 2 bytes
Acquisition mode Cyclic continuous
The following table shows the setup of the tags. The message texts are prefixed
with the “SimoDir_001” filter attribute for the first instance of the SimoDir screen
window.
Table 4-33 Setup of the “QwAlarm” tag

Bit Signal Alarm text
0 QPREO SimoDir_001: Prewarning overload
1 SimoDir_001:
2 SimoDir_001:
3 QGENFAIL SimoDir_001: SIMOCODE – Common failure
4 QLOCK SimoDir_001: Interlock is active
5 SimoDir_001:
6 QERR_EXT SimoDir_001: External error
7 QERR SimoDir_001: Common error
8 QSTOP SimoDir_001: Motor is OFF
9 QRUN SimoDir_001: Motor is ON
10 SimoDir_001:
11 QGENWARN SimoDir_001: SIMOCODE – Common warning
12 LOCK SimoDir_001: Motor is LOCKED
13 REMOTE SimoDir_001: Control => REMOTE
14 QMAN_AUT SimoDir_001: Operating mode => AUTOMATIC
15 QSIM SimoDir_001: Simulation is ON

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

Configure the motor management system in the hardware configuration as “Direct
starter” to ensure that the correct data are transferred.
Figure 4-15
Further setting options in the hardware configuration are available in the

SIMOCODE System Manual (entry ID: 61896631).

Entry ID: 66839614, V1.0, 09/2016 41
4 Mode of Operation
4.8.1 Processing of switching commands in the controller
The WinCC Advanced control tag “OPdwCmd” of a block is used for transmitting
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 on the usage in WinCC Advanced can be found in chapter
4.6.1 “Tags with function tasks”.
Figure 4-16
“SimoDir” (FB 611)
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
fCurrentE QfCurrentA
DIAG_REQ QPREO
STAT_REQ QLOCT
STAT_REQ_WR QGENWARN
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
The following table shows the setup of the “OPdwCmd” tag.
Table 4-34 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
STAT_REQ_WR
SIMULATION
STAT_REQ
DAIG_REQ
PROCESS
REMOTE
MANUAL
RESET
LOCAL
START
Signal
AUTO
STOP

Entry ID: 66839614, V1.0, 09/2016 42
4 Mode of Operation
4.8.2 Transmitting switching commands to the motor management system
Figure 4-17
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Note Make sure to configure the motor management in the hardware configuration as
“Direct starter” to ensure that the correct data are transferred.
To transfer control signals to the SIMOCODE pro, the “QSCwCmd” output is used.
In the block of this application example, the peripheral output word 0 (PAW0) is
interconnected with the output.
Check the hardware configuration (see Figure 4-18) with regard to the correct start
address of the input addresses (1) and adjust the peripheral output word to the set
value.
The status information of the SIMCODE pro is read in via the “SCdwInp” input.
In the block of this application example, the peripheral input double word 0 (PED0)
is interconnected with the input.
Check the hardware configuration (see Figure 4-18) with regard to the correct start
address of the output addresses (2) and adjust the peripheral input double word to
the set value.

Entry ID: 66839614, V1.0, 09/2016 43
4 Mode of Operation
Figure 4-18 I/O addresses depending on basic type and HW configuration
1 2
3
Note For configuring the hardware, the device has been configured with the basic
type “3” (3).
SIMOCODE pro V PN supports several I/O configurations to define the structure
and length of the I/O data that are exchanged cyclically between the
IO controller (PLC) and the IO device (SIMOCODE pro) (4). For SIMOCODE pro,
these configurations are referred to as basic types.
Information on the basic types and the corresponding I/O configurations are
available in the System Manual “SIMOCODE pro PROFINET” under
“Communication > Integration of SIMOCODE pro into the automation system
(PLC)” (entry ID: 61896631).

Entry ID: 66839614, V1.0, 09/2016 44
4 Mode of Operation
4.8.3 Evaluating and displaying process states in WinCC Advanced
The technology block of this application example uses the output “QdwState”
(DWORD) to show the different states in the WinCC Advanced process screen.
Further notes on the usage in WinCC Advanced can be found in chapter
4.6.1 “Tags with function tasks”.
Figure 4-19
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
The following table shows the setup of the “QdwState” tag.
Table 4-35 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
DPV1STAT_WR_QbBUSY
DPV1DEV_QbBUSY
QGENWARN
QMAN_AUT
QERR_EXT
QREMOTE
QGENFAIL
QPREO
QSTOP
QLOCK
QLOCT
Signal
QRUN
QERR
LOCK
QSIM

Entry ID: 66839614, V1.0, 09/2016 45
4 Mode of Operation
4.8.4 Manual/automatic mode
For toggling between the “MANUAL/AUTO” modes, the following signals are used:
Figure 4-20
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Inputs
“LIOP_SEL”
If the “LIOP_SEL” input is set, the operating mode will be defined via the
control input “L_AUT”.
If the “LIOP_SEL” input is not set, the operating mode is defined by the
operator (via “OPdwCmd”).
“L_AUT”
The “L_AUT” input will only be effective, if the “LIOP_SEL” input is set.
“LIOP_SEL” = 1 AND “L_AUT” = 0  “MANUAL” mode
“LIOP_SEL” = 1 AND “L_AUT” = 1  “AUTO” mode

Entry ID: 66839614, V1.0, 09/2016 46
4 Mode of Operation
“OPdwCmd”
The operator commands of the control word “OPdwCmd” will only be effective,
if the “LIOP_SEL” input is not set.
3
“LIOP_SEL” = 0 AND “OPdwCmd [bit 16] ” = 1  “MANUAL” mode
4
“LIOP_SEL” = 0 AND “OPdwCmd [bit 17] ” = 1  “AUTO” mode
Outputs
“QMAN_AUT”
The operating mode is indicated at the “QMAN_AUT” block output.
“QMAN_AUT” = 0  “MANUAL” mode
“QMAN_AUT” = 1  “AUTO” mode
“QdwState”
The current operating mode (“manual/automatic”) is transferred to
WinCC Runtime Advanced in bit 16 of the “QdwState” status word.
5
“QdwState [bit 16] ” = 0  “MANUAL” mode
4
“QdwState [bit 16] ”= 1  “AUTO” mode
Table 4-36 Status of inputs and outputs, operating mode

Operating mode Status of input tag Status of output tag
LIOP_ L_AUT OPdwCmd QMAN_AUT QdwState

SEL
Bit 16 Bit 17 Bit 16
Manual mode 0 ---* 1 0 0 0
Manual mode 1 0 ---* ---* 0 0
Automatic mode 0 ---* 0 1 1 1
Automatic mode 1 1 ---* ---* 1 1
In case of error  always
0 ---* 1 1 1 1
“AUTO” mode
In case of error 
previous operating mode 0 ---* 0 0 1 or 0 1 or 0
remains
* Value without impact
3
Bit 16 = “MANUAL”
4
Bit 17 = “AUTO”
5
Bit 16 = “QMAN_AUT”

Entry ID: 66839614, V1.0, 09/2016 47
4 Mode of Operation
4.8.5 Toggling between local and remote operating mode
In the “Local” operating mode, the control commands of the operator become
effective directly at the device. In the “Remote” operating mode, the control signals
of an automatic function (e. g. control, sequencer etc.) or the control signals of the
operation are effective in WinCC Runtime Advanced.
Figure 4-21
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Inputs
“SCdwInp”
“SCdwInp” evaluates the status word of the SIMOCODE pro.
The structure of the process input is available in the system manual of the
device under “Data formats and data records > Data record 69 – Process
image input” or under “Data formats and data records > Assignment of cyclic
receive and send data for existing control functions > Direct starter” (entry ID:
61896631).
“SCdwInp [bit 29]” = 0  “Local” mode
“SCdwInp [bit 29]” = 1  “Remote” mode

Entry ID: 66839614, V1.0, 09/2016 48
4 Mode of Operation
“LIOP_SEL”
If the “LIOP_SEL” input is set, the operating mode is defined via the control
input “L_REMOTE”.
If the “LIOP_SEL” input is not set, the operating mode is defined by the
“L_REMOTE”
The “L_REMOTE” input is only effective, if the “LIOP_SEL” input is set.
“LIOP_SEL” = 1 AND “L_REMOTE” = 0  “Local” mode
“LIOP_SEL” = 1 AND “L_REMOTE” = 1  “Remote” mode
“OPdwCmd”
The operator commands of the control word “OPdwCmd” are only effective, if
the “LIOP_SEL” input is not set.
6
“LIOP_SEL” = 0 AND “OPdwCmd [bit 18] ” = 1  “Local” mode
7
“LIOP_SEL” = 0 AND “OPdwCmd [bit 19] ” = 1  “Remote” mode
Outputs
“QREMOTE”
The operating mode is indicated at the “QREMOTE” block output.
“QREMOTE” = 0  “Local” mode
“QREMOTE” = 1  “Remote” mode
“QdwState”
The current operating mode (“local/remote”) is transferred to WinCC Advanced
in bit 17 of the “QdwState” status word.
8
“QdwState [bit 17] ” = 0  “Local” mode
7
“QdwState [bit 17] ” = 1  “Remote” mode

LIOP_ L_REM OPdwCmd QREMOTE QdwState
SEL OTE
Local mode 0 ---* 1 0 0 0
Local mode 1 0 ---* ---* 0 0
Remote mode 0 ---* 0 1 1 1
Remote mode 1 1 ---* ---* 1 1
0 ---* 1 1 1 1
“Remote” mode
previous operating mode 0 ---* 0 0 0 or 1 0 or 1
remains
6
Bit 18 = “LOCAL”
7
Bit 19 = “REMOTE”
8
Bit 17 = “QREMOTE”

Entry ID: 66839614, V1.0, 09/2016 49
4 Mode of Operation
4.8.6 Toggling between general operating mode Start/Stop
The switchover is influenced by other functions, e. g. the “manual/automatic”

switchover, “local/remote” switchover and “Simulation”.
Figure 4-22
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Inputs
“SCdwInp”
“SCdwInp” evaluates the status word of the SIMOCODE pro. The outputs of
the status word are configurable and may be different from the documentation.
image input” or under “Data formats and data records > Assignment of cyclic
61896631).
“SCdwInp [bit 24]” = 1  Start (left-hand rotation)
“SCdwInp [bit 25]” = 1  Stop
“SCdwInp [bit 26]” = 1  Start (right-hand rotation)

Entry ID: 66839614, V1.0, 09/2016 50
4 Mode of Operation
“AUT_ON”
The “AUT_ON” input is used for the automatic control of the block.
“AUT_ON” = 0  Stop
“AUT_ON” = 1  Start
“OPdwCmd”
[Bit 0] and [bit 1] in the “OPdwCmd” control word are used for operation in
WinCC Runtime Advanced.
9
“LIOP_SEL” = 0 AND “OPdwCmd [bit 0] ” = 1  Stop
10
“LIOP_SEL” = 0 AND “OPdwCmd [bit 1] ” = 1  Start
Outputs
“QSCwCmd”
Operation of the SIMOCODE pro is realized via the “QSCwCmd” command
word.
image output” or under “Data formats and data records > Assignment of cyclic
61896631).
“QSCwCmd [bit 8]” = 1  Start (left-hand rotation)
“QSCwCmd [bit 9]” = 1  Stop

“QSCwCmd [bit 10]” = 1  Start (right-hand rotation)
Note Depending on the configuration of the device, you can change the controlled bit
in network 10 of the FB611 “SimoDir” from [bit10] to [bit8] to reverse the running
direction of the motor when starting.
“QwState”
The current operating mode is displayed at the “QwState” output as numerical
value.
“QwState” = 1  Stop
“QwState” = 2  Start
“QwState” = 3  Run
“QwState” = 4  Stop
This signal “QwState” is used internally for calculating the status transitions.
9
Bit 0 = “STOP”
10
Bit 1 = “START”

Entry ID: 66839614, V1.0, 09/2016 51
4 Mode of Operation
“QCMD_OFF”, “QCMD_ON”
The signals “QCMD_OFF” and “QCMD_ON” are used for setting [bit 8] and [bit
9] of the “QSCwCmd” command word.
“QwState” = 1  Stop  “QCMD_OFF” = 0, “QCMD_ON”= 0
“QwState” = 2  Start  “QCMD_OFF” = 0, “QCMD_ON”= 1
“QwState” = 3  Run  “QCMD_OFF” = 0, “QCMD_ON”= 0
“QwState” = 4  Stop  “QCMD_OFF” = 1, “QCMD_ON”= 0
“QSTOP”, “QRUN”
Regarding these signals, precisely one of the signals is set at any time. In case of
an error – if no signal is set or both signals are set – the “Illegal” status occurs.
“QSTOP” = 1  Stop (“QwState” = 1)
“QRUN” = 1  Run (“QwState” = 3)
“QdwState”
10
The current “Stop/Run” mode is displayed in the status double word by [bit 0]
11
and [bit 1] .
11
“QdwState [bit 0] ” = 1  Stop
12
“QdwState [bit 1] ” = 1  Run
11
Bit 0 = “QSTOP”
12
Bit 1 = “QRUN”

Entry ID: 66839614, V1.0, 09/2016 52
4 Mode of Operation
4.8.7 Simulation ON/OFF
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 feedback simulation, many automatic functions (e. g. sequencers) cannot
be successfully executed, since the feedback signals are often required for
switching conditions in sequencers or for triggering error messages. The “SCdwInp”
input and the “QSCdwCmd” output are not evaluated in this mode.
Figure 4-23
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Inputs
“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
“L_SIM”
“LIOP_SEL” = 1 AND “L_SIM” = 0  Simulation OFF
“LIOP_SEL” = 1 AND “L_SIM” = 1  Simulation ON

Entry ID: 66839614, V1.0, 09/2016 53
4 Mode of Operation
“OPdwCmd”
The operator commands of the control word “OPdwCmd” are only effective, if
the “LIOP_SEL” input is not set.
13
“LIOP_SEL” = 0 AND “OPdwCmd [bit 20] ” = 1  Simulation OFF
14
“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” operating mode is indicated in the status word by
14
means of [bit 18] .
15
“QdwState [bit 18] ” = 0  Simulation OFF
14
“QdwState [bit 18] ” = 1  Simulation ON

LIOP_ L_SIM OPdwCmd QSIM QdwState
SEL
Simulation OFF 0 ---* 1 0 0 0

Simulation OFF 1 0 ---* ---* 0 0
Simulation ON 0 ---* 0 1 1 1
Simulation ON 1 1 ---* ---* 1 1
0 ---* 1 1 1 1
“Simulation ON”
previous simulation 0 ---* 0 0 0 or 1 0 or 1
status remains
13
Bit 20 = “PROCESS”
14
Bit 21 = “SIMULATION”
15
Bit 18 = “QSIM”

Entry ID: 66839614, V1.0, 09/2016 54
4 Mode of Operation
4.8.8 Displaying and resetting the interlock
Blocks influencing the plant process as actuators (e. g. valves, pumps, controllers,
etc.) usually have signals for the interlock function (INTERLOCK).
If the interlock condition of a block is active, the specific function of the block (e. g.
open valve, switch on motor, etc.) cannot be executed.
If the actual block function is already active (e. g. motor ON) and then the interlock
condition applies, the actual block function will be deactivated (e. g. motor switched
OFF).
This function is used for preventing critical plant conditions.
Figure 4-24
EN ENO
SCdwInp QdwState
LOCK QwState
ERR_EXTERN QSCwCmd
LIOP_SEL QCMD_OFF
L_AUT QCMD_ON
L_REMOTE QRUN
L_SIM QSTOP
L_RESET QMAN_AUT
AUT_ON QREMOTE
DPV1_ID QSIM
INSTANCE QLOCK
RESTART QERR
VISIBILITY QERR_EXT
OPdwCmd QfCurrentP
DIAG_REQ QPREO
STAT_REQ QLOCT
QGENFAIL
DPV0_RETVAL
DPV0_BUSY
QwAlarm
Inputs
“LOCK”
The input signal “LOCK” includes the interlock condition of the block. If the
interlock is pending, the actual block function cannot be executed.
“LOCK” = 0  Interlock condition not active
“LOCK” = 1  Interlock condition active
“L_RESET”
A positive edge at the “L_RESET” input resets the “QLOCK” output.

Entry ID: 66839614, V1.0, 09/2016 55
4 Mode of Operation
“OPdwCmd”
16
Clicking the “RESET” button in the faceplate of the block type sets [bit 24] of
the control word “OPdwCmd”. The controller evaluates this bit and resets the
“QLOCK” output.
Outputs
“QLOCK”
The “QLOCK” output signal is set, if the “LOCK” input is active.
“QLOCK” = 1  Interlock pending
“QLOCK” = 0  Interlock not pending
“QdwState”
The states “Interlock condition active” (LOCK=1) and “Error interlock”
(QLOCK=1) are indicated in the status word by bits 26 and 27.
17
LOCK = 1  “QdwState [bit 27] ” = 1 (Interlock condition active)
18
QLOCK = 1  “QdwState [bit 26] ” = 1 (Interlock pending)
16
Bit 24 = “RESET”
17
Bit 27 = “LOCK”
18
Bit 26 = “QLOCK“

Entry ID: 66839614, V1.0, 09/2016 56
5 Commissioning the Application Example
5.1 Configuring the STEP 7 block

Introduction
Here you will learn how to integrate objects of the library of this application
example into an empty or existing project.
This example uses the non-connected STEP 7 block, the faceplate icon
“SimoDir_001_Icon” and the faceplates belonging to the screen window “SimoDir”.
Note The application example 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 Example”.
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.

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 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.

Entry ID: 66839614, V1.0, 09/2016 57
Process Description
3. Inserting blocks
 Drag the “SimoDir” (FB611) function block from the “Master copies >
SIMODIR” folder in the project tree into the “Program blocks” directory of
the controller.
 Optional: Drag the “SimoDir_DB” instance data block from the “Master
copies > SIMODIR” folder in the project tree into the “Program blocks”
directory of the controller.
4. Calling the blocks
 Integrate the function block into the cycle of the controller. If you call up
the function block in an organization block, the name of the
corresponding instance data block is required in the dialog window
“Calling options” upon insertion.
 You can generate the corresponding instance data block automatically
or use the instance data block “SimoDir_DB” from the library. Select the
desired instance data block and click “OK”.

Entry ID: 66839614, V1.0, 09/2016 58
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, 09/2016 59
5.2.2 Integrating the library elements into the project
The library offers two options to integrate the faceplates into your project.
 The quicker option is to use the elements 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. Project preparation
 Add the desired HMI operator panel and the controller, if not yet available.
 In the project tree, open the HMI project of your HMI operator panel.
2. Opening the global library

Open the global library as described in Table 5-2.

Entry ID: 66839614, V1.0, 09/2016 60
Step Procedure
3. Copying library elements – “Screen
window” faceplates
Drag and drop the folder “SIMODIR”, which

contains the faceplates and the HMI UDT,
from the folder “Types” of the global library
into the folder “Types” of the project library.
4. The folder “SIMODIR” contains the faceplates of the screen window:

 “SimoDir_1_Overview”,
 “SimoDir_2_Messages”,
 “SimoDir_3_Graphs”,
 “SimoDir_4_Diagnosis”,
 “SimoDir_5_Statistics”,
 “SimoDir_6_Service”.
Furthermore, it contains the faceplate of the faceplate icon and the HMI UDT:
 “SimoDir_001_Icon”,
 “SimoDir_UDT”.

Entry ID: 66839614, V1.0, 09/2016 61
Step Procedure
5. Copying library elements
 Drag and drop the following library elements from the folder “Master copies > SIMODIR”
of the global library into the respective folders in the project tree:
– “SimoDir_001_Tags”  “HMI tags”
– “SimoDir_001_Pop-up”  “Screen management > Pop-up screens”
 Drag and drop the tag table “MenuControl” from the folder “Master copies < MenuControl”
of the global library into the “HMI tags” folder in the project tree.
Check the connection of the tags and restore it, if necessary.

For this, go to the tag table and replace the name of the HMI connection
(“HMI_Connection_1”) by the name of the HMI connection used in your project.

Entry ID: 66839614, V1.0, 09/2016 62
Step Procedure
6. Integrating the alarms
 After dragging the tag table, the corresponding HMI alarms are created automatically. This
happens, because the tag “SimoDir_001_UDT.QwAlarm” used as trigger tag is included in
the tag table.
 If you want to create the messages manually, select the category “Master copies >
SIMODIR” within the library. Drag and drop the folder “SimoDir_001_Messages” into the
folder “HMI alarms” in the project tree.
Note
The message numbers of this application occupy the number range starting with 10097.
Before integrating the messages, check your existing project and, if occupied, clear this area.
Restore the connection to the associated trigger tag as well as the associated trigger bit.

Entry ID: 66839614, V1.0, 09/2016 63
Step Procedure
7. Creating the HMI screen
 Drag and drop the faceplate icon “SimoDir_001_Icon” and the transparent button
“SimoDir_001_Button” for calling the “SimoDir_001_Pop-up” screen window into the
desired screen.
 Place the button above the faceplate icon.
Click on the task card “layout” and make sure that the button is assigned to a level with a
number higher than that of the faceplate icon.
Configuring by means of types

Table 5-4
Step Procedure
1. Project preparation
 Add the desired HMI operator panel and the controller, if not yet available.
 In the project tree, open the HMI project of your HMI operator panel.
2. Opening the global library
Open the global library as described in Table 5-2.

Entry ID: 66839614, V1.0, 09/2016 64
Step Procedure
3. Copying library elements – “Screen
window” faceplates
Drag and drop the folder “SIMODIR”, which
contains the faceplates and the HMI UDT,
from the folder “Types” of the global library
into the folder “Types” of the project library.
4. The folder “SIMODIR” contains the faceplates of the screen window:

 “SimoDir_1_Overview”,
 “SimoDir_2_Messages”,
 “SimoDir_3_Graphs”,
 “SimoDir_4_Diagnosis”,
 “SimoDir_5_Statistics”,
 “SimoDir_6_Service”.
Furthermore, it contains the faceplate of the faceplate icon and the HMI UDT:
 “SimoDir_001_Icon”,
 “SimoDir_UDT”.

Entry ID: 66839614, V1.0, 09/2016 65
Step Procedure
5. Copying library elements – “Faceplate icon” faceplate
 Drag and drop the faceplate icon “SimoDir_001_Icon” and the transparent button
“SimoDir_001_Button” for calling the screen window into the desired screen.
 At the transparent button, delete the system function “ShowPopupScreen” under
“Properties > Events > Release”.
 Place the button above the faceplate icon.
Click on the task card “layout” and make sure that the button is assigned to a level with a
number higher than that of the faceplate icon.

Entry ID: 66839614, V1.0, 09/2016 66
Step Procedure
6. Copying library elements – tags
 Drag and drop the library element “SimoDir_001_Tags” from the folder “Master copies >
SIMODIR” of the global library into the “HMI tags” folder in the project tree.
 In an HMI tag table, create an internal “Visibility” tag of the data type “Int.”.
Alternatively, you can use the “Visibility” tag from the library element “MenuControl”. For
this, drag and drop the library element “MenuControl” from the folder “Master copies >
MenuControl” of the global library into the “HMI tags” folder in the project tree.
Check the connection of the tags and restore it, if necessary.

For this, go to the tag table and replace the name of the HMI connection
(“HMI_Connection_1”) by the name of the HMI connection used in your project.

Entry ID: 66839614, V1.0, 09/2016 67
Step Procedure
7. Now, create your own menu structure for calling the individual faceplates. Via your buttons,
provide the following PLC and HMI tags with the appropriate values to control the
corresponding faceplates.
 To call “SimoDir_1_Overview”:
– “Visibility” = 1
 To call “SimoDir_2_Messages”:
 To call “SimoDir_3_Graphs”:
 To call “SimoDir_4_Diagnosis”:
– “SimoDir_DB_OP_VISIBILITY” = 4
– “SimoDir_DE_SE_TAB_DIAG_REQ” = 1
 To call “SimoDir_5_Statistics”:
– “SimoDir_DB_OP_VISIBILITY” = 5
– “SimoDir_DE_SE_TAB_STAT_REQ” = 1
 To call “SimoDir_6_Service”:
8. Integrating the alarms
 After dragging the tag table, the corresponding HMI alarms are created automatically. This
happens, because the tag “SimoDir_001_UDT.QwAlarm” used as trigger tag is included in

the tag table.
 If you want to create the messages manually, select the category “Master copies >
SIMODIR” within the library. Drag and drop the folder “SimoDir_001_Messages” into the
folder “HMI alarms” in the project tree.
Note
The message numbers of this application occupy the number range starting with 10097.
Before integrating the messages, check your existing project and, if occupied, clear this area.
Restore the connection to the associated trigger tag as well as the associated trigger bit.

Entry ID: 66839614, V1.0, 09/2016 68
Step Procedure
9. Interconnecting the faceplate icon
 Connect the dynamic properties of the faceplate icon “SimoDir_001_Icon” to the
respective HMI tag:
– “Process > Value”  “SimoDir_001_UDT”
The faceplate icon is overlapped by the transparent button “SimoRev_001_Button” (see step
5). You can select the faceplate icon by selecting the object “SimoRev_001_Icon” on the
“Layout” task card.
10. Interconnecting the faceplates of the screen window

 Interconnect the dynamic properties of the individual faceplates of the screen window, if
available at the faceplate, with the associated HMI tags:
– “Process > Value”  “SimoDir_001_UDT”
– “Property > Visibility”  “Visibility”

Entry ID: 66839614, V1.0, 09/2016 69
5.3 Setting up the IP address

This chapter describes how to set up the IP address of the motor management
system SIMOCODE pro if you are using the TIA Portal without having installed the
engineering software “SIMOCODE ES”.
Prerequisite
The SIMOCODE pro device and the corresponding controller are in the same
network.
Settings in the hardware configuration

1. Open the hardware configuration in the TIA Portal.
– For this, click “Devices & networks” in the project tree.
2. Assign a name and an IP address for every existing SIMOCODE pro device.
– Assign the name in the properties under “General > Name”.
– Assign the IP address in the properties under “PROFINET interface >
Ethernet addresses > IP protocol > IP address”.
3. Compile the hardware configuration of the connected controller. Thus, the
hardware configuration of the SIMOCODE pro devices will be compiled as well.
The hardware configuration of the SIMOCODE pro device cannot be compiled
separately.
Online access: Accessible devices

1. In the project tree, open the “Online access” folder.
2. In the folder of the interface you are using, click “Update accessible devices”.
3. In the folder of the SIMOCODE pro device, double-click “Online & diagnostics”.
4. Click “Functions > Assign name”.
5. Under “Configured PROFINET device > PROFINET device name:”, enter the
name that you have assigned for the device in the project.
6. Click the “Assign name” button.
Loading the hardware configuration

Load the hardware configuration into the corresponding controller.
The SIMOCODE pro device takes over the IP address of the device which has the
same name in the hardware configuration.
Notes  The steps “Online access: Accessible devices” and “Loading the hardware
configuration” can be carried out in reverse order.
The IP address will be taken over only if all steps have been carried out.
 You can check whether the name and the IP address have been changed
successfully by clicking “Update accessible devices” in the project tree again.
– If the folder of the SIMOCODE pro device shows the entered name, the
name has been assigned successfully.
– If in the name of the folder of the SIMOCODE pro device the name is
followed by the appropriate IP address, the IP address has been assigned
successfully.

Entry ID: 66839614, V1.0, 09/2016 70
6 Operating the Application Example

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 8 or higher.
3. Adjust the configured hardware according to your requirements under “Devices &
networks”.
4. Open the STEP 7 project and generate it again.
5. Load the STEP 7 project into your controller and start it.
6. Open the WinCC V13 Advanced project and generate it again.
7. Start the WinCC Runtime Advanced or the WinCC Runtime Advanced
simulation.

Entry ID: 66839614, V1.0, 09/2016 71
6.1 Navigation
6.1 Navigation
Overview of the user interface
Figure 6-1
2
4
3
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 access the example blocks of this application example.
3 Support
Here you will find out more about the Siemens Industry Online Support.
4 Navigation
You can access the navigation in each screen at the left window frame.
You can access the start screen via this button.
This button takes you to the previous screen.
Use this button to close the application example.
Use this button to change the language (German/English).

Entry ID: 66839614, V1.0, 09/2016 72
6.1 Navigation
Selecting elements
Figure 6-2
1
Table 6-3
Figure Explanation
1 Primary navigation
Here, you can select the individual sets of the application example via
buttons.
The application example consists 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, 09/2016 73
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 example, the faceplate icon
becomes visible.
2 When selecting the faceplate icon, the corresponding screen window
containing more detailed information opens.
Operating the screen window

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

Entry ID: 66839614, V1.0, 09/2016 74
6.2 Faceplate icon
6.2 Faceplate icon

In set 2 of the example project, click the “SimoDir” button to open the screen
containing the faceplate icon.
Overview
Figure 6-5
Properties
 Has a simplified status display
 Opens the screen window via mouse-click
 Contains no language-dependent objects
Functionality
 Displayed operating states:
– ON/OFF status
– Local mode / remote mode status
– Manual / automatic mode status
– Simulation ON/OFF
– Interlock ON/OFF
– Current consumed by the motor in % of the nominal motor current
 Displayed errors:
– General error
 Operation:
– Calling the assigned screen window
Possible operating states:

Table 6-6
Operating QdwState Icon Flashing
mode
OFF Bit 0 = 1 No
ON Bit 2 = 1 No
Error Bit 24 = 1 Yes

Entry ID: 66839614, V1.0, 09/2016 75
6.3 Screen window
Possible status displays:

Table 6-7
Status Icon
Local
Remote
Manual
Automatic
Simulation ON
Simulation OFF
Interlock OFF
Interlock ON
Interlock triggered
Motor ON
6.3 Screen window

In the example project, click the invisible button located above the faceplate icon to
open the screen window.
6.3.1 Menu system und “Close” button
Properties
 Contains language-dependent objects: German (Germany), English (USA)
Executable actions
 Tab selection (optionally via the controller)
 Open, close

Entry ID: 66839614, V1.0, 09/2016 76
6.3 Screen window
6.3.2 Faceplate “SimoDir_1_Overview”
Click the “Overview” tab to call the faceplate.
Overview
Figure 6-6
Properties
 Detailed status display
 Provides the option to intervene in the process
 Contains language-dependent objects: German (Germany), English (USA)
Executable actions
 Switchover between local mode (operation at the device) and remote mode
(operation at the visualization system)
 Switchover manual/automatic mode
 Starting and stopping the motor.
Requires that remote mode and manual mode are enabled.
 Resetting error states

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

Table 6-8
Operating QdwState Icon Flashing
mode
OFF Bit 0 = 1 No
ON Bit 2 = 1 No
Error Bit 24 = 1 Yes

Table 6-9
Description Status Status Flashing
OFF ON
Interlock ON Yes
Simulation ON Yes
External error No
Prewarning overload No
Interlock time active No
Warning No
Error No
Table 6-10
Display Left button Right button
Motor OFF
Motor ON
Manual mode
Automatic mode
Local mode
Remote mode

Entry ID: 66839614, V1.0, 09/2016 78
6.3 Screen window
6.3.3 Faceplate “SimoDir_2_Messages”
Click the “Messages” tab to call the faceplate.
Overview
Figure 6-7
Executable actions
 Display of alarms and warnings
 Acknowledgment of alarms
 Filter for instance-related messages and alarms
The displayed filter corresponds to the instance name in DB611.
If the filter is set, e. g. as “SimoDir_001”, only messages with the filter prefix
“SimoDir_001” in their message text will be displayed.

Entry ID: 66839614, V1.0, 09/2016 79
6.3 Screen window
6.3.4 Faceplate “SimoDir_3_Graphs”
Click the “Graphs” tab to call the faceplate.
Overview
Figure 6-8
Trend views
 Nominal motor current in A
 Actual value of the motor current in A
Note The maximum value of the Y-axis is automatically scaled to the 1.25-fold of the
nominal motor current.

Entry ID: 66839614, V1.0, 09/2016 80
6.3 Screen window
6.3.5 Faceplate “SimoDir_4_Diagnosis”
Click the “Diagnosis” tab to call the faceplate.
Overview
Figure 6-9
Executable actions
 None. There is only a read access to the values of this tab.

 Motor status (different parameters)
 Protective status messages
 Connection to the PLC / PLC status
Table 6-11
OFF ON
General fault No
General warning No
Device OK No
Bus OK No
PLC/PCS in RUN No
Motor current flowing No
ON No
OFF No
Start active No

Entry ID: 66839614, V1.0, 09/2016 81
6.3 Screen window

OFF ON
Interlock time active No
Operational protection No
OFF
Emergency start No
executed
Cooling-down period No
active
Pause time active No
Device check active No
Phase sequence 1-2-3 No
Phase sequence 3-2-1 No
6.3.6 Faceplate “SimoDir_5_Statistics”
Click the “Statistics” tab to call the faceplate.
Overview
Figure 6-10
Executable actions
 Reading statistical data
– Depending on the respective setting, the data are read cyclically or once
by clicking the “Read” button or by selecting (once again) the “Statistics”
tab (see chapter 4.3 “Screen window”).
– Activating the “Enable Input” button prevents the display from being
updated until this same button (“Disable Input”) is deactivated by clicking it
again.

Entry ID: 66839614, V1.0, 09/2016 82
6.3 Screen window
 Writing statistical data

– Click “Enable Input”.
– Enter the desired values and complete the input by clicking the “Enter” key.
– Click “Write” to apply the entered values.
– Alternatively, click “Disable Input” in order not to apply the entered values
and to show the previously displayed device data.

 Motor data (internal, external)
 Device data
Note Writing is only possible, if the SIMOCODE password protection is not enabled.
See system manual of the device under “Data formats and data records > Data
record 224 – Password protection”.
This password protection is independent of a possible access protection on the
HMI side via the user management:
You can, for example, provide the “Enable Input” button with an HMI-side access
protection to control the write access of the users to the values.

Entry ID: 66839614, V1.0, 09/2016 83
6.3 Screen window
6.3.7 Faceplate “SimoDir_6_Service”
Click the “Service” tab to call the faceplate.
Overview
Figure 6-11
Executable actions
 Display of the current instance designation
 Switchover between simulation/real process mode
Scope of the simulation:
– During simulation, you can toggle between automatic and manual mode.
– In manual mode, the motor can be “started” and “stopped”.
– The graphic for visualizing the motor status, the display of the actual value
(in A and %) as well as the trend view respond to the simulated “status” of
the motor.
Status displays:
Table 6-12
Display Left button Right button
Simulation OFF
Simulation ON
Note Optional: Provide the “Service” tab with an HMI-side access protection to control
the access to simulation mode.

Entry ID: 66839614, V1.0, 09/2016 84
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
SCdwInp DWORD 16#0 Status signals by SIMOCODE pro
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 mode, 1=Automatic
mode
L_REMOTE BOOL FALSE 0=Local mode,
1=Remote mode
L_SIM BOOL FALSE 0=Process,
1=Simulation
L_RESET BOOL FALSE Reset error
(positive edge)
AUT_ON BOOL FALSE 0=Manual mode, 1=Automatic

mode
DPV1_ID WORD 16#0 Hardware address
INSTANCE STRING SimoDir_001 Filter attribute for alarms
RESTART BOOL FALSE Initializing at restart
7.2 Input/output parameters

Table 7-2
Parameters Data type Default setting Description
VISIBILITY BYTE 16#0 Representation of the
screen window
OPdwCmd DWORD 16#0 Control tag HMI  PLC
fCurrentE REAL 1.0 Nominal motor current
DIAG_REQ BOOL FALSE 1=Request diagnostic data
STAT_REQ BOOL FALSE 1=Read statistical data
STAT_REQ_WR BOOL FALSE 1=Write statistical data

Entry ID: 66839614, V1.0, 09/2016 85
7 Block Interfaces
7.3 Output parameters

Table 7-3
Parameters Data Default setting Description
type
QdwState DWORD 16#0 Status tag HMI
QwState INT 0 Motor status
(1=Stop / 2=Start / 3=Run /
4=Stop)
QSCwCmd WORD 16#0 Control signals to
SIMOCODE pro
QCMD_OFF BOOL FALSE 1=SIMOCODE stop command
QCMD_ON BOOL FALSE 1=SIMOCODE start command
QRUN BOOL FALSE 1=Run
QSTOP BOOL FALSE 1=Stop
QMAN_AUT BOOL FALSE 0=Manual mode, 1=Automatic
mode
QREMOTE BOOL FALSE 0=Local mode,
1=Remote mode
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
QfCurrentP REAL 0.0 Current in percent (%)
QfCurrentA REAL 0.0 Current in amperes (A)
QPREO BOOL FALSE Prewarning overload
QLOCT BOOL FALSE Interlock time active
QGENWARN BOOL FALSE SIMOCODE common warning
QGENFAIL BOOL FALSE SIMOCODE common failure
DPV1DEV_iCntError INT 0 Data record 92 Number of
reading errors
DPV1DEV_iCntValid INT 0 Data record 92 Number of
successful read processes
DPV1DEV_QbBUSY BOOL FALSE Data record 92 Read process
not yet completed
DPV1DEV_QbVALID BOOL FALSE Data record 92 Read process
completed successfully
DPV1DEV_QbError BOOL FALSE Data record 92 Reading error
DPV1DEV_dwSTATUS DWORD 16#0 Data record 92 Read
status/error information
DPV1DEV_iLEN UINT 0 Data record 92 Length of the
read data record
DPV1DEV_Qdw00 DWORD 16#0 Status messages bytes 0-3
DPV1DEV_Qdw04 DWORD 16#0 Status messages bytes 4-7
PDV1STAT_iCntError INT 0 Data record 95 Number of
reading errors
PDV1STAT_iCntValid INT 0 Data record 95 Number of
successful read processes

Entry ID: 66839614, V1.0, 09/2016 86
7 Block Interfaces

type
PDV1STAT_QbBUSY BOOL FALSE Data record 95 Read process
not yet completed
PDV1STAT_QbVALID BOOL FALSE Data record 95 Read process
completed successfully
PDV1STAT_QbError BOOL FALSE Data record 95 Reading error
PDV1STAT_dwSTATUS DWORD 16#0 Data record 95 Read
status/error information
PDV1STAT_iLEN UINT 0 Data record 95 Length of the
read data record
PDV1STAT_PermStarts BYTE 16#0 Permissible starts (actual
value)
PDV1STAT_DevicePara WORD 16#0 Number of parameterizations
meter
PDV1STAT_OverlTrips WORD 16#0 Number of overload trips
PDV1STAT_IntOverlTrip WORD 16#0 Internal number of overload
s trips
PDV1STAT_MotStopTim WORD 16#0 Stop time
e
PDV1STAT_MotOperHo REAL 0.0 Operating hours (motor)
urs
PDV1STAT_IntMotOper REAL 0.0 Internal operating hours

Hours (motor)
PDV1STAT_DeviceOper REAL 0.0 Operating hours (device)
Hours
PDV1STAT_NumbStarts DWORD 16#0 Number of starts
PDV1STAT_IntNumbStar DWORD 16#0 Number of internal starts
ts_R (right)
PDV1STAT_IntNumbStar DWORD 16#0 Number of internal starts (left)
ts_L
PDV1STAT_ConsumedE REAL 0.0 Energy consumption
nergy
PDV1STAT_WR_iCntErr INT 0 Data record 95 Number of
or writing errors
PDV1STAT_WR_iCntDo INT 0 Data record 95 Number of
ne successful write processes
PDV1STAT_WR_QbBUS BOOL FALSE Data record 95 Write process
Y not yet completed
PDV1STAT_WR_QbDon BOOL FALSE Data record 95 Write process
e completed successfully
PDV1STAT_WR_QdER BOOL FALSE Data record 95 Writing error
ROR
PDV1STAT_WR_dwSTA DWORD 16#0 Data record 95 Write
TUS status/error information
PDV1STAT_WR_iLEN INT 0 Data record 95 Length of the
written data record
DPV0_RETVAL INT 0 Data record 95 Number of
writing errors
DPV0_BUSY BOOL FALSE Data record 95 Number of
successful write processes

Entry ID: 66839614, V1.0, 09/2016 87
7 Block Interfaces

type
QwAlarm WORD 16#0 Alarm tag
ENO BOOL FALSE Release

Entry ID: 66839614, V1.0, 09/2016 88
8 Additional Information
8 Additional Information
Further example blocks of this application example
This document is part of an application example which describes further technology
blocks. Within the framework of this application example, the number of example
technology blocks will be expanded successively.
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
ANALOGUE 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 application examples for example blocks

(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, 09/2016 89
9 Links & Literature
9 Links & Literature

Bibliographic references
This list shows only a selection of relevant information.
Table 9-1
Topic Title
\1\ Reference to the entry https://support.industry.siemens.com/cs/ww/en/view/66839614
\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/67989094
ET 200MP, ET 200SP,
ET 200AL, ET 200pro,
ET 200eco PN analog
value processing
\7\ Faceplates for the https://support.industry.siemens.com/cs/ww/en/view/67318600
Visualization of
SENTRON PAC Power
Meters for
WinCC Runtime
Professional
\8\ SITOP UPS1600: https://support.industry.siemens.com/cs/ww/en/view/78817848
Faceplates and STEP 7
communication blocks
\9\ Measuring and https://support.industry.siemens.com/cs/ww/en/view/86299299
Visualizing Energy
Data
\10\ Configuration https://support.industry.siemens.com/cs/ww/en/view/68014632
instruction for creating
faceplates for Comfort
Panels and
WinCC Runtime
Advanced
\11\ System Manual https://support.industry.siemens.com/cs/ww/en/view/61896631
SIMOCODE pro
PROFINET

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

Entry ID: 66839614, V1.0, 09/2016 91

WCA Faceplate SimoDir 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 SimoDir en

Uploaded by

Copyright:

Available Formats

Application Example  09/2016

TIA Portal Example Block

Warranty and Liability

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

4.4.4 Faceplate “SimoDir_4_Diagnosis” ..................................................... 23

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

6.3.1 Menu system und “Close” button ....................................................... 76

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

WinCC Professional faceplates: The connection to the controller is made

Topics not covered by this application

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

Description of the automation task

The faceplates have the following functions:

The following operating modes of the motor are displayed:

NOTICE It might be necessary to make some adjustments.

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

2.1 Overview of the overall solution

The faceplate icon consists of

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

2.2 Hardware and software components

This application example is valid for:

2.2.2 Topics not covered by this application

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

2.2.3 Components used

Standard software components

Example files and projects

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

3.1 Library objects

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

Types and instances

Further information on faceplates is available in the application example “Creating

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

4.1 Faceplate icon

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

Explanation of the parameters

The “SimoDir_001_UDT” UDT tag of the controller is connected to the “Value”

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

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

4.2 Interfaces of the faceplate icon

Tag group “Process”

Information on the structure of the UDT “SimoDir_001_UDT” are available in the

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

4.3 Screen window

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

Table 4-4 Event-triggered functions of the tabs

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

Whether the read command is set to be continuous or simple depends on

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

4.4 Components of the screen window

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

The following options are available:

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

4.4.1 Faceplate “SimoDir_1_Overview”

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

4.4.2 Faceplate “SimoDir_2_Messages”

The “SimoDir_2_Messages” faceplate is used for displaying messages. Messages

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

The message view is divided into six columns:

4.4.3 Faceplate “SimoDir_3_Graphs”

The “SimoDir_3_Graphs” faceplate is used for displaying graphs.

 Actual value of the nominal motor current in A (“Value [A]”)

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

4.4.4 Faceplate “SimoDir_4_Diagnosis”