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. |




DANGER

If you use an SD card for firmware, boot code and boot project update via non-safety CPU, it is important 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 software update on the safety CPU.
It is possible to read the current firmware version of the safety CPU using POU SF_RTS_INFO⮫ “SF_RTS_INFO”. Thus, you can limit safety program execution only to the pre-defined firmware versions.




NOTICE

You can not update both boot project and firmware / boot code at the same time for the safety CPU. Perform these updates in two steps. It means that you may need two SD cards. One SD card with firmware / boot code update and the other SD card with boot project update.
Firmware and boot code update
The procedure for SD card creation with firmware / boot code for a safety CPU is handled in the same way as described for communciation modules.
Boot project update
The safety CPU boot project can be updated only if no boot project is present on the
safety CPU. This is to avoid unintentional boot project update on the safety CPU.
Before updating a new boot project, delete the existing boot project on the safety
CPU, e.g., via setting the address switch to value 0xFE/0xFC⮫ “Address / configuration switch / F_Dest_Add settings ”, via PLC browser command delappl
in AC500-S Programming Tool or “Online Reset Origin” in Automation Builder.