This document contains the TestStand Semiconductor Module known issues
that were discovered before and since the release of
NI TestStand 2016 SP1 Semiconductor Module. Not every issue known to NI will appear on this
list; it is intended to only show the severe and more common issues
that can be encountered.
Each Issue appears as a row in the table and
includes these fields:
The following document displays the issues by the date the issue was added to the document (not necessarily the date the issue was reported to NI). This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face with NI TestStand 2016 SP1 Semiconductor Module during development.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in TestStand 2016 Semiconductor Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 396711 Return | Second error dialog box appears after run-time error occurs when incorrectly using the Set and Lock Bin step When you use a Set and Lock Bin step in a sequence file and run Single Pass using the Batch model, a run-time error occurs because the step sets the bin to 0 by default. If you do not specify a bin definitions file, bin 0 is a fail bin. When the sequence passes and tries to determine the final bin, it reports a run-time error because the sequence passed but the bin was set to a fail bin. After that run-time error is reported, a second run-time error occurs and indicates that "One or more test sockets have unexpectedly stopped executing". Workaround: Ignore the second error dialog box and configure a bin definitions file.
| |||||
| 457832 Return | TestStand Semiconductor Module Operator Interface Test Program Information control does not clear values when switching from a sequence with a configuration to one without In the TestStand Semiconductor Module Operator Interface, the Test Program Information control updates values to match the test conditions of the current configuration and the station settings. However, if you switch from a sequence file that has a configuration, and thus populated the control with values, to a sequence file that does not have a configuration and has no values to populate it with, the Test Program Information control does not clear itself and continues to show the old values. Workaround: If it is required to execute sequence files without test configurations, modify the operator interface code to handle this use case.
| |||||
| 505457 Return | The Number of Sites control in the Configure Station Settings dialog box does not affect the number of sites when executing with the Sequential model When executing with the TestStand Sequential model, only one site is allowed. However, the Configure Station Settings dialog box displays the number of sites that would run if the Parallel or Batch model were used. Workaround: N/A
| |||||
| 515495 Return | The Create Multisite Digital Waveforms VI takes a long time to execute with large waveforms The execution time of the Create Multisite Digital Waveforms VI increases exponentially with the size of the input waveform. Workaround: The performance of this VI has been improved in the TestStand 2014 Semiconductor Module such that the execution time no longer increases exponentially with the size of the input waveform. The VI executes normally with large waveforms.
| |||||
| 517287 Return | TestStand Seminconductor Module .NET APIs do not appear in the Visual Studio Add References dialog box when 64-bit TestStand is installed but 64-bit TestStand Semiconductor Module is not If 32-bit and 64-bit TestStand are installed but only 32-bit TestStand Semiconductor Module is installed, the TestStand Seminconductor Module .NET Code Module API and Application API do not appear in the Add References dialog box in Visual Studio. Workaround: Install 64-bit TestStand Semiconductor Module or add the reference to the Visual Studio project manually by browsing to <TestStand>\API\DotNET\Assemblies\CurrentVersion.
| |||||
| 528021 Return | TestStand Semiconductor Module result processors do not appear in the Result Processing dialog box If the Result Processing dialog box has been opened at least once before the TestStand Semiconductor Module is installed, the installer is unable to update the items in the Result Processing dialog box. Workaround: Follow the instructions in the "Enabling and Configuring Semiconductor Module Result Processing Plug-ins" topic in the TestStand Semiconductor Module Help to update the Result Processing dialog box.
| |||||
| 529670 Return | The license activation dialog box in the installer for a TestStand deployment that contains the TestStand Semiconductor Module Runtime incorrectly labels the serial number field as "TestStand" instead of "TestStand Semiconductor Module" A TestStand Semiconductor Module serial number will activate the product. If TestStand 2014 SP1 or later is installed, the dialog box displays the correct label. Workaround: N/A
| |||||
| 555661 Return | Building the TestStand 2014 Semiconductor Module LabVIEW operator interface executable after installing TestStand 2014 Semiconductor Module SP1 might result in build errors When you build an existing TestStand 2014 Semiconductor Module LabVIEW operator interface executable after you install TestStand 2014 Semiconductor Module SP1, the build operation might fail with a build error with text similar to the following: Click the link below to visit the Application Builder support page. Use the following information as a reference: Error 1 occurred at EndUpdateResourceA.vi. Workaround: Mass compile the LabVIEW operator interface project before building.
| |||||
| 558650 Return | Cancelling installation of TestStand 2014 Semiconductor Module SP1 might leave TestStand 2014 Semiconductor Module in a bad state The TestStand 2014 Semiconductor Module SP1 installer first un-registers some files from the TestStand 2014 Semiconductor Module but is unable to re-register the files if the installer cancels before completing. Workaround: Run the TestStand Version Selector and make TestStand 2014 active to re-register the files.
| |||||
| 562103 Return | TestStand might launch a license activation dialog box after you install TestStand Semiconductor Module for one bitness and start TestStand for the other bitness before activating the TestStand Semiconductor Module If you have 32-bit and 64-bit TestStand installed and you install TestStand Semiconductor Module for either 32-bit or 64-bit, then start TestStand with the bitness for which you did not install TestStand Semiconductor Module, a license activation dialog box launches with a blank entry for the product that needs to be activated. The dialog box no longer displays after you activate the TestStand Semiconductor Module license. Workaround: Activate the license for the TestStand Semiconductor Module or install the TestStand Semiconductor Module for both bitness versions of TestStand.
| |||||
| 563547 Return | In rare cases, certain steps that use the LabVIEW Adapter and default values might report run-time errors when using a test program configuration that loads limits Certain rare combinations of default values for array parameters on LabVIEW steps can cause a run-time error when running a test program with a configuration that loads limits from a test limits file. Workaround: On the step that reports a run-time error, change the step load option to Load Dynamically and the unload option to Unload after the step executes.
| |||||
| 597659 Return | Using CPU Affinity step might cause some threads to suspend intermittently for several seconds When you configure the CPU Affinity step to use fewer cores than are available in processors with eight or more cores, some threads might intermittently suspend. Workaround: N/A
| |||||
| 612228 Return | Launching the Digital Pattern Editor from the TestStand Semiconductor Module does not always bring the existing editor to the front When an instance of the Digital Pattern Editor is running, attempting to launch the Digital Pattern Editor from the TestStand Semiconductor Module does not always bring the existing editor to the front. If the Digital Pattern Editor was originally launched from the Start menu, the TestStand Semiconductor Module instead launches a new instance of the Digital Pattern Editor. Workaround: Manually navigate to an existing instance of the Digital Pattern Editor instead of using the TestStand Semiconductor Module shortcut to bring the existing instance of the editor to the front.
| |||||
| 612417 Return | TestStand Semiconductor Module (TSM) types do not set the earliest TestStand version that can use the type, which can propagate newer TSM types to older versions of TSM When you save a TSM 2016 sequence file to a previous version, such as TestStand 2014, and then open the sequence file with TSM 2014, TSM 2016 types appear in the TSM 2014 version of the sequence file, and the TSM 2014 sequence files are marked as modified because of the newer type version. Workaround: N/A
| |||||
| 645338 Return | Error when closing sequence editor An infrequent Fatal Error message occurs when you close the TestStand Sequence Editor when the Test Program Editor is displayed. This has no effect on files that were loaded at the time. Workaround: N/A
| |||||
| 647125 Return | TSM bins the part correctly but reports incorrect measurement data when a step errors out If a Semiconductor Multi Test step produces an error on a run other than the first in a lot, TSM logs the measurements of the step from the previous batch. TSM bins the DUT correctly, and the step returns an error. Workaround: Disable the Optimize Non-Reentrant Calls to this Sequence option on all sequences that return report data in the sequence file.
| |||||
| 648900 Return | Run-time error occurs in test programs not using PAT if PAT algorithm settings include bin numbers that are not in the bin definitions file A run-time error can occur if you include bin numbers in a PAT algorithm settings and do not include those bin numbers in the bin definitions file, even if the test program does not use a PAT algorithm. This only occurs if the setting has the DisplaySoftwareBinComboBox attribute set to True. Workaround: Set DisplaySoftwareBinComboBox to False for the bin number attribute and type the bin number instead of selecting it from the combo box.
| |||||
| 651595 Return | Memory usage can increase when using reentrant VIs and testing a high number of sites Testing with many sites that call reentrant VIs can cause increased memory use because TestStand creates a clone of a reentrant VI in each thread where the VI executes. Duplicate clones can be created because the thread used depends on the order at which the sites arrive at the step. The order can vary when you test with many sites. Workaround: N/A
| |||||
| 669922 Return | Run-time errors occur when looping on TSM steps Intermittent errors can occur if you use TSM steps in a loop or enable looping settings in certain multisite situations. Workaround: Avoid using loops with TSM step types or ensure that the last step in a loop block is a Semiconductor Multi Test step with the Multisite Option set to One thread only.
| |||||
| 700536 Return | Importing a large number of test limits takes a long time to complete It takes a long time to import limits files that contain on the order of tens of thousands of limits. The user interface is unresponsive during loading but returns to normal after the load action completes. Workaround: Use the "Replace all tests in matching steps" option when importing for a shorter load time.
|