This document contains the NI-DAQmx known issues that were discovered before and since the release of NI-DAQmx 20.1. 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.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 196440 | 698239 |
Blank Test Panel will display for NI 9469 used in CompactRIO with DAQmx controllers.If you click the *Self Test* button in NI MAX for the NI 9469, a Test Panel will open with nothing displayed. The *Self Test* button in NI MAX is incorrectly enabled for this module. The blank Test Panel does not imply anything negative about the NI 9469's functionality. Workaround: There is currently no known workaround for this issue. This issue does not affect module functionality.
|
Reported Version: NI-DAQmx 18.1 Resolved Version: N/A Added: Jun 24, 2018 |
| 255732 | 742510 |
USB X Series Devices Do Not Work as SCXI Controllers in NI-DAQmx 17.6 and LaterThe USB-6341, USB-6343, USB-6351, USB-6353, USB-6356, USB-6361, USB-6363, and USB-6366 are unable to be configured as a controller for SCXI devices in NI-DAQmx 17.6 and later. The USB-6346 and USB-6349 are unable to be configured as an SCXI controller in any release of NI-DAQmx. Workaround: Use either non-USB X-Series devices or revert to a version of DAQmx prior to 17.6
|
Reported Version: NI-DAQmx 17.6 Resolved Version: N/A Added: May 1, 2020 |
| 661551 |
NI cDAQ-918x/919x Works Incorrectly if Path Includes Non-ASCII (Multi-Byte) CharactersThe NI cDAQ-918x/919x might not function correctly if NI-DAQmx is installed in a path with non-ASCII (or multi-byte) characters. This issue most commonly affects NI-DAQmx installations on Korean, Japanese, and Chinese versions of Windows.
Workaround: If your NI-DAQmx installation path contains non-ASCII characters, uninstall NI-DAQmx and other NI application development software and then reinstall your software to a path without non-ASCII characters. |
Reported Version: NI-DAQmx 9.2 Resolved Version: N/A Added: May 6, 2020 |
|
| 435149 |
Aborting Single-Point Reads and Writes in LabVIEWSingle-point reads and writes do not respond to the Abort Execution button in LabVIEW.
Workaround: There is currently no known workaround for this issue. |
Reported Version: NI-DAQmx 9.0.1 Resolved Version: N/A Added: Aug 14, 2009 |
|
| 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 |
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