Diagnostic codes
The hexadecimal diagnostic codes listed here are output as WORD data type at the DiagCode output of the function block.
Code (hex) | Description | Options 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 file has been deleted, the Done output shows SAFETRUE. | The next delete command can be applied. |
8002 | The function block is in Prepare state. The values at the inputs are checked for plausibility. | Temporary state. No action required. |
8004 | The FB waits for the answer of the Safety PLC whether the firmware is ready to delete the file. | Temporary state. No action required. |
8005 | The FB waits for the answer of the Safety PLC after requesting the deletion of the specified recipe file (in state 8008). | Temporary state. No action required. |
8006 | The firmware of the Safety PLC has confirmed that it is ready to delete the file. The FB now waits for the delete command at the FB input CommandDelete. | Switch the CommandDelete input to SAFETRUE to start the deletion of the file. |
8008 | Once the CommandDelete input has been switched to SAFETRUE, the FB sends a request to the Safety PLC for deleting the file specified at the IDRecipeFile input. | Temporary state. No action required. |
C010 | The 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). |
C040 | The 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 file). Possibly there is a simultaneous access to the file by another recipe function block instance. |
|
C050 | After switching the CommandDelete to SAFETRUE, the firmware of the Safety PLC denied the request to delete the recipe file. The reason is that there is a simultaneous access to the file by another recipe function block instance. |
|
C150 | After switching the CommandDelete to SAFETRUE, the firmware of the Safety PLC denied the request to delete the recipe file. Reason: The file cannot be accessed in the flash memory. Possibly, the storage medium is write-protected, has been removed or is defective. |
|
C0A0 | The recipe file to be deleted does not exist in the flash memory file system. | Make sure that no files are deleted in your safety application unexpectedly or mistakenly. |