Programmable Logic Controllers (PLCs): An Overview

What is a Programmable Logic Controller?

Let me start with a picture you already know. Imagine walking into a soft-drink bottling factory. Thousands of bottles slide down a conveyor belt. Each bottle stops under a nozzle that fills it with cola, then moves to the next station where a cap is screwed on. Down the line a label is glued, then the bottle is packed into a box. Hundreds of times every minute. All day, every day, without anyone touching a single bottle.

Who is running all of that? Not a person — a person can’t react fast enough or work for 24 hours straight. The answer is a programmable logic controller, or PLC: a small, tough industrial computer designed to control machines and processes in real time.

Unlike the office computer on your desk, a PLC is built tough. It can handle electrical noise from nearby motors, vibration from heavy machinery, dust, humidity, and wide temperature swings. And it works in real time — meaning when an input changes, the PLC reacts within milliseconds, not seconds.

A Short History — Why PLCs Were Invented

Back in the 1960s, factories used relay panels to control machinery. A relay is a small electromechanical switch — flick a coil and a contact moves. To control a complex machine, hundreds of relays were wired together. It worked, but it was a nightmare for two reasons.

First, every time a car factory wanted to change to next year’s model, the entire control panel had to be torn out and rewired. Hundreds of relays, thousands of wires. It took weeks and produced lots of mistakes. Second, relays wear out — every day a few would fail and the whole production line would stop.

In 1968, an engineer named Dick Morley and his team at Bedford Associates designed a small electronic box that could replace those banks of relays. Instead of physical wiring, the control logic was stored in the box’s memory as a program. They called it the Modicon 084 — and it changed industrial automation forever.

Why PLCs Replaced Relay Logic — The Big Advantages

Let’s count the wins. Compared to relay panels, PLCs are:

• More reliable — they’re solid-state. No moving contacts to wear out, no coils to burn, no metal-to-metal sparks.
• More flexible — change the logic by editing software, not by rewiring.
• Much smaller — a PLC the size of a textbook can replace dozens of relays that would fill an entire wall.
• Self-diagnostic — the PLC reports its own faults. “Input module 3 has a problem.” “Battery is low.” It tells you what’s wrong.
• Networkable — PLCs talk to each other and to supervisory computers over industrial networks.
• Fast — a modern PLC scans its entire program in under one millisecond. Faster than a human blink, many times over.
• Easy to troubleshoot — the engineer watches the program execute live on a laptop screen, with energised parts highlighted in green.

A useful rule of thumb: if your control problem needs more than about half a dozen relays, a PLC will be cheaper, smaller, and easier to maintain over the equipment’s lifetime.

What’s Inside a PLC — The Four Parts

Open up any PLC — Allen-Bradley, Siemens, Mitsubishi, Schneider — and you’ll find four basic parts. The brand name on the outside changes, but the four parts inside are always there. Let’s look at them.

1. Power Supply — the part that gives the PLC its electricity. It takes regular plant AC voltage (120 V or 240 V) and converts it to clean low-voltage DC (usually 24 V or 5 V) that the PLC’s electronics can handle. Think of it as the PLC’s heart.
2. Central Processing Unit (CPU) — the brain. Inside the CPU is a microprocessor that reads your program and decides what to do, plus memory that stores the program and the data. The CPU is what makes the PLC “think”.
3. Input/Output (I/O) Section — the eyes and hands. Input modules are the eyes — they read signals from sensors, switches, and buttons. Output modules are the hands — they drive motors, valves, and lamps. The I/O section is how the PLC connects to the real world.
4. Programming Device — the laptop you use to write the program. You type the ladder logic, click “download”, and the program flies into the CPU’s memory through a USB or Ethernet cable. After the download is done, the laptop can be unplugged — the PLC keeps running by itself, forever.

Open vs. Closed Architecture

Most PLCs are proprietary — that means the hardware, software, and communication protocols all belong to one company (Allen-Bradley, Siemens, Mitsubishi, Schneider). This is called closed architecture. The advantage is that everything inside is tightly integrated and well supported by the maker. The disadvantage is that you can’t take an Allen-Bradley I/O card and plug it into a Siemens PLC — they don’t talk to each other.

An open architecture PLC, on the other hand, uses standard parts that work with other vendors’ equipment. These are rare in industry — most PLC ecosystems are closed.

Fixed I/O vs. Modular I/O

PLCs come in two physical layouts. You’ll meet both in the field, so let’s understand the difference.

• Fixed I/O — the CPU and the I/O are sealed inside one box, with a set number of input and output points. It’s cheap, compact, and simple. The downside is you can’t add more I/O later — if you need just one more output, you have to replace the whole unit. You’ll find fixed I/O in nano and micro PLCs, often on smaller machines.
• Modular I/O — the CPU, power supply, and each I/O module are separate cards that slide into a chassis (called a rack). Need 16 more inputs? Plug in another input card. Need analog inputs for a temperature sensor? Plug in an analog card. The cards talk to the CPU through a connector at the back of the rack called the backplane. This is the standard for serious industrial work.

How a PLC Thinks — The Scan Cycle

Now here’s something important — and it confuses a lot of beginners. A PLC does not work like a normal computer program. A normal program runs from top to bottom and then stops. A PLC program runs in a loop that never stops, called the scan cycle.

The scan cycle has four steps that the PLC repeats thousands of times per second, every second, forever — until you turn it off.

1. Read inputs — the CPU takes a “snapshot” of every input terminal. Is the START button pressed? Yes or no. Is the level sensor seeing water? Yes or no. The CPU writes all these answers into a memory table called the input image.
2. Execute the program — the CPU reads your ladder program from top to bottom, one rung at a time. For each rung, it looks at the input image, decides what the output should be, and writes the result into another memory table called the output image.
3. Update outputs — the CPU sends the output image to the physical output terminals, energising or de-energising motors, valves, and lamps in the real world.
4. Diagnostics & communication — the PLC checks itself for problems (memory OK? watchdog OK?) and exchanges data with other devices on the network (HMIs, other PLCs, SCADA).

Why Scan Time Matters — A Quick Example

The total time for one full scan cycle is called the scan time. For a small program, it’s typically 1 to 10 milliseconds. That’s so fast you can hardly imagine it — your eye blinks in 100 ms, so the PLC can complete 10 to 100 scans during one of your blinks.

But here’s the catch. The PLC only “sees” what’s happening in the world during step 1 of each scan. If a fast event happens between two scans, the PLC may miss it entirely.

Modifying the Operation

Here’s the magic trick that made PLCs unstoppable. To change a relay-based control panel, you have to physically pull out wires, add new relays, and re-wire the terminals. A small modification can take hours and is a frequent cause of mistakes and downtime.

To change a PLC-controlled system, you do this instead: open the programming software on your laptop, edit the ladder logic, click “Download”, and the new logic takes effect in the very next scan cycle. The wiring to the field devices — sensors, switches, motors, valves — usually doesn’t change at all.

This single feature — software-defined control logic — is the entire economic justification for the PLC industry. It is why every modern factory, refinery, water-treatment plant, and manufacturing line in the world runs on PLCs rather than relay panels.

PLC vs. Personal Computer — What’s the Difference?

Students often ask, “If a PLC has a CPU and memory and I/O, isn’t it just a computer? Why can’t I use my laptop instead?” Good question. The architecture is similar, but they’re designed for very different jobs. Here’s the comparison.

So a laptop in a factory would die within weeks — the dust, vibration, and electrical noise would destroy it. And it would never be reliable enough to control machinery, because Windows can pause for a few seconds while doing background tasks. In a PLC, “deterministic” means the timing is guaranteed — you always know when the output will respond.

What’s a PAC?

You might also hear the term Programmable Automation Controller (PAC). A PAC is a modern controller that combines PLC ruggedness with the multi-tasking power of a PC. PACs handle motion control, machine vision, advanced math, and database connectivity that traditional PLCs couldn’t do. The line between high-end PLCs and PACs has blurred a lot in the last decade — many controllers today are really both.

PLC Sizes — From Tiny to Huge

Not every job needs the same size of PLC. A simple irrigation timer doesn’t need the same controller as an oil refinery. So PLCs are sold in four size classes, mostly defined by their I/O count — the total number of inputs plus outputs the device can handle.

When choosing a PLC, you also look at scan speed, supported communication protocols (EtherNet/IP, Modbus, PROFINET, etc.), supported programming languages, available memory size, and price. The golden rule is simple: pick the smallest PLC that does the job. A nano running a paint plant will run out of resources, but a large PLC running a vending machine is a waste of money.