Edge computing and IIoT
Edge computing, MQTT, OPC UA gateways, historians and PC-based SCADA hosts.
Latest articles
Troubleshooting
Why gRPC ingestion fails when the TCP port test still passes
A passing TCP port test proves only that the listener accepted a connection at that instant; gRPC ingestion also needs a live service, a negotiated HTTP/2 session and capacity behind the port. When both store-and-forward nodes drop together and burst on recovery, diagnose the historian host's service lifecycle, saturation and endpoint limits, not the network.
Explainer
Why your gateway talks MQTT to Azure but not AMQP
MQTT works because Azure IoT Hub natively speaks MQTT v3.1.1 over TLS and the gateway's Java 1.4 runtime can carry that exchange. AMQP does not, because Event Hubs' client-side ingress is AMQP 1.0 on port 5671 and no supported AMQP client runs on Java 1.4. Keep the gateway on MQTT to IoT Hub and route to Event Hubs from there, or bridge with a separate box.
Troubleshooting
Recover a historian dump loop after a service restart
Deleting the dump files does not stop the loop. Preserve a representative set, measure the growth rate to know how many hours of C: drive remain, restart the whole server as the demonstrated temporary recovery, and characterize the shutdown-versus-continuous failure on build 23.1.001.000 through support — the Historian 2017 hotfix does not apply.
How-to
Send PI historian CSV exports to an S3 bucket hourly
Keep the two jobs separate: the existing export produces the hourly CSV, and a scheduled uploader on a host that can read the export folder and reach the bucket delivers it to S3. Verify the completed CSV before any transfer, and scope the upload credentials to that one bucket prefix. The historian does not write to S3 by itself, and an SFTP endpoint is not a bucket.
Troubleshooting
Fix Ignition SQL Server connection faults after an upgrade
After an Ignition 8.1.x upgrade, a faulted SQL Server connection is almost never a credentials problem: the new Java runtime disables TLS 1.0 and 1.1 (builds from 8u291), and a Microsoft JDBC driver as old as 4.0 cannot run on it. Read the Gateway exception, then patch SQL Server to TLS 1.2 per KB3135244 or replace the driver; the reported working pair was 9.4 in place of 4.0.
Explainer
AVEVA Historian Connector redundancy options explained
AVEVA Historian Connector v3.1 does not manage failover between redundant Historians. For collection redundancy, run two Connectors, each writing to its own Historian, with configurations you keep identical by procedure; use Historian partner and client failover only to cover temporary access loss.
Selection guide
Plant SCADA 2023 R2 AEL license tiers and included historian tags
Plant SCADA 2023 R2 (v8.5) AEL server licenses bundle a Historian 2023 R2 Server (Standard) and a Reports for Operations 2023 R2 Server: 500 historian tags and 500 reporting tags at the 1,000- and 2,500-tag tiers, and 5,000 of each from the 10,000-tag tier through Unlimited. Existing enterprise licenses pick the entitlements up with a sync rather than a repurchase; legacy USB keys exchange through the distributor; and Flex shows existing enterprise customers only the 100,000-tag and Unlimited packages.
Troubleshooting
Diagnose a slow historian web client page load on the server
Capture the load in the browser Network tab with the cache disabled and split each slow request into connection, TLS, waiting and download phases. When waiting for server response holds most of the time, the historian web services are waiting on the shared SQL Server host: cap Max server memory, check disk latency, then send support a redacted HAR. The timing split, not the total load time, decides the cause.
Comparison
How AVEVA Historian publishes collected data to a client
Yes — AVEVA Historian publishes collected data, but through a client-matched output rather than one universal server. Seven paths cover the cases: SuiteLink, PCS iData, OMI Replay, SQL History or Live tables, MQTT, OData, and Gateway as an OPC DA client. Keep the OPC UA link as collection, then pick the output by the client's protocol and whether it needs live or stored values.
How-to
Pushing UDT definitions to Ignition Edge gateways with EAM
Yes. An EAM Send Tags task pushes nested UDT definitions to every Edge gateway, because each gateway resolves its instances locally; a remote tag provider will not resolve a type held only on the main gateway. Expect remote tag delay of the 100 ms poll rate plus the network round trip, delivered over WebSockets.
How-to
Recursively browse PLC nodes in Node-RED for InfluxDB
A single read of the PLC root path returns that node's value only — nested levels are never collected. Browse the tree once to every leaf, cache the paths in Node-RED global context, then poll the cached list every 10 seconds and write one payload to InfluxDB with relative paths as field names. The deciding number is cycle duration: about 200 paths at a 20 ms mean read take 4.0 s, so the 10 s timer holds only while a measured cycle stays inside the interval.
How-to
Log analog millivolt signals as booleans in Ignition
Threshold the millivolt signal in an expression tag with a Boolean data type, enable tag history on that tag only with Sample Mode set to On Change, and disable history on the analog tag. Every stored row is then a 0 or 1 written on a transition instead of a float written on every deadband crossing.