A PLC (programmable logic controller) is the unit responsible for logic and control: it reads sensors, makes decisions and drives outputs. An HMI (human–machine interface) is the screen for people to look at and operate: it shows the data held in the PLC and lets people give commands.
The difference is in “who decides” and “who shows it to people”, plus how the two connect, how the programs are divided, where each is installed, and what is affected when one fails. This article compares four points: role and function, communication and connection, program and screen, environment and maintenance; then you choose according to your machine. It focuses on PLCs and touch-screen HMIs used in industrial machines and control panels; supervisory software for a whole production line and large distributed control systems are outside its scope.
Point 1 | Role and function: what control and display each do, and what an all-in-one unit is.
Point 2 | Communication and connection: how the HMI connects to the PLC, and what happens when the link is lost.
Point 3 | Program and screen: what the PLC program and the screen software each handle, and whether changes must be synchronized.
Point 4 | Environment and maintenance: where each is installed, what protection it needs, and what to do when it fails.
This article starts from “you already know the machine needs control and you also want people to operate it”; each source and its basis are in the notes at the end. If you want to read about selection first, see How to choose a PLC and How to choose an HMI. This is the general case and still depends on the individual case.
Figure 1. The four comparison points between a PLC and an HMI (schematic, not to scale)
| Point | PLC | HMI |
|---|---|---|
| ① Role and function | Reads inputs, runs logic, drives outputs | Shows data, accepts operation |
| ② Communication and connection | Connects to sensors and networks; waits for the HMI to read | Connects to the PLC; each point is mapped to an address |
| ③ Program and screen | Ladder and other programs manage logic and sequence | Screen configuration software manages layout and alarms |
| ④ Environment and maintenance | Usually inside the panel; back up the program | Installed on the operator panel; check the protection rating |
Point 1 | Role and function: who controls, and who shows it to people
How to look at it:
Write down first: what the machine must do automatically, whether a person needs to watch status or change settings beside it, and how many points need to be displayed on site.
Sensor inputs, outputs and logic decisions are the PLC’s job.
Showing values, alarms, buttons and setting screens is the HMI’s job.
For an all-in-one unit (one device with both control and screen), ask whether a busy screen can affect control when they share a processor.
What public sources say: A trade magazine article (June 2014; the author works for an automation product vendor, so this is the vendor’s view) says: the HMI lets the operator monitor in real time; the PLC is used for machine control and handles both simple and high-speed tasks well; PLC-plus-HMI units can save wiring, but the two share a processor, and a heavy screen load can drag down real-time control. Another trade magazine article (May 2012, written by the magazine’s editor, quoting people from several vendors) says: the benefits of an all-in-one are less wiring, less cabinet space and one software package; the drawbacks are a smaller screen and a limited number of I/O points; some people also worry about sharing a processor with safety interlocks. A PLC textbook chapter on a teaching site (date uncertain) says: the HMI is a window onto PLC memory and the operator does not touch the program; some panels have a built-in PLC; the HMI can also take over trends and alarms. A trade magazine article (March 2009, by a person at a drive vendor) divides HMIs into three kinds: replacing pushbuttons, handling data, and supervisory (note table 1).
Point 2 | Communication and connection: how they connect, and what happens when the link breaks
How to look at it:
Write down first: whether the PLC and the HMI are the same brand, which communication port is used, and how far apart they are.
The same brand usually has a ready-made connection method; mixed brands need a check of the HMI’s driver list.
When connecting, every point to be displayed must be mapped to an address in the PLC.
Ask what the screen shows when the link is lost and whether the PLC is affected.
What public sources say: An automation maker’s HMI software manual (March 2017; the maker’s view) says: that company’s “integrated connection” is limited to the PLC families it lists; connecting to other brands goes through a driver, and the address must be written as the actual address in the PLC; setting the read period of an area pointer too short can affect HMI performance, and the manual gives no default; for that company’s specific PLC models, if an address changes, the HMI project must be recompiled and downloaded. Another maker’s HMI software help (date uncertain; the maker’s view) says: that model detects a lost link within 5 seconds; before that the screen may still show the old value, afterwards the value is marked as bad quality and recovers when the link returns; this is that model’s own behavior, not a general rule. The 2014 article above says Ethernet is a common connection and fixed PLC addresses need to be mapped by hand. The 2009 article above says that with mixed brands you should check the driver documentation and driver speed. The textbook chapter above says each point maps to one bit or word in the PLC, and a data point should have just one writer (note table 2).
Point 3 | Program and screen: who writes what, and whether changes must be synchronized
How to look at it:
Write down first: who changes the PLC program, who changes the screens, and whether they are the same person.
The PLC program manages logic and sequence; the screen software manages layout, objects and alarm messages.
If a PLC address or a point name changes, the screen side has to change with it.
Back up the two sides separately and record versions, so they can be matched up.
What public sources say: A standards association page on the PLC programming language standard (introduction to the 2025 edition; date uncertain) lists the PLC languages as ladder diagram, function block diagram, structured text, instruction list and sequential function chart; the page does not discuss HMIs. The textbook chapter above says: build the point list first and then draw the screens; objects on the screen can change color according to the point state. The 2014 article says HMI software mostly uses configuration, and programming is needed just at an advanced level; an operator interface terminal can be built on a computer and downloaded to the machine. The 2009 article divides HMI software into proprietary, cross-hardware and open kinds. The software manual above says that for a specific model, when a PLC address changes, the HMI project must be recompiled and downloaded. Backup and version management are not discussed in any of these sources (note table 3).
Point 4 | Environment and maintenance: where they sit, and what to do when one fails
How to look at it:
Write down first: whether the installation location is inside the panel or on the operator panel, and whether there is oil, moisture or vibration on site.
The HMI is often installed on the operator panel, so look at the protection rating; the PLC is usually inside the panel.
Ask whether the program and screens can be restored quickly when a unit is replaced.
Decide in advance whether the machine can keep running from the PLC alone when power is lost or the screen fails.
What public sources say: The 2009 article above says noise, vibration, washdown, high temperature and outdoor use narrow the HMI choices, and washdown and similar conditions may call for a higher protection rating; it gives no required figures. The textbook chapter above says HMI panels are ruggedly built and mostly touch-enabled. The 2012 article says an all-in-one can fit into a small cabinet and lowers the machine builder’s cost, with no figures. Touch life, data retention after power loss and the replacement process are not discussed in any of these sources (note table 4).
Comparison table: the four points at a glance
| Item | PLC | HMI |
|---|---|---|
| Main job | Reads inputs, runs logic, drives outputs | Shows data, accepts operation |
| Who decides | PLC | The HMI does not control; it watches and gives commands (except all-in-one units) |
| Connection | Connects sensors, drives and networks | Connects to the PLC; same brand is simpler, mixed brands need a driver |
| Program and software | Programming languages such as ladder | Screen configuration software; points must map to PLC addresses |
| When the link is lost | Handled according to the program | The screen may stay on the old value, then mark it bad (one maker’s description) |
| Usual location | Inside the control panel | On the operator panel |
| All-in-one unit | Less wiring, less cabinet space | Smaller screen, limited points, shared processor |
Source: note tables 1 to 4 (sources 1 to 7). These are what the sources say; the sources do not agree with each other, and this is not a selection threshold.
How to choose: when a PLC alone is enough, and when to add an HMI
Based on the public sources, the choice can be seen this way:
PLC alone: a PLC is used for machine control and handles simple and high-speed tasks well (source 1). Whether an HMI can be left out when the machine runs automatically and nobody needs to see values or change settings on site is not stated in the sources; this is this article’s arrangement (source 4 calls one class of HMI “replacing pushbuttons”, which shows that physical buttons and indicator lights are also a way to do it).
Add an HMI: the operator needs to see status, alarms and trends in real time (sources 1, 3, 4), or needs to change setpoints on site (source 3 says some variables need to be both readable and writable).
Use an all-in-one: you want less wiring and less cabinet space, the number of points is small and the screens are not complicated; watch the shared processor, the screen size and the point limit (sources 1, 2).
Near the boundary: the sources give no line for “how many points or how complex before they should be separated”; follow your machine, your point count and the people who maintain it. Whether safety interlocks share a processor with the screen should also be asked in advance (source 2).
These items are what public sources say, not a conclusion about your machine; which to choose still depends on your point count, operating needs and installation location.
What Jiahon can help with
Below we take just the product names from the product pages; for the specifications of each model, please inquire. Some pages list both PLCs and HMIs, and each is noted below.
PLC side:
PLC programmable controller component series: the product name reads PLC programmable controller component series and lists a brand; the page mixes various PLC components, the tag area and “also see” section mention HMIs; please inquire about specifications.
PLC expansion modules: lists a brand; the page covers expansion memory cassettes, communication, I/O and temperature modules, and the specification table also mixes in one HMI; please inquire.
PLC series: lists another brand; the page lists CPUs, modules and power supplies, with one HMI in the “also see” section; please inquire.
PLC modules: lists another brand; the page lists CPUs and I/O modules, with HMIs in the “also see” section; please inquire.
PLC modules: another page with the same product name, same brand as the first item in this section but a different series; the page lists 6 modules, and the text also discusses discontinuation and migration; please inquire.
HMI side:
HMI human–machine interface: lists a brand; the page lists two models; which PLC brands it can connect to is the page’s own statement; please inquire.
Industrial touch HMI: lists another brand; please inquire about protection rating and resolution.
PLC full range: lists a brand, and the name also mentions HMI; this page lists both PLCs and HMIs; please inquire.
To match a model, please prepare six items first: what the machine must control and how many points; whether you need on-site display and operation; whether the PLC and HMI are the same brand; the communication port and distance; the installation location and protection needs; the model you use now and the problem you have. Please contact Jiahon.
On SMT / EMS lines: make abnormalities visible on the screen
The lesson of a quality abnormality report. In one quality abnormality report from engineering records, a night-shift burn-in (RDT) tester was started without turning on the oven temperature, and the operator did not fill in the start-up check sheet; the next morning, when the supervisor walked the line, there was no oven temperature value on the screen, and 2 lots, 355 pieces in all, were taken off the line and put on hold. An HMI can stop this kind of error: the screen warns when the temperature is below setpoint, and a PLC interlock does not let the test start (point 1 of this article: the PLC does the interlock, the HMI does display and warning).
The screen gives the verdict directly. A work instruction for a module test station: scan the employee ID, lot number and tray ID, place the unit in the fixture, and the top left of the screen shows PASS or Fail with an error code directly; the operator sorts the trays by the result. The more direct the screen design, the fewer human judgment errors.
Send data upward. The status seen on the HMI has to be uploadable to the MES. Semiconductor equipment commonly uses SEMI E30 GEM, and the electronics assembly industry is promoting IPC-CFX (see the PLC selection article). For the HMI concept, see Human–machine interface.
Notes: sources and exceptions
This part is for readers who need to check; the practices above stand without it. When your equipment maker’s written specifications, site rules or safety requirements differ from this article, follow them.
Sources for each point
| Source | Where used, and where it comes from |
|---|---|
| Source 1 | Points 1, 2, 3: division of work, all-in-one units, connection, software and configuration. An automation trade magazine article (6 June 2014; the author works for an automation product vendor; the vendor’s view) |
| Source 2 | Points 1, 4: pros and cons of all-in-one units, and cabinets. A report in the same magazine (16 May 2012; written by the magazine’s editor, quoting people from several vendors) |
| Source 3 | Points 1, 2, 3, 4: the role of the HMI, points and addresses, screen development, panel build. A PLC textbook chapter on a teaching site (date uncertain; examples mention software from several vendors; the page has a login and subscription banner) |
| Source 4 | Points 1, 2, 3, 4: classes of HMI and software, mixed brands, environmental conditions. Another article in the same magazine (30 March 2009; the author works for a drive vendor; the vendor’s view; content is from 2009) |
| Source 5 | Points 2, 3: integrated connection and drivers, area pointer read period, recompiling after an address change. An automation maker’s HMI software communication manual (March 2017; the maker’s view) |
| Source 6 | Point 2: detection of a lost link and screen behavior. Another automation maker’s HMI software help (date uncertain; the maker’s view; covers that model just) |
| Source 7 | Point 3: PLC programming languages. A standards association’s introduction page (date uncertain; not the standard text) |
| Jiahon material | “What Jiahon can help with”. Source: wording of the product names on Jiahon product pages (8 pages) |
Table 1 | Role and function
| Item | Content |
|---|---|
| Division of work | The HMI lets the operator monitor in real time; the PLC is used for machine control and handles both simple and high-speed tasks well (source 1, 2014, vendor’s view) |
| Risk of all-in-one | PLC-plus-HMI units save wiring but share a processor, and a heavy screen load can drag down real-time control (source 1, 2014, vendor’s view) |
| Pros and cons of all-in-one | Benefits are less wiring, less cabinet space and one software package; drawbacks are a smaller screen and limited I/O points; some worry about sharing a processor with safety interlocks (source 2, 2012, quoting vendor people) |
| Role of the HMI | The HMI is a window onto PLC memory and the operator does not touch the program; some panels have a built-in PLC; the HMI can take over trends and alarms (source 3, teaching site, date uncertain) |
| Classes of HMI | Replacing pushbuttons, handling data, supervisory (source 4, 2009, vendor’s view) |
Table 2 | Communication and connection
| Item | Content |
|---|---|
| Integrated connection and drivers | That company’s “integrated connection” is limited to the PLC families it lists; connecting to other brands goes through a driver, and the address is written as the actual address in the PLC (source 5, 2017, maker’s view) |
| Area pointer read period | A read period set too short can affect HMI performance; the manual gives no default (source 5, 2017, maker’s view) |
| Link loss | That model detects a lost link within 5 seconds; before that the screen may still show the old value, afterwards it is marked bad quality and recovers when the link returns; this is that model’s own behavior, not a general rule (source 6, date uncertain, maker’s view) |
| Connection method | Ethernet is a common connection; fixed PLC addresses need to be mapped by hand (source 1, 2014, vendor’s view) |
| Mixed brands | With mixed brands check the driver documentation and driver speed; the same brand can simplify point addressing (source 4, 2009, vendor’s view) |
| Points and addresses | Each point maps to one bit or word in the PLC; a data point should have just one writer (source 3, teaching site, date uncertain) |
Table 3 | Program and screen
| Item | Content |
|---|---|
| PLC languages | Ladder diagram, function block diagram, structured text, instruction list, sequential function chart; the page does not discuss HMIs (source 7, association page, date uncertain) |
| Screen development flow | Build the point list first and then draw screens; objects can change color with point state (source 3, teaching site, date uncertain) |
| Software operation | HMI software mostly uses configuration, and programming is needed just at an advanced level; an operator interface terminal can be built on a computer and downloaded to the machine (the same article also says the line between PLC and PAC has blurred; not cited in the main text) (source 1, 2014, vendor’s view) |
| Software classes | Proprietary, cross-hardware, open (source 4, 2009, vendor’s view) |
| When an address changes | For a specific model, if the PLC address changes, the HMI project must be recompiled and downloaded (source 5, 2017, maker’s view) |
| Backup and version | None of these sources discuss it |
Table 4 | Environment and maintenance
| Item | Content |
|---|---|
| Environmental conditions | Noise, vibration, washdown, high temperature and outdoor use narrow the HMI choices, and washdown and similar conditions may call for a higher protection rating; no required figures (source 4, 2009, vendor’s view) |
| Panel build | HMI panels are ruggedly built and mostly touch-enabled (source 3, teaching site, date uncertain) |
| Cabinet space and cost | An all-in-one can fit a small cabinet and lowers the machine builder’s cost; no figures (source 2, 2012, quoting vendor people) |
| Life, power loss, replacement | Touch and backlight life, data retention after power loss and the replacement process are not discussed in any of these sources |
This is the general case and still depends on the individual situation.
Exceptions and limits
What was and was not seen: The sources are 3 trade magazine articles on automation (June 2014, the author works for an automation product vendor, vendor’s view; May 2012, written by the magazine’s editor, quoting people from several vendors; March 2009, the author works for a drive vendor, vendor’s view, content from 2009), 1 PLC textbook chapter on a teaching site (date uncertain, examples mention software from several vendors, the page has a login and subscription banner), 1 automation maker’s manual (March 2017, maker’s view), 1 help page from another automation maker (date uncertain, maker’s view), and 1 standards association introduction page (date uncertain, not the standard text). Of the 7 sources, 3 are trade magazine articles written by or quoting vendor people, 2 are maker manuals and help pages, 1 is a teaching site and 1 is an association page; none gives test conditions, and no standard text was read. The two magazine articles that speak directly to “how a PLC differs from an HMI” are those of 2014 and 2012; the others each cover one point, and the main text cites just what they say. No official catalog of any major maker was found, so there is no source from such a company; no source covering both touch life and the effect of power loss was found, so the main text gives no figures for these two. A few seller blogs and one university lecture note were also looked at, but were not used because they were seller lead-generation or did not mention HMIs at all.
Numbers are examples: The main text has just one number, “5 seconds” (source 6, the behavior of one model, not a general rule), and it is not a selection threshold. Source 1’s “saves up to half the development time” and “up to 16 loops” have no citation, and a capacity figure in source 4 has an incomplete unit; none are in the main text, and most capacity and time figures in the sources were left out.
Source 1 is internally inconsistent: It says a PC-based HMI does not need you to write drivers, and also that advanced use needs programming; it calls the PAC new, and also says the line between PLC and PAC has blurred; “tag library saves up to half the development time” and “older PLCs up to 16 loops” have no citation and are not cited in the main text.
Reservations on other sources: Source 2 uses an example of an old operating system to argue that PC-based control is unreliable; this is out of date and not cited, and the cost advantage has no data. Source 3 says “write to the PLC input register”, which is loose wording; the main text cites just “each point maps to a bit or word in the PLC, and a point should have one writer”. Source 4 uses the author’s company software as the example of proprietary software and states its drawbacks; the main text cites just the broad direction of the three functions, the three software kinds and the environmental conditions. The numbers in sources 5 and 6 are the rules of their own models (for example the 5-second link-loss detection, and the station limit for a specific connection) and cannot be taken as general rules; the main text cites just the link-loss example and notes that it is that model’s own behavior.
Differences of position (not numeric conflicts): Source 1 (2014) sees all-in-one units as leaning toward simple applications, while source 2 (2012) and some others see vendors continuing to launch all-in-ones; source 2 (2012) has doubts about PC-based control, while source 1 (2014) recommends PACs and PC-based HMIs. Both are listed side by side and the main text draws no conclusion for you.
Single sources: The shared-processor risk of all-in-one units, a smaller screen and limited points (sources 1, 2); the HMI as a window onto PLC memory, some panels with a built-in PLC, building the point list before screens (source 3); three kinds of HMI and three kinds of software, checking drivers for mixed brands, environment narrowing the choice (source 4); integrated connection limited to listed PLC families, a too-short area pointer period affecting performance, recompiling after an address change (source 5); detecting link loss in 5 seconds (source 6); the five PLC languages (source 7).
Sources with a position: Sources 1 and 4 were written by vendor people, sources 5 and 6 are maker materials, and source 2 quotes vendor people; none is standard text or a third-party test report, so the statements serve as examples for the explanation.
This article’s arrangement: The main text uses no “this article’s arrangement” label, since each statement can be matched to the sources above. The “How to choose” section sorts the sources’ statements into three cases (PLC alone, add an HMI, use an all-in-one); this is an arrangement, not the sources’ own sentences, and it states that the sources give no boundary. “PLC inside the control panel” in the comparison table’s “usual location” row is an arrangement of the general case that the sources do not state outright.
Scope: This article compares PLCs and touch-screen HMIs for industrial machines and control panels; supervisory software for a whole line and large distributed control are outside it; model cross-references, prices and lead times are not covered; it does not say “compliant with regulations” or “this makes it safe”; for matters of personnel and equipment safety, follow the PLC and HMI vendor specifications and site rules.
Equipment and products: “What Jiahon can help with” takes just the wording of product names on the product pages as of 13 October 2026, without citing models or brands on the pages; some pages list both PLCs and HMIs, as noted page by page in that section; for communication ports, point counts, screen sizes and protection ratings of each model, please inquire and follow what sales confirms.
This article is a summary of the general case. It is not a paraphrase of standard text, not an endorsement of any one vendor, equipment maker or service provider, and not an assurance for your equipment or site. Follow your equipment maker’s written specifications, site rules and safety rules, and your own verification. This is the general case and still depends on the individual situation.