How-To Guide

Designing a Dual-Channel E-Stop Safety Circuit with Compact GuardLogix 5380

Complete guide to designing, wiring, and programming a SIL 3 / PLe dual-channel emergency stop circuit using the Allen-Bradley Compact GuardLogix 5380 controller, 5069-IB8S safety input module, and 5069-OBV8S safety output module. Covers functional safety standards, hardware selection, test pulse wiring, Studio 5000 safety configuration, ladder logic, safety signatures, and system reaction time.

Get a Quote for the 5069-IB8S
SIL 3 Safety Integrity Level
PLe Performance Level
Cat. 4 ISO 13849 Category
5069 Compact 5000 Safety

How-To Guide  ·  Allen-Bradley Compact 5000 Safety  ·  E-Stop Safety Circuit Design

E-Stop Safety Circuit: Compact GuardLogix 5380 + 5069-IB8S Wiring & Configuration Guide

Part Number: 5069-IB8S  ·  Compact GuardLogix 5380 · 5069-IB8S Safety Input · 5069-OBV8S Safety Output · Studio 5000

This guide walks through a dual-channel emergency stop (E-Stop) safety circuit built on the Allen-Bradley Compact GuardLogix 5380 safety controller with Compact 5000 safety I/O: the 5069-IB8S safety input module and the 5069-OBV8S safety output module. It covers the safety ratings, a bill of materials, test-pulse input wiring, contactor output wiring, Studio 5000 module configuration, the safety instructions used for the logic, the safety signature, system reaction time, and troubleshooting. Every terminal, tag, parameter and rating below is taken from the Rockwell Automation publications listed at the end of the page, with the publication and page number given next to it. This guide is a design aid, not a substitute for those manuals or for your own risk assessment and validation.

1. Introduction to Safety Systems

Functional safety is the part of overall equipment safety that depends on automatic protection systems operating correctly in response to hazardous conditions. In industrial automation, this means sensors detect a hazard, a safety controller processes the logic, and actuators remove the hazard, typically by removing power from dangerous motion or energy sources.

The Rockwell ratings quoted in this guide are expressed against these standards:

StandardRating used in this guideWhere it appears
IEC 61508SIL (Safety Integrity Level)Controller type approval: SIL 2 or SIL 3 (1756-RM012, p.8)
IEC 62061SIL CL (SIL claim limit)Controller and safety I/O suitability: SIL CL 2 or SIL CL 3 (1756-RM012, p.8; 5069-UM004, p.35)
ISO 13849-1Performance Level (PL) and Category (Cat.)Controller and safety I/O suitability: PLd (Cat. 3) or PLe (Cat. 4) (1756-RM012, p.8; 5069-UM004, p.35)
EN 60204-1Electrical equipment of machinesListed in the Machinery Directive compliance of the 5069-IB8S and 5069-OBV8S (5069-TD001, p.36)

The Compact 5000 safety I/O modules are designed for applications where the off state is the safe state: safety outputs OFF, and safety input data to the controller OFF (5069-UM004, p.38; 1756-RM012, p.31). Safety I/O devices run self-diagnostics at power-up and periodically during operation; if a diagnostic failure is detected, safety input data to the controller and the local safety outputs are set to the safe state, OFF (1756-RM012, p.31).

An E-Stop circuit is one of the most common safety functions. When an operator presses the E-Stop button, the safety system must de-energize the hazardous motion within a known time, and it must detect faults in its own wiring and go to the safe state when it finds one.

The Risk Assessment Sets the Requirement A risk assessment determines whether a safety function requires SIL 2 or SIL 3 (1756-RM012, p.9), and conformity to the relevant safety standards must be determined for the entire system by conducting a risk assessment (5069-UM004, p.36). The E-Stop is one safety function among those that assessment identifies; it does not replace the other safeguards the assessment calls for.

2. SIL, Performance Level, and Category Ratings

Safety system reliability is expressed through two parallel frameworks. The IEC 61508 / IEC 62061 path uses Safety Integrity Levels (SIL), while the ISO 13849-1 path uses Performance Levels (PL) and Categories. In Rockwell documentation, "SIL 2" represents SIL 2, SIL CL 2 and PLd, and "SIL 3" represents SIL 3, SIL CL 3 and PLe (1756-RM012, p.8).

Controller Ratings

ControllerIEC 61508IEC 62061ISO 13849-1Architecture
Compact GuardLogix 5380, catalog number ending in 2 (5069-L3xxxxxS2)SIL 2SIL CL 2PLd (Cat. 3)1oo1 (single-channel) system
Compact GuardLogix 5380, catalog number ending in 3 (5069-L3xxxxxS3)SIL 3SIL CL 3PLe (Cat. 4)Primary controller plus internal safety partner in a 1oo2 architecture

Sources: 1756-RM012, p.8 (ratings) and p.12 (1oo1 / 1oo2); 5069-UM001, p.47 (catalog-number suffixes, internal safety partner, 1oo2).

Safety I/O Module Ratings

Module and configurationSuitable up to and includingSource
5069-IB8S, single-channel mode, Point Mode = Safety Pulse TestSIL CL 3, PLd, Cat. 35069-UM004, p.72
5069-IB8S, dual-channel mode (set up by a safety instruction), Point Mode = Safety Pulse TestSIL CL 3, PLe, Cat. 45069-UM004, p.72
5069-OBV8S, Output Mode = Sourcing, dual-channel mode, Point Mode = Safety Pulse TestSIL CL 3, PLe, Cat. 45069-UM004, p.79

The 5069-IB8S and 5069-OBV8S are rated SIL CL 3, PLe, Cat. 4 (5069-TD001, pp.38 and 42). Whether a module actually sits in a PLe, Cat. 4 function is decided by the overall architecture: it must be a dual-channel system (5069-UM004, pp.72 and 79). For a function to be SIL 3, the entire chain of devices and programming from sensor to actuator must be SIL 3; do not use a SIL 2 input signal for a function that requires SIL 3 (1756-RM012, p.10).

Choosing SIL 2 or SIL 3 If the risk assessment shows that the highest-risk safety function on a machine requires only SIL 2, a SIL 2 capable controller is acceptable; if at least one function requires SIL 3, a SIL 3 capable controller is required (1756-RM012, p.9). The Compact 5000 safety I/O modules can be used in a SIL 2 system even though they are rated for higher (5069-UM004, p.36).

3. System Hardware Overview

This bill of materials covers a single E-Stop station with a dual-channel input and two contactors on the output:

ComponentCatalog NumberPurpose
Safety Controller5069-L306ERS2 (SIL 2) or 5069-L306ERMS3 (SIL 3)Compact GuardLogix 5380. Executes the safety logic in the safety task. The SIL 3 controller is a primary controller plus an internal safety partner in a 1oo2 architecture (5069-UM001, p.47). Controller firmware must be revision 32.011 or later to use Compact 5000 safety I/O (5069-IN020, p.1).
Safety Input Module5069-IB8SEight safety sinking inputs and four test outputs (5069-UM004, p.72). 1 slot wide (5069-TD001, p.35).
Safety Output Module5069-OBV8SEight safety outputs, used as Bipolar (sourcing/sinking) pairs or as sourcing outputs (5069-UM004, p.79). 1.5 slots wide (5069-TD001, p.35).
Power Supplies24V DC, SELV/PELV-listedSELV/PELV supplies are required for MOD power and SA power in functional safety applications (5069-IN020, p.6), and for the OBV8S LA power (5069-TD001, p.39). Separate supplies for MOD and SA power are recommended (5069-IN020, p.6).
E-Stop ButtonTwo normally closed contactsOne contact per channel of the dual-channel input (wiring per 5069-UM004, p.135). The device itself must meet the safety level your risk assessment requires (5069-UM004, p.36).
Safety ContactorsIEC 60947 qualified contactors (K1 + K2)Two contactors switched by the OBV8S. For Cat. 4 the actuator must be qualified, for example in accordance with IEC 60947 (5069-TD001, pp.40 and 42). A feedback contact on each contactor is used for output monitoring (Section 6).
Input RTB5069-RTB18-SPRING or 5069-RTB18-SCREW18-position removable terminal block for the 5069-IB8S. Ordered separately; RTBs do not ship with the module (5069-IN020, p.5).
Output RTB5069-RTB18-SPRING or 5069-RTB18-SCREW18-position removable terminal block for the 5069-OBV8S. Ordered separately (5069-TD001, p.35).
Controller RTB Kit5069-RTB64-SPRING or 5069-RTB64-SCREWMOD power (4-point) and SA power (6-point) terminal blocks for the controller. Order separately, one kit per controller (5069-TD002, pp.5 and 26).
Standard Input Module (optional)5069-IB16Non-safety status and indication signals only. Standard data brought into the safety task through tag mapping has no SIL rating; SIL 2 or SIL 3 functions must use appropriately rated safety inputs (5069-UM001, p.50).
SIL 2 vs. SIL 3 Controller Selection Compact GuardLogix 5380 controllers whose catalog number ends in 2 are for safety applications up to and including SIL 2 / PLd. For SIL 3 / PLe you need a catalog number ending in 3, which consists of a primary controller and an internal safety partner functioning together in a 1oo2 architecture (5069-UM001, p.47; 1756-RM012, p.9).
Ordering Tip: Don’t Forget the RTBs A common procurement mistake is ordering the modules without terminal blocks. The 5069-IB8S and 5069-OBV8S each need one 5069-RTB18-SPRING or 5069-RTB18-SCREW (5069-TD001, p.35), and the Compact GuardLogix 5380 controller needs a 5069-RTB64-SPRING or 5069-RTB64-SCREW kit. All of them are ordered separately (5069-TD002, p.26).

4. How a Dual-Channel E-Stop Circuit Works

A dual-channel circuit uses two separate normally closed contacts on the E-Stop button, each wired to its own safety input on the 5069-IB8S. On this platform the two inputs are not paired in the module. The 5069-IB8S has no point operation type; all of its inputs are treated as single channels (1756-RM012, p.34), and you cannot configure dual-channel mode in the Module Properties. Dual-channel operation is set up with a safety instruction in the safety task (5069-UM004, p.72). Rockwell recommends single-channel mode for inputs that feed a dual-channel instruction such as the Dual Channel Input - Stop (DCS) instruction (5069-UM004, p.36).

  1. Both channels ON (contacts closed): the E-Stop is not pressed and both safety inputs read 1.
  2. Both channels OFF (contacts open): the E-Stop is pressed, both inputs read 0, and the safety logic turns the safety outputs off.
  3. Channels disagree: the DCS instruction evaluates the two channels; dual-channel instruction diagnostics give fault codes that identify channel-specific discrepancy (1756-RM012, p.34).
  4. Wiring fault on a channel: with Safety Pulse Test, the module detects short circuits between an input and 24V and between input signal lines; on an error, Safety Input Data and Safety Input Status for that channel turn off (5069-UM004, pp.73-74).

Choosing the two inputs: you can connect devices to any channel or combination of channels (5069-TD001, p.35). Use one even and one odd input with the safety instruction (5069-UM004, p.36), for example Safety IN 0 and Safety IN 1, and feed each from a different test output (5069-UM004, p.73).

Test Outputs (Safety Pulse Test) Explained

The 5069-IB8S has four test outputs: Test OUT 0, Test OUT 1, Test/Muting OUT 2 and Test/Muting OUT 3 (5069-UM004, p.72; 5069-TD001, p.38 lists 2 test output channels and 2 test output/muting output channels). Each test output is brought out to two RTB terminals (5069-TD001, p.37). Test outputs are rated 300 mA per channel in horizontal mounting, 200 mA in other orientations (5069-TD001, p.38).

When an input is configured for Safety Pulse Test, the external contact is wired between a test output and the input. While the contact is closed, the test output sends a pulse through the field wiring and input circuit, so short circuits between the input and 24V power, and between input signal lines, can be detected (5069-UM004, p.73). The test pulse width is < 700 µs and the test pulse period is < 100 ms (5069-UM004, p.73; 5069-TD001, p.38).

Two rules come from the manuals: safety input pairs must be associated with different test output sources (5069-UM004, p.73), and Rockwell recommends wiring even-numbered inputs to even-numbered test outputs and odd-numbered inputs to odd-numbered test outputs to maximize diagnostic independence (5069-TD001, p.38). Studio 5000 also limits how many pulse-tested inputs one test source can serve; for example, Test Source 0 can be mapped to a maximum of two Safety Pulse tests (5069-UM004, p.106).

Test Outputs Are Not Safety Outputs Never use test outputs as safety outputs (5069-UM004, p.37). They supply the pulse source for the input circuit; contactors and other actuators are driven from the 5069-OBV8S.
Category Depends on the Connection Method For an emergency stop button, Rockwell lists two connection methods: contacts connected between the safety inputs and test outputs without pulse testing (or between a 24V DC SELV/PELV supply and the inputs) for Category 3, and contacts connected between the safety inputs and the test outputs with test pulses for Category 4 (5069-UM004, p.135). A single-channel IB8S input with Safety Pulse Test is suitable up to SIL CL 3, PLd, Cat. 3; PLe, Cat. 4 needs the dual-channel architecture (5069-UM004, p.72). Your risk assessment sets which you need.

5. Wiring the E-Stop to the 5069-IB8S

This section wires a dual-channel E-Stop to Safety IN 0 and Safety IN 1 on the 5069-IB8S, with both inputs set to Safety Pulse Test. This is the Category 4 connection method for an emergency stop button (5069-UM004, p.135). Wire the module as shown in 5069-TD001 (5069-UM004, p.37), and follow the terminal markings on the module and RTB.

Dual-Channel Wiring Table (Safety IN 0 + IN 1, Safety Pulse Test)

WireFromToFunction
1Test OUT 0 (RTB terminal 8 or 9)E-Stop NC contact 1, one sidePulse source for channel A (even input, even test output)
2E-Stop NC contact 1, other sideSafety IN 0 (RTB terminal 0)Channel A
3Test OUT 1 (RTB terminal 10 or 11)E-Stop NC contact 2, one sidePulse source for channel B (odd input, odd test output; a different source from channel A)
4E-Stop NC contact 2, other sideSafety IN 1 (RTB terminal 1)Channel B

Terminal numbers from the 5069-IB8S wiring diagram, 5069-TD001, p.37. Pairing rules: 5069-UM004, p.73; 5069-TD001, p.38.

The module takes its field power from the SA power bus; it uses DC SA power, supplied through the SA power RTB on the Compact GuardLogix 5380 controller, a 5069-AENTR or 5069-AEN2TR adapter, or a 5069-FPD field potential distributor (5069-TD001, pp.35 and 37). When a Compact 5000 safety module is on an SA power bus, only a 24V DC SELV/PELV-rated supply may provide SA power to that bus (5069-IN020, p.6). The COM terminals are used as the return when a test output is configured to power a device or a muting lamp (5069-TD001, p.37).

Terminal Map: 5069-IB8S RTB

RTB TerminalFunction
0–7Safety IN 0 through Safety IN 7
8, 9Test OUT 0 (two terminals)
10, 11Test OUT 1 (two terminals)
12, 13Test/Muting OUT 2 (two terminals)
14, 15Test/Muting OUT 3 (two terminals)
16, 17COM (two terminals)

Source: 5069-TD001, p.37 (wiring diagram with RTB terminal numbers); same terminal order in 5069-UM004, p.113.

Wiring Practices

  1. Feed the contacts from the test outputs. In the Category 4 method the E-Stop contacts sit between the safety inputs and the test outputs (5069-UM004, p.135). Connecting the contacts to an external 24V supply instead is the Category 3 method (5069-UM004, p.135).
  2. Use a different test output for each channel. Safety input pairs must be associated with different test output sources (5069-UM004, p.73). Note that terminals 8 and 9 are both Test OUT 0, so do not use terminals 8 and 9 for the two channels.
  3. Wire size and type. 0.5–1.5 mm² (22–16 AWG) solid or stranded shielded copper wire rated 105 °C (221 °F) or greater, one wire per terminal (5069-TD001, p.35). Do not wire more than 2 conductors on any terminal (5069-IN020, p.4).
  4. Stripping and torque. Strip 10 mm (0.39 in.) for the spring RTB and 12 mm (0.47 in.) for the screw RTB; torque screw terminals to 0.4 N•m (3.5 lb•in). On the spring RTB, crimp a ferrule on a wire that is too thin (5069-IN020, p.8).
  5. Power off first. The RTB and the module do not support removal and insertion under power (5069-IN020, p.7). Confirm MOD power and all SA power are off before you wire (5069-IN020, p.8).

Using the Remaining Inputs

The IB8S has eight safety inputs and four test outputs, and each test source can serve at most two Safety Pulse tests (5069-UM004, pp.72 and 106). Plan the test-source assignment for every pulse-tested input before you wire, keeping each dual-channel pair on two different test outputs (5069-UM004, p.73). Test/Muting OUT 2 and 3 can be used as pulse-test sources when their Point Mode is Pulse Test rather than Muting Lamp (5069-UM004, p.57). The example in this guide also uses spare inputs for the reset button and the contactor feedback (Sections 6 and 8).

6. Wiring the Safety Contactors to the 5069-OBV8S

The 5069-OBV8S has eight safety outputs that are used either as sourcing/sinking pairs in Bipolar Output Mode or as sourcing outputs in Sourcing Output Mode (5069-UM004, p.79). Each channel has a P (sourcing) and an N (sinking) terminal (5069-TD001, p.39). Dual-channel mode, where two output channels act as a connection pair, is only available with Output Mode = Sourcing; the pairs are 0 and 1, 2 and 3, 4 and 5, 6 and 7 (5069-UM004, p.82). Bipolar outputs have no point operation type and operate as a sinking/sourcing pair on one channel (1756-RM012, p.35).

Dual-Channel Sourcing Wiring (Outputs 0 + 1)

WireFrom (5069-OBV8S RTB)ToFunction
1Safety OUT 0 P (terminal 0)Contactor K1 coilChannel 1 of the output pair
2Contactor K1 coil, other sideLA–Coil return
3Safety OUT 1 P (terminal 2)Contactor K2 coilChannel 2 of the output pair
4Contactor K2 coil, other sideLA–Coil return
5LA+ (terminal 16)+24V DC SELV/PELV-listed supplyLocal Actuator (field-side) power for the module
6LA– (terminal 17)0V of the same supplyLocal Actuator power return

Source: 5069-TD001, p.41, "Dual Channel with Actuator" (suitable up to Category 4 with diagnostic testing, for example Safety Pulse Test). Terminal numbers from the RTB in the same diagrams, 5069-TD001, pp.39 and 41.

The motor power runs through the contacts of both K1 and K2 in series, as drawn in the Rockwell diagram (5069-TD001, p.41), so either contactor opening removes power from the motor.

Bipolar alternative: in Bipolar Output Mode, the documented "Single Channel with Actuator" example connects K1 and K2 between Safety OUT 0 P and Safety OUT 0 N; in Bipolar mode you must connect the device to both terminals of the pair (5069-TD001, p.39). That arrangement is also listed as suitable up to Category 4 with diagnostic testing, and requires configuring the application so that a No Load fault is detected only if both the P and N wires are disconnected (5069-TD001, p.39). This guide uses the dual-channel sourcing arrangement above.

Output Monitoring (Contactor Feedback)

For Category 4 applications where the output stays off for a prolonged time, Rockwell recommends one of these: apply output monitoring at the actuator (direct or indirect), limit the safe state to no more than 24 hours, or conduct a functional test if the safe-state dwell time increases (5069-TD001, pp.39 and 41). Monitoring at the actuator is done with the Configurable Redundant Output (CROUT) safety instruction, which controls and monitors redundant outputs and takes two feedback signals (1756-RM012, pp.82 and 88).

  1. Wire a feedback contact from K1 to a spare 5069-IB8S safety input, for example Safety IN 4, fed from Test/Muting OUT 2 (terminal 12) with Point Mode = Safety Pulse Test.
  2. Wire a feedback contact from K2 to Safety IN 5, fed from Test/Muting OUT 3 (terminal 14). Even input to even test output and odd to odd (5069-TD001, p.38).
  3. In the safety logic, use IN 4 and IN 5 as CROUT Feedback 1 and Feedback 2 (Section 8). Use feedback contacts that the contactor manufacturer specifies for monitoring. With normally closed feedback contacts, as in Rockwell's CROUT example, set the CROUT Feedback Type to Negative; with normally open contacts, set it to Positive (1756-RM095, pp.22 and 29-30).
5069-OBV8S Uses LA Power, Not SA Power The 5069-OBV8S does not draw current from the SA power bus; its field-side power comes from the LA+ and LA– terminals, and as a DC-type module it must sit on a DC SA power bus (5069-TD001, p.39). LA power on-state voltage is 17.5–32V DC, and LA power is 8 A per module in horizontal mounting (5069-TD001, p.42). If an output module and an input module are directly connected and powered from separate supplies, Rockwell strongly recommends connecting SA– and LA– together to reduce the risk of grounding float from disruptive diagnostics (5069-TD001, p.39).
5069-OBV8S RatingValueSource
Output current1 A per channel (horizontal); 0.7 A per channel (other orientations)5069-TD001, p.42
Surge current per point, max1.5 A5069-TD001, p.42
Output delay time (backplane to screw)4 ms, max5069-TD001, p.42
Safety reaction time (SRT)4.5 ms5069-TD001, p.42
Output test pulseWidth < 700 µs, period < 100 ms5069-UM004, p.80

7. Studio 5000 Safety Project Configuration

Use Studio 5000 Logix Designer version 32 or greater with the Compact 5000 safety I/O modules (5069-UM004, p.99). By default, all safety input and output channels are disabled, so you must configure every point you use (5069-UM004, p.103).

Create the Safety Project

  1. Create a project for the Compact GuardLogix 5380 controller, for example 5069-L306ERS2 (SIL 2) or 5069-L306ERMS3 (SIL 3).
  2. The safety task. A safety application includes a safety task with a safety program and main routine. There can be only one safety task per controller, it cannot be deleted, and only ladder diagram is supported in it (1756-RM012, pp.47-48).
  3. Set the safety task period, priority and watchdog (right-click the safety task → Properties → Configuration). Period: 2–500 ms; watchdog: 2–500 ms; a priority of 1 is recommended (1756-RM012, pp.48-49 and 108). The watchdog must be less than or equal to the period (1756-RM012, p.103). The period cannot be edited online (1756-RM012, p.48).

Add the 5069-IB8S Safety Input Module

  1. Go offline. Compact 5000 safety I/O modules cannot be added while the project is online (5069-UM004, p.100).
  2. Right-click the 5069 Backplane → New Module, select 5069-IB8S, and assign the slot number on the General page (5069-UM004, pp.100 and 103).
  3. Module Definition (General page → Change): Configured By = This Controller; Input Data = Safety data; Muting Lamp Points = None (5069-UM004, p.105).
  4. Input Points page: enable Safety IN 0 and Safety IN 1 with Point Mode = Safety Pulse Test, and assign each a different test source (Test Output 0 for IN 0, Test Output 1 for IN 1) (5069-UM004, pp.73 and 106). Leave the channels in single-channel operation; there is no dual-channel setting on this page (5069-UM004, p.72; 1756-RM012, p.34). Configure IN 2, IN 4 and IN 5 the same way for the reset button and contactor feedback.
  5. Input delay: Off to On and On to Off delays are 0–50 ms, default 0 ms (5069-UM004, pp.49 and 75). Any delay adds to reaction time (1756-RM012, p.32).
  6. Test Output Points page: set the test outputs you use to Point Mode = Pulse Test (5069-UM004, pp.57 and 106; 5069-TD001, p.38).
  7. Transition Time Limit: the IB8S checks its two internal signals for each input; the user-configurable limit is 2–500 ms on firmware revision 2.011 or later (fixed 2 ms on revision 1.011), and the Add-On Profile version 2.01 is needed to see the setting (5069-UM004, p.77). This is an internal per-channel check. The channel-to-channel comparison of the two E-Stop contacts is done by the DCS instruction.
  8. Safety page: set the RPI here (not on the Connection page); the Advanced button sets the Connection Reaction Time Limit (5069-UM004, pp.103-104).

Add the 5069-OBV8S Safety Output Module

  1. Right-click the 5069 Backplane → New Module and select 5069-OBV8S (5069-UM004, p.100).
  2. Module Definition: Configured By = This Controller; Output Mode = Sourcing for the dual-channel wiring in Section 6 (5069-UM004, p.105).
  3. Points page: configure outputs 0 and 1 with Point Operation Type = Dual and Point Mode = Safety Pulse Test (5069-UM004, pp.63 and 79; 1756-RM012, p.35). Short Circuit Detection is required in functional safety applications (5069-UM004, p.63). No Load Detection is enabled by default (5069-UM004, p.62).
  4. RPI: the safety task period determines the RPI for the 5069-OBV8S (5069-UM004, p.104).

Safety Network Number (SNN)

The SNN uniquely identifies CIP Safety subnets within a routable safety network, and the combination of SNN plus node address identifies each CIP Safety port on each device. A Compact GuardLogix 5380 controller has as many as three SNNs: one for each Ethernet port and one for the backplane. Each CIP Safety network must have a unique SNN (5069-UM001, pp.47-48).

Local Compact 5000 safety I/O modules are automatically assigned the same SNN as the 5069 Backplane SNN in the controller configuration (5069-UM004, p.103). Manual SNN assignment is required when a controller port joins a CIP Safety subnet that already has an established SNN, or when a safety project is copied to another installation within the same routable CIP Safety system (5069-UM001, p.48).

Module Tags Used in This Example

TagTypeMeaning
Local:1:I.Pt00.Data, Local:1:I.Pt01.DataBOOLCurrent safety input value of IN 0 / IN 1: 0 = Off, 1 = On
Local:1:I.Pt02.Data, Local:1:I.Pt04.Data, Local:1:I.Pt05.DataBOOLCurrent safety input value of IN 2 (reset pushbutton) and IN 4 / IN 5 (K1 / K2 feedback): 0 = Off, 1 = On
Local:1:I.Pt00.Status, Local:1:I.Pt01.Status, Local:1:I.Pt04.Status, Local:1:I.Pt05.StatusBOOLChannel status: 0 = Bad (causes a fault), 1 = Good
Local:1:I.Pt00.Fault, Local:1:I.Pt01.FaultBOOL1 = bad data (faulted) or channel set to Not Used
Local:1:I.Test00.Fault, Local:1:I.Test01.FaultBOOLTest output fault: 1 = bad data (faulted) or set to Not Used
Local:1:I.ConnectionFaultedBOOL0 = connection running, 1 = connection not running
Local:2:I.Pt00.Status, Local:2:I.Pt01.StatusBOOLStatus of OBV8S outputs 0 and 1: 0 = Bad, 1 = Good (the OBV8S exchanges input data with the controller)
Local:2:O.Pt00.Data, Local:2:O.Pt01.DataBOOLOutput command for OUT 0 (K1) and OUT 1 (K2): 0 = Off, 1 = On

Source: 5069-UM004, pp.130-131 (safety I/O module tags) and p.105 (OBV8S input data). In this example the 5069-IB8S is in slot 1 and the 5069-OBV8S in slot 2; replace the slot numbers with yours.

8. Safety Logic

All safety logic runs in the safety task, and only safety application instructions can be used in the safety task for SIL 2 or SIL 3 applications (1756-RM012, p.88). Safety tags can be read or written by safety logic; standard logic can read controller-scoped safety tags directly, and external devices such as HMIs cannot write safety tags (5069-UM001, p.50).

The E-Stop function uses two safety instructions from the Compact GuardLogix 5380 instruction set (1756-RM012, p.88):

InstructionNameDescription (1756-RM012, p.88)
DCSDual Channel Input - StopMonitors dual-input safety devices whose main purpose is to provide a stop function, such as an E-stop, light curtain, or gate switch.
CROUTConfigurable Redundant OutputControls and monitors redundant outputs.

Example Routine Structure

The dual-channel safety instructions have built-in safety I/O status monitoring: the DCS has input status for channels A and B, and the CROUT has input status for Feedbacks 1 and 2 and output status for the output channels driven by its O1 and O2 outputs. These status tags must be 1 for the instruction outputs (O1 for input instructions, O1/O2 for CROUT) to energize, and Rockwell states it is important to drive them before (above) the safety instruction (1756-RM012, p.82). The routine therefore builds the status bits first:

// Internal safety tags (BOOL, safety class): EStop_InStatus, Fbk_InStatus, Out_Status // Backing tags (safety class, one per instruction): EStop_DCS (DCI_STOP), K1K2_CROUT (CONFIGURABLE_ROUT) // RUNG 0 -- Input status for the E-Stop channels (IN 0, IN 1) XIC Local:1:I.Pt00.Status XIC Local:1:I.Pt01.Status OTE EStop_InStatus // RUNG 1 -- Input status for the contactor feedback channels (IN 4, IN 5) XIC Local:1:I.Pt04.Status XIC Local:1:I.Pt05.Status OTE Fbk_InStatus // RUNG 2 -- Output status for OBV8S outputs 0 and 1 XIC Local:2:I.Pt00.Status XIC Local:2:I.Pt01.Status OTE Out_Status // RUNG 3 -- Dual Channel Input Stop (configuration and operands in the table below) DCS DCS EStop_DCS Safety Function E-stop Input Type Equivalent - Active High Discrepancy Time 500 (ms) Restart Type Manual Cold Start Type Manual Channel A Local:1:I.Pt00.Data Channel B Local:1:I.Pt01.Data Input Status EStop_InStatus Reset Local:1:I.Pt02.Data // outputs: EStop_DCS.O1, EStop_DCS.FP (Fault Code and Diagnostic Code are members of the backing tag) // RUNG 4 -- Configurable Redundant Output, actuated by the DCS O1 output CROUT CROUT K1K2_CROUT Feedback Type Negative Feedback Reaction Time 250 (ms) Actuate EStop_DCS.O1 Feedback 1 Local:1:I.Pt04.Data Feedback 2 Local:1:I.Pt05.Data Input Status Fbk_InStatus Output Status Out_Status Reset Local:1:I.Pt02.Data // outputs: K1K2_CROUT.O1, K1K2_CROUT.O2, K1K2_CROUT.FP // RUNG 5 -- CROUT Output 1 drives K1 (OBV8S OUT 0) XIC K1K2_CROUT.O1 OTE Local:2:O.Pt00.Data // RUNG 6 -- CROUT Output 2 drives K2 (OBV8S OUT 1) XIC K1K2_CROUT.O2 OTE Local:2:O.Pt01.Data

DCS and CROUT are ladder-only instructions; neither is available in function block or structured text (1756-RM095, pp.21-22 and 81). Rungs 5 and 6 follow the CROUT programming example, where the instruction's O1 and O2 members each drive one safety output point (1756-RM095, p.30). Use a separate backing tag for each instruction, and never write to an instruction output tag or a backing tag member; Rockwell warns this can cause unexpected operation, including a major nonrecoverable fault (1756-RM095, pp.22 and 81).

DCS Operands

OperandData typeValid valuesThis example, and whySource
DCS (backing tag)DCI_STOPTagEStop_DCS, used by this one instruction only1756-RM095, p.82
Safety FunctionDINTE-stop, safety gate, light curtain, area scanner, safety mat, cable (rope) pull switch, user-definedE-stop. Documentation only; it does not change how the instruction behaves.1756-RM095, p.82
Input TypeDINTEquivalent (0): active when Channel A and Channel B are both 1. Complementary (2): active when Channel A is 1 and Channel B is 0.Equivalent. Both E-Stop contacts are normally closed, so both inputs read 1 when the button is released.1756-RM095, p.82
Discrepancy Time (ms)DINT5–3000 ms500 ms, the value in Rockwell's own DCS programming example. It is how long Channel A and Channel B may disagree before the instruction faults; confirm it against your E-Stop's contact behavior during validation.1756-RM095, pp.82-83 and 95
Restart TypeListManual (0): an OFF-to-ON transition of Reset, with all enabling conditions met, is needed to energize O1. Automatic (1): O1 energizes 50 ms after all enabling conditions are met.Manual, so releasing the E-Stop alone does not restart the machine; the operator presses the reset button. Rockwell states Automatic may be used only where you can prove no unsafe condition can result, or the reset is performed elsewhere in the safety circuit.1756-RM095, p.83
Cold Start TypeBOOLManual (0): O1 is not energized when Input Status becomes valid or an Input Status fault clears; the device must be tested first. Automatic (1): O1 energizes as soon as Input Status becomes valid with both inputs active.Manual, so after power-up or a change to Run the E-Stop must be cycled through the safe state (pressed and released) before a reset can energize O1.1756-RM095, pp.83-84 and 86
Channel ABOOLTagLocal:1:I.Pt00.Data (IN 0, even input, Section 5). The input point must be configured as single, not Equivalent or Complementary.1756-RM095, pp.81 and 84; 5069-UM004, p.36
Channel BBOOLTagLocal:1:I.Pt01.Data (IN 1, odd input)1756-RM095, p.84; 5069-UM004, p.36
Input StatusBOOLTag or immediate. 1 = inputs valid, 0 = inputs invalid.EStop_InStatus, built in Rung 0 from the two channel status bits. When inputs come from a safety I/O module this is the module status (Connection Status or Combined Status); when derived in logic, the programmer decides the conditions.1756-RM095, p.84; 1756-RM012, p.82
ResetBOOLTag. OFF-to-ON transition energizes O1 (Manual restart) and resets FP and Fault Code.Local:1:I.Pt02.Data (reset pushbutton on IN 2). Some safety standards require monitoring the reset transition, which may need extra logic.1756-RM095, pp.84-85
O1 (output)BOOL–EStop_DCS.O1, the Actuate input of the CROUT. De-energizes when either channel goes to the safe state or Input Status goes to the safe state.1756-RM095, p.85
FP, Fault Code, Diagnostic Code (outputs)BOOL, DINT, DINT–Read for alarms and troubleshooting (Section 11). Fault Code and Diagnostic Code are not safety-related.1756-RM095, p.85

CROUT Operands

OperandData typeValid valuesThis example, and whySource
CROUT (backing tag)CONFIGURABLE_ROUTTagK1K2_CROUT, used by this one instruction only1756-RM095, p.22
Feedback TypeBOOLPositive (1): Feedback 1 ON when Output 1 ON. Negative (0): Feedback 1 OFF when Output 1 ON.Negative, for normally closed feedback contacts on K1 and K2 (closed while the contactor is de-energized), as in Rockwell's CROUT wiring and programming example. Use Positive only if your feedback contacts are normally open.1756-RM095, pp.22 and 29-30
Feedback Reaction TimeDINT5–1000 ms250 ms, the value in Rockwell's CROUT example. It is how long the instruction waits for Feedback 1 and 2 to follow Output 1 and 2, so it must be longer than the contactor's switching time from the contactor manufacturer's data.1756-RM095, pp.22 and 30
ActuateBOOL1 = energize O1 and O2 if no faults exist; 0 = de-energize themEStop_DCS.O11756-RM095, p.23
Feedback 1 / Feedback 2BOOLTag. Must follow Output 1 / Output 2 within the Feedback Reaction Time.Local:1:I.Pt04.Data (K1) / Local:1:I.Pt05.Data (K2)1756-RM095, p.23
Input StatusBOOLTag or immediate. 1 = inputs valid.Fbk_InStatus (Rung 1)1756-RM095, p.23
Output StatusBOOLTag or immediate. 1 = output connection and module operational; 0 = module fault or connection lost.Out_Status (Rung 2)1756-RM095, pp.23-24
ResetBOOLOFF-to-ON transition resets FP and Fault Code if the fault condition is no longer presentLocal:1:I.Pt02.Data, the same reset pushbutton1756-RM095, p.24
O1 / O2 (outputs)BOOL–K1K2_CROUT.O1 / .O2, driving Local:2:O.Pt00.Data (K1) and Local:2:O.Pt01.Data (K2) in Rungs 5 and 6. Each de-energizes on a feedback fault, when Input Status or Output Status goes to 0, or when Actuate goes to 0.1756-RM095, pp.24 and 30
FP, Fault Code, Diagnostic Code (outputs)BOOL, DINT, DINT–Read for alarms and troubleshooting. Fault Code and Diagnostic Code are not safety-related.1756-RM095, pp.24-25
Restart and Reset Are Set by Your Risk Assessment The values above are this example's choices, taken from Rockwell's own DCS and CROUT examples. Whether restart after an E-Stop must be manual, how the reset is done, and the discrepancy and feedback times are decisions for your risk assessment and the machinery standards it applies. Configuration operands cannot be changed at runtime; if you edit them in Run mode, accept the pending edits and cycle the controller from Program to Run for them to take effect (1756-RM095, pp.22 and 81; 1756-RM012, p.76).
A Reset Button on a Standard Input This example wires the reset pushbutton to a spare safety input (Safety IN 2, Test OUT 0). A standard input can only reach the safety task through safety tag mapping, mapped data has no SIL rating, and Rockwell warns not to directly control a SIL 2 or SIL 3 safety output with standard data (5069-UM001, p.50; 1756-RM012, pp.53-54). If you use mapped standard data, 1756-RM012, p.54 shows how to qualify it with safety data.
Monitor the Connections in Logic Safety I/O connections cannot be configured to fault the controller automatically when a connection is lost; if you must detect a device fault to keep the required SIL, monitor the connection status bits and initiate the fault in program logic (1756-RM012, p.82). When a connection is faulted, the safety data is reset to zero (1756-RM012, p.81).

9. Safety Signature and Validation

The safety signature verifies the integrity of a safety application. It applies to the entire safety portion of the controller project and consists of a unique 64-character alphanumeric ID plus a time stamp. Creating, recording and verifying it is a mandatory part of the safety-application development process, and it must be present for the controller to operate as a SIL 2/PLd or SIL 3/PLe safety controller; operation without it is only suitable during development (1756-RM012, pp.9 and 16; 5069-UM001, p.49). Nothing in the standard application is included in the safety signature (1756-RM012, p.16).

The signature is a hierarchy of safety signature elements (safety task, programs, routines and so on), each with its own ID and time stamp. The elements help impact analysis by identifying which parts changed; the Safety Signature report lists them (1756-RM012, p.16).

Generating the Safety Signature

  1. Check the prerequisites: programming tests complete but verification testing not begun; software online with the controller; controller safety-unlocked; no safety forces or pending online safety edits; safety task status OK. With firmware revision 37 or earlier the controller must be in Program/Remote Program mode; with revision 38 or later it can be in Remote Run, Program/Remote Program, or Remote Test (1756-RM012, pp.67-68).
  2. Generate it from the Safety tab of the Controller Properties (click Generate), from Tools → Safety → Generate Signature, or from the Safety Status menu (1756-RM012, p.68).
  3. Record it. Manually record the safety signature after initial creation, and check it after every download to confirm it matches (1756-RM012, p.68). Click the ellipsis next to the ID to view and copy all 64 characters (1756-RM012, p.68).
  4. Safety-lock the controller (recommended). Safety-locking helps protect safety components from modification and the signature from accidental deletion, but it is not a SIL 2 or SIL 3 requirement and does not by itself satisfy them (1756-RM012, p.71). Safety-lock and unlock are on the Safety tab of the Controller Properties or Tools → Safety → Safety Lock/Unlock (1756-RM012, p.71).
Changing a Signed Safety Program While a safety signature exists, online or offline programming or editing of the safety portion, forcing safety I/O, and changing the inhibit state of safety I/O are not permitted (1756-RM012, p.68). Online edits of safety logic require the controller to be safety-unlocked and unsigned (1756-RM012, p.76). After you edit the safety program, revalidate all affected elements of the application, as determined by your impact analysis, before you resume operation (1756-RM012, p.76), then generate a new signature.

10. System Reaction Time

The system reaction time is the worst-case time from a safety-related event, input to the system or a fault within it, until the system is in the safe state (1756-RM012, p.12). It is the sum of the reaction times of every component in the chain (1756-RM012, p.103):

System reaction time = Sensor reaction time + Logix system reaction time + Actuator reaction time

For a simple input-logic-output chain, the Logix system reaction time is made of five parts (1756-RM012, pp.103-104):

ItemComponentHow to get it
ASafety input device reaction time plus input delay time5069-IB8S safety reaction time is 6 ms; input delay 0–50 ms, default 0 (5069-TD001, p.38)
BSafety input connection reaction time limit (CRTL)Input RPI × (timeout multiplier + network delay multiplier); read it from the module's Safety page. Defaults (RPI 10 ms, timeout multiplier 2, network delay multiplier 200%) give 40 ms (1756-RM012, pp.101-102)
CController (safety task) reaction time(Safety task period + safety task watchdog) × 1.01; the multiplier covers clock drift (1756-RM012, p.103)
DSafety output connection reaction time limitSafety task period × (timeout multiplier + network delay multiplier − 1); read it from the module's Safety page (1756-RM012, p.102)
ESafety output device reaction time5069-OBV8S safety reaction time is 4.5 ms (5069-TD001, p.42)

Example Calculation

Assume default connection settings, input delay 0 ms, and a safety task period and watchdog that you have set to 10 ms each (example values, not defaults):

ComponentValue
A: IB8S reaction time + input delay6 ms + 0 ms = 6 ms
B: input CRTL (defaults)10 ms × (2 + 2) = 40 ms
C: (period + watchdog) × 1.01(10 + 10) × 1.01 = 20.2 ms
D: output CRTL (defaults)10 ms × (2 + 2 − 1) = 30 ms
E: OBV8S reaction time4.5 ms
Logix system reaction time100.7 ms

Add the E-Stop's own reaction time and the contactor's release time (from their manufacturers' data) to get the system reaction time. 5069-TD001, p.42 also lists a 4 ms maximum output delay time (backplane to screw) for the OBV8S; if you are not sure it is included in the 4.5 ms reaction time, add it for a conservative figure (104.7 ms in this example). Any input delay you configure must be counted in the system reaction time (1756-RM012, p.32), and if you raise the connection reaction time limits to avoid connection loss, use the new limits in the calculation (1756-RM012, p.101).

The Network Settings Dominate In this example the two connection reaction time limits (70 ms together) are larger than every other term. They depend on the RPI, the timeout multiplier and the network delay multiplier (1756-RM012, p.106). Do not set the timeout multiplier below 2 for any safety connection (1756-RM012, p.101), and use caution when reducing either multiplier, because lower values increase the likelihood of false trips (1756-RM012, p.108).

11. Troubleshooting

SymptomMeaningResolution
Safety input I/O indicator flashing red; Ptxx.ShortCircuit = 1A short circuit condition exists on the input (5069-UM004, pp.58 and 115)Locate and correct the short (for example both channels fed from the same test output, or a field wire touching 24V). Then recover: remove the cause, place the affected inputs into the safe state, and let the Input Error Latch Time elapse (5069-UM004, p.74).
Ptxx.Data = 0 and Ptxx.Fault = 1 after an internal discrepancyThe IB8S internal signals for that input disagreed for longer than the Transition Time Limit; there is no separate discrepancy bit, only Fault = 1 (5069-UM004, pp.77-78)Reset the module, that is, cycle power to it (5069-UM004, p.78).
DCS reports a discrepancy between channel A and BThe instruction's fault codes identify channel-specific discrepancy and whether it was a delay or a change of state on one channel (1756-RM012, p.34)Fault Code 16#4000 / 16#4001: the channels disagreed for longer than the Discrepancy Time (16#4000 = A active, B safe; 16#4001 = A safe, B active). 16#4002 / 16#4003: Channel A / Channel B went to the safe state and back while the other stayed active (1756-RM095, pp.92-93). Check the wiring and E-Stop contacts, press and release the E-Stop so both channels pass through the safe state, then toggle Reset OFF to ON. After a discrepancy fault, O1 cannot energize until the inputs have cycled through the safe state (1756-RM095, pp.91-92).
Test output fault, I/O indicator flashing or steady redTestxx.ShortCircuit = 1 for a short; overload at ≥ 0.7 A or a short to ground (5069-UM004, pp.56-57)Remove the load or the connection to ground. After the condition is corrected and the test output is in the safe state, it recovers after 10 s or the Input Error Latch Time, whichever is longer (5069-UM004, p.57).
SA indicator off, all IB8S I/O indicators steady red, Testxx.FieldPowerOff = 1Field (SA) power lost on that SA power bus (5069-UM004, p.55)Reapply field power. Recovery can take an additional 1 s after the Input Error Latch Time (5069-UM004, p.55). IB8S SA power is 18–32V DC (5069-TD001, p.38).
Safety output turned off and stays offA fault was detected on the output; outputs stay off until the cause is removed and the outputs are commanded to the safe state (5069-TD001, p.42; 5069-UM004, p.83)Remove the cause, command the output to the safe state (for example set Ptxx.Data to 0), and let the Output Error Latch Time elapse; allow up to 1 s more (5069-UM004, p.83). After a short to 24V DC, cycle module power to reset the diagnostic (5069-UM004, p.63).
Safety output I/O indicator flashing red while offNo Load (load draws less than 10 mA, detected when the output has been off for at least 250 ms) or a short circuit (5069-UM004, pp.62 and 115)Check the coil wiring to the P terminal and LA–.
Output is on but the contactor does not pull inLA power missing or out of rangeVerify LA+ (terminal 16) and LA– (terminal 17) are connected; LA on-state voltage is 17.5–32V DC; output rating is 1 A per channel (5069-TD001, p.42). Use contactor coils rated for 24V DC.
Module status (MOD) flashing greenNo connection to the controller (missing, incomplete or incorrect configuration), or the Validator has not completed an initial Time Coordination exchange (5069-UM004, p.114)Use the Studio 5000 project to find what is preventing the connection (5069-UM004, p.114).
A previously used safety module will not connectIts configuration is still owned by another controller (5069-UM004, p.40)Reset it to out-of-box: inhibit the connection if it is Local, then Module Properties → Safety → Reset Ownership. This is not possible while a safety signature exists in the project (5069-UM004, pp.40 and 109).
ConnectionFaulted = 1The safety connection is faulted; the safety data is reset to zero (1756-RM012, pp.81-82)Check the module and network. If the default connection reaction time limit causes connection loss, increase it and use the new value in your reaction time calculation (1756-RM012, p.101).
Safety task watchdog faultThe safety task ran longer than its watchdog; this generates a nonrecoverable safety fault (1756-RM012, p.48)The instructions in the safety task set a lower limit for the period and watchdog you can use (1756-RM012, p.105). See the Monitor Safety Status and Handle Faults chapter of 1756-RM012.

Status Indicators (5069-IB8S and 5069-OBV8S)

The IB8S has 1 green/red module status indicator, 1 green/red SA power status indicator and 12 yellow/red I/O status indicators; the OBV8S has 1 module, 1 SA power and 16 I/O status indicators (5069-TD001, pp.38 and 42). Do not use the status indicators for safety operations (5069-UM004, p.37).

IndicatorStateMeaning
MODOffPower is not applied
MODSteady greenConnected to the owner-controller and operating normally
MODFlashing greenNo connection to the controller, or (safety modules) the initial Time Coordination exchange is not complete
MODSteady redNonrecoverable fault: cycle power; if it stays steady red, replace the module
MODFlashing redFirmware update in progress or failed, recoverable fault, or connection timed out
MODFlashing red and green(Safety modules) the UNID is not commissioned
SAOffNo SA power, status unknown, SA power below the valid range, or SA power turned off during a safety critical fault
SASteady greenSA power in the valid range
SASteady redSA power outside the valid range (off, too low or too high)
Safety input I/OOff / steady yellowInput off (or not configured, not enabled, no power) / input on
Safety input I/OFlashing redShort circuit condition
Safety input I/OSteady redField power loss, overload or short to ground on a test output, or another hardware fault
Safety output I/OSteady yellowOutput on and a load was detected in the off state
Safety output I/OFlashing redNo Load while off, or short circuit
Safety output I/OSteady redField power loss, overload, short to ground, or another hardware fault
Safety output I/OFlashing red/yellowNo Load detected while off was not corrected and the output is now on

Source: 5069-UM004, pp.113-115.

12. Related Guides

Explore more Compact 5000 and safety-related guides from PLC Exchange:

GuideDescription
5069-IB16 Digital Input Wiring & ConfigurationThe standard (non-safety) 16-channel digital input module: sink wiring, input filters, and ladder logic for the Compact 5000 platform.
5069-RTB Terminal Block Selection GuideHow to select the correct RTB for 5069-series modules and controllers, including the 5069-RTB18 used with the safety I/O modules.
5069-AENTR EtherNet/IP AdapterSetting up remote Compact 5000 I/O over EtherNet/IP, relevant if your safety I/O sits in a remote system.

Reference Documentation

The following Rockwell Automation publications were used as references for this guide. These are the official manufacturer documents for the hardware covered in this article.

PublicationDescriptionDownload
5069-TD001Compact 5000 I/O Modules and EtherNet/IP Adapters Technical Data (5069-TD001P, September 2024)PDF
5069-UM004Compact 5000 I/O Digital Modules User Manual, covering the 5069-IB8S and 5069-OBV8S safety modules (5069-UM004H, March 2026)PDF
1756-RM012GuardLogix 5580 and Compact GuardLogix 5380 Controller Systems Safety Reference Manual (1756-RM012J, September 2025)–
5069-UM001CompactLogix 5380 and Compact GuardLogix 5380 Controllers User Manual (5069-UM001N, January 2026)–
5069-TD002CompactLogix 5380, Compact GuardLogix 5380, and CompactLogix 5480 Controllers Specifications Technical DataPDF
5069-IN0205069-IB8S, 5069-IB8SK Safety Sinking Input Modules Installation Instructions (5069-IN020E, October 2024)–
5069-IN0215069-OBV8S, 5069-OBV8SK Safety Sourcing Output Modules Installation Instructions (5069-IN021D, October 2024)–
1756-RM095Logix 5000 Controller Safety Application Instruction Set Reference Manual, DCS and CROUT operands (1756-RM095O, September 2025)–

Shop the CompactLogix / GuardLogix 5380 Range

Safety-integrated CompactLogix 5380 controllers and accessories.

View all CompactLogix 5380 products →

Need Safety I/O for Your Compact GuardLogix System?

PLC Exchange stocks the 5069-IB8S safety input module, 5069-OBV8S safety output module, and Compact GuardLogix 5380 controllers with a 2.5-year warranty and same-day shipping.