Search

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

16 result(s) for Cached-Loading

OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.1.12 Cached-Loading

Cached-Loading update method where the new software is stored in a separate area Note 1 to entry: Installation is performed later as an extra step
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.3 Types of Devices

firmware in a separate memory without installing it which is referred as Cached-Loading in this specification (see 8.3.4.4 ). In this case the installation is separated from the file transfer
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.1 Overview

section describes valid combinations of options). This way the Server can choose between Direct-Loading , Cached-Loading or FileSystem based Loading and it can use additional optional features like manual
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.3 Direct-Loading option

model where the installation is part of the transfer. To support the Direct-Loading model the Server has to provide the Current Version . This includes parameters like the version number ... integrity of the complete Software Package before the installation. If this is required, Cached-Loading is a better alternative. For Direct-Loading the DirectLoadingType is used, which is described
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.4 Cached-Loading option

Cached-Loading option The Cached-Loading option provides a model where the transfer of the Software Package and its installation are separate steps. To support the Cached-Loading model ... preferred option for best interoperability between Software Update Clients and Devices . For Cached-Loading the CachedLoadingType is used, which is described
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.5 FileSystem option

FileSystem option The Cached-Loading option with a self-contained Software Package and concrete definition of the version information can be too restrictive for some devices. E.g., if new software ... more specific use. If the additional flexibility of FileSystem based Loading is not required, Cached-Loading should be preferred. The purpose of the directories and files is not part
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.6 Installation option

Installation option Using the Cached-Loading option or the FileSystem option, a transferred Software Package or file is installed explicitly (compared to the implicit installation of Direct-Loading ). Therefore ... used (see 8.4.9 ). It can either be used to install a Software Package ( Cached-Loading ) or a list of files from the FileSystem (File System based Loading
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.4.10 Power cycle option

installation. This power cycle state machine is used in combination with the installation. For Cached-Loading it can be used in the Installing state of the InstallationStateMachineType . For Direct-Loading
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.3.5 Software Update Client

Different flows of Direct-Loading , Cached-Loading and FileSystem based Loading The prepare activity can be handled equal for all types of loading. This optionally includes a backup ... Installation activity for Direct-Loading For Cached-Loading and File System based Loading the installation is done using the InstallationStateMachineType . For Cached-Loading the InstallSoftwarePackage Method is used
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.5.1 Overview

supported). Additionally, it allows upload and download of different versions of the software. The Cached-Loading option is described in 8.3.4.4 . The CachedLoadingType is illustrated in Figure 45 and formally
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.6.4 ValidateFiles Method

should also include dependency checks if appropriate. Note: In case of Direct-Loading or Cached-Loading these checks should be part of the transfer and this method shall
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.9.1 Overview

Overview The InstallationStateMachineType can be used if the device supports explicit installation ( Cached-Loading or File System based Loading ). This supports the installation option of 8.3.4.6 . It is illustrated
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.2 Folder structure

content of this folder is defined by the author of the Software Package . For Cached-Loading and Direct-Loading , this folder can contain a single file that shall be transferred
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

Name Value Description DeploymentItem 0 This file shall be deployed to the device. If Cached-Loading or Direct-Loading is used at most one file can be marked as DeploymentItem
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

B.3.1 Simple example using Cached-Loading

B.3.1 Simple example using Cached-Loading The software update model provides several options and variants for advanced use cases. The Update Client must be prepared for the option that ... describe all the optional parts that can be supported. This example uses the Cached-Loading option. If the memory is limited and the installation can be done during the transfer
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

B.3.4 Update sequence using Cached-Loading

B.3.4 Update sequence using Cached-Loading An example sequence of Cached-Loading is shown in Figure B.7 . If the Server does not implement the properties PrepareForUpdate , PowerCycle or Parameters ... installation itself is described in Figure 39 . Figure B.7 - Example sequence of Cached-Loading