Hi, this is a very useful feature.

When can we expect to use local variables as index tags in address multiplexing? I feel like this is a missed opportunity.

Regards

------------------------------------------------------------------------------------------
Split from Simple Sample and TIPs - WinCC Unified - local variables.

Hello SpeedsterJuss

I´m I wrong or does it work already? (perhaps I missunderstand your request...)

If you use Address Multiplexing in WinCC Unified (both Adress multiplexing with abolute addressing and address multiplexing with symbolic addressing) you can use internal HMI Tags for index in symbolic addressing (for Index in the Array) or as variable address number in absolute addressing.

or

Bye Murof

Murof

Hello SpeedsterJuss

I´m I wrong or does it work already? (perhaps I missunderstand your request...)

If you use Address Multiplexing in WinCC Unified (both Adress multiplexing with abolute addressing and address multiplexing with symbolic addressing) you can use internal HMI Tags for index in symbolic addressing (for Index in the Array) or as variable address number in absolute addressing.

or

Bye Murof

 TIA V18 added a new extension. Internal tags can now be declared as being local. Meaning that each device has a personal value for them.

The problem is that I cannot use local internal tags as index tags for multiplex tags.

Stefan Arcularius

Hi SpeedsterJuss,

That would be a question for product management or developers.

But I think it would take a couple of years if it ever came to that. From a technical point of view, it would not be that easy. You can just imagine the case where one session requests the data for index 0 while another session requests it for index 1. Which data should be read from the PLC first?

Kind regards
Stefan

 PLC should just stack those requests up and deal with them one by one. It takes little to no time. Same when writing values with multiplex tags.