Fault avoidance
Dieses Thema enthält die folgenden Abschnitte:
- Validation
- Plausibility and connection errors
- Sporadically switching or toggling signal levels or impermissible signals
- SAFETRUE signal at one input during function block activation
- Impermissible SAFETRUE signals in normal operation
- Machine/system start-up without a function test for safety-related equipment
Validation
Only you, the user, machine builder or system integrator can be aware of all the conditions and factors realized in the design of your application for the machine. Therefore, only you can determine the automation equipment and the related safeties and interlocks which can be properly used, and validate such usage.
WARNUNG
|
Unintended machine operation Validate the overall safety-related function and thoroughly test the application. |
Plausibility and connection errors
Plausibility errors are errors which occur, for example, when a range of values is exceeded or an impermissible connection is made. Such errors are detected and reported either by the function block itself or while the project is being compiled. However, this is not always possible in the case of connection errors.
This means that it is not possible, for example, to automatically verify whether:
- Values or constants within the range of validity at inputs are, in fact, incorrect for the safety-related function executed.
- Inputs and/or outputs are incorrectly connected or are not connected when they should be.
WARNUNG
|
Unintended machine operation Validate the signals, formulas, variables or constants connected to the input and output formal parameters of the safety-related function block and thoroughly test the application. |
Sporadically switching or toggling signal levels or impermissible signals
If no additional fault avoidance measures are taken, signal levels which switch or toggle sporadically at the state-controlled inputs may cause the signal to trigger a potentially undesirable corresponding action.
Impermissible signals at inputs can lead to an unintended start-up, prevent a requested action from being executed or cause an error.
These signals may be caused by:
- Programming errors in the application program (user errors).
- Cross circuit, short circuit, and cable break (user errors, wiring errors).
- Manipulation of a two-hand button (user errors).
- Errors in the two-hand control device or the two-hand button (hardware errors).
- Operating errors (user errors).
To prevent this, the following measures can be taken, depending on the safety-related function:
- Using options for cross-circuit detection.
- Suitable cabling.
- Verifying the safety-related code in the Code Editor followed by validation of all safety-related networks.
- Using buttons with two separate contacts (N/C and N/O) to rule out errors caused by a changeover contact.
The measures listed above can also be taken in combination in order to help prevent cascading or otherwise difficult to detect errors.
SAFETRUE signal at one input during function block activation
SAFETRUE signals from the two-hand buttons during function block activation are not permitted. These impermissible signals generate an error message (output Error = TRUE). The function block will then retain the defined safe state (output S_TwoHandOut = SAFEFALSE).
Impermissible SAFETRUE signals in normal operation
Asymmetric switching operations are not permitted (e.g., S_Button1 and S_Button2 became SAFETRUE at the same time, before either S_Button1 or S_Button2 alone switched to SAFEFALSE again and then back to SAFETRUE). They cause the defined safe state to be maintained (output S_TwoHandOut = SAFEFALSE). The function block does not output an error message here (Error = FALSE).
This does not apply where the input states are changing from SAFEFALSE to SAFETRUE with a time offset of more than 500 ms. The function block detects an error here.
Machine/system start-up without a function test for safety-related equipment
Inoperable or error producing safety-related equipment can only be detected by testing whether it is functioning correctly. The function block does not support function testing.
Possible causes of inoperable or error producing safety-related equipment are:
- Inoperable devices (hardware errors)
- Cross circuit, short circuit, and cable break (user errors, wiring errors)
WARNUNG
|
Unintended machine operation
|