Search

Scope: Core (OPC-10000-*) All specs

26 result(s) for Condition Type

OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

ConditionType The ConditionType defines all general characteristics of a Condition . All other ConditionTypes derive from it. It is formally defined in Table 8 and Table 9 . The False state ... EnabledState shall not be extended with a sub state machine. Table 8 - ConditionType definition Attribute Value BrowseName ConditionType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseEventType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.2 Conditions

some step in the process before proceeding Each Condition instance is of a specific ConditionType . The ConditionType and derived types are sub-types of the BaseEventType ... exposed in the AddressSpace of the Server . Condition instances are specific implementations of a ConditionType . It is up to the Server whether such instances are also exposed in the Server
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

4.3 Acknowledgeable Conditions

Acknowledgeable Conditions AcknowledgeableConditions are sub-types of the base ConditionType . AcknowledgeableConditions expose states related to acknowledged or confirmed in a Condition . An AckedState and a ConfirmedState extend the EnabledState defined
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.1 General

General The Condition model extends the Event model by defining the ConditionType . The ConditionType introduces the concept of states differentiating it from the base Event model. Unlike the BaseEventType , Conditions ... transient. The ConditionType is further extended into Dialog and AcknowledgeableConditionType , each of which has their own sub-types. The Condition model is illustrated in Figure 10 and formally defined
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.4 Disable Method

ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . Since Condition instances are not required to be defined in the AddressSpace , the MethodId ... Call Service shall be the NodeId of the Disable Method on the ConditionType . Signature Disable(); Method Result Codes in Table 11 (defined in Call Ser v ice) Table 11 - Disable
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.5 Enable Method

ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . If the Condition instance is not exposed, then it may be difficult ... Call Service shall be the NodeId of the Enable Method on the ConditionType . Signature Enable(); Method result codes in Table 13 (defined in Call Ser v ice) Table 13 - Enable
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.6 AddComment Method

ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . Signature AddComment( [in] ByteString EventId [in] LocalizedText Comment ); The parameters are defined in Table ... specified ObjectId is not valid or that the Method was called on the ConditionType Node . See 10000-4 for the general description of this result code. Bad_InvalidArgument The Comment
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.7 ConditionRefresh Method

would require resynchronization with the Server . This Method is only available on the ConditionType . To invoke this Method , the call shall pass the well-known MethodId of the Method ... ConditionType and the ObjectId shall be the well-known NodeId of the ConditionType ObjectType . Signature ConditionRefresh( [in] IntegerId SubscriptionId ); The parameters are defined in Table 18 Table 18 - ConditionRefresh parameters
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.8 ConditionRefresh2 Method

single MonitoredItem in the Server . This Method is only available on the ConditionType . To invoke this Method , the call shall pass the well-known MethodId of the Method ... ConditionType and the ObjectId shall be the well-known NodeId of the ConditionType ObjectType . This Method is optional and as such Clients shall be prepared to handle Servers which
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.6.2 DialogConditionType

BrowseName DialogConditionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the ConditionType defined in clause 5.5.2 HasComponent Variable DialogState LocalizedText TwoStateVariableType Mandatory HasProperty Variable Prompt LocalizedText PropertyType ... column indicates that no ModellingRule applies. The DialogConditionType inherits all Properties of the ConditionType . DialogState/Id when set to True indicates that the Dialog is active and waiting for a response
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.1 General

Condition model. AcknowledgeableConditions are represented by the AcknowledgeableConditionType which is a subtype of the ConditionType . The model is formally defined in the following sub clauses
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.2 AcknowledgeableConditionType

AcknowledgeableConditionType The AcknowledgeableConditionType extends the ConditionType by defining acknowledgement characteristics. The AcknowledgeableConditionType is illustrated in Figure 13 and formally defined in Table 32 and Table 33 . Figure 13 - AcknowledgeableConditionType overview ... Value BrowseName AcknowledgeableConditionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the ConditionType defined in clause 5.5.2 . HasSubtype ObjectType AlarmConditionType Defined in Clause 5.8.2 HasComponent Variable AckedState LocalizedText
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.9.1 Overview

Process. The ConditionClass hierarchy is used to specify domains and is orthogonal to the ConditionType hierarchy. The ConditionClassId Property of the ConditionType is used to assign a Condition
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.12 HasCondition Reference type

their InstanceDeclaration Nodes . The TargetNode shall be a Condition instance declaration or a ConditionType . The following rules for instantiation apply: All HasCondition References used in a Type shall exist ... these Types as well. If the TargetNode in the Type definition is a ConditionType , the same TargetNode will be referenced on the instance. HasCondition References can be used solely
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

6.3 Adding Conditions to the hierarchy

Condition instance or - if no instance is exposed by the Server - to the ConditionType . Clients can locate Conditions by first browsing for ConditionSources following HasEventSource References (including sub-types like ... Reference Condition instances. The Object "Tank A" Reference s a ConditionType (MySystemAlarmType) indicating that a Condition exists but is not exposed in the AddressSpace . Figure
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.2 AddressSpace examples

illustrated with the example in Figure B.6 . Figure B.6 - HasCondition reference to a Condition type Figure B.7 provides an example where the HasCondition Reference is already defined in the Type ... system. The Reference can point to a Condition Type or to an instance. Both variants are shown in this example. A Reference to a Condition Type in the Type system
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.3 Event Type mapping

Event type Tracking. Those A & C Event s which are ConditionType are marked as A&E Event type Condition . Those A & C Event s which ... subtype except AuditEventType or ConditionType are marked as A&E Event type Simple. Figure D.2 - Mapping UA Event Types to COM A&E Event Types Note that
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.4 Event category mapping

Event types defined in the hierarchy of subtypes of ConditionType , including ConditionType itself. A&E Simple categories consist of the set of Event types defined in the hierarchy ... subtypes of BaseEventType excluding AuditEventType and ConditionType and their respective subtypes. Figure D.3 - Example mapping of UA Event Types to COM A&E categories Category name is derived from
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.5 Event Category attribute mapping

following items are present only for A&E Condition-Related Events szConditionName UA ConditionType Property: ConditionName szSubConditionName UA ActiveState Property: EffectiveDisplayName wChangeMask Calculated within Alarms and Events ... AlarmConditionType are set to ACTIVE by default. wNewState: OPC_CONDITION_ENABLED A & C ConditionType Property: EnabledState Events mapped as non-Condition Events are set to ENABLED (state bit mask
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

D.3.6 Event Condition mapping

D.3.6 Event Condition mapping Event s of any subtype of ConditionType are designated COM Condition Event s and are subject to additional processing due to the stateful nature of Condition ... triplet ENABLED|ACTIVE|ACKNOWLEDGED. In UA A & C, Event subtypes of ConditionType only carry a value which can be mapped to ENABLED (DISABLED) and optionally, depending on further
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.2 LogRecord EventType Mapping

EventTypes can be defined as needed for specific log information. If desired, subtypes of ConditionType or any of the AlarmTypes might also be used. The only requirement for an Event
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

9.4.2 IRootCauseIndicationType

IRootCauseIndicationType cannot only be applied to AlarmTypes , but in general to subtypes of 0: ConditionType . Table 16 - IRootCauseIndicationType Definition Attribute Value BrowseName IRootCauseIndicationType IsAbstract True Description Information on the root
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

12.1 Overview

IDeviceHealthType as container for those Objects. This specification does not define a specific 0: ConditionType for maintenance activities. Companion specifications or vendors might define their own 0: ConditionTypes for specific
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration

9.1 MultiAcknowledgeableConditionType

BrowseName MultiAcknowledgeableConditionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the Acknowledgeable ConditionType defined in OPC 10000-9, it inherits the InstanceDeclarations of that Node. 0:HasProperty Variable
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management

8.2.2.4 Error handling

active at any time. Error conditions are exposed as subtypes of the ConditionType defined in OPC 10000-9 and may have Acknowledge and Confirm methods and the appropriate state handling
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management

8.2.9.2 ErrorEventType

detail about the circumstances leading to the Error state shall be indicated by active ConditionType events. For more detail see Section 11 . It is formally defined in Table 94 . Table