The FileSystemLoadingTypeenables software update based on an open file system. This enables the FileSystem based Loadingoption of 8.3.4.5.
It is illustrated in Figure 45and formally defined in Table 72.
Figure 45– FileSystemLoadingType
Table 72– FileSystemLoadingType definition
|
Attribute |
Value |
||||
|
BrowseName |
FileSystemLoadingType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Subtype of the SoftwareLoadingType |
|||||
|
HasComponent |
Object |
0:FileSystem |
|
0:FileDirectoryType |
Mandatory |
|
HasComponent |
Method |
GetUpdateBehavior |
|
|
Mandatory |
|
HasComponent |
Method |
ValidateFiles |
|
|
Optional |
|
Conformance Units |
|||||
|
DI SU FileSystem Loading |
|||||
The FileSystem Objectis of type FileDirectoryTypeas 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 Clienthowever the device may restrict this for specific folders or files.
This Methodmay be used to check the specific update behavior for a set of files. The files are identified by the NodeIdof their FileTypeinstance in the FileSystem.
Signature
GetUpdateBehavior(
[in] NodeId[] NodeIds,
[out]UpdateBehaviorUpdateBehavior);
|
Argument |
Description |
|
NodeIds |
NodeIds of the files to install. |
|
UpdateBehavior |
Method Result Codes (defined in Call Service)
|
Result Code |
Description |
|
Bad_NotFound |
If one or more NodeIdsare not found. |
This Methodmay 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-Loadingor Cached-Loadingthese 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]ErrorCodeInt32,
[out]ErrorMessageLocalizedText);
|
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 NodeIdsare not found. |