|
-
All requested safety-related functions are executed correctly, that is to say, are in the defined safe-state, and
-
the function block is activated.
|
|
This state has one of the following reasons:
-
No safety-related function is requested.
-
At least one of the requested safety-related functions has not yet achieved its defined safe-state. However, no monitoring timer or defined threshold has been exceeded.
NOTE:
Due to the different priorities of the safety-related functions, it may be possible that a requested function is overruled by a safety-related function with a higher priority before achieving its defined safe-state. In this case, the S_AllReqFuncActive output also shows SAFEFALSE. Nevertheless, this is not an error.
-
An error has been detected in the safety logic, for example, because a set limit value (time, maximum speed, position tolerance etc.) has been exceeded while executing a safety-related function.
Remedy: A detected error can only be reset by a rising edge applied to the Reset input after removing the cause of the error.
To obtain detailed information on the detected error, evaluate the log entries stored in the EcoStruxure Machine Expert Safety Logger. The Safety Logger can be opened from the contextual menu of the SLC icon in the EcoStruxure Machine Expert devices tree. The Safety Logger is a log file for safety-relevant events that occur.
-
The function block is not activated.
Remedy: Activate the function block by switching its Activate input to TRUE.
|