Mitsubishi MELSEC to MQTT
Mitsubishi PLCs over the MC protocol, 3E or 4E frames on TCP or UDP: D, M, X, W and ZR devices addressed the way GX Works writes them, D100. Design it in the editor, validate it, build the package and run it.
Typical use case
A MELSEC line reporting counts, states and process values to a broker, without a change to the PLC program.
The MELSEC driver deploys and runs in this release of the Edge Runtime. It has been tested against a simulated controller, not yet against a real one, so treat the first commissioning as the verification.
Configuration approach
Device addresses
D100, M200, X10, W1F0, ZR100: the device letter and the number as the manual writes them, with the tag's data type deciding how many words are read.
TCP or UDP, 3E or 4E
Set on the device node to match the PLC's Ethernet module configuration.
Quality travels with the value
A tag that stops being readable is published as such, never as a repeat of the last good number.
Build a Mitsubishi MELSEC to MQTT gateway
Create a project, define the device and its tags in the Edge Logic Editor, and download a runtime to test at the plant.