
Description of the Safety Module
Operation Manual
Safety Module for b maXX 5000
BM5-O-SAF-002/3
Document no.: 5.11016.03
45
7
has elapsed and activates the module "STO".
The essential controller settings for this purpose are described in the current parameter
manual b maXX BM5000 ("SS1 Stop" and "SS1 Stop Time").
m
Programming a "General SS1 Time" for specific error types
Basically, all error types carry out "STO" immediately and cause the drive to coast
down and not being braked actively.
h
Measure:
The user can now define an error reaction time for each axis in ProSafePara that are
not assumed to be critical to the system (P207.003 "SS1-Time General Axis 1" and
P207.011 "SS1-Time General Axis 2"), before "STO" is carried out.
This allows a higher-level control or alternatively the controller can bring down the drive
precisely by a brake ramp. After the "SS1 Time General" has elapsed the drive is
switched to STO by the module.
Example: Pulling the EtherCAT cable during a FSoE communication.
In order to achieve an efficient solution the braking ramp on the control or in the
controller must be set in such a way that the drive comes to a standstill before the SS1
time in the SAF module elapses and activates the module "STO".
The related error reaction must be parameterized in the controller (refer to
"Parameterization of the error reaction" and SS1 Stop Time" on
).
The error types which support the SS1 error reaction were marked in the error list from
as "SS1 General".
m
Function-specific SS1 times
There are no configuration options for specific error procedures within the safety func-
tion such as the reaction behavior of a limit value noncompliance or the switching via
FSoE to a data set which was not configured.
h
Measure:
For most of the safety functions independent SS1 times can be defined, that are
activated during specific error procedures within this safety function. This can include
the following (-> listed in the descriptions referring to the specific safety functions):
n
A limit value violation has occurred (such as the exceeding of the incremental
dimension in "SLI").
n
An encoder is not connected (such as in "SLS").
n
Switchover to a data set via FSoE which is not configured.
n
Exceeding the standstill time (no motion at the encoder within the last 12 hours at
"SOS").
This allows a higher-level PLC to bring down the drive precisely by a brake ramp before
"STO" is activated.
If an error occurs at the same moment a message is reported to the controller so that
it can shut down the drive at the brake ramp. In specific cases a higher-level control is
not necessary.
In order to achieve an efficient solution the brake ramp in the controller must be set in
such a way that the drive comes to a standstill before the SS1-time in the SAF module
has elapsed and the activates the module "STO".
Summary of Contents for BM5-O-SAF-002
Page 181: ......