I am having some issues with the alarm tables in Ignition 8 when referencing a tag with an alarm on a 7.9 remote gateway.
(For reference on the gateway connection setup)
One of my companies clients is interested in moving their existing Ignition installation (version 7.9.10) to Ignition 8 for perspective.
The existing setup has a backend gateway that connects to 25 remote gateways. The remote gateways are just being used to pass through tags while the backend gateway is used for the HMI.
We created a test Ignition 8 gateway (b2019053102) and made remote connections to the backend for the tag providers and a query only version of the database connections.
We found that when we added the new perspective alarm table that it would just show an infinite loading screen and never load any alarms. As well, if we tried adding a vision alarm status table to a vision window the designer would just lock up and we would have to kill the designer process to close it.
If we disabled the “Alarms Enabled” in the remote tag provider then the vision alarm component wouldn’t crash the designer but had no alarms. The perspective component would still have an infinite loading screen displayed.
We tried creating a local test tag that just had an alarm we could toggle on and off. It was found that the vision component would show the local test alarm, but the perspective component still wouldn’t display any alarms.
We made a new blank Ignition 8 with the most recent nightly version to see if that would resolve the issue but still had the same issues.
However, we found that if all the remote connections were removed, the perspective alarm component would show the local test alarm.
So, it seems that if we have a remote gateway connection to a 7.9 gateway, the perspective alarm component will not load even local test tags, despite the option for alarms being disabled on all remote connections.
Is there a setting that we have missed that is preventing even local alarms from showing when there is a remote connection?