News

Mitsubishi Electric has introduced the MELSEC MX Controller, a new programmable automation controller platform designed to combine sequence control, motion processing, and network communication within a single multi-core CPU architecture. The company is positioning the controller as an alternative to machine architectures that traditionally rely on separate PLCs, motion controllers, and communication hardware.

The new platform is aimed at machine builders and system integrators working on applications where synchronized motion, deterministic networking, and conventional PLC control need to operate together. Mitsubishi Electric is particularly targeting sectors such as packaging, material handling, electronics manufacturing, and other automated production environments with increasingly complex motion requirements.

A key feature of the MELSEC MX platform is its scalability. Mitsubishi Electric has divided the range into two families: the MELSEC MX-R for larger systems based on the MELSEC iQ-R hardware architecture, and the MELSEC MX-F for more compact machines using MELSEC iQ-F hardware. Depending on the model, the platform supports between eight and 256 controllable axes.

The MX-R family is designed for larger machines and integrated production lines. Its lineup includes the MXR300-16, MXR300-32, and MXR300-64, supporting 16, 32, and 64 axes respectively. At the upper end of the range, the MXR500-128 and MXR500-256 extend motion capacity to 128 and 256 controllable axes.

All MX-R models support CC-Link IE TSN, Mitsubishi Electric’s industrial Ethernet technology for deterministic communication and synchronized control. The combination of high axis capacity and time-sensitive networking is intended to address applications where motion coordination and network timing can directly affect machine performance.

The smaller MELSEC MX-F family targets standalone machines and compact automation systems. CC-Link IE TSN configurations include the MXF100-8-N32 and MXF100-16-N32, supporting eight and 16 axes. Mitsubishi Electric has also identified source-output variants, including the MXF100-8-P32 and MXF100-16-P32, for future availability.

For facilities that have standardized on EtherCAT, Mitsubishi Electric has added the MXF100-8-N32-EC and MXF100-16-N32-EC. These variants provide EtherCAT connectivity while maintaining the same basic MX-F concept, giving machine builders another option when integrating the controller into existing industrial networks.

This architecture is significant because it allows a machine builder to approach different machine sizes with a common control philosophy. Instead of selecting a conventional PLC for sequence logic, a dedicated motion controller for coordinated axes, and additional networking hardware for data exchange, the MX Controller is designed to bring these functions together.

The multi-core CPU is central to this approach. Mitsubishi Electric states that sequence processing, motion control, and network processing can operate simultaneously, allowing different control workloads to be handled within the same controller architecture.

For complex automation projects, this can reduce the number of control devices required inside the electrical cabinet. Fewer controllers can also mean fewer communication interfaces, less inter-device synchronization, and a simpler overall system design. For machine builders, the benefit is not necessarily limited to hardware reduction; maintaining a common programming and engineering environment can also simplify commissioning and future maintenance.

The MELSEC MX Controller is designed to work with Mitsubishi Electric’s existing MELSEC iQ-R and iQ-F modular hardware. This compatibility gives users a way to integrate the new controller technology without necessarily replacing an entire installed control platform. Existing base units, power supplies, and compatible modules can remain part of the system depending on the selected configuration.

That approach could be particularly relevant for manufacturers modernizing established machines. Industrial automation upgrades often involve a balance between new control capabilities and the need to preserve proven I/O, power, and cabinet infrastructure. Compatibility with established MELSEC hardware provides a potential migration path rather than requiring a complete control-system redesign.

The engineering environment is another important part of Mitsubishi Electric’s strategy. The MELSEC MX Controller is programmed using GX Works3, the same engineering software used with Mitsubishi Electric’s iQ-R and iQ-F PLC families.

Combining sequence and motion development in one engineering environment can reduce the complexity associated with projects where PLC programming and motion programming are traditionally handled through separate tools. Engineers can work with a common project structure while developing conventional control logic alongside motion functions.

The platform supports IEC 61131-3 programming languages and PLCopen motion function blocks, which can help engineering teams maintain familiar programming methods and reuse portions of existing application logic. For OEMs producing multiple machine variants, this can be particularly useful when a common software architecture needs to be scaled across different axis counts.

Networking is equally important to the platform. CC-Link IE TSN provides deterministic communication capabilities for applications where synchronized data exchange is important. Mitsubishi Electric has also incorporated EtherCAT into selected MX-F models, allowing the compact controller family to address machines already built around EtherCAT-based field architectures.

The ability to combine real-time control traffic with information-oriented communication is becoming increasingly important as manufacturers connect machine-level automation with higher-level production systems. Modern control platforms are expected to exchange not only I/O and motion data but also production information, diagnostics, operating conditions, and other machine-level data.

Mitsubishi Electric lists OPC UA communication and MES integration among the capabilities of the MELSEC MX platform. These functions extend the controller beyond traditional PLC duties and position it as part of a broader industrial data architecture.

Built-in diagnostics, data logging, and analysis functions also support the growing requirement for more accessible machine information. Rather than treating data collection as a separate layer added after the control system is designed, the MX architecture incorporates information handling into the controller environment.

Cybersecurity is another area Mitsubishi Electric has addressed. The company lists encryption, authentication, and access control capabilities for the platform, with the design intended to support the requirements associated with IEC 62443-4-2.

Industrial cybersecurity has become an increasingly important consideration as PLCs, motion controllers, HMIs, and factory networks become more connected. A controller that combines control and networking functions must protect both operational technology and the data moving between different levels of an automation system.

The MELSEC MX architecture therefore reflects a broader shift in industrial automation toward integrated control platforms. Instead of treating sequence logic, motion, communication, data acquisition, and cybersecurity as completely separate functions, newer controllers are increasingly expected to coordinate these workloads within a common computing environment.

For high-speed packaging equipment, for example, a controller may need to coordinate multiple servo axes while simultaneously managing sensors, machine sequencing, network communication, and production data. Material-handling systems can present similar requirements, particularly where conveyors, robotic mechanisms, and synchronized motion are distributed across a large machine.

Electronics manufacturing presents another potential application area. Production equipment often requires precise motion coordination, repeatable timing, high-speed communication, and detailed machine data. A unified controller architecture can reduce the number of independent control elements while providing a common environment for machine software.

The upper-end MXR500-256, with support for up to 256 controllable axes, demonstrates where Mitsubishi Electric sees the platform fitting into larger automation systems. At the opposite end, the eight-axis MX-F models allow the same overall concept to be applied to smaller standalone machines.

That range could make the MELSEC MX platform attractive to OEMs seeking greater standardization across machine families. A company producing several equipment configurations may be able to use the MX-F architecture for compact machines and move toward MX-R hardware as axis count and system complexity increase.

The introduction also highlights how the boundaries between PLC control and motion control continue to narrow. Historically, complex motion applications often required dedicated controllers or specialized motion modules alongside the main PLC. Advances in multi-core processing and deterministic industrial Ethernet are making it increasingly practical to consolidate those functions.

Mitsubishi Electric’s approach with the MELSEC MX Controller is built around that consolidation. The objective is not simply to increase CPU performance, but to coordinate different control workloads within one platform while maintaining compatibility with the company’s established MELSEC ecosystem.

For automation engineers, the practical value will ultimately depend on application requirements, axis count, network topology, supported motion functions, and compatibility with existing modules and field devices. However, the architecture provides a clear response to the increasing demand for integrated PLC and motion control, particularly in machines where synchronized movement and real-time networking are central to production performance.

The MELSEC MX Controller also places Mitsubishi Electric alongside a wider industrial automation trend in which PLC platforms are evolving into more powerful automation computing platforms. As manufacturers seek to simplify machine architectures while adding motion, data connectivity, and cybersecurity, the traditional separation between PLC, motion controller, and industrial network controller is becoming less pronounced.

For organizations already using MELSEC iQ-R or iQ-F systems, the compatibility with existing hardware may be one of the most important aspects of the new platform. Rather than introducing an entirely separate control ecosystem, Mitsubishi Electric is extending its existing architecture into a controller designed to handle more demanding combinations of logic, motion, networking, and information processing.

The result is a platform intended to give machine builders more flexibility in designing scalable automation systems, from compact eight-axis equipment to large machines requiring coordinated control across hundreds of axes.

For engineers evaluating the MELSEC MX Controller, the key considerations will likely be the required axis count, choice between CC-Link IE TSN and EtherCAT, existing MELSEC hardware, motion-performance requirements, network architecture, and the level of integration required between machine control and higher-level manufacturing systems.

The new platform ultimately represents Mitsubishi Electric’s move toward a more unified automation architecture, where sequence control, coordinated motion, industrial networking, data processing, and cybersecurity can be managed within a common controller and engineering environment.

Official manufacturer reference: Mitsubishi Electric Factory Automation

Written by: Daniel Mercer — An industrial automation technology writer with more than a decade of experience covering PLC architectures, motion systems, industrial Ethernet, and control engineering. His work focuses on translating complex automation developments into practical information for engineers, OEMs, system integrators, and industrial procurement teams.