OPC UA

Use these OPC UA components to develop your application logic:

OPC UA server object. See OPC UA server.
OPC UA client objects. See OPC UA client.
OPC UA nodes imported from an OPC UA server or a NodeSet. See Import nodes at runtime and Import nodes from NodeSet.
IMPORTANT: To ensure that all alarm types are displayed in OPC UA client projects, import all alarm types from the OPC UA server project. For more information on how to publish and import nodes, see Add an OPC UA server and Import nodes at runtime.

Your system needs to meet the minimum security policy and message security mode to allow for communication between OPC UA components. For more information, see OPC UA communications security and OPC UA certificates and keys.

Use predefined Companion Specifications or import and export Companion Specifications. See OPC UA Companion Specifications.

When an OPC UA client (see Add an OPC UA client) imports nodes from an OPC UA server (see Add an OPC UA server), any localized text variable value is imported as a translation key and not as localized text. To display the text box with text on the client device, see Add a locale language to a localization dictionary and import the localization dictionary from the server. For non-FTOptix servers, use the

Connection Locale ID

property of the OPC UA client. The client then connects using that locale ID and the server sends the value of localized text variables as localized texts with that locale ID.

In addition to importing the localization dictionary, you must specify a locale to the

Localization/Locales

property, add a new user with the Language property set to the locale, and then specify that user as the starting user in the native presentation engine object.