PCS7 OpenOS 3rdparty Integration ABB V9.0 en

Integration of an ABB
Freelance Controller
with PCS 7/OPEN OS
Siemens
SIMATIC PCS 7/OPEN OS Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/49740087 Support
Legal information
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
© Siemens AG 2014 All Rights Reserved
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
at: https://www.siemens.com/industrialsecurity.
ABB Freelance PLC integration with PCS 7/OPEN OS

Entry ID: 49740087, V1.1, 06/2021 2
Table of contents
Table of contents
Legal information ......................................................................................................... 2
1 Task ..................................................................................................................... 4
2 Solution............................................................................................................... 6
2.1 Overview............................................................................................... 6
2.2 Description of the core functionality ..................................................... 7
3 Basic principles ................................................................................................. 8
3.1 Configuration Guide ............................................................................. 8
3.2 Editors ................................................................................................ 13
3.2.1 PCS 7 DBA AS Node Type Wizard .................................................... 13
3.2.2 PCS 7 DBA ......................................................................................... 14
3.2.3 PCS 7 DBA Type Editor ..................................................................... 15
4 Connecting an existing ABB Freelance DCS ................................................ 16
4.1 Acquiring data .................................................................................... 17
4.2 Generating OS block icons and faceplates ........................................ 21
4.3 Determining OPC data ....................................................................... 22
4.4 Generating the AS node with the AS Node Type Wizard .................. 25
4.4.1 General tab ......................................................................................... 25
4.4.2 Instance Source tab ........................................................................... 26
4.4.3 Connections tab ................................................................................. 27
4.4.4 "Addressing" tab ................................................................................. 28

4.5 Creating the AS node ......................................................................... 29
4.6 Generating AS object types ............................................................... 31
4.6.1 Creating a new type ........................................................................... 32
4.6.2 Including default types........................................................................ 33
4.6.3 Creating tags ...................................................................................... 34
4.6.4 Configuring alarms ............................................................................. 36
4.6.5 "Attributes" tab .................................................................................... 40
4.7 Creating ASO instances ..................................................................... 41
5 Configuring the PC station with the DBA...................................................... 44
5.1 Adding a PC Station ........................................................................... 44
5.2 Creating a plant hierarchy .................................................................. 46
5.2.1 Setting project properties ................................................................... 46
5.2.2 Synchronizing the plant hierarchy ...................................................... 48
5.2.3 Extending the plant hierarchy ............................................................. 49
5.2.4 Assigning plant hierarchy to an OS .................................................... 49
5.2.5 Assigning AS object instances ........................................................... 50
5.2.6 Editing object attributes ...................................................................... 51
5.2.7 Compiling the OS ............................................................................... 51
5.3 PCS 7 operator station ....................................................................... 53
6 Appendix .......................................................................................................... 56
6.1 Service and support ........................................................................... 56
6.2 Industry Mall ....................................................................................... 57
6.3 Literature ............................................................................................ 57
6.4 History ................................................................................................ 57

Entry ID: 49740087, V1.1, 06/2021 3
1 Task
1 Task
Introduction
System landscapes that have grown over time often consist of heterogeneous
automation technologies. This results in the requirement that devices which contain
controllers from competitors can also be operated and monitored using a PCS 7
operator system.
SIMATIC PCS 7/OPEN OS is a PCS 7 option with which controllers that do not
belong to the spectrum of SIMATIC PCS 7 system components, can be integrated
into the PCS 7 process control.
PCS 7/OPEN OS V9.0 enables the data exchange between the PCS 7 operator
station and various automation systems via all available WinCC channels. For
third-party systems that can only be integrated via the OPC channel, only the
appropriate OPC server for the particular controller type is necessary.
PCS 7/OPEN OS supports the data exchange with the controllers via Classic
OPC DA and Classic OPC A&E as well as OPC UA DA.
The core of PCS 7/OPEN OS is based on the database automation software (DBA)
familiar from other OS options. This software is mainly composed of the following
components:
• SIMATIC PCS 7 OS engineering and runtime software
• PCS 7/OPEN OS DBA data base automation software
• PCS 7/OPEN OS runtime software option
The supplied base functionality of PCS 7/OPEN OS allows configuration engineers

to effectively integrate the existing third-party controllers into the process control
using the PCS 7 operator system. This gives operators the option of operating and
monitoring the entire system from a single operator system, even if it contains
subareas with controllers from third-party manufacturers.

Entry ID: 49740087, V1.1, 06/2021 4
1 Task
Overview of the automation task

An ABB Freelance DCS should be operated and monitored using the SIMATIC
PCS 7 operator system. The integration of the system into the PCS 7 landscape
will take place using SIMATIC PCS 7/OPEN OS via OPC.
Figure 1-1
ABB Freelance DCS
PCS 7 Operator Station ABB
Alternative without PCS 7/OPEN OS

You can learn how to establish an AS/AS communication between an S7-400
Controller and an AC 800F Controller in the following article:
https://support.industry.siemens.com/cs/ww/en/view/39168210
Figure 1-2
Please note, however, that this variant represents a high configuration effort on the
part of the PCS 7 AS and the ABB Controller.

Entry ID: 49740087, V1.1, 06/2021 5
2 Solution
2 Solution
Using the PCS 7 SIMATIC PCS 7/OPEN OS option, this application example will
show you how you can effectively integrate third-party controllers into the PCS 7
system landscape.
2.1 Overview
The example contained in this document shows you how to integrate an existing
device with an ABB Freelance DCS into an existing PCS 7 landscape.
The integration of the ABB system occurs with the aid of the OPC channel of
the PCS 7 operator station.
Figure 2-1
PCS 7 ES, PCS 7 OS
PCS 7/OPEN OS Client
Engineering
Terminal bus (Industrial Ethernet)

PCS 7 OS Server OPC Server

PCS 7/OPEN OS Server
Plant bus (Industrial Ethernet)
ABB
Freelance DCS
ABB
PCS 7 AS
ET 200M
PROFIBUS DP
Advantages
The solution presented in this document offers you the following advantages:
• Complete integration of controllers that do not conform to PCS 7 into the
PCS 7 operator system.
• Step by step instruction for configuration with PCS 7/OPEN OS.
• Shared alarm and tag logging management of PCS 7 and third-party systems
on one operator system.

Entry ID: 49740087, V1.1, 06/2021 6
2 Solution
Required experience
The following basic knowledge is required:
• Systems configuration with PCS 7 AS engineering
• Generation of a visualization with PCS 7 OS engineering
• Basic knowledge of the third-party system
2.2 Description of the core functionality

A core component for the PCS 7/OPEN OS engineering is the
PCS 7/OPEN OS DBA database automation software.
The DBA generates OS data such as:
• Plant hierarchy
• Tags and archive tags
• Connections
• Alarms and messages
The DBA can use the channels available in the PCS 7 OS to connect the systems
that are not PCS 7-conform. For example, drivers are integrated in WinCC for the
following third-party controllers:
• SIMATIC 505
• Allen Bradley
• Mitsubishi
• …
Third-party systems for which no special connections exist can use the OPC or
Modbus TCP open standards. In this application, a third-party system of the
manufacturer ABB is connected with the aid of OPC.

Entry ID: 49740087, V1.1, 06/2021 7
3 Basic principles
3 Basic principles
3.1 Configuration Guide
You will find here an overview of the steps necessary for integrating a third-party
system into the PCS 7 operator station using PCS 7/OPEN OS.
Table 3-1
No. Description
1. Collecting data
Before you start configuring, you need the following information in order to operate
and monitor the third-party system:
• Access type (S7 connection, OPC DA, OPC A&E, ...)
• Network addresses (OPC server, automation systems)
• Syntax of tag addresses
• Tags, interfaces, alarms
• Project file path of the target operator system
• Plant hierarchy
2. Generating OS block icons and faceplates
Using the available knowledge of the structure of the objects (type of objects
and related tags) in the AS, you can generate the block icons and faceplates.
The symbols are stored in a typical file and the individual views of the faceplates are
generated in conformance with PCS 7.
Further information on the generation of symbols and faceplates can be found in the
"SIMATIC Process Control System PCS 7 APL Style Guide" configuration
instructions in the following article:
Note
It is imperative that this work be completed before the initial compilation of the plant
hierarchy.
3. Generating the AS node type
You will generate the AS node type using the AS Node Type Wizard. The Wizard
already contains information about the channel used and the corresponding
connections as well as the syntax of the tag addresses.
4. Creating the AS node
In the AS View of the DBA, you will generate an instance of the previously
generated AS node type. Depending on the setting, you may still be able to adjust
the connection parameters and assign an instance name in this view.
5. Generating AS object types
The AS objects (ASO) represent the objects present in the automation system, e.g.
motors, valves, closed-loop controllers, analog and digital values, and are
connected to the AS node type.
The ASO types can contain tag addresses, the tag format, tag attributes, and tag
alarms and messages.

Entry ID: 49740087, V1.1, 06/2021 8
3 Basic principles
No. Description
6. Creating ASO instances
Create the ASO instances. These instances are always assigned to an AS node.
7. Creating a PC station
In the PC-Station View of the DBA, you can define the OS project to which the data
will be compiled. Here, you will set the project path of the target system and also
specify a data log if one exists.
8. Specifying the plant hierarchy
An existing plant hierarchy can be read out from the SIMATIC project and
synchronized with the DBA project. In the Plant View of the DBA, you can then
create additional hierarchy folders and subsequently synchronize them with the
SIMATIC project again.
9. Assigning ASO instances to the plant hierarchy
Drag the ASO instance to the corresponding hierarchy folder in the Plant View.
By doing so, you create the relation of the AS objects to the operator system.
Depending on the mode of configuration, you may still be able to assign or adjust
tag addresses and attributes.
10. Compiling the DBA project
This process corresponds to that of the OS compilation from the SIMATIC Manager.
Here, the necessary connections, tags, messages and icons are created in the OS
project.
11. Loading the OS and starting the runtime
If all sequences have been executed properly, the OS project can be loaded and
the OS runtime can be started.

Entry ID: 49740087, V1.1, 06/2021 9
3 Basic principles
Table 3-2
No. Description
1. Collecting data
Before you start configuring, you need the following information in order to operate
and monitor the third-party system:
• Access type (S7 connection, OPC DA, OPC A&E, ...)
• Network addresses (OPC server, automation systems)
• Syntax of tag addresses
• Tags, interfaces, alarms
• Project file path of the target operator system
• Plant hierarchy
2. Generating OS block icons and faceplates
Using the available knowledge of the structure of the objects (type of objects
and related tags) in the AS, you can generate the block icons and faceplates.
The symbols are stored in a typical file and the individual views of the faceplates
are generated in conformance with PCS 7.
Further information on the generation of symbols and faceplates can be found in
the "SIMATIC Process Control System PCS 7 APL Style Guide" configuration
instructions in the following article:
Note
It is imperative that this work be completed before the initial compilation of the
plant hierarchy.
3. Generating the AS node type
You will generate the AS node type using the AS Node Type Wizard. The Wizard
already contains information about the channel used and the corresponding
connections as well as the syntax of the tag addresses.
4. Creating the AS node
In the AS View of the DBA, you will generate an instance of the previously
generated AS node type. Depending on the setting, you may still be able to adjust
the connection parameters and assign an instance name in this view.
5. Generating AS object types
The AS objects (ASO) represent the objects present in the automation system,
e.g. motors, valves, closed-loop controllers, analog and digital values, and are
connected to the AS node type.
The ASO types can contain tag addresses, the tag format, tag attributes, and tag
alarms and messages.
6. Creating ASO instances
Create the ASO instances. These instances are always assigned to an AS node.
7. Creating a PC station
In the PC-Station View of the DBA, you can define the OS project to which the
data will be compiled. Here, you will set the project path of the target system and
also specify a data log if one exists.

Entry ID: 49740087, V1.1, 06/2021 10
3 Basic principles
8. Specifying the plant hierarchy
An existing plant hierarchy can be read out from the SIMATIC project and
synchronized with the DBA project. In the Plant View of the DBA, you can then
create additional hierarchy folders and subsequently synchronize them with the
SIMATIC project again.
9. Assigning ASO instances to the plant hierarchy
Drag the ASO instance to the corresponding hierarchy folder in the Plant View.
By doing so, you create the relation of the AS objects to the operator system.
Depending on the mode of configuration, you may still be able to assign or adjust
tag addresses and attributes.
10. Compiling the DBA project
This process corresponds to that of the OS compilation from the SIMATIC

Manager. Here, the necessary connections, tags, messages and icons are created
in the OS project.
11. Loading the OS and starting the runtime
If all sequences have been executed properly, the OS project can be loaded and
the OS runtime can be started.

Entry ID: 49740087, V1.1, 06/2021 11
3 Basic principles
The following flow diagram shows the procedure for configuring third-party systems
using SIMATIC PCS 7/OPEN OS in abbreviated form.
Figure 3-1

Entry ID: 49740087, V1.1, 06/2021 12
3 Basic principles
3.2 Editors
PCS 7/OPEN OS includes the following editors, which are briefly described below:
• PCS 7 DBA AS Node Type Wizard
• PCS 7 DBA
• PCS 7 DBA Type Editor
3.2.1 PCS 7 DBA AS Node Type Wizard
You will generate the AS node types using the AS Node Type Wizard.
Here, the following information will be stored:
• AS name
• Typical display
• Instance source (DBA or XML)
• Connection parameters
• Address syntax
You start the AS Node Type Wizard at "Start > Siemens Automation > AS Node
Wizard".
You will find detailed information in the "PCS 7 Open OS Engineering Workflow
Guide" manual. The manuals are copied to your system during the OPEN OS
installation.
Figure 3-2

Entry ID: 49740087, V1.1, 06/2021 13
3 Basic principles
3.2.2 PCS 7 DBA
The DBA Editor is the heart of PCS 7/OPEN OS. This is where you configure the
AS structures and connect them to the PCS 7 operator system. Here, you must
carry out the following tasks:
• Create the AS node and AS object instances (ASO's)
• Generate the plant hierarchy and assign ASO instances
• Compile the DBA project
You can start the DBA at "Start > Siemens Automation > PCS 7 DBA".
You will find detailed information in the "PCS 7 Open OS DBA" manual.
The manuals are copied to your system during the OPEN OS installation.
Figure 3-3

Entry ID: 49740087, V1.1, 06/2021 14
3 Basic principles
3.2.3 PCS 7 DBA Type Editor
Using the DBA Type Editor, you can generate the AS objects, which map the
structure of the blocks in the third-party system. They contain:
• Tags, possibly with addresses
• Enumerations
• Alarms and messages
• Attributes
• Runtime scripts
You can start the Editor via the shortcut menu of an AS node in the DBA by
selecting the "Edit AS Object Types..." item.
You will find detailed information in the "PCS 7 Open OS DBA Type Editor"
manual. The manuals are copied to your system during the OPEN OS installation.
Figure 3-4

Entry ID: 49740087, V1.1, 06/2021 15
4 Connecting an existing ABB Freelance DCS
4 Connecting an existing ABB Freelance

DCS
The following chapters describe how to integrate an ABB system into PCS 7 using
OPEN OS. The Freelance project used in this example is a getting started project
from ABB and is provided solely for demonstration purposes. However, the basic
procedure for existing plant units with an ABB controller is largely identical.
For configuring with OPEN OS, the Freelance system must be pre-configured with
a gateway station and the necessary tags for the gateway must be enabled.
The Freelance OPC server is started on the gateway station.
The ABB project represents a simple waterworks system. It consists of an inlet,

an outlet and a tank. The following components have been used for the project:
• Fill level sensor (1)

• Pump drives (2)
• Pressure sensors (3)
• Flow sensors (4)
• Motor valves (5)
Figure 4-1
5
2
3
The pump drive at the inlet line is controlled in automatic mode through the fill
level. The motor turns on when a lower limit is underranged, and it only turns off
again when an upper limit is exceeded. The inlet valve is positioned by means of
a continuous controller.
No automatic mode is intended to be operated at the valve and pump drive outlet.
These are manually operated at the operator station.

Entry ID: 49740087, V1.1, 06/2021 16
4.1 Acquiring data

This example project contains the following components, which are relevant for
operation and monitoring at the OS:
Table 4-1
Type Name Block Description
Pump drive NP10 IDF_1 Inlet pump drive
Flow sensor FI10 M_ANA Inlet flow rate detection
Pressure sensor PI10 M_ANA Inlet pressure detection
Motor valve NS10 IDF_A Inlet control valve
Fill level sensor LI10 M_ANA Vessel fill level
Controller LC10 C_CS Controller for the fill level
Pump drive NP21 IDF_1 Outlet pump drive
Flow sensor FI21 M_ANA Outlet flow rate detection
Pressure sensor PI21 M_ANA Outlet pressure detection
Motor valve NS21 IDF_A Outlet control valve
The different objects always have a drive control block as a basis. The type of the
drive control block can be found in table 4-1. You will find a detailed description of
the blocks in the Freelance documentation.
This information makes it possible to derive a structure from the instances of the
blocks. Using the example of the analog measuring point, the tag syntax would be
the following:
Pressure sensor PI10
– PI10/IN
– PI10/LI1
– PI10/LI2
– …
Fill level sensor LI10
– LI10/IN
– LI10/LI1
– LI10/LI2
– …
The following tables show the required connections of the individual motor blocks,
valves and analog value detections for configuration with OPEN OS.
The information has been taken from the Commissioning Manual of the ABB block
library.

Entry ID: 49740087, V1.1, 06/2021 17
Single control function for 1 direction IDF_1 (motor)

The following connections, provided by the IDF_1 block, are relevant for
configuring with OPEN OS:
Table 4-2
Tag Type Type Access Description
FB1 BOOL IN RW Feedback end position 1
PR1 BOOL IN RW Safety intervention 1
FLT BOOL IN RW Error
IL1 BOOL IN RW Interlock for command 1
IL0 BOOL IN RW Interlock for command 0
LOC BOOL IN RW Local intervention
OUT BOOL OUT RO Control command
SMA BOOL OUT RO Operating mode (1=Automatic)
FRT BOOL OUT RO Runtime error
FEP BOOL OUT RO Limit position error
Hi INT Param RW Manual input (1=on)

Pha INT Param RW Manual/Automatic (0=Manual; 1=Automatic)
Leu BOOL Param RW Runtime monitoring (1=on)
Lz INT Param RW Runtime in ms
MonEP BOOL Param RW Limit monitoring
Lrp BOOL Param RO Positive running direction
Lrn BOOL Param RO Negative running direction
SQ BOOL Param RW Safety acknowledgment
The block can flag the following states, but not all need to be configured:
• Error
• Duration
• Limit position
• Protection
• Local

Entry ID: 49740087, V1.1, 06/2021 18
Single control function for actuators IDF_A (motor valve)

The following connections, provided by the IDF_A block, are relevant for
Table 4-3
FLT BOOL IN RW Error
OUT1 BOOL OUT RO Control command 1
OUT0 BOOL OUT RO Control command 0
SMA BOOL OUT RO Operating mode (0=Manual; 1=Automatic)
FRT BOOL OUT RO Runtime error
FEP BOOL OUT RO Limit position error
FTQ BOOL OUT RO Torque error
Ra BOOL Param RW Feedback message (1=active)
TotZ INT Param RW Dead time for feedback message in ms

Hi INT Param RW Manual input (1=on)
Pha INT Param RW Manual/Automatic (0=Manual; 1=Automatic)
Leu BOOL Param RW Runtime monitoring (1=on)
MonEp BOOL Param RW Limit monitoring (1=on)
Lz INT Param RW Runtime in ms
Lrp BOOL Param RO Positive running direction (1=on)
Lrn BOOL Param RO Negative running direction (1=on)
RaS BOOL Param RO Feedback message Stop (1=Stop)
SQ BOOL Param RW Safety acknowledgment
The block can flag the following states, but not all need to be configured:
• Error
• Duration
• Limit position
• Protection
• Local
• Blockage

Entry ID: 49740087, V1.1, 06/2021 19
Analog monitoring M_ANA (Fill level, pressure, and flow sensors)

The following connections, provided by the M_ANA block, are relevant for
Table 4-4
IN REAL IN RW Input signal
DIS BOOL IN RW No limit value processing when TRUE
L1 REAL IN RW Limit 1
SL1 BOOL OUT RO Limit violation L1
ERR BOOL OUT RO Fault status
Hy1 REAL Param RW Hysteresis limit value 1

Mba REAL Param RW Measuring range start
Mbe REAL Param RW Measuring range end
Dim TEXT Param None Physical unit (only possible internally)
The block can be configured with four limit values that trigger a message when
a limit is exceeded or underrun.

Entry ID: 49740087, V1.1, 06/2021 20
4.2 Generating OS block icons and faceplates

You can generate OS block icons and faceplates with the aid of the WinCC
Graphics Designer. The process conforms to the PCS 7 standard. For this reason,
the topic is not discussed in greater detail in this documentation. Detailed
information on the generation of user-defined icons and faceplates can be found
in the "SIMATIC Process Control System PCS 7 APL Style Guide" manual in the
following article:
With the collected data from the ABB project, you can already generate the
dynamic objects in the WinCC icons and the faceplates with the right tags. Later,
when you generate the OS from the OPEN OS project, the block icons will be
linked to the right measuring points.
For the Typicals picture use a meaningful name, in accordance with the PCS 7
naming conventions. Select, for example, the name
"@ABBFreelance_Typicals.pdl" for the icon picture.
In this sample project, icons and faceplates have been created for the following
objects:
• Motor: ABBMOT (IDF_1)
• Valve: ABBVLVM (IDF_A)

• Analog value: ABBANA (ANA_M)
Figure 4-2

Entry ID: 49740087, V1.1, 06/2021 21
Figure 4-3
4.3 Determining OPC data

The following data is required for configuring with PCS 7/OPEN OS at a later
stage:
• PC name on which the OPC server is started
• Name of the connecting OPC servers (DA and A&E)
• Tag syntax
• Triggering conditions for messages
To determine the OPC server data you can use, for example, the SIMATIC NET
"OPC Scout V10" OPC client or any another OPC client. The OPC Scout can
be found on a PC with a SIMATIC NET installation in the Start menu under the
following path: "Start > Siemens Automation > OPC Scout V10".
After starting the OPC client you can search the entire network for available OPC
servers. In our example, the following two OPC servers are connected to the OPC
Scout:
• Freelance2000OPCServer.50 (OPC DA)
• Freelance2000OPCAEServer.50 (OPC A&E)

Entry ID: 49740087, V1.1, 06/2021 22
OPC Data Access

With the OPC Scout, you can test the connection to the OPC server and look at
individual tag values. The output window also shows the syntax which is used by
the OPC server to build the string of tags. In the case of the input tag for the tank
fill level, this is "LI10/IN". In this case, a "/" is used as a separator for the
construction of the tags. Please note that this may be different from OPC server
to OPC server. The OPC server also distinguishes strictly between upper and
lower case.
Figure 4-4

Entry ID: 49740087, V1.1, 06/2021 23
OPC Alarms & Events

In the Server Explorer of the OPC Scout, you can connect to the OPC A&E server
of the third-party system and identify the source and the triggering conditions of the
pending alarms. These are needed for the subsequent configuration of the alarms
with OPEN OS.
You can also use the OPC Scout to create an AE view. This displays the current
alarms of the OPC A&E server.
Figure 4-5

Entry ID: 49740087, V1.1, 06/2021 24
4.4 Generating the AS node with the AS Node Type Wizard

The AS node type is generated with the aid of the PCS 7 DBA AS Node Type
Wizard. You can find the editor in the Start menu at: "Start Siemens Automation >
AS Node Wizard". The type includes, for example, information about the
connection to the AS and the tag syntax.
The AS node type is not part of a specific DBA project and is therefore stored in
the installation directory of OPEN OS. You can use all the created AS node types
in each of your DBA projects. The following sections explain how to create an AS
node type.
4.4.1 General tab
In the "General" tab, you assign the name of the AS node type and define the
name of the typical picture from which the OS block icons are copied during
compilation.
• Enter the name for the AS node type.
• Enter the name of the WinCC screen that contains the generated picture
symbols.
Figure 4-6

Entry ID: 49740087, V1.1, 06/2021 25
4.4.2 Instance Source tab
This document only describes the "DBA Integrated Instances" option.

• Select the "DBA Integrated Instances" option.
Figure 4-7
You can find a description of the use of XML instances in the following article:
"How do you create an XML input file for automatic creation of instances in DBA?".

Entry ID: 49740087, V1.1, 06/2021 26
4.4.3 Connections tab
In our sample project, the OPC channel is used for the connection to the third-party
CPU. Make the following entries in the "channel & channel group":
• Select the "OPC channel" option.
• Choose the "Enable OPC A&E support" selection.
• Enter the name of the PC on which the OPC servers are running (DA and
A&E).
• Enter the name of the OPC server (DA and A&E).
In the "Connection" area you can enter a fixed connection name or use the
following tags for dynamization in the DBA:
• %SystemName%: The name of the AS node type is used ("General" tab)
• %ASName%: The name of the AS node is used that is entered in the DBA.
In the OS project, the connection is created under this name.
Figure 4-8

Entry ID: 49740087, V1.1, 06/2021 27
4.4.4 "Addressing" tab
In the Addressing tab, you can specify the structure of the tag addressing that
will be used when the project is compiled at a later point. In the case of the OPC
server, the AS address is not relevant and is ignored by the DBA.
Here, the DBA provides the ability to configure all conceivable constellations for
the parameterization of tag addresses. These range from a structured approach
and the free assignment of addresses for all tags, to the use of scripts that can
calculate the addresses individually.
The following tags can be used for the parameterization of the tag addresses:
• %ASName% – name of the AS node
• %ASOName% – name of the AS instance
• %Instance% - Instance address that is allocated during the creation of the
instance
• %Tagname% – name of the tags for which the address is calculated
• %Address% – value of the address field of the tags
• %Field#TagAddress% – value of the extended attribute. Input during
parameter assignment
• %Attribute:Name% – value of the extended attribute with the name "Name"
• %UID% – unique identifier for each AS-object generated by the DBA
• %OPCDataType% – OPC data type number for the tag type

• %UANamespace% - OPC UA adress-namespace
• %UAType% - OPC UA identifier type
• %UAValue% - OPC UA identifier
The program is arranged in the same structured manner as previously determined

during the establishment of the third-party system data. The tags can be derived
from the function blocks used, and are the same for each instance.
In WinCC, the address string for the OPC tags is composed of the following
components:
• Object name
• Access path
• Data type
The object name is formed from the instance and the tag name. The slash "/" is
used to separate the two of them. The access path is already stored in the
configured connection and therefore remains empty. The data type is appended
as a numeric value.
Therefore, in WinCC, the address string of the input value "IN" of the measuring
point "PI10" of the type "Float" in WinCC results as follows:
"PI10/IN","",4
In order to build the tag addresses correctly from the DBA, this example uses the
following construction:
%ASOName%/%TagName%

Entry ID: 49740087, V1.1, 06/2021 28
Figure 4-9
4.5 Creating the AS node

All created AS node types are stored in the OPEN OS system folder. From these
AS node types, you can now set up instances in DBA that represent the controls
of the third-party system. To set up the AS nodes in DBA, proceed as follows:
1. Open a new or existing project in DBA.

2. In the "AS View" tab of the component view, add a new AS node. Select the
"Add AS Source Node..." command in the shortcut menu.
3. Select an AS node type that has been previously created with the "AS Node
Type Wizard". In this case, it is the type for the ABB automation system.

Entry ID: 49740087, V1.1, 06/2021 29
Figure 4-10
4. Assign a name for the station.

5. If you have allowed the subsequent change of connection parameters during
the creation of the AS node type, you can configure these settings in the
"Connection" tab.
Figure 4-11
The new AS node has now been crated in the DBA AS View.

Entry ID: 49740087, V1.1, 06/2021 30
4.6 Generating AS object types

The AS object types in the DBA map the function blocks used in the AS. An ASO
type can be instantiated in the DBA as often as needed. Changes made to a type
effect all instances of the type. The following steps use a block for an analog value
measuring point to demonstrate how to generate this type. These tasks should
then be carried out for all the different blocks that are necessary.
The data established in the chapter "4.1 Acquiring data" are the basis
for generating the ASO types.
An ASO type can contain the following objects:
• Tags (type and address)
• Messages (message text, triggering event, accompanying values)
• Enumerations
• Attributes
• Runtime scripts
Start the DBA Type Editor by selecting the "Edit AS Object Types..." command
from the AS node shortcut menu.
Figure 4-12
Note The AS object parameters are assigned to an AS node type, however they are
linked to the project. If you wish to reuse the objects in another DBA project,
which uses the same AS node type, you can use the Export/Import function for
ASO types.

Entry ID: 49740087, V1.1, 06/2021 31
Some attributes and tags in DBA must be added to the AS objects so that later on
the third-party system objects behave as PCS 7 objects. To this end, the following
types have been already created by default in DBA:
• AlarmGroupDisplaySupport
• CommonMembers
• SymbolAndFaceplateExtendedAttributes
These types introduce tags or attributes which are required for managing alarms or
for managing block icons or faceplates. They can be connected (included) with any
type that these functionalities are intended to work with. It is recommended
additionally to work in a reference to the name of the third-party system.
Figure 4-13
The following sections contain more detailed descriptions of the "Tags, Messages,
Attributes, Includes, Docs and OS Runtime" tabs. In the "Docs" tab you can link
descriptions to your types in HTML format, and in the "OS Runtime" tab you can
add scripts for the OS runtime. You can find more detailed information about this
topic in the "PCS 7 Open OS DBA Type Editor" manual.
4.6.1 Creating a new type
To create a new type in the DBA Type Editor, click the "Add New Type" button.
The dialog window that is then displayed prompts you to enter the following data:
• AS Type Name – Choose a name that creates a relation to the object in
the AS.
• HMI Type Name – Choose a name that creates a relation to the object in
the OS. Please note that this must have the same name that you assigned
to the HMI symbol.

Entry ID: 49740087, V1.1, 06/2021 32
Figure 4-14
4.6.2 Including default types
With type inclusion, it is possible to add tags and attributes to the new types to
achieve specific functionalities.
These types are already included by default in all new types:
• CommonMembers
• SymbolAndFaceplateExtendedAttributes
All available types are displayed in the left-hand window and the already included
types are displayed in the right-hand window. If the block also features an alarm
function, include the "AlarmGroupDisplaySupport" type.
1. Select the "AlarmGroupDisplaySupport" type in the left-hand window.
2. Include the type by clicking the button (right pointing arrow).
Figure 4-15

Entry ID: 49740087, V1.1, 06/2021 33
The new type is now equipped with the basic functionality for PCS 7 blocks.
You can remove the functionality of the included types by clicking the "Left arrow"
button.
4.6.3 Creating tags
The tags form the interface from the OS to the OPC server. The tags are
configured in the "Tags" tab of the DBA Type Editor.
Figure 4-16
To add new tags, click the "Add" button. An additional dialog window is opened.
In the "General" tab, you can enter the following data:
• Name of the tag
• Data type
• WinCC type (default is structure tag)
• Source (external, internal, indirect)
• Runtime options
• Inclusion rules

Entry ID: 49740087, V1.1, 06/2021 34
The OPC tag address is composed of the measuring point name, the tag name and
the data type used. In the case of OPC connections, entries in the address field of
the Tag Editor are ignored for the construction of the tag addresses because the
address syntax has been defined as %ASOName%/%TagName% without using
this address field.
In the "Advanced" tab, you can configure additional settings for the tag:
• Upper and lower limit
• Start value
• Auxiliary tags (description, unit, ...)
• Archiving
The option "DBA-Edit" allows to customize the predetermind standard values while
instantiating the type.
Figure 4-17
Click the "OK" button to close the dialog window and create the type tag.

Entry ID: 49740087, V1.1, 06/2021 35
4.6.4 Configuring alarms
In the "Messages" tab, you can configure the process messages of the AS block.
The messages can be triggered by different tags or by means of an OPC A&E
server. You can configure the following parameters:
• Alarm name
• Message text
• Message class
• Priority
• Trigger tag
• Associated message values
Figure 4-18
To configure new messages at the ASO type, click the "Add" button.
A dialog window with the following tabs will then open.
• General
• Tags
• Process Vars
• Free Vars
"General" tab
Assign the following parameters in the "General" tab:
• Name
• Display name
• Message number – This should remain "0" so that a unique message number
is automatically assigned during compiling.
• Message class
• Priority
• Message text

Entry ID: 49740087, V1.1, 06/2021 36
Figure 4-19
Associated message values are integrated using the control commands known
from PCS 7. For example, associated value 1 of the floating-point number type:
@1%3.2f@.
The associated values must be declared in the "Process Vars" tab.
"Tags" tab
In the "Tags" tab, the triggering tags for the message in WinCC and the initiating
trigger in the AS are configured.

Entry ID: 49740087, V1.1, 06/2021 37
Figure 4-20
On the left-hand side, you can configure the trigger and optional acknowledge in
the controller for the OS – if the connected third-party system supports this. The
message behavior then corresponds to that of the PCS 7 blocks. Messages are
shown in the alarm group display and in the message line, and the "Loop in Alarm"
function can be used.
If you use an OPC Alarm & Events Server such as the one in this example, it is
enough to select this option. In the entry fields, enter the condition and/or the
subcondition. You can determine this information with the OPC Scout.
"Process Vars" tab

In this tab, you can configure the tags that you wish to use as associated values in
your message texts. The system provides 10 fields.
You may select any of the tags you created when generating the type.

Entry ID: 49740087, V1.1, 06/2021 38
Figure 4-21
"Free Vars" tab

In the "Free Tags" tab, you can parametrize constantly recurring text blocks, for
example. You can find further information in the WinCC Alarm Logging description.

Entry ID: 49740087, V1.1, 06/2021 39
4.6.5 "Attributes" tab
The attributes determine the behavior of a tag, a message or the instance of

a type. Most attributes are automatically created during the generation of tags and
messages or copied during the inclusion of other types. It is not necessary to make
changes to these attributes. By default, attributes generated by the system are not
displayed. You can display these attributes by activating the "Show All Attributes"
selection box.
You will find detailed information about the attributes in the "PCS 7 Open OS DBA
Type Editor" manual under chapter 6.5 "Working with the Attribute Editor".
Figure 4-22

Entry ID: 49740087, V1.1, 06/2021 40
4.7 Creating ASO instances

The ASO types created in the previous chapter emulate the function blocks of
the ABB system. You can set up any number of instances from these ASO types.
Open the AS node shortcut menu and select the "Create New AS Object..."
command.
Figure 4-23
Enter the following data in the "Single Instance Editor" dialog window:
• Name of the instance (choose a name that you can associate with the AS
program)
• ASO type
Note The OPC tag addresses are generated as follows, depending on how it was
configured in the DBA AS Node Type Wizard:
"<ASOName>/<TagName>", "", <Datentyp>
For example, the tag string for the input tag IN of the type Float of the analog
value measuring point M_ANA with the instance name PI10 would look like this:
"PI10/IN", "", 4
Carry out these steps for all required objects.

Entry ID: 49740087, V1.1, 06/2021 41
Figure 4-24
Whenever changes are made to the settings of the AS node, to the related types
or to the instances created, the text "(changed)" is added to the AS node as a note.
Note With the "DBA Object Inspector", you can read out information about which data
was created on the OS. For example, you can already verify whether the
structure of the address syntax is correct.
The command to open the "DBA Object Inspector" can be found in the shortcut
menu of an AS node or an ASO instance.

Entry ID: 49740087, V1.1, 06/2021 42
By calling the "Update Controller Objects" function from the AS node shortcut
menu, you can update all instances of the AS object.
Figure 4-25
The configuration of the AS part for the ABB subsystem is now complete.
In the next chapter you will learn how to configure the OS part with DBA.

Entry ID: 49740087, V1.1, 06/2021 43
5 Configuring the PC station with the DBA

The PC station in the DBA Editor serves as an interface to the operator station
on which the third-party system is operated and monitored.
To create a PC station in the DBA, you first need a PCS 7 project complete with
an operator system and a plant hierarchy. This could be an already finished project
that should be extended to a plant section with a Third-Party system, or a newly
created project.
5.1 Adding a PC Station

To create a new PC station in the DBA, follow the steps below:
1. Switch to the "PC Station View" tab.

2. Select the "Add PC-Station" command in the DBA project shortcut menu.
Figure 5-1
3. Assign the name of your OS to the PC station

4. Also insert the computer name of the OS in the "Computer Name" line in the
"Value" column.
Figure 5-2
5. Select "Add Application" from the context menu of the PC station. A dialog
window will then open.

Entry ID: 49740087, V1.1, 06/2021 44
6. Select the "PCS 7 OS (Server/Single Station)" project type and click "OK" in
the dialog window to confirm your selection. Name the application using the
name of the corresponding OS project in the SIMATIC Manager.
Figure 5-3
7. You can link the DBA project to the PCS 7 OS project by entering the path for
the OS project at the "Offline MCP File" line in the "Value" column.
8. By clicking the "..." button you can navigate to the OS project with the aid of
a file selection dialog window and then insert the path string.
Figure 5-4
9. Update the project data in the DBA by selecting the "Refresh OS Cache"
function in the shortcut menu. This function opens the PCS 7 OS project, reads
the alarm classes, alarm types and Tag Logging archive information, and
saves all of this information in the DBA project.
Figure 5-5

Entry ID: 49740087, V1.1, 06/2021 45
10. Select a Tag Logging archive if one is present.
Figure 5-6
5.2 Creating a plant hierarchy

In the DBA, you can use the plant hierarchy to define the picture hierarchy as it
appears on the OS. It is possible to use and extend an existing hierarchy from
a PCS 7 project or to generate a new hierarchy.
You will find detailed information in the PCS 7 Open OS DBA user manual.
In this example, an existing PH will be extended.
5.2.1 Setting project properties
1. Click the "Change Project Properties" button.
Figure 5-7
2. In the "General" tab, you can define the project and the project path with which
you intend to synchronize the PH. With the "Automatic Synchronize with
Simatic Plant View" option, you can trigger an automatic synchronization
with each compiling operation.

Entry ID: 49740087, V1.1, 06/2021 46
Figure 5-8
3. In the "Hierarchy" tab, you can configure the PH (2) settings. Here, you must
choose the same settings as the ones of the PCS 7 project In SIMATIC
Manager (1).
Figure 5-9
4. Click the "OK" button to confirm the settings.

Entry ID: 49740087, V1.1, 06/2021 47
5.2.2 Synchronizing the plant hierarchy
Select the "Synchronize Plant View" command in the DBA project shortcut menu.
Figure 5-10
In this case, the PH is read from the PCS 7 project and created in the DBA, since
no hierarchy was present.
Figure 5-11

Entry ID: 49740087, V1.1, 06/2021 48
5.2.3 Extending the plant hierarchy
You will now extend the loaded hierarchy to include the hierarchy of the third-party
system. By selecting the "Add Folder" command in the shortcut menu, you can
create additional hierarchy folders. Every new folder is automatically assigned
an OS picture with the name of the folder.
Add additional hierarchy folders according to your plant structure.
Figure 5-12
If you have not enabled automatic synchronizing, you should synchronize the PH
with the OS project again after expanding it in DBA.
Note PH synchronization can only be used to add folders. If you wish to remove
existing folders, you must delete them in the SIMATIC project and in the DBA.
5.2.4 Assigning plant hierarchy to an OS
If multiple OS projects have been created, it is possible to select a specific OS for

each hierarchy folder. Lower-level hierarchy folders inherit the setting of higher-
level folders.
To assign a hierarchy folder to an OS project, select the "Edit Folder Properties..."
command in the shortcut menu of the relevant folder. In the dialog window that
then opens, you can select an OS project for the chosen PH folder and its
subfolder.

Entry ID: 49740087, V1.1, 06/2021 49
Figure 5-13
5.2.5 Assigning AS object instances
There are various ways to assign the process objects of the automation system
to the PH. The simplest version is to drag-and-drop the objects from the AS View
to the corresponding hierarchy folder.
Figure 5-14

Entry ID: 49740087, V1.1, 06/2021 50
Drag all AS objects from the designated hierarchy folder. The changes to the plant
hierarchy are indicated in the Plant View by a green background. This means that
the OS project still needs to be compiled at a later point in time.
5.2.6 Editing object attributes
Each AS object has attributes assigned to it, which determine its behavior during
the display in the OS. They can have values pre-assigned to them and can be
edited in DBA for each instance, if this has provided in the appropriate type.
Figure 5-15
To edit the attributes, select one of the AS objects assigned to the hierarchy.
Attributes are grouped into thematic groups and displayed in different tabs to give
a better overview. In the "Graphics" tab you can specify a different symbol variant
(e.g. vertical instead of horizontal valves) or change the unit of the measuring point.
In the "Alarm Messages" tab you can even customize the message text and the
message class.
5.2.7 Compiling the OS
With the Compile OS function, all objects configured in the DBA (tags, symbols,
messages) are created in the OS project. Click the button with the triangle pointing
to the right:

Entry ID: 49740087, V1.1, 06/2021 51
Figure 5-16
In the dialog window that then opens, you can still configure the usual SIMATIC
Manager settings for an entire compilation or the compilation of changes.
After confirming the settings with the "Compile" button, you can track the progress
in another dialog from the OS compilation. If the compiling process cannot be
executed in an error-free manner, you can see the log by activating the "Show
Details" option.
Figure 5-17

Entry ID: 49740087, V1.1, 06/2021 52
5.3 PCS 7 operator station

When you now open the OS project on the Engineering Station, all connections (1),
tags (2), messages (3), process pictures with the used block symbols should be
created.
Figure 5-18
1

Entry ID: 49740087, V1.1, 06/2021 53
Finally, open all process pictures created by DBA. In this example, only the image
"ABBPlant.pdl" was created. You can now see that a symbol has been placed side
by side at the top of the screen (beginning from the left) for each measuring point,
each motor and each valve.
Now draw the process pictures according to your requirements and move the icons
to the positions provided.
Figure 5-19

Entry ID: 49740087, V1.1, 06/2021 54
When all work is completed, you can transfer the project to the OS with the
SIMATIC Manager and start the runtime over there. If everything was done
correctly and the OPC connection is made, the process of the third-party system
is displayed on the OS and can also be operated there.
Figure 5-20

Entry ID: 49740087, V1.1, 06/2021 55
6 Appendix
6 Appendix
6.1 Service and support
Industry Online Support
Do you have any questions or need assistance?
Siemens Industry Online Support offers round the clock access to our entire
service and support know-how and portfolio.
The Industry Online Support is the central address for information about our
products, solutions and services.
Product information, manuals, downloads, FAQs, application examples and videos
– all information is accessible 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
Service offer
Our range of services includes the following:
• Plant data services
• Spare parts services
• Repair services
• On-site and maintenance services
• Retrofitting and modernization services
• Service programs and contracts
You can find detailed information on our range of services in the service catalog
web page:
support.industry.siemens.com/cs/sc
Industry Online Support app

You will receive optimum support wherever you are with the "Siemens Industry
Online Support" app. The app is available for iOS and Android:
support.industry.siemens.com/cs/ww/en/sc/2067

Entry ID: 49740087, V1.1, 06/2021 56
6 Appendix
6.2 Industry Mall
The Siemens Industry Mall is the platform on which the entire siemens Industry
product portfolio is accessible. From the selection of products to the order and the
delivery tracking, the Industry Mall enables the complete purchasing processing –
directly and independently of time and location:
mall.industry.siemens.com
6.3 Literature
Table 6–1
Subject area Title

\1\ Siemens Industry https://support.industry.siemens.com
Online Support
\2\ Download page of this https://support.industry.siemens.com/cs/ww/en/view/49740087
entry
\3\ SIMATIC PCS 7 in https://support.industry.siemens.com/cs/ww/en/view/63481413
Industry Online
Support
\4\ SIMATIC https://support.industry.siemens.com/cs/ww/en/view/109750265
PCS 7/OPEN OS
Delivery Release
\5\ Download SIMATIC https://support.industry.siemens.com/cs/ww/en/view/109781622
PCS 7/OPEN OS
V9.0+Update 1
\6\ SIMATIC Process https://support.industry.siemens.com/cs/ww/en/view/65601446
Control System
PCS 7 APL Style
Guide
6.4 History
Table 6–2
Version Date Change
V1.0 04/2014 First edition
V1.1 06/2021 Update to PCS 7/OPEN OS V9.9

Entry ID: 49740087, V1.1, 06/2021 57

PCS7 OpenOS 3rdparty Integration ABB V9.0 en

Uploaded by

Copyright:

Available Formats

PCS7 OpenOS 3rdparty Integration ABB V9.0 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

PCS7 OpenOS 3rdparty Integration ABB V9.0 en

Uploaded by

Copyright:

Available Formats

Integration of an ABB

ABB Freelance PLC integration with PCS 7/OPEN OS

4.4.4 "Addressing" tab ................................................................................. 28

ABB Freelance PLC integration with PCS 7/OPEN OS

• PCS 7/OPEN OS runtime software option

The supplied base functionality of PCS 7/OPEN OS allows configuration engineers

ABB Freelance PLC integration with PCS 7/OPEN OS

Overview of the automation task

Alternative without PCS 7/OPEN OS

ABB Freelance PLC integration with PCS 7/OPEN OS

Terminal bus (Industrial Ethernet)

PCS 7 OS Server OPC Server

Plant bus (Industrial Ethernet)

ABB Freelance PLC integration with PCS 7/OPEN OS

2.2 Description of the core functionality

ABB Freelance PLC integration with PCS 7/OPEN OS

2. Generating OS block icons and faceplates

ABB Freelance PLC integration with PCS 7/OPEN OS

ABB Freelance PLC integration with PCS 7/OPEN OS

ABB Freelance PLC integration with PCS 7/OPEN OS

8. Specifying the plant hierarchy

This process corresponds to that of the OS compilation from the SIMATIC

ABB Freelance PLC integration with PCS 7/OPEN OS

ABB Freelance PLC integration with PCS 7/OPEN OS

3.2.1 PCS 7 DBA AS Node Type Wizard

ABB Freelance PLC integration with PCS 7/OPEN OS

3.2.2 PCS 7 DBA

ABB Freelance PLC integration with PCS 7/OPEN OS

3.2.3 PCS 7 DBA Type Editor

ABB Freelance PLC integration with PCS 7/OPEN OS

4 Connecting an existing ABB Freelance

The ABB project represents a simple waterworks system. It consists of an inlet,

• Fill level sensor (1)

• Motor valves (5)

ABB Freelance PLC integration with PCS 7/OPEN OS

4.1 Acquiring data

ABB Freelance PLC integration with PCS 7/OPEN OS

Single control function for 1 direction IDF_1 (motor)

Hi INT Param RW Manual input (1=on)

ABB Freelance PLC integration with PCS 7/OPEN OS

Single control function for actuators IDF_A (motor valve)

TotZ INT Param RW Dead time for feedback message in ms

ABB Freelance PLC integration with PCS 7/OPEN OS

Analog monitoring M_ANA (Fill level, pressure, and flow sensors)

Hy2 REAL Param RW Hysteresis limit value 2

ABB Freelance PLC integration with PCS 7/OPEN OS

4.2 Generating OS block icons and faceplates

• Valve: ABBVLVM (IDF_A)

ABB Freelance PLC integration with PCS 7/OPEN OS

4.3 Determining OPC data

ABB Freelance PLC integration with PCS 7/OPEN OS

OPC Data Access

ABB Freelance PLC integration with PCS 7/OPEN OS

OPC Alarms & Events

ABB Freelance PLC integration with PCS 7/OPEN OS

4.4 Generating the AS node with the AS Node Type Wizard

4.4.1 General tab

ABB Freelance PLC integration with PCS 7/OPEN OS

4.4.2 Instance Source tab