This document contains the TestStand Semiconductor Module known issues
that were discovered before and since the release of
NI TestStand 2019 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 2017 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. Visit the NI Website to contact us. 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 Semiconductor Module 2019 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 686176 Return | TSM configuration for TestStand Sequence Editor does not provide option to continue when paused at breakpoint When you use the TestStand Semiconductor Module configuration for the TestStand Sequence Editor, execute a sequence from an entry point that is not a TSM entry point, and pause execution at a breakpoint, no visible Continue option exists to resume execution. Workaround: Right-click the execution caption and select Continue from the context menu.
| |||||
| 711014 Return | Close References VI Analyzer test might return incorrect results when you use Case structures or For loops When you close a reference inside a Case structure or a For loop, the VI Analyzer test that reports open references might report or fail to report a warning. Workaround: N/A
| |||||
| 719692 Return | Semiconductor Multi Test step evaluates to Done when executed without limits or limits file If you use the the Tests tab of the Semiconductor Multi Test step to set a software bin but no limits and you do not overwrite the limits with a limits file, the step evaluates to Done instead of Pass/Fail, which can cause false positive results if no other step fails. Workaround: Include limits or a limits file.
| |||||
| 736291 Return | Accelerometer .NET Example Build Error The .NET Accelerator example might return a build error stating that Ivi.Swtch and Ivi.Scope are not referenced in the project. Workaround: Add these dependencies to the project and rebuild.
| |||||
| 741443 Return | You cannot build a deployment of test programs with template steps that use the High Resolution Polling Wait VI in LV 2018 and later Because of a dependency issue, you cannot build deployments of VIs that use the High Resolution Polling Wait VI. As a result, you cannot build deployments of test programs that use the VI in template steps if you are using LabVIEW 2018 or later. Workaround: N/A
| |||||
| 741749 Return | NI-DAQmx .NET TSM Code Module API methods cause run-time errors in 64-bit TestStand NI-DAQmx versions 19.0 and 19.1 do not install policy files for 64-bit assemblies. Attempting to use the NI-DAQmx .NET TSM Code Codule API methods results in run-time errors. Workaround: N/A
| |||||
| 742370 Return | Running a performance measurement with an open instance of the Test Program Performance Analyzer returns an exception In 32-bit TSM, running a performance measurement while an instance of the Test Program Performance Analyzer is already running returns the following exception: System.ComponentModel.Win32Exception (0x80004005): A 32 bit processes cannot access modules of a 64 bit process.Workaround: Close the Test Program Performance Analyzer before running a performance measurement in 32-bit TSM.
| |||||
| 745615 Return | The Accelerometer .Net example uses C# 7 features that are not available in Visual Studio 2015 and prior, trying to compile in an older version will throw many syntax errors including CS1003 Syntax Error. Workaround: Compile the example using Visual Studio 2017 or newer
|