> For the complete documentation index, see [llms.txt](https://docs.enlyze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enlyze.com/en/connect/ot-connectivity/supported-industrial-protocols/slmp.md).

# SLMP

The following guide walks you through connecting data sources that communicate via the SLMP protocol. SLMP (SeamLess Message Protocol) is [Mitsubishi Electric](/en/connect/ot-connectivity/supported-controller-brands/mitsubishi-electric.md)'s proprietary Ethernet protocol from the MC protocol family (MELSEC Communication Protocol). It is used by MELSEC controllers with an Ethernet interface, from the compact iQ-F (FX5) to the modular families iQ-R, Q, and L. ENLYZE connects these controllers via SLMP over Ethernet (TCP, default port `5001`).

{% hint style="warning" %}
**Prerequisite: knowledge of the memory areas**

SLMP addresses data through device codes (e.g. `D`, `M`, `X`, `Y`) 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.
  {% endhint %}

## Supported devices

SLMP is supported by a broad range of Mitsubishi controllers with an Ethernet interface. A complete overview of the families and devices, along with the matching **Target PLC** setting, can be found on the [Mitsubishi Electric page](/en/connect/ot-connectivity/supported-controller-brands/mitsubishi-electric.md). Connectable are all SLMP-capable devices with an Ethernet interface, including:

* Mitsubishi MELSEC iQ-F (FX5U, FX5UC, FX5UJ)
* Mitsubishi MELSEC iQ-R (R04, R08, R16, R32 CPU with RJ71EN71 or integrated Ethernet)
* Mitsubishi MELSEC-Q (with QJ71E71 module)
* Mitsubishi MELSEC-L (L02, L06, L26 with integrated Ethernet)

{% hint style="info" %}
So far we have field-tested the **FX5U** (iQ-F). The modular families **iQ-R**, **Q**, and **L** are likely connectable via SLMP as well but have not yet been connected by us in the field. Older FX controllers without Ethernet (FX2N, FX3U) are connected through the serial interface instead.
{% endhint %}

## Required information

<table><thead><tr><th width="293.6058349609375">Information</th><th>Comment</th></tr></thead><tbody><tr><td>Name</td><td>Give your data source a descriptive name</td></tr><tr><td>Selection of the Edge Device used for the connection</td><td>Noted on a sticker on every Edge Device. Follows the scheme <code>adjective-scientist</code></td></tr><tr><td>Machine</td><td>Every data source is assigned to exactly one machine</td></tr><tr><td>Manufacturer</td><td>Mitsubishi Electric</td></tr><tr><td>IP address</td><td>The IPv4 address of the controller. It must be <a href="/pages/NOoLZt9S2VJxBY2IkzbA">reachable</a> from the Edge Device</td></tr><tr><td>Port</td><td>Default: <code>5001</code> (SLMP over Ethernet, TCP)</td></tr><tr><td>Target PLC</td><td>Model of the Mitsubishi controller, e.g. <em>FX5U</em>.<br><a href="#target-plc">→ How to find the right Target PLC type</a></td></tr></tbody></table>

## Understanding the connector details

### Target PLC

The **Target PLC** defines which Mitsubishi model the data source uses. The selection determines how the connector addresses the device areas (e.g. `D`, `M`, `X`, `Y`, `R`) of the controller, since the memory model and the available address range differ between models.

Currently field-tested and selectable is the **FX5U** (MELSEC iQ-F). We connect additional models on request. To find the right setting for your device, see the [device overview on the Mitsubishi Electric page](/en/connect/ot-connectivity/supported-controller-brands/mitsubishi-electric.md).

{% stepper %}
{% step %}

#### Connect the data source to the network

If this has not been done yet, a network connection between the data source and the respective Edge Device must first be established. See [Integration scenarios](/en/connect/integration-scenarios.md) for the available options.

{% hint style="info" %}
SLMP runs over TCP on port `5001`. With firewalls, make sure this port is open between the Edge Device and the controller. On the controller itself, an SLMP connection must also be configured (in GX Works3 under the Ethernet settings of the CPU or the Ethernet module).
{% endhint %}
{% endstep %}

{% step %}

#### Create the data source

Open the [ENLYZE Manufacturing Data Platform](https://app.enlyze.com/platform), select the machine for which this data source should be added, and click the *+ Data source* button.
{% endstep %}

{% step %}

#### Add connection details

For a connection to the data source to be established and data recording to start, the connection details must be entered.

Click the *Add connection details* button and enter the IP address, port, and Target PLC as described above. Then *save* the details.
{% endstep %}

{% step %}

#### Add variables

SLMP addresses data through device codes rather than symbolic tags. Variables are therefore created manually based on their device address and data type. Commonly used device codes are:

* `D` – data registers (word)
* `M` – internal relays (bit)
* `X` / `Y` – inputs and outputs (bit, octal addressing)
* `R` – extension registers (word)
* `T` / `C` – timers and counters (word)

The available data types are `Bit`, `Int16`, `UInt16`, `Int32`, `UInt32`, and `Float32`. Keep the relevant addresses from the PLC program (GX Works2 / GX Works3) ready.

{% hint style="warning" %}
No data is recorded until you select the [variables](/en/variable-mapping/contextualisation.md) to record. Follow our variable onboarding flow for this.
{% endhint %}
{% endstep %}
{% endstepper %}

If you have any questions, feel free to contact us at <support@enlyze.com>.