It feels like the platform is slow while swapping windows. Tag overlays always takes 2-5 seconds to go “normal” after window swap.
If I have a leased tag groups with 2 sec driven class and 60 sec when not in fast mode. Should not the quality overlays when opening a window all be “normal” to begin with, given that all tags has been updated the last 60seconds?
Moreover, I have a template which shows around 30 states from a PLC (multistate indicators). This template uses indirect addressing based on an input “UdtAddress” .When changing the address for the template (actually swapping the PLC behind the path), all indicators loads for 2-5 seconds before updating with the new tag values.
This should not have anything to do with the tag setup right? (I am running OPC tags, through a FT Gateway server.) I expect my remote tag providers to always deliver “normal” quality data to the Front End vision server.
The changes in 8.0.10 directly affected how expression bindings evaluate on initial window open. Before these changes, expressions would evaluate with bad quality if referencing any tags, since the tag value would be null during first execution. These evaluations will now return an uncertain initial quality (rather than bad) if the initial tag value hasn’t yet been returned from the gateway, and then once the value is returned, will execute again with the proper value / quality. The unknown qualities shown (gray overlays) when toggling between screens is currently intended behavior to show that the tag value has yet to be initially returned from the gateway. There shouldn’t be any bad quality (red overlays) shown on window open unless the tag / binding is in fact bad.