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__separatorData exchange between safety CPU and AC500 V3 non-safety CPU
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Data exchange between safety CPU and AC500 V3 non-safety CPUdl-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.

Data exchange options between safety CPU and AC500 V3 non-safety CPU:

  • Acyclic non-safe data exchange: several safety CPU cycles needed to transfer the data, max. 84 bytes each direction

  • Cyclic non-safe data exchange: max. 3 safety CPU cycles needed to transfer the data, max. 2 kB each direction

DANGER

DANGER
DANGER
DANGER

DANGER

DANGER

It is not recommended to transfer data values from non-safety CPU to safety CPU. But if doing so, end-users have to define additional process-specific validation procedures in the safety program to check the correctness of the transferred non-safety data, if they would like to use those non-safety values for safety functions.

It is of no concern to transfer data values from safety CPU to non-safety CPU, e.g., for diagnosis and later visualization on operator panels.

  • Acyclic non-safe data exchange
  • Cyclic non-safe data exchange