TDengine TSDB-Enterprise

Global – October 29, 2026 -- Industrial historians should default to data-change subscriptions for continuously monitored OPC UA process variables and reserve polling for explicitly periodic records, according to collection guidance tied to TDengine TSDB-Enterprise.

Polling leaves a blind spot between reads

A polling client issues Read requests at a fixed interval, so a ten-second poll fetches the latest value every ten seconds whether or not it changed. If a motor status flips from 0 to 1 and back to 0 inside that window, both surrounding polls return 0. A shorter interval cuts the risk but raises load, and it never removes the gap between samples.

Polling fits periodic reporting, slow-changing values that need regular records, and servers with weak subscription support. A quality report requiring one temperature record per minute, including unchanged periods, is a polling case.

Global – October 29, 2026 -- A restored OPC UA connection does not guarantee that the historian holds every value generated during an outage, because the three links in the data path (source, collector and historian) each lose data in different ways. Buffering at one layer cannot repair a loss that occurred earlier in the chain.

In the common architecture of device or PLC, OPC UA server, collector and historian, the first step is to find which link failed. If the device or server stops producing values, the collector has nothing to recover unless the source keeps its own history. If the collector cannot reach the historian, a durable local buffer can protect messages it has already collected. Treating all three as a generic network outage leads to the wrong fix.

Global – October 29, 2026 -- Industrial historians that store an OPC UA value and timestamp without the accompanying 32-bit StatusCode can pass stale, substituted, or Bad readings into averages, alarm reviews, and production calculations as ordinary process measurements.

StatusCode carries more than a Good, Bad, or Uncertain label

Every OPC UA DataValue can contain a value, timestamps, and a StatusCode. The severity class is Good, Uncertain, or Bad. The remaining bits can carry a specific subcode and information bits, such as monitored-item queue overflow, limit state, or changed semantics.

The SemanticsChanged bit can indicate that metadata such as engineering units changed and should be re-read before processing. A value of 100 is not comparable with the previous day's 100 if the unit or scale changed in between.

Global – October 27, 2026 -- A successful OPC UA connection check shows only that a client can reach the endpoint. It does not prove the intended nodes are readable, monitored, mapped or written to the historian, according to a five-step troubleshooting workflow for industrial data pipelines.

The method starts with one known, changing point, traced from the OPC UA server to one expected historian table. Large tag lists hide the first failure.

Global – October 27, 2026 -- The right OPC UA collection rate is the slowest configuration that still preserves the process behavior needed for operations and historical analysis, and it is set across five separate stages rather than one "scan rate." Device updates, server sampling, subscription publishing, filtering and historian storage each have their own timing. Treating them as one setting can add load without adding information, or hide a pressure transient the historian was expected to explain.

Server sampling cannot beat the source update rate

A PLC may update a temperature every 500 milliseconds while the OPC UA server refreshes its internal value once per second. A client request to sample every 100 milliseconds then re-reads the same value or detects changes no sooner than the server exposes them.