VeriStand 2020 Bug Fixes

Überblick

The following items are notable issues fixed between the release of VeriStand 2019 R3 and VeriStand 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 VeriStand 2020.

Bug Number

Legacy ID

Description

Details

114960 720821

System Definition File Error Using Inline Timing and Sync Custom Device

When using the Custom Device Template Tool to create an Inline Timing and Sync Custom Device, importing the device creates a "Timing Source Init VI_1" section in the System Definition XML. This section causes error -307832 when adding the Inline Timing and Sync Custom Device.

Workaround:

Open the VeriStand project's .nivssdf file with a text editor, and delete the "Timing Source Init VI_1" section.

Reported Version:

VeriStand 2018

Resolved Version:

VeriStand 2020

Added:

Jan 17, 2020

954238

Old Screens Fail to Load if They Have a RT Sequence Control Using Parameters

Workaround:

Recreate the screen. 

Reported Version:

VeriStand 2019 R3

Resolved Version:

VeriStand: 2019 R3 f1

Added:

Jan 17, 2020

950176

RT Sequence Control in a Cluster Interaction Causes VeriStand UI to Crash

After saving and closing a project with a RT Sequence Control in a cluster, opening the project and interacting with that control will cause the VeriStand UI crash.

Workaround:

Do not place a RT Sequence Control in a cluster.

Reported Version:

VeriStand 2018 SP1

Resolved Version:

VeriStand 2020

Added:

Jan 17, 2020

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