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 described in its own file and then assembled |
yml |
See the Swarm administration or Official documentation |
module.opc-da |
Defines the general OPC-DA module configuration |
json |
|
server.opc-da |
A OPC-DA server connection representation in OnSphere |
json |
|
owner.opc-da |
A OPC-DA read access to a specific itemId |
json |
|
output.opc-da |
A OPC-DA write access to a specific itemId |
json |