VeriStand 2020 R4 Bug Fixes

Overview

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

114970

LIN Scheduler is started before the session resulting in 500 ms of no response frames.

When XNET is configured to be a LIN master, the LIN scheduler appears to start before the outgoing XNET sessions are started. This results in the LIN master scheduler transmitting headers while the master's slave task is unprepared to transmit responses. As a result, the receiving LIN interface will instead detect "No Response" frames.

Workaround:

If you do not need to inline outgoing frames, you can deselect this option and the issue will not occur.

Reported Version:

VeriStand 18.0

Resolved Version:

VeriStand 2020 R4

Added:

N/A

1069833

Show frame IDs in hexadecimal format setting not fully applied

Enabling the setting "Show frame IDs in hexadecimal format" does not completely apply. The frame ID field updates properly to hexadecimal, but does not have a radix added.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2020

Resolved Version:

VeriStand 2020 R4

Added:

N/A

1095791

Deployment error -200077 with a module configured for HWTSP and Sample Rate less than 5 Hz

When enabling "Slow Background Conversion Mode" for a module and setting the Sample Rate to be less than 5 Hz, deployment will fail with error -200077.

Workaround:

Set the "Sample Rate" to either -1 or any value greater or equal than 5 Hz.

Reported Version:

VeriStand 2019

Resolved Version:

VeriStand 2020 R4

Added:

N/A

1163059

VeriStand crashes when moving Alarm Indicator in or out of Tab Control on UI Screen

Dragging an Alarm Indicator that is mapped to an alarm in the System Definition in or out of a Tab Control results in VeriStand crashing with a NullReferenceException.

Workaround:

Avoid dragging the alarm-mapped control into or out of a tab control. 

Reported Version:

VeriStand 2020 R3

Resolved Version:

VeriStand 2020 R4

Added:

N/A

1131292

Input Stream Read Time property introduces jitter to the PCL

The Input Stream Read Time property applies to the Raw Frame Datalogging settings for an XNET configuration in VeriStand, however, it also can considerably affect the HP Loop Duration even when no raw-frame logging is enabled.

Workaround:

Un-inlining the incoming frames. If that is not possible, add a transceiver state channel to all ports with incoming frames, and map the sleep channel to a channel that remains 0. 

Reported Version:

VeriStand 2020 R3

Resolved Version:

VeriStand 2020 R4

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