This document contains the TestStand 2014 Semiconductor Module SP1 known issues that were discovered before and since the release of TestStand 2014 Semiconductor Module SP1. 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 known issue includes these fields:
The following items are known issues in TestStand 2014 Semiconductor Module SP1 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, then 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.
| |||||
| 482476 Return | TestStand reports unclosed object references when exiting the LabVIEW operator interface when running from the LabVIEW development environment The unclosed references do not cause an error when running the LabVIEW operator interface as an executable. Workaround: N/A
| |||||
| 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 WaveformsVI 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.
| |||||
| 526084 Return | Uninstalling one bitness of TestStand Semiconductor Module removes the license for the remaining bitness If the 32-bit and 64-bit TestStand Semiconductor Module are installed and you uninstall one of the two versions, the NI License Manager no longer recognizes the remaining TestStand Semiconductor Module version. Workaround: Repair the installation of the remaining version.
| |||||
| 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 documented in the "Enabling and Configuring Semiconductor Module Result Processing Plug-ins" help topic.
| |||||
| 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
| |||||
| 529409 Return | Configure Station Settings and Configure Lot Settings dialog boxes might become unresponsive when you run the operator interface in LabVIEW Development Environment When you run the Semiconductor Module operator interface in the LabVIEW development system, the Configure Station Settings and the Configure Lot Settings dialog boxes might become unresponsive if you had run and exited the operator interface at least one time. 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.
| |||||
| 557654 Return | Importing limits from a test limits file that changes the evaluation type of a test might not correctly set the flags on the test properties If you import test limits into a sequence file with the Update limits in matching tests option enabled and the import operation changes the Evaluation Type of an existing test, certain flags on the test properties are set incorrectly. These flags do not affect execution of the test program because the Semiconductor Multi Test step corrects the settings at run time. The specific flag involved is the Dont Copy To Results flag on the NumericLimit or PassFail properties.Workaround: N/A
| |||||
| 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 the TestStand 2014 active to re-register the files.
| |||||
| 561325 Return | TestStand might report that references to PropertyObjects were not released properly when you exit the LabVIEW operator interface while running in LabVIEW Development Environment If you run the TestStand Semiconductor Module LabVIEW operator interface in the LabVIEW Development Environment, when you exit the operator interface, TestStand might launch a dialog box warning that nine top-level references to PropertyObjects were not released properly. This warning occurs only when at least one of the Semiconductor Module result processors is enabled and only when running within the LabVIEW development environment. You can safely ignore this warning message. Workaround: You can safely ignore this warning message.
| |||||
| 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 will stop showing once the TestStand Semiconductor Module's license is activated. Workaround: Activate the license for the TestStand Semiconductor Module or Install 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.
| |||||
| 564895 Return | Default operator interfaces do not disable tracing, which can negatively affect performance The default operator interfaces do not disable tracing for executions. Tracing can be useful when executing in the sequence editor but provides no benefit when executing in an operator interface. Tracing can negatively affect performance. Workaround: Refer to the Disable Tracing in TestStand topic in the TestStand Semiconductor Module Help to disable tracing in the station options.
| |||||
| 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.
| |||||
| 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.
|