Device | Bit Address | Word Address | 32bits | Remarks
--- | --- | --- | --- | ---
BOOL | <TAGNAME> | - | - | *1
BYTE SINT USINT | - | <TAGNAME> |  | *1
WORD INT UINT | - | <TAGNAME> |  | *1
DWORD DINT UDINT | - | <TAGNAME> |  | *1
LWORD LINT ULINT | - | <TAGNAME> |  | *1
REAL TIME STRING*2 | - | <TAGNAME> |  | *1
LREAL | - | <TAGNAME> |  | *1
WSTRING |  | <TAGNAME> |  | *1

*1<TAGNAME>: Tag Name can be up to 255 characters long.

Example

BOOL type single tag: | "BOOLSYMBOL"

For tag names, you can use alphanumeric characters (upper and lower case), underscore, space, and multi-byte characters (such as Japanese). Note the following input limitations.
• The last character in the name cannot be the underscore symbol.
• The pound symbol (#) can be used as the first character only.
• Names cannot include any of the following symbols:
. , ! “ $ % ^ & * ( ) - + = { } [ ] / \ ? # @ ~
• You cannot start names with any of the following text:
LS, USR, SCR, PRT

*2The maximum number of characters for the STRING device is 254 characters.

IMPORTANT:

- The data types of tags in the OPC UA Server are mapped to their corresponding data types in BLUE, as shown below.
  When tags from the OPC UA Server are imported, their data types are automatically converted to the appropriate type used in BLUE.
  When creating variables in BLUE, match the data types to the OPC UA Server tag data types.
  If the data types do not match, tag values may not be read or written correctly.

  Data Type of OPC UA Server | Data Type of BLUE
  --- | ---
  Boolean | BOOL
  Byte | BYTE
  Byte | USINT
  Double | LREAL
  Float | REAL
  Int16 | INT
  Int32 | DINT
  Int32 | TIME
  Int64 | LINT
  Sbyte | SINT
  String | STRING
  String | WSTRING
  UInt16 | UINT
  UInt16 | WORD
  UInt32 | DWORD
  UInt32 | UDINT
  UInt64 | LWORD
  UINT64 | ULINT

  DATE, TIME_OF_DAY, DATE_AND_TIME, Array, and Structure are not supported.

NOTE

- When tag names include symbols that are not allowed in BLUE, the tag is not imported. Before importing, please change the tag name.
- You cannot edit imported tag data. Please import again if you change the tag data.
- This driver uses the tag data included in an OPC UA Server.
- Please refer to the precautions on manual notation for icons in the table.
  Supported Devices Symbol and Terms

### Symbol Link

You can import tags registered in the OPC UA Server into the BLUE editor. To import tags securely, you must register the BLUE self-signed certificate with the OPC UA Server.

1. From the application toolbar in BLUE, click icon.

2. Click [Certificates].

3. Click the icon. A self-signed certificate for BLUE is generated.

4. Click the icon. Specify the destination and export the self-signed certificate.

5. Register the exported self-signed certificate as a trusted certificate in the OPC UA Server.
   Example: If the OPC UA Server is the display unit, from the Properties window for Target01 in BLUE, go to [OPC UA Server] > [Security Policy], and set the self-signed certificate in [Trusted Certificates] > [Certificate File Path]. Then, transfer the project.

6. In BLUE, click [Symbol Link].

7. After configuring the target OPC UA Server, a list of tags is displayed. Select the required tags and import them.

NOTE

- For tag import procedures, see the following.
  Importing Symbols from External Devices

During tag import, the following status codes may display.

Status code | Status Code Description | Error Message
0x80050000 | BadCommunicationError | Unable to communicate with the server. This may be due to one of the following: The server is either not running or currently unreachable. The server could not be found using the specified endpoint configuration. The server does not trust the client certificate.
0x800E0000 | BadServerHalted
0x800C0000 | BadShutdown
0x800D0000 | BadServerNotConnected
0x80AE0000 | BadConnectionClosed
0x80310000 | BadNoCommunication
0x80840000 | BadRequestInterrupted
0x80860000 | BadSecureChannelClosed
0x80AD0000 | BadDisconnect
0x801F0000 | BadUserAccessDenied | The client may have a configuration issue. Potential causes: The specified user is not registered on the server. The user lacks the necessary security permissions. The server does not support the client's authentication mode.
0x80200000 | BadIdentityTokenInvalid
0x80210000 | BadIdentityTokenRejected
0x80100000 | BadTooManyOperations | The request was not processed as it specified too many operations.
0x80120000 | BadCertificateInvalid | The certificate provided by the server is invalid. Please try again.
0x80EE0000 | BadServerTooBusy | The server does not have the resources to process the request at this time.
0x80560000 | BadTooManySessions | The server has reached its maximum number of sessions.
0x80850000 | BadRequestTimeout | Timeout occurred while processing the request.
0x80BE0000 | BadProtocolVersionUnsupported | The OPC Client appears to have a configuration issue. Please check the endpoint URL.
*1 | *1 | An error occured while connecting to OPC server.

*1All other server exceptions will return the same error message, but with different status codes.