HMI Control Panel PCB: Human-Machine Interface Design for Industrial Systems

HMI control panel PCB design connects display, touch, power and communication requirements with assembly tests and separate machine safety validation.

An HMI control panel PCB must match the selected display, touch sensor, machine supply and communication software as one assembly. A board that boots on a bench can still lose touch response behind cover glass, reset when the backlight starts, or show stale machine data after a network interruption. Release the board against those operating conditions, with a separate plan for any safety-related function.

A human machine interface panel combines operator input and machine status with the enclosure, cables and software that make them usable. For touch-controller and sensor choices, see HMI PCB design; the focus here is the control-panel mainboard, its manufacturing package and the evidence needed before production. Broader industrial control PCB applications involve additional controller and field-I/O requirements.

What must be defined before HMI control panel design starts?

Freeze the functions and their owners before selecting the processor or layer count. A graphical interface can request an operation, display its status and log a fault without being the component that guarantees a safe machine response.

Function Design input to freeze Evidence needed before release
Display and touch Exact LCD and touch-controller part numbers, pinout, initialization, cover glass and cable Image and touch tests in the assembled panel, including the specified gloves or moisture conditions
Power and recovery Continuous input range, transient profile, rail sequence, peak load and restart behavior Input/rail measurements and power-interruption tests with the production firmware
Machine communication Protocol, device role, peer configuration, update interval and loss-of-link behavior Tests against the intended PLC or controller, including stale data and reconnection
Ordinary buttons and indicators Electrical interface, debounce, labels, illumination and operator workflow Input/output tests and usability checks in the intended environment
Safety-related functions Risk assessment, required risk reduction, complete safety architecture and validation owner Documented safety-function validation; an ordinary PCBA functional test is insufficient

Select an MCU or application processor from the actual UI workload, memory, operating-system support and product lifecycle. A simple fixed-screen interface may not need an application processor and external DDR. A graphics-rich panel may need both. Six or eight layers are possible stackups, not requirements attached to the HMI label; package escape, reference planes, DDR/display routing, power distribution and enclosure space determine the construction.

How should the 24 V input and isolation boundaries be specified?

“24 V industrial supply” does not define the entire input specification. Record continuous minimum and maximum voltage at the panel connector, cable drop, reverse connection, inrush, interruptions and the applicable transient tests. Keep transient survival limits separate from normal operation.

For a concrete manufacturer example, Siemens lists 24 V DC nominal and 19.2–28.8 V permitted supply for the KTP700 Basic in Basic Panels 2nd Generation Operating Instructions, 10/2024, A5E33293231-AE, page 117. That range belongs to the named product; it does not establish an 18–32 V requirement for every HMI. The Siemens manual lists transient conditions separately.

Decide where galvanic isolation is needed from the supply system, connected equipment, ground-potential differences and applicable insulation requirements. Specify both isolated signal paths and their power domains. A converter's isolation rating alone does not define the assembled board's clearance, creepage or safety qualification. TI's TIDA-010009 industrial power reference design, for example, combines buck conversion with isolated flyback rails for communication and digital I/O from a 24 V ±20% PELV input. It is a servo-drive example of domain-specific power design, not a universal HMI circuit.

Test the panel at its maximum declared backlight and processing load inside the intended enclosure. Measure rail droop during startup and load changes, regulator and processor temperatures, and the behavior after brownout. A watchdog or recovery image helps only when its failure detection, reset behavior and recovery path have been tested. Define what happens to commands and displayed status while the HMI is restarting.

How do display interfaces affect bandwidth, routing and fabrication?

Choose RGB, LVDS, MIPI DSI or another interface from the exact display module and host controller, not the screen diagonal. Check pixel format, timing, lane count, voltage levels, connector pinout, initialization and cable limits together. The touch interface is a separate connection even when the touch sensor and LCD arrive as one module.

ST's AN4861 display-interface overview distinguishes parallel DPI/RGB using LTDC from DSI on MCUs that include a DSI Host. Its RGB discussion includes 16–24-bit data configurations. The chosen MCU's peripherals and the module's controller or frame memory determine the data path.

Interface decision What the board designer must confirm What the fabricator needs
Parallel RGB Data width, pixel clock, synchronization and timing margin; simultaneous-switching behavior Layer assignment, reference planes and the released layout constraints
LVDS Host/display format compatibility, link mapping, connector and cable specification Defined differential impedance and approved stackup; controlled pair geometry
MIPI DSI Host and panel lane support, D-PHY requirements, video/command mode and startup sequence Routing and impedance requirements plus an escape plan for the actual packages
Backlight and touch LED string/driver requirements, dimming method, sensor noise and grounding Connector orientation, power-current paths, protection placement and assembly access

MIPI DSI does not by itself require HDI. Use HDI fabrication when package escape, via placement or space justifies the added construction. Microvias do not automatically reduce the total layer count or validate the display link.

A display-resource calculation with explicit assumptions

Assume an 800 × 480 display, 60 frames/s, uncompressed RGB888 (24 bits/pixel) and one full frame stored without row padding. A frame needs:

800 × 480 × 3 = 1,152,000 bytes, or about 1.10 MiB.

Two such buffers need 2,304,000 bytes, about 2.20 MiB. Reading each active pixel once per frame corresponds to 69.12 MB/s of active-pixel data, or 552.96 Mbit/s. These are calculated resource estimates, not measured hardware performance. Rendering, additional layers, memory arbitration and other bus traffic increase the memory requirement; blanking, packet overhead, protocol mode and lane allocation affect the actual link rate. Use the display timing and host documentation to finish that budget rather than treating 552.96 Mbit/s as the required DSI lane rate.

Industrial controller PCB assemblies showing connectors and component placement

Validate touch with the released glass, bezel, grounding and cable assembly. Check coordinates and unintended touches while changing backlight brightness, running communication traffic and applying the specified environmental tests. Resistive and projected-capacitive touch are options with different integration requirements; neither guarantees operation with every glove, liquid or contamination condition.

Where does an ordinary HMI stop and a safety function begin?

An ordinary touch button, keyboard matrix or alarm display must not be assumed to provide an emergency-stop safety channel. If a panel carries an emergency-stop device, its safety-related signal path belongs to the complete machine safety design. The HMI may display its status, but that indication is not proof that the safety function is available.

ISO 13850:2015 addresses emergency-stop design principles; its public scope points to IEC 60204-1 for electrical/electronic realization. The required safety performance follows the machine risk assessment and the applicable standards. Two channels, normally closed contacts, a watchdog or separate PCB traces alone do not establish a Performance Level or SIL. Architecture, component reliability, diagnostics, common-cause failures, software and validation must be considered together. Pilz's functional-safety overview illustrates those separate inputs.

Keep three actions distinct: acknowledging an HMI alarm, resetting an operated emergency-stop device and starting the machine again. Pilz's emergency-stop reset explanation states that reset is an intentional action at the device that initiated the stop and must not automatically restart the machine. Any additional reset arrangement needs assessment in the machine context. Emergency stop is a complementary protective measure, not a replacement for other safeguarding.

Safety PLCs and safety communication can be part of a validated architecture; processor or network use is not automatically disqualifying. Conversely, ordinary Ethernet or a separate button board does not become safety-rated through physical separation. Assign the safety design and validation to the responsible machine engineering team, and keep the PCBA supplier's agreed manufacturing and test scope explicit.

For ordinary controls, specify labels, colors, tactile behavior and access requirements from the applicable machine conventions. Do not reduce the full operator-interface specification to a universal green-start/red-stop rule. Physical buttons can remain useful with gloves or during a display fault, but their availability and electrical function still need testing.

What must be agreed for PLC and industrial-network communication?

A PHY, magnetics and an RJ45 connector provide only part of an Ethernet implementation. Freeze the protocol stack, licensed software where applicable, device role, supported functions and peer configuration. A communication test must exercise the production firmware, not merely show a link LED.

PROFINET has different implementation routes: PI describes software stacks on standard Ethernet microcontrollers and hardware-supported IRT options. The required real-time and synchronization behavior determines the implementation; hardware timestamping is not a blanket requirement for every HMI using PROFINET.

For EtherNet/IP, the ODVA technology overview distinguishes explicit messaging from real-time I/O communication and identifies services such as CIP Sync and CIP Motion. Reading status and writing setpoints does not automatically require the same synchronization architecture as coordinated motion. PCB assembly also does not constitute protocol certification of the completed device.

For Modbus, specify TCP or serial transport, client/server roles, register map, data types, byte order, timeout and retry behavior. For RS-485 or CAN, specify the transceiver, bus topology, termination, biasing where required, grounding and isolation requirements. A matching connector is not sufficient evidence of interoperability.

Record how HMI control panels identify stale values, reject or acknowledge commands and recover after loss of communication. Test with the actual controller configuration, including power cycling either end, cable disconnection and network load. Set measurable update and recovery limits from the application rather than borrowing a generic “real-time” claim.

What should the manufacturing and release package contain?

HILPCB's HMI integration covers display installation, FPC strain relief, image/backlight verification, touch calibration and small-batch-to-volume display integration. Board options include HDI microvias, VIPPO and 0.5 mm BGA/DFN assembly. Each interface and display is checked against its selected module and project test plan.

HILPCB’s published service ranges include ±5% impedance control for multilayer PCB fabrication and 0201 passives (imperial designation; 0.6 × 0.3 mm) and 0.4 mm-pitch packages for SMT assembly. Request confirmation for the released design: the actual stackup, package, land pattern, solder mask, stencil, board support, inspection and rework access must be reviewed. Carry the confirmed scope into the quotation and acceptance plan. A coupon impedance result supports the specified fabrication target; it does not demonstrate that a complete DDR, display or Ethernet channel operates correctly.

For procurement, turnkey assembly addresses component sourcing and PCBA build scope. Enclosure, cable, firmware and system integration belong in an agreed box-build assembly scope. Specify whether display installation, touch calibration and optical bonding are required, and obtain explicit confirmation of the work and acceptance criteria. Gasket installation alone does not establish an IP rating; validate the complete enclosure, connectors and installed panel under the chosen ingress-protection test plan.

Release item Submit with the RFQ or build release Request as evidence
Fabrication definition Gerber/ODB++, drill files, stackup, materials, finish, impedance nets and tolerance Approved fabrication drawing and agreed electrical/coupon test records
Assembly definition BOM with manufacturer part numbers, CPL, polarity/DNP details, panel and mechanical drawings First-article findings, agreed SPI/AOI and selected X-ray coverage; defect disposition
Display and touch assembly Exact part numbers/revisions, cables, glass, mounting details and connection instructions Agreed image, backlight and touch checks on the released assembly
Firmware and communications Approved image/version, programming procedure, configuration and controller test setup Programming identity and functional results tied to unit or lot identification
Failure and recovery behavior Supply limits, reset sequence, communication timeout and retained-data rules Results for specified power-loss, restart and link-loss scenarios
System qualification Installation configuration, environmental profile, EMC/IP targets and safety responsibility Separate qualification reports for the final system and its approved configuration

Before volume release, freeze substitutions as well as the preferred BOM. An alternative display with the same diagonal size can change pinout, timing, initialization or touch behavior. A memory or regulator substitution can affect boot and power sequencing. Specify which changes require engineering approval and repeated tests.

Send the PCB files, BOM, assembly drawings, display and touch specifications, firmware/test package, enclosure drawings, quantities and acceptance requirements through the HILPCB quotation form. Identify separately the PCBA build, display integration, box build and system qualification work so the quotation names who owns each result.

Frequently asked questions

Does an HMI control panel PCB always need an isolated power supply?

No single topology applies to every panel. Define the supply and ground domains, connected interfaces and applicable insulation requirements first. Isolation may be needed at particular communication or power boundaries; specify and validate the complete barrier rather than relying only on a converter rating.

Does a larger display require LVDS or a MIPI display require HDI?

Neither follows from that feature alone. Select the interface from the display module and host controller specifications, then check timing, bandwidth, cable and connector requirements. HDI is a fabrication choice driven by package escape and space, not by the name of the display interface.

Can the touchscreen replace the machine emergency-stop device?

An ordinary touchscreen command must not be treated as an emergency-stop safety channel. Any safety-related implementation needs a suitable, validated safety architecture for the machine. Alarm acknowledgement, emergency-stop reset and machine restart remain distinct operations.

What does a functional test prove about a human machine interface panel?

It proves only the functions and conditions covered by the agreed test: for example, firmware identity, display patterns, touch inputs, backlight control and communication with a specified peer. It does not by itself establish EMC compliance, enclosure IP protection or a safety performance level.

What should be fixed before comparing HMI control panel quotations?

Use the same released PCB and BOM revisions, display/touch parts, firmware, sourcing responsibility, quantities and acceptance plan. State whether the price includes PCBA only, display integration or box build, and identify separately any environmental, protocol or safety qualification work.

How do German buyers describe custom HMI panels?

The query "individuelles hmi panel" (German: individual/custom HMI panel) refers to the same build-to-order scope above: an HMI control panel PCB sized to the enclosure, display, and interface set rather than a catalog part. The RFQ inputs and acceptance plan stay identical.