NI-XNET 2023 Q2 Known Issues
Overview
This document contains the NI-XNET known issues that were discovered before and since the release of NI-XNET 2023 Q2. 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 |
|---|---|---|---|
| 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: N/A Added: Jul 4, 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: N/A Added: N/A |
|
| 2250040 |
Burst of Frames Is Sent After J1939 Single-Point Session of Cyclic Frames ResumesAfter a J1939
Single-Point session of cyclic frames has been stopped and then restarted, NI-XNET sends a quick burst of transport protocol frames. See related bug 2261309, Messages Stay Paused After J1939 Single-Point Session of Cyclic Frames Resumes. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-XNET: 20.0 Resolved Version: N/A Added: N/A |
|
| 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: N/A Added: N/A |
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).