PI Vision Not Updating or Showing Wrong Data? Troubleshoot It
When a PI Vision display shows stale, blank, or incorrect data, first determine whether the problem exists in the display or in the source. Check the display's PI Point or AF attribute reference, compare the underlying PI history, then work upstream through analyses, interfaces, and source systems as needed.
The fastest fix is usually not the first thing people try. Editing the display can hide a problem that actually started upstream.
First, define the symptom
Display won't load: Check whether the issue affects one user, one display, or the whole PI Vision environment. Browser, authentication, network, and service issues can look similar.
Value is blank or in error: Inspect the symbol's source reference, underlying data quality, permissions, and server availability.
Value is stale: Compare the displayed timestamp with the actual event history on the source PI Point. A value can remain visible after its source stops writing.
Value is wrong: Verify that the symbol points to the intended production server, AF database, element, and attribute. A display can show valid data from the wrong source.
Trace the value backward
A useful troubleshooting order is:
1. PI Vision display and symbol.
2. Direct PI Point or AF attribute referenced by the symbol.
3. Underlying PI Point and Data Archive.
4. Analysis or interface producing the value.
5. Upstream control-system or sensor source where applicable.
At each step, compare values and timestamps at the same moment. A mismatch tells you which boundary deserves investigation.
Watch for migration leftovers
After a DEV-to-PROD migration, a display or AF reference may still point to an old environment. If the development server is retired, users see errors that don't clearly identify the bad display or object.
An inventory of display references helps locate these dependencies without opening every screen. Osprey can help PI teams inspect discovered PI Vision sources and related AF/tag mappings so they can narrow the search before correcting the configuration.
Frequently asked questions
Why does PI Vision show an old value even when the display loads?
The last known value may still be visible even though the source tag, interface, or analysis has stopped updating.
How do I find which display references a retired PI server?
Review an inventory of display sources and AF mappings for the old server name, then validate affected displays.
How can I tell whether PI Vision or AF is the problem?
Inspect the display's AF path, read the AF attribute and underlying PI Point independently, and compare timestamps and values.