OPC UA to MQTT
Many PLCs, SCADA systems and machine controllers already expose OPC UA. The gateway connects as a client, reads the variables you name by node id (ns=2;s=Pump.Speed), and publishes them with a name, a unit and a quality, exactly as it does for Modbus. Design it in the editor, validate it, build the package and run it.
Typical use case
An S7-1500 or a machine with an embedded OPC UA server should feed a broker or a database without an OPC UA client licence on the IT side, and without the plant PLC being reachable from there.
The OPC UA client deploys and runs in this release of the Edge Runtime. It has been tested against an open-source OPC UA server and the gateway's own OPC UA Server output, not yet against a vendor's PLC, so treat the first commissioning as the verification.
Configuration approach
Node ids as the server names them
ns=2;s=Pump.Speed or ns=3;i=1001, the way any OPC UA client shows them; the OPC UA Explorer exports a server's whole list.
The security the server offers
None, Sign or SignAndEncrypt with the policy the server accepts; anonymous or a user name, with the password kept on the device.
Quality travels with the value
A variable the server reports as bad is published as bad, never as a repeat of the last good number.
Build a OPC UA 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.