Skip to content

Protocol Encyclopedia

MELSEC and SLMP - communication protocols for Mitsubishi controllers

MELSEC Communication (MC) and SLMP protocols for Mitsubishi MELSEC controllers. 3E/4E frame structure, use cases and security in OT networks.

Józef SulwińskiJózef Sulwiński

Published 5 min read

MELSECSLMPMitsubishiMC ProtocolOT
MELSEC and SLMP - communication protocols for Mitsubishi controllers
Contents
  1. Protocol evolution
  2. Transport
  3. 3E frame structure (SLMP)
  4. MELSEC/SLMP security
  5. Architectural recommendations
  6. Analysis tools
  7. Summary
  8. Sources

MELSEC Communication Protocol (MC Protocol) is a family of communication protocols for the MELSEC series of controllers from Mitsubishi Electric, one of the three dominant PLC manufacturers in Asia (alongside Omron and Keyence). SLMP (Seamless Message Protocol) is a newer, unified communication layer published by the CC-Link Partner Association (CLPA), compatible with MC Protocol and extending it with a coherent interface for devices in the CC-Link IE ecosystem.

In Poland and Europe, MELSEC appears less frequently than Siemens and Rockwell, but it has a significant presence in automotive (Toyota, Nissan, Honda), packaging and production lines delivered by Japanese integrators. An audit of an OT environment that requires full visibility cannot omit MELSEC/SLMP.

Protocol evolution

The history of MC Protocol reflects the evolution of Mitsubishi controllers:

PLC series Protocol Frame format
MELSEC A / A0J2H MC Protocol A-compatible Format 1C
MELSEC QnA, Q, L MC Protocol QnA-compatible Format 3C, 3E
MELSEC iQ-R, iQ-F, Q-series ethernet SLMP (3E-compatible) Format 3E, 4E

The 3E and 4E frames are structurally similar - 4E adds a serial number for matching request/response in asynchronous communication.

Transport

MELSEC/SLMP uses Ethernet communication with ports configured by the user. The recommended range is 1025-4999 or 5010-65534; ports 5000-5009 are reserved by Mitsubishi for system functions.

Transport Notes
TCP Recommended for reliability and error control
UDP Optional for lower overhead in controlled networks

Default ports (frequently seen in configurations):

  • 5007/TCP - typical default MC Protocol port on many Ethernet modules (E71, QJ71, RJ71)
  • 5006/UDP - UDP equivalent
  • 45237/TCP - MELSOFT Communication (GX Works3)

The specific port depends on the communication module model and configuration - in an audit you must verify the current device configuration rather than assume the default port.

3E frame structure (SLMP)

Format 3E - the basic MC/SLMP communication structure:

Field Length Purpose
Subheader 2 bytes 0x5000 (request) or 0xD000 (response)
Network Number 1 byte Target network number (0x00 for local)
PC Number 1 byte Target station address (0xFF for local CPU)
Request Destination Module I/O 2 bytes Target I/O module (0x03FF for CPU)
Request Destination Module Station 1 byte Module station (0x00)
Request Data Length 2 bytes Length of request data
Monitoring Timer 2 bytes Timeout in units of 250 ms
Request Data variable Command code + subcommand + data

Example commands:

Code Operation
0x0401 Batch Read
0x1401 Batch Write
0x0403 Random Read
0x1402 Random Write
0x1620 Remote RUN
0x1621 Remote STOP
0x1630 Remote Reset

MELSEC/SLMP security

WARNING

The standard MC Protocol/SLMP configuration does not require authentication. Access to the communication port allows reading and writing any register in the PLC, changing the operating mode (RUN/STOP), resetting the device and (in some models) overwriting the user program.

Attack vectors:

Attack Impact
Remote STOP command Controller stop, production line downtime
Register manipulation Modification of process setpoints (setpoints, limits)
Program download Replacement of the user program (additionally requires CPU-specific sequences on some CPUs)
Reconnaissance Scanning default ports on the network reveals the topology of the Mitsubishi installation

In newer models (MELSEC iQ-R, iQ-F) Mitsubishi introduced:

  • Password CPU - password required for write and program download operations
  • Access permission management - restriction of commands through an allowlist of operations
  • IP filter - whitelist of IP addresses allowed to communicate with the controller

These features must be actively configured - they are disabled by default.

Architectural recommendations

  1. Closed OT segment for MELSEC - communication between PCs and controllers exclusively in a dedicated VLAN with no access from the IT network
  2. Enable password CPU on newer iQ-R/iQ-F models - minimum for write operations and program download
  3. IP filter on controllers - restrict communication to known engineering stations and HMI
  4. Firewall with MC Protocol port control - block access to ports 5006/5007 (and other ports used) from unauthorized networks
  5. Monitoring of Remote STOP/Reset commands - alert on unusual commands that stop the controller
  6. Segregation of functions - modules for communication with IT networks (MES, historian) should be separate from direct control modules

Analysis tools

Wireshark decodes MC Protocol (filter: melsec).

Open source:

Zeek parsers:

  • Partial support within cisagov/ICSNPP - dedicated parser under development

Production monitoring:

  • Nozomi Guardian, Dragos Platform, Claroty CTD/xDome - MELSEC/SLMP support within their dissectors; semantic coverage (command interpretation) varies between products

Summary

MELSEC/SLMP is a living and evolving ecosystem, present in factories delivered by Japanese integrators. Like other OT protocols from the era of trusted networks, it lacks built-in security mechanisms - newer Mitsubishi models provide optional passwords and IP filters, but activating them remains a deployment decision. In an audit of an automotive environment or an Asian production line, the presence of MELSEC/SLMP should be treated as expected, and the security configuration of the controllers should be actively verified.

Sources

  1. Mitsubishi - MELSEC Communication Protocol Reference Manual - MC Protocol specification
  2. CLPA - SLMP Specification - official SLMP page
  3. plcpeople/mcprotocol - open source implementation
  4. Orange-Cyberdefense/awesome-industrial-protocols - MELSEC - references

Need help in this area?

Our experts will help you assess the risk and plan next steps.

Talk to an expert

We'll discuss scope, methodology, and timeline.

Book a call