Search
13 result(s) for CurrentVersion
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.1.16 Current VersionCurrent Version version information of the software that is currently installed
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.8.5.2 CloseAndUpdateversion of the configuration that the Client believes it is updating. If the CurrentVersion is not the same a Bad_InvalidState error is returned. Targets The list of targets ... does not have the rights required. Bad_InvalidState The VersionToUpdate does not match the CurrentVersion . Bad_ChangesPending Changes are queued on another Session (see 7.10.9 ) Bad_SecurityModeInsufficient The SecureChannel
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesSelecting the correct version to install An update client selects the correct version of the Software Package to install. The rules behind this decision can be complex and can include ... machine. The Server can expose information about the device ( 8.3.11 ) and information about the Current Version ( 8.4.3.2 ) which is then used by the Client to select an update. Selecting
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.3 Direct-Loading optiontransfer. To support the Direct-Loading model the Server has to provide the Current Version . This includes parameters like the version number, a release date or patch identifiers. With this
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.4 Cached-Loading optionseparate steps. To support the Cached-Loading model the Server has to provide the Current Version and the Pending Version . Optionally the Fallback Version can be supported. With the Current
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.5 Software Update Clientdifferent loading types are slightly different. With Cached-Loading the Client can check CurrentVersion and PendingVersion Objects to determine if the Software Package is already transferred. With the FileSystem based
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.11 AddIn modelcomponent. Note that the Properties SoftwareRevision, Manufacturer and ManufacturerUri also appears in the CurrentVersion of the PackageLoadingType . Their values can be different, if the manufacturer of the Device
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.3.1 OverviewOverview The PackageLoadingType provides information about the Current Version and allows transfer of a Software Package to and from the Server . The PackageLoadingType is illustrated in Figure 43 and formally
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.3.2 CurrentVersionCurrentVersion To identify the Current Version , the CurrentVersion Object provides ManufacturerUri , SoftwareRevision and PatchIdentifiers along with other information that allows the user to identify the currently used software. With this
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.4.1 OverviewOverview The DirectLoadingType provides information about the Current Version and allows transfer of a Software Package to and from the Server . Transfer of the Software Package to the Server also
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.5.1 OverviewOverview The CachedLoadingType provides information about the Current Version , the Pending Version and the Fallback Version (if supported). Additionally, it allows upload and download of different versions of the software
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.7.9 Clearsense to free memory. For configuration objects it can be possible to clear the Current Version . This Method supports the use case in 8.2.2.1 . Signature Clear(); Method Result Codes (defined
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesFirst the client determines what version is currently installed by reading the Properties of CurrentVersion of the Loading object. Then the client can transfer the Software Package to the device