Inovance HMI and Mitsubishi PLC Integration Through Serial and Ethernet Communication

Bridging Mixed-Vendor Automation Systems

Human-machine interfaces continue to shape how operators interact with modern PLC systems. In factories where multiple automation brands coexist, interoperability often matters more than vendor loyalty. Engineers increasingly expect HMIs and controllers from different manufacturers to communicate reliably without extensive custom programming.

One practical example is the integration of an Inovance HMI with Mitsubishi FX-series PLCs. The combination offers a cost-effective approach for machine builders seeking flexible visualization without replacing existing controllers.

For facilities maintaining legacy or mixed-platform equipment, solutions from Mitsubishi PLC ecosystems and modern HMI platforms remain highly relevant. Many retrofit projects also rely on replacement hardware available through specialized Mitsubishi Electric automation inventories and broader industrial HMI and computing platforms.

Hardware Selection Shapes Communication Strategy

The demonstration setup combines a Mitsubishi FX3U PLC with an Inovance IT6000 HMI. Although both devices target compact automation systems, their communication methods differ depending on the application architecture.

Serial communication remains common in smaller standalone machines because of its simplicity and low hardware cost. Ethernet, however, increasingly dominates newer systems because it supports higher data throughput, easier diagnostics, and remote connectivity.

Figure 1. The demonstration system uses an Inovance IT6000 HMI with a Mitsubishi FX3U PLC for basic operator control and monitoring.

Preparing the HMI Development Environment

InoTouch Editor serves as the primary engineering software for the IT6000 family. Engineers must first select the correct panel model, screen orientation, and communication preference before configuring the PLC driver.

Correct hardware identification matters because communication capabilities vary between IT-series models. Ethernet-enabled variants typically include the “E” suffix, while other models support serial communication only.

Figure 2. Engineers configure the HMI model, display orientation, and communication preferences during project initialization.

Why Serial Communication Still Matters

Despite the expansion of Industrial Ethernet, RS-232 and RS-485 remain deeply embedded in machine automation. Small packaging systems, conveyor controls, and retrofit machinery frequently depend on serial links because of their reliability and minimal configuration requirements.

In this setup, the Inovance IT6070E communicates with the FX3U PLC through the COM2 RS-232 interface using a DB9-to-Mini DIN cable arrangement.

Figure 3. COM2 on the IT6000 HMI handles RS-232 communication with the Mitsubishi FX-series controller.

Signal Conversion and Noise Considerations

The FX3U PLC uses an MD8 communication port designed around RS-422 signaling characteristics. Signal conversion between RS-232 and RS-422 helps maintain communication stability in electrically noisy environments.

Many field engineers underestimate cable quality during HMI commissioning. In practice, poor shielding and grounding create intermittent communication faults that appear as software issues.

Ethernet Expands the Role of Compact PLCs

As machine builders demand remote diagnostics and IIoT connectivity, Ethernet communication increasingly replaces traditional serial links. The Mitsubishi FX5U series reflects this transition by integrating Ethernet directly into the controller architecture.

For mixed-vendor integration, Modbus TCP remains the most practical protocol. Although Mitsubishi controllers support SLMP communication, InoTouch Editor currently favors Modbus TCP for interoperability with third-party systems.

Configuring Modbus TCP in InoTouch Editor

Unlike vendor-native communication drivers, Modbus TCP requires explicit register mapping between the PLC and HMI. Engineers must configure the Common Driver inside InoTouch Editor and assign the correct PLC IP address.

Figure 4. Modbus TCP configuration requires correct IP addressing and standard port 502 assignment.

On the PLC side, GX Works 3 manages Ethernet configuration and subnet settings. Matching network parameters between the HMI and PLC prevents communication conflicts during runtime.

Figure 5. Ethernet module parameters inside GX Works 3 define the PLC network identity and communication behavior.

Turning PLC Memory Into Operator Visualization

The true value of an HMI appears when PLC memory becomes visual and interactive. Bit switches and status lamps provide operators with immediate visibility into machine conditions without exposing ladder logic.

In this project, the HMI bit switch writes to Mitsubishi memory address M1, while the bit lamp monitors M0 status feedback.

Figure 6. Device mapping connects HMI objects directly to Mitsubishi PLC internal memory addresses.

Improving Operator Usability

Modern HMIs increasingly focus on usability rather than raw functionality alone. InoTouch Editor includes graphic libraries for buttons, lamps, and indicators, allowing engineers to standardize machine interfaces quickly.

Consistent graphical design reduces operator confusion during maintenance and production changeovers.

Figure 7. Built-in graphical libraries accelerate HMI interface development for industrial applications.

Commissioning and Functional Validation

After completing the design, engineers can download the project to the HMI through USB or Ethernet communication. Functional testing confirms whether the HMI correctly reads and writes PLC memory.

In this demonstration, the HMI pushbutton toggles a physical output lamp through Mitsubishi internal logic using a counter-based latch arrangement.

Figure 8. The download utility transfers the HMI runtime project through Ethernet or USB communication.

Figure 9. The HMI and PLC exchange real-time data during operator pushbutton testing and lamp indication.

The Future of Open Industrial Connectivity

Cross-platform communication has become a defining requirement in industrial automation. Manufacturers no longer design production lines around a single automation vendor. Instead, engineers prioritize flexibility, availability, and lifecycle cost.

Protocols such as Modbus TCP continue to survive because they simplify integration between HMIs, PLCs, drives, and SCADA systems from different manufacturers. Even as OPC UA adoption accelerates, practical field integration still depends heavily on established industrial communication standards.

Author Opinion

Many automation teams focus heavily on controller performance while underestimating HMI interoperability. In reality, the communication layer often determines project success. A stable HMI-to-PLC architecture reduces commissioning delays, simplifies troubleshooting, and extends equipment lifespan across mixed-vendor production lines.

For machine builders balancing performance and cost, the combination of Inovance HMIs and Mitsubishi PLCs offers a practical engineering solution rather than a purely budget-driven compromise.

Daniel Mercer | Senior Industrial Systems Reporter

Daniel Mercer has 14 years of experience covering industrial automation platforms, motion systems, and PLC integration projects. His background includes field commissioning work involving Mitsubishi Electric, Siemens, Beckhoff Automation, and Rockwell-based manufacturing systems across packaging and process industries.