VeriStand 2021 Bug Fixes

Overview

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

1181886

System Definition File created with (ECUMC) System Definition API uses invalid "SupportedTarget" entry

Using the System Definition API to create a system definition file which includes an ECUMC Custom Device fails to deploy on Windows.

Workaround:

Edit the system definition file to use "PharLap & Windows" in the "Driver VI Path_X" node. The source distribution is found and deployment is successful.

Reported Version:

VeriStand 2020 R4

Resolved Version:

VeriStand 2021

Added:

Apr 16, 2021

116076 650143

Model parameter files do not import correctly when Windows localization settings specify "," as the decimal separator

Parameters included in the Stimulus Profile Editor shipping example fail to import because model parameter files generally do not support commas as a delimiter.

Workaround:

Change the Windows system language to English before importing model parameter files.

Reported Version:

VeriStand 2016

Resolved Version:

VeriStand 2021

Added:

Jul 26, 2021

1505083

Error 363504 returned when restarting the VeriStand engine on a password-protected RT Target

The Restart VeriStand Engine button found in the Document pane of the Mapping Diagram generates an error when the connected RT target is password-protected.

Workaround:

Set a blank password for the RT controller.

Reported Version:

VeriStand 2019 R3

Resolved Version:

VeriStand 2021

Added:

Jul 26, 2021

375107 352124

Stimulus Profile Editor displays error when viewed on a remote machine

The Stimulus Profile Editor returns a 'This freezable cannot be frozen' error when interacting with SandDoc components. This error occurs when connecting to a remote Windows system with the 'Windows Classic' theme enabled.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2011 SP1

Resolved Version:

VeriStand 2021

Added:

N/A

1521278

Alarm Monitor does not work for alarms in folders

The VeriStand Alarm Monitor does not function correctly on alarms that are inside folders in the Project Files pane. The following actions do not occur when alarms are in folders. 
  1. Reading the alarm status in Active. 
  2. Acknowledging the alarm status in Active. 
  3. Setting the state (enabled/disabled) in Rules.

      Workaround:

      Don't put the alarms in folders. Or write a custom tool using the LabVIEW API.

      Reported Version:

      VeriStand 2020 R5

      Resolved Version:

      VeriStand 2021

      Added:

      N/A

      1618401

      VeriStand cannot add channels to a logging specification

      In a logging specification document with too many existing channels, the Add channel window will appear offscreen. Enlarging the window can help, but only until reaching the end of the monitor. 

      Workaround:

      User could hand edit document in text editor to add channels to the log spec

      Reported Version:

      VeriStand 2020 R6

      Resolved Version:

      VeriStand 2021

      Added:

      N/A

      1622497

      VeriStand crashes due to ChromiumFX proxy authentication error

      VeriStand crashes on second launch due to an issue with proxy authentication in ChromiumFX. The error is usually caused by IT policies preventing authentication. An exception returns from NIWebBrowserChromiumFx.RequestHandler_GetAuthenticationCredentials

      Workaround:

      Work with IT department to address authentication failure.

      Reported Version:

      VeriStand 2020 R6

      Resolved Version:

      VeriStand 2021

      Added:

      N/A

      1719554

      Screen memory leak

      Screen memory usage may grow by gigabytes over a 15-30 minute time span. This can occur in a Screen with certain control types under a heavy workload. For example, Screens with hundreds of updating numeric indicators and a chart with hundreds of channels are more likely to experience a memory leak.

      Workaround:

      Use a less complex screen that is processing less data.

      Reported Version:

      VeriStand 2020 R5

      Resolved Version:

      VeriStand 2021

      Added:

      N/A

      1721945

      VeriStand crashes while undeploying an active logging document

      VeriStand may crash while undeploying a system definition with an active logging document. This crash typically occurs after the first or second undeploy attempt. 

      Workaround:

      Stop the logging before undeploying

      Reported Version:

      VeriStand 2020 R5

      Resolved Version:

      VeriStand 2021

      Added:

      N/A

      1661320

      VeriStand returns Error 1172 when loading a project

      Error 1172 is intermittently reported when opening a project with too many dependencies. 

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      VeriStand 2020 R4

      Resolved Version:

      VeriStand 2021

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