Edge computing and IIoT
Earlier articles
Troubleshooting
Node-RED MQTT fails when the broker rejects plain MQTT
The connect fails because the MQTT OUT broker configuration sends plain MQTT while the Mosquitto listener accepts TLS only; the address and port can be correct and it still fails. Confirm which side is at fault with MQTT Explorer, then pick one mode on both ends — enable the plain listener you intend, or enable TLS in the client — and verify with a same-topic publish and subscribe.
Troubleshooting
Fix InTouch 2023 Test Connection failure to Historian
Test Connection from InTouch 2023 to a remote Historian fails for two reasons: the Historian node's firewall blocks the SQL Server listener even though ping works, and the Distributed Name Manager history provider does not support Windows credentials. Prove TCP reachability, then use a SQL Server login stored in Credentials Manager.
Troubleshooting
Remote tag history stops when gateway redundancy fails
A running Gateway Network connection proves the transport, not the services behind it. In the reported case the redundant pair hosting the history providers had detected thread deadlocks on the backup and a disconnected redundancy peer on the primary after a direct upgrade to 8.3.4, so gateway and redundancy health must be restored before any remote provider is reconfigured.
How-to
Covering the QoS 0 loss window in Sparkplug MQTT transmission
No. Sparkplug B requires NDATA and DDATA at QoS 0, so no supported MQTT Transmission setting publishes data messages at QoS 1 or adds broker acknowledgment. Enable the Rolling Buffer in the transmitter's History Store to replay messages lost in the transient TCP window, and design downstream consumers to accept duplicates, because replay is at-least-once.
How-to
Writing MQTT Distributor ACL topic filters for Sparkplug B
Give each Sparkplug B edge node its own credential with one write filter, spBv1.0/GroupID/+/EdgeNodeID/#, and two read filters, STATE/PrimaryHostID and the same node filter. The ACL is a plain MQTT topic matcher: pin the namespace, group and node as literals, wildcard the message type with + and the device level with #. Any publish or subscribe outside the granted filters disconnects the client, so the NDEATH will and the STATE subscription must be inside the entries.
Troubleshooting
Read Proficy Historian OPC-HDA tags into Ignition
Create the Proficy historical connection through the OPC COM module's documented OPC-HDA workflow, not the new OPC Server connection dialog. Charts get their data from interval reads; values usable as Designer tags need a runScript bridge into a shared script built on system.opchda.readRaw. Enabling tag history on bridged tags stores new values only — the existing Proficy archive is not migrated.
Explainer
SQL Historian database permissions: the full six rights
Grant the Ignition historian login all six rights — SELECT, INSERT, UPDATE, DELETE, CREATE and DROP — but only inside a dedicated historian schema or database. UPDATE is required because Ignition maintains rows in sqlth_partitions and sqlth_te even though logged sample values are append-only.
Troubleshooting
Why a device cannot publish MQTT to a broker on your PC
Point the device's client at the PC's LAN address, not 127.0.0.1 — loopback always means the device that opens the connection. Then confirm the broker listener is bound to the PC's LAN interface on TCP 1883 and that Windows Firewall admits inbound connections on that port from the plant subnet. Fix those three and the publish path works.
Selection guide
Choosing an edge data path for periodic records
For independent periodic samples, Tag Historian with Edge Sync Services is the reliable path and buffers 35 days locally. For one atomic row per collection cycle, use MQTT Transmission records landing in MQTT Recorder. For true transaction groups, license a standard gateway for that node.
How-to
Reusing Ignition edge tag structures on a central gateway
Yes. Rebuild the edge UDTs as reference tags in a realtime provider at the central gateway so copied windows resolve unchanged, cluster the four brokers into two pairs, publish the regional and backup streams under distinct Edge Node IDs, and let the national UDT select the healthy source per tag.
Troubleshooting
Fix Ignition Core Historian high CPU usage
Gateway CPU above 80 percent that falls below 10 percent when only Core Historian is disabled is a historian storage fault, not a 30-tag acquisition load. Upgrade the 8.3.3 (b2026012009) gateway to 8.3.7 or newer, whose release notes fix Core Historian query performance degrading as data accumulated, and leave the partition interval and maintenance age as configured.
Troubleshooting
Why Edge historian gaps look like held values centrally
The single _exempt_ row in sqlth_sce and the empty sqlth_scinfo are designed behavior: the Edge Historian neither tracks nor validates scan classes, locally or over sync, so an outage queries as a held last value on the central gateway. Add a PLC-sourced heartbeat tag, detect holes in its rows as outage windows, and subtract them from runtime totals - a weekend outage otherwise overstated runtime by 16 hours.