01
Information density
Define charts, numeric data, alarms and navigation depth before estimating graphics needs.
Instrumentation HMI solutions
Design an instrumentation HMI around data, workflow and responsiveness.
Instrumentation interfaces often combine dense data, precise controls and long product lifecycles. Architecture decisions should follow the measurement workflow, not just screen size.
Start with requirements
Clarify the HMI workload before choosing the platform.
The goal is not to force every product into one architecture. These are the decisions that narrow the practical options.
02
Control precision
Decide where touch, knobs, keys or mixed input are more appropriate for the workflow.
03
Data interfaces
Map acquisition, storage, logging and external communication requirements early.
Architecture options
Choose the software and compute class from the real workload.
A focused control UI, a graphics-rich real-time interface and an application-style Linux HMI have different engineering and lifecycle trade-offs.
Compact RTOS HMI
For focused instruments with deterministic response and moderate graphics complexity.
Performance RTOS HMI
For richer charts, multiple views and higher display demands without a full Linux stack.
Embedded Linux HMI
For complex applications, networking, file systems and richer UI frameworks.
Hardware + software stack
Evaluate the complete HMI path.
01
Display
Choose resolution from information density and viewing distance, not diagonal size alone.
02
Input
Touch, encoder, keypad or mixed control should match precision and operating conditions.
03
Compute
Size CPU/GPU and memory around worst-case rendering plus acquisition and processing load.
04
GUI & OS
LVGL, Qt, RTOS or Linux should follow workflow complexity and team capability.
05
Storage & logging
Plan data retention, export, update and service requirements.
06
Connectivity
USB, Ethernet, Wi-Fi, Bluetooth or cellular according to instrument integration needs.
Architecture first
Start from workload and workflow.
Display size alone does not determine whether an instrument belongs on MCU/RTOS, a higher-performance real-time platform or embedded Linux.
Reference path
Use architecture decisions to narrow the instrument platform
Start with the data and operator workflow, then use the HMI Selector and architecture guides to compare RTOS and Linux paths before selecting hardware.
Before hardware freeze
Validate what can become expensive later.
01
Data update rate
Test charts and values with realistic acquisition loads.
02
UI responsiveness
Confirm navigation and controls remain responsive during processing and logging.
03
Readability
Validate fonts, contrast and density on the target display.
04
Input accuracy
Test touch targets or physical controls with real operators.
05
Service flow
Define diagnostics, logs, updates and recovery before production.
06
Lifecycle
Align compute, display and storage choices with expected product support life.
Planning a similar product?
Bring a short requirement. Start with the next practical decision.
No complete specification is needed to discuss architecture, evaluation hardware or engineering support.