Skip to main content

Plugin Manuals

These pages describe the settings, address or template rules, variable properties, dedicated debug panels, verification steps, and troubleshooting for each plugin. Configure channels, devices, common variables, forwarding groups, triggers, cache, redundancy, and enable/disable operations in Collection Configuration and Data Forwarding.

All collection and data-forwarding plugins are listed in the Plugins section of the left sidebar. Collection manuals are grouped into general protocols, PLCs and controllers, robots and motion control, instruments and sensors, and gateway or messaging access.

Choose by task

TaskPlugin typeConfiguration page
Read a PLC, instrument, robot, or field protocolCollection pluginDevelopment Configuration → Collection Configuration
Subscribe to MQTT, OPC UA, or another serverCollection pluginDevelopment Configuration → Collection Configuration
Publish to MQTT, Kafka, RabbitMQ, ZeroMQ, or a Web serviceData-forwarding pluginDevelopment Configuration → Data Forwarding
Store current values, historical values, or historical alarmsData-forwarding pluginDevelopment Configuration → Data Forwarding
Expose Modbus, OPC UA, IEC104, or IEC61850 servicesData-forwarding pluginDevelopment Configuration → Data Forwarding
Synchronize ThingsGateway nodesData-forwarding pluginDevelopment Configuration → Data Forwarding

One protocol can have both a collection plugin and a server plugin. For example, Modbus Master reads a device, while Modbus Server exposes gateway data to another system. Choose the plugin according to the direction of data flow.

Common collection entries

Protocol or deviceManualMain topics
ModbusModbus MasterTCP, RTU, ASCII, register addresses, and function codes.
Siemens S7Siemens S7PLC model, rack/slot, and DB addresses.
OPC UAOPC UA ClientEndpoint, security policy, certificates, and nodes.
OPC DAOPC DA ClientWindows OPC DA servers and Items.
MQTTMQTT Collection ClientBroker, topics, payload parsing, and variable mapping.
Gateway MQTTGateway MQTT Collection ClientMQTT collection between ThingsGateway nodes.
IEC104IEC104 MasterGeneral interrogation, indications, measurements, clock sync, and controls.
IEC61850IEC61850 ClientMMS, RCB, GOOSE, and SOE.
Custom packetsCustom Full PacketRequest packets, response parsing, and protocol debug.

Open the Collection Plugins sidebar category to find other PLC, robot, instrument, scanner, and industry-protocol manuals.

Data-forwarding plugins

Database storage

PluginPurpose
Real-time Data StorageStores the latest value of each variable.
Historical Data StorageStores history using change, interval, or condition sampling.
Historical Alarm StorageStores alarm activation and recovery records at or above the selected level.

Protocol servers

PluginPurpose
Modbus ServerExposes variables through Modbus TCP, RTU, or ASCII.
OPC UA ServerExposes OPC UA nodes, writes, and historical queries.
IEC104 ServerProvides indications, measurements, general interrogation, and controls.
IEC61850 ServerProvides MMS models, reports, GOOSE, and controls.

Messaging and Web

PluginPurpose
MQTT Client ForwardingConnects to an external broker and publishes gateway data.
MQTT Server ForwardingPublishes through the built-in MQTT server.
Kafka ProducerPublishes to Apache Kafka.
RabbitMQ ProducerPublishes to RabbitMQ.
ZeroMQ ProducerPublishes through a ZeroMQ socket.
WebhookSends HTTP requests to a Web service.
ThingsBoard MQTTSends telemetry and attributes and processes ThingsBoard RPC.

Gateway integration

PluginPurpose
Sync BridgeSynchronizes configuration and real-time variables between Hub and Edge nodes.

Use a plugin manual

  1. Read Purpose and Open the plugin to confirm the data direction and page entry.
  2. Configure the fields under Plugin properties.
  3. Add variable-level mapping only when the page provides Target variable properties or address rules.
  4. Save and enable the object, then open the dedicated Device debug or Target debug panel.
  5. Complete one real read, publish, database write, or server-side read using the page's verification steps.

Use approved test points for writes, RPC, remote control, start/stop, reset, motion, and raw-packet operations. Follow the site's safety procedure.

Plugin not found

  1. Open Development Configuration → Plugin Management and clear the search and vendor filters.
  2. Search by protocol abbreviation, vendor, or plugin name.
  3. Confirm that the plugin is enabled and check license, platform, and AOT restrictions.
  4. After installing or updating a plugin, run Synchronize Plugins, then return to the configuration page.