IMDTouchKnowledge BaseShop main store

Selection guide

Choosing Between a Raspberry Pi and a Panel PC for HMI

Panel PCs and displays Published 7 min read

Short answer

Classify the screen first. A Raspberry Pi running a Mono-based HMI is defensible only as a read-only production display with a UPS, read-only storage and a soak test behind it. Any screen that carries commands, setpoints or machine recovery belongs on a fanless industrial panel PC with an SSD, qualified restart and a front-panel IP rating matched to the environment.

On this page
  1. Classify the screen before choosing the computer
  2. When the Raspberry Pi is the right answer
  3. When the decision is a fanless industrial panel PC
  4. Storage endurance: the arithmetic that settles it
  5. Restart behavior is the deciding test
  6. Ingress protection belongs to the assembly, not the touch technology
  7. The decision, case by case
  8. Questions asked

You are choosing a platform for a PC-based HMI and the low-cost option looks tempting: a Raspberry Pi, a touchscreen, and the same HMI application running under Mono. Commit to this rule before anything else: classify the screen, not the computer. A read-only production display can run on a Raspberry Pi if you prove UPS-backed power, read-only storage and unattended restart. A screen that carries commands, setpoints, or the ability to recover a machine goes on a fanless industrial panel PC with an SSD — no exceptions. The sizing floor for that panel PC is an Atom-class CPU with 2 GB of RAM, and at typical HMI logging rates — a 2 kB record every 5 s is about 34.6 MB written per day — drive wear is never the deciding number. The sections below give the qualification steps, the numbers, and the decision for each case.

Classify the screen before choosing the computer #

The platform decision follows from what the plant loses when the screen dies, so classify the screen first and let the hardware follow. Three roles cover nearly every station.

Screen role What you lose when it fails Platform decision
Read-only production display: counts, states, a mirror of live values Operator visibility only; the controller keeps running its logic Raspberry Pi qualifies once power, storage and restart are proven
Operator interface carrying commands and setpoints Control access, and the ability to tell live values from stale ones Fanless industrial panel PC with SSD; controller must fail safely on HMI link loss
Interface needed to recover or restart a machine Downtime stretches until the screen is back Industrial panel PC plus one configured spare and a written swap procedure

Two rules hold on every row. Keep safety functions in the safety control system: an HMI on any computer is not a safety device, and neither platform substitutes for the e-stop chain or an interlock. And the controller must run its logic with the HMI gone — no control decision may wait on a screen refresh.

When the Raspberry Pi is the right answer #

Only the first row. The board-plus-display route earns its place where the screen is informational: counts, states, a mirror of live values. If the need is visibility alone, a read-only web client mirror of an HMI screen can even drop the local runtime. If you do run the application on the board, it runs under Mono, a .NET-compatible runtime — close to .NET, not identical, and field reports include occasional minor incompatibilities. Qualification is therefore the actual project on the actual hardware:

  1. Run the real project with live controller comms — every screen, navigation, alarms, any data entry.
  2. Watch processor, memory and exception counts for growth over hours; resource leaks show up as slow creep.
  3. Soak the station across your longest unattended window, not across a lunch break.
  4. Make the OS storage read-only where the platform allows, and keep logs on a separate partition.
  5. Prove touch under the Linux runtime — touchscreen driver work under a Linux HMI runtime is a task of its own.
  6. Drop the controller connection mid-run and confirm the application recovers.

A fault that appears only under Mono is a runtime-compatibility problem; the same fault under Windows points at the driver or the address configuration first.

When the decision is a fanless industrial panel PC #

Once the screen writes to the controller — commands, setpoints, acknowledgements, recovery — the station has to behave like machine hardware, and a board-plus-display build makes you the enclosure engineer. Choose from industrial panel PCs and you get the whole station as one replaceable unit with a rated front face.

Fanless removes the fan and its filter from the maintenance list; confirm operating temperature with the unit installed and the cabinet door closed, not on a bench. An SSD removes the last moving part and boots fast enough that the station is usable shortly after power returns. For performance, AdvancedHMI is a compiled application, and practitioners report it runs with low CPU load on an Atom-class CPU with 2 GB of RAM. Treat that as the floor for a representative screen set, then size against your real project with the RAM, SSD and Windows sizing guide for an HMI panel PC.

Storage endurance: the arithmetic that settles it #

Storage fails two ways: worn out, or corrupted. Wear is the fear people quote; corruption is the one that bites. Work the numbers with illustrative inputs — one 2 kB record written every 5 s, all day, every day:

  • Records per day: 86,400 s ÷ 5 s = 17,280.
  • Written per day: 17,280 × 2 kB = 34,560 kB ≈ 34.6 MB.
  • Written over a full year of continuous operation: 34.6 MB × 365 ≈ 12.6 GB, which is 0.0126 TB.

Divide the drive's rated endurance in TBW — a datasheet number, never a guess — by 0.0126 TB of annual writes and the result is decades for any rating you will find on an industrial SSD. The OS adds its own writes, so measure the running system, but the conclusion stands: at HMI logging rates, wear is not the risk. Corruption during a power cut is. That is what SSD power-loss protection addresses: onboard capacitors hold the drive up long enough to flush buffered writes and mapping data when supply dies, and some drives continuously prepare for unexpected power loss. Keep the OS and the log on separate partitions so a corrupted log can never stop the boot.

Restart behavior is the deciding test #

Power interruptions are a certainty; the specification is what happens next, with nobody present. The chain has four links — firmware auto-power-on, OS auto-login, runtime auto-start, application watchdog — and you prove it by cutting power mid-write on a bench unit, more than once. On the panel-PC side, pair that chain with an SSD that has power-loss protection. On the Raspberry Pi side, the documented setup guidance for the Mono route calls for a UPS, and a read-only OS carries the station through the cuts the UPS misses. If the screen is how operators recover the machine, add one configured spare and a written swap procedure to the same requirement.

Ingress protection belongs to the assembly, not the touch technology #

The requirement often arrives as 'resistive, so it is waterproof.' Touch technology and ingress protection are separate specifications: a resistive sensor is no more waterproof than a capacitive one. What keeps water out is the front-face rating of the complete mounted assembly — display, bezel, gasket and a cut-out made to the manufacturer's instructions. Under IEC 60529, IP65 is dust-tight and protected against water jets, IP66 is dust-tight against powerful jets, and IP69K adds high-pressure, high-temperature spray for washdown.

Two cautions. No IP code converts into a NEMA type: a Type 4X claim has to be the assembly's marked rating, not arithmetic on an IP number. And the rating covers the front face only — the rear of a panel-mount unit and its connectors live inside the cabinet. If the enemy is dust rather than a hose, selecting an IP65 industrial touchscreen for a dusty HMI is the shorter path. Whatever the sensor type, test with the operators' actual gloves: resistive tolerates most gloves, capacitive glove support is model-dependent.

The decision, case by case #

Commit to the row you are in:

  • Read-only production display, controller independent of the screen: the Raspberry Pi is defensible — UPS, read-only storage, proven auto-restart, and a soak test passed on the real project.
  • Operator interface with commands or setpoints: fanless industrial panel PC, SSD with power-loss protection, front-panel rating for the environment, one configured spare. The board does not graduate into this row by testing harder.
  • The interface that recovers or restarts the machine: the same panel PC, with the spare on the shelf and the swap procedure written before the first failure.

The cheap board wins exactly one case. Everywhere the screen touches the control, the panel PC is the platform that brings the machine back after the power blips.

Questions asked

Will Mono make an HMI application crash after running for weeks?

Mono is a mature .NET-compatible runtime, but it is not a byte-for-byte substitute, so the honest engineering answer is to test your application and make the failures speak. Enable the application's exception logging and the operating system logs before the soak test. If a long-run fault repeats under Mono but not under Windows on .NET, treat it as a runtime incompatibility and replace or avoid the failing control. If it fails on both, the driver and the address configuration come first.

What front-panel IP rating does a washdown HMI actually need?

Match the rating to the cleaning method, not to a round number. IP65 covers dust-tight plus handheld jets, so it suits dry and dusty areas with occasional wipe-down. IP66 adds powerful jets and is the minimum where a hose is used routinely. IP69K exists for high-pressure, hot spray with washdown chemicals. The rating is only valid for the complete mounted assembly with its gasket, so follow the manufacturer's cut-out and clamping instructions.

Can we deploy Raspberry Pi displays and panel PCs in the same plant?

Yes, and that split is the right one: boards where the screen is informational, panel PCs where it writes to the controller. Keep one HMI development package across both so the screens stay maintainable by the same people, and keep the project source in one place. The moment a Raspberry Pi display starts carrying setpoints or commands, replace it with a panel PC rather than hardening it in place.

How do we make a failed HMI swap fast?

Before the first failure, keep one configured spare for each machine-critical station and a written restore procedure: the OS image or recovery media, the HMI runtime installer, the project file, the communication settings and the documented license or activation steps. A swap then takes minutes and one technician, and the machine is displaying again before anyone starts diagnosing the dead unit.

Keep reading

  • Selection guide

    Choosing a Panel PC With PRP Network Redundancy Support

    A Panel PC joins a PRP network only through a documented PRP interface, normally an add-on card in a verified expansion slot, or by sitting behind a RedBox. Two onboard Ethernet ports prove nothing. Confirm the exact computer, slot, card, driver and operating-system combination in writing before ordering, or route the panel through a RedBox.

    Panel PCs and displays

  • Troubleshooting

    Fixing startup splash screen errors on legacy panel PCs

    Corrupted splash screens at power-up on a legacy panel PC come from two graphics-heavy programs initializing in the same boot window. Keep the HMI runtime shortcut in the Startup folder, move the remote-access utility to the desktop, and launch it by hand once the runtime has painted. Then verify flash-disk free space and RAM headroom before trusting the unit in production.

    Panel PCs and displays

  • How-to

    Running One HMI Interface on Multiple Touchscreens From One PC

    One computer can drive four touchscreens without four copies of the interface. Put data and commands in one controller, give every screen its own display instance that subscribes to published state and submits commands to one handler, and verify display outputs and touch mapping per screen before you build any views.

    Panel PCs and displays