I'm seeing an issue with the Power Chart in Ignition 8.3 Perspective. When adding a tag to the trend, the trend begins "flickering" and is nearly unusable. It seems like maybe some kind of delay with polling trend data?
In the attached video I am using a pre-made page with a Power Chart component that comes with the Kanoa Ops module, however I see the same thing on other gateways by creating a new view and dropping a Power Chart onto it.
I see this behavior in 8.3.3 and 8.3.6. I do not see this behavior in 8.1.22.
In the video I am using a tag from a Core Historian, but I see the same behavior using a SQL Server backed historian.
Any ideas on what could be causing this behavior?
Ok, I think I've narrowed down the issue slightly. I don't think this is a version problem, as I have found correct behavior in multiple projects on 8.3. Whatever the problem is, it seems specific to one project that I am working with.
When the power chart has a historian tag active, it repeatedly polls for data, I'm assuming this is related to data refresh. In the project I'm trying to troubleshoot, the component occasionally tries to fetch the same resource twice, and the second request always fails. I suspect this may be causing the graph to fail to display data, but I'm a bit at a loss as to why this is happening.
PerspectiveTimeserie…2bf541937ba438.js:2
GET http://localhost/data/perspective/fetch/Coating%20Line/e8ad6a5d-5eb2-48c6-936b-fbca02279439 403 (Forbidden)
fetchSeriesData @ PerspectiveTimeserie…2bf541937ba438.js:2
(anonymous) @ PerspectiveTimeserie…2bf541937ba438.js:2
Promise.then
fetchSeriesData @ PerspectiveTimeserie…2bf541937ba438.js:2
handleEvent @ PerspectiveTimeserie…2bf541937ba438.js:2
dispatchEvent @ PerspectiveClient.5a…4170c920d80c72.js:2
dispatchChildEvent @ PerspectiveClient.5a…4170c920d80c72.js:2
dispatchEvent @ PerspectiveClient.5a…4170c920d80c72.js:2
dispatchEvent @ PerspectiveClient.5a…4170c920d80c72.js:2
eventFiredFromGateway @ PerspectiveClient.5a…4170c920d80c72.js:2
processMessage @ PerspectiveClient.5a…4170c920d80c72.js:2
Support indicated that this is a known issue caused by project names which contain spaces.
