FactoryTalk Launch name

faeldebrito

Member
F
Join Date
May 2021
Location
BH
Posts
5
I have a FactoryTalk View SE application with 4 clients. These clients are operated from different locations, so I need to somehow identify them through code to perform different actions.
My initial idea would be to put this information in an auxiliary variable, but as all clients would write in this same variable, it would overwrite. If I use more than one variable, then I can't identify via code which variable the specific client is running.
Note: I can't do this through "Computer Groups" or "User" due to internal definitions.
 
I came to think of some system variable that would inform the launch name or some local variable (that each HMI writes only in its variable, without interfering with the global database), but I don't know if any of these options is possible
 
I've done this before using some VBA to record the computer name and act accordingly. It was quite a while ago and I no longer have access to that system, so I can't give you any specifics, but it worked.
 
ASF said:
I've done this before using some VBA to record the computer name and act accordingly. It was quite a while ago and I no longer have access to that system, so I can't give you any specifics, but it worked.
Click to expand...

This I know how to do, but I have another problem at this point: the 4 clients are actually remote connections on a terminal service, that is, it ends up being a single computer
 
faeldebrito said:
How do I have access to sockets?
Click to expand...

That, I don't know, perhaps with help from IT? I'm pretty sure that any remote connection service must be able to distinguish each connection in order to send the correct data, even if they are all requesting the same data from your controller.
 
It has been a while, but check the environment variable CLIENTNAME in the terminal server session. I seem to recall that is the name of the RDP client machine.
 
I solved this problem, with the following VBA code:

Set oShell = CreateObject("WScript.Shell")
sPSCmd = "powershell -command (Get-ItemProperty -path ('HKCU:\Volatile Environment\' + (Get-Process -PID $pid).SessionID ) -name ""CLIENTNAME"").CLIENTNAME"
Set oExec = oShell.Exec(sPSCmd)
oExec.StdIn.Close

fClienteName = oExecutor.StdOut.ReadAll
 

Similar Topics

L
FactoryTalk Assetcentre client fails to launch
Hello I have installed FactoryTalk Assetcentre V7 on windows 10. When I try to launch the client it will whirl for a bit and nothing. When I...
Replies
5
Views
3,908
waxx
W
M
Factorytalk View Studio Machine 5.1 won't launch
Hi guys, I had View studio 6.00 and it was working alright but we were forced to switch for 5.1 because almost all of our panelview are old. So...
Replies
12
Views
5,751
Martindag
M
timryder
FactoryTalk View SE Launch Window Exe
Can anyone think of a way to add a button to an HMI Screen in FTVSE which will launch an windows executable file? I have a customer who has...
Replies
2
Views
2,862
rajy2r
rajy2r
M
how to communicate FactoryTalk Optix and Mitsubishi Q Series
how to communicate FactoryTalk Optix and Mitsubishi Q Series. I want to know the details of that
Replies
0
Views
36
MIIN
M
M
Factorytalk SE IP subnet change
Hoping someone can give me some guidance or confirmation of what I need to do. We have a FactoryTalk SE program that I need to change the IP...
Replies
2
Views
80
Cheeseface
C
Back
Top Bottom