Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Connector for OPC UA Gen 1

Apply the filter based on OPC UA NodeIds

  • Last UpdatedJan 27, 2025
  • 3 minute read

In this mode, users have the option to reference a .csv file with a list of NodeIds, and several other optional columns. Only those OPC UA variables, which have their NodeIds listed in the file, will be subscribed for changes and will consequently forward events to the PI System. This mode is fundamentally different from the mode where the connector initially browses the whole OPC UA address space, and users have the option to select the templates (types) that they are interested in. The NodeId-based mode is more explicit and allows for providing additional parameters on a per-NodeId basis. The NodeId Table lists and explains them all, the most important being the CustomStreamId. If present, an entry in this column defines a PI point name. If such a PI point name does not exist, it is then created. If it does, the connector forwards events to it.

Note: In this mode, no PI AF hierarchy is created.

Node ID table

NodeId

(required)

The OPC UA variable's NodeId in the following format: ns=NamespaceIndex;IdentiferType=identifier

CustomStreamId

(optional)

The Stream name, which is used to name a PI point. Be aware that the OPC UA prefix will always be prepended, unless it is explicitly modified or disabled, see Modify the point prefix for more details. If the CustomStreamId is not specified, the NodeId is used.

SamplingInterval

(optional)

A time in milliseconds, which defines the fastest rate at which a given OPC UA variable will be accessed. If not specified, the SamplingInterval from the App.OpcUa.config* is taken.

QueueSize

(optional)

The requested size of the MonitoredItem queue. If not specified, the QueueSize from the App.OpcUa.config* is used.

MonitoringMode

(optional)

Determines if an OPC UA variable will be active or inactive. The corresponding OPC UA variable will be included in a subscription, but it won't produce OPC UA value event notifications if the MonitoringMode for the variable is disabled. MonitoringMode may be set to:

  • Disabled: a given variable is subscribed, but told to not send any OPC UA value event notifications

  • Reporting: a given variable is subscribed and allowed to send out OPC UA value event notifications

    The default is Reporting.

DataChangeTrigger

(optional)

The type of change that triggers an OPC UA value event notification:

  • Status: the status of a value that triggers the OPC UA value event notification

  • StatusValue: the value itself, or the status that triggers the OPC UA value event notification

  • StatusValueTimestamp: the (source) timestamp, or a value, or the status that triggers an OPC UA value event notification

    The default is StatusValue.

Deadband

(optional)

The dead-band. Additional input is specified in the DeadBandType column. Default is 0.

DeadbandType

(optional)

The DeadbandType can be Absolute, None, or Percent. The value event is triggered if the Abs(last value - new value) > DeadBand. The dead-band type=Percent is only valid for variables having the EURange defined. The Percent mode triggers an OPC UA value event notification of change only if a change is more than the specified percentage of the value range. The default is None.

Note: The order of all optional columns is not important. Any optional column can even be omitted and the default will be considered.

* The App.OpcUa.config* file can be found in %PIHOME64%\Connectors\OpcUa\Configuration. It is recommended to modify its content only in cooperation with AVEVA's TechSupport.

TitleResults for “How to create a CRG?”Also Available in