---
title: OPC UA Client (Gen1)
slug: litmusedge-v1/quickstart-guide/industrial-systems-connection-guide/opc-ua/opc-ua-client-gen1
description: Review the following information for setting up and configuring the OPC UA Client (Gen1) driver. 
docTags: 
createdAt: 2023-05-05T20:19:38.000Z
---

:::hint{type="warning"}
**Important**: This driver was deprecated in Litmus Edge version 3.5.2. We recommend using the Gen 2 [OPC UA Client Advanced](docId\:ezRIJipeot9AN_kGPympR).
:::

Review the following information for setting up and configuring the OPC UA Client (Gen1) driver. 

# Litmus Edge Compatible Series 

| Compatibility parameter        | Compatible items                                                                     |
| ------------------------------ | ------------------------------------------------------------------------------------ |
| **Driver type**                | Ethernet                                                                             |
| **Validated devices/series**   | Unified Automation<br />Prosys<br />[](https://opcfoundation.org/certified-products) |
| **Replaced with Gen 2 driver** | [OPC UA Client Advanced](docId\:ezRIJipeot9AN_kGPympR)                               |

# Supported Servers

## OPC UA Client

- Used to poll data from OPC UA servers.
- Does not allow subscription mode.
- Mostly used for systems which have less number of tags or using a DA to UA wrapper. Example: SIKORA or older HMI Systems.

# Set up the PLC Device in DeviceHub

Configure the following parameters when you [Connect a Device](docId\:pal6ABPZbrimdU9LvGJ30) with this driver. Update default values to the specific setup of your device.&#x20;

| Parameter           | Value                 |
| ------------------- | --------------------- |
| **Type**            | OPC UA                |
| **Driver**          | OPC UA Client (Gen1)  |
| **Network Address** | The device IP address |
| **Network Port**    | 4840                  |

# Configure the List of Registers

:::hint{type="info"}
**Notes**:

- Certain device drivers do *not* have a list of Register Names in the DeviceHub Add/Edit Tag form. These are *Free Tag* PLCs. For Free Tag requirements, see [Device Connectivity Issues](docId\:cEy2HVJQ2J6nOkUsBSqDs).
- For the Register Name, in the DeviceHub Add/Edit Tag form, map the OPC server tags to the client using this format: `ns=1;s=tagname`.&#x20;
  - Example: `ns=2;s=Demo.Static.Scalar.Boolean`
- **Server Name** currently is not used, however, an entry must be made in this field.
- The **Browse&#x20;**&#x69;con displayed on the device tile means that this PLC uses Browse Tags. See [Add Tags](docId:8sE7z3PmRfwL1nmzcwaLX) for more information.&#x20;
:::

When you [Add Tags](docId:8sE7z3PmRfwL1nmzcwaLX) to the connected device, use the following tag/register mapping table.

| **Name** | **Value Type** |
| -------- | -------------- |
| R        | BOOL           |
| R        | BYTE           |
| R        | CHAR           |
| R        | SHORT          |
| R        | WORD           |
| R        | LONG           |
| R        | DWORD          |
| R        | FLOAT          |
| R        | DOUBLE         |
| R        | STRING         |
| R        | BoolArray      |
| R        | ByteArray      |
| R        | CharArray      |
| R        | ShortArray     |
| R        | WordArray      |
| R        | LongArray      |
| R        | DWordArray     |
| R        | FloatArray     |
| R        | DoubleArray    |