Home Support Documentation Bugs

VeriStand 2020 R4 Known Issues

Created Jun 20, 2023

Overview

This document contains the VeriStand known issues that were discovered before and since the release of VeriStand 2020 R4. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details
115960 572887

Setting the Frame Type Option in the Raw Data Frame Configuration Page Has no Effect

As the frame type is pulled from the XNET database, the system definition setting does not affect the XNET configuration.

Workaround:

Set the frame type in the XNET database. Do not use the Raw Data Frame Type Configuration option in the system definition.

Reported Version:

VeriStand 2014

Resolved Version:

N/A

Added:

Jan 17, 2020
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:

N/A

Added:

N/A
1174315

Reflective Memory causes latency spikes on Linux RT

Depending on the PCL rate and number of channels, using the VeriStand Reflective Memory solution can cause latency spikes in the PCL on Linux RT. This can lead to HP counts and missed data transfers.

Workaround:

Use the modified GE Reflective Memory Custom Device with Multiple DMA Transfer. The 2020_pxiLinuxRt branch has a solution: https://github.com/NIVeriStandAdd-Ons/GE-Reflective-Memory-Custom-Device-multiple-DMA-transfer/tree/2020_pxiLinuxRt. 

Reported Version:

VeriStand 2020 R2

Resolved Version:

N/A

Added:

N/A

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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