How-to
Identify HMI software before replacing an unknown panel PC
Short answer
The model number on a panel PC names the hardware only. Before you buy a replacement, identify the HMI software: record the application name, window title, and version from the operator screen, then work through delivered documentation, installed files, and the machine builder. A matching panel size proves nothing about software compatibility.
On this page
- The model number names the computer, not the application
- Work the four evidence sources in order
- Runtime versus project: what a deployed package really holds
- Separate a display fault from a communication fault
- Match the replacement to the application, not to the old panel
- Restore the interface and prove it
- Questions asked
The model number on a panel PC identifies the hardware, nothing more. The HMI application on it was installed by the machine builder or system integrator, and that package — not the bezel size — decides what you must obtain before any replacement works. Identify it in a fixed order: the operator screen, the delivered documentation, the installed files, then the machine builder. Record the application name, window title, and version before you buy hardware, because a replacement panel of the same size proves nothing about software compatibility.
The model number names the computer, not the application #
A panel PC is general-purpose Windows or Linux hardware. The same computer ships into machines running a commercial HMI runtime and into machines running software the builder wrote in-house; many builders run their own operator interface on a standard panel. The model number therefore tells you only which hardware documentation to request from the PC maker.
Two very different situations follow from identification. A commercial runtime — an information page naming, for example, a WinCC runtime or FactoryTalk View Machine Edition — has a known installer, a documented project format, and a licensing route. A bespoke application has none of that on the panel: its supplier is the machine builder, and only they hold the source. Every later step in this procedure separates those two cases.
Work the four evidence sources in order #
-
The operator screen. Photograph the startup screen, the window title, and the application information or About page while the interface runs, including every version and license string displayed. A machine name, company logo, or machine number identifies the application's supplier faster than the software platform does. If the interface does not start, record the exact message and the point where startup stops; if it starts with missing or stale values, note which values.
-
Delivered documentation and media. Before touching the running installation, search the machine records for the operating-system recovery package, the HMI installation files, the application backup, the license records, and the restoration instructions. Keep the builder's application records separate from the PC hardware documentation: they come from different parties and are requested separately.
-
Installed files on the PC. Without altering the operating-system configuration, read the installed-program list, the startup entries, and the target of the HMI launch shortcut, and write down executable paths and configuration locations. Record the display configuration, the touch-input software, the communication interfaces, and the connected peripherals too: an application can start and still be unusable because touch is misaligned or a required port is absent.
-
The machine builder or integrator. Ask them for the application package, its deployment instructions, and its dependencies, quoting the machine number you photographed. Ask the PC maker separately for the hardware recovery image. Obtain software only through the manufacturer or its authorized distributors.
| What the screen shows | What it identifies | Next check |
|---|---|---|
| A named runtime on the startup or information page | A commercial HMI package | Its project, installer, and license records |
| A machine name, logo, or machine number | The application's supplier | Contact for the application package |
| Desktop appears, HMI never starts | Launch path or startup configuration | Shortcut target and startup entries |
| HMI runs with missing or stale values | Display binding or controller link | Tag quality and driver connection state |
Runtime versus project: what a deployed package really holds #
A deployed runtime often contains only the files needed to execute the interface. The editable project — screens, tags, bindings — is a separate artifact, and it stays with whoever built the machine. A working screen is evidence of behavior, not of recoverability: you can operate what you cannot change.
| Recovery item | Usual location | It decides |
|---|---|---|
| System recovery image and instructions | Delivered media or supplier archive | Whether the old environment can be restored to compatible hardware |
| Application project or deployment package | Machine backup or integrator archive | Whether screens can be edited or only redeployed |
| Runtime installer and its dependencies | Delivered software package | The software environment the replacement must provide |
| License and transfer records | Machine records or software supplier | The authorized activation or migration route |
| Communication configuration | Project and installed driver settings | Whether the controller link and tag addressing survive the move |
The decision by case: with the project you rebuild on compatible hardware; with a deployment package only you redeploy and send every change back to the builder; with a bespoke application the builder is the only source there ever was.
Separate a display fault from a communication fault #
If the interface runs, split display problems from communication problems before migration, so a pre-existing fault is not carried across and blamed on the new hardware. Read the affected object's configured data binding first: a valid tag shown with the wrong value points at the binding, the formatting, or the visibility logic, and the fix belongs in the project through its engineering tools. Bad tag quality or stale values point at the driver: check its connection state and the configured controller address against the controller itself. Many tags failing on one connection implicates the shared path; one wrong value while its neighbors update implicates that single address, its data interpretation, or its screen binding. Record all of it as the acceptance baseline.
Match the replacement to the application, not to the old panel #
The application's documented operating-system requirement comes first: compare it with the operating system the candidate replacement ships with, and treat a mismatch as a stop, not a risk. Resolution comes second, and it is arithmetic. Worked example: the About page reports the application fixed at 1024 × 768 pixels (XGA, a 4:3 format). Its aspect ratio is 1024 ÷ 768 = 1.33. A candidate panel with 1920 × 1080 native resolution (Full HD, 16:9) gives 1920 ÷ 1080 = 1.78. The ratios differ, so the application letterboxes or stretches on that panel unless its runtime rescales — check the application's supported resolutions before ordering. Forced full-screen is no fix: the axes scale differently, 1920 ÷ 1024 = 1.88 horizontally but 1080 ÷ 768 = 1.41 vertically, so circles become ellipses.
Then check touch support, physical mounting, power, and the ports named in the communication configuration. A panel the same size as the old one has answered none of these questions. Builder applications from the XP era or older need the compatibility routes covered in running legacy DOS machine software on XP or Windows 7. When the old unit is beyond repair, replace it with an industrial panel PC that meets the documented operating-system and resolution requirements.
Restore the interface and prove it #
Make a full copy of the existing storage, or remove the drive and shelve it, before any destructive step: the licenses and configuration on that drive are the last evidence you have. After that, a documented full-system restoration is the first choice when the recovery image and a compatible replacement both exist, because it preserves the established environment. A fresh operating-system and application installation is the right route when the supplier provides a complete package for the unit you chose; it also exposes dependencies an old image conceals. Where no image exists at all, choosing an operating system image for an industrial PC walks that decision.
Prove the replacement against the baseline you captured: every screen operators actually use — process values, commands, alarms, recipes, trends — checked against the readings taken before the swap. Order hardware only after the application's name, its package, the license route, the operating-system requirement, and the resolution are written down. If all four evidence sources come back empty, the machine builder is the only remaining source, and no panel purchase changes that.
Questions asked
The panel will not start and the screen shows nothing. Where does identification begin?
Start at the delivered documentation and media, since a dead panel removes the screen. If no records exist, have the panel's storage drive read in another computer without booting or writing to it; a read-only copy preserves license records and configuration files as evidence. In parallel, contact the machine builder with the machine number from the rating plate, because they supplied the application even when they did not build the computer.
Can I clone the old drive straight onto the replacement panel PC?
Only when the replacement is documented as compatible with that image. On different hardware the drivers, an activation tied to the old machine, and the licensed recovery route can all break, leaving you a fault you cannot diagnose. When the supplier provides a complete installation package for the new unit, install fresh instead: it exposes dependencies an old image hides.
Can I edit the screens with only what is installed on the panel?
No. The runtime only executes the interface; editing screens needs the project and the matching engineering software, which is usually licensed separately from the runtime. If the records yield a deployment package but no project, you can restore exactly what runs today, and every change goes back to whoever built the machine.
Might the project still be sitting in a folder on the panel itself?
Sometimes. Builders occasionally leave deployment files or a project copy in the application folder behind the launch shortcut. Look, but treat anything you find as the last copy: copy it off, never overwrite it, and confirm with the builder that it matches the version shown on screen before you rely on it.