|
This is the web edition of the original ⮫ AC500-S safety user manual, version 1.3.2. This web edition is provided for quick reference only. The original safety user manual must be used to meet functional safety application requirements. |
You can migrate an existing Automation Builder project with AC500 V2 non-safety CPUs and safety CPUs with cyclic non-safe data exchange to a project with AC500 V3 non-safety CPUs. If you do not want to change the safety application, enable the checkbox “Prevent automatic modification of safety application”. When the checkbox is enabled, no variable assignments between safety and non-safety CPU are done.
In AC500-S Programming Tool, no folder “CyclicNonSafeDataExchange” and no corresponding global variables are generated. The safety application remains unchanged. On safety CPU, data exchange with non-safety CPU is done with specific function blocks. Refer to the corresponding description, available via ⮫ www.abb.com/plc - document no. 3ADR025195M0202.
On non-safety CPU, data exchange with safety CPU is done via the variables defined in tables “From safety CPU” and “To safety CPU”.
NOTICE
If you use the compatibility mode, use the checklist for cyclic non-safe data exchange with AC500 V2.