01
Status & control
Define the information hierarchy for state, progress, alarms and operator actions.
Energy & Charging Equipment
Make energy status and control clear at the point of use.
Charging and energy equipment HMIs combine status, control, connectivity and service workflows. The right platform depends on display environment, UI complexity and the surrounding power-system architecture.
What matters first
Clarify the product constraints before choosing components.
Use these questions to narrow the HMI workload, then compare compute, display, GUI and engineering paths.
02
Display environment
Set brightness, touch and mechanical requirements from the installation environment.
03
Connectivity
Map local control, network, service and backend connections before hardware selection.
04
Service workflow
Plan diagnostics, updates and maintenance access alongside the end-user UI.
Architecture options
Let the workload decide the architecture class.
A focused serial or MCU interface, a richer RTOS HMI and an application-class Linux system solve different problems. The HMI Selector uses the rest of your brief to narrow the starting point.
Smart Display / Compact MCU
For focused control and status interfaces where integration effort, startup and cost matter strongly.
Performance RTOS HMI
For richer graphics, more pages and broader I/O while retaining an embedded real-time product model.
Embedded Linux HMI
For complex workflows, larger software stacks, networking, media or application-style functionality.
Reference evaluation path
Turn the application brief into a hardware and software comparison.
No single architecture is assumed for this application. Use the workflow, display, UI, interfaces and project constraints to compare the practical HMI paths.
1 · Status + control workflow2 · Display environment + connectivity3 · Compute / OS / GUI comparison4 · Prototype system integration on target hardware
Planning a product in this category?
Start with the application brief, not a fixed processor.
Use the selector for an initial architecture direction, or share the project constraints for a more specific discussion.