The short answer
What Is a PLC?
A PLC (programmable logic controller) is an industrial computer built to control machinery and processes. It repeatedly reads the state of field inputs, solves a user-written control program, and writes results to outputs. Unlike a general-purpose computer it runs a fixed, predictable cycle, tolerates heat, vibration, and electrical noise, and is expected to run for years without a reboot.
Key points
- A PLC executes a repeating cycle: read inputs, solve logic, write outputs.
- It is built for determinism and uptime, not raw computing speed.
- I/O modules connect it to real field devices at real field voltages.
- Programs are written in the IEC 61131-3 languages, most often ladder logic.
- It replaced racks of hardwired relays, and much of its vocabulary is inherited from them.
What a PLC actually does
Strip away the vendor differences and every programmable logic controller does the same four things over and over, thousands of times a minute. It captures the state of everything wired to its inputs. It solves the control program against that captured state. It writes the results to its outputs. Then it handles communications and diagnostics before starting again.
That repetition is the point. A PLC is not trying to be fast in the way a desktop computer is fast. It is trying to be predictable. If a level switch closes, you need to know the pump will start within a bounded, knowable amount of time, every time, whether the plant has been running for ten minutes or ten years.
The physical parts
- Processor (CPU)
- Holds the program and the data table, solves the logic, and manages communications. It also runs the diagnostics that fault the controller when something is wrong.
- Power supply
- Converts incoming line or 24 VDC power into the backplane power the modules need. Sizing it correctly is a common source of intermittent faults.
- Chassis and backplane
- The physical frame and the communication path between the processor and the modules. Some small controllers are a single sealed brick with no chassis at all.
- Discrete I/O modules
- Read on/off signals like a float switch or a run confirmation, and drive on/off outputs like a motor starter coil or a solenoid.
- Analog I/O modules
- Convert a continuous field signal such as a 4-20 mA level transmitter into a number the program can use, and convert numbers back into signals for devices like a valve positioner or a variable speed drive.
- Communication modules
- Move data to SCADA, to other controllers, and to field devices over Ethernet, serial, or a fieldbus.
Why not just use a PC?
People ask this constantly, and the honest answer has less to do with computing power than with everything around it. A PLC is designed to sit in an unconditioned enclosure next to a variable frequency drive, survive a nearby lightning strike through its surge protection, ride through a power blip, and start back up into a known state without anyone logging in.
| Characteristic | PLC | General-purpose PC |
|---|---|---|
| Execution model | Fixed repeating scan | Preemptive multitasking |
| Timing | Deterministic and measurable | Best-effort |
| Startup | Returns to a defined state automatically | Requires an operating system boot |
| Environment | Rated for heat, vibration, and electrical noise | Office conditions |
| Field connection | Native I/O at field voltages | Requires external interface hardware |
| Expected uptime | Years between restarts | Restarted routinely |
Where the language comes from
Before controllers, machine logic was built from physical relays wired into panels. Changing the sequence meant rewiring. The first programmable controllers were sold on the promise that you could change the sequence by editing a program instead, and to make that sellable to the electricians who would maintain them, the programming language was drawn to look like the relay ladder drawings they already read.
That is why ladder logic still has rungs, contacts, and coils, and why an experienced technician can often follow a program they have never seen. It is also why terms like "normally open" and "seal-in" survive in software that has no relays anywhere in it.
PLC, PAC, and RTU
You will hear three terms used for overlapping equipment, and the boundaries are marketing more than engineering.
- PLC
- The general term. Any controller running a scan-based control program against field I/O.
- PAC (programmable automation controller)
- A vendor term for a higher-end controller with more memory, structured data types, and better handling of motion or batch. Functionally it is still a PLC.
- RTU (remote terminal unit)
- A controller at a remote site, usually optimized for low power, wide temperature range, and reporting over a limited communication path such as radio or cellular. In water and wastewater, most lift station RTUs are simply small PLCs in a remote panel.
What to learn next
The single most useful thing to understand after this is the scan cycle, because almost every confusing PLC behavior traces back to when in the scan something happened. After that, get comfortable with analog signals, because that is where the physical world becomes numbers and where most field problems live.
Frequently asked questions
- What does PLC stand for?
- Programmable logic controller. The name describes what it replaced: hardwired relay logic that could only be changed by rewiring, replaced by logic you can change by programming.
- What is the difference between a PLC and a microcontroller?
- A microcontroller is a chip. A PLC is a finished industrial product built around a processor, with rated I/O, a power supply, diagnostics, an environmental rating, and a standardized programming environment. You can build a controller from a microcontroller, but you would be rebuilding everything a PLC already provides.
- Do I need to know how to program a PLC to work with one?
- No, but you need to be able to read one. Technicians who can follow a rung and see which condition is holding a pump off resolve calls far faster than those who can only check voltages.
- How long does a PLC last?
- Processor and I/O hardware routinely runs fifteen to twenty-five years. The practical limits are usually spare parts availability, software that no longer runs on a supported operating system, and communication protocols the rest of the plant has moved past.
Related topics
- The PLC Scan CycleRead inputs, solve logic, write outputs, housekeeping. Understanding scan order explains most PLC behavior that looks wrong at first glance.
- Ladder Logic FundamentalsRungs, contacts, coils, and the relay conventions the language inherited — plus the patterns you will meet in almost every industrial program.
- 4-20 mA Current LoopsWhy the industry standardized on current instead of voltage, how a two-wire loop is powered, what the live zero buys you, and how to read a loop with a meter.
- PLC I/O SystemsDiscrete and analog input and output modules, sinking and sourcing, relay and transistor outputs, wiring conventions, and the module diagnostics that find field faults from the panel.
- PLC ArchitectureHow a programmable logic controller is physically organized: the chassis, backplane, processor, I/O modules, remote racks, and what those choices mean for wiring, expansion, and failure.
- The PLC ProcessorWhat the processor module does on every scan, how its memory is organized, what the mode switch and status lights mean, and how it faults and recovers.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.