Search
40 result(s) for Addin
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model3.1.1 AddInAddIn 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 Model4.10.3 AddIn modelAddIn 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 Modelsubtype 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 SerializationMethod 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 Model6.3.2 FxAssetType definitionredundant 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 ModelFunctionalEntityType 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 Modeldefined 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: Devices6.3.1 Generalthrough 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: Devices6.4.1 DefinitionDefinition 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: Devices7.1 OverviewOverview 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: Devicesfirmware 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: DevicesFinding 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: Devices8.3.11 AddIn modelAddIn 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: Devices8.4.1.1 OverviewOverview 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: Devices8.4.1.14 DefaultInstanceBrowseNameDefaultInstanceBrowseName 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 Basics10.2 Version InformationThis 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 Basics10.5.1 Overviewprovide 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
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocksblocks for various use cases in the context of machinery. The specification uses the AddIn concept defined in OPC 10000-3 , in order to allow companion specifications and vendors
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocksdefines a building block for Machine Identification and Nameplate (see section 8 ) defined as AddIn capabilities to find all Machines in a Server (see section 9 ) by defining a standardized ... point a building block for component Identification and Nameplate (see section 10 ) defined as AddIn a building block to find all identifiable components of a Machine (see section 11 ) defined
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building BlocksMachineryBuildingBlocks Object . In Figure 7 , an example is given. The SpecificComponentType supports the Identification AddIn as well as the BuildingBlock1 and BuildingBlock2. All three are referenced from the MachineryBuildingBlocks Object ... Identification AddIn is also referenced directly from the ObjectType , and the other AddIns from some domain-specific Objects to structure the component. The SpecificMachineType supports Identification and those two additional
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks8.1 OverviewObjectType MachineryItemIdentificationType are generic ObjectTypes introduced to be used in other use cases. The AddIn MachineIdentificationType with the default name "2:Identification" (as defined
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocksreferenced Objects as representations of Machines , each of those Objects shall provide the MachineIdentificationType AddIn using the 0:DefaultInstanceBrowseName as a direct sub-component of the Object (referenced with
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks10.1 Overviewspecific information for the identification of the component. Figure 11 gives an overview. The AddIn MachineryComponentIdentificationType with the default name "2:Identification" (as defined
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocksidentifiable components shall contain the Identification Object , <Component> references to that AddIn as defined in Table 27 . As a Machine can contain other Machines , it does not reference
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks12.1 OverviewMachineryItemState_StateMachineType is added to the Object MyMachine representing a Machine using the AddIn concept. The MachineryItemState_StateMachineType is defined in 12.2 . Figure 15 - Building Block for MachineryItemState In Figure
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blockssubtype of FiniteStateMachineType defined in OPC 10000-16 . The semantic of this AddIn is to provide the state of a MachineryItem . It is formally defined in Table 29 . Table
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks13.1 OverviewMachineryOperationModeStateMachineType is added to the Object MyMachine representing a Machine using the AddIn concept. The MachineryOperationModeStateMachineType is defined in 13.2 . Figure 18 - Building Block for MachineryOperationMode In Figure
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blockssubtype of FiniteStateMachineType defined in OPC 10000-16 . The semantic of this AddIn is to provide the MachineryOperationMode of a MachineryItem . It is formally defined in Table 32 . Table
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building BlocksMachineryLifetimeCounterType The MachineryLifetimeCounterType serves as AddIn and provides an entry point to various lifetime variables. It is formally defined in Table 38 . Table 38 - MachineryLifetimeCounterType Definition Attribute Value BrowseName MachineryLifetimeCounterType ... lifetime variable. In situations, where there may be no lifetime variable available, the AddIn should be defined as optional on the TypeDefinition and should not be provided on the instance
-
OPC-40001-3 – OPC UA for Machinery - Part 3: Job Managementinto a MachineryItem . The building block, using its 0: DefaultInstanceBrowseName JobManagement , is added as AddIn into the 3: MachineryBuildingBlocks Object . In addition, it is referenced by some domain-specific organization
-
OPC-40001-3 – OPC UA for Machinery - Part 3: Job ManagementJobManagementType ObjectType Definition The JobManagementType provides an AddIn for job management and is formally defined in Table 4 . Table 4 - JobManagementType Definition Attribute Value BrowseName JobManagementType IsAbstract False References Node
-
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical IntegrationTaskControlOperationType ObjectType The TaskControlOperationType is an AddIn to extend instances of TaskControlType described in 7.21 . It provides the possibility to handle programs with designated task controls. The task controls
-
OPC-40200 – OPC UA for Weighing Technology7.1.3 ObjectType Descriptionfeeder. MinimalFeederSpeed defines the minimal possible speed of the feeder. The Identification - AddIn contains information about the identification and nameplate of a feeder. MachineryItemState is used as defined ... Shall also be referenced as AddIn in the MachineryBuildingBlocks Folder MachineryOperationMode is used as defined in OPC 40001-1 . Shall also be referenced as AddIn in the MachineryBuildingBlocks Folder MachineryBuildingBlocks
-
OPC-40200 – OPC UA for Weighing Technology7.2.3 ObjectType Descriptionprint media in percent (e.g., ink, wear of thermal element, etc.). The Identification - AddIn contains information about the identification and nameplate of a printer. MachineryItemState is used as defined ... Shall also be referenced as AddIn in the MachineryBuildingBlocks Folder MachineryOperationMode is used as defined in OPC 40001-1 . Shall also be referenced as AddIn in the MachineryBuildingBlocks Folder MachineryBuildingBlocks
-
OPC-40200 – OPC UA for Weighing Technology7.3.3 ObjectType DescriptionObjectType Description The Identification - AddIn contains information about the identification and nameplate of a machine. A scale system can contain one or more scales. The scales must be a subtype ... MachineryItemState is used as defined in OPC 40001-1 . Shall also be referenced as AddIn in the MachineryBuildingBlocks Folder MachineryOperationMode is used as defined in OPC 40001-1 . Shall also
-
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job ManagementMachineryItemState is used as defined in OPC 40001-1 . Shall also be referenced as AddIn in the 3:MachineryBuildingBlocks folder. 3:MachineryOperationMode is used as defined ... Shall also be referenced as AddIn in the 3:MachineryBuildingBlocks folder. MaintenanceMode, as a SubStateMachine of the 3:MachineryOperationMode (see Table 29 ) , is only valid if the 0:CurrentState
-
OPC-40505 – OPC UA for Wireless Machine Tool Peripherals7.1.1 Overviewused as defined in OPC 40001-1 and shall also be referenced as AddIn in the MachineryBuildingBlocks Folder. BatteryLevel contains all data on the current battery level of the WMTP
-
OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systemswith the HasComponent reference under this Object . This Object shall also be referenced as AddIn in the MachineryBuildingBlocks Folder. ContactMaterial represents the type of material of the transport line which
-
OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinerycomplex jobs on the machine. All Machinery Building Blocks are also referenced as an Addin in the MachineryBuildingBlocks folder. Figure 6 - Shot Blasting Technology Information Model overview
-
OPC-40719 – OPC UA for Plasma Surface Technologycomplex jobs on the machine. All Machinery Building Blocks are also referenced as an Addin in the MachineryBuildingBlocks folder. Annex B contains two implementation examples of the described