Hi,

I made a faceplate as shown in the attached pic. I'm planning to make use of it as a popup, as you would guess, so when clicking any analog reading from the main screen will show this popup. Now, im stuck on how to do the show/hide for this faceplate.

I can't using the visibility animation inside the faceplate as I already used it as a part of the faceplate to switch between tabs (home & settings).

Do you have any suggestions?

*by the way, Im not using UDT array for the analog tags so I'm assuming that the actual pop-up faceplate of TIA will not work.

Regards,

wantutri

Hi, thanks for the suggestion. I really also would like to use the integrated pop-up but I can't figure it out how to pass the correct tags to the pop-up faceplate as I didn't use an array for the analog tags. I attached the structure of my analog tags just in case there is an option to go for this first idea.

I will start to read the 2nd idea, just in case.

Thanks.

Lets have a tag "Pointer"
And a tag udt type "HMI_AL_Indexed"

Use a vb script with :

@sixthomas. Thanks! I will look into it.

@Murof, I'm using this for comfort panel

Regards,

wantutri

Just a quick update. I managed to do it by linking the visibility to an integer tag then just to proper visibility animation to the graphics inside the faceplate.

Regards,

wantutri

Just a tip, I'm not completely sure, but from my experience, "hided" object are present, but not display : what I mean is if you use lots of object on a screen, but hide 75%, is equivalent (from HMI_Runtime) to display, calculate, interact all the objects... 
What I want to say is, you can run like this, you can test on simulation, and all is right, but when you release on real HMI, it can be slow

I think that object which don't need to be always displayed, need to be in a Pop-up or on another screen with a "return function"
And I think, to facilitate modification, it's better to not overload a screen with lots of objects


Another tip, If you just want to "read" an udt, you can use the "pointer" specify above (VBscript in HMI or a FB in your CPU)
If you want to read/write, you can easily use a tag "indexed" in an array of udt
If you don't want the array, use a yourself indexed system in the CPU (one tag udt to read, one to write for example) and use an Int to change mode ("always read", "modifying", "write"), some buttons and of course, your index_tag (can be an I/O field with text list)
Use an invisible button on your simple object to set your index_tag to the good value, and open the pop-up
When mode "read", simply copy your real udt (selected by the value of index_tag) to the udt displayed on screen at every cycle
When mode "modifying", copy one time and display it, from HMI you change values temporarily before click "write"
When write, simply copy the temporarily udt tag to the real tag, one time, and return in "read" mode

Hope this helps

Hi wantutri

I think you can use object:screen window to do this. when you use mouse click valve icon ,that screen window will visible on screen.And your faceplate can inside screen window. Then your HMI tag setting need modify something.It can use "Tag Prefix" setting on screen window.

1.make new screen and put your faceplate on this screen.

2.On your valve screen, insert Controls:screen window on valve screen

3.Setting screen window parameter: Display screen / Tag Prefix

4.others setting please reference "Tag Prefix"