OPC-UA-Server
OPC-UA-Server
CDP OPC-UA-Server is a CDP module that can be added to the CDP application in order to serve and exchange information in the OPC UA (Open Platform Communications Unified Architecture) network.
OPC-UA-Server has the following configuration properties:
| Property | Description |
|---|---|
| EndpointInterface<string> | Interface name (from CDP Application configuration) for the server to listen on. Set empty to listen on all interfaces. Defaults to ETH0. |
| EndpointPort<unsigned short> | TCP port for the server to listen on. Defaults to 4840. |
| SecurityMode<string> | OPC UA message security mode to use. Choose between:
|
| SecurityPolicy<string> | OPC UA security policy to use, when SecurityMode other than None is selected. Choose between:
|
| TLSServerCertFile<string> | Adapter TLS key certificate file name. Must be filled when SecurityMode other than None is selected. See also OPC UA TLS certificate setup. |
| TLSServerKeyFile<string> | Adapter TLS key file name. Must be filled when SecurityMode other than None is selected. See also OPC UA TLS certificate setup. |
| TLSAllowURIMismatch<bool> | Can be set to true to allow connection from clients with TLS certificates that do not match with their application URI. See also OPC UA TLS certificate setup. |
| AnonymousAccessLevel<unsigned char> | Access level flags for clients logging in without credentials (using anonymous mode). The following OPC UA access flags can be set:
|
| EndpointAppURI<string> | OPC UA namespace URI for the application. If left empty, adapter component full name is used. |
| EndpointAppName<string> | Description for the application to be advertised. If left empty, CDP component name is used. |
An unlimited number of AllowedClient sub-elements can be added to OPC-UA-Server to configure allowed clients and their credentials. Each AllowedClient has the following configuration properties:
| Property | Description |
|---|---|
| Name<string> | OPC UA client username |
| Password<string> | OPC UA client password |
| TLSClientCertFile<string> | OPC UA client TLS certificate to use for authentication. Can be left empty if SecurityMode None is used. |
| AccessLevel<string> | Access level flags for this OPC UA client. The following OPC UA access flags can be set:
|
Note: For strongest authentication use AllowedClients that have both password and certificate authentication.
Server state can be observed at runtime via these read-only properties:
| EndpointURL<string> | Endpoint URL. Is automatically composed from protocol, listen ip and port. |
| EndpointProtocol<string> | OPC UA protocol to use. Currently only opc.tcp (binary) protocol is supported. |
| CurrentState<string> | State of the adapter. Can be Online or Offline. When a problem is detected at startup, the server is offline. |
Nodes
An unlimited number of server nodes can be added to the OPC-UA-Server to configure the information that must present to be served by the server. Nodes can contain other nodes and therefore can form a complex node-tree.
The following nodes can be added hierarchically to OPC-UA-Server:
- ServerObjectNode - for accessing OPC UA object nodes
- ServerVariableNode - for accessing OPC UA variable nodes
- ServerMethodNode - for accessing and invoking OPC UA variable method nodes
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.