Data exchange

For communication via CIP Safety™, the safety option (target) must be connected to a fail-safe controller (F-originator) via EtherNet/IP™.

CIP Safety™ data exchange with MOVISAFE® CSB..A

The CSB..A safety options have the module designation "Safety Output" and "Safety Input" with the following process data assignment for data exchange between the safety option and a fail-safe controller via CIP Safety™:

  • "Technology" profile variant
    • 16 bytes input data
    • The first 4 bytes contain the useful data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.
    • 14 bytes output data
    • The first 3 bytes contain the user data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.
CIP Safety™ data exchange with MOVISAFE® CSS21A, CSS31A and CSA31A

To exchange data between the safety option and a higher-level controller via CIP Safety™, the CSS21A, CSS31A, and CSA31A safety options have the module name "Safety output" and "Safety input" with the following process data assignment:

  • "Technology" profile variant
    • 20 bytes input data
    • The first 6 bytes contain the useful data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.
    • 18 bytes input data
    • The first 5 bytes contain the useful data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.
  • "System" profile variant
    • 32 bytes input data
    • The first 12 bytes contain the useful data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.
    • 18 bytes input data
    • The first 5 bytes contain the useful data from the FS protocol profile, and the remaining bytes are required for the safety IO connection.

Profile data must be evaluated and provided in CIP Safety™ in "Little Endian" notation.