Data collection
- Last UpdatedJun 26, 2025
- 2 minute read
- PI System
- Adapter for OPC UA 1.6
- Adapters
The OPC UA adapter collects time-series data from selected OPC UA dynamic variables through OPC UA subscriptions (unsolicited reads) or polling (cyclic reads) and event notifications from selected Event Types. The adapter supports the Data Access (DA), Historical Data Access (HDA) and Alarms and Conditions parts of the OPC UA specification.
For more information, see the following OPC UA Foundation specifications:
-
Data Access (https://opcfoundation.org/developer-tools/documents/view/165),
-
Historical Data Access (https://opcfoundation.org/developer-tools/documents/view/168)
-
Alarms and Conditions (https://opcfoundation.org/developer-tools/documents/view/166)
Data types
The following table lists OPC UA variable types that the adapter collects data from and types of streams that will be created. Types not listed below are currently unsupported.
|
OPC UA data type |
Stream data type |
|---|---|
|
Boolean |
Boolean |
|
SByte |
Int16 |
|
Int16 |
Int16 |
|
UInt16 |
UInt16 |
|
Int32 |
Int32 |
|
UInt32 |
UInt32 |
|
Int64 |
Int64 |
|
UInt64 |
UInt64 |
|
Double |
Float64 |
|
Decimal |
Float32 |
|
Float |
Float32 |
|
DateTime |
DateTime |
|
UtcTime |
DateTime |
|
String |
String |
|
Number |
variable, depending on the actual value |
|
Integer |
Integer |
|
UInteger |
UInteger |
|
Enumeration |
Int16 |
AVEVA Adapter for OPC UA attempts to verify the data type for each data selection item before adding the item to the subscription on the OPC UA server. Verified data selection items with supported types and data selection items for which the type cannot be verified are added to the subscription. Data selection items with unsupported data type are not added to the subscription and a message including the NodeId and TypeId is logged.
The adapter collects event notifications generated from the standard Event Types available in the OPC UA Server's Event Type library (Event Types folder). The adapter also supports any custom event types that are available on the server. The event fields of the events received are processed as streams of String data type.