This document contains the NI-XNET known issues that were discovered before and since the release of NI-XNET 2025 Q1. 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 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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