Mitsubishi MC protocol (SLMP) to OPC UA
PLCGateway reads MELSEC controllers with the MC protocol (SLMP) and serves their devices from an OPC UA server – without an OPC UA module in the rack or a separate OPC server on a PC.
- Mitsubishi MC protocol (SLMP)
mc3e_binarymc3e_asciimc4e_binarymc4e_ascii- OPC UA
Adding OPC UA to a MELSEC system usually means an OPC UA server module in the rack or a Windows OPC server product. PLCGateway is a software alternative: it reads the CPU over its Ethernet port with 3E or 4E frames and offers every tag as an OPC UA variable.
Existing Q and L series lines get OPC UA without touching the hardware, and new iQ-R and FX5 machines appear under the same endpoint, with the same naming and security settings.
- Source
- Mitsubishi MC protocol (SLMP)
mc3e_binarymc3e_asciimc4e_binarymc4e_ascii - Connection
- TCP / UDP · binary or ASCII
- Target
- OPC UA
- Writing
- yes
Set it up in five steps
In GX Works open an Ethernet port for the MC protocol (SLMP) as TCP or UDP and allow writing in RUN if values are to be written.
Add a device with frame (3E or 4E), coding (binary or ASCII), IP address and port, and choose the series (Q/L/FX5 or iQ-R).
Enter the device addresses as tags or import them from CSV and test the connection.
Open Gateway → OPC UA and choose the security modes and whether clients sign in anonymously or with user name and password.
Connect your OPC UA client (UaExpert, an MES, a SCADA) to opc.tcp://<gateway>:4840 and browse Objects → PLCGateway.
Example: node ids in the OPC UA server
A device with the id line2 and these tags appears in the address space as shown below. Names and values are examples.
| Tag | Address | Example value |
|---|---|---|
OvenTemperature | D200 | 182.5 °C |
CycleCount | D100 | 5120 |
AutoMode | M100 | true |
OPC UA node ids
opc.tcp://<gateway>:4840
Objects / PLCGateway / line2
ns=1;s=line2.OvenTemperature = 182.5
ns=1;s=line2.CycleCount = 5120
ns=1;s=line2.AutoMode = true
Every tag is a variable under Objects / PLCGateway / device in namespace 1; clients read it, write it and subscribe to its changes.
The OPC UA server in PLCGateway
Every tag becomes a variable in PLCGateway's built-in OPC UA server, so MES, ERP, SCADA and historians use one standard endpoint instead of each controller's own protocol. Clients browse the devices and tags, read, write and subscribe to value changes.
The server offers the security modes None, Sign and SignAndEncrypt with automatically generated certificates; clients sign in anonymously or with user name and password.
- One endpoint (opc.tcp, port 4840) for all devices and protocols
- A folder per device and a variable per tag, with description and unit
- Subscriptions with data-change notifications; writing only where the tag allows it
- Client certificates are approved in the web interface
Controllers and devices
Equipment that is typically connected with this driver.
Questions and answers
Do I need an OPC UA server module in the PLC rack?
No. PLCGateway provides the OPC UA server in software and reads the CPU with the MC protocol.
What is the difference between 3E and 4E frames?
4E frames add a serial number that matches answers to requests; both are supported in binary and ASCII. 3E binary is the usual choice.
Can OPC UA clients write to the PLC?
Yes, if writing in RUN is allowed in the CPU, writing is allowed in the OPC UA server settings and the tag is not read only.
Connect your machines
Tell us which controllers you run; we show you PLCGateway with your own addresses.
Product and model names are trademarks of their owners. They are named only to show which equipment the drivers communicate with; PLCGateway is not affiliated with these companies.
