IMDTouchKnowledge BaseShop main store

Explainer

Is There One Software That Programs Every HMI Panel

HMI and touchscreens Published 7 min read

Short answer

No single software programs every HMI panel. Each manufacturer ties its panels to its own engineering tool, and one maker can use a different tool per panel family. Identify the panel from its nameplate, confirm the editor against the manufacturer's documentation, and plan on one editor per panel family.

On this page
  1. Why each manufacturer has its own editor
  2. The nameplate decides the software, not a suggestion
  3. The HMI editor and the PLC tool are separate jobs
  4. What looks like a universal tool, and why it is not
  5. Four gates before you install or buy anything
  6. A worked example: one line, five panels
  7. Back up the running application before you edit
  8. The decision, case by case
  9. Questions asked

No. Every HMI manufacturer ties its panels to its own engineering software, and no tool on the market edits and downloads to all of them. The editor is decided by the nameplate — manufacturer, exact model designation, hardware revision — not by what worked on another panel or what a brand name resembles. A tool named in passing for one manufacturer's panels proves nothing about a panel built by a different one. The committed rule: read the nameplate, confirm the editor and its release in that manufacturer's documentation for that exact model, and keep the HMI editor separate from the PLC programming tool. Plan on one engineering tool per panel family, and treat any claim of a single program covering everything as a confusion between a common tool and a universal one.

Why each manufacturer has its own editor #

An HMI panel executes a runtime the manufacturer built into the product. The engineering tool compiles your screens, alarms, tag database and communication settings into that runtime, and every release of the tool documents which panel models and revisions it can build for. That supported-target list is the product boundary: outside it, the tool neither addresses the panel nor opens its project.

Nothing in the standards changes this. IEC 61131-3 defines the standard programming languages for PLCs and says nothing about HMI projects; no standard defines a common, cross-vendor HMI project format. Even on the PLC side, where the languages are standardized, each vendor's suite compiles only to its own controllers. The one-program-for-everything exists neither in the market nor in the standards.

Panel family Engineering tool
Weintek HMI panels EasyBuilder Pro
Rockwell PanelView 800 Connected Components Workbench
Rockwell PanelView Plus FactoryTalk View Studio for Machine Edition
Rockwell PanelView 5000 Studio 5000 View Designer
Schneider Electric HMI panels and industrial PCs Schneider's HMI configuration software; Vijeo Designer for the families it covers

One row per family is the point. Rockwell alone needs three different tools across three panel families, so even a single-manufacturer plant can hold several editors. Pro-face ships its own HMI application-creation software, and other makers do the same. For the full pairing of makers to tools, start with which HMI software works with which HMI panel hardware.

The nameplate decides the software, not a suggestion #

Write down four items before any software question: the manufacturer's full name, the complete model designation, the hardware revision from the nameplate, and the runtime or firmware version from the panel's information screen if it is reachable. Confirm the nameplate belongs to the display unit — a controller in the same cabinet has its own nameplate and its own software, and mixing the two is the most common identification error. The broader audit this feeds into is covered in checking HMI engineering software before a panel replacement.

Similar names are not one company. Schleicher and Schneider Electric are separate manufacturers with separate product lines, and an editor recommended because the names sound alike is worth nothing until documentation confirms the exact panel as a supported target. That confusion is precisely how one maker's tool gets suggested for a panel it has never addressed.

Where the documentation does not name an editor, contact the manufacturer's support channel with those four identifiers plus the actual task — edit screens, change controller logic, recover a runtime, or replace hardware — and get the tool name, the compatible release and the license route in writing. A download area that lists manuals but no installer usually means the tool ships through the vendor or its distributors, not that no tool exists.

The HMI editor and the PLC tool are separate jobs #

The HMI editor builds what the operator sees: screens, alarms, navigation and the communication settings toward the controller. The PLC engineering tool builds what the machine executes: logic and hardware configuration. A machine can need both, from different vendors. When one suite contains both editors, the compatibility question does not go away — it is still answered per supported device.

Vendor manuals state the pairing explicitly. The operating manual for the XCx 1100 and XCx 1200 describes a programming setup assembled from MULTIPROG components, an OPC server, add-ons for MULTIPROG and the vendor's own dialog — one environment engineered for that family and no other. Matched environment, matched targets: that is the normal shape of this market.

What looks like a universal tool, and why it is not #

Brand-label software explains most stories of one tool working across two badges. FrameworX, for example, is HMI and SCADA software built to be embedded in a machine and shipped under the builder's own name and logo. One tool can then edit two panels carrying different badges — because they are the same product underneath, not because the tool is universal.

PC-based platforms are the other confusion. Ignition, for instance, develops HMI that runs on your own server and is viewed on any device with a browser. It replaces the proprietary terminal at the machine; it does not open or edit the compiled application inside a vendor's panel. Adopting it is a station-replacement decision, not a way to program the panels you already have.

Open protocols standardize the wire, not the project. A panel can speak Modbus or serve OPC UA — vendor user manuals describe setting up an OPC UA server inside the HMI project and configuring the In(HMI)/Out(PLC) communication parameters there — but that configuration happens in the manufacturer's own editor. The standard covers data exchange between devices; it does nothing to make project files interchangeable.

Four gates before you install or buy anything #

  1. The panel is identified: manufacturer, model, revision and runtime version read from the nameplate and information screen, and confirmed to be the display unit.
  2. The manufacturer's documentation names the engineering tool and the release that supports exactly that model and revision.
  3. The installer and license come from the manufacturer or its distributors.
  4. The tool's supported-target list contains the exact model, checked before anything is connected to the panel.

Gate 4 is where old and regional models fail in practice. That failure has its own handling, and when an HMI model is missing from the programming software walks through the fixes that exist.

A worked example: one line, five panels #

Take an illustrative packaging line with five operator stations: two Weintek panels, one Rockwell PanelView Plus, one Rockwell PanelView 800 and one Schneider Electric HMI.

Count the editors. EasyBuilder Pro covers both Weintek panels: 1. FactoryTalk View Studio for Machine Edition: 1. Connected Components Workbench: 1. Vijeo Designer: 1. Total 1 + 1 + 1 + 1 = 4 editors for 5 panels, or 4 / 5 = 0.8 editors per panel. Count the archives: 5, one per station, because each station keeps its own application even when two share an editor. Note that one manufacturer contributes two of the four tools — the unit that drives the count is the panel family, not the brand and not the station.

What moves the number: each additional distinct family adds exactly one editor, one license and one skill set. Consolidate those five stations onto one family at replacement time and the count drops from 4 to 1, removing three editors and three sets of version tracking. Decision: record the panel family next to every station in the equipment list, hold one working editor installation per family, and treat family consolidation at replacement time as the only real lever on software count.

Back up the running application before you edit #

The application executing on the panel is a compiled runtime. The editable project is a separate set of files that may exist only on an engineer's disk or in the machine's documentation pack, and an upload from the panel — where the vendor supports one — can return a restore image rather than editable source. Upload capability and source recovery are different features, and you do not find out which one you have by experimenting on the only copy.

Before any download, collect the original project with its libraries, graphics and communication configuration, and record the editor version that built it. Reading an old HMI program before panel replacement covers what to extract and how to tell source from runtime image. If project access is protected, use the manufacturer's documented recovery process and read what a reset removes before you start it.

Schedule the first download to a confirmed panel in an approved window with the machine supervised, because a failed or wrong transfer can leave the operator facing a blank station on a running process. Keep the transfer method — serial, Ethernet or USB — a separate decision from the PLC driver; separating HMI transfer method from PLC driver selection keeps the two from being confused.

The decision, case by case #

  • An unidentified panel: nameplate first. No install, no purchase and no download until the manufacturer's documentation names the tool for that exact model and revision.
  • Mixed panel families under one brand: one editor per family, not per brand.
  • Five stations across four families: four editors and five project archives, until consolidation at replacement brings the editors to one.
  • One environment for every station: a PC-based HMI platform serving browser clients — a replacement of the terminals, never an editor for them.

Questions asked

Is one HMI editor license enough for several panels of the same brand?

Not necessarily. License scope is set by the vendor's terms for each tool, and one brand can require several tools: Rockwell alone uses Connected Components Workbench, FactoryTalk View Studio for Machine Edition and Studio 5000 View Designer for different panel families. Count licenses per tool, and confirm each license covers the number of stations or seats you actually program.

Can the PLC programming software create the HMI screens too?

Only when the vendor's suite bundles an HMI editor and your panel appears in its supported-target list. The two jobs are separate products in most plants: logic in the PLC tool, screens in the HMI editor. Some suites share a tag database between the two editors, which moves addresses between them but does not merge the tools.

The panel's manufacturer no longer exists. Is there any tool left that edits it?

Not a current universal one. Treat it as an obsolete-panel problem: preserve every upload and archived project you can find, keep a workstation that still runs the old editor, and plan migration to a supported platform when parts or the editor fail. Brand-label software can carry a product line forward, but only if your panels were built on it.

Does browser-based HMI software count as one program for every panel?

No. Platforms such as Ignition run the HMI on your own server and serve screens to any device with a browser. They replace the proprietary terminal; they do not edit the application compiled inside it. The gain is one environment for new stations, and the display hardware stops being the compatibility question, but existing panels still need their original editors.

Can I check whether an editor supports my panel before buying it?

Yes, and the check is documentary. Each release documents its supported targets, and the tool's new-project dialog lists the same exact models. Read that list against your nameplate model and revision. If the model is absent, the tool does not support it, whatever the recommendation said, and a purchase will not change the target list.

Keep reading

  • Comparison

    Which HMI Software Works With Which HMI Panel Hardware

    Match the terminal's exact model and firmware to its engineering tool. PanelView 800 uses Connected Components Workbench, PanelView Plus uses FactoryTalk View Studio for Machine Edition, and PanelView 5000 uses Studio 5000 View Designer. Check PLC driver support separately.

    HMI and touchscreens

  • How-to

    Reading an old HMI program before panel replacement

    The software family that programs the replacement panel cannot read the old one: an EA9-family release such as C-more 6.40 will not open or upload a project from an EA7-T8C. Install the EA7-family software, read the project with it, keep the original upload untouched, and convert only a copy through the documented path to the EA9-T8CL.

    HMI and touchscreens

  • Troubleshooting

    Why HMI Programming Software Needs a Ping Reply to Download

    The programming software sends an ICMP echo request to the panel and aborts the download when the reply is blocked, even while remote viewing still works. Ask for one scoped firewall rule: the echo request from your authorized source to the panel address, with its stateful reply. Do not disable the firewall or fake the reply.

    HMI and touchscreens