VeriStand 2021 R2 Bug Fixes

Overview

The following items are notable issues fixed between the release of VeriStand 2021 and VeriStand 2021 R2, 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 VeriStand.

Bug Number

Legacy ID

Description

Details

1754693

Slow Screen connections after deploying a project containing a model with too many matrix parameters

Importing parameters from a model with a 1000+ matrix parameters, leaving the Model Parameter Window open, and then deploying the project can cause significant system slowdown. Screens in your project may take a minute to connect and start receiving value updates.

Workaround:

Close the Model Parameter Manager tool window before deploying the project.

Reported Version:

VeriStand 2020 R3 | VeriStand 2020 R5

Resolved Version:

VeriStand 2021 R2

Added:

N/A

1888830

Target rates in the VeriStand Editor and System Explorer do not match

Setting the PCL rate using the VeriStand Editor target rate control and then later using the System Explorer target rate control can cause a mismatch in displayed rates.

Workaround:

Set the target rate in only one location.

Reported Version:

VeriStand 2021

Resolved Version:

VeriStand 2021 R2

Added:

N/A

1784820

VeriStand projects cannot open on Windows PCs with old versions of .NET Framework

VeriStand 2021 cannot open projects on PCs with either of the following installed.
  1. Windows Server 2016
  2. .NET Framework prior to version 4.7.2  
Aside from Windows Server 2016, all supported Windows OS versions install with .NET Framework 4.7.2 or later by default.

Workaround:

Install .NET Framework version 4.7.2 or later.

Reported Version:

VeriStand 2021

Resolved Version:

VeriStand 2021 R2

Added:

N/A

1893574

RT target renaming causes errors in the Manage Targets tool

Modifying a System Definition's RT target name using the VeriStand Editor configuration pane causes the Manage Targets tool to error out. Subsequent attempts to deploy or connect to RT targets using the tool will fail.

Workaround:

Use System Explorer to modify all RT target names.

Reported Version:

VeriStand 2021

Resolved Version:

VeriStand 2021 R2

Added:

N/A

1880356

RT target connection displayed in the Target Log Viewer is incorrect

Opening and closing a system definition in System Explorer may cause the connected target displayed in the Target Log Viewer to be incorrect. This may occur under the following circumstances:
  1. The system definition has more than one RT target.
  2. The Target Log Viewer tool is actively connected to a RT target before opening and closing the System Explorer.

Workaround:

Ignore the incorrect target displayed in the Target Log Viewer control.

Reported Version:

VeriStand 2021

Resolved Version:

VeriStand 2021 R2

Added:

N/A

Additional Patch Information

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.

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).