📡 PLC & Ethernet ⏱ 12 min read • Updated 2026-10-26

SLMP (MC Protocol 3E/4E) Binary & ASCII Packet Frame Specification

Complete byte-level reference for Mitsubishi Electric SLMP (Seamless Message Protocol) and MC Protocol 3E/4E frames over TCP/UDP, covering subheaders, network routing fields, batch read/write commands, and end-code diagnostics.
Interactive Workstation Available: Test the protocols and algorithms covered in this guide live in your browser using Melsec Monitor & PLC Studio.
Launch Melsec Monitor & PLC Studio ➔

Seamless Message Protocol (SLMP) is the standardized industrial Ethernet application-layer protocol developed by the CC-Link Partner Association (CLPA) and Mitsubishi Electric. It enables deterministic client-server communication between supervisory workstations (HMIs, SCADA, edge gateways, and diagnostic tools) and MELSEC programmable logic controllers (iQ-R, iQ-F, Q, L, and FX5U series) over standard TCP/IP and UDP/IP sockets without intermediate OPC servers or proprietary driver stacks.

In factory commissioning, understanding the exact byte layout of MC Protocol 3E frames (inherited from the QnA series) and 4E frames (which prepend a 16-bit sequence number for multi-threaded socket multiplexing) is essential for diagnosing packet timeouts, endianness reversals, and end-code rejections. This engineering guide details the complete binary and ASCII frame structures, routing headers, command codes, and wire-level byte ordering required to build high-throughput PLC communication engines.

1. Architectural Comparison: 3E Frame vs. 4E Frame

Both 3E and 4E frames share identical network routing headers, monitoring timers, command codes, and payload structures. The sole structural difference is the Subheader and the inclusion of a 2-byte (binary) or 4-character (ASCII) Serial Number in the 4E frame. When an industrial PC or hardware bridge dispatches concurrent asynchronous requests over a single TCP socket or stateless UDP port, the 4E serial number allows the client parser to match out-of-order PLC responses back to their originating request promises.

Frame Field 3E Binary Size 4E Binary Size 3E ASCII Size Standard Value (Hex) & Engineering Role
Request Subheader 2 Bytes 2 Bytes 4 Chars 50 00 (3E Binary) / 54 00 (4E Binary). Identifies frame format to the PLC Ethernet module.
Serial Number Omitted 2 Bytes (LE) Omitted (4E: 4 Chars) Application-defined transaction ID (0x0000–0xFFFF), echoed verbatim in the response frame.
Reserved Field Omitted 2 Bytes Omitted (4E: 4 Chars) Always 00 00. Reserved for future protocol extensions.
Network Number 1 Byte 1 Byte 2 Chars 0x00 for direct local Ethernet connection; 0x01–0xEF for CC-Link IE / MELSECNET routing.
Station Number (PC No.) 1 Byte 1 Byte 2 Chars 0xFF when targeting the directly connected PLC CPU; station index for multi-drop bridging.
Request Destination I/O No. 2 Bytes (LE) 2 Bytes (LE) 4 Chars FF 03 (0x03FF) for the host CPU module; 0x03E0–0x03E3 for redundant or multi-CPU slots.
Destination Multidrop No. 1 Byte 1 Byte 2 Chars 0x00 for standard point-to-point Ethernet links.
Request Data Length 2 Bytes (LE) 2 Bytes (LE) 4 Chars Byte count from the Monitoring Timer field through the end of the request payload.
Monitoring Timer 2 Bytes (LE) 2 Bytes (LE) 4 Chars Wait timeout in 250 ms increments (e.g., 10 00 = 0x0010 = 16 × 250 ms = 4.0 seconds).
Command & Subcommand 4 Bytes (LE) 4 Bytes (LE) 8 Chars Specifies operation (e.g., 01 04 00 00 for 16-bit device batch read on Q/L/FX5U).

2. Binary vs. ASCII Mode Bandwidth and Endianness

MELSEC Ethernet ports (built-in CPU Ethernet or RJ71EN71 communication modules) must be configured in GX Works2/Works3 for either Binary Code Communication or ASCII Code Communication. Sending a binary frame to a port configured for ASCII causes the PLC to misinterpret byte values as invalid hexadecimal characters, resulting in immediate socket closure or error code 0xC059.

  • Binary Mode Efficiency: Every 16-bit word register requires exactly 2 bytes on the wire. Multi-byte integers in the header and payload are transmitted in Little-Endian (Least Significant Byte first) order. For example, reading 100 words starting at D1000 (0x03E8) encodes the head address as E8 03 00 and the point count as 64 00.
  • ASCII Mode Overhead: Every byte is expanded into two uppercase hexadecimal ASCII characters, doubling network bandwidth consumption and increasing CPU serialization overhead on the PLC scan cycle. Moreover, ASCII mode writes numerical fields in human-readable Big-Endian character order ("03E8"), which frequently causes bugs when developers port parsers between modes. For production monitoring, Binary Mode is universally recommended.

3. Core SLMP Command & Subcommand Matrix

Choosing the correct subcommand is critical because Mitsubishi introduced extended 32-bit device addressing in the MELSEC iQ-R and iQ-F (FX5U) generations:

Operation Type Command Q / L Series Subcommand iQ-R / iQ-F Subcommand Address Specification & Notes
Batch Read (Word Units) 0x0401 0x0000 0x0002 0x0000 uses 3-byte device number + 1-byte code; 0x0002 uses 4-byte device number + 2-byte code.
Batch Read (Bit Units) 0x0401 0x0001 0x0003 Returns 2 bit states per byte (upper nibble = first bit, lower nibble = second bit: 0x10, 0x01, 0x11).
Batch Write (Word Units) 0x1401 0x0000 0x0002 Writes contiguous 16-bit registers (up to 960 words per frame on Q/iQ-R).
Random Read (Words & DWords) 0x0403 0x0000 0x0002 Reads up to 192 non-contiguous 16-bit and 32-bit device addresses in a single network roundtrip.
Global Label Read (Symbolic) 0x041C N/A 0x0000 Reads iQ-R global labels by UTF-16LE symbol name without knowing physical register assignments.
Global Label Write (Symbolic) 0x141B N/A 0x0000 Writes typed values directly to iQ-R symbolic global variables and structure members.

4. Wire-Level Dissection: Reading D100 to D104 (3E Binary)

Below is a complete hexadecimal packet capture and byte-by-byte breakdown for reading 5 contiguous words starting at register D100 using a 3E Binary frame (`Subcommand 0x0000`):

# Request Frame (21 Bytes Total)
50 00   # Subheader: 3E Binary Request
00      # Network No.: 0x00 (Local network)
FF      # PC No.: 0xFF (Target connected station)
FF 03   # Destination Module I/O: 0x03FF (Host CPU)
00      # Multidrop Station No.: 0x00
0C 00   # Request Data Length: 0x000C (12 bytes follow)
10 00   # Monitoring Timer: 0x0010 (4 seconds)
01 04   # Command: 0x0401 (Batch Read)
00 00   # Subcommand: 0x0000 (Word units, 24-bit device address)
64 00 00 # Head Device Number: 100 (0x000064 in 3-byte Little-Endian)
A8      # Device Code: 0xA8 (Data Register 'D')
05 00   # Number of Device Points: 5 words (D100..D104)

# Response Frame (21 Bytes Total on Success)
D0 00   # Subheader: 3E Binary Response
00 FF FF 03 00  # Echoed Routing Header
0C 00   # Response Data Length: 12 bytes (2-byte End Code + 10-byte Payload)
00 00   # End Code: 0x0000 (Success - Normal Completion)
E8 03   # D100 = 0x03E8 (1000)
D0 07   # D101 = 0x07D0 (2000)
00 00   # D102 = 0x0000 (0)
FF FF   # D103 = 0xFFFF (-1 signed / 65535 unsigned)
2A 00   # D104 = 0x002A (42)

5. Diagnostic End Codes & Field Troubleshooting

When the PLC rejects a request, the 2-byte End Code immediately following the response data length is non-zero, and the response payload is replaced by a 9-byte error information block. Field engineers should monitor these common SLMP end codes:

  • 0xC059: Command/Subcommand Specification Error — Either Binary/ASCII mode is mismatched on the PLC port, or an iQ-R subcommand (0x0002) was sent to a legacy Q/FX3U PLC.
  • 0xC051 / 0xC052: Device Point Count Out of Range — Requested more than the maximum allowed words per frame (typically 960 words for batch read, 192 points for random read).
  • 0xC056: Address Exceeds Device Boundary — Attempted to read past the upper limit of the configured PLC memory file (e.g., reading D12000 when the CPU parameter ends at D8000).
  • 0x4031 / 0x41C0: Global Label Resolution Failure — Symbolic label does not exist in PLC memory, or "External Device Access" was not checked in the GX Works3 Global Label settings.

Frequently Asked Questions (FAQ)

Q. What is the main difference between MC Protocol 3E and 4E frames?

A 4E frame adds a 2-byte Serial Number and 2-byte Reserved field (4 bytes total in binary mode) right after the subheader (0x5400 instead of 0x5000). The PLC echoes this serial number in its response, enabling asynchronous request-response correlation over shared sockets.

Q. Why does my PLC disconnect immediately or return 0xC059 when sending a valid 3E binary frame?

The target Ethernet port in GX Works2/Works3 is likely set to ASCII Communication Mode instead of Binary Mode, or the PLC CPU series only supports subcommand 0x0000 rather than 0x0002.

Q. How many registers can be polled in a single SLMP 0x0403 Random Read request?

Standard MELSEC Q, L, and iQ-R CPUs allow up to 192 combined word and double-word device points per 0x0403 frame. For symbolic global label communication (0x041C), grouping 20 labels per batch yields optimal stability.

Q. Are 32-bit DINT and REAL (Float) values stored in Big-Endian or Little-Endian across two D registers?

MELSEC PLCs use Little-Endian word and byte ordering: for a 32-bit value at D100, D100 holds the lower 16 bits (low word) and D101 holds the upper 16 bits (high word).

📘 Complete Engineering Guides Directory (16 Technical Articles)