AVEVA Adapter for OPC UA 1​.6 release notes

AVEVA Adapter for OPC UA 1.6.0.296, released June 2025, is a feature release that includes support for Alarms and Conditions for processing events in addition to data values. Version 1.6.0.296 uses version 1.8.3.128 of the Adapter Framework.

For more information on product features and functions, refer to the following sections:

• Prerequisites and system requirements

• Installation/uninstallation instructions

refer to AVEVA Adapter for OPC UA.

The latest information about the 1.6 release is available online on the AVEVA Documentation Portal.

New features and enhancements

The following items were added in this release:

• Support for Alarms and Conditions.

• Support for typeless Enumeration Sets.

• Unified Automation Library upgraded to version 4.1.1.

• Messages logged with a UA status code include the user friendly description from the UA library.

• Logging enhancements, such as suppressed unwanted logs, added enhanced logs at Information level, added logs for adapter connection status changes, and a warning log when a variable's node type definition does not match the data type sent by the server.

• Client Settings now recognizes Failover, Discovery, History Recovery and Server Read operations.

• DiscoveryType values within the Discovery query are now case insensitive.

• Support for users to specify whether to replicate certain properties from the data source or keep existing value in the data endpoint.

• WiX Toolset upgraded to version 5 for Windows Installer.

Resolved issues

This section lists items resolved in this release:

• The adapter properly handles BadNoContinuationPoints Status Codes. All data on the server is returned when ContinuationPoint is needed.

• When subscriptions are deleted due to BadTimeout error, the adapter recreates them so that the data flow can continue without requiring a restart.

• During reconnects to the server, the adapter does not send duplicate CreateMonitoredItems

• If data payloads sent to PI Web API OMF endpoint exceed 972 characters, the value is trimmed and suffixed with [TRUNCATED], and an HTTP 409 error code is logged in the adapter logs. This is reflected in PI Web API 2023 SP1 Patch 1 and later.

• The adapter skips over nodes with invalid Data Types and continues to collect data for any valid nodes. A warning is logged in the adapter logs.

• Client settings can be configured in the adapter even when Data Source is not set.

• The adapter skips History Recovery if a node's History Read Result operation returns DataValue property as NULL.

• Addressed issue where rounding errors could cause failover score to go above 100. This prevented the client failover feature from working properly.

Known issues

This section lists problems and/or enhancements that have been deferred until a future release:

Security information and guidance

We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.

We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release. The tables below provide an overview of security issues addressed and their relative severity based on standard scoring.

Overview of new vulnerabilities - Fixed or Mitigated

This section is intended to provide relevant security-related information to guide your installation or upgrade decision. AVEVA is proactively disclosing aggregate information about the number and severity of AVEVA Adapter for OPC UA security vulnerabilities that are fixed in this release.

For this release of AVEVA Adapter for OPC UA, the following vulnerabilities have been fixed or mitigated.

Security vulnerabilities fixed in AVEVA Adapter for OPC UA 1.6.0.296 release

Vulnerability mitigations in AVEVA Adapter for OPC UA 1.6.0.296 release

Distribution kits

AVEVA Adapter for OPC UA is supported on a variety of platforms and processors. Install kits are available for the following platforms:

Alternatively, you can use tar.gz files with binaries to build your own custom installers or containers for Linux. For more information on installing the adapter with Docker containers, see Install using Docker.