Search

12 result(s) for SoftwareUpdate AddIn

• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.2.4 UAFX FxAsset
  IDeviceHealthType and IAssetRevisionType . This includes supporting all required types. Server UAFX SoftwareUpdate Supports the SoftwareUpdate AddIn . Connectors Server UAFX AssetConnector Id Supports the Id Property of the AssetConnectorType. Server UAFX
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.4.4.2 UAFX Descriptor Contents - UAFX Information Model
  product supports the UAFX SoftwareUpdate ConformanceUnit , the AML descriptions of all instances of UAFX SoftwareUpdate AddIn are included. Offline UAFX Descriptor IAssetRevision Version If the product supports the UAFX IAssetRevision
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.14 Standard package format for transfer to the device
  Standard package format for transfer to the device The Software Update AddIn supports atomic transfer of a single file to the server. To keep the metadata together with the transferred
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.15 Standard package format for transfer from the device (prototype / backup)
  device should be able to create a Software Package and upload it using the SoftwareUpdate AddIn . This package can also be used for backup
• 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.3.5 Software Update Client
  task is to detect what options are supported by browsing the references of the SoftwareUpdate AddIn . Then the Client can check the version information to determine whether an update
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.11 AddIn model
  already implements the Interface IVendorNameplateType . This makes it a good candidate for a SoftwareUpdate AddIn as illustrated in the example in Figure 41 . Figure 41 - Example ... SoftwareUpdate AddIn to a component
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.1.7 Parameters
  supported by devices that cannot retain parameters during update. If supported by the SoftwareUpdate AddIn a Client can read the parameters before the update and restore them after the update
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.12 SoftwareFolderType
  items is server specific, but the items shall at least support the SoftwareUpdate AddIn . They are identified by SoftwareSubclass and SoftwareName which is provided with the Add Method . After adding ... item, the SoftwareUpdate AddIn is used to transfer the initial software. After that it can be used to install updates. The SoftwareUpdate AddIn of each item shall support SoftwareClass , SoftwareSubclass
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.12.1 Add Method
  item to the folder. The parameters Subclass and Name are exposed at the attached SoftwareUpdate AddIn as SoftwareSubclass and SoftwareName Properties . The Name shall be unique within the SoftwareFolderType . Signature
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.6.2 CanUpdate ReferenceType
  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
  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