The following items are notable issues fixed between the release of TestStand 2019 SP1 and TestStand 2020, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of TestStand.
The following items are Bug Fixes in TestStand 2020.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 220360 | 643628 |
Attempting to log INF, NAN, or IND values to a Microsoft SQL Server database results in an error.Microsoft SQL Server FLOAT data type does NOT support storing +INF, -INF, NAN and IND as defined by IEEE 754. Workaround: Update your schema to use a precondition expression to not log a value for non-finite values. |
Reported Version: TestStand 4.0 Resolved Version: TestStand 2020 Added: May 21, 2017 |
| 220503 | 544646 |
Error -17313 or -18005 occurs when passing a .NET refnum constant in a cluster from newer versions of LabVIEW into TestStandIf a LabVIEW VI with a cluster that contains a .NET refnum is passed into TestStand, then error -17313 or -18005 may occur. An example of this type of refnum would be when you create a constant from a .NET terminal in LabVIEW. Workaround: Construct the .NET object from a constructor node in LabVIEW, bundle it into a cluster, and pass that cluster out of LabVIEW. |
Reported Version: TestStand 2014 Resolved Version: TestStand 2020 Added: Jul 17, 2016 |
| 220526 | 493571 |
LabVIEW code modules with a NI VeriStand .NET type definition reference as a VI parameter will fail to load in TestStand when the LabVIEW Development System is active.This issue only occurs when using the Workspace Manager or Project reference from the NI VeriStand API. These references are .NET objects type definitions in LabVIEW. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2013 Resolved Version: TestStand 2020 Added: Aug 2, 2015 |
| 220514 | 736130 |
When a Python module is inspected, attributes with type annotation are not listed in the combo boxWorkaround: Manually type the attribute name in the editable combo box control. |
Reported Version: TestStand 2019 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 220570 | 409938 |
ATML reports that use tr5_horizontal.xsl and tr6_horizontal stylesheet do not display icons correctly when report path contains Japanese charactersWhen you execute a sequence file on a Japanese operating system and the report path contains Japanese characters, the ATML report stylesheet tr5_horizontal.xsl and tr6_horizontal cannot load the images for the expand/collapse button and the error icon. TestStand 2013 fixes this issue for all other stylesheets. Workaround: Click on expand/collapse button twice. |
Reported Version: TestStand 2012 Resolved Version: TestStand 2020 Added: Jun 27, 2013 |
| 220642 | 733030 |
When using the Create/Update Data Type from Struct dialog in the C++ and CVI adapters, TestStand does not get the array sizes for embedded arraysWorkaround: Manually set array sizes in struct passing for the data type. |
Reported Version: TestStand 2019 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 220587 | 736253 |
If LabVIEW VIs containing TestStand palette VIs are opened after TestStand Palette VIs have been removed or not added by Version Selector, LabVIEW incorrectly asks to install the NI GOOP Development SuiteWorkaround: Run TestStand Version Selector or launch the Sequence Editor before opening any LabVIEW VIs that contain TestStand palette files. |
Reported Version: TestStand 2019 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 220563 | 736637 |
Output from LabVIEW string may be incorrectly parsed when converted to binary representationIf the string contains null characters, the output will be cut off even if the user sets them to binary strings. Workaround: Change the representation of the string to a format other than binary |
Reported Version: TestStand 2012 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 220732 | 718635 |
TestStand Diff and Merge Utility produces unreadable XML report when analyzing sequences with invalid charactersThe utility will produces an unreadable XML report when processing strings that contain characters outside of the XML valid character range, such as ASCII control characters. This can commonly occur in situations where raw data is stored in a string. Workaround: Remove invalid characters from the sequence. |
Reported Version: TestStand 2017 Resolved Version: TestStand 2020 Added: Jan 23, 2019 |
| 221007 | 733962 |
If the SystemLink Server cannot be reached and the report type is set to HTML and PDF reporting is enabled, TestStand will crashWorkaround: Ensure that the SystemLink Server can be reached from the client machine. |
Reported Version: TestStand 2019 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 221026 | 482840 |
The ListBox UIControl does not correctly refresh data when connected as an ExecutionList of Execution View Manager.When creating a TestStand UI using a TestStand ListBox that is connected to an ExecutionList of the Execution View Manager, the control does not always show the correct list of executions. This problem is more noticeable for user interfaces that use the batch process model. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2012 Resolved Version: TestStand 2020 Added: Aug 2, 2015 |
| 220943 | 655076 |
The /Version command line argument for the TestStand Version Selector does not work with minor versions.When using a minor version, such as 16.1 (TestStand 2016 SP1) with the /Version argument, the TestStand Version Selector unregisters the active version, does not register any new version, and does not report any errors. Workaround: Use the major version. For example, 16.0 instead of 16.1. |
Reported Version: TestStand 2014 SP1 Resolved Version: TestStand 2020 Added: Jan 25, 2018 |
| 305594 | 589962 |
Expand and Report stylesheets for ATML 5.00 and ATML 6.01 Standards Report Document can display subsequent step results as indices resultsIf you configure the Looping section for a step without enabling the "Record Result of Each Iteration" option, an ATML 5.00 or 6.0.1 Standards Report Document that uses the Expand or Report stylesheets incorrectly displays the results for subsequent steps as the indices results for the looping step. Workaround: Enable the "Record Result of Each Iteration" option, or use the Horizontal style sheet instead. |
Reported Version: TestStand 2014 Resolved Version: TestStand 2020 Added: Dec 12, 2016 |
| 305829 | 600209 |
Logging the default value of a LabVIEW complex number parameter failsWhen the default value box for a LabVIEW complex number parameter is checked and logging for the parameter is enable, this will fail with an error stating "Unable to find variable or property". Workaround: Uncheck the default value box and manually enter the default value. |
Reported Version: TestStand 2012 SP1 Resolved Version: TestStand 2020 Added: Jan 23, 2019 |
| 305902 | 141627 |
HTML, XML, and ATML reports do not preserve formatting when displaying string values that contain LF('\n'), CRLF('\r\n'), or whitespace charactersReports based on the HTML and XML stylesheet are transformed into HTML when displayed in the Report pane or in a browser. Whitespace characters, such as multiple spaces, and line breaks do not display in the report because XML parsers strip them out when displaying them displaying HTML. Workaround: You can manually convert line break characters to the string <br/> if you intend to generate an HTML report. You can similarly convert multiple whitespace characters into characters. |
Reported Version: TestStand 4.0 Resolved Version: TestStand 2020 Added: May 17, 2009 |
| 305794 | 662205 |
Unable to update existing type definition for an array of clusters containing an enum from a LabVIEW NXG code module.The Create/Update Custom Data Type dialog box's option to "Update an Existing Type" will not update the TestStand type definition from LabVIEW NXG if the type has an array of clusters that contains an enum. After pressing the "Update an Existing Type" button you will see that no changes to the TestStand type definition were made. Workaround: You can manually update the TestStand type definition, or delete the existing type and create a new type definition in TestStand. |
Reported Version: TestStand 2017 Resolved Version: TestStand 2020 Added: Jan 25, 2018 |
| 305876 | 736115 |
"Invalid VI Reference" reported during edit-time for a broken VI when the adapter is set to use the LabVIEW Run-time EngineWhen a broken VI is selected for the module in the TestStand LabVIEW step settings panel, with the adapter configured to RTE, the error message reports "Invalid VI Reference," which does not match what appears in the error log for the VI. Workaround: View the detailed error report log and fix the broken VI. |
Reported Version: TestStand 2019 Resolved Version: TestStand 2020 Added: May 21, 2019 |
| 305509 | 665065 |
LabVIEW Full-Featured UI hangs while running in the development environment while it loads a code module in a LabVIEW Project.When running" Full UI - Top-Level VI.vi" from the LabVIEW Full-Featured UI example project in the LabVIEW Development Environment, a hang occurs when attempting to execute a sequence that contains a code module that loads from a separate LabVIEW project. Workaround: The hang only occurs when running the UI in the LabVIEW Development Environment. Build the UI into TestExec.exe before executing the sequence. |
Reported Version: TestStand 2016 SP1 Resolved Version: TestStand 2020 Added: Jan 25, 2018 |
| 305903 | 161523 |
Arrays passed from LabVIEW to TestStand are transposedWhen a VI connector pane passes an array from LabVIEW to TestStand, the array is transposed. For example, a 2D array of four columns and five rows from a LabVIEW VI appears as an array of five rows and four columns when stored in a TestStand PropertyObject. Workaround: Pass the array back to LabVIEW, and the opposite transformation occurs to restore the original position of the elements. |
Reported Version: TestStand 3.0 Resolved Version: TestStand 2020 Added: May 17, 2009 |
| 305880 | 722577 |
Random function in TestStand expressions can return the same value if re-seeded on every callWhen looping over the Random() function in a TestStand expression, if the random value is re-seeded on every call to the function over time it can return the same value on repeated calls. In general, re-seeding a pseudo-random number generator is something that should be done once, or at least rarely, for the lifetime of the use of that generator because it resets the pseudo-random number distribution. Workaround: Only re-seed the number once, not on every call. |
Reported Version: TestStand 2016 Resolved Version: TestStand 2020 Added: Jan 23, 2019 |
| 305802 | 683498 |
Common Parameters are Disabled When Selecting Multiple LabVIEW NXG StepsWhen selecting multiple LabVIEW NXG steps to edit common properties, all properties will be disabled rendering them unable to be edited. Workaround: Edit step properties individually. |
Reported Version: TestStand 2017 Resolved Version: TestStand 2020 Added: Jan 25, 2018 |
| 305883 | 733626 |
When a executing a sequence file with the remote engine using the batch process model, property object leaks are reportedThe property leak data mentions leaks about both sequence file and execution objects, as well as the result processor sequence files even though result processing may be disabled. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand 2017 Resolved Version: TestStand 2020 Added: May 21, 2019 |
The following items are Bug Fixes in TestStand 2020 f1.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1091626 |
Memory leak observed on creating and closing execution windowsMemory leaks may occur when opening and closing multiple execution documents in the TestStand Sequence Editor. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1393320 |
LabVIEW Crashes with TestStand Full-Featured User Interface Example VIIf you open the block diagram for the Load Top-Level VI.vi example VI, then Ctrl-click and drag the IApplicationManager property node to make a copy, LabVIEW slows down and then crashes.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2020 | TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1531818 |
LabVIEW Adapter incorrectly caches icons for VIs in the project but does not use themThe LabVIEW Adapter incorrectly caches icons for VIs in the project but does not use them. This causes problems when using VIs from projects that have a large number of items.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1168500 |
Visual Studio reports exceptions when opening custom step settings panels that use TSTextBox, TSErrorProvider, and other TestStand controls from TestStand 2020Controls like TSTextBox and TSErrorProvider, provided by TestStand 2020 to use on custom panels, cause an exception when opened in Visual Studio. When this occurs you cannot edit the panel unless you choose the Ignore and Continue option, but choosing that option removes the textbox controls from the panel.
Workaround: Edit the designer source code directly and avoid using the visual designer in Visual Studio. |
Reported Version: TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1498966 |
TestStand incorrectly unloads code modulesWhen a new thread calls a sequence, then the sequence calls a code
module, TestStand incorrectly unloads the code module when the thread
completes even when the reference to the thread is held in a file
global. Workaround: Use Notification steps to prevent the new thread from completing execution until the main execution is complete.
|
Reported Version: STS Software Bundle: 20.0 | TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1489985 |
TestStand crashes when passing an array element variable as tuple to a Python moduleTestStand crashes when passing an argument to a Python function in an Action step. This occurs when the data being passed is a single element in an array of containers (custom data type), and the container name is empty.
Workaround: Use a container variable with the same data type outside of an array, or provide a name for the array element which will be passed as a tuple.
|
Reported Version: TestStand: 2019 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1493885 |
TestStand Error -17502 When Passing Array of Containers by Reference to Subsequence and then to Python ModuleTestStand throws error -17502: System Level Exception when an array of containers is passed by reference to a Sequence Call, which then passes that value to a Python module. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2019 f4 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1482008 |
TestStand occasionally hangs when Batch and Parallel Process Model executions are terminatedWhen running a client sequence using either the Batch or Parallel Process Model, if the
Test UUTs execution entry point is terminated, that execution can
occasionally hang on step 0 of Cleanup.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
|
| 1644186 |
VIs that are used to create sessions may get unloaded inadvertently and the session handle may get releasedVIs that are used to create sessions may get unloaded inadvertently and the session handle may get released.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2020 | TestStand Semiconductor Module: 2019 SP1 Resolved Version: TestStand 20.0.1 Added: Oct 27, 2021 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.