🗂️ PLC & Ethernet ⏱ 11 min read • Updated 2026-10-26

Mitsubishi MELSEC iQ-R & iQ-F Device Memory Architecture & Global Label Addressing

Comprehensive engineering reference on Mitsubishi MELSEC bit/word device memory maps (X, Y, M, L, B, D, W, ZR), hexadecimal vs. decimal/octal radix rules, and IEC 61131-3 symbolic global label addressing.
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 ➔

Modern Mitsubishi Electric programmable controllers—spanning the flagship MELSEC iQ-R, compact iQ-F (FX5U/FX5UC), and widely deployed Q/L series—combine classic physical register banks with IEC 61131-3 symbolic memory allocation. When building automated inspection equipment, digital twins, or data acquisition services, misinterpreting a device's numeric radix (Decimal vs. Hexadecimal vs. Octal) or using an incompatible SLMP command for symbolic labels can read the wrong physical memory offset.

This reference details the internal organization of MELSEC bit and word devices, binary SLMP device type codes, data-type alignment rules, and direct symbolic communication using SLMP command 0x041C / 0x141B.

1. Physical Device Memory Classification & Radix Rules

Unlike architectures that use a uniform decimal numbering scheme across all memory banks, MELSEC devices use three distinct numbering radices depending on hardware heritage and network link alignment:

Device Symbol Classification Address Radix Binary SLMP Code Functional Description & Typical Usage
X / Y Bit Device Hexadecimal (Q/iQ-R)
Octal (FX Series)
0x9C (X)
0x9D (Y)
Physical discrete input (X) and output (Y) terminals mapped to I/O modules. Note that FX5U uses octal (X0–X7, X10–X17).
M Bit Device Decimal 0x90 Internal auxiliary relay coils for sequence flags, interlocks, and state machines.
L Bit Device Decimal 0x92 Latch relay backed by battery or non-volatile memory across PLC power cycles.
B Bit Device Hexadecimal 0xA0 Link relay shared across CC-Link IE Controller/Field networks and multi-PLC cyclic data exchange.
D 16-Bit Word Decimal 0xA8 General-purpose Data Register for process variables, recipes, and servo coordinates.
W 16-Bit Word Hexadecimal 0xB4 Link Register for high-speed cyclic word synchronization over industrial Ethernet networks.
R / ZR 16-Bit Word Decimal 0xAF (R)
0xB0 (ZR)
File Register stored in extended SRAM/SD memory. ZR provides continuous linear addressing without bank switching.
SD / SM Word / Bit Decimal 0xA9 (SD)
0x91 (SM)
Special Register and Special Relay holding CPU diagnostics, scan time metrics, and real-time clock values.

2. Bit-in-Word Notation & Digit Specification

Automation engineers frequently pack 16 status flags into a single 16-bit Data Register (e.g., D100.0 through D100.F) or group 16 consecutive bit relays into a 16-bit word using digit-prefixed notation (e.g., K4M100 represents the 16 bits from M100 to M115).

  • Hexadecimal Bit Suffix (D100.A): The bit index after the dot is always evaluated in hexadecimal from 0 (LSB, weight $2^0 = 1$) to F (MSB, weight $2^{15} = 32768$). Since standard SLMP batch read (0x0401) does not accept a fractional bit index on a word device, client drivers read the entire 16-bit word D100 and extract bit $k$ via (word_value >> k) & 1.
  • Nibble Grouping (K1 to K8): Each Kn prefix groups $4 \times n$ consecutive bits. K2M0 spans 8 bits (1 byte: M0–M7), K4M0 spans 16 bits (1 word: M0–M15), and K8M0 spans 32 bits (2 words: M0–M31).

3. Symbolic Global Label Architecture on MELSEC iQ-R

In GX Works3, engineers define structured variables—such as stAxisStatus.rActualPosition or bAutoRunReady[2]—inside the Global Label editor without manually assigning fixed D or M addresses. At compile time, the GX Works3 compiler allocates these symbols in a protected internal label memory area.

To expose global labels to external Ethernet clients, the engineer must check the "Access from External Device" (외부 기기에서 액세스) column in the GX Works3 Global Label table and write the project to the PLC CPU. External clients then communicate using SLMP Command 0x041C (Label Read) and 0x141B (Label Write):

# SLMP 0x041C Global Label Read Request Payload Structure
[Number of Labels: 2 Bytes LE]
[Abbreviation Count: 2 Bytes LE = 0x0000]
For each label:
  [Label Name Character Length: 2 Bytes LE (number of UTF-16 code units)]
  [Label Name String: UTF-16LE encoded bytes (2 bytes per character)]

The PLC response returns a 1-byte Data Type ID, a 1-byte spare field, a 2-byte Read Data Length, and the raw binary value for each requested symbol. Because the PLC resolves the symbol internally, the monitoring software remains 100% immune to memory recompilation shifts when new labels are inserted into the GX Works3 project.

4. Data Type Encoding & Multi-Word Alignment

  • INT (Signed 16-bit) / UINT (Unsigned 16-bit): Occupies 1 word (2 bytes, Little-Endian).
  • DINT (Signed 32-bit) / UDINT (Unsigned 32-bit): Occupies 2 consecutive words (4 bytes, Little-Endian).
  • REAL (Single-Precision IEEE 754 Float): Occupies 2 consecutive words (4 bytes). Care must be taken to filter NaN or denormalized bit patterns when reading uninitialized memory registers.
  • LREAL (Double-Precision IEEE 754 Float): Occupies 4 consecutive words (8 bytes) on iQ-R CPUs.
  • STRING (ASCII / Shift-JIS / UTF-16): Null-terminated byte sequence packed two characters per 16-bit word (low byte = first character, high byte = second character).

Frequently Asked Questions (FAQ)

Q. Why does reading X08 or Y09 fail on a Mitsubishi FX5U (iQ-F) PLC?

FX series PLCs use Octal numbering for physical inputs (X) and outputs (Y). Digits 8 and 9 do not exist in octal; after X07, the next physical input address is X10.

Q. How do I enable SLMP 0x041C Global Label communication in GX Works3?

Open the Global Label setting editor in GX Works3, enable the 'Access from External Device' checkbox for each target label or structure, rebuild the project, and write the program and parameters to the PLC.

Q. What is the difference between R and ZR file registers?

R registers are accessed in 32,768-word banks (R0 to R32767) requiring bank-switching instructions, whereas ZR uses continuous linear addressing (e.g., ZR0 to ZR100000) across the entire file register memory.

Q. How is a 16-bit word's individual bit (like D200.5) written safely without overwriting bits 0..4 and 6..15?

Either use SLMP Random Write in Bit Units (0x1402) if supported by the target module, or perform a read-modify-write cycle where bit 5 is toggled via bitwise OR/AND mask before writing D200 back.

📘 Complete Engineering Guides Directory (16 Technical Articles)