Hi,

TIA V15.1, TP1200 comfort

I have 2 faceplates on a screen, that I want to "coordinate" (this faceplates are used several time on another screen)
I want to rotate them, after a long search, I find nothing, so I create 4 faceplates (up, right, down and left) and put one above the other.
I just have to set visibility for one and invisibility for the 3 remaining, but, I already use visibility for some of item in my faceplate...
So I try to use several pop-up (it works), but remember, I have to coordinate 2 faceplates, and we can't use 2 pop-up at a time...
So I try VBscript to set the .top and .left of the faceplates to move what I don't want away, but it doesn't compile "Faceplates are not supported in scripts"
So modify position of faceplate seems not possible, what about create from nothing ?
I try to use the "layout", but don't find a way to set (in)visibility of one layout
Here, I'm out of idea

Anyone ?

Hello sixthomas,

sixthomas

I just have to set visibility for one and invisibility for the 3 remaining, but, I already use visibility for some of item in my faceplate...

This is the right way to go, when making faceplates invisible.
When you have used visibility for some parts of your faceplate already, then you must implement a kind of "state" for the visibility.

1. In the interface you need a "faceplate visibility" boolean variable, which make the whole faceplate visible or not.
2. Inside the faceplate you need as much boolean variables as there are groups of objects which visibility you want to control independently.
3. Now, identifiy states and set up switch-case construct, which reacts to the state.
   (alternative: if-else construct and check of conditions)
4. In the state, you set the corresponding visibility booleans.
5. Run the script in every change of variables (state or other variables like interface). Depends on your implementation

  pseudo code:

I hope this his helpful, ask if you have questions.

Reagards,

Nzett11
 

I was thinking about this solution but was thinking about use script "outside" the faceplate, I forgot I can run script "inside" the faceplate. I think it's the good way to go. Thanks !

If I extend, I tried (years ago) an all in one faceplate with 4 orientations (up, right, down and left) and use property to set (in)visibility : it works very well on simulation, but was extremely "laggy" on TP1200 (if use several on one screen) -> perhaps I can use "inside" script to "move object" instead of "duplicate them and set visibility for each". It will be a sort of rotating script. If it works, it will simplify future changes !

edit :
Before going further, I find that in script inside faceplate, we can't use HMIRuntime.object, so we can't move object or anything, we can just change visibility and appearance, so it doesn't really help to do an all in one faceplate...

I just did the changes and want to test it.
Sorry but, how to activate the "inside script" ? I can't find how to put an "event on change value" on propeties-tag, or like with screen on "loaded" faceplate ?

I just find this, with no answer :
https://support.industry.siemens.com/tf//WW/en/posts/faceplate-call-script-inside-faceplate-when-loaded/105417?page=0&pageSize=10

I can't use event on change value on my actual propertie, because it's an udt... and even if it's possible, it's not really convenient
So I have to add a propertie_faceplate on every faceplate with a life_word, just to call the script one time at the loading ??

Hello sixthomas,

I don't know if I understood you correctly, but there should be no problem using UDTs as interface variables of faceplates.

As you can see in the attached screenshot, I can use the "value changed" event on an UDT member variable.

Regards

Nzett11

Hello,
Yes you're right, I confused with event on value change directly on udt HMItags (not in faceplate)
To call one time my script at "loading" faceplate, I use a new property 'refresh'
I first put an internal tag, and use script at loading screen to change value of this propertie 'refresh', but it doesn't work, because TIA prevent infinit loop with internal tag (event on value change trigger only with an I/O field)
So I use a CPU link tag

There it is :
Screen "screen_with_faceplate"
CPUTags "refresh_faceplates"
Faceplate "faceplate1", where a script inside the faceplate used to be called at least one time at the loading, triggered with event on change value at the 'propertie/Refresh'

At loading screen, use script or directly put 'refresh_faceplates' to 0
In CPU, always put 1 to this tag (or increment every cycle)

Faceplates will trigger there script at loading
If you want trigger on another event on value on another propertie, you can

Add a button on screen to reset the tag refresh, to refresh all the faceplates if needed, or increment every seconds if needed (but with CPU, never with HMI)

finish

So now, when I use a faceplate "complicated" or "animated" I proceed with 2 properties :
- refresh (inside script on change value, to do what you need, called at least the first time)
- Visibility (inside script on change value, to set visibility by group in the faceplate, I personally use internal bit)
Instead of using 4 faceplates (Orientation up, right, down and left) I can use only one faceplate with this 2 properties -> time saver