Search
15 result(s) for Direct-Loading
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.1.11 Direct-LoadingDirect-Loading update method where the original software is overwritten during the transfer
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.3 Types of Devicesfirmware while it is transferred to the device. In this specification this is called Direct-Loading (see 8.3.4.3 ). Devices with more memory can store a new firmware in a separate
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.1 OverviewProfiles 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
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.3 Direct-Loading optionDirect-Loading option The Direct-Loading option provides a model where the installation is part of the transfer. To support the Direct-Loading model the Server has to provide ... 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: Devices8.3.4.6 Installation optiontransferred Software Package or file is installed explicitly (compared to the implicit installation of Direct-Loading ). Therefore, the InstallationStateMachineType shall be used (see 8.4.9 ). It can either be used
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.10 Power cycle optionCached-Loading it can be used in the Installing state of the InstallationStateMachineType . For Direct-Loading it can be used during the transfer of the new software with the TemporaryFileTransferType
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.5 Software Update Clientinformation about the new software). For Direct-Loading and Cached-Loading the validation is done during the transfer. For File System based Loading this shall be done before the installation ... Figure 36 - 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
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.4.1 OverviewServer . Transfer of the Software Package to the Server also includes the installation. The Direct-Loading option is described in 8.3.4.3 . The DirectLoadingType is illustrated in Figure 44 and formally
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.4.3 UpdateBehaviorinforms the update Client about the specific behavior of the component during update via Direct-Loading
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.6.4 ValidateFiles Methodinstallation. This 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: Devices8.7.2 Folder structurefolder 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 to the device
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.3 Package metadataDeploymentItem 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 . If File System
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesinstallation can be done during the transfer of the Software Package , the Direct-Loading model is another simple option. First the client determines what version is currently installed by reading
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicestechnical preconditions for the update. E.g., if the device uses Direct-, Cached- or File System based Loading (using the Loading Object ). Prepare installation The user selects the software ... software and firmware updates to the PLCs, the robots and the switch, except for Direct-Loading (using CachedLoadingType, FileSystem) . Schedule installation ( Client only) Determine how the update can be executed
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesB.3.3 Update sequence using Direct-Loading An example sequence of Direct-Loading is shown in Figure B.6 . If the Server does not implement the properties PrepareForUpdate , PowerCycle or Parameters ... installation itself is described in Figure 38 . Figure B.6 - Example sequence of Direct-Loading