8 Software update model ToC Previous Next

8.4 ObjectTypes ToC Previous Next

8.4.6 FileSystemLoadingType ToC Previous Next

8.4.6.1 Overview ToC Model

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 45 and formally defined in Table 72.

readme_files/image047.png Figure 45 – FileSystemLoadingType

Table 72 – FileSystemLoadingType definition

Attribute Value
BrowseName FileSystemLoadingType
IsAbstract False

Subtype of the SoftwareLoadingType

References NodeClass BrowseName DataType TypeDefinition ModellingRule
HasComponent Object 0:FileSystem   0:FileDirectoryType Mandatory
HasComponent Method GetUpdateBehavior     Mandatory
HasComponent Method ValidateFiles     Optional
Conformance Units          
DI SU FileSystem Loading          

8.4.6.2 FileSystem ToC

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

8.4.6.3 GetUpdateBehavior Method ToC

This Method may 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] NodeId[]		NodeIds
[out]UpdateBehavior	UpdateBehavior);
Argument Description
NodeIds NodeIds of the files to install.
UpdateBehavior Update behavior OptionSet for the files specified by NodeId

Method Result Codes (defined in Call Service)

Result Code Description
Bad_NotFound If one or more NodeIds are not found.

8.4.6.4 ValidateFiles Method ToC

This Method may 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] NodeId[]	NodeIds
[out]ErrorCode	Int32
[out]ErrorMessage	LocalizedText);
Argument Description
NodeIds NodeIds of the files to validate.
ErrorCode 0 for success or device specific number for validation issues.
ErrorMessage Message for the user that describes how to resolve the issue.

Method Result Codes (defined in Call Service)

Result Code Description
Bad_NotFound If one or more NodeIds are not found.

Previous Next