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. |
The updates of the safety CPU for boot project, firmware and boot code are performed via non-safety CPU, either via Automation Builder or via SD card.




DANGER

Each firmware and boot code update has to be followed by a complete functional safety validation procedure for a given safety process control application.
-
Update via Automation Builder
-
Update via SD card