HI guys,

I am using WinCC Unified PC Runtime V19.

I noticed a strange behavior of my faceplates in Runtime.
When I open the screen where my faceplates are, for a short amount of time (maybe less than a second) all my facelpates are displayed in default mode I designed them in TIA Portal, and after this short time they are dispaying normal values from the PLC.

For example, I designed my faceplate for a pump, and it has inside of it three icons (pump off, pump on, pump in alarm). They are layered one behind another in the faceplate, and depending of the pump status in the PLC I activate the visibility of the coresponding icon. This is all done inside of the faceplate. I conected my PLC variables to faceplate via Tag Interface option in faceplate.
If my pump is ok and it is running, when I open the screen where I am showing this pump faceplate for a short amount of time the pump icon will be dispayed in red color (pump in alarm) and after that it will dispay the real status and that is that pump is ok and running.
Pump icon in red color is top off all other icons in faceplate (pump off, pump on), but still the PLC variable for activating this icon is not active.

I don't know how to get rid of this behavior in my Runtime, can somebody please help me with this?

I attached the short video so you can all see what I am talking you about.

I think that changing refresh rate does not help much. Problem is that you are changing the screen. Tag which is connected to the faceplate was never used and WinCC needs to get it from the PLC.

You can test it lets say creating some invisible field on the main screen (with this tag connected), then change the screen to one with your faceplate on runtime. Since tag will be refreshed from the PLC (through the main screen) your faceplate will display "properly". This is because of the "Acquisition mode" which is set by default to "Cyclic in operation".

If your project is not so big you can change this to "Cyclic continuous". Then tag should be acquired from  the PLC even if the control (faceplate) was not on the screen yet. But I will suggest to not doing like that and design faceplate in such a way that its default state will meet your requirements, will use less resources for sure.

You can read about it here: Defining the acquisition cycle for a tag (Basic Panels, Panels, Comfort Panels, RT Advanced)

If this is not case I guess i need to have project to see what you are doing.