Error Messages¶
Note
If a function block returns an “invalid” (i.e. internal) error code which is not listed here, check for a possible version mismatch between PLC firmware and the CAA File Libraries. If the function block is supported definitely by the firmware version in the PLC, the IEC application might have too many active function blocks in parallel (maximum number is 20).
Function Blocks of CAA_File.lib can return the following error codes:
Value | Error Name | Description |
---|---|---|
0 | FILE_NO_ERROR | No error |
5101 | FILE_TIME_OUT | Time limit exceeded |
5102 | FILE_ABORT | Order has been aborted by activating input xAbort |
5103 | FILE_HANDLE_INVALID | Invalid handle |
5104 | FILE_NOT_EXIST | Directory or file does not exist |
5105 | FILE_EXIST | Directory or file already exists |
5106 | FILE_NO_MORE_ENTRIES | No further entries are available |
5107 | FILE_NOT_EMPTY | File or directory is not empty |
5108 | FILE_READ_ONLY_CAA | Drive, file or directory is write-protected |
5109 | FILE_WRONG_PARAMETER | Wrong parameter(s) at Function Block |
5110 | FILE_ERROR_UNKNOWN | Unknown error |
5111 | FILE_WRITE_INCOMPLETE | Not all data has been written |
5112 | FILE_NOT_IMPLEMENTED | Function not supported |
5113 | FILE_NO_RESSOURCES | No file handles or user tasks available (too many files open or tasks accessing file system) |
5114 | FILE_NO_SPACE | Volume is full |
5115 | FILE_NO_DEVICE | Cannot open disk or no valid disk present |
5151 | FILE_CANT_BE_OPENED | File/directory could not be accessed to execute operation |
5152 | FILE_ERROR_OTHER | Internal or not further specified error |
5153 | FILE_SOURCE_CANT_BE_OPENED | Source file could not be opened to execute required operation |
5154 | FILE_DEST_CANT_BE_OPENED | Destination file could not be opened to execute required operation |
5155 | FILE_CANT_WRITE | Data could not be written to destination file |
5156 | FILE_CANT_READ | Data could not be read from source file |
5157 | FILE_CONFIRM_FORMAT_OPERATION | Formatting operation has not been confirmed at xEnable before activating the Function Block with xExecute. |