Select Page

When a HMI fails, getting an exact replacement can often be problematic, giving rise to issues with proprietary software and programming. This is why many integrators are now switching to panel PCs instead.

An integrator contacted us recently looking for a specific model of touchscreen HMI for a machine on a manufacturing line. The original unit had failed, and they needed an exact replacement. When we looked into it, the model had been discontinued years ago. The HMI ran proprietary software with a program that could only be loaded onto the same brand of hardware. The PLC inside the cabinet was still running perfectly. The machine itself was fine. But the operator had no way to interact with it.

This is a very common scenario we deal with. A PLC mounted inside an electrical cabinet, protected from dust, heat, moisture and physical contact, will routinely outlast the touchscreen HMI that provides the operator interface. The HMI sits on the outside of the cabinet or on the machine itself, exposed to the production environment and to daily use by operators. LCD backlights degrade. Touchscreens wear or crack. Electronics overheat in enclosures that get hotter than anyone expected. The interface fails while the control system behind it keeps running.

The problem is that replacing the interface is rarely as simple as swapping in a new screen.

HMI Article
The brand lock-in problem

Most dedicated HMI touchscreens are programmed using proprietary software specific to that manufacturer. The HMI program can’t be transferred to a different brand without being completely rewritten and re-tested. When the original model is discontinued, the replacement path is constrained to whatever current model from the same brand can accept the existing program.

If the program can be recovered from the failed unit, either by connecting to it with a PC, removing a memory card, or contacting the company that originally programmed it, then loading it onto a compatible current model may be straightforward. But if the program cannot be recovered, the HMI needs to be reprogrammed from scratch. At that point, the brand constraint disappears because you are starting over regardless, but the cost and time involved increase substantially.

The end customer is often not in a position to handle any of this. They may not know which company programmed the HMI originally, may not have a backup of the program, and may not have the proprietary software tools needed to work with it. The search for the original integrator begins, and if that relationship has lapsed or the integrator has moved on, the recovery becomes significantly harder.

Why backups disappear

The HMI program backup problem follows the same pattern we see with industrial PC documentation. At commissioning, the integrator may have a copy of the program on their development PC. The end customer may receive a USB drive or a folder of project files as part of the handover. But years pass, staff change, and by the time the HMI fails, nobody knows where the backup is or even that one existed.

This is preventable. The HMI program, along with PLC programs, wiring diagrams, and design notes, should be handed over to the end customer in a documented package at commissioning. The end customer should keep one copy inside the controls cabinet and another in a known, accessible location within the organisation. The integrator should retain their own copy as well.

This sounds obvious, and it is. But it’s neglected far more often than it’s practised. The organisations that recover quickly from an HMI failure are almost always the ones where someone took the time to ensure the program backup survived the years between commissioning and failure.

The shift to panel PCs as HMI replacements

Integrators are moving away from dedicated proprietary HMI hardware and instead using standard industrial panel PCs running Windows with SCADA or HMI software packages. The operator gets the same touchscreen interface, but the underlying hardware is a standardised industrial PC rather than a proprietary device.

This changes the replacement equation significantly. When a panel PC fails, the replacement is a standard product available from industrial PC suppliers. The SCADA or HMI software is installed onto the new unit from documented installation media, configured to match the original, and commissioned. There is no brand lock-in on the hardware. The constraint moves to the software, which is typically available from the vendor and can be installed on any compatible PC.

This approach has clear long-term advantages for maintainability. But it only works well if the panel PC is specified, configured and documented properly at the outset. A panel PC used as an HMI replacement needs to be treated as a dedicated industrial appliance, not as a general-purpose Windows computer that happens to have a touchscreen.

Specifying the panel PC for the real environment

A panel PC installed on a machine or mounted in a cabinet door on a factory floor faces the same environmental challenges that wear out dedicated HMIs, and the specification needs to account for them.

Temperature. The temperature inside an enclosure or behind a panel can be much higher than the ambient temperature outside it. The panel PC, including RAM and SSD, needs to be rated for sustained operation at the actual internal temperature, not the ambient room temperature. Wide-temperature-rated components should be specified wherever there is any doubt.

Dust, moisture and washdown. The front panel IP rating needs to match the environment. IP65 is adequate for most factory floor installations where the unit is panel-mounted into a sealed enclosure. For washdown areas or food manufacturing environments, higher ratings or stainless steel bezels may be required.

Touchscreen technology. Resistive touchscreens work reliably with gloved or dirty hands and are not affected by liquids on the screen surface, but the plastic pressure-sensitive surface is less durable than glass. Projected capacitive touchscreens have a rugged glass front and better optical clarity, but can be affected by dirt or liquids on the screen and do not work well with thick gloves, although some models can be adjusted for use with thin gloves. The right choice depends on the operating environment and how operators interact with the screen.

Software and OS lifecycle. Use the latest versions of the SCADA or HMI software and operating system at commissioning. Windows 11 IoT Enterprise LTSC is well suited to this application because it provides a 10-year support lifecycle without feature updates that could disrupt a running system. Starting with current software versions maximises the time before the platform becomes unsupported, which matters when the panel PC may be in service for a decade or longer.

Configuring Windows as an industrial appliance

A panel PC running Windows as an HMI needs to be configured differently from a general-purpose PC. The goal is to make it boot reliably, run the HMI software automatically, and resist the kinds of disruptions that cause problems in unattended or continuous-operation environments.

  • Auto power-on after power loss. Configure the BIOS to automatically power on when mains power is restored. This ensures the PC restarts without manual intervention after a power outage.
  • Automatic logon. Configure the default user account to log on automatically without a password prompt. Restrict the permissions of that account to prevent operators from accessing system settings, installing software, or making changes outside the HMI application.
  • Auto-launch the HMI software. Consider replacing the standard Windows shell with the SCADA or HMI application so it runs automatically at boot, rather than launching from the Windows desktop. As an additional reliability measure, configure Windows so that if the software crashes, Windows automatically relaunches it.
  • Protect the OS partition. Industrial plants can suffer from power trips, and operators often power-cycle equipment when something goes wrong. However suddenly cutting the power to a PC can cause corruption of data on the SSD, risking system failure. Separate the critical operating system partition from any writable data areas, and disable write caches. Then enable the Unified Write Filter on the system partition. This prevents Windows from ever writing anything to the OS partition, protecting it from corruption when power is cut and providing a reliable baseline state at every boot.
  • Lock down the network. Configure firewalls to allow only the specific network traffic the HMI application requires. Disable unnecessary services and remove unwanted software from Windows startup.
  • Control updates. Disable automatic Windows updates. Schedule updates to be applied manually by engineering or IT staff at planned times, so that an unexpected update cannot disrupt a running system.

These configurations turn a standard Windows PC into something that behaves more like a dedicated appliance: it powers on, runs the application and resists disruption. But every one of these settings needs to be documented, because a replacement unit configured with default Windows settings will not behave the same way.

The spare that pays for itself

A configured spare panel PC, loaded with the same OS, software, and settings as the production unit, transforms an HMI failure from a multi-week recovery into a same-day swap. The spare goes in, the system comes back online, and the faulty unit is sent for repair without any production impact.

The spare should be purchased and configured at the same time as the primary unit, while the specification, software, and components are all current and available. Buying a spare years later risks finding that the panel PC model has changed, the software version has moved on, or component prices have increased. All of these are easier and cheaper to deal with at procurement time than after a failure.

Document everything

The full configuration of the panel PC, including hardware specification, OS version and licence, BIOS settings, Windows configuration changes, network settings, software versions, and all the application-specific settings, needs to be documented and handed over to the end customer. A backup disk image of the fully configured system should be created and stored alongside the documentation.

This documentation is what allows someone to replicate the system five or ten years from now, when the people who commissioned it have moved on. Without it, the replacement of a failed panel PC becomes the same forensic exercise as replacing a failed proprietary HMI, just with different components.

How ESIS can help

We supply industrial panel PCs and fanless PCs used as HMI and SCADA platforms across manufacturing, utilities, and infrastructure. We understand the specification, configuration, and lifecycle considerations that determine whether a panel PC serves reliably as an industrial appliance or becomes a maintenance problem.

Whether you are replacing a failed HMI, transitioning from proprietary hardware to a panel PC platform, or specifying a new operator interface for a control system, we can help you select the right hardware and plan for long-term maintainability.

Contact us to discuss how you can adopt panel PCs to replace HMIs.

Call Now Button