ABB AC500-S Safety User Manual page 390

Usage of safety CPU with V3 non-safety CPU PM56xx
C.3 V3 CPU parameters configuration
If non-safety CPU is stopped, the safety CPU will go to DEBUG STOP (non-safety) state
(Fig. 12 on page 43) and safety I/O modules will immediately switch to RUN (module passiva-
tion with a command) state (Fig. 15 on page 51).
Later, if the safety CPU changes to DEBUG RUN (non-safety) state, e.g., after switching non-
safety CPU back to RUN state, the safety I/O modules will immediately change to RUN (ok)
state (Fig. 15 on page 51) and deliver valid process values to the safety CPU without the need
for reintegration.
The following settings of AC500 non-safety module configuraton influence the overall system
behavior of safety and non-safety CPUs.
Settings for non-safety CPU in Automation Builder:
● Tab "PLC Settings"
–
● Tab "CPU-Parameters Parameters"
–
● Tab "I/O-Bus I/O Mapping"
–
Settings for communication module in Automation Builder:
● Tab "PROFINET-IO-Controller I/O Mapping" / "PROFINET-IO-Device I/O Mapping"
–
The settings for these parameters do not compromise on system safety.
390
NOTICE!
The described behavior with V3 non-safety CPUs is different to the behavior
with V2 non-safety CPUs. If you are familiar with V2 non-safety CPUs, you need
to know the following differences:
If V2 non-safety CPU is stopped, the safety CPU will go to DEBUG STOP (non-
safety) state and safety I/O modules will go to RUN (module passivation)
state (Fig. 15 on page 51).
If the safety CPU changes to DEBUG RUN (non-safety) state, the safety I/Os
will have to be reintegrated first by going through the RUN (user acknowl-
edgement request) state (Fig. 15 on page 51) and only then deliver current valid
process outputs to the safety CPU.
"Bus cycle task"
"Stop on error class"
"Bus cycle task"
"Bus cycle task"
3ADR025091M0208, 12, en_US 2020/06/19