The following items are notable issues fixed between the release of TestStand 2021 and TestStand 2021 SP1, 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.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 903304 |
LabVIEW full-featured user interface crashes when using 'CommandKind_ToggleBreakpoint' in ExecutionViewManagerIf the cmdKind Enum in IExecutionViewMgr is set to CommandKind_ToggleBreakpoint in UserInterfaces\Full-Featured\LabVIEW\Source Code\TestExec.llb\Configure ExecutionView Manager.vi, the full-featured LabVIEW user interface crashes when a breakpoint is applied in any test sequence. This issue was observed specifically when the above changes were made to associate the Terminate/Restart button with the ToggleBreakpoint command, the UserInterfaces\Full-Featured\LabVIEW\Source Code\TestExec.llb\Top-Level VI.vi was executed, a sequence file was loaded, and a breakpoint was applied to a step.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2017 SP1 Resolved Version: N/A Added: Oct 11, 2021 |
|
| 1144328 |
Doing 'SaveAs Previous' resets the values of Python and LV NXG adapter specific extended data types to default in the original fileWhen you create a sequence file in TestStand 2020 that has custom data types with non-default values, saving it in a previous version resets the values to default. This is an issue with the Python and LabVIEW NXG adapters. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: N/A Added: Aug 9, 2021 |
|
| 1210473 |
Changes to sub-elements of a cluster within an array of cluster do not get updatedWhen changes occur within an array of clusters which is a sub-element of a VI parameter, TestStand does not detect the changes when updating a TS custom data type to match the VI parameter.Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2019 Resolved Version: N/A Added: Oct 11, 2021 |
|
| 1358314 |
Values of sequence call parameters are lost after deleting parameters from called sequenceParameter values are lost from a Sequence Call step when a parameter in the step uses the default value, then you remove the parameter from the called subsequence and reload the Sequence Call step. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2017 Resolved Version: N/A Added: Oct 11, 2021 |
|
| 1440035 |
TestStand hangs when Sweep Loop step generates a large number of values for a parameterWhen a parameter in a Sweep Loop step is configured in a way that generates a large set of values, TestStand hangs while executing the step until the generation of the values is complete. Workaround: There is currently no known workaround for this issue. TestStand 2021 limits the number of values for a parameter to 300,000.
|
Reported Version: TestStand: 2021 Resolved Version: N/A Added: Oct 11, 2021 |
|
| 1558674 |
Error 'Error occurred during processing request' displayed when filter is applied to a parameter and the Test Vector Table is refreshedIf the Test Vector Table is open with a filter applied to a parameter, and you modify the step settings of the Sweep Loop step so they are out of sync with the Test Vector Table, TestStand displays "Error occurred during processing request" when you refresh the Test Vector Table.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2021 Resolved Version: N/A Added: Oct 11, 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.