This document contains the NI-XNET known issues that were discovered before and since the release of NI-XNET 2022 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 product documentation, support content, and NI Community forums; 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 |
Issues found in this section will not be listed in future known issues documents for this product.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
989923 |
Signal to CAN Frame Conversion Does Not Set Extended FlagCAN frames use arbitration identifiers that can be either standard or extended formats. In a Conversion Session, when a signal is converted to a CAN frame that uses an extended ID in the database, the extended flag is not being set
in the frame data.
Workaround: Programmatically set the extended? flag to True after the signal is converted by reading it from the database.
|
Reported Version: NI-XNET: 19.6 Resolved Version: N/A Added: Jul 1, 2022 |
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