Quick Answer
A 7-inch industrial HMI (Human Machine Interface) with multi-protocol support provides a ruggedized touchscreen display for monitoring and controlling industrial equipment. It connects simultaneously via Modbus RTU, Modbus TCP, CAN bus, and MQTT, with a unified tag address space across all protocols. Built with the STM32F746 and LVGL graphics framework on a 32MB SDRAM + 800×480 capacitive touch display, it meets IP65 front panel protection and operates from -20°C to +70°C.
https://innovchip.net/wp-content/uploads/2026/06/unsplash_factory-3.jpg
Why We Chose the STM32F746 for Industrial HMI
The STM32F746VGT6 is specifically designed by STMicroelectronics for graphics-intensive embedded applications. Key features that make it ideal for industrial HMI: a built-in Chrom-ART graphics accelerator that offloads 2D blitting operations (copy, fill, blend) from the CPU, reducing graphics rendering time by up to 80%. A hardware JPEG decoder that decompresses a 800×480 JPEG image in approximately 20ms — essential for loading background images, icons, and photographs without perceptible delay. 1MB flash (enough for firmware + UI resources + web server), 320KB SRAM for runtime data, and an LCD-TFT controller with support for up to WSVGA (1024×768) resolution with up to 24-bit color depth.
The 800×480 frame buffer at 16-bit RGB565 color requires 768KB (800×480×2 bytes), which exceeds the STM32F746’s internal SRAM. We connect a 32MB SDRAM (IS42S32800J-6BL, 8M×32, 166 MHz) via the FMC (Flexible Memory Controller) to hold the frame buffer, graphics resources (font tables, image data), and UI widget state. The FMC provides burst access to SDRAM at 166 MHz, which is more than sufficient for 60 Hz display refresh — each frame transfer (768KB at 32-bit bus width) completes in approximately 4.6μs, well within the 16.7ms frame budget.
Display and Touch System
The 7-inch TFT display panel is the AU Optronics G070VN02V1 (or equivalent from Innolux/BOE for volume production). Specifications: 800×480 resolution, 262,144 colors (RGB565), 500:1 contrast ratio, 400 nits typical brightness with LED backlight, wide viewing angle (70°/70°/50°/50°, H/V). For industrial environments, we apply optical bonding between the display panel and the touch sensor — this eliminates the air gap that causes internal reflections, reducing glare by approximately 40% and improving contrast and readability under direct sunlight or bright factory lighting.
The capacitive touch controller is the FocalTech FT5316 (I2C interface, 5-point multi-touch, 10ms response time). We use a 1.1mm thick cover glass (Corning Gorilla Glass or equivalent) with anti-glare (AG) coating and anti-fingerprint (AF) coating. The AG coating is critical for factory environments where operators may have oil, dust, or moisture on their fingers. The FT5316 supports glove operation with our specific cover glass thickness — we validated this with three types of industrial gloves (nitrile, latex, and cotton) during our operator user testing phase.
The LCD backlight is driven by an MP3309 LED driver configured for constant-current mode with PWM brightness dimming (0-100%, 10-bit resolution). The maximum brightness of 400 nits is adequate for most indoor industrial environments. For outdoor installations (e.g., construction equipment, agricultural machinery), we offer a high-brightness variant with a 1000-nit display panel and a thicker cover glass with enhanced optical bonding.
Multi-Protocol Communication Architecture
The HMI communicates with industrial equipment through four protocol channels, each mapped to a dedicated hardware peripheral on the STM32F746:
Channel 1: Modbus RTU — USART1 with DMA reception (IDLE line detection for frame boundary), hardware flow control (RTS/CTS optional), baud rates from 1200 to 115200 bps. The firmware implements both Modbus RTU master (for polling PLCs and instruments) and Modbus RTU slave (for the HMI to respond to external Modbus queries). Standard function codes 01-06, 15-16 are supported, with register mapping configurable through the UI.
Channel 2: Modbus TCP — Ethernet MAC (STM32F746 internal MAC) connected to LAN8720A PHY via RMII. We use LwIP (Lightweight IP) stack version 2.1.3 with raw API for best performance. The Modbus TCP implementation supports up to 10 simultaneous TCP connections, enabling multiple SCADA systems or HMIs to query the same data simultaneously. The Modbus TCP slave server listens on TCP port 502 by default (configurable).
Channel 3: CAN bus — bxCAN peripheral on CAN1, supporting CAN 2.0A (11-bit identifier) and CAN 2.0B (29-bit extended identifier). Maximum bit rate 1 Mbps at 1Mbaud with 16-sample triple-sampling for noise immunity. Our firmware includes a J1939 protocol layer (PGN addressing, transport protocol for multi-frame messages, address claiming) for heavy equipment and vehicle applications. Additionally, we support CANopen with the CiA 301 communication profile for machine control networks.
Channel 4: MQTT — Ethernet or WiFi (via ESP32-WROOM-32 co-processor for wireless HMI variants, connected to STM32F746 via SPI). The MQTT client uses Mosquitto embedded library with mbedTLS for TLS 1.2 encryption. Supports QoS 0 (at-most-once), QoS 1 (at-least-once), and QoS 2 (exactly-once). Configurable publish/subscribe topics, keep-alive interval, and reconnect strategy. Typical use case: publishing alarm events and trend data to a cloud platform while receiving remote setpoint changes.
Unified Tag Address Space
A key architectural feature of our HMI is the unified tag address space across all protocols. The firmware maintains an internal tag database (up to 1000 tags in SDRAM) where each tag has: a symbolic name (e.g., “Pump1_Speed”), a data type (BOOL, INT16, UINT16, INT32, FLOAT, STRING), a current value, a quality flag (good/bad/unknown), and a timestamp.
Each protocol channel is mapped to one or more tags. For example, tag “Pump1_Speed” might be mapped to Modbus RTU slave #1, register 40001 (floating point) on serial port 1, and simultaneously published to MQTT topic “factory/pump1/speed” and read from CAN ID 0x18FEE500 (J1939 PGN 65257 for electronic engine controller 1). When the Modbus RTU channel reads a new value, the tag is updated, and the new value is simultaneously available to the CAN output, the MQTT publish queue, and the UI display — all through the central tag database. This eliminates the need for custom logic to synchronize data between different protocols.
User Interface Framework: LVGL on STM32
We selected LVGL (Light and Versatile Graphics Library, version 8.3) as the UI framework. LVGL is designed specifically for embedded systems — it runs entirely in RAM (no external dependencies, no OS requirement, approximately 32KB code footprint), provides hardware-accelerated rendering through the STM32F7’s Chrom-ART engine, and supports anti-aliased fonts, alpha blending, and smooth animations.
Font rendering for international markets is a critical consideration. Our standard deployment includes Chinese (GB2312, approximately 6,763 characters) and English fonts. A GB2312 font at 16pt (the minimum readable size for industrial operators at arm’s length with safety glasses) requires approximately 1.2MB of storage — this is stored in external SPI flash (W25Q256, 32MB) and loaded into SDRAM on demand using a font cache. The cache holds the most recently used 256 characters (128KB), providing a cache hit rate of approximately 98% during normal operation.
The standard UI configuration includes 12 screens: (1) Main Overview Dashboard — key process variables in large numeric displays with color-coded status indicators. (2) Real-Time Trends — 4-channel strip chart recorder with adjustable time scale (30s, 1min, 5min, 30min, 1hr windows). (3) Alarm Summary — scrollable list of active alarms sorted by priority and time, with acknowledge and silence buttons. (4) Device Status — grid view of all connected devices with online/offline status and communication error counters. (5) System Configuration — network settings, protocol parameters, tag mapping. (6) Diagnostic Screens — communication statistics, memory usage, CPU load, firmware version. (7-12) Custom process screens — configurable per client application.
Industrial-Rated Mechanical Design
The HMI panel is housed in an aluminum die-cast enclosure (ADC12 alloy, wall thickness 3mm) with the following specifications: IP65 front panel protection (dust-tight, protected against water jets from any direction, tested to IEC 60529), panel cutout 187×141mm (standard 7-inch HMI cutout, compatible with mounting holes for Siemens TP700, Weintek MT8071iE, and Delta DOP-B07), mounting depth 48mm behind the front panel surface, weight approximately 1.8 kg.
Power input: 24V DC ±20% (18-29.4V range), with reverse polarity protection (P-MOSFET, no fuse needed), overvoltage protection (TVS diode, 33V clamping), and EMI filter (common-mode choke + X/Y capacitors). Typical power consumption: 4W at full brightness (backlight + MCU + peripherals). The internal 5V rail is generated by an isolated DC-DC converter (Traco Power TEP 24-0512WI, 2W, 1500V isolation) to prevent ground loops between the HMI and the equipment it connects to.
EMC and Environmental Testing
The HMI has been tested to the following standards: EMC immunity: IEC 61000-4-2 ESD ±8kV contact, ±15kV air; IEC 61000-4-3 radiated immunity 10 V/m (80-1000 MHz, AM); IEC 61000-4-4 EFT 2 kV on power, 1 kV on I/O; IEC 61000-4-5 surge 2 kV line-to-line, 4 kV line-to-earth. EMC emissions: CISPR 32 Class B conducted and radiated. Environmental: operating temperature -20°C to +70°C (tested at +85°C ambient for 72 hours during qualification), storage temperature -40°C to +85°C, humidity 5-95% RH non-condensing. Vibration: IEC 60068-2-6, 10-150 Hz, 2g acceleration, 3 axes, 30 minutes per axis.
Engineer’s Notes: UI/UX Lessons from Operator Testing
The most valuable insight from our HMI development came from user testing with 5 factory operators at a pharmaceutical manufacturing plant in Hangzhou. We observed three critical UI requirements that are often overlooked by engineers designing HMIs: First, font size must be at least 16pt for all text content. Operators work at arm’s length (60-80cm from the display) and often wear safety glasses or goggles, which reduce perceived font size by 15-20%. Our initial design used 12pt fonts to fit more data on screen — operators consistently misread values, especially distinguishing “6” from “8” and “3” from “5” at the smaller size.
Second, color coding must follow ISA-101 (Human Machine Interface) standards: red = alarm/stop/critical, yellow = warning/caution/abnormal, green = normal/running/OK, blue = operator input/manual mode, gray = offline/disabled. Our initial design used a “modern” color palette with various shades of blue and gray — operators found it confusing because nothing stood out as “this needs attention now.” After switching to ISA-101 colors, alarm recognition time dropped from an average of 4 seconds to under 1 second.
Third, screen navigation must not require more than 2 taps to reach any information. Our initial design had a hierarchical menu with 3 levels of navigation to reach certain diagnostic screens. Operators found this frustrating during time-critical situations (“I need to check the pump alarm history, but it takes 6 taps to get there”). We redesigned with a persistent bottom navigation bar (4 main sections: Overview, Trends, Alarms, Settings) and a top notification bar for critical alarms. All information is accessible within 2 taps: bottom bar tap + sub-screen tap.
Frequently Asked Questions
Can the HMI UI be customized for our specific process?
Yes, full UI customization is part of our standard development service. We create custom screen layouts based on your process requirements, P&ID (Piping and Instrumentation Diagram) data, company branding, and operator workflow analysis. Customization includes: process-specific widgets (tank level displays with animated fill indication, pump status with rotation animation, conveyor belt animation, piping network diagrams with flow direction indicators), custom color schemes with company colors, multilingual support (we have delivered HMIs in Chinese, English, Spanish, German, Russian, Arabic, and Thai), and alarm notification schemes matching your existing alarm management procedures. The UI development typically takes 4-6 weeks depending on the number of custom screens (standard is 6-8 custom screens beyond the 6 standard screens).
Can it connect to our existing PLC brand?
We support virtually every major PLC brand through our Modbus RTU/TCP and CAN interfaces: Siemens S7-200/300/1200/1500 (via Modbus RTU/TCP or proprietary S7 communication with optional module), Allen-Bradley MicroLogix/ControlLogix/CompactLogix (via Modbus RTU/TCP or EtherNet/IP with optional module), Mitsubishi FX3U/FX5U/Q Series, Omron CJ2M/NJ/NX series, Delta DVP-SS2/SA2/SV2/SX2 series, Schneider Modicon M340/M580/M580 ePAC, and Keyence KV-5000/7000 series. For PLCs that use proprietary Ethernet protocols (EtherNet/IP, PROFINET, CC-Link IE), we offer optional protocol modules that plug into the HMI’s expansion slot. Contact us with your specific PLC model for compatibility confirmation.
What is the delivery timeline for a custom HMI?
For a standard HMI with no UI customization (6 standard screens, English/Chinese fonts, Modbus RTU/TCP + CAN protocols): 4-6 weeks from order to shipment, including hardware production, firmware configuration, functional testing (48-hour burn-in at 70°C), and EMC pre-compliance verification. For a custom UI design with 6-8 additional screens, branding, and multilingual support: 8-12 weeks total (2 weeks requirements and mockup approval, 4-6 weeks UI development and integration, 1-2 weeks testing and validation). We provide weekly demos of the UI development progress via video call for your review and feedback throughout the process.
What is the display lifetime and backlight MTBF?
The TFT LCD panel has a rated lifetime of 50,000 hours at maximum brightness, which corresponds to approximately 5.7 years of continuous 24/7 operation. The LED backlight MTBF is 100,000 hours at nominal current (11.4 years at 24/7). In practice, most industrial HMIs do not run at full 24/7 operation — a typical deployment runs 16 hours/day, 5 days/week, which extends the effective lifetime to approximately 10 years for the panel and 20 years for the backlight. Replacement display modules are available as spare parts.
Is the firmware source code included?
Yes, all firmware source code (STM32 HAL drivers, FreeRTOS configuration, protocol stacks, LVGL UI application, web server) is delivered as part of the project. We use STM32CubeIDE (Eclipse-based, free from STMicroelectronics) as the development environment. The firmware includes Doxygen documentation for all modules, and we provide a 2-day knowledge transfer session (online or on-site) to walk your engineering team through the code architecture and modification procedures. There are no runtime license fees, no code obfuscation, and no lock-in to our services for future modifications.
Need a custom industrial HMI for your project? Contact InnovChip Electronics for specifications, pricing, and a free mockup of your custom UI.