NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Very simple OI

 I have a sequence which operates in one of two modes, depending on the value of a fileglobal.

For the production line where this is running, I want to create an ultra simple interface consisting of three buttons: "Burn-in", "Vibration" and "Terminate All".
A click on either of the first two would load the sequence file, update the variable value (depending on which button was pressed) and execute the sequence. The third button would terminate the running sequence in case it got stuck. I've been looking at the OI examples and can load the sequence (TSUI_ApplicationMgrOpenSequenceFile), but I haven't found what else I need. Can someone please point me to the function calls I need? I an coding in CVI 8 and running a TestStand 4.0 sequence.

I think I need
  - How to run the sequence with the "Test UUTs" entry point of the batch process model.
  - Update the fileglobal, or pass a value to the sequence (command line argument?)

Thanks for any help
Don
0 Kudos
Message 1 of 3
(3,401 Views)
Hi Don,
 
I would be glad to help you with this question, but I may have to do a bit of research first in order to come up with a solution that matches exactly what you are trying to do. This sounds like a very interesting application, and I am sure that we can work together to get everything up and running. Have a great day Don; you will be hearing back from me shortly.
 
Regards,
 
Casey Weltzin
Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(3,375 Views)
Hi Don,
 
What you are trying to accomplish is definitely possible, and can be accomplished in a variety of ways. I have the following recommendations:
 
1) Your sequence file should ideally be written in a way that it can run from any operator interface (not just your custom interface). Though it is possible for you to set global variables from your operator interface, I would actually recommend avoiding this so that your operator interface and sequence file are less interdependent.
 
2) The shipping example code for the CVI TestStand operator interface should help to get you started with developing your custom interface. This example can be located at (C:\Program Files\National Instruments\TestStand 4.0\UserInterfaces\NI\Simple\CVI). In specific, the example shows exactly how to implement a run button that executes your sequence with a certain entry point, and how to implement a terminate button as well.
 
3) To set a variable in order to run your sequence in "burn in" or "vibration" mode, I would recommend either using a TestStand popup window, or calling a CVI dialog from TestStand. The main idea here is that setting variables in order to control execution makes more sense during run-time, and can happen independent of the operator interface being used.
 
I hope this helps. Please let me know if I can clarify anything above and I would be glad to help you further. Have a great day Don!
 
Regards,
 
Casey Weltzin
Applications Engineer
National Instruments
0 Kudos
Message 3 of 3
(3,338 Views)