Siemens

Industry
Online
Support

APPLICATION EXAMPLE

PCS 7 TeleControl
Type configuration
SIMATIC PCS 7 V9.1 / TeleControl Option / Type configuration
Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several components in the form of text,
graphics and/or software modules. The application examples are a free service by Siemens AG and/or a subsidiary of Siemens AG
(“Siemens”). They are non-binding and make no claim to completeness or functionality regarding configuration and equipment. The
application examples merely offer help with typical tasks; they do not constitute customer-specific solutions. You yourself are responsible
for the proper and safe operation of the products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the application examples used by technically
trained personnel. Any change to the application examples is your responsibility. Sharing the application examples with third parties or
copying the application examples or excerpts thereof is permitted only in combination with your own products. The application examples
are not required to undergo the customary tests and quality inspections of a chargeable product; they may have functional and
performance defects as well as errors. It is your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.

Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for the usability,
availability, completeness and freedom from defects of the application examples as well as for related information, configuration and
performance data and any damage caused thereby. This shall not apply in cases of mandatory liability, for example under the German
Product Liability Act, or in cases of intent, gross negligence, or culpable loss of life, bodily injury or damage to health, non-compliance
with a guarantee, fraudulent non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for damages
arising from a breach of material contractual obligations shall however be limited to the foreseeable damage typical of the type of
agreement, unless liability arises from intent or gross negligence or is based on loss of life, bodily injury or damage to health. The
foregoing provisions do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens against existing or
future claims of third parties in this connection except where Siemens is mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond the liability provisions
described.

Other information
Siemens reserves the right to make changes to the application examples at any time without notice. In case of discrepancies between the
suggestions in the application examples and other Siemens publications such as catalogs, the content of the other documentation shall
have precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.

Security information
Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems,
machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement – and continuously
maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and solutions constitute one element of such a
concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines
and components should only be connected to an enterprise network or the internet if and to the extent such a connection is necessary
and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that
product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are
no longer supported, and failure to apply the latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under https://www.siemens.com/cert.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 2

 Table of contents

Table of contents
1. Introduction ...................................................................................................................................4

1.1. Overview ......................................................................................................................................................4

1.2. Principle of operation ....................................................................................................................................5
1.3. Task description ............................................................................................................................................6
1.4. Limitations ...................................................................................................................................................6
1.5. Components used .........................................................................................................................................7

2. Engineering ...................................................................................................................................8

2.1. Hardware Setup .......................................................................................................................................... 10

2.2. Configuration ............................................................................................................................................. 11
2.2.1. DBA function address calculation ................................................................................................................. 11
2.2.2. Data point configuration in TIA Portal .......................................................................................................... 14
2.2.3. Structure of the IECAnalogValue_V1 type ..................................................................................................... 15
2.2.4. Create a new type by copying ...................................................................................................................... 17
2.2.5. Configure required tags............................................................................................................................... 20
2.2.6. Creating messages ...................................................................................................................................... 26
2.2.7. Copying the block icon ................................................................................................................................ 32
2.2.8. Creating a new faceplate variant.................................................................................................................. 34
2.3. Function test .............................................................................................................................................. 39

3. Appendix .....................................................................................................................................41

3.1. Service and support .................................................................................................................................... 41

3.2. Application support ..................................................................................................................................... 42
3.3. Links and literature ..................................................................................................................................... 42
3.4. Change documentation ............................................................................................................................... 42

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 3

 Introduction

1. Introduction
1.1. Overview
Especially in the water & wastewater industry, technological plants are sometimes very widely distributed. Under certain
circumstances, decentralized plant sections can be located several hundreds of kilometers from a central main plant. For
example, a large central wastewater treatment plant can have extensive branching ductwork, connected to several
sewage pumping stations, rainwater retention basins (RRBs) and detention pipes. Therefore, far-flung plant sections must
be monitored from a central control room, or need to be operated and monitored from a distant location.

Central wastewater treatment plants with a much higher level of automation generally implement a process control
system, such as SIMATIC PCS 7. The local automation of smaller plant sections with a low degree of automation is
however done with simple remote terminal units (RTU) that communicate remotely with the control station by means of a
telecontrol link. Telecontrol systems, such as SIMATIC PCS 7 TeleControl, integrate these RTUs directly into the high-level
control system. Uniform process control and integrated engineering for central and remote plant sections provide high
efficiency during operation and configuration.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 4

 Introduction

1.2. Principle of operation

PCS 7 TeleControl is a software package consisting of the engineering software "Data Base Automation" (DBA) and a
library of OS symbols, OS faceplates and OS diagnostic displays for remote stations of a telecontrol system. The DBA
engineering software automatically generates the OS database with the display hierarchy, required tags, alarms, alarm
messages and alarm priorities, as well as the specific faceplates and block icons.

PCS 7 TeleControl provides a basic library with standard functions. These allow PCS 7-compliant operation via symbols and
faceplates. The basic library can be extended on a project-specific basis.
The basic library is presented below.

NOTE For more information about the library objects, see the "PCS 7 TeleControlObjects" manual. You can find the
manual in the product release: "Product documentation: SIMATIC PCS 7 TeleControl V9.1"
https://support.industry.siemens.com/cs/ww/en/view/109808769

The following types of technological typicals are available:

Analog Value
Analog values such as pressures, temperatures and flow rates in a pipeline network are important pieces of information
that must be correctly evaluated, averaged and archived. The measurement library objects provide several ways to
manipulate these values.
Bit Alarm
The bit alarm is a mechanism by which a message is generated when a binary value is changed. The message can be
triggered when the bit changes to 0, or when it changes to 1.
Command
Since not all stations fully support command processing, a command type has been provided that allows checking of
interlocks and monitoring of checkbacks in the TeleControl server.
Counter
Counters provide important information about product quantities and energy transferred in pipelines. There is a standard
counter that allows scaling, increment calculation, totaling, substitute value calculation, and messages. Other counter
functions can also be implemented, such as the integration of measured values, operating hours counters, switch
counters or the counting of fault times.
The TeleControl counter calculates a CV count from the station's raw values or from specific substitute rules.
MeasuredValue
Analog values such as pressures, temperatures and flow rates in a pipeline network are important pieces of information
that must be correctly evaluated, averaged and archived. The measurement library objects provide several ways to
manipulate these values. Compared to the "Analog Value", this type provides additional functions such as gradient
monitoring, a moving average, and statistics functions.
Motor / Pump / Valve
There are three types of devices: Motor, pump, and valve. All three are based on a common "subtype" and have the same
process tags and telegrams. These types of devices enable the operation of equipment in automatic and manual mode,
plus command locking.
Setpoint
Since not all stations fully support setpoint processing, a setpoint type has been provided that allows scaling, checking of
interlocks, and monitoring of checkbacks in the TeleControl server.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 5

 Introduction

1.3. Task description

The AnalogValue type includes a monitoring function for checking for high and low limit violations of the current process
values with respect to four adjustable limits. Warning or alarm messages are then issued accordingly.
Verification is performed in the OS TeleControl server.

Name Class Type Configured by Condition description

default

High High Alarm Alarm Alarm high Yes PV > HH

High Warning Warning Warning high Yes PV > H

Low Warning Warning Warning low Yes PV < L

Low Low Alarm Alarm Alarm low Yes PV < LL

However, with many process plants, there is the challenge that the test has to be carried out in the automation system,
here referred to as RTU, in order to perform the corresponding functions.
For example, if there is overpressure in a pipe or if the fill level of a container is reached, a pump should be switched off.
Furthermore, limit values should not be "hard programmed" but rather should be changeable. This means that the
necessary type for this must support a write function by means of a setpoint, as well as reading of limits from the RTU.

This application example describes the necessary steps for this. A new variant is created based on the standard type
IECAnalogValue_V1 that allows the limits to be written and read from the RTU.
PCS 7 TeleControl supports the SINAUT ST7, IEC 60870-5-104 and DNP3 telecontrol protocols. This example uses the IEC
60870-5-104 protocol, but the workflow is protocol independent.

1.4. Limitations
This application example is not an introduction to PCS 7 TeleControl Engineering. This knowledge is assumed. We refer
here to the product manuals and other application examples; TIA Portal configuration is also not discussed in greater
detail.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 6

 Introduction

1.5. Components used

The following hardware and software components were used to create this application example:

Component Number Article number Note

SIMATIC PCS 7 V9.1 1 6ES7658-...68-....

PCS 7 TELECONTROL OS RUNTIME V9.1 1 6ES7658-7KX68-0YA0

PCS 7 TELECONTROL OS ENGINEERING V9.1 1 6ES7658-7JX68-0YA5

SIMATIC TELECONTROL IEC 870 DRIVER 1 6DL5101-8CX00-0XB0

CPU 1214C 1 6ES7214-1AG40-0XB0

CP 1243-1 communication processor 1 6GK7243-1BX30-0XE0

TIA Portal V18 1 6ES7823-……….

Table 1-1

The listed components can be obtained from the Siemens Industry Mall, for example.

This application example consists of the following components:

Component File name Note

This document "PCS_7_TeleControl_Engineering_Type_Configuration_Limits"

Table 1-2

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 7

 Engineering

2. Engineering
The DBA engineering system is used for PCS 7 TeleControl. It consists of two functions.

The standard view consists of four different sub-windows or quadrants.

"Plant View": Create

the plant hierarchy Object editor:
and assign PLC Configuration in case of
instances OS instances

Physical objects like PLC PLC object editor,

(RTU), connections, configuration of
OS server, Modbus RTU PLC instances

NOTE For more information on these quadrants, see the manual: "DBA User Guide"
https://support.industry.siemens.com/cs/attachments/109808769/PCS7_TELECONTROL_DBA_en.pdf

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 8

 Engineering

The DBA Type Editor is a powerful, built-in component of the DBA engineering tool. It contains a library of standard
TeleControl types. These allow the user to create user-defined versions of the standard types as well as new, application-
specific types. The type/instance principle allows the user to reuse a defined type as often as he wants without much
effort. In addition, making improvements to one type just once is enough to propagate the improvement to all instances
of the type, with little or no additional effort.

NOTE For more information about the DBA Type Editor, see the manual:
"Process Control System PCS 7 TeleControl DBA Type Editor"
https://support.industry.siemens.com/cs/attachments/109808769/DBATypeEditorTELECONTROL_en.pdf

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 9

 Engineering

2.1. Hardware Setup

The hardware and software used for this application example is as follows. For PCS 7 OS/ES, a single-station system is
used.
WAN is an Ethernet connection between OS and RTU.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 10

 Engineering

2.2. Configuration
2.2.1. DBA function address calculation

NOTE For a detailed description, see the manual:

"Process Control System PCS 7 TeleControl DBA Type Editor"
https://support.industry.siemens.com/cs/attachments/109808769/DBATypeEditorTELECONTROL_en.pdf

When configuring a default address for an external tag, it is possible to use attributes with simple expressions to perform
calculations that can simplify the configuration of instances of the type. For example, for IEC types, each object address
must be unique. These can be calculated using a start address and offsets.

NOTE This application example is protocol-independent and also applies to the SINAUT ST7 and DNP3
protocols. The term "telegram number" is used here to address the process data. In IEC 60870-5-104,
the common term is "Information Object Address" or IOA. With DNP3, addressing is done via an index.

As an example, a type with five external tags was configured: TAG1 TAG2 TAG3 TAG4 TAG5
The individual unique addresses can then be calculated as follows:

• TAG1 - Telegram Number = TELNUM + Offset 1

• TAG2 - Telegram Number = TELNUM + Offset 2
• TAG3 - Telegram Number = TELNUM + Offset 3
• TAG4 - Telegram Number = TELNUM + Offset 4
• TAG5 - Telegram Number = TELNUM + Offset 5
If all instances of the type follow this pattern, then it should be sufficient to configure only one telegram number
(TELNUM) for each instance instead of five telegram numbers.
This can be achieved for the type by carefully considering the default address for each external tag and generating
another attribute for the type.
The following scheme has been defined for the task description.

Description Tag names for Tag names for Tag name for Address Address parameter
feedback setpoint checkback parameter for for setpoint and
feedback checkback

Alarm high limit HH HH_SP HH_CP TelNo + 102 TelNo + 202

Warning high limit H H_SP H_CP TelNo + 101 TelNo + 201

Warning low limit L L_SP L_CP TelNo + 100 TelNo + 200

Warning low limit LL LL_SP LL_CP TelNo + 99 TelNo + 199

RTU value RV TelNo

Quality description QDS TelNo

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 11

 Engineering

Instead of entering individual object addresses for each individual tag, only one address needs to be entered.

As we'll see later, the addressing in the instance will then look like this. The object addresses for each tag are
automatically determined.

To enter the start object address, enter a "TelNo" attribute in the Type Editor.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 12

 Engineering

Description of individual parameters

Field Contents

Name Enter a descriptive name here, e.g. TELNR.

Display name Name that appears when configuring the instance. This is usually the same name as in "Name",
unless the type is configured for multilingual use.

Category Enter any name you like here. Important: Do not use the name "Address" because it is used for
each addressing component of the type. (e.g. the telegram number for each tag)

Display category Category name that appears when configuring the instance. This is usually the same name as in
"Category", unless the type is configured for multilingual use.

Description You can enter a longer description here, e.g. Common Telegram number.

Type Str

Value Enter a default value here, e.g. 0.

Visible Activated

Permission r/w

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 13

 Engineering

2.2.2. Data point configuration in TIA Portal

For the four limits, you will create four analog values of type Real in TIA Portal.

You will configure two data points each for the controller and checkback.

NOTE A detailed description for IEC 60870-5-104 engineering can be found in the manual:
"SIMATIC NET: TeleControl Configuration - IEC 60870-5"
https://support.industry.siemens.com/cs/ww/en/view/109762495

NOTE No further explanation is given here. TIA knowledge is a prerequisite. This description also applies to
other RTU solutions.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 14

 Engineering

2.2.3. Structure of the IECAnalogValue_V1 type

The types have a modular design. A composite type is a type that contains another type, such as "CommonMembers". In
fact, most types belong to this group and contain a type called "CommonMembers", which in turn defines tags and
messages needed by virtually all types. For each tag and each message of a type that is to be included in another type, the
specification can be applied in the required field under "Inheritance". This specifies which tags or messages to include or
exclude as needed.
Type IECAnalogValue_V1 is structured as follows, i.e. it contains two other types.

Included types are marked with blue font in the Type Editor. The corresponding type name is found in the Parent Type
column.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 15

 Engineering

In the "Includes" tab, the structure can be checked and modified. Other types can be added or removed here.
For the task, you need to change the four tags H, HH, L, and LL in the type "CommonTCAnalog_V1" from internal to
external tags. Furthermore, you will need four setpoints for the limit value change.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 16

 Engineering

2.2.4. Create a new type by copying

Because the standard "IECAnalogValue_V1" type consists of three individual types, you must also create three new types
for the new type by copying and modifying.
Usually, these types would be marked with a project-specific abbreviation so that they are clearly identifiable.
We will use "ExtLimit" as the identifier here.
Make a copy of type "CommonTCAnalog_V1":
1. Select the "CommonTCAnalog_V1" type.
2. Use the "Copy" button to copy the type. A dialog opens.
3. Customize the name by replacing the V1 with our identifier "ExtLimit".
4. Confirm the dialog with "OK".

Next, you'll make a copy of type "AnalogValue_V1":

5. Select the "AnalogValue_V1" type.
6. Use the "Copy" button to copy the type. A dialog opens.
7. Customize the PLC and HMI names by replacing the V1 with our "ExtLimit" identifier.
8. Confirm the dialog with "OK".

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 17

 Engineering

Lastly, you'll make a copy of type "IECAnalogValue_V1":

9. Select the "IECAnalogValue_V1" type.
10. Use the "Copy" button to copy the type. A dialog opens.
11. Customize the PLC and HMI names by replacing the V1 with our "ExtLimit" identifier.
12. Confirm the dialog with "OK".

You have assembled the new type as follows:

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 18

 Engineering

Appearance in the "Include" view of the Type Editor:

The view is divided into three parts. In the left panel, all existing types are displayed in a list. However, not all of them are
selectable to create an instance. In the middle panel, all basic types are listed. If a type is selected in the left panel, its
structure of basic types is displayed in the right panel. The two buttons ">" and "<" can be used to change their structure,
i.e. basic types from the middle panel can be added or deleted.
1. On the left side of the DBA Type Editor, select "IECAnalogValue_ExtLimit".
2. Use the arrow keys to adjust the type so that it mirrors the setup described above.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 19

 Engineering

2.2.5. Configure required tags

• External (external tags)
External tags receive data values from the PLC through the data server. An external tag requires a PLC address.
External tags are taken into account when counting all tags. This count provides information about the size of the
project.
• Internal (internal tags)
The values of internal tags are only kept in the data server, not in the PLC. They can be added as you wish for
calculations or local data storage in the OS. They are not included in the total number of tags.
• Indirect (indirect tags)
An indirect tag has an address value that points to another tag which contains the actual value. Indirect tags provide a
high degree of flexibility in terms of the source of interlock signals for motors and valves. If an analog value exceeds a
limit, it can be used to set a tag for the limit that serves as the source of the interlock signal.

Creating limits
You have to change the four internal limit values H, HH, L and LL from internal to external.
1. To do this, select the type "CommonTCAnalog_ExtLimit" on the left side of the DBA Type Editor.
2. Select the tag with the name "H" and open the Tag Editor using the "Edit" button.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 20

 Engineering

3. In the "Names" field, you can customize the name.

4. Change the source from Internal to External.
5. Use the three-dot button to open the "Variable Addressing Information" dialog.
6. Change the data processing mode to "RP" and the RTU data type to "36".
7. Set the flag to "VALUE – Value".
8. Check the Object Address and adjust it if necessary.

9. Adjust the settings for all limit tags.

Additional information on settings

Data processing mode:
This setting generally indicates whether the tag is read-only or can be written, and whether the tag contains special
channel data or process data. The following data processing modes are available in the drop-down list:
• RP (read process data)
• RPA (read process data in advance)
• RO (read special channel data value)
• WP (write process data)
• WO (write special channel data value)
RO and WO are reserved in most cases for use in pre-configured IEC diagnostics types. RPA is used in conjunction with
"General Query".
In general, only the two data types RP or WP are used.
TK 36 has been set for the RTU data type.
<36> := Measured value with abbreviated floating point number and time marker CP56Time2a M_ME_TF_1

VALUE is selected in the Flag parameter. This processes the transmitted analog value.
The object address is determined using the calculation function described above. However, the offset with 101 is only an
example and can be defined on a project-specific basis if a different scheme is used.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 21

 Engineering

Setpoint creation
For the control direction, you need to create four new tags ending in _SP for Setpoint.
1. To do this, select the type "CommonTCAnalog_ExtLimit" on the left side of the DBA Type Editor.
2. Use the "Add" button to create the four new setpoint tags. This will open the Tag Editor.

The WinCC data type is also FLOAT, i.e. floating point.

3. Assign a meaningful name. Now that you are setting the setpoint for Warning High, it is "H_SP".
4. For the data processing mode, select WP (write process data).
5. Set the RTU data type to TK 50.
6. For the Flag parameter, select "QOS_QL0 – Qualifier of Setpoint Command – Default". As a result, the analog value
entered in the faceplate is later transmitted to the RTU.
7. In the Mode parameter, set "EX – Execute Only". Note that this setting must match the RTU configuration.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 22

 Engineering

8. The object address is determined using the calculation function described above. The offset of 199 is only an example
and can be defined on a project-specific basis if a different scheme is used.

9. Adjust the settings for all limit tags.

In addition to these four setpoint tags, you must create four additional tags ending in _CB to evaluate the checkback from
processing.
The following readouts are possible and must be taken into account when engineering the messages:
0 – successful
1 - in operation
2 – failure
3 - time out
4 – cancelled

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 23

 Engineering

Checkback creation
1. To do this, select the type "CommonTCAnalog_ExtLimit" on the left side of the DBA Type Editor.
2. Use the "Add" button to create the four new CB tags. This will open the Tag Editor.

3. Configure the CB tags The configuration works in the same way as the other tags. Adjust the values of the tags as
shown in the screenshot.

Note that an "FT" is required in the Organizational Type parameter field. Specific processing is carried out for the
checkback status, which is controlled by this parameter.
4. Repeat the steps for the other tags.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 24

 Engineering

Configuration result

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 25

 Engineering

2.2.6. Creating messages

If there is an incorrect configuration or if there are problems with setpoint processing in the RTU, this will be displayed in
the checkback status. This is communicated to the operator by means of a message.
You will configure a message each setpoint or checkback status.

NOTE A detailed description can be found in the manual "Process Control System PCS 7 TeleControl DBA Type
Editor" in chapter 7.4 "Working with the message editor"

Process Control System PCS 7 TeleControl DBA Type Editor

https://support.industry.siemens.com/cs/attachments/109808769/DBATypeEditorTELECONTROL_en.pdf

1. To do this, select the type "CommonTCAnalog_ExtLimit" on the left side of the DBA Type Editor.
2. Change to the "Messages" tab.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 26

 Engineering

3. Use the "Add" button to create the four new messages. This will open the Message Editor.
The message is configured in the Message Editor with the four tabs "General", "Tags", "Process Vars" and "Free Vars".

• "General" tab:
Description of the parameters
- Class and Type:
This field may contain one of the PCS 7 Alarm Classes as configured in the WinCC Alarm Logging Editor.
Examples of Alarm Type are "Type1" and "Type161". The Alarm Type denotes the severity or kind of alarm,
such as "Alarm" or "Warning", but it must be specified in the "TypeNNN" format used by PCS 7 OS, and you must
refer to the Alarm Logging Editor in your WinCC project to find the meanings for each type.
- Priority:
Priority is a number indicating the relative importance of an alarm. A list of alarms in the OS may be sorted by
Priority for effectively dealing with the most important ones first. PCS 7 priorities are in the range of 0 to 16, with
16 being the highest.

- Text:
This specifies the text that will be seen by the operator in the runtime in the "Event" field of message windows,
after an alarm has occurred.
Simple text like "High Alarm" could be entered, but a more useful message would include a comment unique to
the Instance that is in alarm, the actual value of the tag causing the alarm, and the engineering unit (dimension)
of the tag. For example: "Boiler 3 in High Alarm at 250.0 psi.g".
Alarm text can be automatically generated from macro expressions that refer to tag information, which in turn can
be extracted from the database.

- Using the "." extension:

If you want to include the start value of an internal tag that was configured as part of an alarm text, for example,
enter a "." (period) followed by the tag name. Example: ‘.#comment" replaces the start value of the field
"#comment" (usually configured for each instance in DBA) in the character string. This is useful if the tag to be
used is constant configuration data and won’t be changing at runtime.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 27

 Engineering

- Using the "@" extension:

If you want to include the current value of any tag in the type, specify it as a process tag as described in the section
below, "Process tags".
Examples:
●Alarm text = .#comment ALM1 .ALM1_TYPE Alarm at @6%f@ .PV#unit
●Alarm text = .#comment valve recirculation failure, alarm disabled
Explanation:
•.# comment is appended by a comment pertaining to the instance, e.g. "VALVE 123 hot water"
•ALM1: the name of this alarm
•.ALM_TYPE: a tag that gives the value of the Type
•@6%f@: the value of the 6th auxiliary process tag
•.PV#unit: the auxiliary tag containing the unit of measure for PV
4. Enter an appropriate name and display name.
5. Set the Class parameter to 4.
6. In the Text field, give a meaningful description for the message.

• In the "Tags" tab of the message editor, you can specify which tags of the type control the behavior of the alarm
function for the selected message.
In the "Tag" field, one of the tags for the type is selected from the drop-down list. This is the tag that will trigger the
message. In the field below the tag, you can enter a bit number. If the specified bit number of the tag changes from 0
to 1, the message will be generated. This is the simplest case. If more complicated message triggers are needed, the
Expression Builder can be used to define a trigger criterion

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 28

 Engineering

7. In the "Tag" field, use the drop-down list to adjust the tag that will be used for the type. In the lower field, you can
enter a bit number.

• You can create triggers of the following types in the "Expression Builder" editor:
•Bit
•Boolean value
•Integer
•Analog

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 29

 Engineering

An integer value is selected to trigger the message.

The configuration appears as follows:
8. Select Integer as the type of trigger.
9. Select the ">" comparison operator.
10. Choose a constant for "Compare To".
11. Here, enter an integer value of 1 against which a comparison will be made.

12. Change to the "Process Vars" tab.

• In the "Process Vars" tab, you can enter a list of tag names for the current type, which provide the actual values for
alarm messages, for example. These values are the auxiliary values that can appear in message texts to the operator.
- The tags specified here are normally output in the alarm text, which causes the current value of the specified
process tag to be inserted in the alarm text at runtime.
- The process tags listed here can be referenced in the alarm text with the following syntax:

• Process tag 1 = @1%f@

• Process tag 2 = @2%f@

etc.
- The term "%letter" after the number indicates the data type of the tag:

• f = float

• d = integer

• s = string
- Other data types, like those of the C programming language, are supported.
By default, parameter 7 is used to insert the instance or block comment at the beginning of the message text.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 30

 Engineering

13. Enter the CB name in parameter 6 and "#comment" in parameter 7.

14. Repeat the steps for the other messages.

Configuration result

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 31

 Engineering

2.2.7. Copying the block icon

In the previous chapters, you created a new DBA type. For each type, following the PCS 7 type concept, there is an icon
for the display in the process screen and a faceplate for the detail view and operation.
The default icons are provided in a special Graphics Designer file.
This file, "@@TeleControlTypicals_APL.pdl" for PCS 7 TeleControl, is copied to the "GraCS" directory of your project during
installation.

If a WinCC OS is created in SIMATIC Manager, this file is copied to the project in addition to many other files.
Project-specific icons should not be created in this file, but in a separate file.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 32

 Engineering

1. Create a new .pdl file named "@TelecontrolTypicals_ABC.pdl".

2. Copy the AnalogValue icon from the "@@TeleControlTypicals_APL.pdl" screen to the "@TelecontrolTypicals_ABC.pdl"
screen
3. Customize the "Type" and "Servername" properties.

NOTE The abbreviation "ABC" is intended to be a project-specific abbreviation. It is recommended to adjust

the abbreviation so that it is always clear which project it comes from.

As an anticipation of later chapters, the context/configuration in DBA, and the parameters in the visualization icon, are
shown here. SN or Symbol Name is automatically determined by DBA from the Type Name.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 33

 Engineering

2.2.8. Creating a new faceplate variant

NOTE For more information on how to create a faceplate, see the guide:
"SIMATIC Process Control System PCS 7 APL Style Guide"
https://support.industry.siemens.com/cs/ww/en/view/65601446

The standard faceplate TC_APL_AnalogValue_V1 cannot be used, so a faceplate variant must be created. For ease of use,
it is recommended to copy all required faceplate files to a new directory first. We will use the D:\Faceplates directory here.

Using the search function of Windows Explorer, the 6 files to be changed can be easily selected and copied in the GraCS of
WinCC project.
1. Go to the "GraCS" folder of your OS and search for "PG_TC_APL_Analog". You will find the 6 files to modify.
2. Copy them to a new directory. We will use a new folder, "Faceplates", in the D: directory

3. Rename the images by adding appending the names with "ExtLimit". Note that the first file must not be renamed.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 34

 Engineering

4. Open the "@PG_TC_APL_Analog_Value_ExtLimit_V1" screen in Graphics Designer.

5. Select the object "@Faceplate" and switch to the Object Properties.
6. Under "Texts", adjust the "FirstView" attribute. Enter "@PG_TC_APL_Analog_Value_ExtLimit_V1_Standard.PDL".

7. Next, select the "ToolbarWindow" object and switch to the Object Properties.
8. Under the "Miscellaneous" item, adjust the "Picture Name" attribute. Enter
"@PG_TC_APL_Analog_Value_ExtLimit_V1_ViewToolbar.PDL".

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 35

 Engineering

9. Next, select the "ObjCollection" object and switch to the Object Properties.
10. Under "Settings", adjust the "BlockType" attribute. Enter "@PG_TC_APL_Analog_Value_ExtLimit_V1".

11. Save and close the "@PG_TC_APL_Analog_Value_ExtLimit_V1" screen.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 36

 Engineering

In order for the limits to be written, the dynamic tags still have to be adjusted.
12. Open the "@PG_TC_APL_Analog_Value_ExtLimit_V1_Limit.pdl" view.
13. Select the object "AlarmHH" and switch to the Object Properties.
14. Open the menu item "LinkedOp" and enter the corresponding setpoint in the property "LinkOp", here ".HH_SP".

To make sure that the limit is written, this must be checked in the "AnalogDisplayExtended" script call and possibly
adjusted.
15. Go to the "Events" tab and open the "AnalogDisplayExtended" script.
16. Check if "LinkedOp" is called in the SetLink function.

17. Repeat the configuration for the other limits.

18. Save and close the screen you modified.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 37

 Engineering

19. Copy the ExtLimit screens from the Faceplate folder to the GraCS folder of your WinCC project.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 38

 Engineering

2.3. Function test

Before a functional test can be performed, the DBA project must first be compiled.
1. Open the DBA project.
2. Press the "Compile" button to open the compile dialog.
3. Select the appropriate project and click on the "Compile" button to start compiling the program.

Then the WinCC project can be started in runtime.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 39

 Engineering

You can enter different values in the faceplate view for the limits and check them in a watch table in TIA Portal.
The individual values are written to the RTU using the setpoint function and transmitted back as checkback.
In the event of an error, check the configuration.

NOTE Common errors are invalid parameters for the setpoint, including an incorrect type or object address.

Another remedy which has proven effective in dealing with errors is to check the system with Wireshark. However, this
will not be covered in more detail here.

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 40

 Appendix

3. Appendix
3.1. Service and support
SiePortal
The integrated platform for product selection, purchasing and support - and connection of Industry Mall and Online
support. The SiePortal home page replaces the previous home pages of the Industry Mall and the Online Support Portal
(SIOS) and combines them.

• Products & Services

In Products & Services, you can find all our offerings as previously available in Mall Catalog.

• Support
In Support, you can find all information helpful for resolving technical issues with our products.

• mySieportal
mySiePortal collects all your personal data and processes, from your account to current orders, service requests and
more. You can only see the full range of functions here after you have logged in.
You can access SiePortal via this address: sieportal.siemens.com

Industry Online Support

Industry Online Support is the previous address for information on our products, solutions and services.
Product information, manuals, downloads, FAQs and application examples - all information is available with just a few
mouse clicks: support.industry.siemens.com

Technical Support
The Technical Support of Siemens Industry provides you fast and competent support regarding all technical queries with
numerous tailor-made offers – ranging from basic support to individual support contracts.
Please send queries to Technical Support via Web form: support.industry.siemens.com/cs/my/src

SITRAIN – Digital Industry Academy

We support you with our globally available training courses for industry with practical experience, innovative learning
methods and a concept that’s tailored to the customer’s specific needs.
For more information on our offered trainings and courses, as well as their locations and dates, refer to our web page:
siemens.com/sitrain

Industry Online Support app

You will receive optimum support wherever you are with the "Industry Online Support" app. The app is available for iOS
and Android:

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 41

 Appendix

3.2. Application support

Siemens AG
Digital Industries
Process Automation
Automation & Engineering System
System Support
DI PA AE SUP SPS
76187 Karlsruhe, Germany
mailto: [email protected]

3.3. Links and literature

No. Topic

\1\ Siemens Industry Online Support

https://support.industry.siemens.com

\2\ Link to the article page of the application example

https://support.industry.siemens.com/cs/ww/en/view/109955629

\3\ Product documentation: SIMATIC PCS 7 TeleControl V9.1

https://support.industry.siemens.com/cs/ww/en/view/109808769

\4\ Process Control System PCS 7 TeleControl DBA Type Editor

https://support.industry.siemens.com/cs/attachments/109808769/DBATypeEditorTELECONTROL_en.pdf

\5\ DBA User Guide

https://support.industry.siemens.com/cs/attachments/109808769/PCS7_TELECONTROL_DBA_en.pdf

\6\ SIMATIC NET: TeleControl Configuration - IEC 60870-5

https://support.industry.siemens.com/cs/ww/en/view/109762495

\7\ SIMATIC Process Control System PCS 7 APL Style Guide

https://support.industry.siemens.com/cs/ww/en/view/65601446

Table 3-1

3.4. Change documentation

Version Date Change

V1.0 04/2024 First edition

Table 3-2

Article ID: 109955629 | V1.0 | 04/2024 © Siemens 2024 | 42