Basic OPC UA Settings

Endpoint
DNS Name / IP Address

Name of the controller in the Domain Name System (DNS) where the OPC UA server is installed as embedded application. A name server can uniquely identify the server using this name by mapping the DNS name to the controller's IP address.

Information Model

Specifies the implementation of the information model and therefore the visibility of data for OPC UA clients.

Using these options, you can define the data structure the OPC UA server will provide to its clients.

'IN/OUT-Port visibility'

'all': all ports and variables contained in the application's GDS (Global Data Space) are visible and accessible for OPC UA clients.
'marked': only ports and variables for which the 'OPC' property is selected in the variables declaration table are visible and accessible for OPC UA clients. Using this option and selecting the required variables in the declaration table, the load of the OPC UA server as well as the communication traffic can be reduced.
'none': clients cannot subscribe any port or variable via the OPC UA server. The entire 'PLCnext' node is excluded from the data information model.
The Device Information (DI, according to the OPC UA standard) remains visible for clients. This includes controller information such as hardware and software revision numbers, serial number, manufacturer name, model specification, etc.

Example

Specification

Only available for iC9200 Series controllers with a firmware version 2023.6 or newer.

Enables the configuration of the maximum number of concurrent OPC UA client sessions for the OPC UA server.

Possible values:

'No' (default) - The default value specified for the maximum number of concurrent OPC UA client sessions in the firmware of the controller is used for the OPC UA server.
'Yes' - The value entered for the maximum number of concurrent OPC UA client sessions (see the following parameter group) is used for the OPC UA server.

Maximum no. of sessions

Only available for iC9200 Series controllers with a firmware version 2023.6 or newer.

Maximum number of concurrent OPC UA client sessions the OPC UA server will allow. (The parameter group is only available if the parameter 'Enable Specification' is set to 'Yes', see above).

Set 'Enable maximum no. of sessions' to 'Yes' and enter the maximum number of concurrent OPC UA client sessions in the input field below.
With 'Enable maximum no. of sessions' set to 'No', the default value specified in the firmware of the controller is used.

Note
The default value and possible value range of concurrent OPC UA client sessions depends on the PLC type used.

Subscription Settings
Subscription Kind

Kind of PLCnext subscription that is used by the OPC UA server.

Possible values:

'Direct Read': With this setting, values are recorded independently of the ESM tasks defined in your controller application. Instead, values are read directly from the respective variables as soon as the responsible firmware function is called. This way, data subscriptions from different ESM task cycles are possible.
This setting may be useful for the asynchronous subscription of non-time-critical data. It has no influence on the real-time behavior.
'Direct Read' is the default setting for new projects.
'High Performance': In this mode, simultaneous reading and writing of data is possible. Each access takes place ESM-task-synchronously. This subscription type consumes the least memory. It actually has impact on the real-time behavior but less than the 'Real Time' mode.
This mode is suitable for the most data acquisition scenarios.
'Real Time': In this mode, simultaneous reading and writing of data is made with minimum access times. Therefore, it enables the fastest data access of all three modes but requires the most memory. Subscription is made task-synchronously.
This mode is suitable for subscribing variables in very fast tasks. However, it influences the real-time behavior even more than in 'High Performance' mode.