Hello, everybody !

I work with a project for TP1500 Comfort in TIA portal v.13 Profess.

I have 25 analog signals in my project.

I need to create a screen where the operators will input/change some parameters for analog signals (LL, L, H, HH  limits), so I need  4 “I\O” fields for every analog signal.

Thus in the screen must be 25 tables with the same text fields absolutely, but the values in "I\O” fields must depend on certain analog signal which is displayed at a moment.

A question is how to organize everything better (less load to WinCC RT , more performance and efficiency).

I see at least 3 ways to solve the problem.

1. to make one basic table faceplate and to put 25 its instances into 25 layers one above another. When an operator chooses the certain analog signal to input the limits the correspondent instance table faceplate becomes visible ;

2. to make one table and :

2.1  to create in the table the required number of some GO (Graphic Object) for input and display the limit values.

Then in WinCC RT to change somehow the values in these GO (do not yet know how, maybe using the drop-down text list or "I\O field" or their combination) depending on analog signal which was chosen by operator before;

2.2  or to make one basic "I\O field" faceplate and to put 4 its instances into one layer (LL, L, H, HH) for every analog signal. Thus we will have 25 layers with 4 "I\O field" faceplate instances inside. When an operator chooses the certain analog signal to input the limits the 4 correspondent "I\O field" faceplates become visible.

How to make better ?

Maybe there is the better way than above mentioned.

Thanks in Advance.

U can use 2 methods :

1.  "How does tag multiplexing work?"    https://support.industry.siemens.com/cs ... 1807421/en

In my case I used this one and I could make everything without creating new PLC tags. I only created and used the internal HMI tags.

2.  How does address multiplexing work?      https://support.industry.siemens.com/cs ... 1808320/en  Here U must use / create  PLC tags.

The above mentioned methods (more exactly.#1) were optimal for me cause they didn't force to make a lot of faceplates.