NI-DAQmx (18.0 to 18.6) Bug Fixes


Below are the IDs and titles of a subset of issues fixed in recent releases of NI-DAQmx. This is not an exhaustive list of issues fixed. If you have a CAR ID, you can search this list to validate that the issue has been fixed.

Issues Fixed in NI-DAQmx 18.6

CAR ID Description Fixed NI-DAQmx Version
705662 Network cDAQ hangs while running self-test during initialization 18.6


Issues Fixed in Previous Versions of NI-DAQmx

CAR ID Description Fixed NI-DAQmx Version
707701 NI-DAQmx crash when calling DAQmxCreateAIVoltageChan in Visual Studio on the NI 9205 18.5
702845 In LabVIEW NXG, a DAQmx task created from an input terminal initially fails with Error -200428 18.5
694140 Gain adjustment value is not set after shunt calibration in DAQExpress 18.5
699289 Including NIDAQmx.h may change the layout of user-defined structs that contain CVITime, CVIAbsoluteTime, or CVITimeInterval 18.5
539710 If the trigger source frequency is too high, NI-DAQmx errors with -200361 on a cDAQ device 18.5
646229 Process remains after exiting C++ application without stopping or aborting on Linux RT cDAQ 18.1
675713 RTSI line resource reserved error occurs while synchronizing tasks on a TSN cDAQ 18.1
697690 Ethernet cDAQ appears to crash on DAQmx watchdog expiration when DSA task is running 18.1
689440 Time trigger uses default time in multi-device tasks when explicitly committed 18.1
688114 When running DAQmx frequency tasks in NI MAX on a NI 9401, the task hangs indefinitely when no signal is connected 18.1
680182 Channel Calibration Wizard forgets Acquisition Attributes when importing NI MAX database 18.1
680179 PXIe-4300 with TB-4300C ignores custom scale after applying channel calibration 18.1
673712 DAQmx Start:Terminal property does not return segment number on cDAQ-9179 when user specifies timing engine 18.1
659756 Explicit commit on a finite task causes continuous acquisition with USB-6001 18.1
677161 Sync lock loss error occurs on TSN enabled devices 18.0
682682 Network cDAQ fails self-test, reset, and reserve with Error -52003 18.0


Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).