Home Support Documentation Bugs

VeriStand 2020 R5 Bug Fixes

Created Jun 22, 2023

Overview

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

Include relevant system information, steps to reproduce, and any workarounds.

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:

VeriStand 2020 R5

Added:

N/A
1203847

Simple deployed VeriStand SDF results in one core reporting 100% CPU

Even simple VeriStand system definition files will result in one core having its CPU rail to 100%. However, this is a normal priority thread that will not lead to deadlock or interrupt network communication.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2020 R3

Resolved Version:

VeriStand 2020 R5

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