Edge computing and IIoT
Earlier articles
Troubleshooting
Recovering lost access to an IIoT edge connector
The vendor-documented way back into a locked IIoT connector is the full software image: it clears the installed configuration and returns the device to its factory login state, whose initial credentials the product documentation defines. The update image keeps settings, so it cannot clear an access problem. Plan the configuration rebuild and change the initial credentials immediately after first login.
Troubleshooting
Troubleshoot Node-RED OPC UA When UaExpert Connects
UaExpert connecting proves the server is up, not that Node-RED negotiates the same endpoint and certificate exchange. Set the security policy to None on an isolated network: if Node-RED then connects, the fault is certificate or encryption compatibility. The deciding evidence is the server-side log line for the same attempt, time-correlated against Node-RED's error.
Selection guide
GeoSCADA Data Tables or an external SQL database
Keep the records in native Data Tables while each retained table stays within the documented 100 MB maximum and writes are infrequent, exporting and trimming what you keep. Move to an external SQL database with ODBC linked tables when growth, business data ownership, or several SCADA systems needing one source of truth dominates, and call that database from client scripts or a separate service, never from logic.
How-to
PLC MQTT failover to a redundant second broker
Yes, with limits. A PLC MQTT client can switch to a second broker without anyone touching it, provided the library supports a second broker destination and you program the trigger, the reconnect sequence and the subscriber-side recovery yourself. Two independent brokers share no sessions, subscriptions or retained messages, so this is failover with a computable gap, not hot standby.
Troubleshooting
Why Citect alarm logging never reaches SQL Server
Alarms that populate the runtime page but never reach the SQL table mean the display path works and the logging path does not. Test three links in order: the alarm category's Log Device binding, the ODBC DSN and device connection including DSN bitness, then the INSERT format string. Read the syslog first and trace with SQL Profiler second — no traced statement puts the fault on the SCADA side, a failing statement puts it in the table or format.
Troubleshooting
When an edge gateway has no MQTT subscribe function
An IIoT secure interface gateway whose software shows only Broker Configuration and Publish has no MQTT receive function: the link is outbound telemetry only, and a connected broker proves nothing about subscriptions. Keep it as a telemetry link, or put the subscription on a separate documented endpoint when cloud-to-machine commands are required.
Explainer
What the Historian Runtime migration script's SQL users mean
The script reconnects the six restored Runtime database users (wwAdmin, wwUser, wwPower, aaAdmin, aaUser, aaPower) to destination server logins and assigns database ownership to the aadbo login. aadbo is a named login the procedure expects, not your current username: run the line as written, create any missing logins through the release's configuration procedure, and verify with the account the Historian service uses.
How-to
Trace a PLC tag from controller to historian display
Trace one existing, noncritical measurement end to end: controller source, collector mapping, historian point, optional calculation, then display binding. Check the value and the timestamp at each boundary before you change any configuration. A value that matches and a timestamp that agrees at every step means the path is sound; the first mismatch names the layer to fix.
Explainer
SQL Server CAL count for historian clients: how to size it
SQL Server CALs attach to the people and devices that reach SQL Server, not to historian client sessions or pooled connections. Trace every SQL access path - historian server services, collection nodes, trend and report clients, embedded controls - to its users and devices, count both populations, and buy whichever count is smaller. The historian's tag count, even 25,000 tags, sets neither the SQL edition nor the CAL total.
Troubleshooting
Replicate to PI needs PI Web API 1.16 or later
Replicate to PI from AVEVA Historian 2023 R2 sets no PI Server version requirement. The only stated floor is PI Web API 1.16 or later on the PI side, and the feature exists from Historian 2023 onward. Read the PI Web API version first; if it reads below the floor, upgrade PI Web API, and treat the Data Archive version as a PI Web API compatibility question, not a replication blocker.
Troubleshooting
PI-to-PI interface service will not start from FactoryTalk Historian
When the PI-to-PI interface service will not start, the fault sits in the local launch, access to the two historians, or the FactoryTalk Historian license, which must permit native OSIsoft clients. Capture the exact startup error, work the three gates in fixed order, then prove the destination with values, timestamps and quality.
How-to
Move PI historian data to another PI server without MQTT
The PI Connector for MQTT only subscribes to a broker and writes into PI; it cannot publish, and a PI server has no broker role. Move tag data between two PI historians with the PI to PI interface. Use MQTT only when policy mandates a broker, and then add your own publisher on the source.