Search

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

17 result(s) for Addin

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

3.1.1 AddIn

AddIn a widely applicable feature or feature-set represented by an ObjectType that will be applied using aggregation
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 ... AddIn model in that it is based on composition. An AddIn is applied to a Node by adding a Reference to the AddIn instance. There are no restrictions for AddIn
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

7.20 HasAddIn ReferenceType

subtype of the HasComponent ReferenceType . The semantic of this ReferenceType is to bind an AddIn to another Node that is the source of this Reference . The AddIn concept is described
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.3 ConfigureSerialization Method

Method to set the SerializationProperties of the parent SerializationEntity . The DI:LockingServicesType is an AddIn defined in OPC 10000-100 . This AddIn shall be added as instance with the instance
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

redundant nested Assets , one might fail without the parent Asset failing). SoftwareUpdate is an AddIn (see OPC 10000-100 ) that defines support for firmware or software updates. This optional AddIn ... firmware or software that can be upgraded or changed. For a definition of the AddIn concept, see OPC 10000-3 . The following definitions are associated with the IAssetRevisionType interface
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

FunctionalEntityType may be directly used in an existing ObjectType , either via the AddIn concept or the Interface concept defined in OPC 10000-3 . For an illustration of how this
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

defined in UA FX [for example, any of the FxAssetType interfaces - iVendorNameplateType , iTagNameplateType ]. An AddIn also allows the function to be placed as a separate object, which might be easier ... profile as included or omitted. Figure B.6 - Extending type with Addin
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.3.1 General

through TransferToDevice , TransferFromDevice together with FetchTransferResultData . These Methods are exposed by means of an AddIn instance of TransferServicesType described in 6.4.2 . Both offline and online are created and driven
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.4.1 Definition

Definition The "Online-offline data transfer" is based on the AddIn model specified in OPC 10000-3 . The transfer of information ( Parameters ) between offline nodes and the physical
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

7.1 Overview

Overview The following Locking feature is based on the AddIn model specified in OPC 10000-3 . Locking is the means to avoid concurrent modifications to an Object by restricting access
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.8 Update of individual parts of a software

firmware of devices and to the software of components. This is realized with the AddIn model ( 8.3.11 ). If a Software Package becomes very large and only parts
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.3.1 Finding devices that provide the SoftwareUpdate AddIn within a Server

Finding devices that provide the SoftwareUpdate AddIn within a Server If an OPC UA Server abstracts several devices that support the SoftwareUpdate AddIn , the Information Model shall provide a defined
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.11 AddIn model

AddIn model To support an individual software update for the devices of a Server AddressSpace the software update model is defined using the AddIn model as it is described ... Objects that support an Identification FunctionalGroup (see B.2 ) that implements IVendorNameplateType . For the AddIn instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.1.1 Overview

Overview The SoftwareUpdateType defines an AddIn which can be used to extend Objects with software update features. All software update options are exposed as references of this AddIn . This ... Client can check for the references of the AddIn to determine which options are provided by a Server . If an option is available, it shall be used as specified
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.1.14 DefaultInstanceBrowseName

DefaultInstanceBrowseName The DefaultInstanceBrowseName Property - defined in OPC 10000-3 - is required for the AddIn model as specified in 8.3.11 . It is used to specify the BrowseName of the instance
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.2 Version Information

This is used for updating software via the OPC UA interface, using the SoftwareUpdate AddIn . In case the Server supports the AddIn for the asset, the SoftwareVersionType shall be used ... provide the patch information. In case, the Server does not support the AddIn for the asset, the Property 2: PatchIdentifiers should be provided on the same level as SoftwareRevision with
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.5.1 Overview

provide links to digital records, the ObjectType DocumentationLinksType is introduced, which is deployed as AddIn on Objects representing assets. The AddIn serves as entry point to Variables linking to digital ... documents like operator's handbooks. In Figure 6 , an example of using the DocumentationLinks AddIn is given. Figure 6 - Example of the DocumentationLinks AddIn Instead of providing the optional Methods