dl-breadcrumbs__homedl-breadcrumb-item__separatorAC500-S safety PLCdl-breadcrumb-item__separatorSafety user manual V1.3.2dl-breadcrumb-item__separator...dl-breadcrumb-item__separatorAppendixdl-breadcrumb-item__separatorUsage of safety CPU with AC500 V3 non-safety CPU PM56xxdl-breadcrumb-item__separatorAC500 V3 non-safety CPU PLC commands
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
AC500 V3 non-safety CPU PLC commandsdl-permalink__symbolPermalink

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 following PLC shell commands (if supported by the current non-safety CPU firmware) from non-safety CPU can influence safety CPU state:

  • ‎reboot‎

    It reboots non-safety CPU and, as a result, safety CPU will be restarted as well.

  • ‎stopprg‎, ‎resetprg‎, ‎resetprgcold‎

    They force the safety CPU to leave RUN (safety) mode and to switch to DEBUG STOP (non-safety) mode.

  • ‎startprg‎

    It forces the safety CPU to leave DEBUG STOP (non-safety) mode and to switch to DEBUG RUN (non-safety) mode. If safety CPU is already in RUN (safety) mode or DEBUG RUN (non-safety) mode, this PLC shell command has no influence on the safety CPU.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

The error messages of the safety CPU are aggregated in the diagnosis system on non-safety CPU.

⮫ “Diagnosis and debugging”