From 7:00 PM CST Friday, January 24th - 7:00 PM CST Sunday, January 26th, will be undergoing system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

TSM Step Templates

NI TestStand 2017 Semiconductor Module Help

Edition Date: July 2018

Part Number: 373892H-01

»View Product Info
Download Help (Windows Only)

Use the set of TSM step types with template code to perform common operations, such as setting up and closing instruments, powering up a DUT, or executing common tests. You can modify the code to customize the behavior of the step within a test program.

TSM provides template code for the following step types:

Adding Step Templates to a Test Program

When you add a step template to a test program, the step prompts you to specify a location for the corresponding predefined VI or .NET assembly the step generates, based on the current module adapter setting. The step executes the corresponding code module from the location you specify.

Note Notes
  • Some of the generated template VIs are not compatible with all the versions of LabVIEW that TSM supports. TSM generates a template VI that is compatible with the version of LabVIEW that has most recently been run on the computer.
  • If you use the LabVIEW Adapter, you must have the LabVIEW Development System installed, and you must configure the LabVIEW Adapter to use the LabVIEW Development System.
  • If you use the .NET Adapter, TSM generates the template code for all the step type templates in a single .NET assembly when you add any of the step type templates to the test program.

Configuring the Step

The template code module for each step type uses default values for most input parameters. You must configure settings, such as limits and the pin(s) to use for the operation, for any tests associated with the step.

Step types that perform tests are based on the Semiconductor Multi Test step type. Step types that do not perform tests are based on the Semiconductor Action step type.

Modifying the Code Templates

Modifying the code module template for a step type affects the code module TSM generates when you add a new instance of the step type to any test program on the computer.

To modify a LabVIEW code module template, copy the VI from one of the directories in the <TestStand>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW directory to the <TestStand Public>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW directory and make changes to the VI in that location. If you want to use subVIs in the LabVIEW code module template, store the subVIs in a SubVIs folder and use the name of the template as a prefix followed by an underscore for the subVI filename.

For example, to modify the Continuity Test LabVIEW template, copy the <TestStand>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW\LabVIEW 2018 and later\Template_Continuity to the <TestStand Public>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW directory and copy all the subVIs with the prefix Continuity Test_ from the <TestStand>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW\SubVIs directory to the <TestStand Public>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW\SubVIs directory.

To create LabVIEW template VIs to use in specific versions of LabVIEW, copy the customized VIs to directories that correspond to the year-based version of LabVIEW you want to use. For example, to use the Continuity Test LabVIEW template only when LabVIEW 2018 is active, copy it to a <TestStand Public>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\LabVIEW\2018 directory.

To modify a .NET code module template, copy the <TestStand>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\DotNet directory to the <TestStand Public>\Components\Modules\NI_SemiconductorModule\StepTypeTemplates\DotNet directory, make changes to the .NET source in this location, and rebuild the .NET assembly to update the template. After you rebuild the .NET assembly, rename it to use the Template_ prefix so the step types detect it properly.


Not Helpful