How to disable default login action at Application_Manager-Start and replace with default User.

[Gary_H]

I would like to disable the default action of the Login dialogue box when the Labiew Simple Operator Interface (TestExec.exe)

is run.

The reason is so that I can implement a custom PreUUT callback which includes a login process.

So far I have managed to disable the ApplicationMgr - LoginOnStart property, which prevents the Login dialogue box appearing.

But I find that I still need to login to procede, i.e. the Simple Operator Interface displays but unable to load a sequence or continue execution of a Windows shortcut target string which includes the loading and running of a sequence.

Is it possible to programmatically login a "Default User" which prevents the login "hold up" ?

I would expect to have to create a "Default User" in the User Manager to be part of the process, but I am unsure what the Application Manager requires to satisfy it's login process.

regards,

Gary.

[JonBowers]

Hi Gary,

You can programatically log a user in by calling the GetUser method and Seting the CurrentUser property of the Teststand Engine respectively. I have created an example sequece which calls these methods. You could change the frontEndCallbacks sequence file so it automatically logs on a user, though I would suggest you make a backup of it before you alter it.

Regards

Jon B
Applications Engineer
NIUK

[SercoSteve]

Hi Gary

You can also get TS to automatically logon to the Windows System User.  This is selected in the Menu Configure->Station Options.. Execution Tab.

For this to work properly you need to add a TS User whos LoginName matches the Windows System Login name. 

When working the FrontEndCallback sequence will not display the login dialog box and the privileges for the user will be as specified for you created user.

This is good for systems where you have a limited number of logins.

Regards

Steve

[James_Grey]

For completeness, I should mention that you can set the value of Engine.StationOptions.EnableUserPrivilegeChecking to False.

[Gary_H]

Jon,
I finally got round to implementing your solution......thank you, it works fine.

However there is something in the solution which I do not understand.

Allow me to explain:
I created the new FrontEndCallbacks.seq, as you described, then I ran the Simple Labview Operator Interface (7.1).
The Operator Interface was displayed but with most of the controls greyed out, except for a couple, in particular the "Login" control.
When this was pressed, the other controls were made available.

My question is:
Why didn't the new FrontEndCalback sequence automatically login the default user ?
As I understand it, within the Simple Labview Operator Interface block diagram,
when the invoke node:IApplicationMgr--Start is executed, it calls the FrontEndCallback sequence.
But this did not appear to be the case, hence the need to press the Login control.
When the Login control was operated, the new FrontEndCallback sequence executed correctly - no Login dialogue box displayed and a default user logged in.

To overcome the need to press Login, I added the property node:
IApplicationMgr--LoginOnStart (true)
just before IApplicationMgr--Start.

With all that said and done, I now have the ability to create and execute
this customised desktop short cut target string:
<operator interface.exe> /runEntryPoint "Test UUTs" <client sequence.seq>
without the need to display the Teststand Login dialogue box.

thanks,

Gary.