osp-opc-da

Overview

The osp-opc-da module allows communicating with OPC Da servers over IP for reading and writing values.

Behavior

Server connection

In OPC DA, the initial communication is typically established over port 135, which is used for DCOM’s initial RPC (Remote Procedure Call) connection. After that, DCOM dynamically selects a port for further communication, which can vary each time the communication is initiated. This dynamic port is usually within a specific range.

If you’re configuring firewalls or network settings for OPC DA communication, it’s important to allow traffic on port 135 and to configure DCOM to use a specific port range for dynamic ports. You can typically find information on how to configure these settings in the documentation of your OPC server and client software.

List of configuration files

Filename

Short description

Format

Documentation

module.service

Each service is defined in a separate file and then combined into a unified compose stack file

yml

See the Swarm administration or Official documentation

module.opc-da

Defines the general OPC-DA module configuration

json

module.opc-da

server.opc-da

A OPC-DA server connection representation in OnSphere

json

server.opc-da

owner.opc-da

A OPC-DA read access to a specific itemId

json

owner.opc-da

output.opc-da

A OPC-DA write access to a specific itemId

json

output.opc-da

Environment Variables

All modules env variables

Variable Name

Default Value

Usage

PROMETHEUS_PORT

9100

The internal port used for Openmetrics exposition.

DISPATCHER_HOST

modules_configuration-dispatcher_main

The hostname on which the modules can fetch the configuration.

DISPATCHER_PORT

10000

The port used by the module to listen for configuration request.

USE_LEGACY_RESTART

Not set

When this flag is enabled, the container will terminate itself whenever a restart is needed (for example, after a configuration change). This is the legacy restart (before version 2.1.0). Otherwise, the system will simply restart the process running inside the container.

CUSTOM_JVM_OPTIONS

Not set

Allow to inject JVM options. See Configuration changes for more information.

ALLOW_VERSION_MISMATCH

Not set

Allow to disable the version check when a new configuration is published to a module. By default, a module will not be restarted if its configuration does not match its version.

Dedicated variables

None