Edge computing and IIoT
Earlier articles
Troubleshooting
Why buffered Sparkplug B data is rejected after reconnect
Replayed samples are dropped because the MQTT Publisher component in System Platform v2023 P01 sends them without the per-metric is_historical = true flag the Eclipse Sparkplug B specification defines for late data, so the broker treats old timestamps as suspect. No setting in that component sets the flag; keep MQTT for live values and recover the outage window through a separate backfill path.
Troubleshooting
Historian trend flat line: check Query Row Limit
A historian trend that draws one straight value in history mode while live mode and a direct SQL query both return good data is truncating rows client-side. The tag's Query Row Limit on the graph was set to 2 instead of the documented default 0, so only two samples came back. Set it to 0, then confirm the trend's saved row count matches the SQL count.
Troubleshooting
Plant SCADA Connector shows connected but historian tags are NULL
Connected status on both Connector ends proves the connections, not the reads: with Citect error 29, Bad User Parameters, the driver subsystem rejects the read before any value exists to store. Check the I/O Device special options and the variable tag data types first and leave the historian destination alone.
Selection guide
Manual lab data entry into a historian: choosing the write path
Put every measured variable into its own timestamped PI point and write it from inside PI Vision with a manual-entry symbol; keep specifications, qualifiers, blanks and notes as separate AF fields, not in the value. The load is only 1,800 values per day, so the decision rides on the write path, authentication and per-operator write rights, never on avoiding the 300 points.
Troubleshooting
Getting backfilled Sparkplug history through Ignition reference tags
Your settings are right; order is the missing condition. Backfill reaches the reference tags only when Store Historical Events is OFF so backfilled samples drive the Engine tag, and only when the edge replays its backlog oldest-to-newest past metric timestamp validation. Out of order, disable metric timestamp validation and keep the replayed value out of live control reads.
Troubleshooting
Why Citect Historian 2016 setup never installs SQL Server
The completed message from the Historian SQL launcher proves the launcher finished, nothing more. Accept the engine only on two checks: the database-engine service for the instance, and a client connection to it. When the package ships without the SQL installer, copy the separately obtained SQL Server 2012 files into HistorianSQL\Extras\1033\SQL Server\, clean the partial install, and rerun setup; the ActiveX error that follows is a separate COM fault.
Troubleshooting
Repoint InTouch trend files to a new Historian server
The hang is a server-binding fault: each saved trend file carries the retired Historian's name and the client waits on it before the window opens. Map the old name to the new server with a DNS alias or a hosts entry, change the server reference inside each file, keep the tagnames, then remove the alias and confirm every file opens. Old history does not return with the tagnames; it exists on the new server only if the old database was restored or migrated into it.
Troubleshooting
Redirect saved trend files to a new historian server
A saved .aaTrend file keeps the server name it was created with, so it hangs when the old historian is gone. Open it in the current Trend client, let the connection attempt finish (observed one to two minutes), save a new copy, then search for the old server name in that copy and replace it with the new one; tag names stay unchanged.
How-to
Forward Canary historian data through a SaF proxy
Forwarding site history to a corporate Canary historian is a Store and Forward routing job. Enable the Proxy feature in the sending SaF service, set RouteDestinations to localhost plus the corporate historian, and open TCP 55291 inbound on the destination. An API token with Write permission to the Historian View is required only when Tag Security is enabled on the destination Identity service.
How-to
Connecting a Yokogawa ExaOPC server to Canary Historian
Yes. Canary Historian's OPC client collector reads tags straight from ExaOPC, Yokogawa's OPC server for CENTUM, over DA or UA with no custom driver. Run the DA collector on the ExaOPC host or a same-domain host: cross-host DCOM is where these links break.
Explainer
MQTT broker support is not Sparkplug support
No. A compliant MQTT broker carries Sparkplug traffic without knowing it exists: to the broker the payload is opaque bytes, and the topic namespace, payload encoding and birth/death state conventions are implemented entirely by the publishing and subscribing clients. Verify Sparkplug support at both endpoints, never in the broker.
Explainer
AVEVA Historian 2023 R2 license backward compatibility explained
Yes. AVEVA knowledge base 000033942 lists Historian among the 2023 products whose licenses are backward compatible to their 2017 versions, and one field test reports a 2023 R2 license running Historian 2020 R2. That clears the license layer only: Citect 2016 connectivity must be proven through the Plant SCADA Connector and CtAPI path.