July 2011
Thank you for using NI-DAQmx, version 9.4. The readme contains the following main sections:
The following features were added in NI-DAQmx 9.4:
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.
The following issues were fixed in NI-DAQmx 9.4:
| CAR ID | Summary |
|---|---|
| 168864 | Device identifier is not an input to the DAQ Assistant |
| 194507 | Timestamp does not account for Simultaneous Sample and Hold (SSH) on the NI SCXI-1520 |
| 204330 | Wait Until Done on CO ticks task ends task too early at low frequencies |
| 214307 | C Series calibration date and temperature cannot be updated without performing an adjustment |
| 242128 | Unable to reconfigure task from software-timed back to hardware-timed |
| 243644 | 100% CPU Usage On X Series with DAQmx Write in loop on counter output |
| 280166 | Enabling change detection for a DO task results in Error -88700 |
| 281228 | Error -200361 with USB-6009 and Windows 7 PCs |
| 281366 | Cannot post measurements from an NI SCXI-1600 DAQmx global channel to OPC server or other distributed variable |
| 282875 | USB-6008 and USB-6009 Sometimes Return Error -200361 Using USB Hubs with Windows 7 |
| 285656 | Cannot use large number of NI-DAQmx scales in MAX |
| 286530 | RSE greyed out in MAX with an NI 9263 in an NI cDAQ-9172 |
| 292905 | No waveform attributes returned on DAQmx Read timeout |
| 297667 | Sample complete event callback does not execute with hardware-timed single point on X Series |
| 297754 | Performing a shunt calibration on an NI SCXI-1121 sometimes throws error -200077 |
| 298367 | Ethernet and/or wireless DAQ devices can cause system crash during network connection outages |
| 299441 | Non-buffered change detection does not work when using change detection event on STC3 devices |
| 299887 | Changing the bridge configuration (AI.BridgeCfg) on an NI 9219 after channel creation returns Error -50003 |
| 300017 | Reconfiguration of an NI 4461/2 Master-Slave Sync Task Can Cause a Loss in Synchronization of the Sample Clocks |
| 300305 | NI USB-4431 AO briefly holds last amplitude when reconfiguring AI |
| 301517 | Reserving Digital Output Task on NI 9401 Before Writing or Configuring Timing Causes Blue Screen |
| 302700 | Error -89000 when registering an "every N samples event/callback" in 64-bit compilers running on a 64-bit OS on NI 6533/34 devices |
| 303896 | First sample of buffered digital output may be incorrect with cDAQ |
This section covers known issues and considerations specific to NI-DAQmx.
The NI cDAQ-918x/919x configuration, both with the NI Web-based configuration and in MAX, requires Microsoft Silverlight. Silverlight is installed with NI-DAQmx and is available from microsoft.com/silverlight. To find out more about using Microsoft Silverlight with NI software, visit Notice Regarding Microsoft Silverlight Installation and Redistribution.
The 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. 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 is available for the NI cDAQ-918x/919x 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.
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 ni.com/info 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.
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).
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.
Single-point reads and writes do not respond to the Abort Execution button in LabVIEW.
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.
The maximum number of channels you can have in a task created with the DAQ Assistant is 4096 channels.
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.
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.
Not all NI-DAQmx events will fire if the conditions for the event occur more quickly than the system can process.
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.
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.
This section covers changes in NI-DAQmx functionality.
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.
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:
To learn more, refer to Duplicate Count Prevention in the NI-DAQmx help.
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.
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-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 ni.com/calibration.
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.
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.
The following operating systems are supported in NI-DAQmx 9.4:
For OS-specific device support information, refer to ni.com/support/daq/versions.
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 ni.com/info 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.4 supports Phar Lap only with the LabVIEW Real-Time Module 8.6 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.com/downloads.
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.
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.6.x (including 2009 and later) |
| LabVIEW Real-Time Module | 8.6.x and later (including 2009 and later) |
| LabWindows/CVI | 8.5 and later (including 2009 and later) |
| LabWindows/CVI Real-Time Module | 8.5 and later (including 2009 and later) |
| Measurement Studio | 8.5 and later (including 2009 and later) |
| LabVIEW SignalExpress | 2.5 and later (including 2009 and later) |
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.
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) |
2005 | |
| .NET Framework 3.5 Languages (C# and Visual Basic.NET) |
2008 | |
| .NET Framework 4.0 Languages (C# and Visual Basic.NET) |
20104 | |
| Visual Basic 61 | 6 | |
| 1 NI-DAQmx includes limited support for Visual Basic 6 and Visual Studio C++ MFC. For more information, visit ni.com/info 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 ni.com/downloads.
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 ni.com/info and enter the info code ex6rzd.
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 ni.com/support/daq/versions.
For MXI-3 and MXI-4 OS-specific support information, refer to ni.com/kb and search for KnowledgeBase entry 45MA9LF7.
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 ni.com/support/daq/versions.
For MXI-3 and MXI-4 OS-specific support information, refer to ni.com/kb and search for KnowledgeBase entry 45MA9LF7.
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 | ✓ | ||
| NI 6376 | ✓ | ||
| NI 6378 | ✓ |
The following M Series DAQ devices are supported:
| Device | PCI | PCIe | PXI | PXIe | USB |
|---|---|---|---|---|---|
| NI 6210/11/12/15/16/18 | ✓ | ||||
| NI 6220 | ✓ | ✓ | |||
| NI 6221 | ✓ | ✓ | ✓ | ||
| NI 6224 | ✓ | ✓ | |||
| NI 6225 | ✓ | ✓ | ✓ | ||
| NI 6229 | ✓ | ✓ | ✓ | ||
| NI 6230/32/33/36/38/39 | ✓ | ✓ | |||
| NI 6250 | ✓ | ✓ | |||
| NI 6251 | ✓ | ✓ | ✓ | ✓ | ✓ |
| NI 6254 | ✓ | ✓ | |||
| NI 6255 | ✓ | ✓ | ✓ | ||
| NI 6259 | ✓ | ✓ | ✓ | ✓ | ✓ |
| NI 6280 | ✓ | ✓ | |||
| NI 6281 | ✓ | ✓ | ✓ | ||
| NI 6284 | ✓ | ✓ | |||
| NI 6289 | ✓ | ✓ | ✓ |
The following E Series DAQ devices are supported.
| Device | PCMCIA | PCI | PXI |
|---|---|---|---|
| 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 | ✓ | ✓ | |
| NI PCI-MIO-16E-1 | ✓ | ||
| NI PCI-MIO-16E-4 | ✓ | ||
| NI PCI-MIO-16XE-10 | X | ✓ | |
| NI PCI-MIO-16XE-50 | X | ✓ |
The following S Series DAQ devices are supported:
| Device | PCI | PXI | PXIe |
|---|---|---|---|
| NI 6110 | ✓ | ||
| NI 6111 | ✓ | ||
| NI 6115 | ✓ | ✓ | |
| NI 6120 | ✓ | ✓ | |
| NI 6122 | ✓ | ✓ | |
| NI 6123 | ✓ | ✓ | |
| NI 6124 | ✓ | ||
| NI 6132 | ✓ | ✓ | |
| NI 6133 | ✓ | ✓ | |
| NI 6143 | ✓ | ✓ | |
| NI 6154 | ✓ |
The following SC Express devices are supported:
| Device | PXIe |
|---|---|
| NI 4300 | ✓ |
| NI 4330 | ✓ |
| NI 4331 | ✓ |
| NI 4353 | ✓ |
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 92112 | ✓ | ✓ | ✓ | ✓ |
| NI 9213 | ✓ | ✓ | ✓ | ✓ |
| NI 9214 | ✓ | |||
| NI 92152 | ✓ | ✓ | ✓ | ✓ |
| NI 9217 | ✓ | ✓ | ||
| NI 9219 | ✓ | ✓ | ✓ | ✓ |
| NI 9221 | ✓ | ✓ | ✓ | |
| NI 9222 | ✓ | |||
| NI 9223 | ✓ | |||
| NI 9225 | ✓ | ✓ | ||
| NI 9227 | ✓ | ✓ | ||
| NI 9229 | ✓ | ✓ | ✓ | |
| NI 9232 | ✓ | |||
| NI 9233 | ✓ | ✓ | ✓ | |
| NI 9234 | ✓ | ✓ | ✓ | ✓ |
| NI 9235 | ✓ | ✓ | ||
| NI 9236 | ✓ | ✓ | ||
| NI 9237 | ✓ | ✓ | ✓ | ✓ |
| NI 9237 (DSUB) | ✓ | ✓ | ||
| NI 9239 | ✓ | ✓ | ✓ | |
| NI 9263 | ✓ | ✓ | ✓ | |
| NI 9264 | ✓ | ✓ | ✓ | |
| NI 9265 | ✓ | ✓ | ✓ | |
| NI 9269 | ✓ | ✓ | ||
| NI 9375 | ✓ | |||
| 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. | ||||
| 2The NI USB-9211A and NI USB-9215A (C Series modules with a bundled NI USB-9162) are supported in NI-DAQmx. The NI USB-9211 and NI USB-9215 (C Series modules with a bundled NI USB-9161) are not supported in NI-DAQmx. | ||||
The following CompactDAQ chassis are supported:
| CompactDAQ Chassis | Ethernet | USB | Wireless |
|---|---|---|---|
| NI cDAQ-9171 | ✓ | ||
| NI cDAQ-9172 | ✓ | ||
| NI cDAQ-9174 | ✓ | ||
| NI cDAQ-9178 | ✓ | ||
| NI cDAQ-9181 | ✓ | ||
| NI cDAQ-9188 | ✓ | ||
| NI cDAQ-9191 | ✓ | ✓ |
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 | ✓ | ✓ |
The following digital I/O devices are supported.
| Device | DAQCard | PCI | PCIe | PXI | PXIe | USB |
|---|---|---|---|---|---|---|
| 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 | ✓ | ✓ | ||||
| NI DIO-24 | ✓ | |||||
| NI DIO-32HS | ✓ | |||||
| NI DIO-96 | ✓ | |||||
| 1Does not have NI-DAQmx simulated device capability. | ||||||
The following TIO series devices are supported:
| Device | PCI | PXI |
|---|---|---|
| NI 6601 | ✓ | |
| NI 6602 | ✓ | ✓ |
| NI 6608 | ✓ | |
| NI 6624 | ✓ | ✓ |
The following DSA devices are supported:
| Device | PCI | PXI | PXIe | USB |
|---|---|---|---|---|
| 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 | ✓ |
The following SC Series DAQ devices are supported:
| Device | PXI |
|---|---|
| NI 4200 | ✓ |
| NI 4204 | ✓ |
| NI 4220 | ✓ |
| NI 4224 | ✓ |
The following switches are supported:
| Device | PCI | PXI | PXIe |
|---|---|---|---|
| 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 2543 | ✓ | ✓ | |
| 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 2812 | ✓ | ||
| NI 2813 | ✓ | ||
| NI 2814 | ✓ | ||
| NI 2815 | ✓ | ||
| NI 2816 | ✓ | ||
| NI 2817 | ✓ |
The following SCXI Chassis are supported:
The following SCXI modules are supported:
The following TEDS devices are supported:
The following academic devices are supported:
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 | ✓ | ||
| SensorDAQ | ✓ |
The following low-cost USB devices are supported. These do not have NI-DAQmx simulated device capability:
| Device | USB |
|---|---|
| NI 6008 | ✓ |
| NI 6009 | ✓ |
| NI TC01 | ✓ |
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 Use | RAM | Processor |
|---|---|---|
| Development | 1 GB | Pentium IV or later |
| Deployment | 256 MB | Pentium III/Celeron 600 MHz or Equivalent |
Some NI components require Microsoft Silverlight. If you do not have Silverlight installed on your computer, but you do have Internet access, you can download the installer from Microsoft at http://www.microsoft.com/silverlight/. If you do not have Internet access, you can install Silverlight from this NI distribution media.
You may not use any H.264/MPEG-4 AVC and/or VC-1 technology or codecs included in or with Microsoft Silverlight software which may be provided by NI as Third Party Software, including for the purpose of encoding or decoding video in compliance with, or making use of, the H.264/AVC visual standard or the VC-1 video standard.
If you create and distribute software applications that contain NI components that also use Microsoft Silverlight, you may be authorized to include Silverlight in installers or on physical media as long as you comply with certain requirements. Refer to the notice.txt file in the <National Instruments>\_Legal Information\Microsoft Silverlight 4.0 directory or the NI standard End User License Agreement (EULA) located in the <National Instruments>\Common\MDF\EULADepot\NIReleased directory for more information.
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, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks 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 ni.com/patents.