Copyright 2008 National Instruments. All rights reserved. For patents covering National Instruments products, refer to ni.com/patents.
CVI™, LabVIEW™, Measurement Studio™, National Instruments™, NI™, ni.com™, and NI-DAQ™ are trademarks of National Instruments Corporation.
Product and company names mentioned herein are trademarks or trade names of their respective companies.
Thank you for using NI-DAQmx Base 3.2.
The NI-DAQmx Base 3.2 software contains LabVIEW and C Application Programming Interfaces (API) that allow you to create applications for your device.
NI-DAQmx Base 3.2 supports the following:
The Readme contains the following main sections:
The following sections provide a NI-DAQmx and NI-DAQmx Base overview and include information about choosing the right API for the device and application.
NI-DAQmx is the latest NI-DAQ driver with new VIs and functions and development tools for programming measurement devices. Install and use NI-DAQmx if the following situations apply:
Install and use NI-DAQmx Base 3.2 if the following situations apply:
Install and use NI-DAQmx Base 3.1 if the following situations apply:
Install and use NI-DAQmx Base 2.2 if the following situations apply:
Install and use NI-DAQmx Base 2.1 if the following situations apply:
Install and use NI-DAQmx Base 2.0 if the following situations apply:
Install and use NI-DAQmx Base 1.5.1 for RTX if the following situations apply:
Install and use NI-DAQmx Base 1.0.x if the following situations apply:
The following table lists the application software versions supported by NI-DAQmx Base 3.2:
| NI Application Software | Versions Supported by NI-DAQmx Base 3.2 |
|---|---|
| LabVIEW | 8.2, 8.2.1, 8.5, 8.5.1, 8.6 |
| LabVIEW Mobile Module | 8.6 |
| LabVIEW Touch Panel Module for Windows CE | 8.6 |
The following table lists the language versions supported by NI-DAQmx Base 3.2:
| Programming Language | Versions Supported by NI-DAQmx Base 3.2 |
|---|---|
| ANSI C | Windows Desktop only |
Device support is divided into the following categories:
The following tables lists devices supported by NI-DAQmx Base 3.2 for Windows Mobile:
| Devices | Description |
|---|---|
| NI DAQCard 6024E | 200 kS/s, 12-bit, 16 AI channels, two AO channels, 8 DIO lines, two counter/timers |
| NI DAQCard 6062E | 500 kS/s, 12-bit, 16 AI channels, two AO channels, 8 DIO lines, two counter/timers |
| NI DAQCard 6036E | 200 kS/s, 16-bit, 16 AI channels, two AO channels, 8 DIO lines, two counter/timers |
| NI DAQCard AI-16E-4 (6041E) | 500 kS/s, 12-bit, 16 AI channels, 8 DIO lines, two counter/timers |
| NI CF-6004 | 200kS/s, 14-bit, 4 AI channels, 4 DIO lines |
| NI USB-6008 | 12-bit, 10 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6008 OEM | 12-bit, 10 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6009 | 14-bit, 48 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6009 OEM | 14-bit, 48 kS/s, 8 AI channel, 12 DIO line, 1 event counter device |
| NI USB-6501 | 24 DIO line, 1 event counter device |
| NI USB-6210 | 16-Bit, 250 kS/s, 16 AI channels, 4 DI, 4 DO, 2 counters (requires USB 2.0 host support) |
| NI USB-6211 | 16-Bit, 250 kS/s, 16 AI channels, 2 AO, 4 DI, 4 DO, 2 counters (requires USB 2.0 host support) |
| NI USB-6211 OEM | 16-Bit, 250 kS/s, 16 AI channels, 2 AO, 4 DI, 4 DO, 2 counters (requires USB 2.0 host support) |
| NI USB-6215 | 16-Bit, 250 kS/s, 16 AI channels, 4 DI, 4 DO, 2 counters, isolated (requires USB 2.0 host support) |
| NI USB-6218 | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated (requires USB 2.0 host support) |
| NI USB-6218 OEM | 16-Bit, 250 kS/s, 32 AI channels, 2 AO, 8 DI, 8 DO, 2 counters, isolated (requires USB 2.0 host support) |
| NI USB-9211A | 4 AI Channels, 24-bit thermocouple input module |
| NI USB-9215A | 4 AI Channels, ±10 VDC, 16-bit simultaneous sampling analog input module |
| NI USB-9215A BNC | 4 AI Channels, ±10 VDC, 16-bit simultaneous sampling analog input module |
| NI USB-9215A BNC | 4 AI Channels, ±10 VDC, 16-bit simultaneous sampling analog input module |
| NI USB-9233 | 4 AI Channels, ±5 VAC, 24-bit simultaneous sampling DSA module with IEPE |
| NI USB-9234 | 4 AI Channels, ±5 VAC/VDC, 24-bit simultaneous sampling DSA module with IEPE |
| Minimum Processor | RAM | Operating System |
|---|---|---|
| Pentium III/800 MHz or equivalent | 256 MB | Windows 2000(SP3 or later)/XP |
| Pentium III/800 MHz or equivalent | 512 MB | Windows Vista x86/x64 |
The following list covers issues specific to NI-DAQmx Base 3.2.
| Device | Supported Channel Range |
|---|---|
| USB-9211A | ±80 mV |
| USB-9215A | ±10 V |
| Error Code | Description |
|---|---|
| –223700 | 200 kS/s, 12-bit, 16 AI channels, two AO channels, 8 DIO lines, two counter/timers. |
| –200797 | An empty string was specified as a terminal name which is not supported. Specify a valid terminal name. |
| –200745 | Frequency and Initial Delay property values are inconsistent with one or more counter timebase properties. The conflicting properties must satisfy the following constraints:
|
| –200714 | Acquisition has stopped because the driver could not transfer the data from the device to the computer memory fast enough. This was caused by computer system limitations Reduce your sample clock rate the number of channels in the task or the number of programs your computer is executing concurrently. |
| –200608 | Acquisition cannot be started, because the selected buffer size is too small. Increase the buffer size. |
| –200565 | Specified digital channel contains more bits than supported by the 8-bit version of DAQmxBase Port Write. Use the version of DAQmxBase Port Write that supports wider digital ports. |
| –200564 | Specified digital channel contains more bits than supported by the 32-bit version of DAQmxBase Port Read. |
| –200561 | Attempted writing analog data that is too large or too small. |
| –200559 | Task cannot contain a channel with the specified channel type, because the task already contains channels with a different channel type. Create one task for each channel type. |
| –200558 | One task cannot contain multiple independent devices. Create one task for each independent device. |
| –200552 | Specified string is not valid, because it contains an invalid character. |
| –200536 | Specified value is smaller than the minimum value supported for this property. |
| –200527 | Requested values of the Minimum and Maximum properties for the counter channel are not supported for the given type of device. The values that can be specified for Minimum and Maximum depend on the counter timebase rate. |
| –200526 | Write cannot be performed because this version of DAQmxBase Write does not match the type of channels in the task. Use the version of DAQmxBase Write that corresponds to the channel type. |
| –200525 | Read cannot be performed because this version of DAQmxBase Read does not match the type of channels in the task. Use the version of DAQmxBase Read that corresponds to the channel type. |
| –200524 | Write cannot be performed, because the data does not contain data for all channels in the task. When writing, supply data for all channels in the task. Alternatively, modify the task to contain the same number of channels as the data written. |
| –200523 | Read cannot be performed because this version of DAQmxBase Read only returns data from a single channel, and there are multiple channels in the task. Use the multichannel version of DAQmxBase Read. |
| –200498 | Syntax for a range of objects in the input string is invalid. For ranges of objects, specify a number immediately before and after every colon (":") in the input string. Or, if a name is specified after the colon, it must be identical to the name specified immediately before the colon. Colons are not allowed within the names of the individual objects. |
| –200489 | Specified channel cannot be added to the task, because a channel with the same name is already in the task. |
| –200485 | The specified task cannot be loaded, because it is not a valid task. |
| –200478 | Specified operation cannot be performed when there are no channels in the task. |
| –200474 | Specified operation did not complete, because the specified timeout expired. |
| –200473 | Read cannot be performed when the Auto Start property is false and the task is not running or committed. |
| –200459 | Write failed, because there are no output channels in this task to which data can be written. |
| –200452 | Specified property is not supported by the device or is not applicable to the task. |
| –200430 | I/O type of the physical channel does not match the I/O type required for the virtual channel you are creating. |
| –200428 | Value passed to the Task/Channels In control is invalid. The value must refer to a valid task or valid virtual channels. |
| –200361 | Onboard device memory overflow. Because of system and/or bus-bandwidth limitations, the driver could not read data from the device fast enough to keep up with the device throughput. Reduce the sample rate, or reduce the number of programs your computer is executing concurrently. |
| –200341 | Generation was configured to use only onboard memory, but the corresponding buffer is larger than onboard memory. Buffer size is provided implicitly when data is written or explicitly when the buffer is configured. |
| –200330 | An attempt has been made to use the PFI0 terminal of the device for both an analog and digital source. Use a terminal other than PFI0 as the source of your digital signal. |
| –200326 | An attempt has been made to perform a route when the source and the destination are the same terminal. In many cases, such as when configuring an external clock or a counter source, you must select a PFI, PXI Trigger, or RTSI line as the source terminal. |
| –200287 | Attempted to write to an invalid combination of position and offset. The position and offset specified a sample prior to the first sample generated (sample 0). Make sure any negative write offset specified selects a valid sample when combined with the write position. |
| –200284 | Some or all of the samples requested have not yet been acquired. To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock. |
| –200278 | Attempted to read a sample beyond the final sample acquired. The acquisition has stopped, therefore the sample specified by the combination of position and offset will never be available. Specify a position and offset which selects a sample up to, but not beyond, the final sample acquired. The final sample acquired can be determined by querying the total samples acquired after an acquisition has stopped. |
| –200265 | An attempt has been made to use an invalid analog trigger source. If you explicitly named the virtual channel using DAQmxBase Create Channel, you must use the name assigned to that channel. |
| –200261 | An attempt has been made to use an analog trigger in multiple situations with differing properties. Change the analog trigger properties so they are the same, or do not use an analog trigger for all situations. |
| –200254 | Terminal for the device is invalid. |
| –200220 | Device identifier is invalid. |
| –200214 | Analog trigger circuitry unavailable on the device. Select a non-analog trigger type, or use a device with analog triggering hardware. |
| –200170 | Physical channel specified does not exist on this device. Refer to the documentation for channels available on this device. |
| –200099 | Physical channel not specified. |
| –200096 | Number of samples to read must be -1 or greater. |
| –200089 | Task name specified conflicts with an existing task name. |
| –200082 | Minimum is greater than or equal to the maximum. |
| –200077 | Requested value is not a supported value for this property. |
| –200040 | Source terminal to be routed could not be found on the device. Make sure the terminal name is valid for the specified device. Refer to help for valid terminal names. |
| –200012 | Specified physical channel does not support digital output. |
| –89136 | Specified route cannot be satisfied, because the hardware does not support it. |
| –89131 | An attempt has been made to perform a route when the source and the destination are the same terminal. In many cases, such as when configuring an external clock or a counter source, you must select a PFI, PXI Trigger, or RTSI line as the source terminal. |
| –89120 | Source terminal to be routed could not be found on the device. Make sure the terminal name is valid for the specified device. |
| –50256 | USB Device error: feature not supported. |
| Error Code | Description |
|---|---|
| 209800 | DAQmxBase Read did not complete before the arrival of the next sample clock which indicates that your program is not keeping up with the hardware clock. For tasks using sample clock timing slow down the hardware clock or else change your application so that it can keep up with the hardware clock. |
| 209802 | DAQmxBase Wait for Next Sample Clock detected one or more missed sample clocks since the last call to Wait for Next Sample Clock which indicates that your program is not keeping up with the sample clock. To remove this warning slow down the sample clock or else change your application so that it can keep up with the sample clock. |
| 233700 | Internal software warning. |
| Error Code | Description |
|---|---|
| 15 Resource Not Found | The application cannot get access to the hardware. Occurs if the DAQ device is not installed on the PDA or the reference to the hardware is invalid. For an invalid reference, restart LabVIEW |