ReferenceDevice driversOPC UAConnect to a server

Connect to an OPC UA server

Connect to an OPC UA server using Synnax.

The Synnax Driver connects to any OPC UA server: PLCs, SCADA systems, DCS, MES, and industrial sensors. Secure and non-secure connections are supported with anonymous, username and password, or certificate authentication.

Prerequisites

Before you can connect to an OPC UA server, you will need to ensure that you have the following:

  1. A Synnax Core running on your network.
  2. A Synnax Driver running on your network. This Driver must be connected to the Core and running on the same machine or network as your OPC UA server.
  3. The Synnax Console installed on your local machine.
  4. An OPC UA server running on your network. This server must be reachable by the Driver.

Supported operating systems

Platform Status
Windows ✓ Supported
Linux ✓ Supported
NI Linux Real-Time ✓ Supported
macOS ✓ Supported
Docker ✓ Supported

When running in a Docker container, ensure the container has network access to the OPC UA server.

Common OPC UA servers

Server Description
open62541 Open-source OPC UA stack
Beckhoff TwinCAT PLC and automation platform
FactoryTalk Allen-Bradley FactoryTalk with OPC UA
Ignition SCADA platform with built-in OPC UA server
Siemens S7 PLCs with OPC UA support
Prosys OPC UA Simulation Server For testing and development

Configuration parameters reference

Parameter Type Required Default Description
name string - Human-readable server name for identification in Console
rack string - Synnax Driver (rack) key that will connect to the OPC UA server
endpoint string - Server endpoint URL (e.g., opc.tcp://localhost:4840)
username string - Username for server authentication (optional)
password string - Password for server authentication (optional)
security_mode string None Security mode: None, Sign, or SignAndEncrypt
security_policy string None Security policy: None, Basic128Rsa15, Basic256, Basic256Sha256, Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss
client_cert string - Client certificate for signing/encrypting (required if security policy ≠ None)
client_private_key string - Client private key for signing/encrypting (required if security policy ≠ None)
server_cert string - Trusted server certificate (required if security policy ≠ None)

Security mode and policy reference

Security mode:

  • None -> No security applied
  • Sign -> Messages are signed but not encrypted. Provides authentication without confidentiality
  • SignAndEncrypt -> Messages are signed and encrypted for full authenticity and confidentiality

Security policy:

  • None -> No encryption
  • Basic128Rsa15 -> 128-bit encryption with RSA-15
  • Basic256 -> 256-bit encryption
  • Basic256Sha256 -> 256-bit encryption with SHA-256
  • Aes128_Sha256_RsaOaep -> 128-bit AES with SHA-256 and RSA OAEP
  • Aes256_Sha256_RsaPss -> 256-bit AES with SHA-256 and RSA PSS

How-to