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 FB has been completed: the recipe data set has been read successfully. Before writing the data to its outputs PayloadRead** (with ** = 0 to 15), the FB verifies that the read data set is identical with the data validated in the previous state 800C.
If this validation is successful the value SAFETRUE is shown at output Done. The read values are applied to the PayloadRead** (with ** = 0 to 15) and can be further processed in the safety application.
If the data set is not identical with the data validated in the previous state 800C, Done remains SAFEFALSE. The failsafe values applied to the inputs PayloadRead** (with ** = 0 to 15) are output by the FB.

Done = SAFETRUE:
The next read command can be applied.

Done = SAFEFALSE:
Make sure that the recipe file is not overwritten in your safety application while the read operation is in progress.

8002 The 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) is requested at the Safety PLC.

Temporary state. No action required.

8004 The FB waits for the answer of the Safety PLC after requesting read access to the specified recipe file. Temporary state. No action required.

8006 The Safety PLC has allowed the read access to the recipe file. The FB now waits for the read command at the FB input CommandRead. Switch the CommandRead input to SAFETRUE to start the read access.

800C Reading the data from the addressed data set is in progress followed by the validation of the read data.
Details on the fault validation can be found in the chapter "Fault avoidance", section "Data validation". 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).

C020 The 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).

C030 The request for reading the file (sent in state 8002, see above) has been denied by the Safety PLC. Retry to start the read access by applying a rising edge to the CommandRead input.
After that, the FB enters the Prepare state (8002).

C040 Error while reading the recipe file. Either the flash memory of the standard controller cannot be accessed or the file is corrupted. Verify that the flash memory is installed correctly in the standard controller.

C050 An error occurred while reading the data set in RAM of the Safety PLC during the validation (i.e. previous state was 800C).
The file cannot be accessed in the RAM. Possibly there is a simultaneous access to the file/data set by another recipe function block instance.

Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress.

Retry the read command again at a later time.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C150 An error occurred while reading the data set in RAM of the Safety PLC when the previous state was 8000.
The file cannot be accessed in the RAM. Possibly there is another access to the file/data set by another by another recipe function block instance.

Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. (See topic "Preventing multiple and competing accesses to recipe files".)

Retry the read command again at a later time.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C060 An inconsistent data set checksum was detected during the validation of the data set (i.e. previous state was 800C):
The CRC calculated by the FB is not identical with the read CRC. Possibly, the data set has been falsified by a soft error. Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C070 An inconsistent data set checksum was detected during the validation of the data set (i.e. previous state was 800C):
The data set CRC calculated by the FB is not identical with the expected value applied to the DataSetCRC input of the FB. This means the data set has been overwritten in the meantime by a SF_RecipeWrite FB.

Make sure that the correct recipe file (version) is stored on the target controller.

Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started. (See topic "Preventing multiple and competing accesses to recipe files".)

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C080 An inconsistent file checksum was detected during the validation of the data set (i.e. previous state was 800C):
The file CRC calculated by the FB is not identical with the expected value applied to the FileCRC input of the FB. This means the file has been overwritten in the meantime by a SF_RecipeWrite FB.

Make sure that the correct recipe file (version) is stored on the target controller.

Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started. (See topic "Preventing multiple and competing accesses to recipe files".)

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C090 An inconsistent project checksum was detected during the validation of the data set (i.e. previous state was 800C):
The project CRC read from the recipe file is not identical with the project CRC of the current project.
Possibly, the project has been modified in the meantime or the recipe file is outdated.
Background information on the ProjectCRC comparison

The comparison of the project CRC helps ensuring that the recipe file to be read has been written out of exactly the same application project (version).

The project checksum has been calculated in PLCnext Engineer when building the project and was then written into the project file.
The SF_RecipeWrite FB reads this checksum from the project file and writes it into the header of the recipe file.
If the CheckProjectCRC input is set to SAFETRUE, the SF_RecipeRead FB reads the ProjectCRC from the recipe file header and compares it with the ProjectCRC of the current project.

Make sure that the correct recipe file (version) is stored on the target controller.

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C0C0 An inconsistent serial number was detected during the validation of the data set (i.e. previous state was 800C):
The serial number of the controller read from the recipe file is not identical with the serial number of the connected controller.
Possibly, the controller has been replaced in the meantime or the wrong controller is currently connected. Make sure that the correct target device is connected.

C160 An inconsistent data set checksum was detected when the previous state was 8000:
The CRC calculated by the FB is not identical with the read CRC. Possibly, the data set has been falsified by a soft error. Retry the read command again at a later time.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
If the error still exists, write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.

C170 An inconsistent data set checksum was detected when the previous state was 8000:
The data set CRC calculated by the FB is not identical with the expected value applied to the DataSetCRC input of the FB.
The data set has either been overwritten in the meantime by a SF_RecipeWrite FB or the data it contains has been corrupted.

Make sure that the correct recipe file (version) is stored on the target controller.

Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. (See topic "Preventing multiple and competing accesses to recipe files".)

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C180 An inconsistent file checksum was detected when the previous state was 8000:
The file CRC calculated by the FB is not identical with the expected value applied to the FileCRC input of the FB.
The file has either been overwritten in the meantime by a SF_RecipeWrite FB or the data it contains has been corrupted.

Make sure that the correct recipe file (version) is stored on the target controller.

Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress.

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C190 An inconsistent project checksum was detected when the previous state was 8000:
The project CRC read from the recipe file is not identical with the project CRC of the current project.
Possibly, the project has been modified in the meantime.
Background information on the ProjectCRC comparison

The comparison of the project CRC helps ensuring that the recipe file to be read has been written out of exactly the same application project (version).

The project checksum has been calculated in PLCnext Engineer when building the project and was then written into the project file.
The SF_RecipeWrite FB reads this checksum from the project file and writes it into the header of the recipe file.
If the CheckProjectCRC input is set to SAFETRUE, the SF_RecipeRead FB reads the ProjectCRC from the recipe file header and compares it with the ProjectCRC of the current project.

Make sure that the correct recipe file (version) is stored on the target controller.

Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress.

Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C1C0 An inconsistent serial number was detected when the previous state was 8000:
The serial number of the controller read from the recipe file is not identical with the serial number of the connected controller.
Possibly, the controller has been replaced in the meantime or the wrong controller is currently connected. Make sure that the correct target device is connected.

C0A0 To recipe file to be read does not exist in the file system of the standard controller. Create the recipe file using the SF_RecipeWrite FB and retry the read command again at a later time.
After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).

C0B0 A validation error occurred: During the validation in the state 8000, the FB detects that the read data set differs from the data set validated in state 800C, i.e., contains unexpected data. Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started.

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 FB has been completed: the recipe data set has been read successfully. Before writing the data to its outputs PayloadRead (with = 0 to 15), the FB verifies that the read data set is identical with the data validated in the previous state 800C. If this validation is successful the value SAFETRUE is shown at output Done. The read values are applied to the PayloadRead (with = 0 to 15) and can be further processed in the safety application. If the data set is not identical with the data validated in the previous state 800C, Done remains SAFEFALSE. The failsafe values applied to the inputs PayloadRead (with = 0 to 15) are output by the FB.	Done = SAFETRUE: The next read command can be applied. Done = SAFEFALSE: Make sure that the recipe file is not overwritten in your safety application while the read operation is in progress.
8002	The 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) is requested at the Safety PLC.	Temporary state. No action required.
8004	The FB waits for the answer of the Safety PLC after requesting read access to the specified recipe file.	Temporary state. No action required.
8006	The Safety PLC has allowed the read access to the recipe file. The FB now waits for the read command at the FB input CommandRead.	Switch the CommandRead input to SAFETRUE to start the read access.
800C	Reading the data from the addressed data set is in progress followed by the validation of the read data. Details on the fault validation can be found in the chapter "Fault avoidance", section "Data validation".	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).
C020	The 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).
C030	The request for reading the file (sent in state 8002, see above) has been denied by the Safety PLC.	Retry to start the read access by applying a rising edge to the CommandRead input. After that, the FB enters the Prepare state (8002).
C040	Error while reading the recipe file. Either the flash memory of the standard controller cannot be accessed or the file is corrupted.	Verify that the flash memory is installed correctly in the standard controller.
C050	An error occurred while reading the data set in RAM of the Safety PLC during the validation (i.e. previous state was 800C). The file cannot be accessed in the RAM. Possibly there is a simultaneous access to the file/data set by another recipe function block instance.	Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. Retry the read command again at a later time. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C150	An error occurred while reading the data set in RAM of the Safety PLC when the previous state was 8000. The file cannot be accessed in the RAM. Possibly there is another access to the file/data set by another by another recipe function block instance.	Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. (See topic "Preventing multiple and competing accesses to recipe files".) Retry the read command again at a later time. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C060	An inconsistent data set checksum was detected during the validation of the data set (i.e. previous state was 800C): The CRC calculated by the FB is not identical with the read CRC. Possibly, the data set has been falsified by a soft error.	Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C070	An inconsistent data set checksum was detected during the validation of the data set (i.e. previous state was 800C): The data set CRC calculated by the FB is not identical with the expected value applied to the DataSetCRC input of the FB. This means the data set has been overwritten in the meantime by a SF_RecipeWrite FB.	Make sure that the correct recipe file (version) is stored on the target controller. Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started. (See topic "Preventing multiple and competing accesses to recipe files".) Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C080	An inconsistent file checksum was detected during the validation of the data set (i.e. previous state was 800C): The file CRC calculated by the FB is not identical with the expected value applied to the FileCRC input of the FB. This means the file has been overwritten in the meantime by a SF_RecipeWrite FB.	Make sure that the correct recipe file (version) is stored on the target controller. Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started. (See topic "Preventing multiple and competing accesses to recipe files".) Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C090	An inconsistent project checksum was detected during the validation of the data set (i.e. previous state was 800C): The project CRC read from the recipe file is not identical with the project CRC of the current project. Possibly, the project has been modified in the meantime or the recipe file is outdated. Background information on the ProjectCRC comparison The comparison of the project CRC helps ensuring that the recipe file to be read has been written out of exactly the same application project (version). The project checksum has been calculated in PLCnext Engineer when building the project and was then written into the project file. The SF_RecipeWrite FB reads this checksum from the project file and writes it into the header of the recipe file. If the CheckProjectCRC input is set to SAFETRUE, the SF_RecipeRead FB reads the ProjectCRC from the recipe file header and compares it with the ProjectCRC of the current project.	Make sure that the correct recipe file (version) is stored on the target controller. Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C0C0	An inconsistent serial number was detected during the validation of the data set (i.e. previous state was 800C): The serial number of the controller read from the recipe file is not identical with the serial number of the connected controller. Possibly, the controller has been replaced in the meantime or the wrong controller is currently connected.	Make sure that the correct target device is connected.
C160	An inconsistent data set checksum was detected when the previous state was 8000: The CRC calculated by the FB is not identical with the read CRC. Possibly, the data set has been falsified by a soft error.	Retry the read command again at a later time. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002). If the error still exists, write the data set again using a SF_RecipeWrite FB and retry the read command afterwards.
C170	An inconsistent data set checksum was detected when the previous state was 8000: The data set CRC calculated by the FB is not identical with the expected value applied to the DataSetCRC input of the FB. The data set has either been overwritten in the meantime by a SF_RecipeWrite FB or the data it contains has been corrupted.	Make sure that the correct recipe file (version) is stored on the target controller. Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. (See topic "Preventing multiple and competing accesses to recipe files".) Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C180	An inconsistent file checksum was detected when the previous state was 8000: The file CRC calculated by the FB is not identical with the expected value applied to the FileCRC input of the FB. The file has either been overwritten in the meantime by a SF_RecipeWrite FB or the data it contains has been corrupted.	Make sure that the correct recipe file (version) is stored on the target controller. Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C190	An inconsistent project checksum was detected when the previous state was 8000: The project CRC read from the recipe file is not identical with the project CRC of the current project. Possibly, the project has been modified in the meantime. Background information on the ProjectCRC comparison The comparison of the project CRC helps ensuring that the recipe file to be read has been written out of exactly the same application project (version). The project checksum has been calculated in PLCnext Engineer when building the project and was then written into the project file. The SF_RecipeWrite FB reads this checksum from the project file and writes it into the header of the recipe file. If the CheckProjectCRC input is set to SAFETRUE, the SF_RecipeRead FB reads the ProjectCRC from the recipe file header and compares it with the ProjectCRC of the current project.	Make sure that the correct recipe file (version) is stored on the target controller. Make sure that the recipe file is not overwritten or deleted in your safety application while the read operation is in progress. Write the data set again using a SF_RecipeWrite FB and retry the read command afterwards. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C1C0	An inconsistent serial number was detected when the previous state was 8000: The serial number of the controller read from the recipe file is not identical with the serial number of the connected controller. Possibly, the controller has been replaced in the meantime or the wrong controller is currently connected.	Make sure that the correct target device is connected.
C0A0	To recipe file to be read does not exist in the file system of the standard controller.	Create the recipe file using the SF_RecipeWrite FB and retry the read command again at a later time. After applying a rising edge at CommandRead, the FB enters the Prepare state (8002).
C0B0	A validation error occurred: During the validation in the state 8000, the FB detects that the read data set differs from the data set validated in state 800C, i.e., contains unexpected data.	Make sure that the recipe file is not overwritten or deleted in your safety application before the read operation is started.