From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Thanks for pointing that out - i misinterpreted this the first time i read through it.
There are a few workarounds that i think are easy enough. One i haven't seen mentioned here or the other thread is calling the step in a sub sequence with looping configured on the sequence call. You could pretty easily change the limits based off pass/fail.
Similar concepts have been solved in TSM, and could also be solved in a custom plugin:
It would be very good if teststand would offer the native testing against multiple limits. Let say the test will pass if the measurement is less than 5 and it pass under concesion when is less than 7, otherwise its fail.
So, summarising TS shall have the ability to delinie not only one set of limits per measurement along with the different kinds of passes.
@WireWeaver, This idea should probably be listed as declined or new rather than completed.
The request is not to have a more complex expression for determining pass/fail but to have a third state in addition to Pass/Fail (Pass with Concession) where it still passes the overall limits, but fails a set of stricter warning or engineering limits. The example given requires the measurement to be <5 for an unqualified "Pass", >=7 for an unqualified "Fail", and between 5 and 7 for a qualified "Pass with Concession". See the thread the OP linked to for more details (and some ways to make it work with TestStand's current result system).
Thanks for pointing that out - i misinterpreted this the first time i read through it.
There are a few workarounds that i think are easy enough. One i haven't seen mentioned here or the other thread is calling the step in a sub sequence with looping configured on the sequence call. You could pretty easily change the limits based off pass/fail.
Similar concepts have been solved in TSM, and could also be solved in a custom plugin:
,
Thanks for pointing that out - i misinterpreted this the first time i read through it.
There are a few workarounds that i think are easy enough. One i haven't seen mentioned here or the other thread is calling the step in a sub sequence with looping configured on the sequence call. You could pretty easily change the limits based off pass/fail.
Similar concepts have been solved in TSM, and could also be solved in a custom plugin:
Grading/Binning: http://zone.ni.com/reference/en-XX/help/373892H-01/tssemiconductor/binning/
PAT: http://zone.ni.com/reference/en-XX/help/373892H-01/tssemiconductor/partaveragetesting/