ABB AC500-S Safety User Manual page 295

Name Data type
activate_FV_DC BOOL
OA_Req_DC BOOL
The PROFIsafe F-Device instances start asynchronously after power-up. F-Parameters are
written to the PROFINET IO device (CM589-PNIO or CM589-PNIO-4) by the corresponding F-
Host / PROFINET IO controller. F-Parameters are then transferred via the non-safety CPU to
the SM560-S-FD-1 / SM560-S-FD-4, which can use them to parameterize F-Device instance.
If parameterization is repeated, F-Device instances are to be re-initialized at runtime. F-Parame-
ters are only transferred by AC500 communication modules and non-safety CPU and are pro-
tected against transmission errors by the F_Par_CRC.
The F-Source address of an F-Device instance is set at runtime by the F-Host using the
F_Source_Add parameter in F-Parameters. On SM560-S-FD-1 / SM560-S-FD-4, in addition to
the normal tests of the F-Device stack, it is checked that the F-Source address of an F-Device
instance does not overlap with the F-Source addresses of the own F-Host. If there is an overlap,
the error is set for the newly parameterized F-Device instance.
As soon as the F-Device instance is configured, it continues to check that the F-Source
addresses reported by the F-Host are valid. If not, the error is set and the boot project is not
loaded.
The F-Device stack can report the following errors to the F-Host via the status byte:
● Device_Fault: malfunction in the device. This error can be triggered from the application
using the Device_Fault_DS flag on the PROFISAFEDEVICESTACK FB.
● CE_CRC (communication error): CRC error or wrong consecutive number. This error is
automatically triggered by the stack.
● WD_timeout (watchdog timeout): No valid PROFIsafe telegram received within the
F_WD_Time. This error is automatically triggered by the stack.
● FV_activated_S (fail-safe values are activated): Indicates to the F-Host that FV are used. It
can also be set by the FV_activated_DS flag from the F-Device application.
The F-Host can also detect communication errors (watchdog timeout, CRC error or incorrect
consecutive number). The application behind the corresponding F-Device can be informed
about these errors via the activate_FV_DC flag = TRUE of the PROFISAFEDEVICESTACK
instance and can react accordingly.
The application can use the output variable "STATE" to obtain information about the current
status of the F-Device instance.
2020/06/19
Initial value
FALSE
FALSE
NOTICE!
Since the F-Device instances do not support iParameters, the function block
has no possibility to set the bit iPar_OK_S in status byte or read the bit
iPar_EN_C from the PROFIsafe control byte.
3ADR025091M0208, 12, en_US
AC500-S libraries > SafetyDeviceExt_LV100_PROFIsafe_AC500_V27.lib
Description, parameter values
This parameter is for debugging purposes only.
If TRUE, this parameter indicates to the F-Device
that FV shall be used.
This parameter is for debugging purposes only.
If TRUE, the F-Host requests an operator acknowl-
edgment for the F-Device from the F-Host safety
application. In the event of an error (watchdog
timeout or CRC, etc.) the fail-safe values are acti-
vated. If the error is no longer present (the communi-
cation with the module was re-established) and an
operator acknowledgment is possible, the F-Host
driver sets OA_Req_S = TRUE. If the F-Host applica-
tion sets OA_C = TRUE, OA_Req_S is reset to
FALSE and normal operation is resumed.
Configuration and programming
295