QuickOPC User's Guide and Reference
SubscribeMonitoredItem(IEasyUAClient,EasyUAMonitoredItemArguments) Method



OpcLabs.EasyOpcUA Assembly > OpcLabs.EasyOpc.UA Namespace > IEasyUAClientExtension Class > SubscribeMonitoredItem Method : SubscribeMonitoredItem(IEasyUAClient,EasyUAMonitoredItemArguments) Method
The client object that will perform the operation.
Array of arguments, one element per each monitored item involved in the operation.
Subscribe to changes of a particular monitored item. For each significant monitored item change, either the IEasyUAClient.DataChangeNotification event is generated, or a specified callback method is invoked. Subscribe to a monitored item, specifying an object that holds all necessary arguments (the object can optionally contain the callback method as well).
Syntax
'Declaration
 
<ExtensionAttribute()>
Public Overloads Shared Function SubscribeMonitoredItem( _
   ByVal client As IEasyUAClient, _
   ByVal monitoredItemArguments As EasyUAMonitoredItemArguments _
) As Integer
'Usage
 
Dim client As IEasyUAClient
Dim monitoredItemArguments As EasyUAMonitoredItemArguments
Dim value As Integer
 
value = IEasyUAClientExtension.SubscribeMonitoredItem(client, monitoredItemArguments)

Parameters

client
The client object that will perform the operation.
monitoredItemArguments
Array of arguments, one element per each monitored item involved in the operation.

Return Value

The method returns an integer handle that uniquely identifies the monitored item subscription.
Exceptions
ExceptionDescription

A null reference (Nothing in Visual Basic) is passed to a method that does not accept it as a valid argument.

This is a usage error, i.e. it will never occur (the exception will not be thrown) in a correctly written program. Your code should not catch this exception.

Remarks

It is more efficient to subscribe to multiple monitored items using SubscribeMultipleMonitoredItems method.

 

This method operates (at least in part) asynchronously, with respect to the caller. The actual execution of the operation may be delayed, and the outcome of the operation (if any) is provided to the calling code using an event notification, callback, or other means explained in the text. In a properly written program, this method does not throw any exceptions. You should therefore not put try/catch statements or similar constructs around calls to this method. The only exceptions thrown by this method are for usage errors, i.e. when your code violates the usage contract of the method, such as passing in invalid arguments or calling the method when the state of the object does not allow it. Any operation-related errors (i.e. errors that depend on external conditions that your code cannot reliably check) are indicated by the means the operation returns its outcome (if any), which is described in the text. For more information, see Do not catch any exceptions with asynchronous or multiple-operation methods.
Requirements

Target Platforms: .NET Framework: Windows 10 (selected versions), Windows 11 (selected versions), Windows Server 2016, Windows Server 2022; .NET: Linux, macOS, Microsoft Windows

See Also