How-To Guide

CompactLogix 5069-L306ER: First-Time Setup & Basic Program

Hardware assembly, power wiring, I/O module configuration in Studio 5000, a motor start/stop Structured Text example, EtherNet/IP network setup, and PanelView HMI connection.

Get a Quote for the 5069-L306ER
0.6 MB User Memory
2-Port EtherNet/IP (DLR)
5069 Compact 5000 I/O
Studio 5000 Logix Designer

How-To Guide  ·  Allen-Bradley CompactLogix  ·  PLC Setup & Programming

CompactLogix 5069-L306ER: First-Time Setup, I/O Wiring, and Basic Program

Part Number: 5069-L306ER  ·  Compact 5000 Platform  ·  Dual EtherNet/IP  ·  Studio 5000 Logix Designer

The 5069-L306ER is a CompactLogix controller in Rockwell's Compact 5000 platform — the current-generation mid-range PLC paired with the high-speed 5069 I/O system. Its dual EtherNet/IP ports support linear, star, and Device Level Ring (DLR) network topologies, making it a solid choice for machine control, pump stations, and process skids. This guide walks through hardware setup, power wiring, I/O module configuration in Studio 5000, a practical Structured Text example, and network setup.

1. Hardware Overview

The catalog number breaks down as follows:

CodeMeaningValue
5069PlatformCompact 5000 — high-speed I/O bus
L3Controller familyCompactLogix 5380 -- standard control
06Memory0.6 MB user memory
ERCommsDual embedded EtherNet/IP ports (linear / DLR capable)

The system mounts horizontally on an EN50022 35 x 7.5 mm DIN rail (zinc-plated, chromate-passivated steel), which also grounds it. Left to right: Controller → I/O Modules → End Cap. The controller is always the leftmost component, and the end cap must be installed on the right side of the last module before power-up. There is no separate power-supply module: the modules interlock side by side and pass MOD power and SA power along the bus from module to module.

Compact 5000 vs. Compact 5370 — Key Differences If you're migrating from a 1769-L3x CompactLogix, note that the 5069 platform uses entirely different I/O modules. 1769 modules do not work on the 5069 I/O bus and vice versa. The controller firmware and Studio 5000 project files are also not interchangeable.

Reusing existing 1769 I/O: Compact I/O can still serve as distributed I/O for a CompactLogix 5380 controller over EtherNet/IP. Replace the 1769 controller in the existing bank with a 1769-AENTR EtherNet/IP adapter (see the 1769-AENTR installation instructions for placement and power), then add the adapter and its modules under the controller's Ethernet port in the I/O Configuration tree. The bank becomes a remote I/O node for the 5069-L306ER. This is a cost-effective migration path when a full I/O replacement isn't justified.

2. Power Wiring

The 5069-L306ER has no embedded power supply and there is no 5069 power-supply module. The controller distributes power to the system through two removable terminal blocks (RTBs) on the controller, each wired to an external power supply. Order the RTBs separately, individually or as a 5069-RTB64-SCREW / 5069-RTB64-SPRING kit (4-pin and 6-pin).

Power TypeRTBSuppliesLimit
MOD power (system side)4-pin, 5069-RTB4-SCREW or -SPRINGOperates the controller and the I/O module electronics; passed across the MOD power bus10 A max continuous at 18–32V DC
SA power (field side)6-pin, 5069-RTB6-SCREW or -SPRINGPowers field-side devices; passed across the SA power bus10 A max at 18–32V DC, or 10 A max at 18–240V AC; source must be SELV/PELV

MOD Power RTB Wiring (5069-RTB4)

TerminalConnectionNotes
24V(+) (x2)24V DC(+) from the external MOD power supply, to the first 24V DC(+) terminalPut any power switch or other power control device on this VDC+ side. On the VDC- side the controller can fail to power up or down properly.
24V(-) (x2)24V DC(-) from the external MOD power supply, to the first 24V DC(-) terminalJumpers are not included with the RTBs

SA Power RTB Wiring (5069-RTB6)

TerminalDC SA PowerAC SA Power
DC(+) or L1/AC(+) (x2)DC(+) to the first DC(+) terminalL1/AC(+) to the first L1/AC(+) terminal
DC(-) or L2/N/AC(-) (x2)DC(-) to the first DC(-) terminalL2/N/AC(-) to the first L2/N/AC(-) terminal
Earth GroundWire to the first Earth Ground terminal from the SA supply, the DIN rail, or another earth ground point. This connection is required.

Strip 12 mm (0.47 in) for screw RTBs or 10 mm (0.39 in) for spring RTBs; torque screw terminals to 0.4 N•m (3.5 lb•in). Turn on MOD and SA power only after the end cap is installed on the last module.

Use Separate Supplies for MOD and SA Power One external supply can feed both RTBs, but Rockwell strongly recommends separate supplies: if SA power is lost, MOD power stays up for the Compact 5000 I/O modules. The SA supply type (DC or AC) must match the I/O modules on that SA bus. Use a 5069-FPD field potential distributor to start an additional SA power bus or to change the SA power type.
No RIUP The controller and its RTBs do not support Removal and Insertion Under Power. Remove MOD and SA power before installing or removing the controller, the RTBs, or field wiring.

3. Common 5069 I/O Modules

Compact 5000 I/O modules install to the right of the controller (or the previous I/O module). Each module must then be added to the I/O Configuration tree in the project, either with New Module or, while online, with Discover Modules. Common modules for machine and process control:

5069-IB16

16-point 24V DC sinking input (use sourcing / PNP field devices). Use for pushbuttons, limit switches, proximity sensors, relay contacts.

5069-OB16

16-point 24VDC digital output, sourcing. Use for pilot lights, relay coils, solenoid valves (via relay interface).

5069-IF8

8-channel analog input, ±10V / 0–10V / 0–20mA / 4–20mA per channel. Use for pressure transmitters, flow meters, temperature (via transmitter).

5069-OF8

8-channel analog output, 0–10V / 4–20mA. Use for drive speed references, control valves, current-to-pressure transducers.

5069-OW16

16-point normally-open relay output.

5069-OW4I

4-point isolated, normally-open (Form A) relay output, 5–264V AC / 5–125V DC, 2 A per channel. Use for 120/240V AC loads, contactor coils, or any load that needs isolated dry contacts.

Maximum Local I/O The 5069-L306ER supports up to 8 local Compact 5000 I/O modules. Add more I/O over EtherNet/IP with a remote adapter (5069-AENTR or 5069-AEN2TR; both support DLR).

4. Studio 5000 Project Setup

Requires Studio 5000 Logix Designer v28 or later (v29 or later for Dual-IP mode).

  1. Open Studio 5000 Logix Designer → New Project
  2. In the controller browser, expand CompactLogix 5380 → select 5069-L306ER
  3. Enter a project name (e.g. Pump_Station_1) and select your firmware revision — match the revision to the firmware currently on the controller
  4. Choose a save location and click Next
  5. On the Tasks screen, the default MainTask → MainProgram → MainRoutine structure is created automatically — this is fine for most applications
  6. Click Finish — the project opens with the controller in the I/O tree
Firmware Revision Must Match If the project revision does not match the physical controller's firmware, the download will fail. To check the controller's firmware: in RSLinx Classic, right-click the controller and select Device Properties. The revision is shown in the General tab.

5. Configuring Local I/O in the Project Tree

  1. In the controller organizer (left panel), expand I/O Configuration → [your controller]
  2. Right-click the controller node → New Module
  3. Search for your module (e.g. 5069-IB16) → select it → click Create
  4. Set the Slot number to match the physical position (slot 1 = first module right of controller, etc.)
  5. Set the RPI (Requested Packet Interval). Valid values for standard Compact 5000 I/O modules are 0.2–750 ms; choose a rate no faster than the application needs
  6. For analog modules (5069-IF8 / 5069-OF8): in the Module Definition, configure each channel's signal type (voltage / current) and range
  7. Repeat for all I/O modules in your system
  8. Save the project (Ctrl+S)

Once modules are added, Studio 5000 creates module-defined tags for all I/O points:

Tag PatternExampleDescription
Local:<slot>:I.Ptxx.DataLocal:1:I.Pt00.DataDigital input, slot 1, point 0
Local:<slot>:O.Ptxx.DataLocal:2:O.Pt03.DataDigital output, slot 2, point 3
Local:<slot>:I.Chxx.DataLocal:3:I.Ch00.DataAnalog input channel 0 (REAL, IEEE 32-bit floating point, scaled units)
Local:<slot>:O.Chxx.DataLocal:4:O.Ch00.DataAnalog output channel 0 value (REAL)
Create Aliases for Readability Right-click any I/O tag in the Tag Database → New Alias. Naming tags like PB_Start, PB_Stop, Motor_Run makes logic far easier to read and troubleshoot than raw I/O addresses.

6. Basic Program (Structured Text) -- Motor Start/Stop

The following Structured Text shows the equivalent of a classic hardwired motor control circuit: a normally open Start button, normally closed Stop button, seal-in contact, and overload relay interlock. This pattern is the foundation for virtually every motor in a PLC program.

// ── Motor_1 Start/Stop Routine ─────────────────────────────────────────────── // Aliases assumed (define these in the Tag Database): // PB_Start → Local:1:I.Pt00.Data (NO momentary pushbutton) // PB_Stop → Local:1:I.Pt01.Data (NC momentary pushbutton — wired NC) // OL_OK → Local:1:I.Pt02.Data (NC contact from motor overload relay) // Motor_Run → Local:2:O.Pt00.Data (Motor contactor coil output) // Pilot_Run → Local:2:O.Pt01.Data (Green run indicator light) // Pilot_Fault → Local:2:O.Pt02.Data (Red fault indicator light) // PB_FaultReset → Local:1:I.Pt03.Data (NO momentary fault-reset pushbutton) // Motor_Fault → BOOL internal tag (latched overload fault) // ───────────────────────────────────────────────────────────────────────────── // Rung 1 -- Fault latch (OL trips while running). Evaluated first so // Motor_Run still holds last scan's state when OL_OK drops. IF Motor_Run AND NOT OL_OK THEN Motor_Fault := 1; END_IF; IF PB_FaultReset AND OL_OK THEN Motor_Fault := 0; END_IF; // Rung 2 -- Start/Stop seal-in circuit IF (PB_Start OR Motor_Run) AND PB_Stop AND OL_OK AND NOT Motor_Fault THEN Motor_Run := 1; ELSE Motor_Run := 0; END_IF; // Rung 3 — Pilot lights Pilot_Run := Motor_Run; Pilot_Fault := Motor_Fault;

Wiring the Pushbuttons and Outputs to 5069-IB16 / 5069-OB16

Field DeviceTypeModuleTerminalNotes
Start PB (green)NO momentary5069-IB16, Slot 1Input 0 + CommonWired to 24VDC and input point
Stop PB (red)NC momentary5069-IB16, Slot 1Input 1 + CommonNC wiring provides fail-safe stop on wire break
OL Relay (95-96)NC contact5069-IB16, Slot 1Input 2 + CommonNC = normal; opens on overload trip
Fault Reset PBNO momentary5069-IB16, Slot 1Input 3 + CommonClears Motor_Fault once the overload has been reset
Motor Contactor24VDC coil5069-OB16, Slot 2Output 0 + 24VUse a 5069-OW4I or 5069-OW16 relay module for 120V AC contactor coils
Run Pilot (green)24VDC LED5069-OB16, Slot 2Output 1 + 24V—
Fault Pilot (red)24VDC LED5069-OB16, Slot 2Output 2 + 24V—

7. EtherNet/IP Network Setup

The 5069-L306ER has two EtherNet/IP ports (A1 and A2, 10 Mbps / 100 Mbps / 1 Gbps). The controller runs in either Dual-IP mode (each port has its own IP address; the out-of-box setting, Logix Designer v29 or later) or Linear/DLR mode (one IP address for the controller). Supported topologies:

TopologyHow to WireBest For
StarLinear/DLR mode: connect one port to a switch. Dual-IP mode: each port has its own IP address and must be on a different subnetDual-IP example: port A1 to the plant/HMI network, port A2 to an isolated device network. Never cable both ports to the same switch in Linear/DLR mode without DLR configured
Linear / Daisy-chainPort A1 to upstream device; port A2 to next device in chain (Linear/DLR mode)Small systems with no managed switch; eliminates switch cost
DLR (Device Level Ring)Form a ring -- last device connects back to controller port A1 (Linear/DLR mode)Fault-tolerant networks; at least one node must be configured as ring supervisor (the supervisor function is disabled by default)

Setting the Controller IP Address

The controller ships with no IP address, in Dual-IP mode, with each Ethernet port DHCP-enabled. If no DHCP server assigns an address, set it manually. The controller has no rotary switches for addressing.

  1. Pick a tool: the BOOTP DHCP EtherNet/IP Commissioning Tool (v3.02.00 or later), Studio 5000 Logix Designer (v31.00.00 or later), or RSLinx Classic (v4.00.00 or later). Note the MAC ID from the label on the side of the controller
  2. With RSLinx Classic or Logix Designer, connect to the controller through its USB port (temporary connection only, cable no longer than 3.0 m, no hubs)
  3. In Dual-IP mode, assign a unique IP address to port A1 and to port A2 (on different subnets)
  4. If you want a single IP address for a linear or DLR network, use RSLinx Classic to change the controller from Dual-IP mode to Linear/DLR mode, then set the IP address
  5. To return the controller to its out-of-box state (DHCP-enabled, no IP address), perform a Stage 2 Reset
Network Segmentation Best Practice Put your PLC and drives on a dedicated control network VLAN (e.g. 192.168.10.x) separate from your corporate/office network. This prevents broadcast traffic from affecting scan time and keeps unauthorized devices off the control network.

8. Download & Go Online

  1. In Studio 5000, click Who Active (named Network Browser in Logix Designer v38 and later), expand the communication path, and select your controller
  2. Click Set Project Path to store the path in the project, so you do not have to choose it each time you go online
  3. Click Download. Read the warning in the Download dialog box, then click Download again. Logix Designer warns if the project revision differs from the controller firmware; resolve that before continuing
  4. After the download, put the controller in Run or Remote Run mode only when the machine is safe to operate
  5. Click Go Online to monitor the running program
  6. Verify I/O: in the I/O Configuration tree, no module should show a fault or warning icon. Check live input states against the field devices
Run Mode vs. Program Mode In Run mode, outputs are controlled by the PLC program — energize only when safe to do so. Before first download on live equipment, place the controller in Program mode (Controller → Program Mode) and verify I/O wiring with outputs inhibited before switching to Run.

9. Connecting a PanelView HMI

A PanelView Plus 7 (or PanelView 800) terminal communicates with the 5069-L306ER over EtherNet/IP. In the HMI application software, create a communication path (shortcut) that points to the controller's IP address, then reference controller tags such as Motor_Run by name through that shortcut. Follow the HMI software documentation for the exact menu steps and tag syntax for your terminal and software version.

Dual-IP Mode and the HMI In Dual-IP mode the controller has a different IP address on each port. Point the HMI shortcut at the address of the port that is on the HMI's network.

10. Common Setup Errors

Error / SymptomLikely CauseResolution
Module faulted (yellow ⚠ in I/O tree)Physical module not present or wrong slot number in projectVerify slot numbers match physical assembly; check module is fully seated
Download fails — revision mismatchProject firmware rev differs from controller firmwareUpdate project revision: Controller Properties → General → change revision to match
Can't find controller in RSLinxController has no IP address yet (ships DHCP-enabled, no address), or PC is on a different subnetConnect over USB and set the IP address; confirm PC is on the same subnet as the port you are using; try ping to controller IP; check Ethernet cable
Outputs won't energize in Run modeI/O module inhibited or program not reaching output rungCheck for inhibited modules (I/O tree → right-click → Uninhibit); force tags offline to test
Analog input reads 0.0 or channel fault bit (I.Chxx.Fault) setChannel not configured for correct signal typeIn module properties, verify channel is set to 4–20mA or correct voltage range; check field wiring polarity
Controller in faulted state (red LED)Major fault in program or I/O connection faultGo online → Controller Diagnostics → Major Faults tab — read the fault code and clear after resolving root cause
PanelView can't connect to PLCRSLinx Enterprise shortcut wrong IP or HMI on different VLANVerify the shortcut IP matches the controller port on the HMI network; ping the controller from a PC on the same network; check switch/VLAN config

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-UM001CompactLogix 5380 and Compact GuardLogix 5380 Controllers User ManualRockwell publication
5069-IN013CompactLogix 5380 Controllers Installation InstructionsRockwell publication
5069-TD002CompactLogix 5380, Compact GuardLogix 5380, and CompactLogix 5480 Controllers SpecificationsPDF
5069-UM007Compact 5000 EtherNet/IP Adapters User ManualPDF
5069-RM001Compact I/O to Compact 5000 I/O Migration GuideRockwell publication
5069-UM004Compact 5000 Digital I/O Modules User ManualPDF
5069-UM005Compact 5000 Analog I/O Modules User ManualPDF
5069-TD001Compact 5000 I/O Technical DataPDF

Shop the CompactLogix 5380 (5069-L) Range

Every CompactLogix 5380 controller variant from stock with matching communication modules.

View all CompactLogix 5380 products →

Need a 5069-L306ER or Compact 5000 I/O Modules?

PLC Exchange stocks CompactLogix controllers and 5069 I/O with a 2.5-year warranty and same-day shipping. Get pricing in a few hours.