Search
6 result(s) for HasAddIn
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.10.3 AddIn modelthere is no special supertype for AddIns . To identify instances as an AddIn , the HasAddIn Reference or a subtype shall be used. The AddIn ObjectType shall include the definition ... applied to an instance Clients can detect the implementation of AddIns by passing the HasAddIn Reference as filter to the Browse Service request. If an AddIn has a default BrowseName
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelHasAddIn ReferenceType The HasAddIn ReferenceType is a concrete ReferenceType and can be used directly. It is a subtype of the HasComponent ReferenceType . The semantic of this ReferenceType is to bind
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelusing AddIns Extending the type definition with AddIns is done by adding the Reference HasAddIn to the FunctionalEntityType and FxAssetType . During instantiation, this leads to the creation
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesProperties and should have the BrowseName Lock . It shall be referenced using HasComponent or HasAddIn from the lock-owner Object (for example, a Device ). The LockingServicesType and each instance
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.1 Node definitionsalso selected. Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target of a HasSubtype Reference
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.1 Node definitionsalso selected. Dependencies exist if the Node is the source of HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target of a HasSubtype Reference