Acknowledging a limit value violation of a safety sub-function
After a limit violation of a safety sub-function has been identified, the status of this function will become inactive. In addition, a fault of the "FS Warning" class will be set.
A limit violation must always be acknowledged.
A limit violation cannot be acknowledged through deactivation of the safety sub-function. The exception to this is the SSM safety sub-function, which acknowledges the limit violation by undershooting the limit speed.
The acknowledgment always affects all safety sub-functions. The safety sub-function can still be activated during acknowledgment.
Parameterized speed filters of the safety sub-functions that have triggered a limit violation are reset.
Note the following behavior of the safety sub-functions during an acknowledgment:
- SDI:
- The limit positions are recalculated.
- SLS:
- The delay time and the transition ramp will not be recalculated; there will be an immediate monitoring of the limit speed.
- SS1:
- The delay time and the transition ramp are not recalculated; the final state becomes immediately active (STO activation).