Power Chart doesn't reflect loss of connection to Remote Tag Provider

Ignition
1

Hi everyone,

I'm facing an issue in a distributed Ignition architecture and would like to understand whether this is expected behavior or if there are ways to mitigate it.

Scenario:

  • I have a main Ignition gateway (full version) running the entire Perspective application.

  • There are two Ignition Edge gateways running on edge computers, which:

    • Perform local OPC tag acquisition.

    • Act as Remote Tag Providers for the main gateway.

    • Store data locally in databases.

Problem:

When the main gateway loses connection to the Edge gateways, Perspective charts (e.g., Power Chart) continue to display the last received values, as if the data were "frozen".
There’s no clear indication that the data source (remote tag provider) is unavailable. This could mislead operators into thinking that the system is still online and updating properly.

Is there a way to configure the Power Chart (or another chart component) to stop displaying data when the Remote Tag Provider is offline?

Any suggestions or best practices would be greatly appreciated!

2

You could create alarm tags on the main gateway looking at the quality of tags on the edge gateways, then do an overlay, an alarm banner, or something on the views to reflect the loss of comms to the edge?

3

That wouldn’t exactly solve my problem…

What I’d like is a way to configure the Power Chart to stop displaying data from the moment the Remote Tag Provider goes offline — in other words, to break the line on the chart at that point.

However, it should still display the previously stored historical data normally.

The idea is to prevent the chart from showing “frozen” data as if it were still updating in real time, which could be misleading to the operator.

4

If the provider is down, the very next refresh is going to break it either way.

I don’t see any way of doing what you are expecting, without redundant connections/historians.

Or a lot of custom programming to store the dataset locally in a cache and trend that vs direct connections to the historian.