Mitsubishi Electric
Connect Mitsubishi Electric controllers to the ENLYZE Platform.
Mitsubishi Electric is one of the world's leading automation vendors and is especially widespread across Asia. Its controllers have been sold under the MELSEC name since the 1980s. Two product lines have grown out of it: the compact controllers of the FX family (today MELSEC iQ-F) and the modular, rack-based systems, from the MELSEC-A through the MELSEC-Q and MELSEC-L to the current MELSEC iQ-R.
ENLYZE connects Mitsubishi controllers in two ways:
SLMP (SeamLess Message Protocol): Mitsubishi's proprietary Ethernet protocol from the MC protocol family. It is the recommended connection for all controllers with an Ethernet interface and runs over TCP (default port
5001). Connections are made through the SLMP connector.MELSEC serial: for older compact controllers of the FX family without an Ethernet interface. The connection is made through the controller's programming or RS interface.
The manufacturer alone is not decisive, but rather the specific device and the available interface. Controllers without an integrated Ethernet interface (such as older FX controllers or modular CPUs without an Ethernet module) can only be connected via SLMP if they are extended with a corresponding network module (e.g. FX5-ENET, QJ71E71, RJ71EN71). Otherwise the connection is made serially.
Prerequisite: knowledge of the memory areas
Mitsubishi controllers address data through device codes (e.g. D for data registers, M for internal relays, X / Y for inputs and outputs) rather than symbolic tags. To record the right variables, we therefore need the relevant device addresses of the controller. There are two ways to obtain them:
The machine manufacturer or controller programmer tells us the relevant device addresses directly.
We receive the controller's project file (GX Works2 or GX Works3) and derive the device addresses from it.
Device overview
The following table gives an overview of the Mitsubishi families and typical devices. The Generation column distinguishes the compact FX line from the modular systems and names the associated programming software. The Recommended connector column names the connector used for the connection. The Status column indicates whether we have already connected the family in the field.
MELSEC FX3
FX3U, FX3UC
Compact (GX Works2)
MELSEC serial
✅ Supported
MELSEC FX (legacy)
FX2N, FX2NC, FX1N, FX1S, FX0N
Compact (legacy)
MELSEC serial
✅ Supported
MELSEC FX3 (others)
FX3G, FX3GE, FX3GC, FX3S
Compact (GX Works2)
MELSEC serial
🧪 Likely possible, not yet field-tested
MELSEC iQ-R
R04, R08, R16, R32, R120 (CPU)
Modular (GX Works3)
🧪 Likely possible, not yet field-tested
MELSEC-Q
Q03UD(E), Q06UDH, Q13UDH, Q26UDH, QnA
Modular (GX Works2)
🧪 Likely possible, not yet field-tested
MELSEC-A / QnA
A1S, A2N, A3N, AnS, Q2AS
Legacy
MC protocol (Ethernet module)
🧪 Likely possible, not yet field-tested
Rule of thumb: connect controllers with an Ethernet interface via SLMP (TCP, port 5001). Connect older FX compact controllers without Ethernet (FX2N, FX3U) through the serial programming interface. So far we have field-tested the FX5U (SLMP) as well as the FX2N and FX3U (serial).
The modular families MELSEC iQ-R, MELSEC-Q, and MELSEC-L, as well as the remaining FX3 variants and the older MELSEC-A, are likely connectable via SLMP or the MC protocol but have not yet been connected by us in the field. If you want to connect such a device, feel free to contact us at support@enlyze.com so we can check the connection together.
If you have any questions, feel free to contact us at support@enlyze.com.
Last updated