IMDTouchKnowledge BaseShop main store

Explainer

What an HMI Is and How a Touch Panel Runs One

HMI and touchscreens Published 6 min read

Short answer

An HMI is the hardware or software through which an operator watches and commands a controller. It is not written in a general-purpose language: you configure screens in a vendor engineering editor, compile the project into a runtime, and the touch panel computer runs that runtime while exchanging variables with the control logic over a driver you verify first.

On this page
  1. What an HMI actually is
  2. The four layers that make an HMI work
  3. The programming-language question, answered
  4. What the touch panel computer runs
  5. How the panel talks to the controller
  6. Following one temperature from controller to screen and back
  7. Questions asked

An HMI — a human-machine interface — is the operator-facing layer between a person and the control logic: it shows what the process is doing and turns operator actions into data the logic can act on. It is not a programming language, and it is not the program that runs the machine. On a touch panel, an HMI is an application you build somewhere else: you draw screens and bind them to controller variables in an engineering editor on a PC, compile the project into a runtime, load that runtime onto the panel, and the panel then exchanges values with the controller over a verified cable and driver. Four layers are involved, and each one is chosen and checked separately before development starts.

What an HMI actually is #

NIST's cybersecurity glossary keeps the definition short: an HMI is the hardware or software through which an operator interacts with a controller. That covers both ends of what you see in a plant. A physical panel of pushbuttons and indicator lights is an HMI; so is the touch screen drawing synoptics with live values. Both exchange information in two directions: process data and status flow toward the operator, while commands, setpoint changes and acknowledgements flow back to the logic.

The control logic owns the process. It executes the functions, holds the variables, and runs whether or not anyone is watching a screen; the HMI only reads and writes those variables. Anything the machine must do to remain safe belongs in the logic, never in the screen.

The four layers that make an HMI work #

Layer Primary role
Control logic Runs the machine or process functions and maintains the process variables
Communication Moves digital and analog values between the control logic and the panel
HMI runtime The compiled application the panel executes: draws screens, refreshes values, sends operator entries
Engineering editor The PC package where screens, objects, text and data connections are created, then compiled

Each layer fails differently, which is why they are checked separately. The engineering editor stops you before you start if it cannot target your panel model. The runtime fails at load, when the panel rejects a project compiled for different hardware. The communication layer fails live, with values frozen at their last state because the data path is broken. Three verifications, three failure modes: the editor must support the panel, the runtime must match the panel's hardware and operating system, and the driver must match the controller's protocol.

The programming-language question, answered #

The direct answer to "what language do those touch screens use" is: none, in the general-purpose sense. You do not type code into a panel; you configure it. The engineering editor gives you graphical objects — numeric displays, buttons, bar graphs, alarms, mimics — and you bind each object to a controller variable. When the project is complete you compile it, and compilation produces the runtime that executes on the device. Siemens documents exactly that sequence for WinCC Unified, where compiling the project yields the runtime for the HMI device.

The practical catch is that the editor belongs to a vendor family. Rockwell's PanelView Plus terminals are built in FactoryTalk View Studio for Machine Edition, PanelView 800 in Connected Components Workbench, and PanelView 5000 in Studio 5000 View Designer; Weintek panels use EasyBuilder Pro. No package covers every panel, so the first selection you make is the editor that targets your hardware — is there one software that programs every HMI panel works through that trade-off.

Scripting does exist, as an add-on rather than the entry ticket. Where a package includes scripts — chiefly in browser-based runtimes — they carry behavior the standard objects cannot express, and where JavaScript and WebAssembly actually run on an HMI settles which side of the connection executes them. For the scope of the building work itself, start from what HMI programming covers from screens to controller tags.

What the touch panel computer runs #

A touch panel computer is a computer: processor, memory, an operating system, and communication interfaces. The runtime is an application built for that specific operating system and hardware, which is why the engineering tool needs the target model and firmware before it compiles. At power-up the panel loads the runtime and starts exchanging data with the controller.

Operating systems differ across panel generations. Windows CE was long a common choice on operator panels and still runs legacy hardware; a runtime compiled for it will not execute on a full Windows or an Android panel. If you inherit a running panel and need to know what it loads, how to find the runtime file an HMI terminal actually loads identifies it. And if you are still choosing the station itself, industrial panel PCs and touchscreen computers are the class of machine that carries a runtime at the machine — decide the computer and its operating system first, then pick an editor that targets it.

How the panel talks to the controller #

Choose the communication from four facts: the interfaces physically present on the panel and on the controller, the transfer speed the application needs, the volume of data exchanged, and the cost of the whole application. The candidate categories are Ethernet, RS-232, CAN bus, fieldbus and Profibus — match the one your controller already speaks.

A connector proves nothing by itself. What moves the data is a protocol on top of the medium, a driver in the runtime that speaks that protocol to that controller family, and a variable mapping that puts each screen object on the right controller address. Verify those three — and the cable — before drawing a single screen, because a screen drawn against an unverified mapping is artwork until the data arrives.

Following one temperature from controller to screen and back #

Take the starter case behind most first HMI projects: one live value on the screen, one setpoint the operator can change.

Inputs:

  • 1 displayed value: the temperature process variable held by the control logic — the number the synoptic shows.
  • 1 written value: the setpoint the operator enters on the same screen.
  • 2 layer boundaries in each direction: control logic to communication, and communication to runtime, taken from the four-layer stack above.

Rule in words: the data handoffs you must prove equal the number of data paths times the boundaries each path crosses.

Arithmetic: 2 paths (one read, one write) × 2 boundaries per path = 4 handoffs. Behind those 4 handoffs sit 2 screen objects (1 display, 1 entry) and 2 tag mappings (1 read, 1 write) in 1 driver.

Result: four proven handoffs, two objects, two mappings.

Decision: run one live test per handoff before building the second screen. If the display updates but the entry does nothing, the write pair — 2 of the 4 handoffs — has failed, and the fault is in the mapping or the driver, not the graphics. No screen goes to an operator until the write path is proven.

Questions asked

Is an HMI the same thing as a PLC?

No. The PLC or other controller executes the process logic and owns the variables; the HMI only reads and writes them. Allocate functions accordingly: sequencing, interlocks and anything that keeps the machine safe belong in the logic, and the process design should let the machine run with the HMI offline.

Can one touch panel serve more than one controller?

Yes, when the panel's documented drivers, physical ports and connection limits cover the combination. Count operator stations by the job each one needs to do, not by the number of controllers. A PC-based runtime can also serve several controllers under the same documented conditions.

Do I need to learn a programming language before building screens?

For most panels, no. The daily work is configuration: placing objects, binding tags, setting user permissions. Scripting appears in some engineering packages for behavior the standard objects cannot express, and in browser-based runtimes those scripts execute on whichever side the runtime assigns them, so treat scripting as an add-on, not the entry ticket.

Why does a value display correctly while a button or setpoint entry does nothing?

Check three things in order: the tag mapping for the write, because a wrong address is the most common cause; the driver's documented support for writes to that controller family; and the control program itself, which may overwrite the setpoint every scan so the write lands and is immediately replaced. The screen is the last place to look.

What is the difference between an HMI and SCADA?

A panel HMI is one operator's window on one machine or line. SCADA is the supervisory layer above it: shared alarms and historians across areas, multiple clients, usually PC-based. The two meet when a panel or PC runtime acts as one client of a larger SCADA system.

Keep reading

  • Selection guide

    Do You Need SCADA Software for a Modbus HMI Project

    No. Modbus only proves a possible data link, so pick the runtime target first: a touch panel programmed by its own editor for machine-side parameter control, or a licensed PC SCADA runtime when the screens must run on a computer. The documented demonstration mode of a Vijeo Citect-class runtime stops after about 15 minutes with live devices, which settles a bench test but not continuous operation.

    HMI and touchscreens

  • How-to

    How to find configuration software for a legacy TP070 touch panel

    A TP070 is configured with TP Designer, the add-on that shipped in the STEP 7 Micro/WIN Toolbox era and runs under Micro/WIN V4 — not with WinCC flexible, ProTool or TIA Portal. Read the order number on the rear label to match the toolset to the panel's firmware generation, source the package through the manufacturer's own channels, and transfer over PPI at 9.6 kbit/s.

    HMI and touchscreens

  • Troubleshooting

    When Only One Touchscreen Icon Responds to Press

    If only one of several icons answers a press, the others are most likely status indicators: they display state but never accept input. Read each object's role in the configuration tool before touching hardware — a healthy screen shows exactly as many responsive icons as it has assigned press actions, and a silent indicator is correct behavior, not a dead touch area.

    HMI and touchscreens