NI-DAQmx (18.0 to 19.1) Bug Fixes


The following items are issues fixed in NI-DAQmx, starting with NI-DAQmx 18.0. 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 19.5

CAR or Bug IDDescriptionFixed NI-DAQmx Version
734812NI-DAQmx does not return an error when specifying an unsupported external sample clock for NI USB 6001/2/3 AO tasksNI-DAQmx 19.5
728999Incorrect force measurement sensitivity units in IEPE - Continuous exampleNI-DAQmx 19.5
650465Creating a Current Channel using a TB-4300C with Measurement Studio returns Error -200077 indicating incorrect Shunt Resistor valueNI-DAQmx 19.5
202389ELVIS II+ Oscilloscope from Instrument Launcher does not work with new 19.0 version of NI-ELVISmxNI-DAQmx 19.5


Issues Fixed in Previous Versions of NI-DAQmx

CAR IDDescriptionFixed NI-DAQmx Version
703378S Series DAQ Devices hang when acquiring in DMA transfer mode on Linux19.1
636702ANSI C Examples fail to compile due to missing file locations on Linux19.1
736987Setting invalid strain gage resistance value with FieldDAQ causes a crash19.1
734612Error -209836 using FirstSampClk properties on a TSN-sync'ed FieldDAQ target19.1
734581Error: Undefined symbol when compiling LabWindows/CVI application using function DAQmxCreateCIDutyCycleChan19.1
719193NI 9260 AO slave task throws Error -201347 "Sync Pulse not detected" when synchronized with AI task19.0
731238Data corruption can occur when synchronizing multiple NI 9202s with different filter cutoffs19.0
705662Network cDAQ hangs while running self-test during initialization18.6
707701NI-DAQmx crash when calling DAQmxCreateAIVoltageChan in Visual Studio on the NI 920518.5
702845In LabVIEW NXG, a DAQmx task created from an input terminal initially fails with Error -20042818.5
694140Gain adjustment value is not set after shunt calibration in DAQExpress18.5
699289Including NIDAQmx.h may change the layout of user-defined structs that contain CVITime, CVIAbsoluteTime, or CVITimeInterval18.5
539710If the trigger source frequency is too high, NI-DAQmx errors with -200361 on a cDAQ device18.5
646229Process remains after exiting C++ application without stopping or aborting on Linux RT cDAQ18.1
675713RTSI line resource reserved error occurs while synchronizing tasks on a TSN cDAQ18.1
697690Ethernet cDAQ appears to crash on DAQmx watchdog expiration when DSA task is running18.1
689440Time trigger uses default time in multi-device tasks when explicitly committed18.1
688114When running DAQmx frequency tasks in NI MAX on a NI 9401, the task hangs indefinitely when no signal is connected18.1
680182Channel Calibration Wizard forgets Acquisition Attributes when importing NI MAX database18.1
680179PXIe-4300 with TB-4300C ignores custom scale after applying channel calibration18.1
673712DAQmx Start:Terminal property does not return segment number on cDAQ-9179 when user specifies timing engine18.1
659756Explicit commit on a finite task causes continuous acquisition with USB-600118.1
677161Sync lock loss error occurs on TSN enabled devices18.0
682682Network CDAQ fails self-test, reset, and reserve with Error -5200318.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).