DescriptionMode
This mode is reached if a fatal error (for example, CPU
test, RAM test, STO channel test, etc., failed) takes
place.
Fault-detected
In the end, the drive STO is activated and transition to
fail-safe mode is performed.
ABB_PS3 profile bits from the module to the F-Host:
• device_mode.0 = 1
• device_mode.1 = 0
Note:
Time spent in this mode may be so short that
device_mode-bits may not be updated to Safety PLC.
The application keeps the system in the safe state.
PROFIsafe communication is up and running.
Fail-safe
This mode is reached after safe stopping function has
been completed in fault-detected mode.
The drive STO is kept permanently active.
PROFIsafe Status Byte bits from the module to the F-
Host:
• Device_fault = 1
ABB_PS3 profile bits from the module to the F-Host:
• device_mode.0 = 0
• device_mode.1 = 1
• device_state = 1
Note:
This mode can be left only to the Start-up mode by
cycling power of the FSPS-21 module or by giving the
reset command via the drive (parameter 51.27), see
the drive firmware manual).
Note:
Modes and states are not directly linked together. The table above shows the states in RUN
mode for simplicity. For example, in fail-safe mode the PROFIsafe communication may also
have an error and appropriate PROFIsafe status bytes are set.
Transitions between states
This table describes the transitions between the FSPS-21 module states. The ID refers to
the transitions shown in the State diagrams (page 118).
DescriptionID
PROFIsafe error and safe state reachedA
No PROFIsafe errors, command bit "activate_FV = 1" from PLC, and safe state reachedB
No PROFIsafe errors and safe state reachedC
No PROFIsafe errors, all stopping-related safety function requests removed, and safety
functions acknowledged
D
No PROFIsafe errors, "activate_FV = 0" from PLC, and no stopping-related safety function
requests active
E
No PROFIsafe errors, "activate_FV = 0" from PLC, and stopping-related safety function re-
quests active
F
PROFIsafe 121