Unified-E OPC-UA Adapter

Size: px

Start display at page:

Download "Unified-E OPC-UA Adapter"

Violet Carpenter
5 years ago
Views:

1 Unified-E OPC-UA Adapter Adapter version and higher September 2017 Content 1 General Specific Adapter Parameters Datapoint Addressing... 3 Unified-E OPC-UA Adapter Page 1 of 5

2 1 General The OPC-UA adapter is used for communication with an OPC-UA server. OPC-UA is a widespread, industrial communication protocol. Depending on the PLC controller the OPC- UA protocol may be supported directly from the PLC or an additional OPC-UA server for the controller is required. Secure communication: OPC-UA allows an encrypted and signed communication. The communication partners authorize each other with a SSL certificate. The partner's certificate has to be known or trusted. For this there are two options: 1. Install the partner's certificate as trusted in a "Windows"-common way, e. g. use a certificate from a well-known publisher (only recommended for IT administrators) 2. Copy the partner certificates into a specific directory Directory for client certificates: %ProgramData%\OPC Foundation\CertificateStores\MachineDefault\certs %ProgramData%\OPC Foundation\CertificateStores\MachineDefault\private The OPC-Adapter uses this certificates e. g. for signing. Directory for trusted server certificates: %ProgramData%\OPC Foundation\CertificateStores\UA Applications\certs Copy all certificates of the trusted servers into this directory. 2 Specific Adapter Parameters General parameters Address: URL of the OPC-UA server. The endpoint which fits best to the parameters will be used. Datapoint addressing: Describes how to address the datapoints (OPC variables). Browse name: The address path is build up with <Namespace index>:<browse name> segments, e. g. "4:Demo/4:Static/4:Scalar/4:Boolean" Unified-E OPC-UA Adapter Page 2 of 5

3 Node ID: The variable is identified with the Node ID (textual or numerical), e. g. "23" Symbolic name: The address path is build up with <Symbolic name> segments, e. g. "Demo/Static/Scalar/Boolean". If a node can't be identified uniquely the first matching node is used. Display name: The address path is build up with <Display name> segments, e. g. "Demo/Static/Scalar/Boolean". If a node can't be identified uniquely the first matching node is used. Timeout [ms]: The timeout value for an operation like connecting or reading values. Client certificate name: The subject name of the client certificate which is stored in the folder "%ProgramData%\OPC Foundation\CertificateStores\MachineDefault\certs". If the field is not set a client certificate will be created automatically. Security-relevant parameters The parameter "Preferred security mode" defines if you want to sign or encrypt data packages. "Preferred security mode" with value "None": No further parameters are required. Data packages are not signed or encrypted. "Preferred security mode" with value "Sign" oder "Sign and encrypt": Force secure endpoints: If "Yes", the best secure endpoint will be used. Use domain checks: If "Yes", there is an additional check if the domain name of the server matches with the domain name entry in the server certificate. Accept untrusted certificates: If "Yes" then also untrusted servers are accepted. User name/user password: These parameters are only required if the server needs an additional user authentication. 3 Datapoint Addressing The address of a datapoint depends of the selected addressing mode which is defined with the parameter "Datapoint addressing". Most OPC-UA servers support "Display name" for the "Datapoint addressing parameter". However, some servers with textual OPC-UA nodes like WinCC OPC UA server require the value "Node ID" for this parameter. So, the datapoint address must be the node ID of the OPC variable. Unified-E OPC-UA Adapter Page 3 of 5

Supported data types: BOOL (Boolean) BYTE (Byte) SINT (SByte) WORD, UINT (UInt16) DWORD, UDINT (UInt32) INT (Int16) DINT (Int32)

4 Import datapoints: If it is possible to establish a connection between the App-Designer and the OPC-UA server then you can import the required datapoints by clicking the button "Import datapoints" in the endpoint editor. Supported data types: BOOL (Boolean) BYTE (Byte) SINT (SByte) WORD, UINT (UInt16) DWORD, UDINT (UInt32) INT (Int16) DINT (Int32) LINT (Int64) ULINT (UInt64) REAL (Float) LREAL (Double) STRING (String) Arrays History lists for time charts Example configuration: Unified-E OPC-UA Adapter Page 4 of 5

5 Addressing of bit for numeric variables: Example Demo/Static/Byte.0 addresses the first bit. Unified-E OPC-UA Adapter Page 5 of 5

NEO OPC Client Driver. The NEO OPC Client can be launched by configuring an OPC Link from the New Link or Add Link dialog as the followings:

NEO OPC Client Driver. The NEO OPC Client can be launched by configuring an OPC Link from the New Link or Add Link dialog as the followings: The configuration program provides a built-in OPC UA Client that enables connections to OPC Servers. The NEO OPC Client is built with the OPC Client SDK and can be used to interactively browse and retrieve