JavaScript (active content) is disabled. For all content to be accessible, you must enable JavaScripts in your browser.

NI-DAQmx 9.3 Readme

NI-DAQmx 9.3 Readme

February 2011

Thank you for using NI-DAQmx, version 9.3. The readme contains the following main sections:

New Features Added in NI-DAQmx 9.3

The following features were added in NI-DAQmx 9.3:

Important Notice: Microsoft Hotfix for USB DAQ Devices and Windows XP

If you are using NI-DAQmx with a USB DAQ device on Windows XP, you should install the Microsoft hotfix reported in Microsoft Knowledge Base 969238.

Fixed Issues

The following issues were fixed in NI-DAQmx 9.3:

CAR ID Summary
106314 Shunt cal and offset null in a strain task do not work properly if a custom scale is selected
187820 NI USB-4431 may output stale data at the start of a task if the sample rate has changed from the last task's rate
206282 Starting an AO task on an NI USB-4431 causes a glitch on the channel
235725 The NI WLS-9163 may experience connection issues with international wireless routers
239962 Starting an acquisition using multiple NI 9219 devices takes 10-20 seconds
242484 Explicitly committing a task with events on a simulated cDAQ chassis can result in a system crash
242611 NI 9203 may return improperly scaled data with an NI 9174, 9178, or 9188 chassis when mixing bipolar and unipolar channels
245504 NI USB-4431 doesn't support DAQmxGetWriteTotalSampPerChanGenerated property
246579 DAQ Assistant hangs when creating a digital NI-DAQmx task from a LabVIEW Project
246651 Master Timebase cannot be shared between tasks in a cDAQ chassis
248436 Using the DAQ Assistant to calibrate a strain channel on the NI 9235/6 gives error -200077
249685 Scaled units for acceleration measurement type should support in/s^2
250609 NI-DAQmx Test Panels Are Taller Than 600 Pixels
251790 NI LabVIEW SignalExpress 2010 freezes when generating a calibration report
252395 Repeatedly creating, starting, stopping, and clearing AO tasks on an NI 4461 may cause it to output full scale noise
252811 Setting timeout to -1 can timeout with a Frequency Measurement DAQmx Global Virtual Channel
253284 NI USB-4431 AO tasks do not stop generating at task stop when "Allow Regeneration" and "Use Only Onboard Memory" are enabled
255249 NI USB-4431/32 inputs invert the polarity of out of range voltage signals
277095 Value of DAQmx Channels to Read property changes when you modify other NI-DAQmx properties
278121 NI WLS-9163 may become unresponsive during long-term use
278249 NI USB-4431 AO to AI synchronization may vary when the unit is power cycled
278838 NI USB-4431 may output data from previous tasks if continuous AO tasks are stopped and restarted
279016 NI USB X Series digital I/O lines glitch on Windows restart
280611 NI USB-4431 may not update the output for short finite output tasks
281238 In an NI 9172, on-demand digital output can tri-state other lines on the same NI 9401
282045 Error -200152 may be reported repeatedly for NI ENET-9163 or NI WLS-9163 devices
282383 C Series modules used with the NI WLS/ENET-9163 may return corrupted data in adverse network conditions

NI-DAQmx Considerations

This section covers known issues and considerations specific to NI-DAQmx.

Microsoft Silverlight Required for NI cDAQ-918x Configuration

The NI cDAQ-918x configuration, both with the NI Web-based configuration and in MAX, requires Microsoft Silverlight. Silverlight is available from To find out more about using Microsoft Silverlight with NI software, visit and enter the info code Silverlight.

NI cDAQ-918x Works Incorrectly if Path Includes Non-ASCII (Multi-Byte) Characters

The NI cDAQ-918x 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. 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.

Web-Based Configuration for the NI cDAQ-918x Available Only for Windows and Macintosh

Web-based configuration is available for the NI cDAQ-918x by accessing the device in a Microsoft Silverlight-enabled Web browser via its host name or IP address. This support is only accessible from Windows-based or Macintosh-based systems. Refer to the chassis user guide for more information.

Firmware Update Required to Use NI cDAQ-9188 in NI-DAQmx 9.3

You must update the firmware on the NI cDAQ-9188 to use it with NI-DAQmx 9.3. Firmware files for Network DAQ devices are named ni<model number>fw.cfg (for instance, ni9188fw.cfg). You can obtain the latest version of firmware in the Firmware directory on the NI-DAQmx media or by going to

Required Firmware Updates for Network DAQ Devices in NI-DAQmx

If you receive Error -201340, you need to update the firmware on your Network DAQ device. Firmware files for Network DAQ devices are named ni<model number>fw.cfg (for instance, ni9188fw.cfg). You can obtain the version of firmware supported by your version of NI-DAQmx by going to and entering the info code exkpzt. If you installed NI-DAQmx from a DVD, you can also find a compatible version in the Firmware directory on that DVD.

New Error Returned when Loading an Invalid Device Name

In NI-DAQmx 9.3 and later, an invalid device name returns Error –200220, kErrorInvalidDeviceID, instead of Error –200170, kErrorPhysicalChanDoesNotExist. This change has no impact on newly created applications but can affect existing applications if the applications are performing error checking by looking for the specific error number (–200170).

NI USB-4431 Specifications Changes

The NI USB-4431 specifications have changed. The AO offset is specified with a higher level of uncertainty. The analog inputs and outputs also have a higher gain uncertainty than previously specified. In particular, sample rates of less than 40 kHz result in an accuracy drop. The newest version of the NI USB-443x Specifications reflects these changes. A separate document, Notice of Specification Change - USB 4431, details these changes as well.

Aborting Single-Point Reads and Writes in LabVIEW

Single-point reads and writes do not respond to the Abort Execution button in LabVIEW.

Configuring MAX Strain Tasks

MAX strain tasks do not support configuring terminal configurations. By default, the configuration in MAX is differential. For the NI SC-2043-SG, the terminal configuration is NRSE. To avoid configuration issues, use the NI-DAQmx API to create the task.

DAQ Assistant Maximum Channel Count

The maximum number of channels you can have in a task created with the DAQ Assistant is 4096 channels.

NI DAQCard-6715 Analog Output

Hardware-timed single-point mode and hardware-timed nonbuffered mode are nonfunctional. Your application is using hardware-timed nonbuffered mode if you have set up a sample clock and a buffer size of 0, or set up a sample clock, but do not begin writing until after you start the task. All other waveform and static analog output modes work as expected.

NI ENET/WLS-9215 Times Out Unexpectedly

On the NI ENET/WLS-9215, an unexpected timeout can occur in continuous tasks using an external or very slow sample clock. The last sample may not be returned until the next sample clock pulse. To avoid the timeout, increase the timeout time (to allow the next sample clock pulse to occur) or acquire an even number of samples.

NI-DAQmx Events

Not all NI-DAQmx events will fire if the conditions for the event occur more quickly than the system can process.

Samples Not Acquired on NI 660x or NI 6624 Devices

When using pulse width, semi-period or two-edge separation buffered measurements with the NI 660x and NI 6624 on counters 0 and 1, some samples may not be acquired under certain circumstances.

Microsoft Windows 7/Vista and Visual Studio C++, C#, Visual Basic .NET, and ANSI C Examples

Running certain applications on Microsoft Windows 7/Vista requires administrator privileges, because the application name contains keywords such as setup, update, or install. To avoid this problem, you must add an additional manifest to the application that specifies the privileges required to run the application. Some NI-DAQmx ANSI C, Measurement Studio Visual C++, C#, and Visual Basic .NET examples include these keywords. Therefore, some examples for these application development environments include an additional manifest file that you must embed in the example executable.

In ANSI C, Measurement Studio Visual C++ , C#, and Visual Basic .NET, the manifest file is named [ExampleName].exe.manifest, where [ExampleName] is the NI-provided example name. The steps for embedding an example varies depending on the programming language. Refer to the comments included with affected examples for additional information.

Compiling Visual Studio 2005 examples can generate the following warning: manifest authoring warning 81010002: Unrecognized Element "requestedPrivileges" in namespace "urn:schemas-microsoft-com:asm.v3". For more information, refer to the Microsoft Feedback web page. This warning does not affect example execution and can be ignored. This warning happens because of the version of mt.exe that is shipped with Visual Studio 2005. The mt.exe tool embeds the additional manifest in the example executable.

Important: Performing these steps on Windows XP Service Pack 2 (SP2) may cause your computer to restart when you run the application. Refer to the Microsoft Knowledge Base entry for more information. To avoid a computer restart, build your application using Visual Studio 2005 SP1.

Upgrade Considerations

This section covers changes in NI-DAQmx functionality.

DAQmx Is Read or Write Late Obsoleted

The existing DAQmx Is Read or Write Late function/VI has been obsoleted and no longer has any effect. Applications that must check whether they are maintaining real-time behavior have two options. For the strictest checking, use the Wait for Next Sample Clock function/VI. Refer to your API reference help, such as the LabVIEW Help or the NI-DAQmx C Function Reference Help, for more information on this function/VI. To check only whether the application misses any analog input samples, set the Report Missed Samples property to True on the analog input task. In LabVIEW, the Report Missed Samples property is in the Real Time property node. For more details, National Instruments strongly recommends that you read the document referred to by the Wait for Next Sample Clock function/VI.

Duplicate Count Prevention Defaults

As of NI-DAQmx 7.4, the default setting for the duplicate count prevention attribute/property on M Series and TIO-based counters has been changed. This change affects all input counter operations, with the exception of single-point edge counting and position measurements. Duplicate count prevention is now on by default as long as the following conditions are met:

  1. The duplicate count prevention attribute/property has not been explicitly set.
  2. The selected counter timebase source is not set to an internal timebase.
  3. The prescaler attribute/property has not been set.
  4. The counter output event has not been configured.

To learn more, refer to Duplicate Count Prevention in the NI-DAQmx help.

Existing .NET Project Produces Build Errors

If you are using NI-DAQmx with a .NET language, an existing project can produce build errors from an assembly that is not referenced. To eliminate this error, add a reference to the NationalInstruments.Common assembly to the project.

Multichannel SCXI Convert Clock Default Rate Change in NI-DAQmx 8.5

Starting in NI-DAQmx 8.5, a delay of 20 µs was added to the fastest possible channel conversion rate on an SCXI chassis connected to a 16-bit or 18-bit E or M Series device. If a sample rate is set fast enough to require a convert clock rate greater than the default rate, warning 200011 is generated, informing the user that the accuracy of the measurement might be compromised. However, since this is a warning, the convert clock used is based on the rate needed by the sample clock set by the user (that is, convert clock = sample clock * number of channels).

For SCXI chassis containing a module with track-and-hold circuitry, 10 µs of padding is now added to the fastest possible conversion rate when connected to a 12-bit E Series device.

These changes ensure the most accurate data is being acquired. However, if the effect on the performance due to this change is too great (such as on an RT system using hardware-timed single point in a control loop), then the convert clock rate attribute can be explicitly set, overriding the default rate.

This change affects only multichannel acquisitions.

In versions prior to NI-DAQmx 8.5, only 10 µs of delay was added to the fastest possible channel conversion rate on an SCXI chassis without a track-and-hold module connected to any DAQ device. In these versions of NI-DAQmx, no warning was generated when the sample rate needed a faster convert clock than was chosen by default. When an SCXI chassis with a track-and-hold module was present, the convert clock rate selected was the fastest possible rate that the DAQ device can handle, up to 333 kHz.

NI PCI-6704 and PXI-6704 Current Output Accuracy

NI-DAQmx 8.3 changes the algorithm used to scale the 20 mA current outputs of the NI 6704 to a method that matches the behavior of Traditional NI-DAQ (Legacy). Previous versions of the NI-DAQmx driver use a second method.

The effect of the change is that when NI-DAQmx programs the 6704 to output current, the actual current level of the 6704 is 10 µA higher with NI-DAQmx 8.3 compared to previous versions of NI-DAQmx. The actual current output with NI-DAQmx 8.3 is the same compared to Traditional NI-DAQ (Legacy) drivers. This change has no effect on the voltage outputs of the 6704.

Because of this change, NI recommends that you externally calibrate NI 6704 devices with NI-DAQmx 8.3 (or later) before using devices with the NI-DAQmx 8.3 (or later) driver. NI 6704 devices that ship with NI-DAQmx 8.3 have already been calibrated with NI-DAQmx 8.3. For other NI 6704 devices, refer to the manual calibration procedure available at

USB-9xxx Devices

Unplug your USB-9xxx and plug it back in or power the USB device down and up after upgrading NI-DAQmx. If the USB-9xxx is connected to a USB hub, make sure to disconnect the USB-9xxx from the hub, not the hub from the computer. Disconnecting power from the USB device causes installed devices to load the correct version of the firmware.

Virtual TEDS Data for the USB-9233/9237

If you connect hardware TEDS to USB-9233/9237 channels configured with virtual TEDS, the virtual TEDS will be replaced with hardware TEDS data after upgrading to NI-DAQmx 8.6 or later.

Software Support in NI-DAQmx 9.3

Operating System Support

The following operating systems are supported in NI-DAQmx 9.3:

For OS-specific device support information, refer to

Note  Support for Windows Server 2003 R2 may require disabling physical address extensions (PAE). To learn how this might affect your use of Windows Server 2003 and what actions you might have to take, visit and enter the info code PAESupport.

Caution  If you plan to perform an upgrade of your system from a prior version of Microsoft Windows to Microsoft Windows Vista, you are required to uninstall all National Instruments software prior to performing the upgrade. After the upgrade has been completed, you can reinstall your National Instruments software.

NI-DAQmx 9.3 supports Phar Lap only with the LabVIEW Real-Time Module 8.5 and later.

Windows 2000 users must use NI-DAQmx 9.1.1 or earlier.

To find and download an earlier version of NI-DAQmx that supports other operating systems, refer to

NI-DAQmx does not support guest accounts on Windows 7/Vista/XP. You must log into an administrative or user account to use NI-DAQmx on these OSes.

NI Application Software Support

The following table lists the NI application software versions supported by NI-DAQmx. If you are not using NI application software, refer to Microsoft Visual Studio Support.

In NI-DAQmx 8.6 and prior, when you add the DAQ Component as a new item to your Visual Studio 2005 project, the DAQ Component is located in the Measurement Studio folder and the Visual Basic Items or Visual C# Project Items folders. In NI-DAQmx 8.7 and later, the DAQ Component is located only in the Visual Basic Items or Visual C# Project Items folder and named NI-DAQ Component.

NI Application Software Versions Supported by NI-DAQmx and the DAQ Assistant
LabVIEW 8.5.x, 8.6.x, 2009, and 2010
LabVIEW Real-Time Module 8.5.x and later (including 2009 and later)
LabWindows/CVI 8.1 and later (including 2009 and later)
LabWindows/CVI Real-Time Module 8.1 and later (including 2009 and later)
Measurement Studio 8.1 and later (including 2009 and later)
LabVIEW SignalExpress 2.x and later (including 2009 and later)

Measurement Studio Examples

The directories that the Measurement Studio examples install to depends on which component is installed, the version of Visual Studio or the .NET Framework the example supports, the version of Measurement Studio installed, and the operating system. For detailed information on examples for Measurement Studio, refer to Where To Find Examples in the NI Measurement Studio Help.

Microsoft Visual Studio Support

The following table lists the programming languages and Microsoft Visual Studio versions supported by NI-DAQmx.

Programming Language Visual Studio Versions Supported by NI-DAQmx
ANSI C 2003, 2005, 2008, and 2010
Visual C++ MFC1 20052 and 20083
.NET Framework 2.0 Languages
(C# and Visual Basic.NET)
.NET Framework 3.5 Languages
(C# and Visual Basic.NET)
.NET Framework 4.0 Languages
(C# and Visual Basic.NET)
Visual Basic 61 6
1 NI-DAQmx includes limited support for Visual Basic 6 and Visual Studio C++ MFC. For more information, visit and enter the info code daqmxvstudio.
2 Requires Measurement Studio 8.0.1 — Measurement Studio 2009
3 Requires Measurement Studio 8.6 — Measurement Studio 2009
4 With Windows XP, Service Pack 3 or later is required

Earlier versions of NI-DAQmx support other application software and language versions. To find and download an earlier version of a driver, refer to

If you are using the DAQmx .NET Library, the .NET 2.0 Framework, .NET 3.5 Framework, or .NET 4.0 Framework is required.

NI-DAQmx 9.2 is the last release that includes full feature support for Visual C++ MFC 2005 and 2008.

If you are using the .NET Framework 1.1 or Visual C++ MFC 2003, you must use NI-DAQmx 9.1.5 or earlier. For more information on NI-DAQmx support for .NET Framework 1.1 or Visual C++ MFC 2003, including considerations for users upgrading from NI-DAQmx 9.1.5 or earlier, visit and enter the info code ex6rzd.

Device Support in NI-DAQmx

The following lists detail the devices supported in NI-DAQmx. Device support is divided into the following categories:

For OS-specific device support information, refer to

For MXI-3 and MXI-4 OS-specific support information, refer to and search for KnowledgeBase entry 45MA9LF7.

Devices Supported in NI-DAQmx

The following lists detail the devices supported in NI-DAQmx. Device support is divided into the following categories:

Note  In the device support tables that follow, a ✓ indicates that the device is supported, a blank cell indicates that the device either does not exist or is not supported in NI-DAQmx, and an X indicates that the device is no longer supported in NI-DAQmx.

For OS-specific device support information, refer to

For MXI-3 and MXI-4 OS-specific support information, refer to and search for KnowledgeBase entry 45MA9LF7.

X Series DAQ

The following X Series DAQ devices are supported:

Device PCIe PXIe USB
NI 6320
NI 6321
NI 6323
NI 6341
NI 6343
NI 6351
NI 6353
NI 6356
NI 6358
NI 6361
NI 6363
NI 6366
NI 6368

M Series DAQ

The following M Series DAQ devices are supported:

NI 6210/11/12/15/16/18
NI 6220
NI 6221
NI 6224
NI 62251
NI 6229
NI 6230/32/33/36/38/39
NI 6250
NI 6251
NI 6254
NI 62551
NI 6259
NI 6280
NI 6281
NI 6284
NI 6289
1USB versions do not have NI-DAQmx simulated device capability.

E Series DAQ

The following E Series DAQ devices are supported.

NI 6023E
NI 6024E
NI 6025E
NI 6030E
NI 6031E
NI 6032E/33E/34E/35E
NI 6036E
NI 6040E
NI 6052E
NI 6062E
NI 6070E
NI 6071E

S Series DAQ

The following S Series DAQ devices are supported:

NI 6110
NI 6111
NI 6115
NI 6120
NI 6122
NI 6123
NI 6124
NI 6132
NI 6133
NI 6143
NI 6154

SC Express

The following SC Express devices are supported:

Device PXIe
NI 4300
NI 4330
NI 4331
NI 4353

C Series, Network DAQ, and USB DAQ

The following C Series, Network DAQ, and USB DAQ devices are supported:

Device CompactDAQ Chassis1 Legacy Chassis and Carriers
NI ENET/WLS-9163 NI USB-9162 NI cDAQ-9172
NI 9201
NI 9203
NI 9205
NI 9206
NI 9207
NI 9208
NI 9211
NI 9211A
NI 9213
NI 9214
NI 9215
NI 9215A
NI 9217
NI 9219
NI 9221
NI 9222
NI 9223
NI 9225
NI 9227
NI 9229
NI 9233
NI 9234
NI 9234B
NI 9235
NI 9236
NI 9237
NI 9239
NI 9263
NI 9264
NI 9265
NI 9269
NI 9401
NI 9402
NI 9403
NI 9411
NI 9421
NI 9422
NI 9423
NI 9425
NI 9426
NI 9435
NI 9472
NI 9474
NI 9475
NI 9476
NI 9477
NI 9478
NI 9481
NI 9485
1Does not include the NI cDAQ-9172.

CompactDAQ Chassis

The following CompactDAQ chassis are supported:

Device CompactDAQ Chassis
NI cDAQ-9171
NI cDAQ-9172
NI cDAQ-9174
NI cDAQ-9178
NI cDAQ-9181
NI cDAQ-9188

AO Series

The following AO Series devices are supported:

Device DAQCard PCI PXI
NI 6703
NI 6704
NI 6711
NI 6713
NI 6715
NI 6722
NI 6723
NI 6731
NI 6733

Digital I/O

The following digital I/O devices are supported.

NI 65011
NI 6503
NI 6508
NI 6509
NI 6510
NI 6511
NI 6512
NI 6513
NI 6514
NI 6515
NI 6516
NI 6517
NI 6518
NI 6519
NI 6520
NI 6521
NI 6525
NI 6527
NI 6528
NI 6529
NI 6533 X
NI 6534
NI 6535
NI 6536
NI 6537
1Does not have NI-DAQmx simulated device capability.

TIO Series

The following TIO series devices are supported:

Device PCI PXI
NI 6601
NI 6602
NI 6608
NI 6624

Dynamic Signal Acquisition (DSA)

The following DSA devices are supported:

NI 4431
NI 4432
NI 4461
NI 4462
NI 4472/B
NI 4474
NI 4492
NI 4495
NI 4496
NI 4497
NI 4498
NI 4499

SC Series DAQ

The following SC Series DAQ devices are supported:

Device PXI
NI 4200
NI 4204
NI 4220
NI 4224


The following switches are supported:

NI 4021
NI 2501
NI 2503
NI 2510
NI 2512
NI 2514
NI 2515
NI 2527
NI 2529
NI 2530
NI 2531
NI 2532
NI 2533
NI 2534
NI 2535
NI 2536
NI 2545
NI 2546
NI 2547
NI 2548
NI 2549
NI 2554
NI 2555
NI 2556
NI 2557
NI 2558
NI 2559
NI 2564
NI 2565
NI 2566
NI 2567
NI 2568
NI 2569
NI 2570
NI 2571
NI 2575
NI 2576
NI 2584
NI 2585
NI 2586
NI 2590
NI 2591
NI 2593
NI 2594
NI 2595
NI 2596
NI 2597
NI 2598
NI 2599
NI 2800
NI 2810
NI 2811
NI 2815
NI 2816

SCXI Chassis

The following SCXI Chassis are supported:

NI 1010
NI 1011
NI SCXI-1001

SCXI Modules

The following SCXI modules are supported:

TEDS Interface

The following TEDS devices are supported:

Academic Devices

The following academic devices are supported:

Legacy DAQ Devices

The following legacy DAQ devices are supported. These do not have NI-DAQmx simulated device capability:

Device DAQ Pad PCI USB
NI DAQPad-6015
NI DAQPad-6016
NI PCI-6013
NI PCI-6014

Low-Cost USB

The following low-cost USB devices are supported. These do not have NI-DAQmx simulated device capability:

Device USB
NI 6008
NI 6009

Devices Not Supported in NI-DAQmx on Windows 7/Vista

The following devices are not supported in NI-DAQmx on Windows 7/Vista (32-bit and 64-bit versions):

The following devices are supported in NI-DAQmx on the 32-bit versions of Windows 7/Vista. They are not supported on the 64-bit versions of Windows 7/Vista:

System Requirements

System Use RAM Processor
Development 1 GB Pentium IV or later
Deployment 256 MB Pentium III/Celeron 600 MHz or Equivalent


The mDNSResponder notice is installed with NI-DAQmx. By default, the notice is installed at Program Files\National Instruments\Shared\mDNS Responder\mDNS Responder FOSS notices.doc.


Copyright 2003–2011 National Instruments. All rights reserved.

Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.

National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.


CVI, LabVIEW, National Instruments, NI,, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at for other National Instruments trademarks.

The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.

Other product and company names mentioned herein are trademarks or trade names of their respective companies.


For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at