---
title: B&R PVI Ethernet
slug: litmusedge/bandr-pvi-ethernet
docTags: 
createdAt: 2026-01-21T17:36:31.691Z
---

Review the following information for setting up and configuring the B\&R PVI Ethernet driver.

:::hint{type="info"}
**Note:** The B\&R PVI Ethernet driver supports up to 10,000 tags and enables high-density deployments with large B\&R PLC installations.
:::

## Litmus Edge Compatible Series

| Compatibility parameter      | Compatible items  |
| ---------------------------- | ----------------- |
| **Driver type**              | Ethernet          |
| **Validated devices/series** | B\&R X20CP Series |
| **Replaces Gen 1 driver(s)** | N/A               |

To set up and configure this device in Litmus Edge, you will need to do the following:

- Step 1: Set up and Configure the PLC Device
- Step 2: Set up the PLC Device in Litmus Edge DeviceHub
- Step 3: Configure the List of Registers

## Step 1: Set up and Configure the PLC Device

1. Ensure your B\&R PLC is configured with PVI (Process Visualization Interface) enabled.
2. Record the PLC's IP address for Ethernet communication.
3. Verify that the PVI service is running on the PLC (default port: 11169).
4. Ensure network connectivity between Litmus Edge and the B\&R PLC.
5. Confirm that the necessary variables are defined in your Automation Studio project.

## Step 2: Set up the PLC Device in Litmus Edge 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.

| Parameter           | Value                                  |
| ------------------- | -------------------------------------- |
| **Type**            | B\&R                                   |
| **Driver**          | B\&R PVI Ethernet                      |
| **Network Address** | The IP address you recorded in Step 1. |
| **Port**            | 11169                                  |

## Step 3: Configure the List of Registers

When you [Add a Tag](docId\:Tuy-hh0Gi8DjVOT70wRoh) to the connected device, refer to the following register table and tag parameters. Refer to the following additional resources:

- [Organize Device and Tag Data by Using Metadata](docId\:MU-6j6Zhi0CvCHDad0w8n)
- [Tag Formula Variables](docId\:Io7xgyrdVv_vmpnFXOACi) 

## Register Table

| Name | Value Types                                                    | Access Types | Description |
| ---- | -------------------------------------------------------------- | ------------ | ----------- |
| R    | BOOL, USINT, UINT, UDINT, SINT, INT, DINT, REAL, LREAL, STRING | R/W          | Variables   |

## Tag Parameters

- **Name**: Select a register name from the drop-down list. The available options depend on the names in the register table.
- **Value Type**: Select a data type from the drop-down list. 
- **Polling Interval**: Enter a value in milliseconds. This determines how often the tag should poll the register for data.
- **Tag Name**: Enter a name for the tag.
- **Description** (Optional): Enter a description for the tag.
- **Task**: Enter the task name where the variable is defined in the B\&R PLC. Leave blank to use the default task context.
- **Tag Formula**: Enter a formula for the tag to process the generated data. Two variables are permitted: `value` (current tag value) and `timestamp` (current tag UNIX time in milliseconds). The following math functions are available: 
  - sin
  - cos
  - sqrt
  - tan
  - power: power (`x`) performs the operation `10^x`
  - log: log (`x`) is the natural logarithm (the logarithm is in base `e`)
  - exp: exp (`x`) performs the operation `e^x`
- **Only Publish on Change of Value**: Select the checkbox to customize NATS messages to be published only when the value parameter changes from a previous value to a new one. **Change of Value** only applies to boolean, numeric (such as int or float), and simple string data types. It does not apply to complex types, such as JSON or array. Poll-once topics will not be affected by **Change of Value** settings. These topics will still only see a single message.
- **Meta Data**: Metadata summarizes basic information about data. This feature allows you to define key-value pair data for the device output payload later on. It can then be used to find, use, and reuse particular instances of data.

:::hint{type="info"}
**Note**: If you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload. This can cause two key names to be combined into one. For example, configuring the key names a\*\*b and a&\&b will cause only one key name to be created (a\_\_b).
:::