Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Display UserName and LocalMachineName in Client

Created by: dwilder at: 10/26/2006 12:30 AM (25 Replies)

Rating (1)

Thanks 4

Result pages:: |; 1 | 2 | 3; |

26 Entries

Entries per page: 10 | 20 | all

10/26/2006 12:30 AM	Rate (0)
dwilder Posts: 58 Rating: (4)	Greetings. I have searched through the FAQs and forum threads for an answer to my question, but I have not come across it yet. I understand that @LocalMachineName and @UserName are local tags on each computer that are intended to contain the machine name and the WinCC user name respectively. I was hoping to display this information on each of the clients in out multi-user project and use this information in various global procedures. For the login information wehave addedtext fields on the picture where the font text is linked to thesetwo fields. This way we can look at the screen and see what user is logged on to the station and see the station name as well. On the Server thisworks as expected, buton the clients, which have their own client project with the server package loaded in, we are notgetting anything in these internal system tags when we look at them. On thepictures where we have addedthe fields, we are only seeing the Server machine name and user name. In the Client side global scripts the@LocalMachineName and@UserNametags are empty. Do we have to use the SIMATIC LOGIN option to have these fields work for us? Thanks, Dan
dwilder Posts: 58 Rating: (4)
Suggestion To thank Quote Answer

10/27/2006 9:57 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Hi, no you don;t need to have simatic logon for this. and it shoud work as you wan to have it. Please have a look in wincc explorer on the clients project. Locate the @localmachineName tag and hover over it (be sure to do this when being in runtime). Now a tooltip text will pop-up telling you the content and state of the tag. could you please reply that information back in the forum/post? Thanks in advance, with regards, Ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

10/27/2006 7:57 PM	Rate (0)
dwilder Posts: 58 Rating: (4)	Hi, Yes, here is the information: @CurrentUser Process value : operator Quality: 80 Last Change: 25/10/2006 2:38:30 PM and @LocalMachineName Process value : DELCDCCR002 Quality: 4c - Start value Last Change: 25/10/2006 1:33:22 PM So this looks correct, does it not? Thanks, Dan
dwilder Posts: 58 Rating: (4)
Suggestion To thank Quote Answer

10/27/2006 8:44 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	[quote user="dwilder"] In the Client side global scripts the@LocalMachineName and@UserNametags are empty. Dan Dan, When you say that in the client side "global scripts" you mean you're using the tags in scripts? Or are you just trying to show them directly, in static texts? Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

10/27/2006 9:19 PM	Rate (0)
dwilder Posts: 58 Rating: (4)	Hi Danielle, We are showing the @LocalMachineName and @CurrentName in a static text field on the screens. We would expect that information to be different on each machine and depending upon what user is logged in. As well, we have this information in Global VB scripts. For example, when a user left clicks on a button to start/stop equipment, we have VB script tied to that event. These event scripts then invoke a Global VB script where we reference the LocalMachineName and UserName tags. In that Global script we validate the user request (that is the authorized user must be logged in to certain machines only in order to take these actions) and as well we log the user activity, including the machine name. At least that is the plan. Each client has a local copy of theglobal VB scripts that we had to copy from the Server. Dan
dwilder Posts: 58 Rating: (4)
Suggestion To thank Quote Answer

10/27/2006 9:43 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	I usually use more C Scripts in WinCC, so I'm more used to them... In C there are the Local and Global actions, and local actions may be assigned to a computer, while global actions are executed on all of the project computers in a Client-Server project. I realize that in VB there are the Standard and Project Modules, and Standard Modules contain procedures which are globally available to the project, while Project Modules contain project-specific procedures. I'm not sure about this(and I can't conduct any tests right now, sorry), but if you're using Computer-local updated tags within the script you should be using project modules, right?
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

10/28/2006 11:39 AM	Rate (0)
Mehrnoosh Posts: 102 Rating: (9)	Hi Dan If you have a multi user project, I think you don’t need a local copy of your script and graphics. -Put an I/O field, dynamic its output value with “current user” tag. -Change the data format to string. -Do the same action for “machine name”. - Make your I/O fields as big as you can see whole data on it. Now you must see the user name in each client. If you can see the correct user and client name, it means you have the correct data (which it seams you have due to 3rd post). If your user can perform an action only in specific client: - You need a script on the action (for example mouse click). It is not an action defined in global script; it is in graphic where the user wants to perform an action. - In the script you must read the user name and machine name. In a “case structure” check if the user can perform this action on this machine or not. - You can save the action in a User archive as well. - You can do this in C or VB. Remember you do not need a local copy of any thing. Best regards, Mehrnoosh
Mehrnoosh Posts: 102 Rating: (9)
Suggestion To thank Quote Answer

10/28/2006 8:53 PM	Rate (0)
dwilder Posts: 58 Rating: (4)	Hi Mehrnoosh We have a Multi-User project, but remember, there are two types of clients in a Multi-User project. There are those that do not have their own project and instead just open the server project. Then there are those that have their own client project and load the server package. Projects that have redundant servers (as we do) must use the latter type of client - that is a client with their own project. With a client without its own project we can do all that you have suggested, and that is what we would like to do. However this does not work when we are using the client with its own project, and as I said we are required to do that because of the redundancy option. So what we are seeing on the Client system with these tags (@CurrentUser and @LocalMachineName is: 1) Using WinCC Explorer we are seeing the correct expected values as shownin the reply above. 2) The graphic screen is showing the same on the client and server screens with the server log in information. That is the @UserName and @LocalMachineName from the server machine and not from the client. The client does not have its own pdl screens,it is using the server pdl screens. 3) The Client side Global VB scripts in the Project Module are showing blank for the @CurrentUser and @LocalMachineName tags. Assuming that we are able to get the @CurrentUser and @LocalMachineName tags to work as expected in this environment we are planning to use them in the scripts to validate the user action as you have suggested. The other thing that we are hoping to do is to be able to use this information to determine the "Operator-Control Enable" setting for various buttons and control devices. If we were using a client without its own project we would be able to use an internal tag with "Computer-local update" selected for this purpose. However this will not work with clients with their own projects. So, we are hoping that we would be able to use scripts and the @CurrentUser and @LocalMachineName to get around this problem. Thanks, Dan
dwilder Posts: 58 Rating: (4)
Suggestion To thank Quote Answer

10/30/2006 6:47 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	[quote user="dwilder"]So what we are seeing on the Client system with these tags (@CurrentUser and @LocalMachineName is: 1) Using WinCC Explorer we are seeing the correct expected values as shownin the reply above. 2) The graphic screen is showing the same on the client and server screens with the server log in information. That is the @UserName and @LocalMachineName from the server machine and not from the client. The client does not have its own pdl screens,it is using the server pdl screens. 3) The Client side Global VB scripts in the Project Module are showing blank for the @CurrentUser and @LocalMachineName tags. The other thing that we are hoping to do is to be able to use this information to determine the "Operator-Control Enable" setting for various buttons and control devices. If we were using a client without its own project we would be able to use an internal tag with "Computer-local update" selected for this purpose. However this will not work with clients with their own projects. So, we are hoping that we would be able to use scripts and the @CurrentUser and @LocalMachineName to get around this problem. Thanks, Dan Hi Dan, When you say the scripts are showing blank you mean when you transfer @CurrentName to a Computer-local update tag you get nothing or haven't you tried that yet? Also... in this thread /tf/WW/en/Posts/5541 an user detected that when you trigger an action with @CurrentName, that tag doesn't receive the new user's name right away, it takes a while for that to happen. If the action triggered by @CurrentName upon change transfered the name to another tag with no delay, the other tag would be empty. Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

10/30/2006 8:00 PM	Rate (0)
dwilder Posts: 58 Rating: (4)	[quote user="Danielle"] Hi Dan, When you say the scripts are showing blank you mean when you transfer @CurrentName to a Computer-local update tag you get nothing or haven't you tried that yet? Also... in this thread /tf/WW/en/Posts/5541 an user detected that when you trigger an action with @CurrentName, that tag doesn't receive the new user's name right away, it takes a while for that to happen. If the action triggered by @CurrentName upon change transfered the name to another tag with no delay, the other tag would be empty. Best regards, Danielle Danielle, For now I have just tried displaying the CurrentUser and LocalMachineName in a trace message. As to transferring them to a Computer-local update tag, I do not think that is an option as we are using a client with its own project (required due to redundancy). With clients with their own project the Computer-local update tags are not supported. I had already looked at that thread you referenced with respect to the delay, and it is not relevant to us at this point. Any other ideas? Thanks, Dan
dwilder Posts: 58 Rating: (4)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on