Capability / Human–Machine Interfaces

Make the product easier to understand.

Custom display graphics, embedded firmware, and communication interfaces developed around the equipment. Connect what the user sees with what the product needs to do.

Discuss your application Explore embedded systems

HMI dashboard example from Theta’s August 2023 presentation — Engineering image from Theta’s supplied presentation

HMI / Original interface examples

The interface is part of the product.

Explore the graphics and display examples in Theta’s supplied HMI presentation. Select a view and enlarge the original image.

A visual engineering perspective

Custom graphics and visual states

Use visual hierarchy, status colors, and operating information to shape the product interface.

Layouts and graphics tailored to the equipment
Status indicators and operating values
Different display sizes and visual requirements

HMI / Product architecture

Connect the display.
Integrate the application.

A shared-MCU architecture is one option described in the source material. Select the hardware around both interface and application requirements.

Display & user inputGraphics, commands, operating values, and status.

Shared MCU optionHMI and application firmware on the same processor.

HMI functionsApplication functions

Equipment interfacesCommunication with the rest of the equipment.

Conceptual diagram based on the HMI architecture described in the presentation. Processing resources, timing, memory, and EMC/EMI requirements are evaluated for each product.

Inspect the original display / processor reference matrix

**Display and processor reference matrix**Original selection matrix from Theta HMIs, August 2023, slide 3. This is the source’s reference, not a universal minimum-CPU specification; memory, graphics workload, interfaces, and the complete application also affect platform selection.

HMI / Communication

The interface needs
to speak the product’s language.

Protocols listed in the supplied HMI material. Their use and implementation are selected for the target equipment.

Wired interfaces

Integrate with the equipment.

CAN / J1939-based protocolsUARTRS485 / Modbus

Coordinate HMI commands, status information, and application functions with the equipment interfaces.

Wireless interfaces

Evaluate wireless connections.

2.4 GHz Wi-Fi · 802.11b/g/nBluetooth 5 LE

Evaluate connectivity, integration, and the communication requirements of the complete product.

Engineering approach

From architecture to application.

01 / ENGINEERING APPROACH

Design the interface around the product

Define the operating information, commands, alerts, and visual hierarchy the user needs. Theta’s supplied HMI material describes support for different display sizes and custom graphics.

02 / ENGINEERING APPROACH

Connect the interface to the equipment

The material lists experience with CAN and J1939-based protocols, UART, RS485/Modbus, 2.4 GHz Wi-Fi IEEE 802.11b/g/n, and Bluetooth 5 LE. Select the protocol around the equipment architecture and integration requirements.

Evaluate shared-MCU integration

HMI and application functions can share a microcontroller in an appropriate architecture. Evaluate graphics workload, memory, response time, communication, and application demands before selecting the platform.

04 / ENGINEERING APPROACH

Develop the electronics and firmware together

Theta’s HMI material describes complete hardware design and EMC/EMI testing and validation experience. Product-specific testing and any required certification remain part of the agreed development scope.

What does your next product need to do?

Bring your requirements. Let’s explore the engineering together.

Discuss your application