Multiple Read VI

Owning Palette: OPC UA Client VIs

Requires: OPC UA Toolkit

Reads the value, timestamp, and status of one or multiple nodes. NI recommends choosing the Variant instance for all value data types. You must manually select the polymorphic instance to use.

Example

Multiple Read (Variant)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. value can also return the Matrix data type. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Bool)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (SByte)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Byte)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int16)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value is the number read from shared memory. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt16)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int32)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value of the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt32)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int64)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt64)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Float)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Double)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (String)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (DateTime)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (ByteString)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. value returns the value that this VI reads from the node. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Bool Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (SByte Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Byte Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int16 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt16 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int32 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt32 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Int64 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (UInt64 Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Float Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (Double Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (String Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (DateTime Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Multiple Read (ByteString Array)

	OPC UA client refnum in specifies the reference for the OPC UA client.
	node IDs specifies the IDs of the 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, node IDs 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.
	error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
	timeout specifies the maximum time, in milliseconds, that this VI waits to get a response from the OPC UA server. The default is 5000.
	OPC UA client refnum out returns the reference for the OPC UA client.
	results returns the IDs of the nodes, the values of the nodes, the timestamps associated with the values, and the statuses of the nodes. node ID returns the ID of the node. values returns the values that this VI reads from the nodes. timestamp returns the date and time associated with value. status returns the status code.
	error out contains error information. This output provides standard error out functionality.
	service status returns the status of an OPC UA service call. OPC UA services contain parameters that are conveyed between an OPC UA client and an OPC UA server.

Example

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