TestStand Example 3: Thermal Chamber Controller Example With Multiple DUTs.seq
This example sequence is an advanced example calling into the Public API of multiple DQMH modules from TestStand. This example starts a Thermal Chamber Controller DQMH module (singleton) and multiple instances of the Device Under Test DQMH Module (cloneable) in addition to a TestStand Manager DQMH Module (singleton). The TestStand Manager acts as a relay, monitoring the execution status of the TestStand sequence and calling the Stop Module.vi of the other modules should the sequence be terminated or aborted. This prevents the likelihood of being left with orphaned running DQMH modules.
We utilize batch synchronization in TestStand to ensure that only a single thread will execute code associated with Thermal Chamber Controller operations. However, all threads will communicate and interact with a unique instance of the Device Under Test module. For more information on Batch Synchronization and Thread Scheduling please refer to the TestStand 1: Test Development course provided by NI.
|This sequence programmatically sets TestStand to execute using the BatchModel.seq process model file to better demonstrate the use of cloneable DQMH modules.|
See LabVIEW Example 3: Thermal Chamber Controller with Multiple DUTs.vi for a similar example in LabVIEW.
To get the example: