TestStand 2019 Semiconductor Module Known Issues By Date

Aperçu

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:

  • Issue ID - the number at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
  • Legacy ID (optional) -  If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
  • Issue Title: in italics - it describes the issue in one sentence or less
  • Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
  • Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
  • Reported Version - the earliest version of TestStand Semiconductor Module the issue was reported in. If you discover the issue appears in an earlier version of TestStand Semiconductor Module than is reported in this field, you can report that to NI (contact information below) to have the field updated.
  • Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
  • Date Added - the date the issue was added to the document (not necessarily the reported date)

Document Organization:

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.

Contacting NI

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.

Known Issues by Date

The following items are known issues in TestStand Semiconductor Module 2019 sorted by Date.

686176 TSM configuration for TestStand Sequence Editor does not provide option to continue when paused at breakpoint
694826 TestStand Offline Results Processing Utility hangs while processing reports generated with TSM report plug-ins enabled
711014 Close References VI Analyzer test might return incorrect results when you use Case structures or For loops
719692 Semiconductor Multi Test step evaluates to Done when executed without limits or limits file
736291 Accelerometer .NET Example Build Error
741443 You cannot build a deployment of test programs with template steps that use the High Resolution Polling Wait VI in LV 2018 and later
741749 NI-DAQmx .NET TSM Code Module API methods cause run-time errors in 64-bit TestStand
742370 Running a performance measurement with an open instance of the Test Program Performance Analyzer returns an exception
745615 Accelerometer DotNet example requires Visual Studio 2017 or later to compile



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.

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
694826

Return
TestStand Offline Results Processing Utility hangs while processing reports generated with TSM report plug-ins enabled
The utility returns an error and hangs when you add reports that TSM report processors, such as the Lot Summary Report plug-in, generate.

Workaround: N/A

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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.

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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.

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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

Reported Version: 2019    Resolved Version: N/A    Added: 08/13/2019
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.

Reported Version: 2017    Resolved Version: N/A    Added: 08/13/2019
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

Reported Version: 2019    Resolved Version: N/A    Added: 08/13/2019

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).