This document contains the NI-DAQmx known issues that were discovered before and since the release of NI-DAQmx 2023 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 |
---|---|---|---|
1795745, 2281142 |
LabVIEW applications that allocate memory using nipalk.sys may occasionally have bugcheck (Blue Screen) errorsA customer has reported that one of their LabVIEW-based applications causes occasional bugcheck (Blue Screen of Death--BSoD) errors. The crash dump stacks vary, the involved process varies (nipalsm.exe, 'Customer Application'.exe), and the reported types vary (SYSTEM_SERVICE_EXCEPTION, ATTEMPTED_WRITE_TO_READONLY_MEMORY). However, all the observed errors involve nipalk.sys and they all seem to involve memory allocation. The error is observed only when the application initializes access to NI-DAQmx for the first time during an OS session. If the application is able to initialize successfully, the error is not observed while the application executes. The root cause of this error is currently unknown. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-DAQmx 19.1 | NI-PAL 19.0 Resolved Version: N/A Added: Feb 13, 2023 |
|
2509941 |
When adding connections to an 802.1w capable Ethernet switch, some NI Ethernet devices may briefly send duplicated packetsFieldDAQ and TSN Ethernet cDAQ devices have an integrated network switch to enable daisy-chaining of devices. When used with a dedicated ethernet switch, like the cRIO-9805, rings of devices can be created. To prevent network flooding when connected in rings, the switches on theses devices implement the rapid spanning tree protocol (IEEE 802.1w). This protocol establishes a loop-free logical network from a physical network which may have multiple paths between devices. Rarely, when a physical link is established between a FieldDAQ, TSN Ethernet cDAQ, or cRIO-9805 device and any other 802.1w capable ethernet switch, if the link completes a physical network loop, the NI device may incorrectly forward packets through the new loop. This error can be triggered when manually connecting a cable, or when a link is lost temporarily and returns; perhaps because of a loose connection. The time in this error state is brief; much less than a second. This error is not believed to affect the operation of FieldDAQ or cDAQ devices. It may affect devices using the network that cannot tolerate receiving duplicated packets. Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-DAQmx 20.1 Resolved Version: N/A Added: N/A |
|
1335783, 1859807, 2065508 |
Using the DAQAssistant with DAQmx 2022 Q3+ on LabVIEW 2023 Q3 Fails to Generate CodeUsing the DAQAssistant on LabVIEW 2023 Q3 with DAQmx 2022 Q3+ installed fails to configure the DAQAssistant node and gives the following code generation error: "LabVIEW Code Generation failed to execute. This may occur if the code gen engine is not properly installed, or if you are using a LabVIEW version under development" . Other workflows that use the DAQ Assistant to generate DAQmx tasks also fail.
Workaround: Install LabVIEW 2021 SP1
|
Reported Version: LabVIEW: 2022 Q3 | NI-DAQmx: 2022 Q3 | NI-DAQmx: 2022 Q4 | NI-DAQmx: 2023 Q1 | NI-DAQmx: 2023 Q2 | NI-DAQmx: 2023 Q3 | NI-DAQmx: 2023 Q4 Resolved Version: N/A Added: Aug 2, 2022 |
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