Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

WinCC Faceplate Properties array in script

Created by: Marek93 at: 7/21/2021 8:34 AM (3 Replies)

Rating (1)

Thanks 1

4 Entries

7/21/2021 8:34 AM	Rate (0)
Marek93 Regular Member Joined: 2/17/2021 Last visit: 1/12/2024 Posts: 4 Rating: (4)	Hello everyone, Is it possible to use an array in script, which is declared in properties? I've been struggling with this problem for a long time. In the picture below you can see how I want to read values from an array. Line 3 is working without problem and value is read from tag. Line 4 is not working and I got a message „$ 20010 Error no tag 'Properties\UDT.History[0].DateAndTime'“ but the name of the tag is right. Line 5 is written according to instructions from siemens manual, but is not working. Does someone have answer?

Suggestion To thank Quote Answer

7/27/2021 10:41 AM	Rate (1)
Murof Platinum Expert Joined: 8/3/2009 Last visit: 4/25/2025 Posts: 15355 Rating: (1895)	Hello Marek93 I Think the problem is that you use an UDT Check out this Note in the TIA Help System: https://support.industry.siemens.com/cs/de/en/view/109773785/109377913227 look here for : " Current system behavior for dynamic access to elements of a user data type " Bye Murof
	If this Information really helps, you could use the Rate function
Suggestion To thank Quote Answer

8/9/2021 2:27 PM	Rate (0)
Marek93 Regular Member Joined: 2/17/2021 Last visit: 1/12/2024 Posts: 4 Rating: (4)	Hello Murof, thank you for your response. Yes, I think you are right. I cannot compose tag names like that. But also it is not possible to create array data types in faceplate properties. I cannot access my array without UDT. I wanted to make a scrolling function inside faceplate but it is not possible, however I made it with help from PLC. It is a pity, because I don't want to program things in PLC that are intended for HMI. Thank you.

Suggestion To thank Quote Answer

8/12/2021 1:23 PM	Rate (0)
Marek93 Regular Member Joined: 2/17/2021 Last visit: 1/12/2024 Posts: 4 Rating: (4)	Hello everyone, I got a official answer from Siemens about my problem: regarding your question about VBS SmartTags access within a faceplate. Generally you have to note that the faceplate configuration and interface linking is a engineering environment only. All that what you configure in the ES about the interface does not exists in the runtime anymore. The compile resolve the complete linking an interface properties to the instance connected variables. So in the runtime no SmartTag("Properties....") does exists anymore. The compile replaces Properties..... with the tag name which is linked at the faceplate instance in the screen. Therefore only SmartTags("Properties...") can be resolved which can be recognized exactly as interface property about the unique name. If you use indirect addressing for the SmartTags within the faceplate, the compile cannot recognize which HMI Tag is assigned at this Faceplate instance in the screen and cannot replace the SmatTags address during compilation. In Runtime you then get the Systemmessage in a Message View in the Message Class System that the script has an error and the object "Properties...." does not exists. Which is totally correct. Via indirect access via SmartTags you can access in runtime the global HMI Tags of the project only (e.g. SmartTags("DB_Machines.Machine1.OEE_Result")). Therefore at each instance in the screen you have to pass also the desired project and instance specific tag name into the Faceplate to the address indirect this global HMI Runtime tag via SmartTags.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Jen_Moderator

|

Share this page:

Share this page on...

Follow us on