CompactLogix 5069-L306ER: First-Time Setup, I/O Wiring, and Basic Program
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 ladder logic example, and network setup.
Contents
1. Hardware Overview
The catalog number breaks down as follows:
| Code | Meaning | Value |
|---|---|---|
| 5069 | Platform | Compact 5000 — high-speed I/O bus |
| L3 | Controller family | CompactLogix — standard control, no embedded Windows |
| 06 | Memory | 6 MB user program memory |
| ER | Comms | Dual embedded EtherNet/IP ports (linear / DLR capable) |
The system mounts on a standard 35mm DIN rail. Left to right, the assembly order is always: Power Supply → Controller → I/O Modules. The modules connect via a direct side-bus — there is no backplane to route wiring through, which is a significant difference from the older 1769 CompactLogix platform.
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: If you have a working 1769 Compact I/O rack you want to retain, you don't have to abandon it. Add a 1769-AENT EtherNet/IP adapter to the right end of the existing 1769 rack. This converts the rack into a remote I/O node on your EtherNet/IP network, accessible from the 5069-L306ER just like any other remote adapter. In Studio 5000, add the 1769-AENT under your Ethernet module in the I/O tree and the existing 1769 modules appear as remote I/O slots — no rewiring required. This is a cost-effective migration path when a full I/O replacement isn't justified.
Reusing existing 1769 I/O: If you have a working 1769 Compact I/O rack you want to retain, you don't have to abandon it. Add a 1769-AENT EtherNet/IP adapter to the right end of the existing 1769 rack. This converts the rack into a remote I/O node on your EtherNet/IP network, accessible from the 5069-L306ER just like any other remote adapter. In Studio 5000, add the 1769-AENT under your Ethernet module in the I/O tree and the existing 1769 modules appear as remote I/O slots — no rewiring required. This is a cost-effective migration path when a full I/O replacement isn't justified.
2. Power Wiring
The 5069-L306ER controller itself is powered by the 5069 power supply module — it does not have its own power connector. Select the right power supply for your panel voltage:
| Catalog Number | Input | Output | Use Case |
|---|---|---|---|
| 5069-PA2 | 120/240V AC | 24V DC, 2A | Panels with AC distribution — most common |
| 5069-PA3 | 120/240V AC | 24V DC, 3A | Same as PA2 but more I/O current capacity |
| 5069-PD1 | 18–32V DC | 24V DC bus | Panels already supplied with 24VDC |
Power Supply Wiring (PA2 / PA3)
| Terminal | Function | Notes |
|---|---|---|
| L1 | AC Line (Hot) | 120V or 240V AC from panel breaker |
| L2 / N | AC Neutral | Neutral on 120V systems; L2 on 240V |
| ⏚ GND | Chassis Ground | Bond to panel ground bus — required for noise immunity |
| OK LED | Status indicator | Green = power good; off or red = fault |
I/O Power vs. Logic Power
The 5069 power supply powers the controller and I/O module logic. Field device power (24VDC for sensors, outputs) is typically provided by a separate 24VDC power supply wired directly to the I/O module field terminals. This keeps field faults isolated from the controller bus.
3. Common 5069 I/O Modules
5069 I/O modules snap onto the right side of the controller (or previous I/O module) and register automatically in the I/O tree when the controller powers up. Common modules for machine and process control:
5069-IB16
16-point 24VDC digital input, sink/source compatible. 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-IB6XOB8
Combination: 6 DI + 8 DO. Efficient footprint for smaller I/O counts — saves a slot vs. separate DI and DO modules.
5069-OW8I
8-point relay output (isolated). Use for 120/240V AC loads, motor starters, or any load that needs dry contact isolation.
Maximum Local I/O
The 5069-L306ER supports up to 16 local 5069 I/O modules on the I/O bus. Additional I/O can be added over EtherNet/IP using remote adapter modules (5069-AEN2TR for DLR networks).
4. Studio 5000 Project Setup
Requires Studio 5000 Logix Designer v32.00 or later for full 5069 platform support. If your version is older, update via the Rockwell Activation Center.
- Open Studio 5000 Logix Designer → New Project
- In the controller browser, expand CompactLogix 5380 → select 5069-L306ER
- Enter a project name (e.g.
Pump_Station_1) and select your firmware revision — match the revision to the firmware currently on the controller - Choose a save location and click Next
- On the Tasks screen, the default MainTask → MainProgram → MainRoutine structure is created automatically — this is fine for most applications
- 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
- In the controller organizer (left panel), expand I/O Configuration → [your controller]
- Right-click the controller node → New Module
- Search for your module (e.g.
5069-IB16) → select it → click Create - Set the Slot number to match the physical position (slot 1 = first module right of controller, etc.)
- Set the RPI (Requested Packet Interval) — default 2 ms is fine for most applications; increase to 5–10 ms for non-time-critical I/O to reduce network load
- For analog modules (5069-IF8 / 5069-OF8): in the Module Definition, configure each channel's signal type (voltage / current) and range
- Repeat for all I/O modules in your system
- Save the project (Ctrl+S)
Once modules are added, Studio 5000 automatically creates tag aliases for all I/O points:
| Tag Pattern | Example | Description |
|---|---|---|
Local:<slot>:I.Ptxx.Data | Local:1:I.Pt00.Data | Digital input, slot 1, point 0 |
Local:<slot>:O.Ptxx.Data | Local:2:O.Pt03.Data | Digital output, slot 2, point 3 |
Local:<slot>:I.Ch<n>Data | Local:3:I.Ch0Data | Analog input channel 0 raw value |
Local:<slot>:O.Ch<n>Data | Local:4:O.Ch0Data | Analog output channel 0 value |
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 ladder logic far easier to read and troubleshoot than raw I/O addresses.
6. Basic Ladder Logic Program — 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)
// ─────────────────────────────────────────────────────────────────────────────
// Rung 1 — 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 2 — Fault latch (OL trips while running)
IF Motor_Run AND NOT OL_OK THEN
Motor_Fault := 1;
END_IF;
IF PB_FaultReset THEN
Motor_Fault := 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 Device | Type | Module | Terminal | Notes |
|---|---|---|---|---|
| Start PB (green) | NO momentary | 5069-IB16, Slot 1 | Input 0 + Common | Wired to 24VDC and input point |
| Stop PB (red) | NC momentary | 5069-IB16, Slot 1 | Input 1 + Common | NC wiring provides fail-safe stop on wire break |
| OL Relay (95-96) | NC contact | 5069-IB16, Slot 1 | Input 2 + Common | NC = normal; opens on overload trip |
| Motor Contactor | 24VDC coil | 5069-OB16, Slot 2 | Output 0 + 24V | Use 5069-OW8I relay module for 120V AC contactor coils |
| Run Pilot (green) | 24VDC LED | 5069-OB16, Slot 2 | Output 1 + 24V | — |
| Fault Pilot (red) | 24VDC LED | 5069-OB16, Slot 2 | Output 2 + 24V | — |
7. EtherNet/IP Network Setup
The 5069-L306ER has two EtherNet/IP ports (Port 1 and Port 2) that can operate in three topologies:
| Topology | How to Wire | Best For |
|---|---|---|
| Star | Both ports connect to managed switch independently | Most common; use Port 1 for SCADA/HMI, Port 2 for drives/I/O |
| Linear / Daisy-chain | Port 1 → upstream device; Port 2 → next device in chain | Small systems with no managed switch; eliminates switch cost |
| DLR (Device Level Ring) | Form a ring — last device Port 2 connects back to controller Port 1 | Fault-tolerant networks; ring heals in <3ms on cable break |
Setting the Controller IP Address
- Connect the controller to your PC via an Ethernet cable
- Open RSLinx Classic → Configure Drivers → add an EtherNet/IP Driver on your PC's network adapter
- In RSLinx, browse to find the controller (it will appear with its default BOOTP address or factory default
192.168.1.1) - Right-click the controller → Module Configuration → Port Configuration tab
- Disable BOOTP and enter your static IP, subnet mask, and gateway
- Click Set — the controller stores the IP in non-volatile memory
- Alternatively, set the IP inside the Studio 5000 project: right-click the controller in the I/O tree → Properties → Internet Protocol tab, then download
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
- In Studio 5000, go to Communications → Who Active (Ctrl+W) — browse to find your controller by IP address
- Right-click the controller → Set Project Path — this tells Studio 5000 which physical controller to communicate with
- Click Controller → Download (Ctrl+D) — Studio 5000 will warn if the project revision differs from the firmware; resolve before continuing
- On the download dialog, select Go to Remote Run to put the controller in Run mode after the download completes
- Click Download — the program transfers and the controller starts executing
- Press Ctrl+W again and select Go Online (or Controller → Go Online) to connect in monitoring mode
- Verify I/O: in the I/O tree, all modules should show a green circle. Open the Ladder Diagram — inputs are shown with their live state highlighted in green when energized
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) connects to the 5069-L306ER over EtherNet/IP. In FactoryTalk View Studio ME:
- In your FactoryTalk View ME project, go to RSLinx Enterprise → Communication Setup
- Add an EtherNet/IP shortcut — enter the controller's IP address
- Name the shortcut (e.g.
PLC) — this prefix is used in all HMI tag addresses - To reference a PLC tag from an HMI object, use the format:
[PLC]Motor_Run - Download the FactoryTalk View project to the PanelView via USB or FTP, and the HMI will connect to the PLC on power-up
10. Common Setup Errors
| Error / Symptom | Likely Cause | Resolution |
|---|---|---|
| Module faulted (yellow ⚠ in I/O tree) | Physical module not present or wrong slot number in project | Verify slot numbers match physical assembly; check module is fully seated |
| Download fails — revision mismatch | Project firmware rev differs from controller firmware | Update project revision: Controller Properties → General → change revision to match |
| Can't find controller in RSLinx | IP address mismatch or PC on different subnet | Confirm PC is on same subnet; try ping to controller IP; check Ethernet cable |
| Outputs won't energize in Run mode | I/O module inhibited or program not reaching output rung | Check for inhibited modules (I/O tree → right-click → Uninhibit); force tags offline to test |
| Analog input reading 0 or -32768 | Channel not configured for correct signal type | In 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 fault | Go online → Controller Diagnostics → Major Faults tab — read the fault code and clear after resolving root cause |
| PanelView can't connect to PLC | RSLinx Enterprise shortcut wrong IP or HMI on different VLAN | Verify shortcut IP; ping PLC from HMI terminal (Diagnostics → Shell → ping); 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.
| Publication | Description | Download |
|---|---|---|
| 5069-UM004 | Compact 5000 Digital I/O Modules User Manual | |
| 5069-UM005 | Compact 5000 Analog I/O Modules User Manual | |
| 5069-TD001 | Compact 5000 I/O Technical Data |
Shop the CompactLogix 5380 (5069-L) Range
Every CompactLogix 5380 controller variant from stock with matching communication modules.
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.