-

Done output

Output for signaling "function block processing completed".

Data type: SAFEBOOL

Connection: If required, the signal can be connected to a variable of the SAFEBOOL data type or to other safety-related functions/function blocks.

ValueDescription
SAFETRUE
  • Function block is activated (Activate = TRUE) and
  • the function block has completed its operation successfully.

    This means:

    • The FB has read the recipe data successfully from the specified file and data set.
    • The read file and data set are neither corrupted nor damaged.
    • If the validation of at least one checksum or the serial number was activated, this validation was successful and the read data is considered as valid.
    • The read data is now present at the PayloadRead** outputs (with ** = 0 to 15) of the function block.
The DiagCode = 8000 is shown.

Note
  • The read operation may last several Safety PLC cycles. Therefore, Done may only be set to SAFETRUE after a few cycles after switching the CommandRead input to SAFETRUE.
  • After a successful read operation, output Done remains SAFETRUE until the next operation, even if the CommandRead input is switched back to SAFEFALSE. With a new SAFETRUE signal at CommandRead, Done is always switched to SAFEFALSE.

SAFEFALSE
  • Function block is either not activated (Activate = FALSE, DiagCode = 0000), or
  • an error occurred due to an invalid value applying at a function block input (e.g., IDRecipeFile out of valid range), or
  • the addressed recipe file is not accessible/not existent, or
  • the function block processing is still in progress, or
  • the validation of the read data resulted in an error and the data are considered as invalid. Either at least one checksum or the serial number of the target system.
As long as Done = SAFEFALSE, the failsafe values applied to the FB inputs FV_PayloadRead** are present at the PayloadRead** outputs (with ** = 0 to 15) of the function block instead of the values read from the file.
Observe the hazard message below this table.

Refer to...
  • ... the help topic "Fault avoidance" where the handling of various potential error scenarios is explained.
  • ... the diagnostic code value present at the DiagCode output for details.

WARNING
Non-conformance to safety function requirements
  • Verify that the payload values applied to the inputs of the function block correspond to your risk analysis and always ensure the defined safe state of the application.
  • Be sure that your risk analysis includes an evaluation for incorrectly setting the payload values at the inputs.
  • Validate the overall safety-related function with regard to the set payload values and thoroughly test the application.