Search
16 result(s) for HasNotifier
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.5.1 Object NodeClasstheir "SubscribeToEvents" bit set in the EventNotifier Attribute . See 7.17 for details. HasNotifier 0..* The HasNotifier Reference points to notifiers of the Object . References of this type ... most one HasModellingRule Reference pointing to a ModellingRule Object . ModellingRules are defined in 6.4.4 . HasNotifier and HasEventSource References are used to provide information about eventing and can only be applied
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelHasTypeDefinition - BaseObjectType /F/H HasTypeDefinition - PropertyType /B/J HasTypeDefinition - PropertyType /B HasComponent /B/H - /B/H HasTypeDefinition - BaseDataVariableType / HasNotifier /B - /B HasProperty /B/D - / HasComponent /C - / Y /C - /C HasTypeDefinition - BaseDataVariableType /B/D HasTypeDefinition - PropertyType /B/D ... exists in the table so it does not need to be added. However, the HasNotifier reference from "/" to "/B" does not exist and was added
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.18 HasNotifierHasNotifier The HasNotifier ReferenceType is a concrete ReferenceType and can be used directly. It is a subtype of HasEventSource . The semantic of this ReferenceType is to relate Object Nodes that
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsEventNotifier and source hierarchy HasNotifier and HasEventSource References are used to expose the hierarchical organization of Event notifying Objects and ConditionSources . An Event notifying Object represents typically an area ... available, they shall be linked together and with the included ConditionSources using the HasNotifier and the HasEventSource Reference Types . The Server Object shall be the root of this hierarchy. Figure
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsConditions by first browsing for ConditionSources following HasEventSource References (including sub-types like the HasNotifier Reference ) and then browsing for HasCondition References from all target Nodes of the discovered References ... Figure 27 shows the application of the HasCondition Reference in a HasNotifier hierarchy. The Variable LevelMeasurement and the Object "Device B" Reference Condition instances. The Object "Tank
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.2 HasEffectDisabledisabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are disabled, If the target is an AlarmType then all instances ... that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are disabled, If the target is an Alarm instance then the given Alarm instance is disabled. The SourceNode
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.3 HasEffectEnableenabled. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are enabled, If the target is an AlarmType then all instances ... that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are enabled If the target is an Alarm instance then the given Alarm instance is enabled. The SourceNode
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionstarget is an AlarmType then all instance of that AlarmType in the HasNotifier hierarchy below the Object containing the StateMachine are suppressed, If the target is an Alarm instance then
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionssuppressed. If the Reference is to an Object then all Alarms in the HasNotifier hierarchy below that Object are removed from being suppressed, If the target is an AlarmType then
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions9.1 Overviewentire Server . An instance might also be provided on an Object that includes a HasNotifier hierarchy, such as a tank Object . In this case, it would provide the summary ... Alarms that are part of the tank HasNotifier hierarchy
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions9.2 AlarmMetricsTypemetrics are desired for Tank A Object (see Figure B.5 ) that is in the HasNotifier hierarchy than an instance of this object would be referenced by the Tank A object
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsAddressSpace examples This Clause provides additional examples for the use of HasNotifier , HasEventSource and HasCondition References to expose the organization of areas and sources with their associated Conditions . This hierarchy
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.2.1 Event areasBrowseName that depends on the UA Server . It is always the target of a HasNotifier Reference from the Server Node . The root Area allows multiple A&E COM Server ... combination of machine and COM Server . Each Area is the target of HasNotifier Reference from its parent Area. It may be the source of one or more HasNotifier Reference
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.2.3 Event categoriesfrom the Event Categories and Condition Names are placed in the standard OPC UA HasNotifier hierarchy. Figure D.1 - The type model of a wrapped COM AE server
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsD.3.7 Browse mappingleaves. The A&E COM UA Proxy relies on the "HasNotifier" Reference to assemble a hierarchy of branches/areas such that each Object Node which contains a HasNotifier ... EventNotifier Attribute is set to SubscribeToEvents is considered an area. The root for the HasNotifier hierarchy is the Server Object . Starting at the Server Object , HasNotifier Reference s are followed
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsF.1 Overviewillustration. The current state from the StateMachine is applied to all items in the HasNotifier hierarchy below the object with which the StateMachine is associated. The SystemState StateMachine