ABB FSO-21 - Page 219

PROFIsafe 219
Safe (Module
passivation with a
command)
PROFIsafe communication is up and running. The FSO application is
running without any detected errors.
The FSO module and all its I/O channels are passivated because the
safety application on the safety PLC requested a module passivation
(activate_FV_C = 1 was set).
The drive is stopped using the configured method. In the end, the drive
STO is activated and the FSO module is in the Safe state. The fail-safe
value “0” is set to all I/O channels. The fail-safe value “0” is transferred to
the safety PLC for all I/O channels.
PROFIsafe Status Byte bits in the F-Host for the FSO module:
• OA_Req_S = 0
• FV_activated_S = 1
• 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 = 0
• SF_end_ack_req = 0
• FSO_state = 1
Safe (User
acknowledgement
request)
PROFIsafe communication is up and running. The FSO application is
running without any errors but waits for the acknowledgment of a module
reintegration (module error has been solved).
The FSO module is in the Safe state. The fail-safe value “0” is still
transferred to the safety PLC for all input channels. All output channels
have a state of “0”. The OA_Req_S bit is reported as “1”.
As soon as the safety application in the safety PLC sets OA_C (positive
edge), the FSO module goes to the Operational state if no further errors
are detected. The OA_C must be “1” until OA_Req_S starts to deliver “0”.
PROFIsafe Status Byte bits in the F-Host for the FSO module:
• OA_Req_S = 1
• FV_activated_S = 1
• Device_Fault = 0
ABB_PS1 profile bits in the F-Host for the FSO module:
• FSO_mode.1 = 0
• FSO_mode.0 = 1
• SF_end_ack_req_local = 0
• SF_end_ack_req = 0
• FSO_state = 1
State Description