Design Considerations for Multimedia HMI

In today’s world, humans use human-machine-interface (HMI) in their daily lives with ease.

Whether using your cellular phone or going to the bank’s Automated-Teller-Machine (ATM) we use HMI without even thinking about it.

With each day, consumers are getting more and more sophisticated and are increasingly migrating towards higher-performance HMI expecting an intuitive, fast and effective experience with any devices they encounter.

A properly designed touchscreen Multimedia HMI interface between a machine and its human operator greatly impacts efficiency and ease of use.  Often, the HMI software is paired up with a selected hardware which combines video and sound capabilities with embedded communications interfaces.

Our Clients continually update their HMI to differentiate and set themselves apart from the crowd.

Careful planning, time, the right set of tools, and a can-do attitude are the key ingredients that development teams need to create a winning, next-generation HMI or to completely re-innovate an older product.

For a properly designed HMI interface, one should start the HMI design process with a clear definition of the operational and functional requirements, as well as any communication and interaction requirements that are needed to interface with other devices or systems.

Since the HMI interface provides the controls for a human user to operate a machine, system, or instrument, a clear understanding/definition of these elements is essential.  And because a user machine interface is composed of HMI that interfaces machines with physical input hardware such as keyboards, mice, or game pads, and output hardware such as computer monitors, speakers, and printers, effective implementation requires discipline in design requirements.

Once the operational/functional requirements are nailed down, the next logical step would be to work with the software team on creating a storyboard to define the human interactive experience. A good starting point could be a simple text-based outline documenting each screen’s proposed behavior.

With time, the client can work with the designer to add details for each screen such as: number of buttons, buttons shapes and colors, status information, set points/limits thresholds, message information for various faults and errors warnings and other details that are needed for an intuitive and effective/enjoyable experience.

The designer can convert these text-based screen definitions into a graphical storyboard for customer review/feedback. From our experience, having more buttons/data on the screen is not always an improvement; overwhelming the user with information is not always a good thing.

Cluttered screens often cause confusion and user rejection. It is always a good idea to engage the client or the end-user during the HMI storyboard design process to get their input and incorporate their feedback and specific requirements.

Deploying a prototype of the HMI as early as practical in the design cycle and requesting the client’s feedback is always the preferred approach. As an HMI creator, never forget that you are building the HMI for a client, so their feedback is always a very valuable input. But also remember that you are designing the HMI for the end user experience as well, so try to make the HMI easy to use and fun to interact with.

On the hardware side, Multimedia HMI systems must be able to interface/interconnect with the control system as well as other surrounding systems.

The HMI controller will connect with the device that is being human user controlled via one or multiple standard interfaces: SPI, I2C, RS-232, RS-485, USB, Ethernet, CAN, GPIO and others. The selected hardware also needs to meet environmental requirements, such as exposure to high/low temperature extremes and other potential surrounding harsh environments like grease, moisture, or harsh chemicals.

The display, which falls under the hardware requirements, needs to be selected with use requirements in mind such as:  size, number of pixels, viewing angle, luminance/brightness, hardware interface, operating temperature, cover glass thickness, LED life time, or other potential requirements. Hardware also need to accommodate Multimedia requirements.

Video storage as well as record and playback capabilities must be implemented on the software side while the sound output/input interfaces must be present on the hardware side.  Multimedia HMI transforms the application from static images to active motion with video capabilities.

Venture Embedded Solutions Technology (VEST) products provide a host of video and audio capabilities with embedded communications interfaces to provide an unparalleled multimedia platform. VEST solutions strike a comfortable balance between the Multimedia HMI and the hardware platform driving it while also fitting the most demanding budget.

In Summary:

The above design tips and tricks are only a few aspects of what VEST recommends keeping in mind when designing an HMI interface.

A highly reliable HMI system that delivers an intuitive, fast, cost-effective, and high-performance experience relies on the application of engineering best practices throughout the design process. Developing embedded HMI software may seem like a simple task, but the development time, cost, and maintenance of the deployed applications can be considerably simplified with purchased software.

The look, feel, and ease of use of an HMI can vary widely given all the tools available with modern HMI software.

VEST can help with creating the best HMI experience and potentially offer a substantial return on investment. Time, careful planning, the right set of tools, and a can-do attitude are the key ingredients that development teams need to create a winning, next-generation human machine interface or to completely re-innovate an older product.