Panel PCs and displays
Earlier articles
Selection guide
Selecting a Panel PC With Audio Output for an HMI
Select the panel PC by its audio path and its supplied Windows edition, not by screen size. The output must be line level into an amplified speaker or amplifier, Windows must use that output as its default playback device, and the deployed HMI project must run on the edition that actually arrives with the unit. A display under 10 inches is a preference, not a selection criterion.
Selection guide
Choosing Between a Raspberry Pi and a Panel PC for HMI
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.
Selection guide
HMI Panel PC RAM, SSD and Windows Selection Guide
Order 4 GB of RAM as the default: the documented floor of one size lower suits only a panel running a single lightweight runtime such as AdvancedHMI. Take 128 GB of SSD storage unless logs are small or purged quickly, when 64 GB is enough. Order 64-bit Windows 10, ideally the IoT Enterprise LTSC build, and have RAM, SSD and the OS printed on the quotation before the enclosure is cut.
How-to
Running Touch Calibration Without Administrator Rights on a Panel PC
An administrator creates one Scheduled Task with Run with highest privileges that starts the calibration executable, and the operator triggers it with schtasks /run — no credentials, no admin group membership. Before rollout, pass one test: the calibration window must land in the operator's own session, because tasks stored to run whether the user is logged on or not start programs where no window is visible. If the tool needs a visible crosshair, grant the operator write access to the exact key it saves instead.
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.
Comparison
Panel PC HMI or PLC plus HMI for meter data display
Run the meter vendor's software on an industrial panel PC and read the meter directly when the operator screen is the only consumer of the values and the software's driver covers the meter's Modbus link. Put a PLC between meter and screen when the same values feed control logic, alarms or other equipment, and prove either path by interrupting the link to confirm a bad-quality indication instead of a stale number.
How-to
How to Commission USB-VGA Video and Touch for a Native HMI
Commission in three independent branches: the USB-VGA adapter must enumerate with a matching chipset driver, the touchscreen must report correct corner coordinates at the final orientation, and the GUI runtime must launch from the operating account. A working display proves nothing about touch, and both prove nothing about the application.
Troubleshooting
Getting a Touchscreen Working Under a Linux HMI Runtime
A loaded kernel module proves only that the kernel accepted the touchscreen driver. Touch reaches the visualization only when the driver exports events the image's input layer actually reads — typically an event device under /dev/input consumed by the Nano-X or evdev layer — so verify each link before editing configuration. If the driver exports no event interface, no configuration change fixes it.
Troubleshooting
Why HDMI Video Works but USB Touch Does Not on a Panel
A stable HDMI image with dead touch is a USB-path fault. Power the panel from its own supply or an externally powered hub, confirm the host enumerates a supported touch controller family, set the visualization to TargetVisu, and treat misplaced touches as a coordinate-mapping error rather than a touch failure.
Troubleshooting
Troubleshooting a Panel PC HMI Dark Screen After Reboot
Treat the dark screen as a startup-chain fault and measure first: the 24 VDC feed at the HMI terminals under load, then the flashlight test. A faint image means the backlight path; no image anywhere with a good feed means board startup or graphics. The replaced SSD only rules out worn flash if the restored image itself was healthy.
Selection guide
Selecting an IP65 industrial touchscreen for a dusty HMI
Yes, a third-party touchscreen works with a CX5340 and TE2000 build once four checks pass: the IP65 claim covers the surfaces your installation actually exposes, the HMI client's video output matches the monitor input, the touch interface and its driver match the client's operating system, and the panel cutout leaves a sound gasket land. Buy on those four lines, not on the brand.
Troubleshooting
Industrial PC Will Not Boot: Video, POST or SSD Fault
A blank screen proves nothing on a CPU card with no onboard video. Yes, you can clear CMOS without a monitor, but only through the board's documented jumper and only after video works. Split the fault into power, video or SSD boot before changing parts: fit a basic ISA VGA card in a verified slot, read the BIOS, then decide between a settings reset and SSD recovery.