OPCUA Collector Features
Important: You do not have the latest version of Historian! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Historian product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.
Summary of OPCUA Collector Features
The following table outlines the features of the OPCUA Collector.
| Feature | Capability |
|---|---|
| Browse Source For Tags | Yes (on OPCUA Servers that support browsing) |
| Browse Source For Tag Attributes | Yes |
| Polled Collection | Yes |
| Minimum PollInterval | 100 ms |
| Unsolicited Collection | Yes. If you are using an OPCUA Collector with unsolicited data collection and have collector compression disabled, all new values should produce an exception. When the OPCUA Collector is doing unsolicited collection, the deadband percentage is determined by the collector deadband percent. You can only configure the collector deadband percent by enabling compression. |
| Timestamp Resolution | 1ms |
| Accept Device Timestamps | Yes |
| Floating Point Data | Yes |
| Integer data | Yes |
| String data | Yes |
| Binary data | Yes |
| Python Expression Tags | Yes |
Note: You must set Time Assigned by field to Source if you have unsolicited tags getting data from an OPCUA Collector.
Tag Attributes Available In Browse (OPCUA Data Collectors)
The following table outlines the tag attributes available when browsing.
| Attribute | Capability |
|---|---|
| Tagname | Yes |
| Source Address | Yes |
| Polled Collection | Yes. See Selecting Data Types |
| Hi Engineering Units | Yes, varies by OPCUA Server Vendor. |
| Lo Engineering Units | Yes, varies by OPCUA Server Vendor. |
| Hi scale | Yes |
| Lo scale | Yes |
| Is array tag | No |
| Integer data | Yes |
Note: While some of these attributes are queried on a browse, they are not shown in the browse interface. These attributes are used when adding a tag, but you will not be able to see whether or not all attributes come from the server.
Recommended Data Types
The following table lists the data types recommended for use with Historian.
| OPCUA Data Type | Recommended Data Type in Historian |
|---|---|
| I1 - 16 bit signed integer | Single integer |
| I4 - 32 bit signed integer | Double integer |
| R4- 32 bit float | Single float |
| R8- 64 bit double float | Double float |
| UI2- 16 bit unsigned single integer | Unsigned single integer |
| UI4- 32 bit unsigned double integer | Unsigned double integer |
| UI8- 64 bit unsigned quad integer | Unsigned quad integer |
| I8- 64 bit quad integer | QuadInteger |
| BSTR | Variable string |
| BOOL | Boolean |
| I1- 8 bit single integer | Byte |
Note: The OPCUA Collector requests data from the OPCUA server in the native data type. Then the OPCUA collector converts the received value to a Historian Data Type before sending it to the Data Archiver.