Modbus to WebSocket dashboard
A dashboard on the plant network needs live values and nothing else: no broker, no database, no polling of its own. The Gateway serves a WebSocket endpoint: a client receives a snapshot of every tag on connect, then one message per update.
Typical use case
An operator screen, a kiosk display or an in-house web application that should show what the machines are doing now, on the local network, without the plant depending on a cloud connection.
Configuration approach
One endpoint
Listen address and path, a maximum number of clients, and the browser origins allowed to connect.
Snapshot, then updates
A client that connects gets every tag's current value at once, then a message each time one changes, with its quality and timestamp.
Access control
An access token, set on the device and never in the design, and TLS with a certificate and key file for wss://.
Build a Modbus to WebSocket dashboard gateway
Create a project, define the device and its tags in the Edge Logic Editor, and download a runtime to test at the plant.