Search
16 result(s) for AcknowledgeableConditionType
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsAcknowledgeableConditionType 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 ... Table 32 - AcknowledgeableConditionType definition Attribute 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
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.5.1 GeneralBaseEventType , Conditions are not 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
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.7.1 Generalacknowledgement and confirmation are added to the Condition model. AcknowledgeableConditions are represented by the AcknowledgeableConditionType which is a subtype of the ConditionType . The model is formally defined in the following
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.7.3 Acknowledge MethodConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node . Signature Acknowledge( [in] ByteString EventId [in] LocalizedText Comment ); The parameters are defined in Table ... result code. Bad_MethodInvalid The MethodId is not the well-known method of the AcknowledgeableConditionType or MethodId does not refer to a Method for the specified Object or ConditionId
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.7.4 Confirm MethodConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node. Signature Confirm( [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 AcknowledgeableConditionType 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 & Conditions5.8.2 AlarmConditionTypeAlarmConditionType The AlarmConditionType extends the AcknowledgeableConditionType by introducing an ActiveState , SuppressedState and ShelvingState . It also adds the ability to set a delay time, re-alarm time, Alarm groups and audible ... AlarmConditionType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the AcknowledgeableConditionType defined in clause 5.7.2 HasComponent Variable ActiveState LocalizedText TwoStateVariableType Mandatory HasProperty Variable InputNode NodeId PropertyType
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.2.6 Condition instancesacknowledged by passing the EventId to the Acknowledge Method defined on the AcknowledgeableConditionType . Condition s cannot be enabled or disabled via the COM A&E Wrapper
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsENABLED (state bit mask = 0x1) by default. wNewState: OPC_CONDITION_ACKED A & C AcknowledgeableConditionType Property: AckedState A & C Events mapped as non-Condition Events or which ... derive from AcknowledgeableConditionType are set to UNACKNOWLEDGED and AckRequired = False by default. wQuality A & C ConditionType Property: Quality Events mapped as non-Condition Events are set to OPC_QUALITY
-
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration7.11.1 Overviewenable the Client to acknowledge conditions. By exposing at least one instance of AcknowledgeableConditionType inside the Server's AddressSpace located within the Conditions folder as defined in the ConformanceUnit RobAckCondInstance
-
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integrationfrom the OperationStateMachineType. The folder Conditions (part of the ConformanceUnit RobAckCondInstance ) provides instances of AcknowledgeableConditionType for the acknowledgement of single conditions or instances of MultiAcknowledgeableConditionType (see 8.1) for the acknowledgement ... subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others Conditions Organizes Object <AcknowledgeableCondition> AcknowledgeableConditionType MP Table 44 - SystemOperationType Attribute values for child Nodes BrowsePath Value Attribute Description Attribute
-
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical IntegrationPropertyType M Conformance Units Rob RobAckCondInstance The MultiAcknowledgeableConditionType inherits all Properties of the AcknowledgeableConditionType. The Variable ConditionDescriptions provides in an Array of descriptions of all conditions, which need acknowledgement. When ... start. Confirmation of the MultiAcknowledgeableConditionType instances (using the optional Confirm method, inherited from the AcknowledgeableConditionType ) is undefined and out of scope
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management8.2.8.4 ConfirmAll methodserver derived from VisionConditionType . In analogy to the Confirm method of the AcknowledgeableConditionType it expects a LocalizedText as a comment, not, however an EventId as this would not make sense
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management11.4.4.3 Usage of additional propertiesfollowing describes the usage of the properties added by VisionConditionType with respect to AcknowledgeableConditionType . ErrorString A system specific string classifying the error / warning. ErrorCode A system specific numeric code classifying
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management11.4.5 VisionWarningConditionTypeSection 11.3.4 . The server can use the AckedState and ConfirmedState variables of the AcknowledgeableConditionType to control whether the vision system requires acknowledgement and confirmation of the condition as described
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management11.4.6 VisionErrorConditionTypeSection 11.3.5 . The server can use the AckedState and ConfirmedState variables of the AcknowledgeableConditionType to control whether the vision system requires acknowledgement and confirmation of the condition as described
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result managementSection 11.3.6 . The server can use the AckedState and ConfirmedState variables of the AcknowledgeableConditionType to control whether the vision system requires acknowledgement and confirmation of the condition as described