PROFIsafe 215
Description of states
This table describes the FSO module states and how the states are shown in the
PROFIsafe messages. The Status Byte and the profiles are described in detail in
sections Status Byte and CRC2 bit order on page 201 and FSO PROFIsafe profiles
on page 201.
The table refers to several variables that are available to the programmer of an
F-Host program (for example, an AC500-S program in CoDeSys):
OA_Req_S This variable indicates that the FSO is in the “Safe (User
acknowledgement request)” state ready for acknowledgement.
FV_Activated_S This variable indicates that the FSO is in the Safe state. Fail-safe
values (“0”) are set to the I/O channels.
OA_C This variable indicates that PROFIsafe is running successfully after
PROFIsafe communication error(s) have been solved. The FSO is in
the “Safe (User acknowledgement request)” state and variable
OA_Req_S is set to “1”. Setting OA_C variable to “1” acknowledges
that the PROFIsafe communication errors have been solved and it is
possible to go to the Operational state.
Device_Fault This variable is the Device_Fault bit of the PROFIsafe Status Byte.
When the value is 1, the FSO is in the Fail-safe mode.
State Description
Start-up The FSO module hardware is initialized and internal start-up tests are
executed. After a successful parameterization, the PROFIsafe
communication is expected to be initiated by the PROFIsafe F-Host.
The FSO module remains in this state:
• if the parameterization failed or is pending
• if the PROFIsafe communication is pending.
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 = 0
• SF_end_ack_req_local = 0
• SF_end_ack_req = 0
• FSO_state = 1
To Next Page
Loading...
