Difference between revisions of "uaCap:AlarmsConditions Instances"

From UaCapabilities
Jump to: navigation, search
(Created page with "{{CapabilityUri|/Alarms/Instances}} '''Description''' <br>By default the notification of events generated by transition between states are the only way to detect alarm & cond...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
{{CapabilityUri|/Alarms/Instances}}
 
{{CapabilityUri|/Alarms/Instances}}
 
 
'''Description'''
 
'''Description'''
 
<br>By default the notification of events generated by transition between states are the only way to detect alarm & condition situations. When instances are supported, a client can browse the address space and discover the items that the server considers of interest, such as alarms.
 
<br>By default the notification of events generated by transition between states are the only way to detect alarm & condition situations. When instances are supported, a client can browse the address space and discover the items that the server considers of interest, such as alarms.
  
 
'''Usage Considerations'''
 
'''Usage Considerations'''
<br>In some systems clients may want to access some aspects of alarm or condition information in manner other than via the event notifications.  For example a client may need to know the possible error state an object could encounter. In these systems the server would have to expose Alarm and Condition instances, to allow the client to browse the Alarm and Conditions.
+
* In some systems clients may want to access some aspects of alarm or condition information in manner other than via the event notifications.  For example a client may need to know the possible error state an object could encounter. In these systems the server would have to expose Alarm and Condition instances, to allow the client to browse the Alarm and Conditions.
 
+
* Allows using Clients that are able to access data but not events.
{{uaConformance|TBD <!-- Client -->|
+
* Allows enabling and disabling of Alarms
TBD <!-- Server -->
+
{{uaConformance|
<!-- Example
+
* [http://opcfoundation.org/UA-Profile/Client/ACAddressSpaceInstance '''Use of Alarm instances''']
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
+
* [http://opcfoundation.org/UA-Profile/Client/ACEnable '''Enable / disable Alarms''']
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
+
|
-->
+
* [http://opcfoundation.org/UA-Profile/Client/ACAddressSpaceInstance '''Use of Alarm instances''']
 +
* [http://opcfoundation.org/UA-Profile/Server/ACEnable '''Alarms can be enables and disabled''']
 
}}
 
}}

Latest revision as of 13:34, 16 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Alarms/Instances

Description
By default the notification of events generated by transition between states are the only way to detect alarm & condition situations. When instances are supported, a client can browse the address space and discover the items that the server considers of interest, such as alarms.

Usage Considerations

  • In some systems clients may want to access some aspects of alarm or condition information in manner other than via the event notifications. For example a client may need to know the possible error state an object could encounter. In these systems the server would have to expose Alarm and Condition instances, to allow the client to browse the Alarm and Conditions.
  • Allows using Clients that are able to access data but not events.
  • Allows enabling and disabling of Alarms

Conformance Testing

Client Server