TestStand Semiconductor Module 2020 Known Issues
Overview
This document contains the TestStand Semiconductor Module known issues that were discovered before and since the release of TestStand Semiconductor Module 2020. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 566444 | 612417 |
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 TSMWhen 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: There is currently no known workaround for this issue.
|
Reported Version: TestStand Semiconductor Module 2014 Resolved Version: TestStand Semiconductor Module 2017 Added: May 21, 2017 |
| 228151 | 702568 |
Unable to Load NI-Digital Pattern Driver 17.x Assemblies from Existing Applications, Including TSM Examples.NET code modules that use NI-Digital Pattern Driver 17.x must directly target that assembly version. .NET code modules written for a previous version of NI-Digital Pattern Driver, such as 16.0, will not load the 17.x version of the NI-Digital Pattern Driver without rebuilding. Some TSM examples with .NET components target the NI-Digital .NET 16.0 driver. To run these examples, you must change the .csproj file to reference the newer version of the NI-Digital Pattern Driver and recompile the code.
Workaround: Upgrade to NI-Digital Pattern Driver 18.0.
|
Reported Version: TestStand Semiconductor Module 2016 SP1 Resolved Version: TestStand Semiconductor Module 2020 Added: Jul 26, 2018 |
| 228155 | 742370 |
Running a performance measurement with an open instance of the Test Program Performance Analyzer returns an exceptionIn 32-bit TSM on a 64-bit OS, 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: TestStand Semiconductor Module 2017 Resolved Version: TestStand Semiconductor Module Unknown Added: Aug 12, 2019 |
| 228178 |
Compiling Accelerometer with .NET Example Throws Syntax ErrorsThe Accelerometer with .NET example uses C# 7.0 features that are only available in Visual Studio 2017 and later. Compiling the example in an older version of Visual Studio causes syntax errors, including the CS1003 Syntax Error. Workaround: Compile the Accelerometer with .NET using Visual Studio 2017 or later.
|
Reported Version: TestStand Semiconductor Module 2019 Resolved Version: N/A Added: Sep 7, 2021 |
|
| 1039919 |
Objects Not Released Properly When Measuring Test Program PerformanceThe warning shown below may appear after measuring the performance of a test program when the following conditions are met:• The test program contains LabVIEW code modules. • The test program was run prior to selecting Semiconductor Module»Measure Performance of <filename>. • Allow execution with LabVIEW Development Environment adapter is enabled under the Advanced menu of the Test Program Performance Measurement Configuration dialog box. The TestStand Debug Options Warning contains the following text: "The Station Option, Report Object Leaks and Reported Known OS and Component Problems, reported the following warnings on shutdown: References to PropoertyObjects were not released properly."  Workaround: There is currently no known workaround for this issue. |
Reported Version: N/A Resolved Version: TestStand Semiconductor Module 2020 Added: Sep 7, 2021 |
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1148498 |
Broken Reference to NationalInstruments.Common from TSM .NET Examples When Using STS Bundle 19.5 and NI-DCPower 20.6After installing STS Software Bundle 19.5 and NI-DCPower 20.6, compiling a TestStand Semiconductor Module .NET example produces an error. For example, the Accelerometer example produced the following error: 1>------ Build started: Project: AccelerometerExample, Configuration: Debug Any CPU ------ 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3277: Found conflicts between different versions of "NationalInstruments.Common" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. 1>CSC : error CS1705: Assembly 'NationalInstruments.ModularInstruments.NIDCPower.Fx40' with identity 'NationalInstruments.ModularInstruments.NIDCPower.Fx40, Version=20.6.0.39, Culture=neutral, PublicKeyToken=dc6ad606294fc298' uses 'NationalInstruments.Common, Version=19.0.40.49152, Culture=neutral, PublicKeyToken=dc6ad606294fc298' which has a higher version than referenced assembly 'NationalInstruments.Common' with identity 'NationalInstruments.Common, Version=17.5.40.49153, Culture=neutral, PublicKeyToken=dc6ad606294fc298' 1>C:\Users\Public\Documents\National Instruments\TestStand 2020 (64-bit)\Examples\NI_SemiconductorModule\Accelerometer\DotNET CXP\Code Modules\AccelerometerCodeModule.cs(731,4,731,51): error CS1705: Assembly 'NationalInstruments.ModularInstruments.NIDCPower.Fx40' with identity 'NationalInstruments.ModularInstruments.NIDCPower.Fx40, Version=20.6.0.39, Culture=neutral, PublicKeyToken=dc6ad606294fc298' uses 'NationalInstruments.Common, Version=19.0.40.49152, Culture=neutral, PublicKeyToken=dc6ad606294fc298' which has a higher version than referenced assembly 'NationalInstruments.Common' with identity 'NationalInstruments.Common, Version=17.5.40.49153, Culture=neutral, PublicKeyToken=dc6ad606294fc298' 1>C:\Users\Public\Documents\National Instruments\TestStand 2020 (64-bit)\Examples\NI_SemiconductorModule\Accelerometer\DotNET CXP\Code Modules\AccelerometerCodeModule.cs(743,4,743,51): error CS1705: Assembly 'NationalInstruments.ModularInstruments.NIDCPower.Fx40' with identity 'NationalInstruments.ModularInstruments.NIDCPower.Fx40, Version=20.6.0.39, Culture=neutral, PublicKeyToken=dc6ad606294fc298' uses 'NationalInstruments.Common, Version=19.0.40.49152, Culture=neutral, PublicKeyToken=dc6ad606294fc298' which has a higher version than referenced assembly 'NationalInstruments.Common' with identity 'NationalInstruments.Common, Version=17.5.40.49153, Culture=neutral, PublicKeyToken=dc6ad606294fc298' ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Workaround: Use the following steps to update the version of the NationalInstruments.Common reference.
|
Reported Version: NI-DCPower: 20.0 | STS Software Bundle: 19.5 | TestStand Semiconductor Module 2020 Resolved Version: TestStand Semiconductor Module 2020 Added: Sep 7, 2021 |
Final Time Issue Listed
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Additional Resources
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country
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).