ABB AC500-S Safety User Manual page 329

No. Item to check
3. Verify that special organizational procedures (e.g., limited
access to the cabinet where safety CPU is located) on
the end-customer site are defined to avoid unintended
firmware and/or boot code update on the safety CPU
using SD card.
4. Verify that correct parameter settings of non-safety CPU
are used for the given safety application
"V2 CPU parameters configuration" on page 375
Ä Appendix C.3 "V3 CPU parameters configuration"
on page 390.
5. Verify that required safety function response time of your
safety application can be satisfied with current AC500-S
safety PLC settings and your SFRT calculation is done
Ä Chapter 5.3 "Safety function response time"
based on
on page 317.
6. Verify that none of safety output channels has a configu-
ration with "Detection" parameter = OFF, which reduces
safety diagnostics for such safety output channels. If
such configuration is used, explain in the "Comment"
section of this checklist your reasons and claim that the
required SIL and PL application levels can be reached
with such configuration.
7. Verify that:
● Address setting is correct.
● Assignment of signal inputs is complete.
● Assignment of signal outputs is complete.
● Assignment of unused inputs is complete.
● All terminal blocks are plugged.
8. Verify that correct firmware versions are used for
dependent non-safety components
"Compatibility with AC500 V2" on page 366
C.1 "Compatibility with AC500 V3" on page 384.
Contact ABB technical support if needed.
9. Verify that only one safety CPU is attached to non-safety
CPU. The use of more than one safety CPU on one non-
safety CPU is not allowed.
10. Verify that the correct CODESYS Safety boot project is
loaded on the right AC500-S safety CPU, for example,
using organizational procedures or fault exclusion (only
one safety CPU is available in the machine).
Examples of organizational procedures are:
● If engineering PC is used and there is more than one
safety CPU, then make sure that only one and right
safety CPU is reachable for engineering PC when the
given CODESYS Safety boot project is transferred to
the safety CPU.
● If SD card is used and there is more than one safety
CPU, then clearly identify each safety CPU and SD
card using a proper ID marking on stickers attached
to each safety CPU and SD card. These ID markings
on stickers shall provide a clearly readable unique
identification of each object to establish clear rules for
relations "SD card with given CODESYS Safety boot
project - Safety CPU".
2020/06/19
Fulfilled (yes / no)?
Ä Appendix B.3
Ä Appendix B.1
Ä Appendix
3ADR025091M0208, 12, en_US
Checklists for AC500-S commissioning
Checklist for configuration and wiring
Comment
329