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

NI-DAQ 8.5 Readme

NI-DAQ 8.5 Readme

Copyright 2003–2007 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, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks.

Patents

For patents covering the National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your CD, or ni.com/patents.



Thank you for using NI-DAQmx, version 8.5f5. This release differs from 8.5f3 with the inclusion of the following changes:
  • Updated to MAX 4.2.1 which resolves an issue with MAX 4.2 where Real-Time targets may not be listed when unconfigured or in Safe Mode. Refer to ni.com/kb and search for KnowledgeBase entry 47IC8SCW.
  • Resolves an issue that may have resulted in delays in task creation and editing. The original issue is only present in NI-DAQmx 8.5f3 and affects tasks larger than approximately 64 channels in size.

The Readme contains the following main sections:

NI-DAQ 7.x and Later Software

This section provides an overview of NI-DAQmx and Traditional NI-DAQ (Legacy). National Instruments measurement devices are packaged with NI-DAQ driver software, an extensive library of VIs and ANSI C functions you can call from your application software, such as LabVIEW or LabWindows™/CVI™, to program your NI measurement devices. Measurement devices include DAQ devices such as the M Series multifunction I/O (MIO) devices, signal conditioning modules, and switch modules. Driver software has an application programming interface (API ), which is a library of VIs, functions, classes, attributes, and properties for creating applications for your device.

NI-DAQ 7.x and later includes two NI-DAQ drivers, NI-DAQmx and Traditional NI-DAQ (Legacy), each with its own APIs, hardware configuration, and software configuration.

Choosing the API to Use

This section includes information on choosing the right API for your device and application.

NI-DAQmx

NI-DAQmx is the latest NI-DAQ driver with new VIs and functions and development tools for programming measurement devices. You should install and use NI-DAQmx if you are using devices supported by NI-DAQmx; refer to Device Support. If you are using a TEDS sensor, you can use only NI-DAQmx.

If you are using NI application software with NI-DAQmx, you must use LabVIEW, LabWindows/CVI, or Measurement Studio version 7.x and later, LabVIEW SignalExpress 2.x, or the LabVIEW Real-Time Module 7.1 or later.

To use Visual C# or Visual Basic.NET, you must use NI-DAQmx.

You can also use supported versions of Visual Studio to create NI-DAQmx applications with Visual Basic 6.0 and ANSI C.

Traditional NI-DAQ (Legacy)

Traditional NI-DAQ (Legacy) is an older driver with outdated APIs for developing data acquisition, instrumentation, and control applications for older National Instruments DAQ devices. Traditional NI-DAQ (Legacy) has the same VIs and functions and works the same way as NI-DAQ 6.9.3, except you can use Traditional NI-DAQ (Legacy) and NI-DAQmx on the same computer, and some hardware and software is no longer supported.

You should use Traditional NI-DAQ (Legacy) only in certain circumstances.

New Features

The following main features were added in this release.

NI-DAQmx Known Issues

This section covers issues specific to NI-DAQmx.

Aborting Single-Point Reads and Writes in LabVIEW

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

Counter Behavior of the NI DAQPad-6015/6016 for USB

When performing buffered counter measurements on both ctr0 and ctr1 simultaneously, ctr1 returns duplicate counts. If you do not use ctr0 or if ctr0 performs a software-timed measurement, ctr1 functions properly.

DAQ Assistant Maximum Channel Count

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

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

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-DAQ with a .NET language, an existing project can produce build errors that read "error CS0011: Referenced class 'className' has base class or interface 'NationalInstruments.ISynchronizeCallbacks' defined in an assembly that is not referenced. You must add a reference to assembly 'NationalInstruments.Common'." To eliminate this error, add a reference to the NationalInstruments.Common assembly to the project. This problem occurs when an existing project was built with NI-DAQ 7.2 or earlier and is rebuilt with NI-DAQ 7.3 or later.

LabVIEW Long Property Names

When importing or exporting .ini files and tab-delimited text, LabVIEW long property names are not supported. Only English LabVIEW short property names, CVI property names, and C++/.NET class.property names are supported.

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 333kHz.

.NET Remoting

Accessing objects in the DAQmx .NET class library from a remote application domain with .NET Remoting is not supported in Microsoft Visual Studio .NET 2003.

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-DAQmx .NET Framework 1.1 Help Shortcut

A shortcut to the NI-DAQmx .NET Framework 1.1 Help is installed by default at Start»All Programs»National Instruments»NI-DAQ»NI-DAQmx .NET Framework 1.1 Help. This documentation is in the Microsoft Help 2.0 format and requires a Microsoft Help 2.0 viewer to be displayed. A Microsoft Help 2.0 viewer is installed with both Microsoft Visual Studio .NET and the Microsoft .NET Framework SDK. The SDK is freely available from MSDN at http://www.microsoft.com/downloads . If you do not have either of these products, you will need a standalone Microsoft Help 2.0 viewer to display the documentation. Some Help 2.0 viewers are available for download, such as Helpware's H2Viewer.

NI PCI-6704 and PXI-6704 Current Output Accuracy

NI-DAQmx 8.3 changes the algorithm used to scale the 20mA 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.

NI PCI-7041/6040E Support

The NI PCI-7041/6040E device for LabVIEW RT is no longer supported in NI-DAQmx 8.3 and will not be supported in future versions. The device continues to be supported in NI-DAQmx 8.1 and earlier.

Resolving Compiler Warnings from SynchronizingObject in Visual Studio 2005

SynchronizingObject has been obsoleted in Measurement Studio class libraries for .NET Framework 2.0. Accessing this property produces compiler warnings. If you were using SynchronizingObject in .NET Framework 1.1, you must update your code to use SynchronizationContext in .NET Framework 2.0. For more information about SynchronizationContext, refer to Events, Callbacks, and Thread Safety in Measurement Studio Class Libraries in the NI-DAQmx .NET Framework 2.0 help. The help can be launched from Start»All Programs»National Instruments»NI-DAQ».NET Framework 2.0 Help.

Some Devices Enumerate Twice

Supported CompactRIO devices that fit into the NI USB-9162 carrier enumerate twice in MAX. When a device, such as the NI USB-9421, is first installed, it appears as the NI USB-9162 before appearing as the correct device.

Temperature Sensors and the Mass Termination USB-6251/6259

When configuring the SCB/SCC-68, the temperature sensor check box is greyed out when the block is connected to either connector of a Mass Termination USB-6251 or USB-6259

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.

USB Device Removal During a DAQ Operation

If a USB DAQ device is unplugged while a DAQ operation is being performed, unexpected results may occur, including causing the operating system to hang. In these occasional, extreme cases, you must reboot the computer. NI recommends stopping all DAQ operations on a USB device before unplugging the device from the computer.

Using the C++ API from Multiple DLLs in the Same Process

If you use the C++ API from multiple DLLs in the same process, you must access the API from only one DLL at a time. You must stop using the API in one DLL and destroy all API objects before using the API in another DLL.

Virtual TEDS Data for the NI 9233/9237

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

Using NI-DAQmx and Traditional NI-DAQ (Legacy) on the Same Computer

Existing applications developed with earlier versions of NI-DAQ will run under Traditional NI-DAQ (Legacy). You can use both the Traditional NI-DAQ (Legacy) API and the NI-DAQmx API on the same computer with the following restrictions:

Refer to ni.com/support for details and instructions about the following topics:

Support in NI-DAQ 8.5

Operating System Support

NI-DAQ Version Windows Vista 641 Windows Vista 321 Windows XP Windows 2000
NI-DAQmx 8.5 Yes Yes Yes Yes
Traditional NI-DAQ 7.4.4 No No Yes Yes
1Windows Vista Business edition

For OS-specific device support information, refer to ni.com/support/daq/versions.htm.

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 8.5 supports PharLap only with the LabVIEW Real-Time Module 7.1 and later.

Measurement Studio requires Visual Studio .NET 2003, which requires Windows 2000/XP. If you are using the DAQmx .NET Library, the .NET 1.1 framework is required. .NET 1.1 requires Windows 2000/XP.

Windows NT users must use NI-DAQmx 7.5 or Traditional NI-DAQ (Legacy) 7.4.

Windows Me/98 users must use NI-DAQ 7.1 or earlier. Windows 95 users must use NI-DAQ 6.9.3 or earlier

LabVIEW Real-Time for the Macintosh 7.1 will not be supported in LabVIEW 8.0 due to low demand. However, National Instruments continues to support PCI and USB data acquisition hardware using NI-DAQmx Base. Macintosh systems can continue to serve as hosts to real-time targets. For more information on supported products, refer to ni.com/mac.

For operating system-specific installation instructions, use the Hardware Installation/Configuration Troubleshooter at ni.com/support/install.

To find and download an earlier version of NI-DAQ that supports other operating systems, refer to ni.com/downloads.

NI Application Software Support

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

Starting with NI-DAQ version 7.4.2, Traditional NI-DAQ (Legacy) installs support only for the latest version of LabVIEW found on the system. The Traditional NI-DAQ (Legacy) API is mass-compiled in LabVIEW version 7.0. See LabVIEW Support in the Traditional NI-DAQ (Legacy) Readme for more information.

NI Application Software Versions Supported by NI-DAQmx Versions Supported by Traditional NI-DAQ (Legacy)
LabVIEW 7.1 and later 7.0 and later
LabVIEW Real-Time Module 7.11 and later 7.0 and later
LabWindows/CVI 7.x and later 6.0 and later
Measurement Studio 7.x and later 6.0 and later
LabVIEW SignalExpress 2.x and later
1To use LabVIEW Real-Time Module 7.1 with NI-DAQmx, you must use NI-DAQmx 7.2 or later.
2Traditional NI-DAQ (Legacy) with the Measurement Studio ActiveX control. These versions do not include a Measurement Studio C++ or .NET interface.

.NET and Measurement Studio Visual C++ Example Paths

Starting with NI-DAQ version 8.5, the .NET and Measurement Studio 8.1.1 Visual C++ example paths have changed. In the following paths, x is the letter of the hard drive.

The .NET example paths for Windows Vista are x:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\DotNET1.1 and x:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\DotNET2.0.

The Measurement Studio 8.1.1 Visual C++ example paths for Windows Vista are x:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\MStudioVC2003 and x:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\MStudioVC2005.

The .NET example paths for Windows XP and Windows 2000 are x:\Documents and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\DotNET1.1 and x:\Documents and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\DotNET2.0.

The Measurement Studio 8.1.1 Visual C++ example paths for Windows XP and Windows 2000 are x:\Documents and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\MStudioVC2003 and x:\Documents and Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\MStudioVC2005.

For more information, 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 and Traditional NI-DAQ (Legacy).

Programming Language Visual Studio Versions Supported by NI-DAQmx Visual Studio Versions Supported by Traditional NI-DAQ (Legacy)
ANSI C 6.0 and later 6.0 and later
C++ 2003 (7.1)1
Visual Basic 6.0 6.0 SP62 6.0 SP63
.NET Framework 1.1
Languages
(C# and Visual Basic.NET)
2003 (7.1)
.NET Framework 2.0
Languages
(C# and Visual Basic.NET)
2005 (8.0)
1 Requires Measurement Studio 7.x
2 Support through ANSI C type library
3 Support through ActiveX

Earlier versions of NI-DAQ support other application software and language versions. To find and download an earlier version of a driver, refer to ni.com/downloads.

LabVIEW SignalExpress

LabVIEW SignalExpress LE gives you a 30-day trial of the Full version of LabVIEW SignalExpress. For more information on the trial version, refer to Getting Started with LabVIEW SignalExpress, installed by default at Start»All Programs»National Instruments»LabVIEW SignalExpress.

Device Support

The following lists detail the devices supported in NI-DAQmx and Traditional NI-DAQ (Legacy). Device support is divided into the following categories:

For OS-specific device support information, refer to ni.com/support/daq/versions.htm.

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

Devices Supported Only in NI-DAQmx

NI-DAQmx supports the following devices:

Devices Supported in NI-DAQmx and Traditional NI-DAQ (Legacy)

The following devices are supported in NI-DAQmx and Traditional NI-DAQ (Legacy). For information on calibrating SCXI devices in NI-DAQmx 8.0 or later, refer to ni.com/info and enter the info code rdsct4.

Devices Restricted to Traditional NI-DAQ (Legacy)

NI-DAQmx does not support the following devices. The following devices are supported only in Traditional NI-DAQ (Legacy):

Devices No Longer Supported in NI-DAQmx 8.3 and Later

The following products are not supported in NI-DAQmx 8.3 and later and will not be supported in future versions of NI-DAQmx:

Devices No Longer Supported in NI-DAQ 7.x and Later

The following products are not supported in NI-DAQmx 7.x and later or Traditional NI-DAQ (Legacy) 7.x and will not be supported in future versions of NI-DAQ. All references to unsupported products, such as VXI-DAQ devices, should be ignored. You must use NI-DAQ version 6.9.x or earlier to program these devices:

System Requirements

Development

Minimum Processor Pentium III/Celeron 600 MHz or Equivalent
RAM 128 MB
Screen resolution 800 x 600 pixels
Operating system Windows 2000/XP or later


Recommended Processor Pentium 4 or Equivalent
RAM 256 MB
Screen resolution 1024 x 768 pixels
Operating system Windows 2000/XP or later

Deployment

Minimum Processor Pentium 200 MHz or Equivalent
RAM 64 MB
Screen resolution 800 x 600 pixels or no screen
Operating system Windows 2000/XP or later


Recommended Processor Pentium III/Celeron 600 MHz or Equivalent
RAM 256 MB
Screen resolution 1024 x 768 pixels or no screen
Operating system Windows 2000/XP or later

You must have Internet Explorer version 5.0 or later to use some features of the NI-DAQ 7.x and later documentation, including the help system and Device Document Browser.

If you are using either an M Series USB device or NI cDAQ-9172 CompactDAQ chassis, you must run either Windows Vista, Windows XP Service Pack 2 or greater, or Windows 2000 Service Pack 4 or greater.