PROFIsafe 217
Safe
(Module
passivation &
reintegration)
PROFIsafe communication is up and running. The FSO application is
running with detected errors.
At least one of the active safety functions has encountered an error. For
example, the SLS1 function is active and its speed limits are violated. The
drive is stopped using the configured method. In the end, the drive STO is
activated.
As soon as the STO function has been completed and no errors are
detected, reintegration of the FSO module is possible. It depends on the
FSO configuration from where the reintegration can be done. All tripped
safety functions must be acknowledged to complete the reintegration.
SF_end_ack_req_local is set if any of the safety functions can be
acknowledged locally via FSO inputs.
SF_end_ack_req is set if any of the safety functions can be
acknowledged via PROFIsafe frame bit SF_end_ack. A positive edge
from “0” to “1” is required to acknowledge the module reintegration.
If automatic acknowledgement is configured for the error condition,
neither of the status bits is set. The acknowledgement is done
automatically.
As soon as all errors have been solved and they have been
acknowledged, the Operational state is reached.
PROFIsafe Status Byte bits in the F-Host for the FSO module:
• OA_Req_S = 0
• FV_activated_S = 0
• Device_Fault = 0
ABB_PS1 or ABB_PS2 profile bits in the F-Host for the FSO module:
• FSO_mode.1 = 0
• FSO_mode.0 = 1
• SF_end_ack_req_local = 1, if it is possible to acknowledge any of the
tripped safety functions locally via the FSO inputs.
SF_end_ack_req_local = 0, otherwise.
• SF_end_ack_req = 1, if it is possible to acknowledge any of the tripped
safety functions via PROFIsafe.
SF_end_ack_req = 0, otherwise.
• FSO_state =1
State Description
To Next Page
Loading...
