SLMP Connector Concepts

SLMP is also known as Mitsubishi, CCLINK IE, and MELSEC

CC-Link SLMP (Seamless Message Protocol) is an open, Ethernet-based communication protocol developed by Mitsubishi Electric for exchanging data with programmable logic controllers (PLCs) and other industrial devices on a CC-Link or CC-Link IE network.

In practice, this protocol goes by several names. Control and automation engineers most often refer to it as SLMP, its current standardized name, but it is also widely known as MC Protocol (short for MELSEC Communication Protocol) or by CC-Link or CC-Link IE, which is the name of its industrial network.

Regardless of the name used, the protocol serves the same core purpose: allowing FairCom Edge, external devices, SCADA systems, and other controllers to read and write device memory, registers, and I/O on a PLC, device, sensor, or equipment over a standard Ethernet or serial connection, making it a foundational tool for integrating equipment into broader industrial networks.

A variety of devices, sensors, and equipment support this protocol, including PLCs, Inverters and Servos, Digital and Analog I/O devices, Load cell and Indicators, Robots, Process Devices, Sensors, Power Reception and Distribution, Solenoid Valves, Barcode Readers, and HMI devices.
 

"slmpDevice" Codes

Code Name Type Description
X Input Relay Bit Represents physical external inputs wired into the PLC — sensors, switches, limit switches, etc. Reflects the real-world signal state; not writable.
Y Output Relay Bit Represents physical external outputs driven by the PLC — solenoids, contactors, indicator lamps, etc. Writable to control field devices.
M Internal Relay (auxiliary relay) Bit General-purpose internal bit memory used for program logic, flags, and intermediate conditions. Not tied to any physical I/O — purely internal to the CPU's logic.
D Data Register Word (16-bit; pairs combine for 32-bit) General-purpose numeric storage — holds values like setpoints, calculated results, counter/timer current values, and other process data. This is the most commonly used register for general data exchange.
SD Special Register Word System-reserved registers holding CPU/diagnostic information — error codes, scan time, date/time, self-diagnostic status, etc. Mostly read-only status data maintained automatically by the CPU (a few are user-writable for configuration purposes).
W Link Register Word Word-type memory used to hold data exchanged over a data-link network (e.g., CC-Link), functioning as buffer memory for inter-station communication rather than general program storage.
R File Register Word Extended word-storage area, effectively an expansion of the D-register space for applications needing more data storage than the standard register area provides. Historically associated with block-switched memory or a memory card.
ZR Extended File Register Word An extension of the R file-register area that provides continuous, linear addressing across the entire file-register memory space. It avoids the block-switching R normally requires, which makes it easier to address large data sets directly.

Notes

Bit devices (X, Y, M) vs. word devices (D, SD, W, R, ZR) matters for slmpNumberOfPoints — for word devices it counts 16-bit words; for bit devices it counts individual bits, and SLMP has separate read/write commands for bit-unit vs. word-unit access.

Addressing radix differs by device — X, Y, and W are conventionally written/addressed in hexadecimal (e.g., X1F, Y20), while M, D, SD, R, and ZR are decimal. This matters if you're constructing slmpHeadDeviceNumber values programmatically from PLC documentation, since a value written as X1F in the PLC program is hex 0x1F (31 decimal), not literal 1, F.

SD is often paired with a bit-type counterpart called SM (Special Relay) for system status flags rather than system status values.

 

Startup configuration

Verify that the SLMP (CC-Link) service is enabled in the FairCom Edge server:

Edit the services.json file in the config folder.

Locate the "integrationServices" object of the service for the desired platform.

Set "enabled" to true.

Windows Example

"integrationServices": [
{
 "serviceName": "slmp",
 "serviceLibrary": "slmpservice.dll",
 "schemaName": "slmp",
 "enabled": true
},

Unix/Linux Example

"integrationServices": [
{
 "serviceName": "slmp",
 "serviceLibrary": "libslmpservice.so",
 "schemaName": "slmp",
 "enabled": true
},