Section 2 OPC Server

Installation of OPC Server

Section 2 OPC Server

An OPC server is used to make process data from a Control Builder F project
available to other systems via the OPC interface.

Installation of OPC Server

In the Freelance set up, if the OPC Server is selected in the Workplace type, OPC
Server is installed,
For further details refer to Getting Started

Configure window.
The OPC server is configured in the Configure window with a unique resource ID.
OPC server is downloaded to the Process station.

3BDD012511R0401_Eng_Manual_OPC_Server_F

19

Configure window.

Section 2 OPC Server

ABB_config_OPC

Select > Start > Programs >ABB Industrial IT > Freelance V9.2 > Configure

20

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

ABB OPC Tunnel Configuration

Select > Start >Programs >ABB Industrial IT > Freelance V9.2> ABB
Configure> OPC- Server Options > New resource ID
New resource ID

Current version of the OPC server is downloaded to the process station with the
unique resource ID.

ABB OPC Tunnel Configuration

The Resource ID for the OPC Server is set in Configure. In order to start the OPC
Tunnel the PROG ID for the server has to be configured in ABB OPC Tunnel
Configurator as [Link], where xxx is the Resource ID of
the OPC Server(s)
Select > Start > Programs >ABB Industrial IT > Freelance> OPC Tunnel >
Configurator
ABB OPC Tunnel Configurator appears as an icon in the right bottom side of the
system. ABB OPC Tunnel Configurator provides Restart server to restart the
Server.

3BDD012511R0401_Eng_Manual_OPC_Server_F

21

Configuration using Control Builder F

Section 2 OPC Server

Configuration using Control Builder F

In order to make the data from a project available to other systems, a gateway must
be configured in the Control Builder F project. A gateway resource is entered and
subsequently configured in the project tree to determine which tags and variables
can be accessed via this gateway.
Server software must be installed on the gateway station. This software
communicates with the AC 800F and the Freelance process stations and supplies the
data 'to the outside' over the OPC interface.
In order to implement an OPC server interface, a gateway of type OPC is configured
in the Control Builder F project tree. The OPC-Server F software is installed on the
OPC gateway computer. Following this, the configured project data is downloaded
to the OPC gateway with Control Builder F in commissioning mode. Immediately
after downloading, the Freelance data can be accessed via the OPC interface.

22

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Adding a gateway station

Adding a gateway station

Add the station resource Gateway Station D-GS in the project tree > Set up an
OPC type gateway

[Link]

Name

Name of the gateway station, max. 4 characters

Short text

max. 12 characters

Version

Date and time the object was created

Drawing footer/ Drawing header

Enter the drawing footer or header, see Engineering Manual System
Configuration, Documentation.
Access Rights Read and/or write rights for the gateway; default access for new
variables / tags
Type

Type of gateway station. Select OPC gateway. Additional the

following types are available: DCP gateway, DDE gateway and UNI
gateway.

3BDD012511R0401_Eng_Manual_OPC_Server_F

23

Access rights for a gateway

Port number

Section 2 OPC Server

Port number for the ABB OPC tunnel communication. Default

value is 9950.

Short comment Enter the short comment, see Engineering Manual System
Configuration.

Access rights for a gateway

[Link]

Read only

The gateway is only allowed read access to the process variables.

Any write accesses that are configured on the process stations,
variables and tags are ignored.

Access

A parameter is set for every process station that is already

configured in the project to specify whether read-only access or
read/write access is permitted. If read-only (not write) access is
specified for a process station here, then any write accesses that are
configured on the variables and tags are ignored. The parameter
read-only for the entire gateway overrides any write access that is
defined here.

Default access for new variables / tags

All newly-created variables and tags are by default assigned the
access rights defined here for this gateway.
Variables that are written via a gateway may not be simultaneously written via
the process image. The values of such variables are thus not capable of redundant
operation. If these variables are used in a redundant task, then they should be
duplicated to other variables.

24

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Adding the gateway station to the hardware structure

Adding the gateway station to the hardware structure

A free space within the control level must be selected in the hardware editor's
system view, and this must be assigned to a gateway resource that has already been
created in the project tree.

[Link]

Network addresses
Within the hardware editor, the stations' IP addresses and resource IDs are
configured under Network. The values specified here must correspond to the
parameters defined during the installation of the OPC server software.

Enabling tags and variables for OPC access

A parameter is defined for every tag and every variable in the project to specify
whether the data from the process station can be only read or read/written via the
gateway.

3BDD012511R0401_Eng_Manual_OPC_Server_F

25

Enabling tags and variables for OPC access

Section 2 OPC Server

In station view (Tag list or Variable list > Station view), the permitted access modes
through a gateway can be defined for each list entry. The station accesses that have
been defined are indicated in the variable list and tag list by single letters:
R

Read

Write

A double-click with the left mouse button in a gateway column or positioning the
cursor in a line and choosing the menu item Edit /Station access... brings up the
dialog for configuring the access rights. The station access for more than one list
entry can be changed at the same time: select more than one entry in the list by
means of Shift + arrow keys before choosing (Station access...) from the menu.

[Link]

Left-hand column
List of all the operator stations and gateway stations that have been
set up; in the variable list only the gateway stations are shown;

26

Read

The previously selected variable(s) and/or tag(s) data can be read

from the process station via the gateway,

Write

The previously selected variable(s) and/or tag(s) data can be

modified in the process station via the gateway (only user-defined

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Enabling Profibus parameters for OPC access

variables can be written to, while pre-defined process station

variables can only be read).
Variables that are written via a gateway may not be simultaneously written via
the process image. When the process image is used, a variable that has been
modified by the OPC server can be overwritten again by the task.
Variables with no process image are not capable of redundant operation. If such
variables are used in a redundant task, then they should be duplicated to other
variables

Enabling Profibus parameters for OPC access

The Profibus DPV1 and user parameters are configured to determine whether the
data is available via the OPC gateway.
There are two columns for configuring OPC access in the overlays of the DPV1
parameters and the user parameters. A check-box in the OPC access column is used
to configure whether the parameter is loaded into the OPC gateway or not. The
corresponding parameter can be accessed in the gateway under <tag name
>/<component name>. If a name is entered in the OPC short name column, this
name will be used in the gateway instead of the component name.

3BDD012511R0401_Eng_Manual_OPC_Server_F

27

Initiating communication

Section 2 OPC Server

[Link]

OPC access

The parameter can be accessed via an OPC gateway

OPC short nameThe parameter is not addressed in the OPC gateway by the
component name in the Name column, but by the name entered
here. This name must be unique within an object.
The components of a Profibus object which are available via an OPC gateway are
defined by means of these dialogs. The gateway station through which this data can
be accessed is configured in the tag list for the object.

Initiating communication
An OPC server is started automatically when requested by an OPC client.
It can be started manually by calling the command window in Windows from the
installation default directory, e.g. c:\Program Files\ABB
IndustrialIT\Freelance\Control Builder F\EXE\... :
[Link] /xx
xx = assign resource ID no., e.g. 45 as in Setup

28

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Downloading project data to the gateway station

When an OPC server has started, the following icon appears in the Windows
taskbar:

[Link]

Several OPC servers can be started simultaneously on one PC as long as they

have different resource IDs.

Downloading project data to the gateway station

Like the process stations, a gateway station also needs to be commissioned.
After the project has been checked for plausibility and all the process stations
loaded, the project data must also be downloaded to the gateway station. The first
time a gateway is commissioned, Load > Whole station must be executed.
Configuration changes are transferred to the gateway station through Load >
Changed objects.
In the course of the downloading process from Control Builder F, the gateway
station receives notification about all variables and tags that can be accessed via this
gateway. The variable data and tag data can be read and written from the external
client.

Addressing the Freelance variables

A variable is addressed using the same name within the system and over the OPC
interface.
Input pins, output pins and parameters of a tag are addressed using the tag name and
the pin or parameter name:
<Tag name> / <Pin name or parameter name>
Example: TIC123/SP

Read the set-point input of controller TIC123

TIC123/Wi

Read the set-point input of controller TIC123

The component and parameter names of the user-defined function blocks can be
found in the class definition of the block. All the elements of the block interface that
reside in the process station can be accessed through the OPC server.

3BDD012511R0401_Eng_Manual_OPC_Server_F

29

Data types of the variables

Section 2 OPC Server

The component names of the Profibus objects can be modified, see Enabling
Profibus parameters for OPC access on page 27. The current names can be found in
the associated configuration dialogs.
The OPC interface is case-sensitive. The variable names must therefore be
identical in OPC and in the Control Builder F project.

Data types of the variables

The procedures for the OPC interface are based on the definitions for COM.
Canonical data types are used for data transmission within these definitions. The
data types involved here are those which the Microsoft environment supports as
basic data types.
A data request via OPC can be issued either with or without data type. In the case of
data requests with no data type (variant type), the AC 800 F / Freelance system data
types are mapped as follows:
Data transmission for unsigned data types has been changed with version 6.
The unsigned data types must be read in Visual Basic applications as Long
(VT_UI2) or as Single (VT_UI4). The optional parameter
RequestedDataTypes of the AddItems method must be set to VT_I4 where the
default Variant datatype is VT_UI2 and to VT_R4 where the default is VT_UI4.

30

Data type in
Control Builder F/
Freelance

Canonical data types in

OPC

Visual Basic data type

up to V5

up to V5

BOOL

VT_BOOL

Boolean

BYTE

VT_UI1

Byte

WORD

VT_I2

VT_UI2

Integer

Long

UINT

VT_I2

VT_UI2

Integer

Long

INT

VT_I2

DWORD

VT_I4

VT_UI4

Long

Single

UDINT

VT_I4

VT_UI4

Long

Single

since V6

since V6

Integer

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Data types of the variables

Data type in
Control Builder F/
Freelance

Canonical data types in

OPC

Visual Basic data type

up to V5

up to V5

DINT

VT_I4

Long

REAL

VT_R4

Single

TIME

VT_I4

Long

DT

VT_DATE

Date

STRING8.. STRING256

VT_BSTR

String

since V6

since V6

The AC 800 F, AC 700F, Freelance data types are described in the Engineering
Manual IEC 61131-3 Programming, Variables, Overview of Data Types.
Data requests with a specific data type (requested data type) were always accepted
in versions up to 6.1 as long as it was in principle possible to convert the AC 800 F
/AC 700F, Freelance data type into the requested data type. If it was ascertained
during this process that one or more values lay outside the range of valid values,
then the value concerned was sent out with the attribute Bad Quality.
In version V6.2 and later versions, only data types in which it is always possible to
perform a conversion are accepted. The possible combinations are shown in the
table below:
Conversion is possible to VT_xx
DAT
E

Control Builder F BOOL UI1

UI2

UI4

I1

I2

I4

R4

R8

BOOL

BYTE

WORD

UINT

INT

DWORD

X
X

3BDD012511R0401_Eng_Manual_OPC_Server_F

BSTR

31

Message priorities, severity

Section 2 OPC Server

Conversion is possible to VT_xx

Control Builder F BOOL UI1
UDINT

DINT

REAL

TIME

DT

UI2

UI4

I1

I2

I4

STRINGx

DAT
E

R4

R8

X
X

BSTR

X
X

The system response with regard to the data type conversion requested can be set in
the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Hartmann & Braun\Freelance
\OPCServer]
With the setting OptimisticDataConversion = 1 the OPC Server behaves as in
the earlier versions.
With the setting OptimisticDataConversion = 0 (Default setting from version
6.2) the more restrictive form of data conversion is implemented.

Message priorities, severity

Control Builder F incorporates the message priorities 0 to 5. Message types are
linked to these priorities. The system messages (priority 0) are also subdivided
between system message groups S1, S2 and S3. These groups become visible at
the operator interface and can be used for filtering and initiating actions.
In order to display a message priority there is the severity attribute within the OPC
server. Severity values can range from 1 to 1000, whereby 1000 represents the
highest priority. Incoming and outgoing messages are reported with the same
severity. The value 0 is reserved: In response to a query of alarm status, severity
value 0 is sent for an inactive, acknowledged message.

32

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Message types, category and condition

The priorities of the AC 800 F / Freelance messages are mapped to the following
severity values:
AC 800 F / Freelance
Prio

Type

OPC
Severity

System S1

900

System S2

500

System S3

100

Fault

1000

Fault

800

Fault

600

Switch

400

Hint

200

Message types, category and condition

The message types of the AC 800 F / Freelance system are mapped to the attributes
category, condition and subcondition in the OPC server.
The process messages of an AC 800 F / Freelance system are subdivided into
categories and conditions of OPC alarms. There are no subconditions for these
alarms. In accordance with the OPC specifications, the strings which are then
delivered for condition and subcondition are identical.
The index of the associated alarm point in the function block (starting with '0' for
the first alarm point) has been added to the list of strings in the table in the appendix.
If a high-level alarm is configured for the first alarm point in a function block, then
this alarm is reported with the string "H_0" for condition and subcondition. See
Appendix B, Representation of the Freelance message types.
The system messages of an AC 800 F / Freelance system are all reported with the
category OPC_CATEGORY_SYSTEM. The text contents correspond to the
messages on a DigiVis station. See Appendix D, System messages for a list of the
system messages.

3BDD012511R0401_Eng_Manual_OPC_Server_F

33

Message types, category and condition

Section 2 OPC Server

The system messages are transmitted in the language in which the OPC server was
installed. All other text, e.g. conditions and subconditions, are available only in
English.
Depending on the message category, various attributes of the OPC message are
supplied with current data from the AC 800 F / Freelance system.

RateOfChange

Category

Hint

Hint text

VT_BSTR

WaveFile

WAV file

VT_BSTR

LongText

Long text

ShortText

Short text

VT_BSTR

CV

Current value

VT_VARIANT X

Dimension

Dimension

VT_BSTR

AcknowledgeRule

Acknowledgement
rule

VT_BSTR

ResourceID

Resource ID

VT_I2

ObjectNumber

Object number

VT_I2

AlarmIndex

Index of message
point

VT_I2

VT_BSTR

ConditionSubType
ErrorString

34

Error text

VT_BSTR

System

Limit

VT_BSTR

User

System area

Discrete

Area

Duration

Data type

Deviation

Description

Level

Attribute

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Project version control

RateOfChange

Category

VT_BSTR

SystemMessageGroup Message group

S1..S3

System
X

Limit

VT_I4

User

Error number

Discrete

ErrorCode

Duration

Data type

Deviation

Description

Level

Attribute

Project version control

When data is accessed within the OPC server for reading and writing, the internal
project version is compared with that in the process stations. The response in the
event of a version error is defined in the PC's registry entries. In this way it is
possible to ensure that no read/write operations are carried out on a process station
that has been reconfigured using Control Builder F unless the OPC server has been
reloaded.
In general, following a configuration change to and subsequent loading of a
process station, the OPC server must also be loaded. If no OPC related data has
been modified, then only the project version number needs to be updated. This
modification is post-loaded automatically from Control Builder F.
The version control for writing via the OPC server is by default set more
restrictively than for reading. This means that, in the event of a version conflict, data
can be read but not written.
No version controls of any kind are carried out for transmitting alarms and alarm
acknowledgements. This means that every alarm message from the Freelance
system is forwarded to the OPC client, and every acknowledgement of an alarm is
likewise forwarded from a client to the process stations.
Registry entries for the OPC server:
The version monitoring entries are located in the following path:

3BDD012511R0401_Eng_Manual_OPC_Server_F

35

Project version control

Section 2 OPC Server

[HKEY_LOCAL_MACHINE\SOFTWARE\Hartmann & Braun\Freelance

\VersionControl]

[Link]

VersionControlDepthRead / Write
Specifies the differences between process stations and gateway
stations that produce a version error.
0: No version control,
1: Project names are checked,
2: Project names + MajorVersionNo are checked,
3: Project names + MajorVersionNo + MinorVersionNo are
checked,
4: Project names + MajorVersionNo + MinorVersionNo +
PatchVersionNo are checked.
The default value is 3, i.e. the name, MajorVersionNo and
MinorVersion-No of the project must be identical on the process
station and the gateway in order to avoid having a version error
reported when a variable is accessed.
VersionReadFlag / WriteFlag
Defines the response when a version error is detected (corresponds
to the VersionControlDepth setting).

36

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Alarm messages from the OPC server

1: The variable is read or written even if a version error is detected.

2: Any version error that is detected will be reported, while the
read- or write access requested is not carried out.
Defaults:
The default value for read accesses is 1, in other words the read
command will be carried out even when a version error has been
detected.
The default value for write accesses is 2, in other words if a version
error is detected, it is reported and the write command is not carried
out.

Alarm messages from the OPC server

In version 6.2 and later the OPC server generates its own alarm messages. These
messages indicate a fault in the connection state between the OPC server and the
subordinate process station. The gateway name from the project tree is used as the
source for these messages. These alarms are always single-value alarms, i.e. no
acknowledgement is expected.
The following alarm messages are implemented:
Status of the connection with a process station
Source:

<Gateway name from P-tree>

Condition:

<Name of PS in P-tree>_CONNECTION_STATE_0

with the following subconditions:

NOT_CONNECTED

"No connection to station %d"

ESTABLISHING_CONNECTIO
N

"Establishing connection to station %d"

PROJECT_VERSION_ERROR

3BDD012511R0401_Eng_Manual_OPC_Server_F

"Version error, project name different in station

%d"

37

Alarm messages from the OPC server

Section 2 OPC Server

MAJOR_VERSION_ERROR

"Version error, major version number different

in station %d"

MINOR_VERSION_ERROR

"Version error, minor version number different

in station %d"

Read/write status of the individual process stations

The connection status and the registry values are evaluated for the version control
system.
Source:

<Gateway name from P-tree>

Condition :

<Name of PS in P-tree>_READ_WRITE_STATE_1

with the following subconditions:

NO_READ_ACCESS

"No read access to station %d"

NO_WRITE_ACCESS

"No write access to station %d"

NO_ACCESS

"No access to station %d"

OPC server offline:

This is activated if the OPC server has lost its connection to all process stations.
Source:

<Gateway name from P-tree>

Condition :

OPC_SERVER_OFFLINE

with the following subcondition:

OPC_SERVER_OFFLINE_0

"OPC server %d offline"

Handling of NOT_CONNECTED with redundant process stations

If a connection is lost with a redundant resource, it is assumed that a redundancy
transfer is taking place. Only if the connection has still not been re-established after
4 seconds does the disconnection have an effect on the quality of items and alarms.
The relevant internal alarms are also generated at this point.
The system response can be set in the registry:

38

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Tools and utilities for error diagnosis

[HKEY_LOCAL_MACHINE\SOFTWARE\Hartmann &
Braun\Freelance\OPCServer]
RedToggleQualityGood = 0 Disconnection is reported immediately,
RedToggleQualityGood = 1 Disconnection is only reported after a timeout
(default setting)
The length of the timeout can likewise be set in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Hartmann &
Braun\Freelance\OPCServer]
RedToggleTimeOut Value in seconds (default setting = 4)

Tools and utilities for error diagnosis

Testing on the process station
The connection monitoring block M_CONN can be used to check from a process
station the connection to the OPC server. In the event of a disruption to the
connection, specific safety values can be adopted in the process, or a message can
also be generated for other operator stations that are not connected via this OPC
server.

Testing the PC on which the OPC server is executed

If the OPC server has been installed for an interactive Windows user, a running OPC
server can be detected on the gateway PC by an entry in the taskbar.

[Link]

A dialog for monitoring the various sequences of the OPC server can be started in
the context menu of this entry. The trace dialog is invoked by means of Trace...
from the context menu or from the start menu via ... / Control Builder F / OPC
Server / OPC Server Trace:

3BDD012511R0401_Eng_Manual_OPC_Server_F

39

Testing on the process station

Section 2 OPC Server

[Link]

OPC Server
Computer name, Res-ID
The linked OPC server is described by means of the two entries.
The two fields can be edited after actuation of the Disconnect
button. A connection to the registered OPC server is established by
means of the Connect button.
Keyword trace
The various functions of the OPC server can be hierarchically
selected in the left-hand half of the dialog. Depending on the entries
selected, the respective function calls in the OPC server are
recorded together with the current parameters.
As a result, it is possible to track specifically defined functions or
functional groups of the OPC server. See Appendix C, OPC
Keyword Tracing.
Trace level
Trace file
Path

40

The degree of detail of the trace outputs is specified by means of the

trace level.
The directory for the trace file is specified. A file named opc<ResID>.trc is created in the specified directory.

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

Testing on the process station

Size [KByte]
The maximum size of the trace file in KBytes.
If the size of the trace file reaches maximum, the file is renamed
opc<Res-ID>.bak and a new opc<Res-ID>.trc file is created.
Apply Settings The settings for directory and size of the trace file are transferred.
Show File

The current trace file is displayed in the standard Windows editor. If

information from the *.bak file is required, the latter has to be called
separately.

Clear File

The current trace file is deleted. the *.bak file is not affected by this
action.

Server dump
Dump Configuration
All the configuration data of the OPC server is written to the trace
file.
The entries are marked with the text Dumping configuration
data... and ...configuration dump finished.
Dump Connections
An entry is generated in the trace file for all active connections.
The entries are marked with the text Dumping server objects... and
...server object dump finished.
Dump Groups
An entry is generated in the trace file for all installed groups of the
OPC server.
The entries are marked with the text Dumping group objects... and
...group object dump finished.
Save Settings All settings of the dialog are stored and preset on the start of a new
trace dialog or restart of the OPC server.
Example of a trace file

3BDD012511R0401_Eng_Manual_OPC_Server_F

41

Testing in Control Builder F

Section 2 OPC Server

[Link]

Testing in Control Builder F

During commissioning, like the process station variables, the OPC variables can
also be displayed in Control Builder F's value window and trend window.

System monitor for OPC

A system monitor (Performance Monitor) is included in the Windows standard
[Link] can be used to check and monitor the performance of the Windows
PC. The software package from Microsoft allows all general variables, e.g. free
disk space, CPU workload to be displayed and monitored.
An add-on component also allows application-specific AC 800F and Freelance
process station variables, such as statistical data on read/write errors, to be
displayed on the OPC server.
The system monitor is called up from the Start menu:
> Start > Settings > Control Panel > Administrative Tools > Performance

42

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

System monitor for OPC

Selecting the display type and entering variables

The display type is selected by means of the buttons in the toolbar.

Variables for the monitoring can be selected after invoking the + button in the
performance monitor:
In the AddCounters dialog:
-- Select the Control Builder F computer (remote operation is possible) >
-- Select the Freelance object >
-- Select the desired variables via Select counters from list and exit the dialog
with Add and Close
If Freelance is not displayed in the Performance object window you should
check whether the correct language setting has been configured for your
Windows installation. The language settings of Windows and Control Builder F
must be the same.

[Link]

Chart display

Once the data sources have been defined, the current values are displayed in a chart.
The display parameters can be set in the Properties the performance monitor
dialog.

3BDD012511R0401_Eng_Manual_OPC_Server_F

43

System monitor for OPC

Section 2 OPC Server

Meaning of the variables

General variables
Name

Description

% Communication buffers

% Communication buffers is the percent

amount of "in use" communication buffers. Normally this value is 0.

Communication buffers

Total amount of "in use" communication buffers.

Normally this value is 0.

% Connections

% Connections is the percent amount of active

connections.

Connections

Total number of active connections.

% DMS-Handles

% DMS-Handles is the percent amount of "in

use" DMS-Resources. These value includes the
dynamic SEG-Handles.

DMS-Handles

Total amount of "in use" DMS-Resources.

These value includes all dynamic SEG-Handles.

% SEG-Handles

% SEG-Handles is the percent amount of "inuse" DMS-Resources for cyclic requests.

SEG-Handles

Total amount of "in-use" DMS-Resources for

cyclic requests.

Process-ID

PID of the running process.

Station-Number

First station number

OPC variables

44

Name

Description

Item No

Number of configured items.

Event No

Number of configured event points.

3BDD012511R0401_Eng_Manual_OPC_Server_F

Section 2 OPC Server

System monitor for OPC

Name

Description

Client connections

Number of OPC Data Access client connections.

Groups

Number of OPC Groups.

Active items

Number of active OPC Items, the same item in

different groups is counted once.

AddItem failures (bandwidth)

Number of OPC Items which could not added

due to limited bandwidth.

AddItem failures (interaction)

Number of OPC Items which could not added

due to wrong interaction between client and
server.

AddItem failures (configuration)

Number of OPC Items which could not added

due to configuration errors..

Pending jobs

Number of pending acyclic jobs.

Acyclic read errors

Number of failed acyclic reads, counted on item

base

Acyclic write errors.

Number of failed writes, counted on item base

Station No. for Station n

Station No. for Station n.

% used cyclic bandwidth St. N

Percentage of used cyclic bandwidth for Station

n. If this value reaches 100% it is not possible
to communicate additional cyclic values from
this Station. This could also happen due to fragmentation when the value is a little bit below
100%.

Changed cyclic items/second

Number of changed cyclic items per second,

items sent to different clients are counted once.

Acyclic reads/second

Number of successfully acyclic read items from

devive per second.

Acyclic writes/second

Number of successfully written items per second.

3BDD012511R0401_Eng_Manual_OPC_Server_F

45