Search
9 result(s) for FileSystem
-
OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer4.1 Overviewfile system is represented by an instance of the FileDirectoryType with the BrowseName FileSystem . All directories below the root directory are represented by instances of the FileDirectoryType or a subtype
-
OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer4.3.2 FileSystem ObjectFileSystem Object The support of file directory structures is declared by aggregating an instance of the FileDirectoryType with the BrowseName FileSystem as illustrated in Figure 1 . Figure 1 - FileSystem example ... Object representing the root of a file directory structure shall have the BrowseName FileSystem . An OPC UA Server may have different FileSystem Objects in the AddressSpace . HasComponent is used
-
OPC-10000-100 – OPC Unified Architecture - Part 100: DevicesServer , the installation can be started for the set of files. Here the FileSystem option ( 8.3.4.5 ) can be used
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.5 FileSystem optionFileSystem option The Cached-Loading option with a self-contained Software Package and concrete definition of the version information can be too restrictive for some devices. E.g., if new software ... should be installed. For this use case the FileSystem based Loading provides an open structure of files and directories where a Client can read and write. These files could
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.4.6 Installation optionInstallation option Using the Cached-Loading option or the FileSystem option, a transferred Software Package or file is installed explicitly (compared to the implicit installation of Direct-Loading ). Therefore ... install a Software Package ( Cached-Loading ) or a list of files from the FileSystem (File System based Loading
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.5 Software Update ClientPendingVersion Objects to determine if the Software Package is already transferred. With the FileSystem based Loading the Client can browse the FileSystem to find out which files are already transferred ... illustrated in Figure 36 . 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
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.6.2 FileSystemFileSystem The FileSystem Object is of type FileDirectoryType as it is defined in OPC 10000-5 . It provides access to a hierarchy of directories and files of the device
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.6.3 GetUpdateBehavior Methodfiles. The files are identified by the NodeId of their FileType instance in the FileSystem . Signature GetUpdateBehavior( [in] 0:NodeId[] NodeIds, [out] UpdateBehavior UpdateBehavior); Table 86 - GetUpdateBehavior Method Arguments Argument ... HasProperty Variable 0:OutputArguments 0:Argument[] 0:PropertyType M Conformance Units DI SU FileSystem Loading
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.4.9.5 InstallFiles Methodfiles. The files are identified by the NodeId of their FileType instance in the FileSystem . If the installation succeeds but the software cannot run properly this should not be treated