Edge computing and IIoT
Earlier articles
Comparison
Move DeltaV Continuous Historian data into a PI system
When PI points exist, collect DeltaV live values with OPC DA and recover history with OPC HDA; when points and AF structure are missing, let the DeltaV Smart Connector create them from EntHist.xml. Add PI-to-PI only for a second office-LAN server. Prove buffering, service identity and archive coverage by test before the bulk load.
Troubleshooting
Historian replication sends raw values to PI Server: fix it
Historian 2023 R2 replication carries raw values to PI Server and scaled values to another Historian, so PI-bound tags need their value selection checked before any scaling change. Confirm the mismatch by comparing one stored sample at both servers against the source tag at the same timestamp. Then convert in exactly one place: scaled-value selection in the PI-bound interface if documented, otherwise one downstream conversion.
Troubleshooting
Fix npm E502 when installing Node-RED nodes behind a proxy
npm error code E502 on a palette install means an answering hop could not resolve or connect onward to the registry host, even when a generic HTTP check passes. Work the failure upstream from the proxy: confirm the proxy process, match the device's proxy address and mode, check the firewall rule, then verify outbound TCP 443 to registry.npmjs.org. Treat an App Unavailable editor as a missing localhost exception, a separate fault.
How-to
Expose historian latest values over OPC UA or MQTT
Yes — connect an integration gateway to the historian's classic I/O Server over SuiteLink (application name aahiosvrsvc, topic TagName) and publish the current values as OPC DA and MQTT. After a historian restart the I/O Server and the Live table return nothing until the source sends a new value, so a true last-known-from-disk read needs T-SQL or the historian SDK.
Troubleshooting
Edge trend shows no historian data: fix the doubled SELECT
The trend stays blank because a complete SELECT statement was pasted into the Table field, so the gateway wraps it in its own SELECT ... FROM and SQL Server rejects the result as incorrect syntax near the keyword select. Put only Runtime.dbo.History in Table, carry DateTime, TagName and Value in the column controls, and move TagName = 'SysTimeSec' into the filter control.
Troubleshooting
Edge gateway shows offline: check the 3.5.16 requirement
An edge gateway that flipped from green to offline most likely sits on 3.5.15 while the Automation Server lists Edge Gateway 3.5.16.0 or higher as the runtime system requirement. Read the installed version first, then remove and re-add the gateway, replace it through the service tool, update to 3.5.16.0 or higher, and escalate through a CODESYS Store support question if it stays red.
Explainer
Does the PI Data Archive store tag data in SQL Server
No. The PI Data Archive writes time-series tag values to its own proprietary storage and never uses SQL Server for tag data; SQL Server is in the PI Server stack only for PI AF, whose asset model lives in a SQL database treated as a black box. A SQL Server backup therefore protects the asset model and none of the tag history.
Explainer
Does an MQTT broker store historic data you can query
No. An MQTT broker transports publications and keeps only delivery state: the newest retained value per topic and messages queued for offline persistent sessions, with no time-range query and nothing else to query. To move many timestamped samples in one delivery, the publisher must buffer them and send a multi-sample payload such as Sparkplug B; to query history later, something must store it when it arrives, in a historian or database.
Explainer
Connect on-premise OPC UA and SQL servers to a cloud PI System
Yes. Install the AVEVA adapters on-premise, on a small host next to the OPC UA and SQL servers, and point egress at PI Web API in the cloud; the PI Data Archive port is not a supported egress destination. Only the adapter-to-Web API direction needs an outbound route.
How-to
Connect EcoStruxure Automation Expert to SQL Server
The runtime cannot own the SQL connection: standard FCT functions execute Structured Text only, and the 24.1 release closed the build-your-own service block route. Run a gateway on a PC that reaches both networks, exchange typed data over OPC UA or MQTT, and let the gateway alone own the SQL Server connection on TCP port 1433.
Troubleshooting
Citect Historian database creation fails on a named instance
The error names a failed server-level command on the named instance's master database, not a broken wizard. Get the underlying SQL exception, confirm that the login the wizard presents sits in the sysadmin server role on that instance, and confirm the engine version is on the historian build's support list. Switching between Windows and SQL Server authentication fixes neither a permission gap nor a version mismatch.
How-to
Writing timestamped history back into a SCADA server
Write timestamped results into the SCADA historic database through the vendor's .NET client API, under a dedicated account that holds the right to edit history, running as a daily scheduled task or a file-watching service. Test one ODBC insert under that account first: if the historic table still refuses writes, ODBC is read-only on your build and the API is the route.