Search

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

13 result(s) for SoftwareUpdate

OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

BaseDataVariableType O 0:HasComponent Object 5:DeviceHealthAlarms 0:FolderType O 0:HasAddIn Object 5:SoftwareUpdate 5:SoftwareUpdateType O ConformanceUnits UAFX FXAsset Type The components of the FxAssetType have additional subcomponents ... 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
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.1 Overview

Overview The software update model defined in this clause is used to manage the software of a Device . This can include the installation of new software, the update of existing ... these options are defined in the profiles section. 8.3.5 describes how to implement a Software Update Client that has to deal with several options. The types for this model
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.2.2.2 Update Devices from different manufacturers with a Software Update Client

Update Devices from different manufacturers with a Software Update Client Allow devices to be updated via Software Update Client software. To address the domain specific constraints this ... domain e.g., a redundant device will be activated.) 8.3.5 describes the workflow of a Software Update Client
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 ... DeviceFeatures as it is described in the DI specification. This folder could reference all SoftwareUpdate AddIns
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.1 System perspective

System perspective Besides specific Clients for specific devices, this specification also describes Software Update Clients that can update devices of various vendors (for additional details see 8.3.5 ). For Devices ... often necessary to consider the operation state of the software / machine / plant before performing the update (e.g. stop and start the operation). For this case a specialized Client
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.1 Overview

several options where a vendor can select the parts that are necessary for the software update. All these options are exposed as optional References of the SoftwareUpdateType . A Server ... like manual power cycle, parameter backup / restore or confirmation. It is necessary that a Software Update Client checks which options are exposed by the Server and how the Server behaves
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.5 FileSystem option

standard way to expose the current version number(s) of the system. Therefore, a Software Update Client requires additional vendor-specific information, or other companion specifications must define a more ... specifications could add this definition for specific types of devices. If accessed by a Software Update Client, the FileSystem root can be used to store and install the files
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.11 AddIn model

FunctionalGroup (see B.2 ) that implements IVendorNameplateType . For the AddIn instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware- or software-component the opportunity ... support SoftwareUpdate . With this mechanism it is also possible to update parts of a software independently: A Server could expose parts as additional software components with their own update AddIn
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.6.2 CanUpdate ReferenceType

used directly. It is a subtype of HierarchicalReferences . For components with SoftwareUpdate that accept Solution Packages this reference type is used to describe which subcomponents can be updated ... Package (see 8.7.5 ). The source of this ReferenceType is a component that supports the SoftwareUpdate AddIn . The target of this ReferenceType is the component that can be updated. SourceNode
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

compatible. True Assignments[] 2:Assignment Assignments of Software Packages to components that support SoftwareUpdate Only for solution packages (see 8.7.5 ) True Table 121 - PackageMetadata definition Attribute Value BrowseName 2:PackageMetadata ... compatibility of a Software Package with a component on the server that supports the SoftwareUpdate AddIn . This can be simple terms like a minimum SoftwareRevision or a specific HardwareRevision
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

B.3.6.1 Update Sequence for Single Device - where solution package is created 'on the fly'

successful matched elements, the sub-packages are copied or linked to the SoftwareUpdate instances of each device into the PendingVersion. Server is returning the info which elements are ready
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

Agreement of Use

additional usage scenario for Abort Method 9546 Errata Missing HasCause References in StateMachines for SoftwareUpdate Missing references are added to all state machines 9547 Editorial Drawings for StateMachines of Software ... transitions then in the Model Additional transitions removed from the diagrams 10218 Editorial Missing SoftwareUpdate reference at ComponentType Added optional SoftwareUpdate reference to ComponentType . 10223 Feature Standardized folder
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.2 Version Information

SoftwareVersionType . 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