-

Diagnostic codes

The hexadecimal diagnostic codes listed here are output as WORD data type at the DiagCode output of the function block.

Code (hex)DescriptionOptions for remedy
0000 The function block is not activated. The Activate input is FALSE.Activate the function block by switching Activate to TRUE.
8000 The function block has completed its operation successfully. The data set has been deleted, i.e., overwritten with 0-values. The Done output shows SAFETRUE.The next delete command can be applied.
8002The function block is in Prepare state. The following operations are done:
  • The values at the inputs are checked for plausibility.
  • Read permission to the recipe file (specified at the IDRecipeFile input) from the file system is requested at the Safety PLC.
Temporary state. No action required.
8004The FB waits until the recipe file (in which a data set is to be deleted) is read and ready in the RAM for the delete operation (i.e., for overwriting its values with 0s).Temporary state. No action required.
8005After deleting the data set (IDRecipeDataSet) in the specified file (IDRecipeFile), the FB waits for the confirmation of the Safety PLC that the file has been written to the file system in the flash memory of the standard controller.Temporary state. No action required.
8006The recipe data is loaded into the RAM of the Safety PLC and is ready to be overwritten. The FB now waits for the delete command at the FB input CommandDelete.Switch the CommandDelete input to SAFETRUE to start the operation.
8008Once the CommandDelete input has been switched to SAFETRUE, the FB sends a request to the Safety PLC for overwriting the values in the data set specified at the IDRecipeDataSet input with 0-values.Temporary state. No action required.
800CThe deleted data set is read from the RAM of the Safety PLC and validated: The CRC of the section must have the value 0. This way, the FB checks whether the data set has been overwritten in the same cycle by a SF_RecipeWrite instance meanwhile.Temporary state. No action required.
C010The file ID applied to the IDRecipeFile input is not within the valid value range. Apply a valid file ID to the IDRecipeFile input.
After applying a valid ID, the FB enters the Prepare state (8002).
C020The data set ID applied to the IDRecipeDataSet input is not within the valid value range.Apply a valid data set ID to the IDRecipeDataSet input.
After applying a valid ID, the FB enters the Prepare state (8002).
C030The request for reading the specified file (sent in state 8002, see above) has been denied by the Safety PLC.Retry to start the delete operation by applying a rising edge to the CommandDelete input.
After that, the FB enters the Prepare state (8002).
C040The firmware of the Safety PLC is not ready to accept the SAFETRUE value at the CommandDelete input (i.e., not ready to delete the recipe data set). Possibly there is a simultaneous access to the file by another recipe function block instance.
  • Make sure that the recipe file is not accessed in your safety application by another recipe function block instance while the delete operation is in progress.
  • Retry the delete command again at a later time.
    After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
C050An error occurred while deleting the data set from the RAM of the Safety PLC. The data available in the RAM is not up-to-date.Retry the delete command again at a later time.
After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
C150An error occurred while writing the file from the RAM into the flash memory file system of the standard controller.
Possibly, the storage medium is write-protected, has been removed or is defective.
  • Retry the delete command again at a later time.
    After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
  • Verify that the flash memory is installed correctly in the standard controller and is neither defective nor write-protected.
C250An error occurred while reading the newly overwritten data set from the file system in the flash memory of the standard controller for verification purposes. Without successful verification, the process cannot be completed. Possibly, the data have been modified or deleted in the meantime by another FB.Make sure that accesses to the same recipe file (data set) are not colliding in your safety application.

Retry the delete command again at a later time.
After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
C070A validation error occurred. The newly overwritten data set could not be validated due to the following reason: After deleting the data set, it must contain only 0-values. The validation detects that the data set CRC is not null. This means, that the data set has been overwritten in the same Safety PLC cycle by aSF_RecipeWrite instance.
  • Make sure that only one FB instance is writing the file/data set at the same time.
  • Retry the delete command.
    After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
C0A0The file in which a data set is to be deleted does not exist in the file system.Make sure that no files are deleted in your safety application unexpectedly or mistakenly.
C0B0An error occurred while saving or deleting the modified file. The newly written data set could not be validated as it contains different values than 0s.Retry the delete command again at a later time.
After applying a rising edge at CommandDelete, the FB enters the Prepare state (8002).
C0C0The data set to be deleted is empty. For example, it has already been deleted by another instance of the SF_RecipeDeleteDataSet FB.Make sure that no data sets are deleted in your safety application unexpectedly or mistakenly.