HMI

Operator interfaces measured in frame time and input latency, on the panel the product actually ships with.

Qt and LVGL interfaces built and profiled on the target panel, so the frame rate you see in review is the frame rate that ships.

HMI input-to-display pathWhat an operator judges an HMI on: the delay between touching it and seeing it move. Every stage that can add milliseconds is drawn separately.Touchinput eventUI toolkitQt · LVGLCompositorGPU · buffersPanelrefresh · backlightFrame on glasswhat they seeBudgetmeasured per stage

Scope

What we do

  • HMI development in Qt/QML and LVGL, targeting the shipped SoC and display.
  • Frame-time and input-latency profiling on the real panel, with a stated budget.
  • Display bring-up: LVDS, MIPI-DSI, backlight control, touch integration.
  • Offline-first data models so the interface stays usable when the link drops.
  • Theming and localisation structured for long product lifetimes.
  • Boot-to-first-frame reduction as part of the Linux boot-time work.

Typical stack

  • qt
  • lvgl
  • latency-budget
  • boot-time
  • imx8m
  • am62x
  • rk3588
  • raspberry-pi-cm

Standards worked to

Applicable standards are agreed at the start of a programme and written into the scope. Certificates we hold are shared on request.

Deeper reading: HMI & Vision

Talk to an engineer

Ask about this capability directly — the person who answers has shipped it.

Talk to an engineer