OPC-UA Server - Instance & item setup
How to setup an OPC-UA server instance and item in SIA
The SIA OPC-UA Server Connector allows connections to items in SIA using the OPC-UA protocol.
Both unencrypted as well as encrypted access is available.
Parameters
The OPC-UA Server has specific parameters for both the instance and the item.
Username & Password
The username and password used to authenticate your connection to the OPC UA Server is the same as the username and password used to authenticate when accessing the SIA Connect web-interface. You can find more information on adding users from the following guide
Instance
The instance needs the following parameters to configure the server
| Parameter | Description |
|---|---|
| Name | The dot(.) separated URN of the service. My Service -> urn:My.Service.sia |
| Port | The TCP port where the server will be available Default: 4840 |
| Certificate (optional) | A certificate file in .pem or .der format for establishing authenticity |
| Key (optional) | An x509 key pair in either .pem or .der format for encryption |
| Security Mode None | Security Mode None enabled on the server Default: Enabled |
| Security Mode Sign | Security Mode Sign enabled on the server Default: Enabled |
| Security Mode Sign And Encrypt | Security Mode Sign And Encrypt enabled on the server Default: Enabled |
| Security Policy None | Security Policy None enabled on the server Default: Enabled |
| Security Policy Basic128rsa15 | Security Policy Basic128rsa15 enabled on the server Default: Enabled |
| Security Policy Basic256 | Security Policy Basic256 enabled on the server Default: Enabled |
| Security Policy Basic256sha256 | Security Policy Basic256sha256 enabled on the server Default: Enabled |
| Security Policy Aes128 Sha256 Rsaoaep | Security Policy Aes128 Sha256 Rsaoaep enabled on the server Default: Enabled |
| Security Policy Aes256 Sha256 Rsapss | Security Policy Aes256 Sha256 Rsapss enabled on the server Default: Enabled |
| Anonymous User | Anonymous User enabled on the server Default: Disabled |
Item
The item must be configured to expose an item in another connector
| Parameter | Description |
|---|---|
| Name | Browsable name of the OPC-UA node. Do not use spaces |
| Folder Path | Enter the hierarchical path for the folder structure in the OPC UA address space e.g. /Site/Building/Machine. Use forward slashes (/) to separate folder names, e.g., Devices/Test/Sub creates a folder Sub under Test under Devices. Each folder name should be unique within its parent and use alphanumeric characters or underscores (avoid special characters like # or %). This path defines where nodes (e.g., variables or devices) will be placed. Default: /SIA Connect/Devices/%INSTANCE.NAME% |
| Namespace | Structure of the folder Default: http://sia-connect.com/Server/UA |
| Data type | Data Type of the node Choose the data type you want the node to be, from the drop-down menu. Auto will automatically assign a data type to the node Default: Auto |
| Node Identifier | Choose whether to use the Sender Item from the Mapping as the Node Identifier, or you want the name of your OPC UA Server item to generate the name Default: Use name from mapping sender item |
| Node Type | Choose whether you want the node to be a Variable or a Method Variable: A variable stores one or more values, and will act much as a PLC tag Method: A method is a function, which can take input arguments and generate output arguments Default: Variable |
| Method Inputs | JSON array defining input arguments Example: [{"name":"deviceId","type":"String"},{"name":"targetPort","type":"Int32"}] |
| Method Outputs | JSON array defining output arguments Example: [{"name":"status","type":"Boolean"},{"name":"message","type":"String"}] Adding values to the output: To add values to the output of your method, you need to have the definition of the values in the Input Template Format: { " NAME " : [ VALUE ] } Example: {"status" : [1], "message": ["MESSAGE HERE"] } |