NI TestStand
Custom UI - Multi Socket， Batch Mode Setting 4 Sockets， but want to just start some of them
Solved!
If you have 4 test sockets defined in the model. You will need to disable the two you don't use before starting a new run.
In the batch process model, you should look at "Locals.ModelData.TestSockets[0].Disabled"
Usually, you define the maximum number of sockets you are capable of doing. This will define the number of "TestSockets" in ModelData. Afterward, you start your process model running and your client file.
There's a Callback called "PreBatch" you can use to change the number of sockets enabled. You can see this example clearly if you run any sequence using the batch process model. From there, I'm sure you can easily create a boolean or any LabVIEW call to update this variable during this callback.
I don't know your situation well enough to make that determination. You will need to make that determination.
If you system can support 4 DUTs at once, then yes it makes sense to set max sockets to 4. if it's only 2, then I would set your max to that and not worry about disabling certian sockets. If it's 8, set to 8, etc.
Ii'd also ask how likely will you get into a situation where, assuming you have 4 DUT capacity, you would be only testing 2. Would they always be DUT 1 and DUT 2, or would it be effectively random? These are engineering questions outside understanding how TestStand works.
Well, I'd definitately do a batch or parallel process model. If the need is that they have to start at the same time, then batch. If any could be started at any time, then I'd consider parallel.
If batch, I'd modify the PreBatch Callback to loop check each socket using the presence detection. If detected, check serial number. If number is valid, enable socket for testing. While this is looping, I'd have a UI that displays the status of each socket (depending on coding, it could all be in the display UI). I'd also continuiously check an active socket's serial number just in case the Operator pulled the UUT out before ready to test. (Disable socket if serial number can't be determined) Once the person closes the UI, it returns the array/cluster of valid sockets to the PreBatch Callback who will in turn update the ModelData Parameter.
