Home Support Documentation Bugs

NI-XNET 21.8 Bug Fixes

Created Jun 22, 2023

Overview

The following items are notable issues fixed between the release of NI-XNET 21.5 and NI-XNET 21.8, 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 NI-XNET.

Bug Number

Legacy ID

Description

Details
1855134

LabVIEW Crashes When XNET Read API is Called Through a SubVI

If a VI receives CAN FD or CAN FD+BRS frames after it has created an in-memory database with clusters and named :can_fd: or :can_fd_brs:, these frames may overwrite unallocated memory and cause LabVIEW to crash abruptly.

Using empty databases named :can_fd: or :can_fd_brs: as input to Create Session is not problematic.

Workaround:

In NI-XNET releases prior to 21.8, do not use :can_fd_brs: or :can_fd: in-memory database to create clusters when the database is used as input to a frame stream session at the same time.

Reported Version:

NI-XNET: 18.5

Resolved Version:

NI-XNET: 21.8

Added:

Apr 7, 2022
1840970

XNET Generic Synchronization LabVIEW Example is Confusing

Synchronized Interface and Synchronizing Interface labels are reversed, and the layout of the controls for master and slave interfaces on the front panel is confusing.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-XNET: 20.5

Resolved Version:

NI-XNET: 21.8

Added:

Apr 6, 2022

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