IBH Link UA:MQTT Description

From IBHsoftec Wiki English
Revision as of 13:15, 30 December 2025 by Andreas (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

MQTT Connection:

Here, user-defined OPC UA variables can be exchanged with an MQTT broker/server via the MQTT publisher/subscriber functionality. MQTT supports security mechanisms such as encrypted connections, certificates and user authentication, thereby achieving a very high level of data security.

A structured layout of the variables can be created very conveniently using the IBH OPC UA Editor, which is available free of charge.


The MQTT function in the IBHL ink UA supports remanent storage for messages on the SD card. This means that messages can be retained even after a restart, power failure or connection interruption and sent later.

With the support of Sparkplug-B, MQTT becomes suitable for industrial use (IIoT).

The key advantages of Sparkplug-B:

- Uniform data model

- Online/offline detection

- Plug-and-Play

- Binary & efficient

The MQTT function can be controlled via the PLC – however, not directly via MQTT commands, but via the OPC UA variables linked to MQTT topics.

  • In the IBHLinkUA configuration, you can define OPC UA variables that serve as triggers or statuses for MQTT.
  • These variables can be read or written by the PLC (e.g. Siemens S7, Mitsubishi, Rockwell) via OPC UA.
  • Typical controls::
    • Trigger publish: A PLC variable is set to a specific value, and IBHLinkUA sends the message to the MQTT topic.
    • Monitor status: Received MQTT messages are written to OPC UA variables, which are evaluated by the PLC.


The IBH Link UA can therefore be used as a layer between machines and control systems (MES, ERP, etc.) independently of Simatic, Mitsubishi or Rockwell controlers controllers.