OPC Studio User's Guide and Reference
IEasyUAAlarmsAndConditionsClientExtension Class
Members 



OpcLabs.EasyOpcUA Assembly > OpcLabs.EasyOpc.UA.AlarmsAndConditions.Extensions Namespace : IEasyUAAlarmsAndConditionsClientExtension Class
Extends OpcLabs.EasyOpc.UA.AlarmsAndConditions.IEasyUAAlarmsAndConditionsClient.
Syntax
'Declaration
 
<ExtensionAttribute()>
<ComVisibleAttribute(False)>
<ExceptionContractAnnotationAttribute(True)>
<ExceptionContractVerificationAttribute(True)>
Public MustInherit NotInheritable Class IEasyUAAlarmsAndConditionsClientExtension 
[Extension()]
[ComVisible(false)]
[ExceptionContractAnnotation(true)]
[ExceptionContractVerification(true)]
public static class IEasyUAAlarmsAndConditionsClientExtension 
[Extension()]
[ComVisible(false)]
[ExceptionContractAnnotation(true)]
[ExceptionContractVerification(true)]
public ref class IEasyUAAlarmsAndConditionsClientExtension abstract sealed 
Remarks

This class contains extension methods (info: C#, VB.NET). In languages that have support for extensions methods (such as C# and VB.NET), you can use the extension method as if it were a regular method on the object that is its first parameter. In other languages (such as with Python.NET), you will call the extension as a static method, and pass it the object on which it acts as its first parameter.

 

Methods described in this chapter allow your application to modify information in the underlying data source that the OPC server connects to or in the OPC server itself (acknowledging conditions). It is assumed that your application already somehow knows how to identify the data it is interested in. If the location of the data is not known upfront, use methods described Browsing for Information chapter first.

The operations performed by the methods described here are actually implemented inside the OPC server. The OPC specification defines OPC UA methods for that, and as such, you could use e.g. one of the EasyUAClient.CallMethod overloads in order to achieve the same outcome. You would have to, however, look up and specify the Node ID of the desired method, and properly assemble the array of input arguments (with proper types), and so on. The methods described below make it easier, and do the boring part for you. They are all implemented in a specialized client object for OPC UA Alarms and Conditions (EasyUAAlarmsAndConditionsClient Class), which you can derive from the IEasyUAClient, or instantiate standalone.

The easiest way to access the functionality is usually to call the AsAlarmsAndConditionsClient Method on the IEasyUAClient Interface you already have. See Specialized Client Objects for more details. For an example of how to do that, see Examples - OPC UA Alarms&Conditions - Acknowledge an event.

The features discussed here, or some of them, may not be available in all editions of the product. Check the QuickOPC Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.

 

Inheritance Hierarchy

System.Object
   OpcLabs.EasyOpc.UA.AlarmsAndConditions.Extensions.IEasyUAAlarmsAndConditionsClientExtension

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