CPU31xT Error Message DOKU v422 en

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

deficiency or breach of a condition which goes to the root of the contract
(“wesentliche Vertragspflichten”). The damages for a breach of a substantial
contractual obligation are, however, limited to the foreseeable damage, typical for
the type of contract, except in the event of intent or gross negligence or injury to
life, body or health. The above provisions do not imply a change of the burden of
proof to your detriment.
Any form of duplication or distribution of these Application Examples or excerpts

hereof is prohibited without the expressed consent of Siemens Industry Sector.
Security Siemens provides products and solutions with industrial security functions that
informa- support the secure operation of plants, solutions, machines, equipment and/or
tion networks. They are important components in a holistic industrial security
concept. With this in mind, Siemens’ products and solutions undergo continuous
development. Siemens recommends strongly that you regularly check for
product updates.
For the secure operation of Siemens products and solutions, it is necessary to
take suitable preventive action (e.g. cell protection concept) and integrate each
component into a holistic, state-of-the-art industrial security concept. Third-party
products that may be in use should also be considered. For more information
about industrial security, visit http://www.siemens.com/industrialsecurity.
To stay informed about product updates as they occur, sign up for a product-
specific newsletter. For more information, visit
http://support.automation.siemens.com.
"Error Messages" Technology Template

Entry-ID: 21402122, V4.2.2, 06/2014 2
Table of Contents
Table of Contents
Warranty and Liability .............................................................................................. 2
1 Inter Project Engineering ............................................................................... 5
2 Technology Template ..................................................................................... 6
2.1 Introduction ....................................................................................... 6
2.1.1 The technology template.................................................................... 6
2.1.2 Configuration systems ....................................................................... 6
2.1.3 Main contents of this technology template .......................................... 6
2.1.4 Scope ................................................................................................ 6
2.2 Objective and purpose ....................................................................... 7
2.2.1 Task .................................................................................................. 7
2.2.2 Advantages ....................................................................................... 7
2.3 Possible applications ......................................................................... 8
2.3.1 Tasks that can be solved with the technology template ...................... 8
2.3.2 Properties .......................................................................................... 8
2.3.3 Restrictions ....................................................................................... 9
2.4 Components of the technology template ............................................ 9
2.5 Approved hardware and software .................................................... 10
2.5.1 Hardware components..................................................................... 10
2.5.2 Software components ...................................................................... 10
3 Basics ........................................................................................................... 12
3.1 Functional principle of the technology template ................................ 12

3.2 Monitoring a technology object......................................................... 13
3.3 Monitoring a technology function...................................................... 13
4 Functional Mechanisms ............................................................................... 14
4.1 The ALARM_S message function .................................................... 14
4.2 Text lists .......................................................................................... 15
4.3 Associated values of the ALARM_S message function..................... 16
4.4 Configuring Report system error ...................................................... 16
4.5 Formatting the ALARM_S message texts......................................... 18
4.5.1 Setting the special object properties................................................. 18
4.5.2 Formatting the output format for the text messages .......................... 19
4.6 Change language ............................................................................ 23
4.6.1 Language versions of the text lists ................................................... 23
4.6.2 Change language in STEP 7............................................................ 23
4.6.3 Change language of the HMI user interface ..................................... 24
5 Installation .................................................................................................... 25
5.1 Preparations .................................................................................... 25
5.1.1 Retrieving the technology template .................................................. 25
5.2 Integration into your application ....................................................... 26
5.2.1 Transferring the complete S7 program folder ................................... 26
5.2.2 Integrating the technology template into your STEP 7 project ........... 27
5.2.3 Calling the function blocks ............................................................... 27
5.2.4 Assigning the instance data blocks .................................................. 28
5.3 Message configuration in WinCC flexible (STEP 7 V5.x) .................. 28
5.4 Message configuration in WinCC (TIA Portal) .................................. 31
5.4.1 Reconfiguring the operator panel ..................................................... 32
5.4.2 Updating the operator panel configuration ........................................ 36
5.4.3 Migrating the operator panel from STEP 7 V5.x ............................... 38
5.4.4 Storing the CPU messages in TIA Portal .......................................... 39
6 Startup .......................................................................................................... 41

Entry-ID: 21402122, V4.2.2, 06/2014 3
Table of Contents
6.1 Call environment.............................................................................. 41

6.2 Interfaces ........................................................................................ 41
6.2.1 Interface of FB 510 “ShowErrFB” ..................................................... 41
6.2.2 Interface of FB 511 “ShowErrDB”..................................................... 42
6.3 Warning messages and error messages .......................................... 43
6.3.1 Signaling error events in the “Error Messages” template .................. 43
6.3.2 Warning and error codes at the “ErrorID” output ............................... 44
7 Operation ...................................................................................................... 45
7.1 Monitoring with FB 510 “ShowErrFB” ............................................... 45
7.2 Monitoring with FB 511 “ShowErrDB” ............................................... 46
7.3 Error text output using “CPU Messages” .......................................... 47
7.3.1 Calling the “CPU Messages” function............................................... 47
7.3.2 Settings of the “CPU Messages” function ......................................... 48
7.3.3 Change language for the “CPU Messages” function ......................... 48
7.4 Error text output on the operator panel ............................................. 49
7.5 Test projects for the technology template ......................................... 49
7.5.1 Requirements for running the test projects ....................................... 49
7.5.2 The HMI user interfaces of the test projects ..................................... 50
7.5.3 Operating the test program .............................................................. 52
7.6 Generating error messages ............................................................. 54
7.6.1 Warning message 0021: Dynamic values are being limited .............. 54
7.6.2 Error message 8014: Approached a software limit switch ................. 55
7.6.3 Error message 8040: The axis / external encoder is not enabled,
or the wrong mode is set .................................................................. 56
7.6.4 Error message 804A: The required object interconnection is

missing ............................................................................................ 56
8 Editing the Text Lists ................................................................................... 58
8.1 Expanding/modifying the text lists .................................................... 58
8.2 Adding more language versions in STEP 7 ...................................... 59
8.2.1 Adding a display language ............................................................... 59
8.2.2 Exporting the text library .................................................................. 60
8.2.3 Opening and editing the exported text library ................................... 61
8.2.4 Importing a text library with additional texts ...................................... 63
9 Displaying your own Messages ................................................................... 64
9.1 Display with FB 510 “ShowErrFB” .................................................... 64
9.2 Display with FB 511 “ShowErrDB”.................................................... 64
10 References .................................................................................................... 66
11 History .......................................................................................................... 68

Entry-ID: 21402122, V4.2.2, 06/2014 4
1 Inter Project Engineering
1 Inter Project Engineering

Configuration in STEP 7 V5.x
A SIMATIC S7-300 Technology CPU 31xT is configured or programmed using the
STEP 7 V5.5 automation software and the integrated S7 Technology V4.2 option
package. A range of operator panels is available for visualization; they are
configured using the SIMATIC WinCC flexible HMI system that can be integrated
into STEP 7. In the following, this used tool environment will be referred to as
“STEP 7 V5.x”.
Configuration in TIA Portal

With the launch of the TIA Portal engineering framework, new operator panels, for
example Comfort Panels, can also be considered for visualizing T-CPU
applications. They are configured in TIA Portal V13 using the WinCC Comfort V13
engineering software. To distinguish the TIA Portal engineering framework from
STEP 7 V5.x, this document simply uses the terms “TIA Portal” or “TIA project”.
Visualization of a T-CPU with a Comfort Panel

IPE (Inter Project Engineering) is required to visualize a T-CPU with a Comfort
Panel. You have to create two projects – one STEP 7 V5.x project and one TIA
project:
1. Create your STEP 7 V5.x project using the T-CPU as usual.

2. Create a TIA project with a device proxy as a CPU from the catalog. A device
proxy is a proxy for a CPU in another TIA or STEP 7 V5.x project.
3. Initialize the device proxy with the data (program blocks, technology objects,
PLC tags, PLC alarms, text lists) of your T-CPU.
4. In TIA Portal, configure the desired operator panel with an HMI connection to
the device proxy and connect the required tags. Instead of re-engineering the
operator panel, WinCC in TIA Portal also allows you to migrate WinCC flexible
projects with version WinCC flexible 2008 SP2 and then replace and modify
the operator panel as desired.
The application description describes the individual IPE steps in detail.
In case of subsequent modifications to your STEP 7 V5.x project, you have to
update the device proxy in TIA Portal. For this purpose, an update function is
available in the context menu of the proxy CPU.

Entry-ID: 21402122, V4.2.2, 06/2014 5
2 Technology Template
2.1 Introduction
2.1 Introduction
2.1.1 The technology template
A technology template is a software object or a code block with a defined interface

that can be easily integrated into other software projects with little overhead and
that performs a precisely defined technological task in these projects.
This technology template helps you easily implement a clear text error display for
error messages of the integrated technology in the technology CPU. All occurring
error texts in German and English are already included in the technology template
and can be additionally supplemented by your own messages.
The technology template was developed for use in conjunction with the technology
CPU, but it can also be used as an error display with any other CPU that supports
the ALARM_S function.
2.1.2 Configuration systems
The technology template was written for the SIMATIC STEP 7 automation
software, version V5.4 or higher. The HMI is configured in WinCC flexible 2008
SP3 integrated in STEP 7 or – in order to use, for example, Comfort Panels – in
TIA Portal. To distinguish between the two configuration systems, the terms
STEP 7 V5.x and TIA Portal will be used in the following sections.
2.1.3 Main contents of this technology template
This technology template discusses the following key issues:

Output of clear text error messages via the ALARM_S function
Expansion of already existing text lists
Text output formatting using the ALARM_S function
Inserting user-defined axis names into the error messages via another text list.
2.1.4 Scope
This technology template does not include a description of …

... the exact processes and sequences on which the ALARM_S function is
based.
... the application and use of technology functions and technology objects with
the technology CPU.
... the programming of the technology CPU in STEP 7 V5.x.
... the configuration of the HMI user interface.
Basic knowledge of these topics is assumed.

Entry-ID: 21402122, V4.2.2, 06/2014 6
2.2 Objective and purpose
2.2 Objective and purpose

2.2.1 Task
When operating the technology CPU, states may occur in which warning and error
messages are output by the technology objects of the integrated technology or the
technology functions in the user program. These messages can only be detected
by targeted monitoring of the technology objects or technology functions and
indicated to the operator.
If a warning or error message occurs, a hexadecimal error code on the technology
object or technology function is used to inform the user of the cause of the error.
However, this makes it difficult to easily and quickly interpret the warning or error
message and locate the cause of the error.
This “Error Messages” technology template helps the user monitor the desired
technology objects and technology functions with regard to warning and error
messages and display, in clear text, the occurring events in STEP 7 V5.x or on a
connected HMI user interface configured in TIA Portal.
Figure 2-1: Detecting and interpreting technology error messages

“Error Messages ”
technology template Error message
Additional
? error information
?
Therefore, the “Error Messages” technology template enables the user to easily
and quickly locate and eliminate the cause of the error.
2.2.2 Advantages
The use of this technology template provides the user with the following
advantages:
Fast program generation

With the aid of the “Error Messages” technology template, monitoring technology
objects and technology functions with regard to warning and error messages can
be implemented easily and quickly. The error codes can be easily displayed in
clear text in STEP 7 V5.x or on the HMI user interface.

Entry-ID: 21402122, V4.2.2, 06/2014 7
2.3 Possible applications
Adaptability
The objects of the “Error Messages” technology template are not protected and can
be modified and expanded by the user if necessary.
It is also possible to supplement user-defined error numbers and error texts in the
supplied text lists and output them using the alarm procedure of the technology
template.
Immediate readiness for service

The objects of the “Error Messages” technology template can be applied to a self-
created user program simply by copying and are ready for service immediately
after calling the function blocks of the “Error Messages” technology template in the
user program.
2.3 Possible applications

2.3.1 Tasks that can be solved with the technology template
The technology template allows you monitor the supported technology objects and
technology functions for error messages and quickly display occurring warning and
error messages.
2.3.2 Properties
The “Error Messages” technology template can be used for clear text display of
error codes of the following technology objects and technology functions:
Table 2-1: Supported technology objects and technology functions

Category Technology object / technology function
Axes Real and virtual drive axes, positioning axes and following
axes.
Electrical and hydraulic axes.
Cams Cams as an interpolation point table and a polynomial
definition.
Output cams Position-based cams, switching output cams and time-based
cams
Measuring inputs Measuring inputs
External encoders External encoders
Technology functions Technology function blocks from S7 Technology
Note The warning and error messages included in the error texts of the technology
template are valid for the technology objects and technology functions of “S7
Technology” up to and including version 4.2.

Entry-ID: 21402122, V4.2.2, 06/2014 8
2.4 Components of the technology template
2.3.3 Restrictions
The following properties were not considered in the implementation of the

technology template.
Only one message can be displayed per technology DB/FB
Only one error or warning message can be displayed for each technology
object and each technology function call.
No archiving of error messages
Occurring error messages are not stored in the “Error Messages” technology
template. If necessary, the messages have to be archived by the used display
system (for example, the “CPU Messages” STEP 7 function).
ALARM_S message system must be supported
The “Error Messages” template can only be used with HMI systems, for
instance WinCC flexible, that support the ALARM_S message system.
2.4 Components of the technology template

In STEP 7 V5.x, the “Error Messages” technology template consists of two function
blocks and three text lists1.
Figure 2-2: Components of the “Error Messages” technology template

“Error Messages” technology template
Function blocks Text lists
FB 510 textlist
„ShowErrFB“ „31xT_ErrorText “
FB 511 textlist
„ShowErrDB“ „31xT_ErrorDescription“
textlist
„Axis_names_userdefined“
The function blocks of the technology template can be used independently of one
another. They are used to monitor warning and error messages on the technology
objects and technology function calls of the integrated technology of the technology
CPU.
All text lists are available in German and English and can be edited as desired. The
“31xT_...” text lists contain the warning and error messages for the hexadecimal
ErrorIDs of the integrated technology and additional info texts in clear text. The
“Axis_names_userdefined” text list contains your user-specific axis names. In
STEP 7 V5.x, the error texts can be displayed using the “CPU Messages” STEP 7
function or integrated into self-created HMI user interfaces.
1
While TIA Portal uses the term “text list”, “text library” is used in STEP 7 V5.x. Both terms
mean the same thing.

Entry-ID: 21402122, V4.2.2, 06/2014 9
2.5 Approved hardware and software

2.5.1 Hardware components
Table 2-2: Hardware components

Component No. Article number Note
CPU 31xT 1 6ES7315-7TJ10-0AB0 CPUs with FW V2.4.1 or
6ES7317-7TK10-0AB0 higher can also be used:
6ES7317-7UL10-0AB0 6ES7315-6TG10-0AB0
6ES7315-6TH13-0AB0
6ES7317-6TJ10-0AB0
6ES7317-6TK13-0AB0
The CPU executes the
user program and the
technological functions.
Micro Memory Card 1 6ES7953-8LP31-0AA0 The S7 program is stored
8 MB on the MMC.
Note To be able to use the “Error Messages” technology template, the following
system function blocks must exist in the controller:
SFC 18 “ALARM_S”: To output ALARM_S messages
SFC 24 “TEST_DB”: To check data blocks
2.5.2 Software components
Standard software components

Table 2-3: Standard software components
Component No. Article number Note
STEP 7 1 6ES7810-4CC10-0YA5 STEP 7 is the basic
Floating License package for all optional
(STEP 7 V5.x) Version: V5.5 SP4 software packages and
used for programming the
SIMATIC.
S7 Technology 1 6ES7864-1CC42-0YA5 Tool for parameterizing
(STEP 7 V5.x) and programming the
Version: V4.2 SP3 technology objects of the
technology CPU.

Entry-ID: 21402122, V4.2.2, 06/2014 10
Software components additionally required for the test program

Table 2-4: Software components additionally required for the test program
Component Article number Note
WinCC flexible 2008 6AV6613-0AA51-3CA5 The packages are needed to
Advanced configure the operator panel in
Engineering Software Version: 2008 SP3 WinCC flexible and run it on your
Floating License PG/PC.
(STEP 7 V5.x)
WinCC flexible 2008 6AV6613-1BA51-3CA0
Runtime, 128 PowerTags
Single License
(STEP 7 V5.x)
SIMATIC STEP 7 6ES7822-1AA03-0YA5 The packages are needed to
Professional V13 create a proxy CPU as a
Floating License communication partner for the
(TIA Portal) HMI device (e.g., Comfort Panel)
Update 2 Free download \20\ also configured in TIA Portal.
for STEP 7 V13
(TIA Portal)
SIMATIC WinCC 6AV2101-0AA03-0Ax5
Comfort V13 x=A: As a DVD
Floating License x=H: As a download
(TIA Portal)
Sample files and projects

The following list contains all files and archives that are used in this technology
template:
Table 2-5: Files and STEP 7 archives of the technology template
Component Note
21402122_CPU31xT_error_meassage_ This STEP 7 V5.x archive contains only the
CODE_v422.zip blocks associated with the technology
template for integration into a user program.
21402122_CPU31xT_error_meassage_ This STEP 7 V5.x archive contains both the
example_CODE_v422.zip blocks associated with the technology
template for integration into a user program
and a test program to check the
parameterization options and functions of the
technology template. A CPU 315T is
configured in the project.
21402122_CPU31xT_error_meassage_ This TIA Portal archive contains the HMI
example_HMI_v422.zip configuration of a TP900 Comfort operator
panel to test the application example, the
communication configuration for the panel
and a proxy CPU as a proxy for the T-CPU.
21402122_CPU31xT_error_meassage_ This document.
DOKU_v422_en.pdf

Entry-ID: 21402122, V4.2.2, 06/2014 11
3 Basics
3.1 Functional principle of the technology template
3 Basics
3.1 Functional principle of the technology template
The figure below shows the functional principle of the “Error Messages” technology
template:
Figure 3-1: Functional principle of the “Error Messages” technology template
STEP 7 V5.x
S7-Anwenderprogramm
S7 user program Textliste
textlist
ErrorID
ErrorID == Fehlertext
error text
…
Text
ID
Technology
Technologie
FB
ErrorID + Status
„Error
Technology
Messages“ Text
Technology
Technologie
S7-Anwenderprogramm
S7-Anwenderprogramm
technology
Template
DB
ErrorID „Fehleranzeige“
template
…
WinCC
(TIA)
The function blocks of the “Error Messages” technology template monitor the
technology function calls (technology FB) or technology objects (technology DB)
of the integrated technology. If an error or warning occurs, the hexadecimal
ErrorID is transferred to the ALARM_S message system via the function block.
The ALARM_S message system combines the ErrorID with the error text stored
in the text list. This error text can then be displayed together with the ErrorID.
To display the warning and error messages during runtime, the following media are
available:
“CPU Messages” function in STEP 7 (STEP 7 V5.x)
“Alarm View” and “Alarm Window” objects in the HMI configuration in WinCC
2
flexible (STEP 7 V5.x)
“Alarm View” and “Alarm Window” objects in the HMI configuration in
3
WinCC (TIA Portal)
2
In the supplied application example, the warning and error messages are displayed in the
alarm view of WinCC flexible Runtime on the PG/PC.
3
In the supplied application example, the warning and error messages are displayed in the
alarm view of a TP900 Comfort Panel simulated on the PG/PC.

Entry-ID: 21402122, V4.2.2, 06/2014 12
3 Basics
3.2 Monitoring a technology object
3.2 Monitoring a technology object

A technology object is monitored with the aid of the FB 511 “ShowErrDB” function
block of the technology template.
Figure 3-2: Monitoring a technology object
S7 user program
Technology TDB_Nr
DB
FB 511
ErrorID Error code „ShowErrDB“
ErrorID
To monitor a technology object, the “ShowErrDB” function block of the template

has to be called once during an OB1 cycle. Referencing to the technology object is
performed using the number of the technology data block assigned to the
technology object.
The function block independently monitors the location for the error code (ErrorID)
included in the technology DB. If the technology object enters an error code in this
location, this code is detected via FB 511 “ShowErrDB” and displayed.
3.3 Monitoring a technology function

A technology function block is monitored with the aid of the FB 510 “ShowErrFB”
function block of the “Error Messages” technology template.
Figure 3-3: Monitoring a technology function call
S7 user program
Technology
FB
Error Status Error
ErrorID Error code ErrorID

FB 510
„ShowErrFB“
To monitor a technology function call, a “ShowErrFB” function block of the

technology template must be assigned to each technology FB of the technology
CPU that is to be monitored. The output signals for the occurrence of an error and
for the error code (ErrorID) are transferred to the function block of the template.
If a pending error is detected by FB 510 “ShowErrFB” via the Error signal, the
error code communicated in the ErrorID is evaluated and displayed.

Entry-ID: 21402122, V4.2.2, 06/2014 13
4 Functional Mechanisms
4.1 The ALARM_S message function
4.1 The ALARM_S message function
The generation of messages in this technology template is implemented using the
SFC 18 “ALARM_S” system function.
In the user program, this system function has to be called from a function block that
features an input for transferring the EventID. Special attributes must be assigned
to this input.
In the STEP 7 program, the EventID designates the message location for the
ALARM_S message function. When integrating the function block into the user
program in which the SFC 18 “ALARM_S” system function is called, STEP 7 –
due to the system attributes – automatically enters the EventID at the block input.
Table 4-1: Assignment of the EventID by STEP 7

STL FBD
FB 510
“ShowErrFB”
FB 511
“ShowErrDB”
To assign the necessary system attributes to the EventID input variable of a newly
created function block so that it can be used in conjunction with the SFC 18
“ALARM_S” system function, proceed as follows (these attributes have already
been set at the FB510 and FB511 blocks of the technology template):
Table 4-2: Definition of the system attributes

No. Action Remark
1. Open the function block and in the
interface table, select the EventID input
variable.

Entry-ID: 21402122, V4.2.2, 06/2014 14
4.2 Text lists
No. Action Remark

2. Use the context menu of this variable
to open the object properties.
3. In the Attribute section of the object

properties, set the following two
attributes:
S7_a_type = alarm_s
S7_server = alarm_archiv
Note:
The attributes and values to be set can
be taken from the drop-down lists of
the setting fields.
Note The use of multi-instance data blocks for the function blocks in which SFC 18
“ALARM_S” is called is not possible since in this case the EventID cannot be
automatically assigned by STEP 7 and therefore no reference to this block is
possible in the ALARM_S message system.
4.2 Text lists

The “Error Messages” technology template includes two text lists for clear text
display of error codes:
“31xT_ErrorText” text list
This list contains the error texts for the error code.
“31xT_ErrorDescription” text list
This list contains the related error information for the error code and notes on
locating and eliminating the cause of the error.
“Axis_names_userdefined” text list
This list contains the user-defined axis names that appear in the message
texts. For the two axes of the supplied example, this template contains axis
names (“slide A” and “slide B”) that can be replaced by the user. The text list
can be expanded.
By default, the “31xT_...” text lists contain all the error texts and related error
information for S7 Technology version 4.2 in German and English.

Entry-ID: 21402122, V4.2.2, 06/2014 15
4.3 Associated values of the ALARM_S message function
4.3 Associated values of the ALARM_S message function

With the aid of SFC 18 “ALARM_S”, one associated value from the user program
with a maximum length of 12 bytes can be transferred to the ALARM_S message
system.
Within the associated value, however, it is possible to transfer multiple process
values up to an overall length of 12 bytes as an array (ARRAY) or structure
(STRUCT).
Figure 4-1: Transfer of multiple process values in the associated value of SFC 18
“ALARM_S”
The process values transferred in this way can then be displayed separately within
the alarm message of the ALARM_S message system. The process values are
split via the formatting of the ALARM_S message texts.
4.4 Configuring Report system error

Using default values
The user must configure how system errors are reported, which blocks should be
used for this purpose, which reaction should be triggered, etc. As the application,
except for one setting, uses the default values, there is no need to provide a
detailed description of the message configuration at this point. For more
information, refer to the SIMATIC Manager online help for the “Report system
error” function, which provides valuable information.
Optimized creation of messages

This setting significantly reduces the creation time and the number of message
instances. To ensure that a WinCC flexible configuration can be compiled without
errors, uncheck Optimized creation of messages, which is checked by default.
Proceed as follows:

Entry-ID: 21402122, V4.2.2, 06/2014 16
4.4 Configuring Report system error
Table 4-3: Unchecking Optimized creation of messages

No. Action
1. Open the hardware configuration and select the CPU. Select Options, Report
System Error.
2. Open the Messages tab.

Uncheck Optimized creation of messages and select Generate to close the

window. Then save and compile the hardware configuration.
When configuring your HMI in TIA Portal with WinCC, you can create messages in
an optimized way.

Entry-ID: 21402122, V4.2.2, 06/2014 17
4.5 Formatting the ALARM_S message texts

4.5.1 Setting the special object properties
The output format of the text messages is defined via special object properties of
the function block in which the call of the SFC 18 “ALARM_S” system function is
made.
Table 4-4: Setting the output format of the text messages
No. Action Remark
1. In the SIMATIC Manager, use the context menu of the function block to call the
Message... function in Special Object Properties.
2. Enter the desired formatting for the message text (Message text) and the
additional information on the error message (Info text) to provide a more detailed
description of the cause of the error.
Use More>> to show an advanced display where you can also create multi-line
texts by inserting line breaks (return).
For the input syntax for formatting the message texts, please refer to the next
section.

Entry-ID: 21402122, V4.2.2, 06/2014 18
4.5.2 Formatting the output format for the text messages
The text messages to be output can be taken from a text list or entered directly in
the text line of the Message Configuration window. In the technology template, for
example, the word “code” was put in front of the output of the error number.
Process values can also be output in the text message directly from the user
program. In the example, this was done with the ErrorID.
Text message format
The output of a text block from a text list or a process value from the user program
must have the following format:
@<Number of the process value><element type>%<format>@
Process value number
Via the number of the process value, the respective process value is selected for
display from the associated value of the SFC 18 “ALARM_S” function.
Figure 4-2: Selection of the process value

Process value 1
Process value 2
Process value 3
Associated value of
SFC 18
Element type
The element type defines the length of the respective process value within the
associated value. The element type must be suitable for the transferred process
value so that it can be processed consistently in the message system.
Table 4-5: Possible element types of the process values

Element type Data type Note
Y BYTE
W WORD
X DWORD The total of the byte lengths of the individual
I INT data types of the process values must not
exceed the maximum length of the associated
D DINT value of the SFC 18 “ALARM_S” function of
B BOOL 12 bytes.
C CHAR
R REAL

Entry-ID: 21402122, V4.2.2, 06/2014 19
Figure 4-3: Element types of the process values within the associated value
3 x WORD = 3 x 2 bytes = 6 bytes
Associated value of SFC 18
In the above figure, the three transferred process values of the WORD type occupy
6 bytes of the possible 12 bytes of the associated value of SFC 18 “ALARM_S”.
Format
The format defines the output of the process value within the message text.
Likewise, the process value can be interpreted as an index of a text block in a text
list. In this case, the text block is output in the message text instead of the process
value.
Table 4-6: Possible formats for value output in the message text
Format Description Example
iX Hexadecimal number with i digits 4X
iu Unsigned decimal number with i digits 4u
id Signed decimal number with i digits 4d
ib Binary number with i digits 4b
i.yf Signed fixed-point number with y decimal 4.1f
positions and i total number of digits
is String with i characters 4s
t#[text list] Text block from a text list t#31xT_ErrorText

Entry-ID: 21402122, V4.2.2, 06/2014 20
Figure 4-4: Formats of the process values for the text output
Message text:
@1I%t#Axis_names_userdefined@ - Code @2W%4X@ : @2W%t#317T_ErrorText@
Output of the axis number Output of the ErrorID Output of the ErrorID
as text from the as a 4-digit as text from the
“Axis_names_userdefined” hexadecimal number “31xT_ErrorText”
text list text list
NOTICE Please note that the format identifier is case sensitive.

For example, in contrast to a WinCC flexible HMI configuration, the axis name
“Axis @1I%3U@” (in contrast to “Axis @1I%3u@”) cannot be displayed for a
WinCC configuration in TIA Portal and error messages will be displayed when
compiling the operator panel.

Entry-ID: 21402122, V4.2.2, 06/2014 21
Completing the message configuration

To complete the message configuration, compile all blocks and check their
consistency.
Table 4-7: Compiling and checking the consistency
No. Action
1. From the Blocks context menu, select the Check Block Consistency… menu
item.
2. Select Compile All.

Entry-ID: 21402122, V4.2.2, 06/2014 22
4.6 Change language
4.6 Change language

4.6.1 Language versions of the text lists
The error and warning messages for clear text output are available in the supplied
text lists in the following languages:
German
English (USA)
To output the clear texts, the language can be changed in STEP 7 or – if change
language was configured – on the HMI user interface.
4.6.2 Change language in STEP 7
In order to implement a change language feature for the error display, the message
configuration must be made for every single language as described in Chapter
4.5.2. To change the language – for both the multilingual message configuration
and the display of CPU messages using the CPU Messages function (see Chapter
7.3) – proceed as follows:
Table 4-8: Change language in STEP 7

No. Action
1. In STEP 7, in offline mode, select Options, open the Manage Multilingual Texts
drop-down list and select the Change Language… function.
2. Select the desired language and confirm the selection with OK.

Entry-ID: 21402122, V4.2.2, 06/2014 23
4.6 Change language
4.6.3 Change language of the HMI user interface
In WinCC flexible (STEP 7 V5.x) or WinCC V13 (TIA Portal), the change language
feature needs to be configured separately. At this point, only the most important
steps will be briefly described as an example. For detailed information, please refer
to the appropriate documentation on the development systems.
WinCC flexible (STEP 7 V5.x)

In Language Settings, Project Languages, select the desired languages
from the list.
In Device Settings and Languages and Fonts, define the order of the
selected languages.
In Communication and Tags, define an integer tag for the display language
change. This tag is an internal tag; that is why “<internal Tag>” is entered as a
connection. In the tag properties in Events and Change Value, select the
SetLanguage function with the assignment of the DisplayLanguage tag.
Set a button on the HMI user interface that influences the integer tag for the
display language. The language is displayed whose ordinal number in the
defined order corresponds to the value of the tag for the display language.
WinCC V13 (TIA Portal)

In Language & resources, Project languages, select the desired languages
from the list.

In Runtime settings, Language & font, define the order of the selected
languages.
Configure a button and click to run the “SetLanguage” function with the
selected “Toggle” entered as the language. Each time you click the button, the
display language changes in the order defined above.
Note In the supplied sample projects, change language using buttons is implemented
in both WinCC flexible and WinCC (TIA Portal).

Entry-ID: 21402122, V4.2.2, 06/2014 24
5 Installation
5.1 Preparations
5 Installation
5.1 Preparations
5.1.1 Retrieving the technology template
The “Error Messages” technology template is supplied as a STEP 7 archive

(STEP 7 V5.x). To be able to use the technology template, this archive first has to
be retrieved in the SIMATIC Manager.
Table 5-1: Retrieving the technology template

No. Action Remark
1. Start the STEP 7 programming
environment and in the File section,
select Retrieve…
Select the STEP 7 archive of the

template.
2. Select the destination directory for the

template.
In most cases, the destination
suggested by STEP 7 can be used.
Use the OK button to start retrieving.
3. After successfully retrieving the objects,

open the technology template in STEP
7.
Select the Yes button.
The “Error Messages” technology template includes an S7 program folder that

contains all the necessary elements for the use of the technology template.
Figure 5-1: Contents of the technology template

Entry-ID: 21402122, V4.2.2, 06/2014 25
5 Installation
5.2 Integration into your application

For easy and quick transfer of the “Error Messages” technology template to your
STEP 7 project, you should proceed as described below.
5.2.1 Transferring the complete S7 program folder
Table 5-2: Transferring the S7 program folder

No. Action
1. In STEP 7, select the S7 program
folder by clicking it.
In the Edit section, select the Copy
function to copy the program folder to
the clipboard.
2. In STEP 7, create a new project or

open an existing STEP 7 project into
which you want to integrate the
template.
3. Depending on the default setting, a

Message Number Assignment
Selection window appears when
creating the CPU in a new project.
Select Assign CPU-oriented unique
message numbers. Assign CPU-
oriented unique message numbers
must also be selected for existing
projects. For information on changing
the setting, please refer to the STEP 7
online help.
4. Insert the copied S7 program folder

with the elements of the template into
the project.
Select the root node of the S7 project
by clicking it (first item in the project
structure overview) and in the Edit
section, select the Paste function.

Entry-ID: 21402122, V4.2.2, 06/2014 26
5 Installation
5.2.2 Integrating the technology template into your STEP 7 project
Table 5-3: Integrating the technology template into your project

No. Action Remark
1. Transfer the text libraries:
Select the Text libraries folder and use
drag and drop to copy this folder to your
S7 program folder.
2. Transfer the function blocks:

Select all blocks that are available in the
template in the Blocks folder and use
drag and drop to copy these blocks to
the block folder of your project.
2
1
5.2.3 Calling the function blocks
Once you have transferred all the blocks and text libraries supplied with the
technology template to your STEP 7 project, you can use the functions provided by
the technology template in your user program.
The calls of the function blocks of the “Error Messages” template in the STL and
FBD programming languages are shown below as examples:
Table 5-4: Calling the function blocks

STL FBD
FB 510
“ShowErrFB”
FB 511
“ShowErrDB”
When calling the function blocks and after assigning the instance data blocks,
STEP 7 automatically assigns a CPU-wide unique number to each block on the
EventID parameter.

Entry-ID: 21402122, V4.2.2, 06/2014 27
5 Installation
5.3 Message configuration in WinCC flexible (STEP 7 V5.x)
Note The CPU-wide unique number automatically assigned by STEP 7 on the

EventID parameter must not be changed by the user!
5.2.4 Assigning the instance data blocks
A separate instance data block has to be assigned to each called function block of
the “Error Messages” template.
The use of multi-instance data blocks is not possible when using the function
blocks from the “Error Messages” template. In this case, the EventID is not
automatically assigned by STEP 7 and therefore a reference to the block in the
ALARM_S message system is not possible.

To implement a message output via the HMI user interface, WinCC flexible must
be integrated into the respective STEP 7 V5.x project. Furthermore, you have to
set up and configure the message output via ALARM_S in WinCC flexible.
Table 5-5: Message configuration in WinCC flexible

No. Action
1. Make sure that an active communication connection between the HMI and the CPU
has already been configured.

Entry-ID: 21402122, V4.2.2, 06/2014 28
5 Installation
No. Action
2. Configure an Alarm View or Alarm
Window.
3. In its properties in General, (additionally) select the S7 Alarm alarm class by

checking the appropriate check box.

Entry-ID: 21402122, V4.2.2, 06/2014 29
5 Installation
No. Action
4. Activate the ALARM_S alarm procedure in
Alarm Management > Settings > Alarm Settings > Alarm procedures. Select All
display classes.

Entry-ID: 21402122, V4.2.2, 06/2014 30
5 Installation
5.4 Message configuration in WinCC (TIA Portal)
No. Action
5. Once your message configuration for the CPU is complete and all blocks have been
checked for consistency and compiled on the CPU, delete all temporary files in
WinCC flexible and regenerate the HMI project.

To implement a message output via the HMI user interface, the HMI user interfaces
must be configured in the project that contains the text libraries to be integrated.
Use the IPE (Inter Project Engineering) method to set up an HMI project in which
the operator panel is given access to the data of a CPU included in another V5.x or
TIA project. In your HMI project to be created in TIA Portal, create a proxy CPU – a
so-called proxy device – that is initialized once with the data of the original CPU
and can be updated as often as desired.
A message output via ALARM_S must be set up and configured in the HMI user
interface.

Entry-ID: 21402122, V4.2.2, 06/2014 31
5 Installation
5.4.1 Reconfiguring the operator panel
Table 5-6: Reconfiguring the operator panel

No. Action
1. Make sure that the following software/data is on your PG/PC:
STEP 7 V5.x (complete development environment to configure your T-CPU)
Your STEP 7 V5.x project you want to visualize
TIA Portal with STEP 7 Professional V13 and at least WinCC Comfort V13
2. Create a new TIA project for the HMI configuration.
3. Insert a proxy CPU.
1
If necessary, change the default name PLC_Proxy, for example, to CPU315T.

However, this is not necessary.

Entry-ID: 21402122, V4.2.2, 06/2014 32
5 Installation
No. Action
4. Initialize the device proxy.
You are prompted to open the device proxy data source, i.e., the STEP 7 V5.x
project that contains your T-CPU. Enter the name of the appropriate s7p file. Make
sure that the project is executable (consistent) and not open.
5. Apply all transferred data.

Entry-ID: 21402122, V4.2.2, 06/2014 33
5 Installation
No. Action
6. Insert the desired operator panel by dragging the mouse.
7. Select the HMI connection and establish the communication connection between
the proxy CPU and the operator panel by connecting the Ethernet ports with the
mouse.
8. In the desired HMI screen, configure an

Alarm View or Alarm Window.

Entry-ID: 21402122, V4.2.2, 06/2014 34
5 Installation
No. Action
9. In its properties in General, check the appropriate check box to (additionally) select
the alarm class that was transferred from the T-CPU to the device proxy and stored
in the project navigation in Shared data > Alarm classes. In the supplied example,
this is the Alarm - high4 alarm class.
10. The ALARM_S alarm procedure must be on. This is the case by default. The setting
is made in Runtime settings > Alarms. No user action is required at this point.
4
In STEP 7 V5.x, the Alarm – high alarm class is selected from a drop-down list in HW Config
under the CPU in the alarm attributes section: Options > Report System Error… >
Messages. The default value is Alarm – high. For more information, please refer to the
appropriate manuals.

Entry-ID: 21402122, V4.2.2, 06/2014 35
5 Installation
No. Action
11. Compile the complete HMI project.
2
12. If the HMI configuration has been compiled without errors, save it and start the
simulation or download the configuration to the operator panel.
2 3 3
Load HMI panel Start simulatiom
5.4.2 Updating the operator panel configuration
If you subsequently make changes to your STEP 7 V5.x project, you have to
update the proxy CPU data in your TIA project and then once again compile the
complete HMI configuration:

Entry-ID: 21402122, V4.2.2, 06/2014 36
5 Installation
Table 5-7: Updating the operator panel configuration

No. Action
1. Update the device proxy.
2
You are prompted to open the device proxy data source, i.e., the STEP 7 V5.x
project that contains your T-CPU. Enter the name of the appropriate s7p file.
Make sure that the project is executable (consistent) and not open.
2. Apply all transferred data.
3. If the changes in the STEP 7 V5.x project also require changes in the operator
panel configuration, for example a new tag you want to visualize, make these
modifications now.
4. Compile the complete HMI project; if it has been compiled without errors, save
the HMI configuration and start the simulation or download the configuration to
your operator panel (identical to steps 0 and 0 from Table 5-6).

Entry-ID: 21402122, V4.2.2, 06/2014 37
5 Installation
5.4.3 Migrating the operator panel from STEP 7 V5.x
This method is particularly suitable if you have an existing STEP 7 V5.x project with
an integrated HMI configuration and want to replace the operator panel, for
example, with a Comfort Panel that can only be configured in TIA Portal.
Figure 5-2: Migrating the operator panel from STEP 7 V5.x
Table 5-8: Migrating the operator panel from STEP 7 V5.x

No. Action
1. Open WinCC flexible RT within your STEP 7 V5.x project.
2. Use Project > Copy from STEP 7… to copy the entire HMI configuration of the
WinCC flexible project to be migrated to a separate folder on your hard drive you
have newly created if necessary.
3. Close WinCC flexible RT and STEP 7 V5.x.
4. Start TIA Portal V13.
5. Select Project > Migrate project….
6. In the window that appears, enter the *.hmi file of the WinCC flexible project you
have copied from STEP 7 V5.x in “Source Path”.
Then TIA Portal enters default names (based on the project to be migrated) for
the target as the TIA project name and target path, both of which can be
changed.
7. In Options > Settings > Visualization > Resize screen, define how the screens
should be resized when replacing the operator panel.
8. Go to the Device configuration of the migrated operator panel and use drag
and drop to replace it with the device of your choice from the hardware catalog.

Entry-ID: 21402122, V4.2.2, 06/2014 38
5 Installation
No. Action
9. You may have to post-edit the screens (in particular, if the resolution and/or
screen size change due to the device replacement).
10. Insert a proxy CPU into the project as described in steps 3, 4 and 5 in Table 5-6
and initialize it with the data from the STEP 7 V5.x project.
11. As described in step 7 Fehler! Verweisquelle konnte nicht gefunden
werden.Fehler! Verweisquelle konnte nicht gefunden werden.in Table 5-6,
establish an HMI connection between the operator panel and the proxy CPU.
12. For the new operator panel, change all tags connected to the CPU to the newly
created connection in the tag table, HMI tags > Show all tags.
13. In Connections, delete the old connection from the migration for the new
operator panel.
14. In the Alarm View/Alarm Window properties, General, follow step 9 in Table 5-6
to (additionally) select the alarm class transferred from the CPU in the STEP 7
V5.x project to the device proxy.
15. Compile the complete HMI project as described in step 3411 in Table 5-6.
5.4.4 Storing the CPU messages in TIA Portal
In TIA Portal, the message texts configured in STEP 7 V5.x, including the formats
for the library texts, can be found in TIA Portal in the set editing language under the
operator panel in
HMI alarms > Controller alarms.
Figure 5-3: Controller alarms
On a language-related basis, the message texts are stored in Languages &

resources > Project texts.
Figure 5-4: Project texts

Entry-ID: 21402122, V4.2.2, 06/2014 39
5 Installation
The individual text lists are under the proxy CPU and cannot be accessed by the
user.
NOTICE In TIA Portal, do not change any controller alarm texts or formats of a
proxy CPU to avoid inconsistencies with the STEP 7 V5.x project.
If necessary, change the message texts in the STEP 7 V5.x project and then
update the proxy CPU in TIA Portal.
2

Entry-ID: 21402122, V4.2.2, 06/2014 40
6 Startup
6.1 Call environment
6 Startup
6.1 Call environment
The blocks of the “Error Messages” technology template have to be called
cyclically in the user program. The call of the blocks can be made directly in an OB
or within a cyclically processed FB.
Figure 6-1: Call environment of the technology template

Controller Integrated
technology
User block
PLCopen
FB
Technology
objects
Cyclic OB
(e.g. OB1,
OB35 ...) FB 510
„ShowErrFB“
FB 511 Technology Technology

„ShowErrDB“ DB objects
Axes
The FB 510 “ShowErrFB” block should be programmed in the respective user

block directly after the technology function block to be monitored. This ensures that
the user program can be clearly designed and possibly occurring warning and error
messages are transferred directly after calling the technology function block.
However, monitoring a technology object via the technology DB with the aid of
FB 511 “ShowErrDB” should be programmed at the end of the cyclic OB. The
technology object has been influenced via the technology function calls during the
OB cycle and the current technology object status can be checked by the block of
the “Error Messages” technology template.
The individual instances of FB 511 “ShowErrDB” can be called directly in the cyclic
OB or within a cyclically called FB that is processed at the end of the OB cycle.
6.2 Interfaces
6.2.1 Interface of FB 510 “ShowErrFB”
To monitor the technology function calls by the FB 510 “ShowErrFB” function block,
the following interfaces are available at the block:
EventID FB_ErrorID
Error
ErrorID FB 510
Axis „ShowErrFB“
AdditionalData

Entry-ID: 21402122, V4.2.2, 06/2014 41
6 Startup
6.2 Interfaces
Table 6-1: Interfaces of FB 510 “ShowErrFB”

Parameter Data type Initial value Description
Input parameter
EventID DWORD DW#16#0 The EventID is used to assign the
error message by the ALARM_S
message system. It is
automatically assigned by STEP 7
when integrating the block and
must not be changed by the user.
Error BOOL False A pending error is signaled via this
input.
ErrorID WORD W#16#0 The ErrorID contains the error
code and forms the reference to
the error text to be output.
If the Error input has the value
True, the ErrorID is transferred to
the message system and the error
message is displayed in clear text.
Axis INT 0 Number of the axis DB.
In the “Axis_names_userdefined”
text list, this number also
represents the index for the user-
defined axis name.

AdditionalData WORD W#16#0 This additional data is transferred
as a third process value in the
associated value and can be
displayed in the message text.
However, the third process value
is not yet configured in the
message text!
Output parameter
FB_ErrorID INT 0 If an error occurs in the block while
processing the error output, an
error code is output.
6.2.2 Interface of FB 511 “ShowErrDB”
To monitor the technology objects by the FB 511 “ShowErrDB” function block, the
following interfaces are available at the block:
EventID FB_ErrorID
TDB_Nr
IgnoreWarnings FB 511
„ShowErrDB“
Table 6-2: Interfaces of FB 511 “ShowErrDB”

Input parameter
EventID DWORD DW#16#0 The EventID is used to assign the
error message by the ALARM_S
message system. It is
automatically assigned by STEP 7

Entry-ID: 21402122, V4.2.2, 06/2014 42
6 Startup
6.3 Warning messages and error messages

when integrating the block and
must not be changed by the user.
TDB_Nr INT 0 This is where the data block
number of the technology object to
be monitored or the technology
data block assigned to it must be
specified as a reference.
In the “Axis_names_userdefined”
text list, the number entered here
represents the index for the user-
defined axis name.
IgnoreWarnings BOOL False If this input is set to True, only
error messages of the technology
objects are output. Warning
messages are suppressed.
Output parameter
FB_ErrorID INT 0 If an error occurs in the block while
processing the error output, this
error is signaled here via the error
code.

6.3.1 Signaling error events in the “Error Messages” template
If an error occurs when processing the error codes in the “Error Messages”
template, this error is displayed at the FB_ErrorID output of the relevant function
block via an error code.

Entry-ID: 21402122, V4.2.2, 06/2014 43
6 Startup
6.3.2 Warning and error codes at the “ErrorID” output
The Ref. column indicates the block-internal error source of the function block of
the “Error Messages” technology template.
Table 6-3: Error codes of the “Error Messages” technology template

FB_ Error Ref. Remark
ErrorID
0000 No error ---
0001 Associated value too long / SFC 18 The message is sent
no access to user memory
0002 Last free message SFC 18
acknowledgement memory
has been used
807F Internal error FB 511 Address of the DB data is outside the
permitted range
8081 EventID non-permissible SFC 18 The specified EventID is outside the
permitted range
8082 Resources exhausted SFC 18 Loss of messages since the CPU
has no more resources for
generating block-related messages
by SFCs.
8083 Signal overflow SFC 18 Loss of messages since the same
signal change already exists but
could not yet be sent (signal
overflow).
8084 No signal change detected SFC 18 The signal triggering the message
has the same value for the current
and previous SFC 18 call.
8085 EventID invalid SFC 18 No logon for specified EventID.
8086 Double SFC call SFC 18 An SFC call for the specified EventID
is already being processed in a
“lower priority” priority class.
8087 Signal with value 0 SFC 18 When SFC 18 was first called, the
transferred signal triggering the message had
the value 0.
8088 Double EventID SFC 18 The specified EventID is already
being used by another system
resource.
80A1 Error in DB number SFC 24 The specified DB number has the
value 0 or exceeds the maximum DB
number possible for the CPU.
80B1 DB does not exist SFC 24 The DB with the specified number
does not exist on the CPU.
80B2 Unlinked DB SFC 24 The DB was generated using the
keyword UNLINKED.
817F Internal error FB 511 Incorrect data block type detected or
data block type is not supported by
the template.

Entry-ID: 21402122, V4.2.2, 06/2014 44
7 Operation
7.1 Monitoring with FB 510 “ShowErrFB”
7 Operation
7.1 Monitoring with FB 510 “ShowErrFB”
To monitor technology function calls by the FB 510 “ShowErrFB” block, the FB 510
block has to be programmed after each technology function call to be monitored.
When using this block, it has to be carefully checked which technology function
calls are to be monitored since a separate instance data block must be assigned to
each block call of FB 510 “ShowErrFB”.
Use during the development phase

To save memory and avoid unnecessary CPU load, FB 510 “ShowErrFB” should
be used mainly during the development phase of a program.
Parameterization and call errors are primarily output on the technology function
calls so that the use of this block should be limited to technology function calls with
changing parameterization.
Monitoring of an MC_CamClear in the STL and FBD programming languages is
shown below as an example.
Data transfer between the two blocks takes place via the temporary variables
TempError and TempErrorID.
Table 7-1: Integration of FB 510 “ShowErrFB”

STL FBD

Entry-ID: 21402122, V4.2.2, 06/2014 45
7 Operation
7.2 Monitoring with FB 511 “ShowErrDB”
Note In the FBD/LAD programming language, the technology function call and the call
of the FB 510 block must be made in different networks.
For the call of the FB 510 block, the best network to be selected is the one after
the technology function call.
The STL programming language does not require this separation into different
networks.
7.2 Monitoring with FB 511 “ShowErrDB”

To monitor technology objects by FB 511 “ShowErrDB”, one function block call has
to be programmed for each technology object to be monitored.
It is recommended that the function block calls for monitoring the technology
objects be integrated into a separate network at the end of OB1.
Monitoring of technology objects 2 and 5 in the STL and FBD programming
languages is shown below as an example.
Table 7-2: Integration of FB 511 “ShowErrDB”

STL FBD
A separate FB 511 “ShowErrDB” with an assigned instance data block is

programmed for each technology object. Via the TDB_Nr input, FB 511
“ShowErrDB” is informed of the number of the technology object to be monitored.
This number corresponds to the number of the technology data block of the
respective technology object.

Entry-ID: 21402122, V4.2.2, 06/2014 46
7 Operation
7.3 Error text output using “CPU Messages”
Via the IgnoreWarnings input, the “True” or “False” status can be used to
additionally inform the function block of whether (“False”) or not (“True”) warning
messages of the technology object are to be output.

Using the “CPU Messages” STEP 7 function, the error messages displayed by the
function blocks of the technology template can be displayed in the SIMATIC
Manager without any additional configuration and programming overhead.
7.3.1 Calling the “CPU Messages” function
When the CPU is selected, this function can be called in the SIMATIC Manager in
online mode by selecting PLC > CPU Messages...
Figure 7-1: Opening the “CPU Messages” window
2
To display the error texts from the “Error Messages” technology template, the
“A” column of the CPU on which the “Error Messages” template is executed must
be checked in the header of the window of the “CPU Messages” function. The error
messages received from the “Error Messages” template will then be displayed in
the window of the “CPU Messages” function.

Entry-ID: 21402122, V4.2.2, 06/2014 47
7 Operation
Figure 7-2: “CPU Messages” STEP 7 function
only if checked
Display of error and
warning messages
Display of related information to

locate and eliminate the error
7.3.2 Settings of the “CPU Messages” function
In the window of the “CPU Messages” function, the following settings can be made
via the menu in the View section:
Place on Top: When new error messages arrive or error messages are
deleted from the display, the “CPU Messages” window is automatically placed
on top or a blinking signal in the taskbar indicates this status.
Leave in the Background: The “CPU Messages” function receives the
incoming error messages and archives them, but does not indicate incoming
and outgoing messages.
Ignore Messages: The “CPU Messages” function does not receive messages
from the “Error Messages” technology template, it does not display and archive
them.
In the Edit section, the archive of the “CPU Messages” function can be emptied
using the Empty Archive function. In File, the archive entries can be saved using
the Export Archive... function.
The Display Info Text function in the View section allows you to activate the
window where the related error information is displayed. Clicking the desired error
message displays the related error information in this window.
7.3.3 Change language for the “CPU Messages” function
To change the language for this function, switch to offline mode. Proceed as
described in Chapter 4.6.2.

Entry-ID: 21402122, V4.2.2, 06/2014 48
7 Operation
7.4 Error text output on the operator panel
7.4 Error text output on the operator panel

On the operator panel, the message texts are displayed in an Alarm View or
Alarm Window. The configuration in WinCC flexible (STEP 7 V5.x) or WinCC (TIA
Portal) is described in Chapters 5.3 and 5.4.
7.5 Test projects for the technology template

For the first tests before integrating the technology template into a user program,
two test projects are available that offer the option to extensively test the display of
error messages of the technology objects and technology functions using a
convenient HMI user interface.
STEP 7 V5.x project with a CPU 315T and WinCC flexible RT (integrated)
TIA V13 project with a proxy CPU and TP900 Comfort Panel
No real machine axes are required for the test projects. The program is
immediately executable on a technology CPU and the necessary axes are
simulated for the test as virtual axes in the controller.
NOTICE The test projects are used to familiarize with the principle of operation and
the reactions of the technology template.

These projects are not intended for use in real machines and therefore not
released.
The test projects are available as separate STEP 7 archives with all required
technology objects and STEP 7 blocks.
7.5.1 Requirements for running the test projects
To start up the application examples, the following requirements must be met:

PG/PC interface
– In the Control Panel, the interface of your PG/PC is set to the interface
card used.
– The PG/PC is in the same subnet as the controller (192.168.0.xxx).
– The CPU is connected to the PG/PC via an Ethernet cable.
All blocks and system data of the controller in the STEP 7 V5.x test project
were correctly downloaded to the technology CPU.
The CPU is in RUN.

Entry-ID: 21402122, V4.2.2, 06/2014 49
7 Operation
7.5.2 The HMI user interfaces of the test projects
The design of the user interfaces of WinCC flexible RT and TP900 differs slightly
due to the different screen formats. The following explanations use the screenshots
of WinCC flexible RT.
The button for displaying the extended error information was configured in the
alarm view of the TP900. WinCC flexible RT cannot access the text list on which
the extended error information is based so that the display is unnecessary in this
case.
Figure 7-3: HMI user interface of WinCC flexible RT


Entry-ID: 21402122, V4.2.2, 06/2014 50
7 Operation
Figure 7-4: HMI user interface of the TP900
Button to display the extended

error information
With the aid of the HMI user interface, two virtual axes can be controlled using jog
buttons. It is also possible to transmit a positioning job via which the appropriate
axis is automatically moved to the selected position.
The two axes in the test project are displayed on the HMI user interface. The axes
can be enabled and reset below the respective drive motor with the buttons
available in this section. The axis enable is signaled by the green display next to
the respective motor. The position and velocity of the axis are displayed above the
motor.
The enabled software limit switches in the plus and minus direction are displayed
at the lower end of the axis. They can be approached using the jog buttons of the
axis in the Jog section or by selecting the Move Absolute positioning command.
To synchronize the two axes via gearing, the Axis 1 -> GearIN -> Axis 2 button is
available. Synchronous operation coupling of the axes can be requested using this
button.
The error and warning messages are output in the top section of the HMI user
interface. This is where the messages are output in the alarm view. The
ShowErrFB active and ShowErrDB active buttons allow you to activate the
message output for technology function calls and technology objects. When the
buttons are green, the respective message function is activated. The Ignore
Warnings button additionally allows you to suppress the output of warning
messages so that only error messages are displayed in the message table.
In WinCC flexible the language of the error and warning messages can be
changed online using the two flags. The currently active language is displayed with
a green frame.
At the TP900 the language toggles between German and English with pressing the
button Language. The currently active language is represented by the displayed
flag.

Entry-ID: 21402122, V4.2.2, 06/2014 51
7 Operation
7.5.3 Operating the test program
The HMI user interface offers the following operating options for the test program:
Figure 7-5: Operating options
Position
Velocity
Minus
jog button
Axis Coupling of the axes via the

enabled MC_GearIN gearing
Axis
enable
Axis
reset Minus Axis Plus
software limit switch slide software limit switch
The following functions are available to control the display of the error messages:
Figure 7-6: Error display

Display section for
error messages
Activate monitoring Activate monitoring Suppress output Change language:

of of of English-German
technology FBs technology objects warnings

Entry-ID: 21402122, V4.2.2, 06/2014 52
7 Operation
How to use the application example

Table 7-3: Starting up the application example
No. Action Remark
1. On the programming unit, start the
HMI user interface.
2. Select the respective Enable buttons

to enable the drives and use the
Reset button to reset all errors and
warnings of the test program for the
appropriate drive.
3. The axes can now be moved using the

jog buttons.
In addition, a positioning job can be
started by selecting the desired
position from the drop-down list and
starting the job using the Go! button.
4. Finally, the monitoring of the

technology function calls and
technology objects has to be enabled
using the ShowErrFB active and
ShowErrDB active buttons.
If the respective button is displayed in
green, monitoring is enabled and
occurring error messages are
displayed in the display section of the
test program.

Entry-ID: 21402122, V4.2.2, 06/2014 53
7 Operation
7.6 Generating error messages

With the aid of the test program, you can deliberately generate error and warning
messages on a machine and display them using the “Error Messages” template.
The following error and warning situations can be generated easily and quickly in
the test program for the “Error Messages” technology template:
0021: Dynamic values are being limited
8014: Approached a software limit switch
– 0026: Position limited to software limit switch
8040: The axis / external encoder is not enabled, or the wrong mode is set
804A: The required object interconnection is missing
(Reason: The leading axis is not configured for synchronous operation.)
Additionally occurring error and warning messages of the CPU are of course also
indicated via the “Error Messages” technology template.
Note If, with the aid of the test program, error and warning situations are successively
generated in too short a period of time, the CPU may go to STOP!
To continue to execute the test program, the CPU must then be restarted, i.e., it
has to be reset to RUN.
7.6.1 Warning message 0021: Dynamic values are being limited

The axes of the test program are set so that the dynamic values are being
permanently limited. Therefore, warning message 0021 “Dynamic values are
being limited” is output for each motion of the axis.
Table 7-4: Generating warning message 0021
No. Action Remark
1. Enable the desired axis by selecting the Enable
button.
2. Activate the monitoring of the technology objects or
technology data blocks by the “Error Messages”
template.
3. Move the axis with the jog function using the Minus or
Plus jog buttons
or
activate a positioning job by selecting a position and
using the Go! button.
4. Delete the message when the axis is stopped using

the Reset button.
Note:
The message is only removed from the alarm view
when the monitoring is activated using the
ShowErrDB active button.
5. You can suppress the output of the warning message
when ShowErrDB active is active by selecting the
Ignore Warnings button.

Entry-ID: 21402122, V4.2.2, 06/2014 54
7 Operation
7.6.2 Error message 8014: Approached a software limit switch
The software limit switch is approached when the yellow sensor at the lower end of
the slide reaches the yellow limit switch marking.
Figure 7-7: Approaching software limit switch
Table 7-5: Generating error message 8014

No. Action Remark
1. Enable the desired axis by selecting the Enable
button.
technology data blocks by the “Error Messages”
template.
3. Move the axis with the jog function using the Minus or
Plus jog buttons
or
activate a positioning job by selecting a position
behind a software limit switch and using the Go!
button.
4. The axis can only be moved when you have deleted

the pending error message using the Reset button.
Note:
The message is only removed from the alarm view
when the monitoring is activated using the
ShowErrDB active button.
5. Move the axis away from the software limit switch in
the opposite direction with the jog function using the
Minus or Plus jog buttons
or
using a positioning job by selecting a position in the
opposite direction and selecting the Go! button.
If necessary, warning message 0026 “Position limited to software limit switch”

can be output when approaching a software limit switch via a positioning job before
the axis has reached the limit switch.
The controller detects that the target position of the positioning job is behind the
software limit switch and indicates this via warning message 0026 “Position
limited to software limit switch”.

Entry-ID: 21402122, V4.2.2, 06/2014 55
7 Operation
7.6.3 Error message 8040: The axis / external encoder is not enabled, or the
wrong mode is set
Table 7-6: Generating error message 8040

No. Action Remark
1. Deactivate the enable for both axes using the Enable
button.
2. Activate gearing for the two axes of the application
example by selecting the Axis1 GearIN Axis2
button.
The error message appears.
3. Now deactivate gearing using the Axis1 GearIN
Axis2 button and the message disappears.
7.6.4 Error message 804A: The required object interconnection is missing
In the S7T Config configuration tool, the axes of the test program are created in
such a way that a coupling option of the axes exists via MC_GearIn, whereas the
leading axis coupling of the following axis to the leading axis was not activated.
Figure 7-8: Missing coupling between leading axis and following axis in S7T Config
!
Table 7-7: Generating error message 804A
No. Action Remark
1. Enable both axes of the application example by
selecting the Enable button.
technology data blocks using the ShowErrDB active
button.
3. Activate the monitoring of the technology function calls
using the ShowErrFB button.

Entry-ID: 21402122, V4.2.2, 06/2014 56
7 Operation
4. Activate gearing for the two axes of the application

example by selecting the Axis1 GearIN Axis2
button.
Note:
Error code 804A for axis 2 is displayed twice. (once
from the technology DB and once from the technology
function call).
5. Now deactivate gearing using the Axis1 GearIN
Axis2 button.
Note:
Message 804A from the technology function call
disappears since the Execute signal of the technology
function call is removed by the button.
6. Delete error message 804A from the technology DB
by selecting the Reset button of axis 2.

Entry-ID: 21402122, V4.2.2, 06/2014 57
8 Editing the Text Lists
8.1 Expanding/modifying the text lists

8.1 Expanding/modifying the text lists
Opening the text list
To expand the text list, open the “Edit user text libraries” editor.
Figure 8-1: Opening the Text list editor
1
Editing the text list

Add more rows to the text list. The reference to the respective text for display in the
message text is made via the index that is entered in the first column of the text
library.
In particular, the Axis_names_userdefined text list must be customized to the
user-specific conditions. Expand the list by the number of your axes and customize
the texts to your requirements. The index corresponds to the axis DB number.
NOTICE The indices in the text list are always interpreted as integer values. For example,
ErrorID 8014hex (Software limit switch actuated) output by the technology object
in hexadecimal format as WORD is entered in the “31xT_ErrorText” text list in
integer format as index 32788dec.

Entry-ID: 21402122, V4.2.2, 06/2014 58
8.2 Adding more language versions in STEP 7
Figure 8-2: Expanding the text library
If you want to enter the text in multiple languages, first fill the text library in the
currently activated language. Then enter all other languages by changing the
display language or, as explained in the following chapters, by exporting and
importing the text library.
Saving the changes

SIMATIC Manager
For the above changes to become effective in the CPU messages (see Chapter
7.3.1), save the respective text list using .
WinCC flexible (STEP 7 V5.x)
For the above changes to become effective in WinCC flexible, proceed as
described in 1 and additionally:
Delete the temporary files in Options and use Project > Compiler to regenerate
everything (see step 5 in Table 5-5).
WinCC (TIA Portal)
For the above changes to become effective in WinCC, update the proxy CPU and
compile the complete operator panel configuration (see Chapter 5.4.2).

8.2.1 Adding a display language
Before using or editing different language versions of the text libraries, all desired
languages first have to be defined in the SIMATIC Manager:

Entry-ID: 21402122, V4.2.2, 06/2014 59
Figure 8-3: Adding a display language
3
8.2.2 Exporting the text library
To be able to translate the existing texts into the desired and just defined
languages, the entire text library must be exported to a csv file.

Entry-ID: 21402122, V4.2.2, 06/2014 60
Figure 8-4: Exporting the text list
2
In the “Export User Text” window, enter the following data:

In “Text Tables”:
– Target directory for the file to be exported
– Storage format: “csv”
In “Languages”:
– Source language
– New target language into which you want to translate
8.2.3 Opening and editing the exported text library
For editing, the exported text file in csv format of the text library can now be
opened with Microsoft EXCEL. To do so, use Microsoft EXCEL’S Open dialog box.
After opening, each language of the text library is available in a separate column.
By default, newly added languages are assigned the source language text. This
text can now be replaced with the translated wording.

Entry-ID: 21402122, V4.2.2, 06/2014 61
Figure 8-5: Opening the exported text library in Microsoft EXCEL
Source language Target language
The translation can

be entered here
Note When editing the csv file, change only the texts in the target language column
and save the file in csv format.
The original settings for all other entries and notes must not be changed.
Otherwise, problems may occur when importing the csv file into STEP 7.

Entry-ID: 21402122, V4.2.2, 06/2014 62
8.2.4 Importing a text library with additional texts
Figure 8-6: Importing a text library
2
In the “Import User Text” window, enter the following data:

In “Source”:
– Source directory of the file to be imported
– Storage format: “csv”
Note An exported text library should only be reimported into the project from which it
originates.

Entry-ID: 21402122, V4.2.2, 06/2014 63
9 Displaying your own Messages
9.1 Display with FB 510 “ShowErrFB”

The function blocks of the technology template can also be used to display your
own messages by means of the ALARM_S message system.
9.1 Display with FB 510 “ShowErrFB”

FB 510 “ShowErrFB” is best suited for displaying your own messages using the
“Error Messages” template.
Figure 9-1: Display of your own messages via FB 510 “ShowErrFB”
EventID FB_ErrorID
Error
ErrorID FB 510
Axis „ShowErrFB“
AdditionalData
This requires that the index of the desired message be entered at the ErrorID
input. When the Error input is set to True, the message – if the message text has
already been entered in the text library – is output via the “Error Messages”
technology template.
The message disappears from the display when the Error input of FB 510
“ShowErrFB” is set to False.
9.2 Display with FB 511 “ShowErrDB”

Via FB 511 “ShowErrDB”, messages can be displayed that are output via a data
block.
Figure 9-2: Display of your own messages via FB 511 “ShowErrDB”
EventID FB_ErrorID
TDB_Nr
IgnoreWarnings FB 511
„ShowErrDB“
The number of the data block to be monitored must be entered at the TDB_Nr
input. Then the function block reads out the DBW 20 data word in the specified
data block and determines the data block type from this information. For
technology data blocks, the data block type also indicates the technology object
type.
The data block type also defines the address of the location in the data block from
which the error code can be read out.
By default, the “Error Messages” technology template supports the following
technology objects:

Entry-ID: 21402122, V4.2.2, 06/2014 64
9.2 Display with FB 511 “ShowErrDB”
Table 9-1: Supported TO types (for Technology version 1.0, 2.0, 3.0, 4.1 and 4.2)
TO type (UDT number)
Technology object ErrorID address
V 1.0 V 2.0 V 3.0 V 4.1 V 4.2
DriveAxis 1 13 17 34 47 DBW 26
PosAxis 2 12 22 31 46 DBW 26
FollowingAxis 3 11 23 32 45 DBW 26
ExternalEncoder 4 14 18 36 --- DBW 26
Cam 5 5 24 33 49 DBW 22
MeasuringInput 6 6 21 30 ---- DBW 26
OutputCam 7 15 19 35 48 DBW 22
CamTrack --- --- --- 37 --- DBW 26
TraceDB 8 8 8 8 --- Not supported
DeviceDB 10 16 25 25 --- DBW 26
PathObject --- --- --- --- 40 DBW 26
PolynomData --- --- --- --- 41 Not supported
XYZVektor --- --- --- --- 42 Not supported
ZoneDefinition --- --- --- --- 43 Not supported
ZoneDefinition --- --- --- --- 44 Not supported
If you want to monitor self-created data blocks, a type that refers to the correct
location of the message index (ErrorID) must be entered in the DBW 20 data word
of the data block. It may be necessary to supplement this type accordingly in
FB 511 “ShowErrDB”.

Entry-ID: 21402122, V4.2.2, 06/2014 65
10 References
10 References
Table 10-1
Subject Title
\1\ Siemens Industry http://support.automation.siemens.com
Online Support
\2\ Download page of http://support.automation.siemens.com/WW/view/en/21402122
the entry
\3\ STEP 7 V5.x SIMATIC Working with STEP 7 V5.5
\4\ SIMATIC Configuring Hardware and Communication
Connections STEP 7 V5.5
\5\ SIMATIC Programming with STEP 7 V5.5
\6\ SIMATIC STEP7 V5.5 Function Block Diagram (FBD) for
S7-300 and S7-400 Programming
\7\ SIMATIC STEP 7 V5.5 Ladder Logic (LAD) for S7-300 and
S7-400 Programming
\8\ SIMATIC STEP 7 V5.5 Statement List (STL) for S7-300 and
S7-400 Programming
\9\ System Software for S7-300/400 System and Standard
Functions Volume 1 and Volume 2
\10\ Automating with STEP 7 in STL and SCL
Author: Hans Berger
Publisher: Publicis Publishing
ISBN: 978-3-89578-412-5
\11\ Technology CPU SIMATIC S7-300 CPU 31xT – Manual
\12\ SIMATIC S7-300 CPU 31xT-3 PN/DP – Manual
\13\ SIMATIC Engineering Tools S7 Technology - Function
Manual
\14\ SIMATIC S7 300 Automation Systems CPU 317T-2 DP:
Controlling a virtual axis
\15\ WinCC flexible SIMATIC HMI WinCC flexible 2008 Getting Started – First-
Time Users
\16\ WinCC flexible Getting Started Power User
\17\ SIMATIC HMI WinCC flexible 2008 WinCC flexible 2008
Compact/ Standard/ Advanced

Entry-ID: 21402122, V4.2.2, 06/2014 66
10 References
Subject Title
\18\ TIA Portal STEP 7 Professional V13.0 – System Manual
\19\ WinCC Comfort/Advanced V13.0 – System Manual
\20\ Updates for STEP 7 V13 and WinCC V13
\21\ Application Palletizer with Simply Interpolating Axes Based on Cam
examples for the Discs:
technology CPU http://support.automation.siemens.com/WW/view/en/21062269
(a selection) Feeder for a press based on static cam disks:
Flying shears with print-mark synchronization based on gear
synchronism:
Cross Slide / Single Belt Application:
Parameterization of the "Gear Synchronization" Technology
Function (SyncOp Guide):
\22\ Technology Technology Template "Simple 3D-Interpolation with cam
templates for the disks":
technology CPU
(a selection) Technology Template “Hydraulics Characteristic”:
Technology Template “Flying shears”:
Technology Template “Flying shears”:
Technology Template “Move_Jog”:
\23\ FAQs for the Which encoders can you use with the Technology CPUs?
technology CPU http://support.automation.siemens.com/WW/view/en/19968954
(a selection) Which versions of the S7 Technology option package are
available and which SINAMICS S120 drive firmware can you
use with which of these versions?
How can I display a cam disk of the technology CPU on the
HMI using WinCC flexible?

Entry-ID: 21402122, V4.2.2, 06/2014 67
11 History
11 History
Table 11-1
Version Date Modifications
V1.0 First version
V2.0 01/2005 Revision of the “Error Messages” technology template:
Integration of the messages for the “S7 Technology”
option package up to version 2.0 into the text libraries.
Introduction of the compact documentation.
V3.0 09/2006 Revision and extension of the “Error Messages” technology
template:
Implementation of the test program for the technology
template in WinCC flexible.
Modification of the documentation to comply with the
changes.
V4.1 02/2009 Revision and extension of the “Error Messages” technology
template:
Implementation of the test program for the technology

template in WinCC flexible 2008.
changes.
V4.1.1 02/2010 Revision and extension of the “Error Messages” technology
template:
Expansion of the technology template blocks for the
axis number display in the message text.
changes.
V4.2.2 06/2014 Revision and extension of the “Error Messages” technology
template:
Expansion of the text lists of the technology template to
display the axis number in the message text as a user-
defined axis name.
Additional TIA project for configuring the operator panel
with WinCC in TIA Portal (for example, for Comfort
Panels).
changes.

Entry-ID: 21402122, V4.2.2, 06/2014 68

CPU31xT Error Message DOKU v422 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

CPU31xT Error Message DOKU v422 en

Uploaded by

Copyright:

Available Formats

Application Description 06/2014

Warranty and Liability

body or health, guarantee for the quality of a product, fraudulent concealment of a

Any form of duplication or distribution of these Application Examples or excerpts

"Error Messages" Technology Template

3.1 Functional principle of the technology template ................................ 12

"Error Messages" Technology Template

6.1 Call environment.............................................................................. 41

7.6.4 Error message 804A: The required object interconnection is

"Error Messages" Technology Template

1 Inter Project Engineering

Configuration in TIA Portal

Visualization of a T-CPU with a Comfort Panel

1. Create your STEP 7 V5.x project using the T-CPU as usual.

"Error Messages" Technology Template

A technology template is a software object or a code block with a defined interface

2.1.2 Configuration systems

2.1.3 Main contents of this technology template

This technology template discusses the following key issues:

This technology template does not include a description of …

"Error Messages" Technology Template

2.2 Objective and purpose

Figure 2-1: Detecting and interpreting technology error messages

Fast program generation

"Error Messages" Technology Template

Immediate readiness for service

2.3 Possible applications

Table 2-1: Supported technology objects and technology functions

"Error Messages" Technology Template

The following properties were not considered in the implementation of the

2.4 Components of the technology template

Figure 2-2: Components of the “Error Messages” technology template

Function blocks Text lists

"Error Messages" Technology Template

2.5 Approved hardware and software

Table 2-2: Hardware components

SFC 24 “TEST_DB”: To check data blocks

2.5.2 Software components

Standard software components

"Error Messages" Technology Template

Software components additionally required for the test program

Sample files and projects

"Error Messages" Technology Template

"Error Messages" Technology Template

3.2 Monitoring a technology object

To monitor a technology object, the “ShowErrDB” function block of the template

3.3 Monitoring a technology function

ErrorID Error code ErrorID

To monitor a technology function call, a “ShowErrFB” function block of the

"Error Messages" Technology Template

Table 4-1: Assignment of the EventID by STEP 7

Table 4-2: Definition of the system attributes

"Error Messages" Technology Template

No. Action Remark

3. In the Attribute section of the object

the setting fields.

4.2 Text lists

"Error Messages" Technology Template

4.3 Associated values of the ALARM_S message function

4.4 Configuring Report system error

Optimized creation of messages

"Error Messages" Technology Template

Table 4-3: Unchecking Optimized creation of messages