8.4.6 FileSystemLoadingType

8.4.6.1 Overview

The FileSystemLoadingType enables software update based on an open file system. This enables the FileSystem based Loading option of 8.3.4.5.

It is illustrated in Figure 46 and formally defined in Table 85.

Figure 46 – FileSystemLoadingType
Table 85 – FileSystemLoadingType definition
Attribute Value
BrowseName1:FileSystemLoadingType
IsAbstractFalse
References NodeClass BrowseName DataType TypeDefinition Other
Subtype of the SoftwareLoadingType
0:HasComponentObject0:FileSystem0:FileDirectoryTypeM
0:HasComponentMethod1:GetUpdateBehaviorM
0:HasComponentMethod1:ValidateFilesO
Conformance Units
DI SU FileSystem Loading
8.4.6.2 FileSystem

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. The structure can be read and written by the Client however the device can restrict this for specific folders or files.

8.4.6.3 GetUpdateBehavior Method

This Method can be used to check the specific update behavior for a set of files. 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 Description
NodeIdsNodeIds of the files to install.
UpdateBehaviorUpdate behavior OptionSet for the files specified by NodeId

Method Result Codes (defined in Call Service)

Result Code Description
Bad_NotFoundIf one or more NodeIds are not found.
Table 87 – GetUpdateBehavior Method AddressSpace definition
Attribute Value
BrowseName1:GetUpdateBehavior
References NodeClass BrowseName DataType TypeDefinition Other
0:HasPropertyVariable0:InputArguments0:Argument[] 0:PropertyTypeM
0:HasPropertyVariable0:OutputArguments0:Argument[] 0:PropertyTypeM
Conformance Units
DI SU FileSystem Loading
8.4.6.4 ValidateFiles Method

This Method can be used to check if the specified set of files are valid and complete for an installation. This should also include dependency checks if appropriate.

Note: In case of Direct-Loading or Cached-Loading these checks should be part of the transfer and this method shall not be supported since it is part of the file transfer (e.g., in CloseAndCommit).

Signature

	ValidateFiles(
	  [in] 0:NodeId[]		NodeIds,
	  [out] 0:Int32		ErrorCode,
	  [out] 0:LocalizedText	ErrorMessage);
Table 88 – ValidateFiles Method Arguments
Argument Description
NodeIdsNodeIds of the files to validate.
ErrorCode0 for success or device specific number for validation issues.
ErrorMessageMessage for the user that describes how to resolve the issue.

Method Result Codes (defined in Call Service)

Result Code Description
Bad_NotFoundIf one or more NodeIds are not found.
Table 89 – ValidateFiles Method AddressSpace definition
Attribute Value
BrowseName1:ValidateFiles
References NodeClass BrowseName DataType TypeDefinition Other
0:HasPropertyVariable0:InputArguments0:Argument[] 0:PropertyTypeM
0:HasPropertyVariable0:OutputArguments0:Argument[] 0:PropertyTypeM
Conformance Units
DI SU FileSystem Loading