Workflow - ABB AC500-S Safety User Manual

You can transfer your safety program to the safety CPU from a PC or using SD card.
Transferring a 1.
safety applica-
2.
tion program to
SD card
3.
The outlined procedure must be ensured through organizational measures.
For safety applications developed with AC500-S, CODESYS visualizations using CODESYS
Safety are allowed for debugging and maintenance purposes only.

4.2 Workflow

The engineering workflow presented in this chapter describes only the steps needed to instan-
tiate, configure and program safety modules and those non-safety modules which are a part of
the "black channel"
arately covered in
AC500-S system 1.
configuration
2.
and program-
ming workflow
3.
4.
5.
6.
7.
2020/06/19
DANGER!
If you transfer your safety program to safety CPU using SD card, you have to
make sure that the inserted SD card contains the correct safety program. You
can check this through program identification (e.g., boot project CRC) or other
measures, such as a unique identifier on the SD card.
NOTICE!
The safety CPU boot project can be updated via SD card only if no boot project
is present on the safety CPU
Transfer the safety program to the SD card
Perform a program identification - check if SD card and offline (e.g., on PC) safety pro-
gram CRCs match using "Online è Check boot project in file system" in CODESYS
Safety.
Attach an appropriate label to the SD card.
DANGER!
Changing values via controls (e.g., "Write values") would cause the safety CPU
to switch to a DEBUG RUN mode, which is non-safe.
In case of an activation of DEBUG RUN (non-safety) mode on the safety CPU,
the responsibility for safe process operation lies entirely with the organization
and person responsible for the activation of DEBUG RUN (non-safety) mode.
Ä [3] in the safe communication part. All other non-safety modules are sep-
Ä [4].
Install Automation Builder, as described in the installation guide.
Activate a license.
Create a new project and configure user management to limit access to safety modules
and their configuration to safety personnel only.
Install GSDML files to be able to configure 3rd party PROFIsafe F-Devices (optional step).
Instantiate safety modules and non-safety modules, which are a part of the "black
channel" for safe communication, and do a proper configuration of those. Define variable
names for input, output and PROFIsafe signals and pay attention to CODESYS Safety
programming guidelines to define proper variable names.
Write your safety application program and pay attention to system start-up procedure.
Check your program and system configuration. Use the
tion of safety application program" on page 326.
3ADR025091M0208, 12, en_US
Ä "Boot project update" on page 39.
Ä "Boot project update" on page 39.
Ä Chapter 6.2 "Checklist for crea-
Configuration and programming
Workflow
129