Hello everybody,

I read the sample in this link:

https://support.industry.siemens.com/cs/ww/en/view/66839614 

in this sample, every motor or valve needs its own screen window with the tag prefix fixed, which means screen window are a lot.

is there better solution to pick out "motor001." through the interface tag "motor001.QdwState", and set the tag prefix with it?

thanks a lot in advance

realauto9999

Hello everybody,

I read the sample in this link:

https://support.industry.siemens.com/cs/document/66839614/example-blocks-for-wincc-(tia-portal)-and-step-7-(tia-portal)-for-s7-1200-and-s7-1500-with-scl?dti=0&lc=en-WW

in this sample, every motor or valve needs its own screen window with the tag prefix fixed, which means screen window are a lot.

is there better solution to pick out "motor001." through the interface tag "motor001.QdwState", and set the tag prefix with it?

thanks a lot in advance

 sorry, I use WinCC Professional V15

realauto9999

 

realauto9999

Hello everybody,

I read the sample in this link:

https://support.industry.siemens.com/cs/document/66839614/example-blocks-for-wincc-(tia-portal)-and-step-7-(tia-portal)-for-s7-1200-and-s7-1500-with-scl?dti=0&lc=en-WW

in this sample, every motor or valve needs its own screen window with the tag prefix fixed, which means screen window are a lot.

is there better solution to pick out "motor001." through the interface tag "motor001.QdwState", and set the tag prefix with it?

thanks a lot in advance

 sorry, I use WinCC Professional V15

 If by "pick out" you mean find the name of the tag through scripting that you would probably want on the Click event of the faceplate instance then I fear you are not going to be able to do it.  There seems to be no way to get information like that in runtime scripting, only the value, last update time, status of the tag.

You could add another interface string parameter that you explicitly set to the name of the tag prefix, then use scrpting to access that.  You have to tie this paramater to some animation within the faceplate for you to be able to set a static value for it otherwise it will only allow you to tie it to a tag (who thought that was a good idea when designing this package?)

Once you have a string in the script that has your tag name in it, then you can assign it to the TagPrefix of a single ScreenWindow object and open that window to show the popup for the selected motor/valve.  Different faceplate instances would assign different tag prefixes.  Note that with a single ScreenWindow you can only open the popup for a single motor/valve at a time.

I wonder whether there's some way to create a new ScreenWindow object from within a script, assign the prefix to that and open it.  That way each valve could create its own ScreenWindow when you click it rather than having to create every one during configuration.  Then you could have multiple popups open at once.

Hope this gives you some ideas.

Freemaster

 If by "pick out" you mean find the name of the tag through scripting that you would probably want on the Click event of the faceplate instance then I fear you are not going to be able to do it.  There seems to be no way to get information like that in runtime scripting, only the value, last update time, status of the tag.

You could add another interface string parameter that you explicitly set to the name of the tag prefix, then use scrpting to access that.  You have to tie this paramater to some animation within the faceplate for you to be able to set a static value for it otherwise it will only allow you to tie it to a tag (who thought that was a good idea when designing this package?)

Once you have a string in the script that has your tag name in it, then you can assign it to the TagPrefix of a single ScreenWindow object and open that window to show the popup for the selected motor/valve.  Different faceplate instances would assign different tag prefixes.  Note that with a single ScreenWindow you can only open the popup for a single motor/valve at a time.

I wonder whether there's some way to create a new ScreenWindow object from within a script, assign the prefix to that and open it.  That way each valve could create its own ScreenWindow when you click it rather than having to create every one during configuration.  Then you could have multiple popups open at once.

Hope this gives you some ideas.

 Thank you for your information, Freemaster.

I have  experiences in Step 7 + WinCC.

Acutually with Step7 + WinCC, your question would be yes, there is some way, pls check this link.

Step7+WinCC Sample

and I copy the key script to TIA, and tested it, it still works.

I don't know why TIA's sample didn't use this method. I think the old method is smarter.