IMDTouchKnowledge BaseShop main store

Explainer

What an HMI terminal is and what it actually controls

HMI and touchscreens Published 8 min read

Short answer

An HMI terminal combines the display, input hardware, processor and communication interfaces that run a visualization application and pass operator requests to a controller. The controller program, not the terminal, decides how the machine responds, so confirm every command from controller feedback rather than from the button animation.

On this page
  1. What is an HMI terminal?
  2. What is inside an HMI terminal?
  3. Does the HMI terminal control the machine?
  4. Can an HMI terminal replace a safety function?
  5. Why does the screen still show values after communication stops?
  6. How does an HMI terminal talk to a PLC?
  7. Can an HMI terminal read a sensor directly?
  8. Touchscreen, keypad, or buttons: which input fits the job?
  9. Where does the HMI application actually run?
  10. Questions asked

An HMI terminal is the industrial box at the machine that shows the operator what the process is doing and carries the operator's requests to a controller: display, input surface or keypad, processor running the visualization application, communication ports and an enclosure, engineered as one unit. It does not run the machine. The controller program owns the sequence, the interlocks and the response to every command, which is why a screen that looks alive can be showing stale data and a button that animates can have been refused. This article opens the terminal up, then follows one operator command across it to the controller and back.

What is an HMI terminal? #

An HMI terminal — also called an HMI panel, operator panel or operator terminal — is one industrial device that combines the display, the input hardware, the processor running the visualization application and the communication interfaces, giving the operator a single point to view the process and issue commands.

Its job is to turn machine data and operator commands into one usable interaction point: status, alarms, trends and diagnostics on the screen, setpoint entry and commands from the same screen. Everything on the operator's side of the glass is human factors; everything on the far side is the control system. Define the terminal by that boundary, not by screen size — the display is one component of the boundary device, not the definition of it.

What is inside an HMI terminal? #

Six functional blocks: the display, the input hardware, the processor and memory that execute the runtime, the communication ports, the enclosure, and the mounting arrangement — panel cut-out, wall bracket, pedestal or desk — that puts it in front of the operator.

Each block carries its own selection number. Display size, resolution and color depth set readability at the working distance and under the local lighting. The enclosure's protection is a documented per-model rating matched against dust, moisture, washdown, temperature and shock at the mounting spot — read it from the datasheet, never assume it from the look of the bezel. Processing power follows the application: a handful of screens with slow tags is light duty, while long alarm histories, trending and recipe handling take more. Panel mounting means a cut-out in a door or console, so the cut-out drawing is part of the mechanical decision. Select these as a system; screen size is one line on the list, not the specification.

Does the HMI terminal control the machine? #

No. The terminal writes requests and values into controller data; the controller program decides what the machine does with them, so sequences, permissives, interlocks and time-critical actions belong to the controller.

Mechanically, a display object reads a mapped data item to show a value, and an input object writes a value through the configured communication driver when pressed. Two failures hide inside that arrangement. A press can reach the controller and still not move the machine because an interlock refuses it — a correctly rejected command, not a terminal fault. And the press animation on the button is drawn locally by the terminal, so it proves nothing about the controller receiving anything. The rule that saves diagnostic hours: build every status indication from controller feedback, never from the appearance of the input object. ISA-101, the standards series for HMI design and management in process automation, treats exactly this as an engineering deliverable — displays designed for the operator's decisions and kept that way over the system's life. For what belongs on the screens themselves, the working practice is designing HMI screens for clear operator decisions.

When a command does nothing, walk the chain in order: operator input, object action, communication transfer, controller logic, machine feedback. A dead touch stops at step one, a communication fault at step three, and a refused command completes all five with the interlock as the answer — read the answer at the controller end, not on the screen.

Can an HMI terminal replace a safety function? #

No. A standard operator interface displays information and carries requests; it is not a safety device, and an emergency stop drawn on its screen does not meet the integrity or response requirements of a safety function.

Emergency stops, guard interlocks and similar functions belong in hardwired circuits or a safety controller built to the applicable machinery safety standard, independent of the HMI. The terminal may display their status; it must never execute them. If a risk assessment calls for a safety function, hardware it outside the HMI path.

Why does the screen still show values after communication stops? #

Because a display object shows the last value it successfully read, and nothing blanks it on its own: at a 250 ms poll rate, a damaged cable means zero successful reads while the number on the screen holds still.

Run the arithmetic on an illustrative configuration: a tank-level tag polled every 250 ms gives 1 s ÷ 0.25 s = 4 reads per second. The operator watches the screen for 2 minutes after the cable is crushed: 120 s × 4 reads/s = 480 polls, of which 0 succeed. The displayed level stays exactly what it was at the moment of failure, and its age grows without limit — one second, one minute and one hour look identical on screen. Most terminals raise a communication fault only after a configured timeout, and that timeout is a project setting, so a readable number and a live number are two different claims.

Treat any displayed value as unproven unless the terminal's communication status for that connection is healthy, and alarm communication failure so a crushed cable surfaces in seconds rather than at end of shift.

How does an HMI terminal talk to a PLC? #

Through a physical port plus a matching driver: Ethernet, RS-232, RS-485 or USB on the hardware side, and a communication driver and protocol — Modbus, Profibus, DeviceNet or a vendor protocol — on the software side; both must line up.

Connection What it is What you verify
Ethernet Network technology carrying several industrial protocols Driver for that controller, addressing, physical link, access
RS-232 Serial point-to-point electrical interface Port assignment, pinout, serial settings, protocol carried
RS-485 Serial interface wired as a multidrop bus Topology, polarity, termination, serial settings, device addresses
USB Port whose available functions depend on the terminal Support for programming, storage or the intended function
Modbus Application protocol needing matching implementations Transport, device address, register mapping, data types, direction

A matching connector is the first check, not the last: Ethernet hardware does not make every Ethernet-connected controller reachable, because the driver decides. Use the connection both devices already support for the data you need, and add a gateway only when no direct path exists — every gateway is another configuration and diagnostic boundary. When a Modbus device on an RS-485 run stops answering, that boundary is where the work is: fixing HMI Modbus no-response over RS-485.

Can an HMI terminal read a sensor directly? #

Only when the sensor's output signal matches an interface the terminal documents; a communication port is not an analog input, so in most installations the sensor wires to controller I/O and the HMI reads the value as a controller tag.

Read the sensor's output specification — current loop, voltage, discrete, or a digital bus — against the terminal's documented inputs and drivers. Where they match, direct reading works; where they do not, the choices are an interface converter or controller I/O. Default to controller I/O unless the terminal's own documentation lists the sensor's signal type: the controller path also keeps the value available to the control program, which a direct-to-HMI reading does not.

Touchscreen, keypad, or buttons: which input fits the job? #

Match the input to the task: touchscreens suit graphical navigation and selectable equipment views, keypads suit repeated numeric entry, and physical buttons suit frequent discrete commands an operator has to find without looking.

Input Fits Acceptance check
Touchscreen Graphical navigation, equipment views, changing layouts Target size, touch accuracy, readability, operation with intended gloves and surface conditions
Keypad Repeated numeric or text entry Entry workflow, correction method, feedback for accepted and rejected values
Physical buttons or switches Frequent discrete commands, tactile operation Labels, mapping to application or wiring, command versus actual state
Joystick or specialized input Dedicated motion commands Hardware support and how the controller interprets the input

Glove operation, wet surfaces and heavy continuous use are model-dependent — test them with the selected hardware, not with the technology label. For consequential actions, add a confirmation step and controller-side range checks; numeric entry should carry its unit and permitted range, and "accepted" should mean the controller took the value, not that the entry window closed.

Where does the HMI application actually run? #

On the terminal, in most installations: the screens and tag links are built as a project on a PC in the terminal's programming software, downloaded to the terminal, and executed there as a runtime with the communication drivers configured inside it.

The other architecture runs the same kind of application on a touchscreen computer at the machine — the route when the visualization is a PC runtime, a SCADA client or PC-based HMI software rather than a proprietary terminal. When that migration is on the table, industrial panel PCs take the terminal's place at the machine. For choosing between the device categories themselves, the comparison lives in industrial HMI device types and how to choose between them. And when a terminal shows the wrong screens after a download, the first check is which file it actually loads: how to find the runtime file an HMI terminal actually loads.

Whatever runs the application, the division of labor holds: the terminal presents and requests, the controller decides, and the proof of any command is the machine's feedback read back through the controller.

Questions asked

Is an HMI terminal the same as a touchscreen monitor?

No. A touchscreen monitor is display and input hardware only; it renders whatever a connected computer draws. An HMI terminal adds the processor, memory and communication drivers that run the visualization application and exchange data with the controller. A touchscreen monitor paired with a panel PC can behave like a terminal, but the monitor alone does nothing.

Does an HMI terminal need its own program?

Yes. The screens, tags and object actions that tie displays to controller data are developed as a project on a PC in the terminal's programming software, then downloaded to the terminal, which loads and executes that runtime. Without a matching project the terminal has nothing to render and no tags to poll.

Can one HMI terminal talk to several controllers?

Often yes. Many HMI platforms let a single project hold multiple communication connections with different drivers, so one terminal can poll several PLCs at once. The limit is the terminal's documented driver list and connection count, and each connection adds poll traffic, so verify both against the application before committing.

What is the difference between an HMI and SCADA?

An HMI terminal is the local operator-facing device at one machine or line. SCADA is supervisory software, usually running on servers or PCs, that gathers data across many controllers, handles plant-scale history and alarms, and serves its own clients. A SCADA system typically includes HMI screens, but an HMI terminal is not a SCADA system by itself.

Keep reading

  • How-to

    How to find the runtime file an HMI terminal actually loads

    The startup configuration, not the file list, selects the loaded .MER. Cycle power and press the white box in the lower-left corner (touch, firmware 5.0 or later) or hold F1 on a directly connected USB keyboard to reach the configuration screen and read the loaded runtime name. Copy every stored runtime off before deleting anything in File Management.

    HMI and touchscreens

  • Troubleshooting

    Keeping PanelView Plus User Passwords After an MER Download

    There is no download option that leaves terminal users intact: a .mer replaces the runtime's users and passwords with the project's accounts. The working path is to upload the running runtime, restore it in FactoryTalk View Studio ME 8.00 or higher, which returns the terminal's current users to the project, then edit, rebuild and download, qualified once per terminal family. If downloads must never touch accounts, manage them with FactoryTalk Administration Console instead.

    HMI and touchscreens

  • Explainer

    Why a USB Joystick Cannot Drive PanelView Tags

    No. PanelView documentation supports USB flash drives, keyboards and mice, and the Plus 7 Performance host ports add removable drives and a printer — no game-controller class and no runtime mechanism that maps an input device to tags. The joystick belongs on PLC inputs or on a PC-based panel.

    HMI and touchscreens