Connecting to OPC/UA Server

This section describes the steps to configure the OPC UA Server Settings in the display unit.

WARNING

unintended equipment operation Application designer must be cautious in exposing variables to OPC UA client. As it is accessible and modifiable by any clients. Failure to follow these instructions can result in death, serious injury, or equipment damage.

1. In Project Explorer window, go to [System Architecture] and click [Target01].
2. In Properties window, go to [Advanced] tab ➞ [Data Access] tab and click [OPC UA Server].
3. Select [Enable] and configure the below properties:

   Property	Description
   [Transport Protocol]	Select the transport protocol.
   [Port Number]	Set the Port Number for data communication.
   [Data Format]	Select the Data Format.
   [Security Policy]	Select required [Security Policy]. You can select [NoSecurity] for communicating with the OPC UA Server without security. We recommend you to set the security policy. The following Security Policies are supported: NoSecurity Basic128Rsa15Sign Basic128Rsa15SignAndEncrypt Basic256Sign Basic256SignAndEncrypt Basic256Sha256Sign Basic256Sha256SignAndEncrypt Aes128Sha256RsaOaepSign Aes128Sha256RsaOaepSignAndEncrypt Aes256Sha256RsaPssSign Aes256Sha256RsaPssSignAndEncrypt Note: We recommend using one of the higher security policies based on AES (Advanced Encryption Standard), such as [Aes128Sha256RsaOaepSign].
   [Trusted Certificates] [Issuers Certificates]	Choose the desired option from following and set [No. Of Certification] and [No. Of CRL]. [Trusted Certificates]: Use this for Self-signed or CA Certificates needed to be verified.   [Issuers Certificates]: Use this for CA certificates needed to be verified by a chain of CA. [No. Of Certification] Set the [No. Of Certification] and select the certification file from [Certification File Path]  . If no security is selected in [Security Policy], then no need to set [No. Of Certification]. Note: The maximum number of certification files is 100. The file, which is already used in other [Certification File Path] of [Trusted Certificates] or [Issuers Certificates], cannot be used. Even if the file has different name and same content with other, the file cannot be used. [No. Of CRL] Set the [No. Of CRL] and select the CRL (Certificate Revocation List) file from [Certification File Path]. Note: The number of CRL files is equal to or less than the number of certification files. The file, which is already used in other [Certification File Path] of [Trusted Certificates] or [Issuers Certificates], cannot be used. Even if the file has different name and same content with other, the file cannot be used.
   [Security Setting]	When restricting the user according to the user access level of OPC UA, select [Enable] and set the security level. The user access level is as follows: User Access Level Description [SecurityLevelForBrowse] User can see the Server properties and variable names. [SecurityLevelForRead] User has Browse level privilege and can see variable value. [SecurityLevelForReadWrite] User can Read/Write variable value. This includes Read level privilege.
   [Node ID Naming Format]	Select the naming format for variables shared by the OPC UA server with external devices on the network. [Standard]: (default) Naming format consistent with OPC UA naming conventions. [Compatible]: Naming format compatible with screen editing software 3.3 Service Pack 1 or earlier. Note: You cannot use binding or script to dynamically change the value of this property. Variable Name Node ID Naming Format [Compatible] Version 3.3 Service Pack 1 or earlier [Standard] Version 3.4 or later Var1[0] Target01.Var1.Var1[0] Target01.Var1[0] Var1[1,1] Target01.Var1.Var1[1,1] Target01.Var1[1,1] Var2.BOOL1 Target01.Var2.Var2.BOOL1 Target01.Var2.BOOL1 Folder1.Var1[0] Target01.Folder1.Var1.Folder1.Var1[0] Target01.Folder1.Var1[0] Changing the [Node ID Naming Format] may cause references by other devices on the network to not work anymore.

4. In Project Explorer window, click [All Variables] and create a variable.

5. Select the required option to share the variable data from [Data Sharing].

   Note: The OPC UA server cannot share the value of local variables on a screen. If you want to share the value of a local variable, associate the value of the local variable as a binding source to an internal variable set to [Data Sharing].

An Effective Data Type

The following data type can be used. The data type descriptions are different from OPC UA.

Data Type	Data Type of OPC UA
BOOL	Boolean
BYTE	Byte
SINT	SByte
INT	Int16
DINT	Int32
LINT	Int64
UINT	UInt16
UDINT	UInt32
ULINT	UInt64
REAL	Float
LREAL	Double
STRING*1	String
WSTRING	String
TIME	Int32

*1 When using a string variable with its [Variable Length] property enabled, the variable can store up to 512 bytes (UTF-8 encoding).

OPC UA Server's Certificate details

Common Name	BLUE_OPCUA_Server@IP Address*1
Organization	Pro-face
Organization Unit	HMI
Locality	-
State	-
Country	JP
Domain Component	IP Address*1
URI	urn:IP Address*1:Pro-face:BLUE_OPCUA_Server

*1 When using OPC UA Server on Windows OS, it is displayed Windows' computer name instead of IP Address.

OPC Foundation Certified Details

Category	Description
Profiles	Nano Embedded Device Server
	Micro Embedded Device Server
Security Category	SecurityPolicy-Aes128Sha256RsaOaep
	SecurityPolicy-Aes256Sha256RsaPss
	SecurityPolicy-Basic128Rsa15
	SecurityPolicy-Basic256
	SecurityPolicy-Basic256Sha256
	SecurityPolicy-None
Server Category	Base Server Behavior
	Core Server
	Embedded DataChange Subscription Server
	Enhanced DataChange Subscription Server
	Standard DataChange Subscription Server
	User Token – User Name Password Server
Transport Category	UA-TCP UA-SC UA Binary