NI-XNET 2025 Q4 Known Issues
Overview
This document contains the NI-XNET known issues that were discovered before and since the release of NI-XNET 2025 Q4. 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 DialogsNI-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 ErrorWorkaround: There is currently no known workaround for this issue. |
Reported Version: NI-XNET: 17.0 Resolved Version: N/A Added: May 30, 2020 |
|
| 1855134 |
LabVIEW Crashes w/ XNET Read and "Shared Clone Reentrant" ModeIf the XNET Read VI is called in a SubVI with execution mode
set to “Shared clone reentrant execution,” the application might crash. Workaround: Change the execution mode to “Preallocated clone reentrant
execution” or “Non-reentrant execution,” depending on the application
requirements.
|
Reported Version: NI-XNET: 21.8 Resolved Version: NI-XNET: 21.8 Added: Apr 7, 2022 |
|
| 2251664 |
Sending Multiple Data as Frames on AssignFrameIdRange is not SupportedThe LIN Specification indicates that multiple bits can be sent in a frame. If AssignFrameIdRange is used multiple times in a schedule, some data is lost and random values appear at the end of the
command. The following image compares the data used in the LDF file with the
data imported by NI-XNET.  Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-XNET: 2022 Q3 Resolved Version: NI-XNET: 2023 Q4 Added: Oct 4, 2023 |
|
| 2251215 |
NI-XNET Component Fails to Load When Added to a LabVIEW ProjectWhen an XNET palette item is added to a blank VI in a
LabVIEW project, a conflict occurs in the project explorer dependency tree. After the project has been saved and closed, the component points to the wrong VI
paths.  Workaround: First create the VI with the XNET content, and only then add it to the project and save the project. |
Reported Version: NI-XNET: 2023 Q1 Resolved Version: NI-XNET: 2023 Q4 Added: Oct 3, 2023 |
|
| 2360396 |
"File not Found" Message Appears When User Tries to Access XNET LV Project Examples on LinuxA "File not Found" message is displayed when users try to use the NI Example Finder to access NI-XNET LabVIEW project examples on Linux. The projects directory that is installed for Windows environments cannot yet be installed on Linux machines.  Workaround: Access LabVIEW project examples on Windows platform.
|
Reported Version: NI-XNET: 21.0 Resolved Version: NI-XNET: 2023 Q4 Added: Oct 3, 2023 |
|
| 2830100 |
A PHY can be put into low power mode when a PXIe-8520 link partner is not low-power capableWhen 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 |
|
| 3107733, 3138766, 3138766, 3168906 |
NI-XNET Read Frame VI Returns No Data When the LabVIEW Queue is Used to Store the Frame Payload
This issue affects all the communication protocols with NI-XNET 2025 Q2 driver but with NI-XNET 2025 Q3 driver, only LIN and FlexRay protocols exhibit this issue while other communication protocols (CAN, CAN FD, J1939, and Automotive Ethernet) do not. Workaround: There is currently no known workaround for this issue.
|
Reported Version: NI-XNET: 2025 Q2 Resolved Version: NI-XNET: 2025 Q4 Added: Jul 3, 2025 |
|
| 2948278, 3126745, 3160078, 3214290, 3220328 |
Creating a new NI-XNET Session from the LabVIEW Project Explorer Will Return an ErrorCreating a new NI-XNET Session from the LabVIEW Project Explorer like below:  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 |
|
| 3304082, 3431155 |
NI-XNET Bus Monitor on LinuxRT Logs Timestamps in UTC Instead of Local TimeOn LinuxRT systems, log files generated by the NI-XNET Bus Monitor record timestamps in Coordinated Universal Time (UTC), whereas on other supported operating systems, timestamps are recorded in local time.
Workaround: Users may perform post-processing on the log files to manually convert the UTC timestamps to the appropriate local time.
|
Reported Version: NI-XNET: 2025 Q4 Resolved Version: N/A Added: Oct 15, 2025 |
|
| 3261560, 3372138 |
Internal Error During NI-XNET Session Creation with FIBEX Files with Missing InformationWhen attempting to create a session using a FIBEX file that lacks COMPU-METHOD information within the CODING element, the NI-XNET driver may encounter an internal error. This issue arises due to incomplete signal definition metadata required for session initialization.
Workaround: Open the affected FIBEX file in the NI-XNET Database Editor and save it. This process automatically adds the missing COMPU-METHOD information, allowing session creation to proceed without error.
|
Reported Version: NI-XNET: 2025 Q3 Resolved Version: N/A Added: Oct 15, 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).