Allen-Bradley Studio 5000 Tutorial: First ControlLogix Project

Studio 5000 Logix Designer is the Rockwell Automation (Allen-Bradley) software for programming the Logix 5000 family, including ControlLogix and CompactLogix. A first project follows a clear sequence: create the project for your controller, add the I/O modules, create tags, write a ladder routine, then download and monitor it. This tutorial builds a pump control with a latched high-level alarm, and explains how Rockwell's tag-based model differs from Siemens' data-block approach.

What do you need to follow a Studio 5000 tutorial?

You need the software and either a controller or an emulator, and the cheapest route is an emulator or a Micro800 trial setup. Logix Designer is licensed software: Rockwell's product page refers to an ordering guide and subscription options, so check licensing with your employer, distributor or Rockwell sales contact. We could not find a free trial of Logix Designer on the Rockwell pages we reviewed, so this tutorial does not assume one.

For practice without hardware, Rockwell's FactoryTalk Logix Echo emulates ControlLogix 5580 and 5590, GuardLogix 5580, CompactLogix 5380 and Compact GuardLogix 5380 controllers. Rockwell's page describes a 30-day trial that needs an account and sign-in, and limits online trial requests. The older Studio 5000 Logix Emulate is listed as a separate product, and Rockwell's documentation notes that Logix Designer v37 and later no longer support emulated 5560 and 5570 controllers. For the smaller Micro800 range you use Connected Components Workbench, whose Standard Edition Rockwell describes as free to download, with a demo version of the Micro800 Simulator; the workflow is similar to Studio 5000.

Version-wise, the Studio 5000 Logix Designer product page says the ControlLogix 5590 was added in version 38. Match the Logix Designer version to the controller firmware you are using.

How is a Studio 5000 project organised?

A Logix project is organised as tasks, programs and routines, and data lives in tags rather than in data blocks. Rockwell's documentation lists three task types: continuous, periodic and event. A project does not need a continuous task and can have only one. A periodic task runs at a set interval (0.1 ms up to 2,000,000 ms, default 10 ms) and interrupts lower-priority tasks. A ControlLogix 5580 supports up to 32 tasks, and periodic and event tasks take priorities from 1 (highest) to 15 (lowest), with the continuous task lowest of all. Each task holds programs, and each program holds routines written in ladder, function block, structured text or sequential function chart.

Tags are the unit of memory. Rockwell defines a tag as a named area of controller memory used to allocate memory, reference data from logic and monitor data. Controller-scoped tags are visible to every routine; program-scoped tags are visible only inside one program. A base tag allocates memory, and an alias tag points at memory defined by another tag, which lets you write logic with descriptive names and map them to real I/O points later.

How do you create and configure the project?

Create the project for your controller, add I/O modules, and let Studio 5000 generate the tags.

1. Open Logix Designer and create a new project. Choose the controller type (for example a ControlLogix or CompactLogix model) and the revision that matches your controller's firmware.
2. Name the project and choose where to save it.
3. In the Controller Organizer, add I/O modules under I/O Configuration, for example a 16-point 24 V DC input module and a 16-point output module, and name them DI01 and DO01.
4. Studio 5000 creates the I/O tags for each module automatically. Rockwell's help explains that module tags are named with :I for input, :O for output and :C for configuration data, and that all I/O tags are controller scoped. An input point therefore appears as a tag such as DI01:I.Data.0.
5. Open the tag editor and create the tags below, using aliases to connect names to I/O points.

How do you write the ladder routine?

Write three short rungs: a seal-in start-stop, a latched high-level alarm, and the beacon output. Create a new ladder routine in your program (for example PumpControl) and call it from the main routine with a JSR instruction.

Rockwell's instruction reference defines the core bit instructions. XIC (examine if closed) sets its rung condition true when the tested bit is true, and XIO (examine if open) does the opposite. OTE (output energise) sets the bit true when the rung is true and clears it when the rung goes false; Rockwell also notes that OTE clears its bit at prescan and postscan.

• Rung 1 (pump seal-in): XIC Start_PB in parallel with XIC Pump_Running, in series with XIC Stop_PB, then OTE Pump_Running.
• Rung 2 (set the alarm): GEQ with Source A Tank_Level and Source B High_Level_SP, then OTL High_Level_Alarm.
• Rung 3 (reset the alarm): XIC Alarm_Reset_PB in series with LES comparing Tank_Level to High_Level_SP, then OTU High_Level_Alarm.
• Rung 4 (beacon): XIC High_Level_Alarm, then OTE Alarm_Light.

Notice that Stop_PB is examined with XIC. The stop button is wired normally closed, so the input is true when the button is healthy, and examining it with XIC makes a broken wire stop the pump. Many older tutorials get this backwards. Also notice the alarm uses OTL and OTU (latch and unlatch) so the alarm stays until reset, while the beacon uses OTE so it simply follows the alarm bit. Our ladder logic tutorial covers these instructions in more detail.

How do you download and monitor the project?

Verify the routine, put the controller in Program mode, download, then switch to Run and watch the tags online. Check the project for errors before you download, because a clean verify is the quickest way to catch a typo. Once online, use the tag monitor to watch values and test inputs safely. Only force I/O on equipment where it is safe to do so and where your site procedures allow it, because a forced value overrides the real signal.

What are Add-On Instructions, and why use them?

An Add-On Instruction packages commonly used logic as a single reusable instruction. Rockwell states that AOIs promote reuse and consistency, can be written in ladder, function block diagram and structured text, and can be used from any routine. They also support source protection, so a user can be limited to read-only access or denied access to the internal logic and local tags. Build one AOI for a standard pump or valve and reuse it across the project; it is the Rockwell counterpart to a Siemens function block. Our PLC programme structure guide covers modular design.

Is Allen-Bradley worth learning in the UK?

It is worth learning if your target employers use Rockwell, and the job data suggests demand is real. According to ITJobsWatch, UK permanent adverts citing Allen-Bradley numbered 155 in the six months to 21 October 2026, against 50 in the same period of 2025, with a median salary of £52,500 based on 117 quoted salaries. ITJobsWatch is an IT-focused index and the page warns that its figures reflect the general labour market, so treat them as indicative. Most UK engineers eventually meet both Siemens and Rockwell, and our comparison Siemens vs Allen-Bradley helps you choose where to start. You can follow along for free with the Allen-Bradley Studio 5000 course.

How EDWartens can help

The EDWartens UK Professional Module is Siemens TIA Portal training, not Allen-Bradley: a five-day live online class (certificate states V17) covering ladder logic, HMI and WinCC SCADA, followed by 68 self-paced Basic Engineering modules and career support. It costs £2,140 + VAT (£2,568), with a £100 deposit option and a maximum of 10 learners per cohort, and the CPD certificate is not a regulated qualification. Because the programming concepts (scan cycle, contacts, timers, structured code) transfer, many learners start with Siemens and add Rockwell later. Rockwell practice is available in the free course linked above, and you can sign up for Siemens training.