Search

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

16 result(s) for AddIns

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

4.10.1 Overview

object which provides several functions instead of over-using inheritance [GH95] , [FF04] . Interfaces and AddIns complement the type model and can be used when subtyping is not suitable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.10.3 AddIn model

AddIn model AddIns associate a feature or feature-set, represented by an ObjectType to the Node (an Object or ObjectType ) they are applied to. The Interface model is different than ... There are no restrictions for AddIn ObjectTypes and there is no special supertype for AddIns . To identify instances as an AddIn , the HasAddIn Reference or a subtype shall be used
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.20 HasAddIn ReferenceType

ObjectType . The TargetNode shall be an Object . One SourceNode can refer to multiple AddIns
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.1 Overview

several ways: by a simple mapping, by using Interfaces (see B.3.2 ), by using AddIns (see B.3.3 ). Defining a parallel OPC UA FX model and linking it to an existing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.1 Overview

part of its model. These additions could be accomplished using Interfaces or via AddIns ; examples of both are provided. Figure B.2 illustrates the original model defined in the example specification
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.3.1 General

B.3.3.1 General Figure B.5 illustrates the base model used for illustrating AddIns . This base model is similar to the base model for Interface, but it has removed the iVendorNameplateType . Figure ... Base Information Model for examples AddIns are used to attach OPC UA FX Information Model -specific content to an existing OPC UA Information Model . This is possible on the type
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

B.3.3.2 Extending an existing OPC UA model using AddIns Extending the type definition with AddIns is done by adding the Reference HasAddIn to the FunctionalEntityType and FxAssetType . During instantiation, this
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.3 Update of underlying Devices (e.g., IO Link Devices)

just connected to the device hosting the Server . This can be done using the AddIns described
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.3.1 Finding devices that provide the SoftwareUpdate AddIn within a Server

described in the DI specification. This folder could reference all SoftwareUpdate AddIns
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

C.5 Guidelines on how to use functionality in companion specifications

reuse other aspects of this specification, defined in the Interfaces in 4.5 or the AddIns "Locking" in 7 or software update in 8 , the companion specification ... this specification. Instead of, it can just implement the Interfaces or use the AddIns in their ObjectTypes and build an ObjectType -Hierarchy independent of this specification. In Figure
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

5.1 General information about Relative Spatial Location

described in 7.2 ) which must be subtyped to use with the Relative Spatial Location AddIns . This specification describes Relative Spatial Location AddIns (described in 6.1 and 6.2 ), which ... need a relative spatial location description for the objects of interest, can use these AddIns in a standardized way. For a concrete description of a frame, which can be used
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

5.3 Overview of subtypes of BaseDataVariableType

based. A subtype of SpatialLocationType is needed to use the Relative Spatial Location AddIns. The CartesianFrameAngleOrientationType, described in 7.3 , provides a discrete description of a frame, with a position defined ... ConformanceUnits of the RSL concept. Figure 3 shows an overview of Relative Spatial Location AddIns by using the CartesianFrameAngleOrientationType as a subtype of the SpatialLocationType and which ConformanceUnits are defined
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

6.3 Organization of Building Blocks

Organization of Building Blocks The building blocks defined in this specification are typically AddIns that can be applied to Objects or ObjectTypes representing Machines or components of Machines . The specification ... open how the information for the MachineryItem is further structured in addition to the AddIns . This allows a domain-specific organization of the MachineryItem , for example defined in a domain
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

16.1 Overview

levels of this building block. The Status Object shall reference the MachineryItemState and MachineryOperationMode AddIns , if they are provided by the MachineryItem . The Health of the MachineryItem may be represented
OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems

7.2 Identification and MachineryBuildingBlocks

this version of OPC 40082-4, the Object uses the two AddIns MachineryItemState and MachineryOperationMode . Table 2 - DosingSystemType Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Other 2:Identification
OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitions

6.3 Identification and MachineryBuildingBlocks

this version of OPC 40084-1, the Object uses the two AddIns MachineryItemState and MachineryOperationMode , where for the first a sub-state machine with substates for Executing is added. Table