PLC vs HMI: What's the Difference and How They Work Together
PLC vs HMI: What's the Difference and How They Work Together
The question comes up in every beginner's first week: if the PLC is controlling the machine, what is the HMI actually doing? And why do you sometimes see one without the other?
A PLC (Programmable Logic Controller) runs the control logic and directly controls machine outputs. An HMI (Human Machine Interface) provides a graphical interface for operators to monitor the process and send commands. The PLC is the brain; the HMI is the face.
They are separate devices that communicate with each other, and they have entirely different jobs. Mixing up the roles is one of the most common beginner confusions in automation — and it leads to genuine mistakes in wiring, programming, and fault-finding.
What a PLC Does
A PLC executes a program — typically ladder logic, structured text, or function block — on a fixed scan cycle. Every scan, it reads all its inputs (sensors, switches, pushbuttons), runs the program logic, and updates all its outputs (motor contactors, solenoids, valve actuators). This loop runs continuously, typically 5–50 milliseconds per cycle, regardless of whether anyone is watching.
The PLC enforces safety interlocks. If the e-stop is pressed, the PLC output goes off — immediately, in the current scan — because the logic says so. An operator standing at an HMI screen cannot override that, because the HMI does not control outputs directly. The PLC does.
Key characteristics of a PLC:
- Deterministic: same inputs always produce the same outputs in the same scan.
- Runs on dedicated industrial hardware designed for electrical noise immunity and 24-hour operation.
- Requires no operator interaction to run. The machine runs whether the screen is on or not.
- Inputs and outputs are physical wires connected to terminal blocks on I/O cards.
What an HMI Does
An HMI displays the current state of the process — live values, status indicators, trends — and gives operators a way to interact with the process without touching physical wiring or PLC software. The operator touches a button on the screen; the HMI writes a value to a PLC tag; the PLC logic reads that tag and decides what to do.
Key characteristics of an HMI:
- Reads PLC memory tags over a network connection (Ethernet in modern systems).
- Updates the display at a polling rate, typically 200–500 ms. Not the same as the PLC scan rate.
- Writing to an output from the HMI always goes via a PLC tag and PLC logic, never directly to a physical output.
- If the HMI loses communication with the PLC, the machine keeps running. The PLC does not know the HMI is gone; it just stops receiving any command writes.
Side-by-Side Comparison
| | PLC | HMI | SCADA | |---|---|---|---| | Primary role | Execute control logic | Operator interface | Multi-site supervision | | Runs the logic? | Yes — always | No — reads/writes tags | No — reads/writes tags | | Output wiring | Physical I/O cards | None | None | | Runs without operator | Yes | Panel can be off | Server can be offline | | Programming language | Ladder, ST, FBD, etc. | Graphical screen editor | Database config, scripting | | Communication | Scans I/O directly | Polls PLC over Ethernet | Polls PLCs over network | | Safety-critical | Yes — directly | No | No | | Failure consequence | Machine stops / faults | Loses visibility only | Loses remote oversight |
Where They Connect: The Tag Handshake
The link between PLC and HMI is the tag — a named address in PLC memory. Both devices share the same tag names, and that shared address space is how they exchange information.
For example, in a pump control system:
- The PLC has a tag
Pump_Running(bit) that the ladder logic sets to 1 when the pump motor is energised. - The HMI has a status lamp bound to
Pump_Running. When the bit is 1, the lamp turns green. - The HMI has a start button that writes 1 to
HMI_Start_Cmdwhen pressed. - The PLC ladder logic has a rung that reads
HMI_Start_Cmdand, if all permissives are met, starts the pump and clears the command bit.
The HMI never wires directly to the pump. The PLC ladder never wires directly to the screen button. The tag is the interface between them.
The Three Devices That Confuse Beginners
Once HMI is understood, SCADA confusion follows. Here is where each fits:
PLC — directly controls one machine or process unit. Physical I/O, deterministic, safety-critical.
HMI — operator interface for one machine or area. Panel-mounted, touchscreen, local.
SCADA — supervisory system connecting multiple PLCs and HMIs across a site or multiple sites. Runs on a server, provides a plant-wide view, historical data logging, and reporting. A single pump skid has a PLC and an HMI. The entire water treatment plant's worth of pump skids has SCADA watching all of them.
The boundary between HMI and SCADA is blurring — modern software platforms like Ignition can function as either, or both. But the conceptual distinction holds: HMI is local and machine-specific; SCADA is site-wide and supervisory.
Common Confusions Cleared Up
"The HMI controls the motor." No. The HMI writes a command bit to the PLC. The PLC controls the motor. If the PLC has an interlock that prevents the motor starting (e-stop depressed, overload tripped, permissive not met), pressing the HMI start button does nothing to the motor because the PLC logic blocks it.
"If the HMI crashes, the machine stops." Usually not. The PLC is independent. If it is in automatic mode running a cycle, it will continue unless its logic requires an operator to acknowledge something. Loss of HMI communication is a visibility problem, not necessarily a safety stop — though good practice is to program a PLC watchdog that triggers a safe state if HMI communication is lost for more than a defined time.
"You program the HMI in the same software as the PLC." On Siemens TIA Portal, the PLC and the HMI are configured in the same project environment (different tools within it, but one project file). On Allen-Bradley, Studio 5000 handles the PLC and FactoryTalk View handles the HMI — different software. The degree of integration varies by vendor. The concepts remain the same.
"The HMI runs on the PLC hardware." In a PanelView or similar panel, the HMI hardware is a separate device from the PLC, even if they are mounted in the same cabinet. There are edge cases — some small PLCs have an integrated display — but in industrial systems these are separate boxes with separate processors.
Lifecycle Differences
A PLC and HMI are also maintained differently over their service lives.
A PLC program change requires a trained controls technician, a laptop with the appropriate vendor software, and usually a formal modification procedure (MOC — Management of Change) in a well-run plant. PLC programs are revision-controlled for good reason: a wrong rung can stop a machine or create a safety hazard.
An HMI screen change is lower risk in most cases — adding a display or changing a label does not affect control logic. But binding a new button that writes to the wrong PLC tag is the exception that breaks that rule. HMI changes still need to be reviewed before deployment.
Practice both roles in the simulator: write the PLC logic for a motor start-stop scenario, then look at the machine view panel on the right side of the screen — that is the HMI layer showing you the live state the PLC is maintaining. The separation between logic (left panel) and visualisation (right panel) is the same separation that exists between a PLC and an HMI on a real machine.
Frequently Asked Questions
Q: Can an HMI work without a PLC?
A: In theory yes — some HMI platforms support direct I/O connections — but this is not typical for industrial machines. The standard architecture is HMI over a network to PLC, with the PLC handling all safety-critical logic and I/O. Using an HMI to directly control outputs would bypass all the interlock and safety logic that typically lives in the PLC, which is why it is almost never done.
Q: What is the difference between an HMI and a SCADA system?
A: An HMI is typically a single-panel or single-machine interface that reads from one PLC. SCADA connects to many PLCs across a site or multiple sites, with a centralised server, historian, and reporting layer. HMI is local; SCADA is supervisory. A plant has one or several PLCs each with their own HMI panel, and all of them reported to a SCADA system watching the whole site.
Q: Does the HMI slow down the PLC scan?
A: HMI communication uses the PLC's built-in Ethernet communications processor, not the scan processor, in most modern PLCs. So the HMI polling the PLC for tag values does not slow down the ladder scan. However, very high-speed polling of thousands of tags can load the communications processor and affect scan time indirectly. This is rarely a problem with sensible poll rates (200–500 ms for most process values).
Q: Is the HMI program version-controlled the same way as the PLC program?
A: It should be. In a well-managed site, both are stored in a document management system and any change goes through a change control procedure. In practice, HMI backups are sometimes less disciplined than PLC backups because "it's just a screen." This is the mistake you discover when a panel computer fails and nobody has the latest HMI project file.
Q: Can I learn HMI programming before I know PLC programming?
A: You can learn the screen-building mechanics, but you will not understand what you are connecting to. HMI programming is most useful once you understand PLC tags, what they represent, and how the PLC logic that drives them works. The beginner PLC track takes you through the fundamentals — once you are comfortable writing a motor start/stop and understanding what the tags mean, the HMI layer becomes straightforward.
Ready to write the PLC logic that an HMI would sit on top of? The motor start-stop scenario is free, runs in your browser, and auto-grades your work. No install, no hardware.