Hi

I'm trying to read the @UserName tag on a unified comfort HMI using the script below but cannot seem to get the statement to return true. When I connect the @UserName tag to an IO field, I can see that the value within the tag is "SEW" which is what is expected yet the return of the script is still false.

Any ideas where I'm going wrong?

V18 Upd 3

Do you know of a way I can get round that? I need to know the current logged in user and send this information to the PLC either by string or bool

Stefan Arcularius

Hi LWilliams94,

You cannot access @UserName within a scheduled task because it is a local system tag. See system manual for details.

Kind regards
Stefan

Hi Stefan,

I have followed what you have suggested but the issue I have now is that the statement doesn't return false once I logout. Any idea why this might be? I have checked the value of the @UserName tag using a IO field and it shows empty when I logout so can't see a reason why the script would not change the value back to 0.

edit: It seems that the @Username tag does not change once you logout so the value would never retun false.

Stefan Arcularius

Hi LWilliams94,

You must run the script in local scope when the tag value changes. To do this, you must use dynamization on an item property of your choice. However, it is important that this item is always visible. You can use the screen management to configure the properties of the root screen. There you create a main window and create a script to dynamize a property. In my example, I used the 'Left' property. For the script it is important to return a value (in case of 'Left' just return 0) and since you are using two tags but only one is read you should change the trigger to manual to trigger only on changes to '@UserName'. Otherwise the script will be triggered on changes to the second tag as well.

Kind regards
Stefan

Hello LWilliams94

do you use it in a PC RT or a Unified Comfort Panel?

I have used such a function in the last projects and here I used it to jump back to the main screen after logout. This seems to work ..

So I would try to test with a Script on Value Change of the @CurrentUser and here just do a Trace.

Then you can check if only the trigger does not work or if there are some issues in your script

Bye Murof