Add Condition VI

Owning Palette: Alarms and Conditions VIs

Requires: OPC UA Toolkit

Adds a condition node to the notifier.

You must manually select the polymorphic instance to use.

Details  Example

Add Dialog Condition

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the properties of the condition node. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. prompt specifies the textual content of a dialog prompt. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA dialog condition refnum out returns the reference to the dialog condition. The OPC UA server uses the dialog condition to request user input.
	error out contains error information. This output provides standard error out functionality.

Add Off-Normal Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the properties of the condition node. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. normal state node ID specifies the ID of the node that has a value corresponding to one of the possible values of the source node. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA off normal alarm refnum out returns the reference to an off-normal alarm condition node. An off-normal alarm condition represents an abnormal condition.
	error out contains error information. This output provides standard error out functionality.

Add Exclusive Level Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Exclusive Deviation Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. setpoint node ID specifies the ID of the setpoint node in the deviation calculation. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Exclusive Rate of Change Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Nonexclusive Level Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Nonexclusive Deviation Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. setpoint node ID specifies the ID of the setpoint node in the deviation calculation. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Nonexclusive Rate of Change Alarm

	OPC UA server refnum in specifies the reference data value of the OPC UA server.
	notifier node ID specifies the ID of the notifier. A notifier is an object that you can subscribe to get events from the associated condition nodes. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, notifier node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item.
	property specifies the property of the condition instance. condition name specifies the name of the condition instance. source node ID specifies the node ID of the condition source. A condition source is an element that a specific condition is based upon or related to. The format of the node ID is ns=<namespace index>;<identifier type>=<identifier>. A node ID contains the following components: namespace index is a base 10 number that indicates the namespace of the node ID. If namespace index is 0, the format of the node ID can be <identifier type>=<identifier>. The namespace index for a node that you created with the OPC UA Toolkit is 2. identifier type represents the type of the identifier and has the following values: Value Identifier Type i Numeric s String g GUID b Opaque identifier is a string value that represents the name of the identifier. The format of the node ID can also be ns=<namespace index>;<identifier type>=<identifier>@<index>:<index>. For example, ns=2;s=Folder.Array@1:2. This format only applies to the array data type and allows you to read a single element or a range of elements of an array. You cannot use @ in a node name. For backwards compatibility, source node ID also accepts node paths as input for OPC UA servers only. You can regard the node path as the string type identifier of the node ID. For example, a node path can be Device.folder.item. limit specifies the values that causes LabVIEW to generate an alarm. high high limit specifies the value above which LabVIEW generates a high high limit alarm. high limit specifies the value above which LabVIEW generates a high limit alarm. low limit specifies the value below which LabVIEW generates a low limit alarm. low low limit specifies the value below which LabVIEW generates a low low limit alarm. description specifies additional information of the condition.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	OPC UA server refnum out returns the reference data value of the OPC UA server.
	condition node ID returns the ID of the condition node.
	OPC UA limit alarm refnum out returns the reference to the OPC UA limit alarm condition.
	error out contains error information. This output provides standard error out functionality.

Add Condition Details

The dialog is a condition that an OPC UA server uses to request user input.

Alarms are specializations of acknowledgeable conditions that add the concepts of an active state, a shelving state, and a suppressed state to a condition. This VI supports the following alarm types:

• Off-normal alarm—Specifies a condition that is not normal.
• Limit alarm—Specifies limits that can generate an alarm when a value equals or exceeds the limit. There are four alarm limits: high high limit, high limit, low limit, and low low limit. This VI supports the following limit alarm types:
  • Exclusive alarm—Contains multiple mutually exclusive limits. For an exclusive alarm, multiple states can be active at the same time.
  • Nonexclusive alarm—Contains multiple nonexclusive limits. For a nonexclusive alarm, only one state can be active at a specific time.
  • Level alarm—Reports when a limit is exceeded.
  • Deviation alarm—Reports an excess deviation between a desired setpoint level of a value and an actual measurement of that value.
  • Rate of change alarm—Reports an unusual change or lack of change in a measured value related to the speed at which the value has changed.

The condition type affects the available data types of the source node and the normal state node:

• For the dialog condition type, the data type of the source node must be Boolean.
• For the off-normal alarm condition type, the data type of the source node and the normal state node must be scalar and they must have the same data type.
• For the deviation alarm condition type and level alarm condition type, the data type of the source node must be Double.
• For the rate of change alarm condition type, the source node must be analog data and the data type must be scalar.

Example

Refer to the OPC UA Demo.lvproj in the labview\examples\Data Communication\OPCUA directory for an example of using the Add Condition VI.