Gateways
LuxConnect talks to a gateway that offers the mapp Connect API. The gateway reads and writes variables on the controller.
| Gateway | Runs on | Controller | Protocol to controller |
|---|---|---|---|
| mapp Connect | B&R controller | B&R | Built into Automation Runtime |
| OPC UA Proxy (experimental) | PC, or inside an Electron HMI | Controllers without mapp Connect, through their OPC UA server | OPC UA |
mapp Connect
mapp Connect is part of B&R mapp and runs on the controller. See LuxReact + LuxConnect for the controller setup.
OPC UA Proxy
OPC UA Proxy is experimental and available to Loupe projects. Ask the HMI maintainers for access.
The proxy is for controllers that don’t have mapp Connect. It doesn’t replace mapp Connect: on a B&R controller, connect LuxConnect directly to mapp Connect.
OPC UA Proxy is a Node.js program that exposes the same HTTPS and WebSocket API as B&R mapp Connect and forwards requests to an OPC UA server. LuxConnect connects to it exactly as it would to mapp Connect, so a LuxReact HMI can reach controllers that don’t run mapp Connect.
It runs in two ways:
- As a service: on a Windows or Linux PC, or in Docker, shared by several HMIs.
- Inside Electron: started from the HMI’s Electron main process, so the HMI ships as a single application.
For Beckhoff controllers, the proxy connects to the TwinCAT OPC UA server (TF6100). This combination has not been validated yet; test it on your controller before you rely on it.