HMI Number Looks Normal but Never Changes? Check Data Age and Quality
A believable number can be stale. When communication fails, an HMI may retain the last value unless the application deliberately shows bad quality or excessive data age. Diagnose the value, quality, and timestamp together instead of trusting a familiar-looking display.
General HMI diagnostic framework; available metadata and polling behavior depend on the platform.
What is happening?
Data passes through several stages: device sampling, controller processing, communication service, HMI acquisition, and screen rendering. A value may stop at any stage. Timestamp meaning is also important: the time a screen refreshed is not necessarily the time the physical measurement was acquired. In exception-based systems, an unchanged source timestamp can be legitimate; evaluate timestamp semantics and connection health before declaring data stale.
Check these five things
-
Compare the controller's source tag with the displayed HMI tag and confirm the binding points to the intended device.
-
Inspect available communication quality, status codes, and source or server timestamps rather than only the numeric value.
-
Review acquisition intervals, display refresh, deadbands, and visibility-dependent polling in the HMI configuration.
-
In a simulator, change the source through recognizable values and record when each layer updates.
-
Test the designed communication-loss indication and recovery behavior. Define an acceptable age for each operationally important value.
Worked example
A simulated tank level stays at 62 percent after the data source disconnects. The screen continues refreshing its clock, but that does not make the level current. A separate bad-quality indication or stale-data state prevents the old number from looking like a fresh measurement.
Quick diagnostic reference
| Displayed evidence | What it tells you |
|---|---|
| Value | Last available measurement |
| Quality | Whether the data is considered usable |
| Source timestamp | Age of the source update, when supplied |
The mistake to avoid
Do not use a changing screen clock as proof that all process tags are communicating. It may be generated locally by the HMI.
How to verify the fix
Confirm that disconnected, stale, recovering, and healthy states are visibly distinguishable and meet the project's operating requirements.
Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.
Technical reference
OPC Foundation: DataValue, quality, and timestamp definitions. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.