The following items are notable issues fixed between the release of TestStand 2021 SP1 and TestStand 2022 Q4, 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 |
|---|---|---|---|
| 1877776 |
Reports generated by the Sequence Analyzer use default rules instead of rules you specifyWhen you make changes to the Sequence Analyzer rules and then click Generate Analysis Report, the report uses the default rules and the changes made to the rules are not reflected.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: May 31, 2022 |
|
| 1897783 |
The Home button on the report view control does not move the page to the beginningWhen you click the Home button in the report view, the report does not reposition to the beginning. Workaround: Press the Home key on the keyboard.
|
Reported Version: TestStand: 2021 SP1 Resolved Version: TestStand: 2022 Q4 Added: May 31, 2022 |
|
| 2148506 |
When relative paths are used, LabVIEW VIs with the same file name but belonging to different namespaces do not get loaded correctlyA LabVIEW step does not correctly resolve the relative path to a VI when multiple VIs with the same name are present in the TestStand search directories and the relative path specified in the step can resolve to more than one VI.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 1981778 |
The 'Not Editable' flag of a variable gets reset during run-timeWhen the 'Not Editable' flag for a variable is set at edit-time, it gets reset during run-time.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2041314 |
Unable to enter text in the text input field in a message popup window that contains an imageWhen using a message popup window that includes an image, inputting a serial number using either a scanner or a keyboard does not work. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2021 SP1 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2041314 |
Browsing to Create/Update Custom Type from Enum from step settings of substep crashes TestStandTestStand crashes when you have a custom step type with a Python substep, change the parameter type to enum, open the Create/Update Custom Data Type from Enum dialog box, and then provide the Python module path by browsing to the file or typing it in the field.
Workaround:
|
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2090284 |
The ForEach Step reports an edit-time error when iterating over unsigned and signed 64-bit arraysWhen using a ForEach loop to iterate over an array of numbers represented as signed or unsigned 64-bit integers, the Array to Iterate Over variable reports an edit-time error stating that it expected an Array of Numbers but found an Array of Numbers (Unsigned 64-bit integer) or Array of Numbers (Signed 64-bit integer).
Workaround: Option 1: Ignore the error, as it occurs during edit-time only.
Option 2: Ignore this error when performing a sequence analysis. |
Reported Version: TestStand: 2019 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2112613 |
TestStand crashes when modifying a Python or LabVIEW parameter type in a substepTestStand crashes if you add a Python or LabVIEW post substep in a custom step, then either change the parameter type of the return parameter for the Python substep, or change the parameter expression value for the LabVIEW substep, and then cancel the changes in the dialog box.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2113367 |
Unable to persist changes to Users.ini outside of the global TestStand environmentIf you make changes to user management (Configure > Station Options > User Manager) in a custom environment so that the default Users.ini file is not used, the changes do not persist when you click OK and restart TestStand. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2127752 |
PropertyObject leaks occur after execution of sequence files containing a LabVIEW step configured to use a LabVIEW projectWhen an API call from an external program, such as .NET or Python, executes a sequence containing a LabVIEW step that uses a LabVIEW project, TestStand reports PropertyObject leaks due to failure to release the sequence file that was executed.
Workaround: Option 1: Instead of creating Engine, create ApplicationMgr and use Engine from there. Option 2: Before shutting down Engine, call the Engine.UnloadAllModules() function.
|
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2135563 |
Error occurs if logging is enabled when TestStand executes a LabVIEW step and fetches default values for input parametersWhen logging is enabled for a parameter but 'Use Default Value' is not selected, TestStand throws an error stating that the default value for the parameter cannot be fetched.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 2141361 |
Unable to save sequence files to TestStand 2017 when they have a custom step type that uses a LabVIEW substepWhen a sequence file has a custom step type that uses a LabVIEW substep, saving the sequence file as a TestStand 2017 file fails, stating that 'OverrideBinaryVIPath' is an unknown variable or property name. Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2019 Resolved Version: TestStand: 2022 Q4 Added: N/A |
|
| 1926850 |
Typing "Step." causes an automatic auto complete to "Enums.SegmentListMode.Step." in an expressionWhen typing "Step." in an expression, it auto completes to "Enums.SegmentListMode.Step.". When you delete the extraneous characters, they return when you click away. This is encountered when TestStand Semiconductor Module is installed with TestStand.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2021 SP1 Resolved Version: TestStand: 2022 Q4 Added: N/A |
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.