Condition Monitoring KPI Dashboard

Live Feed selected. A browser page can't open a raw PLC socket directly (Modbus TCP, PROFINET, OPC UA…) — point it at the PLC or gateway below. In production, a small gateway service bridges that address to a secure feed this dashboard subscribes to; until it's deployed, tags keep showing their last simulated snapshot, frozen.

MQTT is the one protocol here a browser can speak natively — over WebSocket, no gateway needed, because MQTT brokers already offer a WebSocket listener.

Defaults to broker.emqx.io — EMQX's public test broker: open, unauthenticated, and shared by everyone testing MQTT, so don't publish anything sensitive. Point this at your own broker instead once you have one. To see a tag move, publish a message such as {"value": 7.2} (or just a plain number) to a topic ending in that tag, e.g. cems/demo/VT-1021 — any MQTT client (mosquitto_pub, MQTT Explorer, Node-RED) will do.

Modbus TCP needs a bridge to reach a browser — a browser can't open a raw TCP socket, so it can never speak Modbus TCP directly to a PLC. The tools/ folder next to this page has a small script that does the real protocol work and republishes values as plain JSON over WebSocket — this connects to that, for real.

Condition Monitoring — Live KPI Dashboard

Add sensor

Tag detail

Add data point

Edit tag mapping — Modbus TCP