To support an individual software update for the devices of a Server AddressSpacethe software update model is defined using the AddInmodel as it is described in OPC 10001-7. An instance of SoftwareUpdateTypeshall be attached to either Objectsthat implement the Interface IVendorNameplateType(see 4.5.2) or Objectsthat support an Identification FunctionalGroup(see B.2) that implements IVendorNameplateType. For the AddIninstance the fixed BrowseName“SoftwareUpdate” shall be used. This model gives any device, hardware- or software-component the opportunity to support SoftwareUpdate.

With this mechanism it is also possible to update parts of a software independently: A Servercould expose parts as additional software components with their own update AddIn.

To identify the device / component that is the target for the software update, the IVendorNameplateType Interfaceis used. In this Interfaceat least the Variables Manufacturer, ManufacturerUri, ProductCodeandSoftwareRevisionshall be supported and have valid values. Optionally Modeland HardwareRevisionshould be supported. TheseProperties may be shown to the operator. ManufacturerUri, ProductCodeand HardwareRevisionshould be used to identify the component.

Note that the Properties SoftwareRevision, Manufacturerand ManufacturerUrialso appears in the CurrentVersion ofthe PackageLoadingType. Their values may be different, if the manufacturer of the Deviceis not the same as the manufacturer of the software. The SoftwareRevision Object shall be the same at both places.

The ComponentType(see 4.6) already implements the Interface IVendorNameplateType. This makes it a good candidate for a SoftwareUpdate AddInas illustrated in the example in Figure 40.

image043.png

Figure 40– Example how to add the SoftwareUpdate AddIn to a component