EOS OPC UA Server

EOS OPC UA Server is a communication component that provides data collected or processed by EOS applications to external systems as an OPC UA Server.

The server operates through an OPC UA endpoint to which OPC UA Client applications can connect.

Data within EOS is created as Nodes within the Address Space structure of OPC UA.

Within these Nodes, the data name, data type, description, access properties and other OPC UA properties are defined, allowing client applications to discover and use the data in a standard structure.

EOS OPC UA Server creates an OPC UA Address Space using the data and group structure available in EOS.

Group structures are created as hierarchical folders within the OPC UA Address Space.

EOS data points are created as OPC UA Variable Nodes under this hierarchy.

Current values in the EOS system are transferred to the created OPC UA Variable Nodes, allowing client applications to access the latest data.

EOS OPC UA Server transforms the group and data structure within EOS into a hierarchical structure within the OPC UA Address Space.

At the top level, a root structure belonging to EOS is created. Under this structure, the groups and subgroups defined in EOS are used to create a hierarchical structure.

Data points are created as OPC UA Variable Nodes under the corresponding group.

Data points within EOS are created as OPC UA Variable Nodes. A unique NodeId is created for each data point.

The data name is used as BrowseName, which can be used when OPC UA Client applications browse the Address Space, and as DisplayName, which is displayed in user interfaces.

The data description is stored in the Description field of the OPC UA Node.

The operating parameters of the EOS OPC UA Server are configured through EOS SCADA Project Settings. The IP address on which the server will operate, the port to which OPC UA clients will connect, and the data update interval can be configured in the project settings.

OPC UA Port defines the TCP port that OPC UA clients use to connect to the EOS OPC UA Server. This value can be changed through Project Settings when required.

The Update Interval is set to 1 second by default. This interval determines how frequently EOS SCADA data is checked by the OPC UA Server and how often updated values are transferred to OPC UA clients.

When the OPC UA Server is started, it begins operating on the IP address and port specified in the Project Settings and accepts OPC UA client connections. Clients can connect to the server, access the provided data points, and monitor these data through the supported OPC UA mechanisms.

EOS OPC UA Server maps the different numeric and Boolean data types used within EOS to the appropriate OPC UA data types and exposes them.

EOS OPC UA Server does not require all data within EOS to be exposed through OPC UA. The group of data to be exposed can be determined according to the configuration.

The EOS OPC UA Server uses the group structure of the EOS SCADA data tree to create Nodes within the OPC UA Address Space. The Node structure is formed by organizing the upper group, sub-group, and data name hierarchically.

UPPER_GROUP / SUB_GROUP / DATA_NAME

For example, if the EOS SCADA data tree contains the following structure: Plant / Turbine1 / ActivePower the following Node hierarchy can be created within the OPC UA Address Space:

Plant
 └── Turbine1
      └── ActivePower

In this structure, group and sub-group levels are created as Object Nodes, while data points are exposed as Variable Nodes.

For example, the ActivePower data point is exposed as an OPC UA Variable Node. The Node contains the data value, data type, and other OPC UA properties.

This structure provides a direct relationship between the OPC UA Address Space hierarchy and the EOS SCADA data hierarchy.

EOS OPC UA Server transfers the current values within EOS to OPC UA Variable Nodes.

The update process is continuously performed using the refresh interval defined for the OPC UA Server.

When the current value of an EOS data point changes, the value of the corresponding OPC UA Node is updated.

Along with the data, the read timestamp within EOS can also be used in the OPC UA DataValue structure.

EOS OPC UA Server provides services to OPC UA Client applications over the TCP/IP-based OPC UA Binary communication profile.

The server's TCP port can be defined through the OPC UA Server configuration within the EOS application.

EOS OPC UA Server does not only transfer values. A StatusCode is also generated to indicate the status of the value within OPC UA.

For successful conversions, the data is exposed with a Good StatusCode. If the data cannot be converted to the expected data type or is not within the appropriate range, the appropriate Bad StatusCode is used.

EOS OPC UA Server enables client applications that support the OPC UA standard to access EOS data.

OPC UA Client applications can browse the Address Space created by EOS to access data Nodes, read current values, and monitor data changes through supported mechanisms.

EOS OPC UA Server is designed to operate as an integrated component within the EOS ecosystem.

The server directly retrieves real-time data from the EOS data structure and transfers it to the Nodes created within the OPC UA Address Space.

The group structure within EOS is preserved as a hierarchical structure on the OPC UA side. This allows OPC UA Client applications to display the data organization within EOS in a more understandable manner.

Through this integration, EOS-collected or processed data can be accessed through OPC UA without the need to develop a separate data transfer application.

EOS OPC UA Server facilitates the use of real-time industrial data within EOS systems by different systems that support the OPC UA standard.

EOS OPC UA Server is an integrated OPC UA Server component that enables real-time industrial data within EOS systems to be transferred to different systems through OPC UA.

The group structure within EOS is transformed into a hierarchical Node structure within the OPC UA Address Space. Data points are exposed as OPC UA Variable Nodes.

Boolean, various Integer types, Float and Double data types are mapped to the appropriate data types on the OPC UA side.

As EOS data is updated, OPC UA Node values are also updated and data changes can be notified to clients through the supported DataChange mechanism.

In addition to Anonymous and Username-based user access, support for different OPC UA Security Policy options and application certificates enables EOS data to be used in secure communication scenarios with industrial systems supporting OPC UA.

Through this structure, EOS systems can be directly integrated with PLC, SCADA, HMI, MES and other industrial applications that support the OPC UA standard.

You can contact us regarding EOS software, OPC UA communication or technical content.

• benanbasoglu@gmail.com
• ANKARA