02-02-2014 11:59 PM
You can use UI Messages to send information from the GUI to the sequence file and vice versa: http://www.ni.com/white-paper/4532/en/
You can just use the Parallel model. It will need to be a combination of using UI Messages as well as editing the Process model to handle "empty" or "unchecked" UUTs.
I'm very busy lately or I'd throw together an example for you. Here is the gist of it:
Inside of the Initialize TestSocket sequence send a UI Message to the UI with the sequence context. Then from the UI Message callback VI in the UI set which sockets you want to start from what the user selected. Then back in the process model use those flags to start or not start the proper sockets. Hopefully this helps get you on the right track.
I haven't looked much at the new models so if you are using 2012 or newer then I'm not sure if Initialize TestSocket is the right place. Basically, wherever the executions get spawned.
Regards,
07-15-2019 08:20 AM
Hi Jigg,
Could you share example to me?
I am doing same things as NewSCRuser. I do not want the default pop up dialog box from Test UUT - Parallel Model. I am looking way to disable/override the pop up dialog box (as attach).
Then test socket shall be select from my custom Operator/User Interface and trigger start test by a button.
Seek for your advice.
Thank you.
07-15-2019 01:34 PM
It would be a lot to put together an example for this.
Ultimately there are 2 things you need to understand. How UI Messages work and how to override the callback that displays that dialog.
This thread points to examples on how to override the callback? https://forums.ni.com/t5/NI-TestStand/Creating-a-custom-UUT-dialog-for-the-parallel-model/td-p/47521...
Here is some info on UI messages:
http://www.ni.com/tutorial/4532/en/