Search

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

34 result(s) for HasAddIn

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.3 AddIn model

there 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 Model

7.20 HasAddIn ReferenceType

HasAddIn 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 Model

B.3.3.2 Extending an existing OPC UA model using AddIns

using 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: Devices

7.3 LockingServices Object

Properties 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 Mapping

3.3.1.1 Node definitions

also 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 Positioning

3.4.1.1 Node definitions

also 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-30081 – OPC UA for Process Automation Devices - PA-DIM™

3.4.1.1 Node definitions

also 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-30141 – OPC UA for PROFIenergy

7 PROFIenergy Service Access Point Information Model

Entity . The connection with the PROFINET submodule is provided with a HasAddin Reference . One device can have more than one service access points thus containing more than one PE Entity
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

3.5.1.1 Node definitions

also 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-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

3.4.1.1 Node definitions

also 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-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

3.5.1.1 Node definitions

also 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-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

3.4.1.1 Node definitions

also selected. Dependencies exist if the Node is the source of a HasTypeDefinition , HasInterface , HasAddIn or any HierarchicalReference . Dependencies also exist if the Node is the target of a HasSubtype
OPC-34100 – OPC UA for Energy Consumption Management

3.4.1.1 Node definitions

also 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-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

3.4.1.1 Node Definitions

also 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-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

6.3 Organization of Building Blocks

this specification should be applied to this Object , i.e. being referenced with a HasAddIn Reference or a subtype from this Object . Because of the base characteristics of the identification
OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System

3.4.1.1 Node definitions

also 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-40301 – OPC UA for Flat Glass Processing

3.5.1.1 Node definitions

also 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-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management

C.1 Modular enhancement of existing type model

PtAssetType or a sub-type, e.g. PtAssetMotorType . For this the references HasInterface or HasAddIn are used in general. To reference specific InstanceDeclarations of asset attributes the HasPtAttributes reference
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management

C.3 Enhancement with whole asset type

instance of the PtAssetType or a sub-type e.g. PtAssetMotorType is attached with a HasAddIn reference. As in the previous use cases, the DefaultBrowsename of the PtAssetType definitions is also
OPC-40444 – OPC UA for Textile Testing Devices

3.4.1.1 Node definitions

also 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-40450-1 – OPC UA for Joining Systems - Part 1: Base

3.4.1.1 Node definitions

also 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-40503-1 – OPC UA for Metal Forming - Part 1: General

3.4.1.1 Node definitions

also 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-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing

3.4.1.1 Node definitions

also 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-40505 – OPC UA for Wireless Machine Tool Peripherals

3.4.1.1 Node definitions

also 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-40505 – OPC UA for Wireless Machine Tool Peripherals

7.1.1 Overview

HasComponent Object WMTPWorkCycleData WMTPWorkCycleDataType O 0:HasComponent Object WMTPServiceCycleData WMTPServiceCycleDataType O 0:HasAddIn Object 3:LifetimeCounters 3:MachineryLifetimeCounterType O 0:HasAddIn Object 3:OperationCounters 3:MachineryOperationCounterType O 0:HasComponent Object ... with the HasComponent reference under this Object. This Object shall also be referenced as HasAddIn in the MachineryBuildingBlocks Folder. MachineryOperationCounters is representing a collection of all incrementing counters
OPC-40530 – OPC UA for Laser Systems

3.4.1.1 Node definitions

also 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-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface

3.4.1.1 Node definitions

also 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-40560 – OPC UA for Mining - General

3.2.1.1 Node definitions

also 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-40570 – OPC UA for Wire Harness Manufacturing

3.4.1.1 Node definitions

also 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-40700 – OPC UA for Surface Technology - General Types

3.3.1.1 Node definitions

also 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-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems

3.3.1.1 Node definitions

also 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-40718 – OPC UA for Surface Technology - Shot Blasting Machinery

3.4.1.1 Node definitions

also 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-40719 – OPC UA for Plasma Surface Technology

3.4.1.1 Node definitions

also 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-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)

3.4.1.1 Node definitions

also 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