Search

10 result(s) for Update Client

• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.13 Pack software for distribution
  Pack software for distribution An Update Client imports a software along with all metadata and all supporting files. These files can come from different vendors for different devices. For easier
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.16 Select Software Packages for the SoftwareUpdate AddIn on the device
  Select Software Packages for the SoftwareUpdate AddIn on the device An Update Client identifies Software Packages that are installable to a SoftwareUpdate AddIn found on the server. For example, getting
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.17 Check package compatibility before transfer
  Check package compatibility before transfer An Update Client checks the compatibility before transfer anything to a device. This includes selecting the proper version as a valid update
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.18 Validate dependencies to hardware, firmware, other software
  Validate dependencies to hardware, firmware, other software An Update Client ensures that all dependent hardware / firmware / software components have suitable versions
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.19 Support supplementary files in a Software Package
  Support supplementary files in a Software Package An Update Client presents additional files to the user. This can include release notes, license information, manuals
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.20 Prove integrity and authenticity of a Software Package
  Prove integrity and authenticity of a Software Package An Update Client verifies the integrity and authenticity of the files within the Software Package
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.7.2 Folder structure
  case 8.2.2.16 ). The optional SUPPLEMENT folder can contain supplementary documents for use by the Update Client . These can include license details, release notes, or manuals related to the software ... Update Client can present them to the user as part of the software update (see use case 8.2.2.19 ). The optional META-INF folder contains the digital signatures of the Software
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.7.4 Package signature
  case 8.2.2.20 ). The verification of these signatures can be done by the Update Client or by the device if the whole update package is deployed. Typically, a PKI with ... Software Package for use in a specific plant. With this in place the Update Client and OPC UA servers can be configured to only allow updates of Software Packages with
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.7.5 Solution packages
  single node. If the distribution of the packages is done by the Update Client and the package shall be installed on a specific server, the TargetServer contains the ApplicationUri
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.3.1 Simple example using Cached-Loading
  software update model provides several options and variants for advanced use cases. The Update Client must be prepared for the option that the server provides ... user can be determined subscribing the UpdateStatus property. To verify if the update was success the client verifies that Loading.CurrentVersion now describes the desired updated version. Figure B.4 - Example