NI-XNET 2026 Q3 Known Issues

Overview

This document contains the NI-XNET known issues that were discovered before and since the release of NI-XNET 2026 Q3. 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; see Additional Resources.

Bug Number

Legacy ID

Description

Details

210421

Installing a New Version of NI-XNET To Older LabVIEW Can Break I/O Control Dialogs

NI-XNET (full version) and the NI-XNET Runtime Engine include the four most recent versions of the XNET LabVIEW driver library. If you build an application with a version of LabVIEW that is more than four years old, after you install a new version of NI-XNET your deployable installer will not include support for NI-XNET.

Workaround:

Do not install a new version of NI-XNET to use with a version of LabVIEW that is four years old or older.

Reported Version:

NI-XNET: 19.0

Resolved Version:

N/A

Added:

Jun 18, 2020

199657

XNET Read (Frame CAN) Can Return Fewer than the Requested Number of J1939 Frames Without Reporting Error

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-XNET: 17.0

Resolved Version:

N/A

Added:

May 30, 2020

2830100

A PHY can be put into low power mode when a PXIe-8520 link partner is not low-power capable

When a PXIe-8520 is configured to disable sleep capability, a paired link partner can still initiate a TC10 sleep request and enter a low-power sleep state while the paired PXIe-8520 port remains awake. This behavior differs from the existing behavior seen with the PXIe-8523, where disabling sleep capability on a port correctly prevents the paired link partner from entering a sleep state when both PHYs on the link cannot sleep.

Workaround:

Synchronizing sleep capability states between paired ports should be handled explicitly from the user application.

Reported Version:

NI-XNET: 2025 Q2

Resolved Version:

N/A

Added:

Mar 14, 2025

2948278, 3126745, 3160078, 3214290, 3220328

Creating a new NI-XNET Session from the LabVIEW Project Explorer Will Return an Error

Creating a new NI-XNET Session from the LabVIEW Project Explorer will return the following error:

Initialization Error

Some components required for editing are missing. Please contact National Instruments for more information.

Workaround:

Use the pre-created VI (XNET Create Session.vi) in LabVIEW for the same functionality.

Reported Version:

NI-XNET: 2024 Q3

Resolved Version:

N/A

Added:

Aug 5, 2025

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