GuardLogix System

The
GuardLogix®
 system can communicate with safety I/O devices via
CIP Safety™
 over an
EtherNet/IP™
 network (
Guard I/O™
 modules, integrated safety drives, integrated safety components).
The
GuardLogix®
 controller, can interface with local standard and safety I/O via the backplane and interface with standard and safety I/O via the front Ethernet port.
For standard tasks,
GuardLogix®
 controllers support:
  • Ladder Diagram (LD)
  • Structured Text (ST)
  • Function Block Diagram (FBD)
  • Sequential Function Chart (SFC)
For the safety task, GuardLogix controllers support Ladder Diagram only.
The
GuardLogix®
 system supports up to SIL 3 and PLe safety applications.
  • Without a safety partner installed, you can achieve SIL 2/PLd (Category 3) with the use of the safety task and safety I/O.
  • With the use of the safety task and a safety partner that is installed, you can achieve SIL 3/PLe (Category 4) capability.
For SIL 3 safety applications, the
GuardLogix®
 system is composed of a primary
GuardLogix®
 controller and a safety partner that function together in a 1oo2 architecture.
  • The primary controller is the processor that performs standard and safety functions and communicates with the safety partner for safety-related functions in the
    GuardLogix®
     control system.
  • The safety partner is a co-processor that provides an isolated second channel for safety-related functions in the system. The safety partner does not have a keyswitch or communication port. The primary controller controls the configuration and operation of the safety partner.
  • The safety partner must be installed in the slot immediately to the right of the primary controller. The firmware major and minor revisions of the primary controller and safety partner must match exactly to establish the control partnership that is required for safety applications
For information on Safety Integrity Level (SIL) and Performance Level (PL) requirements and safety application requirements, see the
GuardLogix®
 5580 and
Compact GuardLogix®
 5380 Controller Systems Safety Reference Manual, publication 1756-RM012.

GuardLogix with Safety I/O and Integrated Safety Drives

In the following example, a
GuardLogix®
 safety controller makes the Motion and Safety connections.
IMPORTANT:
If only one controller is used in an application with Motion and Safety connections, it must be a safety controller such as the
GuardLogix®
 5580 controller.
Motion and Safety Configuration (Single Controller)
This image shows an example system with a GuardLogix controller and safety I/O and drives.
In the following example, a standard controller makes the motion-only connection and a separate
GuardLogix®
 5580 controller makes the safety-only connection.
IMPORTANT:
If two controllers are used in an application with motion-only and safety-only connections, the safety-only connection must be a
GuardLogix®
 controller while either a standard or safety controller can make the motion-only connection.
Motion and Safety Configuration (Multiple Controllers)
This image shows an example system with standard and safety controllers.
Item
Description
A
Motion program—Module definition configured with Motion Only connection
B
Safety program—Module definition configured with Safety Only connection
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal