Search

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

21 result(s) for ConditionId

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

5.1 General

Alarm or Condition . Instances not exposed in the AddressSpace still have a ConditionId ( NodeId ). This NodeId can be the target of references in the AddressSpace even though the target node
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.2 ConditionType

defined in 10000-5 . The NodeId of the Condition instance is used as ConditionId . It is not explicitly modelled as a component of the ConditionType . However, it can be requested ... detailed definition of the SelectClause in an Event Subscription . Table 10 - ConditionId SimpleAttributeOperand Illustration Name Type Description SimpleAttributeOperand typeId NodeId NodeId of the ConditionType Node browsePath[] QualifiedName empty attributeId IntegerId
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.3 Condition and branch instances

Objects which have a state which changes over time. Each Condition instance has a ConditionId as an identifier which uniquely identifies it within the Server . This Condition (and it representative ... ConditionId) follows the same rules associated with Nodes (and their representative NodeIds ) in the AddressSpace (see 10000-3 ). Therefore, once a Condition is created in a system that does
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.4 Disable Method

AddressSpace. Therefore, all Servers shall allow Clients to call the Disable Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.5 Enable Method

AddressSpace. Therefore, all Servers shall allow Clients to call the Enable Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node ... exposed, then it may be difficult for a Client to determine the ConditionId for a disabled Condition. Since Condition instances are not required to be defined in the AddressSpace
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.6 AddComment Method

Therefore, all Servers shall also allow Clients to call the AddComment Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.3 Acknowledge Method

AddressSpace. Therefore, Servers shall allow Clients to call the Acknowledge Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node . Signature ... AcknowledgeableConditionType or MethodId does not refer to a Method for the specified Object or ConditionId . Bad_EventIdUnknown See Table 137 for the description of this result code. Bad_NodeIdInvalid Used
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.4 Confirm Method

AddressSpace. Therefore, Servers shall allow Clients to call the Confirm Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node. Signature ... method id does not refer to a method for the specified object or ConditionId . See 10000-4 for the general description of this result code. Bad_EventIdUnknown See Table
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.5 Reset Method

AddressSpace. Therefore, Servers shall allow Clients to call the Reset Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.7 Silence Method

AddressSpace. Therefore, Servers shall allow Clients to call the Silence Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.8 Suppress Method

AddressSpace. Therefore, Servers shall allow Clients to call the Suppress Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.10 Unsuppress Method

AddressSpace. Therefore, Servers shall allow Clients to call the Unsuppress Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.12 RemoveFromService Method

AddressSpace. Therefore, Servers shall allow Clients to call the RemoveFromService Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.14 PlaceInService Method

AddressSpace. Therefore, Servers shall allow Clients to call the PlaceInService Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.2 Unshelve Method

Therefore, all Servers shall also allow Clients to call the Unshelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has Shelving child . The Method
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.4 TimedShelve Method

Therefore, all Servers shall also allow Clients to call the TimedShelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has the Shelving child ... with an ObjectId of the ShelvedStateMachineType Node . This Method can be called on any ConditionId , even if it is not active. The timer will start on Method invocation. The Alarm
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.6 OneShotShelve Method

Therefore, all Servers shall also allow Clients to call the OneShotShelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has the Shelving child ... with an ObjectId of the ShelvedStateMachineType Node . This Method can be called on any ConditionId , even if it is not active. Signature OneShotShelve( ); Method Result Codes are defined in Table
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.10.2 AuditConditionEventType

will be used as defined. The inherited Property SourceNode shall be filled with the ConditionId . The SourceName shall be "Method/" and the name of the Service that generated
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.2 Server maintains current state only

Events are coming from the same Condition instance and therefore have the same ConditionId . Figure B.1 - Single state example Table B.1 - Example of a Condition that only keeps the latest
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.3 Server maintains previous states

Events are coming from the same Condition instance and have therefore the same ConditionId . Figure B.2 - Previous state example Table B.2 - Example of a Condition that maintains previous states
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.1.4 Server current-State Model with Suppression

Events are coming from the same Condition instance and therefore have the same ConditionId . The Client subscription includes an event filter that excludes suppressed or out of service conditions