Safetyext2_Lv100_Ac500_V27.Lib - ABB AC500-S Safety User Manual

Configuration and programming
AC500-S libraries > SafetyExt2_LV100_AC500_V27.lib
Value of STATE output on PROFIsafe F-Device stack
instance
PROFIsafe_STATE_DATAEX_F_OUTPUT_COM_ERR
PROFIsafe_STATE_
DATAEX_F_OUTPUT_WD_TIMEOUT
PROFIsafe_STATE_DATAEX_F_OUTPUT_CLEAR

4.6.6 SafetyExt2_LV100_AC500_V27.lib

SafetyExt2_LV100_AC500_V27.lib library includes the following POUs:
System commands
● SF_SAFE_STOP (Triggering of the SAFE STOP on the safety CPU)
System information
● SF_MAX_POWER_DIP_GET_CFG (Getting the configured number of restarts after power
dip in the safety CPU)
● SF_BOOTPROJECT_CRC (Getting boot project CRC)
4.6.6.1 SF_SAFE_STOP
The function SF_SAFE_STOP allows the user setting the safety CPU directly into the SAFE
STOP state.
Table 74: FB name: SF_SAFE_STOP
Name Data type
VAR_INPUT
DUMP_INFO DWORD
VAR_OUTPUT
SF_SAFE_STOP BOOL
298
Meaning
PROFIsafe error: CRC error in PROFIsafe output tele-
gram is detected.
If required, customized AC500 diagnosis message shall
be generated from the application (if
PROFIsafe_STATE_DATAEX_F_OUTPUT_COM_ERR
is detected on STATE output of F-Device stack
instance).
PROFIsafe error: Watchdog timeout detected.
If required, customized AC500 diagnosis message shall
be generated from the application (if
PROFIsafe_
STATE_DATAEX_F_OUTPUT_WD_TIMEOUT is
detected on STATE output of F-Device stack instance).
Zero telegram received, old PROFIsafe output data is
still valid.
Initial value Description, parameter values
16#00000000 The value DUMP_INFO is written to the core dump
so that the user can find out together with the ABB
support team at which point in his safety application
the SAFE STOP state was triggered.
FALSE The output is not used and only available because
functions must be defined with a return value. The
application will not be able to evaluate the output as
the safety CPU switches to the safe state.
3ADR025091M0208, 12, en_US 2020/06/19