‎08-22-2017 05:18 AM - edited ‎08-22-2017 05:18 AM
ehh 😞 this is bad.. ;/ i check your link but nothing usefull is there, but thank you anyway
‎08-22-2017 06:22 AM
I don't think that it is possible make a auto login into TestStand from an external program using the default TestStand login methods.
If you want something like that, the best way is to make your own login method using the FrontEnd call back option in TestStand.
This does not change the execution of the sequence in TestStand, just the handle of how login is done.
You could make a FrontEnd Call back that just automatic logged you as Admin or any other TestStand user.
‎08-22-2017 08:03 AM
Can you give me example of automatic login?
‎08-22-2017
08:45 AM
- last edited on
‎11-01-2024
03:15 PM
by
Content Cleaner
Look up FrontEnd Callback for TestStand to get information about how the Login is handled.
And a quick google gave me this:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YINaCAO&l=en-US
‎08-22-2017 08:51 AM
This give me nothing, I need to do this in LabVIEW and i can't change anything in TestStand or in application I have
‎08-22-2017 09:05 AM
Honestly, you are looking for something which you might not get.
You want to automate test execution which is exposing UI elements (e.g. blocking popup dialogs) which HAVE to be controlled by a user. At least this is what i understand from your description from the task you provided up till now.
From this point, you have two options:
a) Automate UI interaction using one of these tools
b) Modify the test code as such that these UI elements do not need user interaction
Please note that b) is not possible as long as you are not ready to make the appropiate/necessary modifications.
As a final note
You can 'easily' create an appropriate framework including custom UI, modified process model, etc. to meet your requirements. However, you have to do this yourself (or let someone else do it for you. You will, however, most likely have to pay that *someone*) and you have to get enough knowledge/experience in case you want to do it on your own.
‎08-23-2017 01:11 AM
Thank you for your reply, that is what I though this can be done, but maybe I can somehow login to Test Stand from LabVIEW without changing any code in test stand? On the bottom panel in test stand is logged user maybe you can tell me from what test stand get it?
‎08-23-2017 01:52 AM - edited ‎08-23-2017 01:54 AM
Using the standard TestStand login screen, you require option a) to control it automatically. There is no interface to "remote control" that dialog. Period. No further discussion.
What you can do is to replace that dialog (in the FrontEndCallback.seq) with a dialog which you can easily control remotely. That would be option b) and requires you to change some parts of the target system.
@Kamil5554 wrote:
[...] On the bottom panel in test stand is logged user maybe you can tell me from what test stand get it?
What are you referring to?
When you use the full featured UI (or SequenceEditor), there is a "status bar". If a user is logged into TS, it will display that user name. Your challenge is that when the login dialog shows up initially, no user is logged in. That is also your problem why the "CurrentUser" reference is NULL. No logged in user => no user referrence.
‎08-23-2017 04:02 AM
With this reference to CurrentUser, after i log in my reference is still NULL. even I see in TestStand that I am logged. Maybe I do it wrong , but I think I should change the CurrentUser.
Last question in StationGlobals -> TS I have two options "CurrentUser" and "LastUserName" :
but when I want connect to StationGlobals.TS.CurrentUser, LabVIEW tells me there is no such thing like "CurrentUser", but when I i receive value from "LastUserName" there is no error and I get value, you know why ?
‎08-23-2017 04:13 AM
I don't know what you are meddling here with. Most likely, you mess up the manager controls which will then of course do not interact with what you think it does, but with a separated, local instance.
The default configuration of TS including all framework components (UI, process model interaction, configuration dialogs, ...) are NOT designed for remot control. In case you want to completely remote control these items, you have to prepare them for it. Read: You have to modify/add code in the TS station to get your remote control option. The option a) i was stating (automated remote UI control) is only a workaround.