11-10-2008 01:08 AM
11-10-2008 02:06 PM
Hi Zofe,
By a specific time do you mean according to the system clock (I.E. 3:00 PM) or a certain amount of time between steps?
11-10-2008 02:44 PM
Hi CorbinH
I mean a specific time according to the system clock.
Maayan
11-10-2008 03:28 PM
I can think of a couple different options for you:
1) Create a code module (LabVIEW VI, etc) where you implement a Wait function in the code and call that code module as the first step in your sequence.
2) Use the Wait step under the Synchronization folder. You can access the system clock in a pre-expression with the function Time(). You could somehow use some ingenuity and math to find the number of seconds between the current time and the time you want your test to run and set that variable as amount of time to wait within the Wait Settings.
Now the problem with both of these options are that your UI will hang while TestStand waits for the "wait" step to end. Would either of these options be what you are looking for? If not, could you explain what you are wanting to do in a little more detail? Thanks.
11-10-2008 06:17 PM
Zofe,
Another way I can think of is to use the Windows Scheduled Tasks item. To open Scheduled Tasks, click Start, point to Programs, point to Accessories, point to System Tools, and then click Scheduled Tasks.
In this dialog, you can choose any program to run at any time you specify. What you can then do is use TestStand command line arguments with your UI or the sequence editor to run the sequence you would like to run.
12-04-2008 12:32 AM
Hi Josh,
I tried your last idea, to schedule a task and to use the TestStand's command line argument (TestExec.exe <sequence>...)
The main problem that I encounterd is the "log in" window (password) TestStand present to me, each time it's running.. In addition to that I'm working with a main sequence of my own that prompt the output to other GUI. This GUI is condition the start of the main part of the test by pressing on a "start" bottom. Is there any way to overcome the "log in" problem from the command line arguments and is there any "macro" at TestStand (I didn't find any) to overcome pressing start at the GUI.
Thanks
12-04-2008 02:16 PM
You have a couple options available to you.
1) In the sequence editor, select Configure » Station Options and then the User Manager tab. The last checkbox is Automatically Login Windows System User. Selecting this will automatically login to TestStand with the username of the windows user. The next modification needed would be renaming the user in the User Manager to the windows login (i.e. Administrator to yourname).
2) Another option would be to alter the frontend callback. This would be quite a bit more challenging since it would require opening the login DLL and customizing it.