dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProgramming of Applications dl-breadcrumb-item__separatorRuntime systems, OPC UA serverdl-breadcrumb-item__separatorOPC UA dl-breadcrumb-item__separatorOPC UA Server
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
OPC UA Server

The standard installation of CODESYS includes an OPC UA Server. You can use it to access the variable interface of the controller via a client. The OPC UA Server communicates with connected OPC UA Clients over a separate TCP connection. That is why these connections have to be examined again separately with regard to security.

The OPC UA Server can now be safeguarded by using encrypted communication to the client and OPC UA user management. You will find the possible settings for this in the following sections:

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

In runtime version 3.5 SP17 and higher, a device user management has to be set up by default for access to the CODESYS runtime systems. However, for the OPC UA Server it is possible to continue to allow anonymous access if this is explicitly permitted. This permission is granted in the “Change Communication Policy” dialog on the ⮫ Communication Settings tab of the device editor.

The CODESYS OPC UA server supports the following features:

  • Browsing of data types and variables

  • Standard read/write services

  • Notification for value changes: subscription and monitored item services

  • Encrypted communication according to "OPC UA standard (profile: Basic256SHA256)"

  • Imaging of the IEC application according to "OPC UA Information Model for IEC 61131-3"

  • Supported profile: "Micro Embedded Device Server Profile"

  • Number of sessions

    By default, monitored items and subscriptions are not restricted. The number depends on the performance of the respective platform.

  • Sending of events according to the OPC UA standard

  • Communication with a data source OPC UA Client

    For more information, see: ⮫ “Establishing the Connection of a Data Source OPC UA Client to an OPC UA Server ”

The OPC UA Client UAExpert is cited many times in this chapter. UAExpert is a product of the vendor "Unified Automation".

For more information, see: ‎⮫ Unified Automation

When you create a ⮫ “IEC Symbol Set Configuration ” with the Communication Manager, OPC UA access is automatic. With the previous symbol configuration, you need to create a project for OPC UA access according to the following instructions.

Application note

How to install and configure an OPC V2 or OPC V3 server and how to use it for AC500 PLCs is described in the application note ‎⮫ How to use OPC server.

Application example

To gain a deeper understanding of the OPC protocol and to configure the PLC accordingly, an ‎⮫ application example is available.

  • Creating a project for OPC UA access with the existing symbol configuration
  • Configuration and commissioning of the OPC UA Server
  • Specification-compliant configuration of the OPC UA Server
  • Setting up an encrypted connection with the "UaExpert" client
  • User management in OPC UA
  • Using the OPC UA Client to change a variable
  • Using events or alarms in the CODESYS project
  • Observing an event via the "UaExpert" OPC UA Client
  • OPC UA Server Configuration Settings
  • Extension of the default OPC UA tag limitation