Edge computing and IIoT
Earlier articles
Troubleshooting
Why the Rebirth metric arrives without its Sparkplug alias
The command is correct: Sparkplug B forbids an alias on Node Control/Rebirth in NBIRTH, so a host sends that NCMD by full name with the alias field unset, and your decoder prints 0 because an unset numeric protobuf field reads as 0. Delete the alias from the Rebirth metric in your birth payload and dispatch the command by name on the node.
Troubleshooting
Fix ECONNREFUSED when Node-RED connects to a remote SQL database
ECONNREFUSED 127.0.0.1:3306 means the MySQL node dialed loopback on the machine running Node-RED, so the database computer was never contacted. Put the database computer's LAN address in the node's Host field, confirm MariaDB listens on that interface with TCP 3306 open, and create the account with the edge device's address as its host part.
How-to
Configuring TLS in the Node-RED Sparkplug node
Set the Sparkplug node's broker Server URL to ssl:// followed by the broker hostname, and the Port to 8883. The connection negotiates TLS only when the broker presents a certificate chaining to a CA the Node-RED runtime already trusts and requests no client certificate; the editor exposes no fields for a self-signed trust anchor, client certificate, or private key, so those broker policies need a different client.
Troubleshooting
Why a Sparkplug float shows 16 decimals but the historian shows three
A Sparkplug B Float metric is a 32-bit IEEE 754 value carrying about 7 significant decimal digits. The 16-decimal string is that binary value widened to a 64-bit double for display, and the historian's 3-decimal tile is formatting — neither proves stored data changed. Compare the declared data type and decoded value at publisher, broker, collector input and historian query before blaming storage.
How-to
MQTT store and forward backfill after a connection outage
Yes. Tag data collected on the edge during the outage fills the server gap after reconnection, but only when Store and Forward is enabled in MQTT Transmission on the edge and history is enabled on the receiving MQTT Engine tags. Matching historian database names on both systems does nothing.
Troubleshooting
Historian stores zero after an MQTT edge node reconnects
A 0 stored just before the true value at every MQTT edge reconnect is a reported pattern on Ignition 8.1.5 through 8.1.15 with the MQTT Transmission and Engine modules 4.0.6 through 4.0.10. Confirm it by querying stored records around each reconnect, exclude those zeros from process data, and remove them with a timestamped rule instead of a blanket zero filter.
How-to
How to move Wonderware Historian data into Canary Historian
Yes. Backfill Wonderware history by exporting CSV files or a SQL database that Canary consumes, run a parallel real-time collection path for the same tags, and verify record counts and values at the timestamp where imported history meets live data.
Explainer
Can plant historian software run in Docker containers
The processes will start, but historian services hold retained state and are not documented to communicate statelessly, so a started container proves nothing about collection, calculations, events, or queries surviving replacement. Keep the working deployment in production and evaluate containers only in an isolated test, with a volume mapped for every path that holds data or configuration, passing a counted query across a restart, a recreate, and a host move.
Troubleshooting
Troubleshoot missing data in a Node-RED InfluxDB Grafana stack
Work the chain in order: acquisition into Node-RED, the InfluxDB service and its storage mount, the write settings, then the Grafana query. In a 2.x stack most empty panels trace to a wrong token, bucket, URL or a controller clock that stamps points outside the panel's time range.
Comparison
MQTT on a CoDeSys 2.3 PLC: gateway vs controller client
No MQTT client library is identified for the WAGO 750-830 running CoDeSys 2.3, so the controller cannot be the MQTT client; keep it on control and publish from an external gateway or edge PC that reads it over an interface the installation already supports. Migrate the controller only when MQTT must run inside it. The comparison below gives the decision for each path.
Selection guide
Selecting MQTT I/O hardware for a single sensor signal
For one discrete sensor, choose an Ethernet I/O block whose input matches the sensor's 24 V PNP or NPN output, publish on state change, and verify hostname, TLS and QoS support in the documentation before buying. QoS 2 guarantees delivery only between client and broker, so prove the path with a staged wiring-to-subscriber test.
How-to
Bridge a cellular tracker's TCP stream into MQTT for AWS IoT Core
Build a small ingest service on your edge PC: it terminates the tracker's raw TCP session, decodes each stored record, and republishes one MQTT message per fix over TLS on port 8883. Acknowledge a packet only after every publish is confirmed, or a coverage-gap batch is silently lost.