Edge computing and IIoT
Earlier articles
Troubleshooting
Fix duplicate driver IDs after a Docker historian upgrade
Duplicate rows in the historian driver table after a container upgrade mean the gateway identity changed: the data volume or hostname was not carried forward, so the historian opened a new driver ID and logged under it. Pin the volume and hostname, restart the history provider to flush its cached tag IDs, and rebuild the schema only after that. ID jumps of about 1,000 are database sequence caching, not a fault.
Selection guide
Sizing an edge PC for oversampled PLC data to InfluxDB
Yes — the database side carries it. 50 samples every 2 ms is 25,000 values per second, reaching InfluxDB as 2.5 writes per second at the documented 10,000-line batch, about 0.38 MB each. What decides the project is the controller's 2 ms buffer handshake and line serialization — no vendor rates that path in bytes per second, so each stage is proven on the box with a synthetic signal before a sensor is wired.
Troubleshooting
Fixing AVEVA Historian VSS writer 0x800423f4 backup failures
Windows VSS error 0x800423f4 means a writer reported a non-retryable error. Identify the failing writer and operation, then check AVEVA knowledge article 000112336 if the Historian storage writer failed on 2023 R2 SP1 P02, P03 or P04. Verify a backup and isolated restore covering the SQL Runtime database and history blocks.
Troubleshooting
Fix PI calculations on slash-containing DeltaV historian tags
Quote the entire point name — 'FIC101/PID1/ PV.CV' — in single quotes and put the arithmetic outside it: 'FIC101/PID1/ PV.CV' / 2. The slashes inside the quotes belong to the stored name; the parser divides only at the slash after the closing quote. Renaming points is a later decision, not the fix.
Troubleshooting
Fix historian table creation failing on MySQL over ODBC
Capture the MySQL error from the historian's table-creation attempt. Use the historian's runtime connection settings to check the database, account, grants and supported schema. After provisioning for the exact historian release, verify a known test value and its recorded timestamp.
Selection guide
Choosing a PI System to Oracle integration route with validation
With read-only PI access and cleansing owned by the receiving side, pull AF assets and status with the PI OLEDB Enterprise Provider through SSIS into a staging SQL Server, qualify transitions there — reject momentary interruptions and anything older than 2 hours — then write Oracle. Event Frames and the RDBMS interface need PI-side configuration or tag-based mapping that loses AF context.
Troubleshooting
Trace a SQL log error after a historian migration
Run a SQL Server Profiler trace against the Runtime database, capture the error event with its query text and user context, and match its timestamp to the log entry within 5 seconds. Live data collection and the SQL message are separate observations; the trace tells you which request failed and whether the migration is the suspect.
Explainer
Securing ctrlX MQTT data paths to AWS or GCP
Yes — Node-RED plus Mosquitto can carry ctrlX Data Layer values under X.509 authentication and TLS 1.2, but each of the three connections (publisher to broker, device to broker, uploader to cloud) needs its own trust and client-certificate configuration. DeviceBridge joins only when the chosen AWS or GCP service's protocol calls for it.
Troubleshooting
Why PI shows live values but no trend history
A moving live value with an empty trend means the Snapshot is healthy and the archive write path is not. Sample piartool -qs twice a few minutes apart: if Total Event Reads climbs while Total Event Writes stays fixed, check free space on the archive and queue volumes, then piartool -al for an online writable primary archive, and stop at suspected corruption with the outputs in hand.
Troubleshooting
Historian tagnames showing a ? prefix mean hidden spaces
A ? prefix on a tagname in an aahDBDump export marks a hidden space-type character in the stored name, not a corrupt tag or lost history. Find every affected tag with a CHARINDEX query on dbo.Tag in the Runtime database, then rename them with the aahTagRename utility (TN Hist235), which preserves history and needs Historian stopped and disabled under store-and-forward protection.
Troubleshooting
Running redundant InTouch historians with parallel tag logging
InTouch has no dual-Historian target, so a partner Historian configured for redundancy stays empty. Log process data in parallel: the same tag list imported into both Historians, an IDAS on each node reading the OI Server. Handle historical alarms separately with A2ALMDB, because IDAS failover does not carry alarm data.
Troubleshooting
Fix historian silent data gaps with a registry value
The data is stored; the retrieval view of it is stale. On the Historian server, create the DWORD32 value UseFileCacheForRetrieval set to 0 under HKLM\SOFTWARE\ArchestrA\Historian\Programs\aahStorage, then refresh the trend, with no reboot required. Confirm the fix by loading a previously blank window before running any manual query.