Skip to content
PembelajaranMachine Connectivity with OpexFlowMQTT as the Connectivity Spine
Progres Anda0%
Lanjutan20 menit

MQTT as the Connectivity Spine

Why MQTT publish/subscribe carries every other protocol off the floor and into OpexMX.

MQTT as the Connectivity Spine

MQTT is the single bus that Modbus, OPC-UA, and FOCAS readings get normalized onto.

Why MQTT

  • Publish/subscribe — many consumers, one source of truth.
  • Lightweight — works over flaky plant Wi-Fi without choking.
  • Hierarchical topics — site/line/asset/metric, easy to filter.

Bridging Protocols

  1. Edge Connector reads the native protocol from the asset.
  2. Translates the value into a JSON payload with asset ID and timestamp.
  3. Publishes to a topic like opexmx/site3/lineA/cnc14/status.
  4. OpexMX subscribes, persists, and reacts.

Topic Discipline

  • One topic per asset per metric.
  • Keep topic depth consistent so downstream rules are predictable.
  • Prefix with site code to keep multi-site data clean.

Tips

Pick your topic scheme once and document it. Changing topics after fifty assets are live is painful.

SebelumnyaBerikutnya