NI-DAQ 6.9.3 Readme File

© Copyright 2002 National Instruments. All rights reserved. NI-DAQ software is covered by one or more of the following patents:

U.S. Patent No(s).:  5,619,702; 6,067,584; 6,096,094; 6,052,743; 6,148,438; 5,926,775; 5,987,530; 6,073,205

Thank you for using National Instruments NI-DAQ for PC Compatibles, version 6.9.3, for Windows 2000/NT/XP/Me/9x.

This file contains important information regarding this version of NI-DAQ. Please read it carefully so that you will be aware of any known problems or incompatibilities.

Information in this file is organized in the following sections:

Changes in NI-DAQ 6.9.3 from NI-DAQ 6.9.2

The purpose of this release is add support for new devices and to fix some issues from the previous release of NI-DAQ.

New Devices Supported

DIO Clear (DIG_Block_Clear) Fix for NI 6534

When you call DIO Clear.VI (or the DIG_Block_Clear function), the ports on the NI 6534 will no longer toggle to another state intermittently. The state remains unchanged from the last value that was input or output until device reset.

NI 6120 Issues Fixed

NI 6115 and NI 6120 Support for Onboard Acquisition Memory

NI-DAQ 6.9.3 supports single buffered acquisitions of 16 or 32 MS to onboard memory in LabVIEW. Please refer to Knowledge Base 2MBBRQB5, “Using NI 6115 and NI 6120 Onboard Memory to Store Acquisition Data for Later Retrieval,” for further details.  This mode does not support pretrigger acquisitions.

NI 6052E Issue Fixed

NI-DAQ 6.9.3 fixes the NI-DAQ 6.9.2 issue that caused an error to be generated when running the NI 6052E at its maximum sampling rate.

Longer Virtual Channel Names Supported in LabWindows/CVI

NI-DAQ 6.9.3 allows virtual channel names longer than 100 characters to be used with the LabWindows/CVI Easy I/O functions. 

Strain Virtual Channel Issue Resolved for SCXI-1520

NI-DAQ 6.9.3 resolves the SCXI-1520 strain virtual channel issue in NI-DAQ 6.9.2. You can now perform offset nulling on strain virtual channels for the SCXI-1520 with no residual offset.

NI 6025E for PXI, PXI-1010, and SCXI-1125 Recognition Issue Resolved

The issue of the SCXI-1125 not configuring when used with some versions of the NI PXI-6025E in a PXI-1010 chassis has been resolved. You can now configure the SCXI-1125 for operation with all revisions of the NI PXI-6025E.

Continuous Acquisition Issue for NI 4472 Resolved

NI-DAQ 6.9.3 addresses a spontaneous buffer overflow error that can occur in LabVIEW RT and (rarely) Windows operating systems. The issue affects continuous (double-buffered) acquisitions on the NI 4472. When this problem manifests, the scan backlog will suddenly jump to a very large value, and the acquisition will halt with a -10846 buffer overrun error.  

Back to Top

Changes in NI-DAQ 6.9.2 from NI-DAQ 6.9.1

The main purpose of this update is to add support for new devices and Windows XP. This release also includes an updated version of NI-PAL that fixes some issues from 6.9.1.

Issues Fixed by NI-PAL

NI-PAL now provides the following functionality:

New Features

  • Windows XP Support

  • CardWizard Support for Windows NT

  • New Devices Supported

    Configuring Transfer Conditions with the NI 4451

    For NI 4451 devices, you can now configure the AO FIFO transfer condition with the AO_Change_Parameter function. For each selectable transfer condition, the default FIFO transfer count is used (the FIFO transfer count cannot be programmed). For information on AO FIFO transfer conditions and default FIFO transfer counts, see the NI-DAQ Function Reference Help.

    Synchronizing Multiple DSA Devices

    To synchronize DSA devices, note the following:

    Guest Access Issues for Windows 2000 Users

    NI-DAQ will not work in Windows 2000 for users who log on with guest access. 

    6.9.2 Compatible Devices with Minor Issues

    The DAQPad-16XE-50 and SCXI-1200 are not be supported under Windows XP.

    Back to Top

    Changes in NI-DAQ 6.9.1 from NI-DAQ 6.9

    The main purpose of the NI-DAQ 6.9.1 release is to update Measurement & Automation Explorer (MAX) to version 2.1 to support LabVIEW RT 6.0.3.

    Also included is an update to NI-PAL 1.4.4 to resolve an issue that, under certain conditions, could cause system hangs when performing Analog Output operations with E Series devices.

    Support for two new devices was added in this release:

    NI-DAQ 6.9.1 includes support for up to 64 devices and/or device numbers. Please consult the Knowledge Base entry 27C9QJQI for known issues with this feature.

    To use the NI 5112 for PXI/CompactPCI with NI-DAQ 6.9.1 or later, you must use NI-SCOPE 1.6.2 or later. Please refer the Knowledge Base entry 27CCBKV2 for more information.

    NI-DAQ 6.9.1 Compatible Devices with Minor Issues

    The AT plug and play devices, DAQPad-16XE-50, and SCXI-1200 are not be supported under Windows XP.

    All other information in this Readme file applies to NI-DAQ 6.9, NI-DAQ 6.9.1, NI-DAQ 6.9.2, and 6.9.3.

    Back to Top

    New Features and Products Supported in NI-DAQ 6.9 and Later

    New Features Supported in This Version

    New Products Supported in This Version

    All of the following new products are supported in NI-DAQ 6.9:

     

    Back to Top

    Products Supported in Prior Versions of NI-DAQ Not Supported in This Version

    The following products are not supported by NI-DAQ 6.5 or later; the latest release of NI-DAQ that supports them is in parentheses:

    To use any of these products, you must use the NI-DAQ version listed in parentheses or an earlier version.

    Back to Top

    Updates to the Data Acquisition Library for LabVIEW Version 4.x Not Provided in NI-DAQ 6.7 and Later

    Starting with NI-DAQ 6.7 for Windows, the NI-DAQ Setup Utility no longer has an option to install LabVIEW for Windows version 4.x Data Acquisition support files (English and Japanese).

    If for any reason you need to re-install LabVIEW for Windows version 4.x Data Acquisition support files, and you need the NI-DAQ for Windows version 6.7 driver, you can install the core driver components and LabVIEW 4.x DAQ support from an older version of NI-DAQ for Windows (recommended: NI-DAQ 6.6 for English, NI-DAQ 6.1 for Japanese), then install the NI-DAQ for Windows version 6.7 core driver components on top.

    Back to Top

    Changes to the LabVIEW for Windows Data Acquisition Library LLBs for NI-DAQ 6.7 and Later

    As of NI-DAQ 6.7 and later, the LabVIEW for Windows Data Acquisition Library LLBs in the following list (installed in <LabVIEW>\vi.lib\daq) now contain function calls to a dynamic link library (DLL) called LVDAQ.DLL. (This DLL is located in the same directory as the LLBs and replaces the code interface nodes (CINs) that were previously embedded in each VI.)

    These LLBs and the DLL are compatible with LabVIEW for Windows 5.x, LabVIEW RT version 5.1.2 or later, BridgeVIEW 2.x, and LabVIEW Student Edition version 5.x for Windows. These LLBs are backwards compatible, that is, they will load without a broken Run button with NI-DAQ for Windows version 5.0 or later. If a particular operation or feature is not supported, some VIs return DAQ error code –10242 (functionNotFoundError) when you run them.

    One benefit of changing the VIs to call DLL functions instead of CINs is that VI load time is drastically improved. NI’s benchmarks, run on a Pentium III 500 MHz Dell Precision 610 running Windows NT 4.0 SP4, have shown at least a 75% reduction in load time, on average, after the NIDAQ32.DLL is loaded into memory when the first DAQ VI is loaded in LabVIEW.

    The following LabVIEW-related files are no longer needed with LabVIEW for Windows when used with the Data Acquisition LLBs installed with NI-DAQ 6.7 or later:

    Note:   If you are using LabVIEW Application Builder to create an executable that calls DAQ Library VIs, you may manually need to add a reference to LVDAQ.DLL in your build script.

    Back to Top

    New, Renamed, and Removed DAQ Examples

    Following are lists of LabVIEW Data Acquisition examples new in NI-DAQ 6.9 grouped by the default installation locations of the files.

    The following example is added to the vi.lib folder:

    The following examples are added to the examples folder:

    The following NI-DAQ C API examples written in Visual Basic, Visual C++, CVI, or Borland C++ are added to <Examples Directory>\daq\CDIO\:

    Back to Top

    Compiling and Running NI-DAQ Examples in Microsoft Visual C++

    To compile and run examples, follow these steps:

    1. Open a new project by going to File»New. The Projects tab should come up by default.
    2. Select Win32 Console Application as the type of project, and give your project a name.
    3. Select Empty Application. When you have created a new project, it shows your folder menu on the left and the file screen on the right. When you double-click any file you have in your project, the file displays on the right side. To make navigation easier, change from Class View to File View.
    4. Go to Project»Add to Project»File.
    5. Select the NI-DAQ\LIB directory, and add the nidaq32.lib file and the nidex32.lib file. You should also insert the nidaqex.h and nidaq.h file from the NI-DAQ\Include folder. Adding two libraries and header files to your project integrates the source code for most of the data acquisition application examples.
    6. Go to Tools»Options, and select the Directories tab.

    a.       Set the option to Include Files. Make sure that you point to the same directory in NI-DAQ\Include.

    b.      From the same tab, set the option to Libraries and set a path for NI-DAQ\LIB.

    1. If you are using any applications that use Easy I/O functions, you need to include additional files because the Easy I/O functions use some functions from the CVI Run-Time libraries. The additional libraries are easyio.lib, cvisupp.lib, cvirt.lib, and cviwmain.lib and are located in the CVI\EXTLIB directory.

    a.    Go to Tools»Options, and select the Directories tab.

    b.    Set the option to Include Files. Point to the CVI\INCLUDE directory.

    c.    From the same tab, set the option to Libraries, and set a path for CVI\EXTLIB.

    1. Add the source code and header if needed to the project that you want to use.

    You should now be able to build the project into an executable.

    Back to Top

    What to Do if Your Device Is Not Listed in MAX

    If you are using MAX and do not see your device listed, press F5 or go to View»Refresh to refresh MAX.

    If you are using Windows XP and do not see your device listed, go to the Control Panel»Performance and Maintenance»System (or Control Panel»System). Select the Hardware Tab. Select the Device Manager button, and select Other Devices. Right click the devices listed in Other Devices, and select the Driver tab. Select Update Driver…. When the driver has been loaded, go to MAX and press F5 or go to View»Refresh to refresh MAX.

    DSA Devices (44XX, 45XX)

    Functionality Not Supported

    DSA devices do not support analog input/output nonbuffered operations. In LabVIEW, AI SingleScan and AO Single Update VIs are not supported.

    New Instrument Driver Required

    If you have already installed a version of the DSA instrument driver, you must install its latest version to work with NI-DAQ 6.9.

    Back to Top

    DAQPad-6020E Notes

    Externally timed A/D: By default, the DAQPad-6020E supports external sample-interval and scan-interval timing for low speeds (up to about 90 Hz). For faster external sampling, run the Set DAQ Device Information VI (or equivalent) with Information Type = interrupt generation mode and Information Setting = generate interrupt every half FIFO.

    Software analog triggering: The DAQPad-6020E supports software analog triggering only for low-speed acquisitions (up to about 75 S/s). This restriction does not apply to other types of triggering. For more information on analog triggering, refer to the Config_DAQ_Event_Message topic in the NI-DAQ Function Reference Help, or the AI Trigger Config VI in the LabVIEW DAQ Help.

    Continuous, low-speed AI transfers: With the DAQPad-6020E, at the beginning of a continuous, low-speed AI transfer (from 80 to about 400 S/s), there is a noticeable delay before data begins to arrive in the acquisition buffer. The reason is that, although A/D conversions are being generated, the device does not begin transferring data to the PC until its AI FIFO becomes at least half full.

    Timed nonbuffered AI: On the DAQPad-6020E, timed nonbuffered AI operations, as illustrated in the LabVIEW example Cont Acq&Chart (hw timed) VI, are limited to about 50 Hz. At higher rates, LabVIEW may become unresponsive as NI-DAQ tries to empty the AI FIFO by reading one scan at a time from the device.

    Back to Top

    DAQPad-6070E/DAQPad-6052E Notes

    Some 1394 adapter boards report incorrect FIFO sizes. Therefore, NI uses the lowest common denominator for the FIFO size. If your 1394 adapter board has a FIFO depth greater than 456 bytes or reports the wrong speed, download fwctl.exe and readme.txt from ftp://ftp.natinst.com/support/daq/pc/ieee1394 to increase performance.

    Typically, you can disable device and mini-MITE FIFOs within control applications to remove sluggishness. However, this action impacts all DMA channel transfers on the DAQPad-6070E. Also, you can only change FIFO sizes before running any DMA transfers.

    Back to Top

    NI 6527 Information

    When a 6527 device is using an interrupt level (IRQL) that matches the IRQL of either a USB Host Controller or a 1394 Host Controller, change detection may not work. Refer to the Interrupt Performance Issues between PCI Devices and Windows 98section for more information on this issue and ways to work around it.

    Back to Top

    NI 6534 Information

    New Features Supported

    Improved buffered output operations: The 6534 devices feature two memory modules onboard, one for each group. By default, NI-DAQ will load the SCARABs with either the entire data buffer or the entire memory module, whichever is smaller, before starting the output operation, thus eliminating the bus bandwidth limitations. However, you may override the default loading:

    Continuous, high-speed output with repeat data: The 6534 devices support output memory looping mode in which the output data are loaded into the SCARAB only once, and the entire buffer is repeated over and over again, provided that the buffer size is less than or equal to the onboard memory size:

    Onboard memory size: The 6534 devices feature memory modules of various sizes. You can query the memory size of your 6534 device:

    The memory size is returned in bytes.

    20 MHz pattern I/O: You can set the clock frequency to 20 MHz by running the Digital Clock Config VI or DIO Config VI. If you are programming in C, call DIG_Block_PG_Config with timebase = -3 and interval = 1.

    Back to Top

    NI 660X Valid Ranges

    The valid range for NI 660X devices is 0 in the following functions:

    You set this range with the Port parameter.

    Back to Top

    Updating the RT Series PXI Controller for LabVIEW 5.1.2 Users

    If you are using LabVIEW 5.1.2 with an RT Series PXI Controller, NI-DAQ 6.9 detects the Remote System Explorer if it is installed on your system and automatically updates the data acquisition files. After the NI-DAQ installation completes, follow these instructions to update the PXI controller:

    1. Launch Remote System Explorer.
    2. Select the PXI system to upgrade, then click Tools»Install/Upgrade Software to open the Install/Upgrade Software dialog box.
    3. Choose install.rts, in the ~Remote System Explorer\install\pxi directory, as the install image.
    4. Click Install.
    5. Verify the list of software to be installed, and click Proceed to continue with the installation.
    6. When the installation is complete, click Close, then click Yes when prompted to reboot the system.

    Back to Top

    Interrupt Performance Issues between PCI Devices and Windows 98

    Interrupt processing may be slower on systems that exactly match all of the following conditions:

    Extreme sluggishness, timeouts, or lockups may occur on systems that exactly match all of the following conditions:

    Determining the IRQL of Your PCI DAQ Device and USB/1394 Host Controller

    To determine if the IRQL of your PCI DAQ device and USB/1394 host controller are the same, follow these instructions:

    1. Right-click the My Computer icon, usually located in the top left corner of the screen.
    2. Select Properties from the pop-up menu to open the System Properties window.
    3. Click the Device Manager tab.
    4. Double-click Computer to open the Computer Properties window.
    5. Make sure the Interrupt request (IRQ) option is selected.
    6. Scroll through the selection box to find the PCI DAQ device, and record the number in the Setting column (the IRQ for the device).
    7. Scroll through the selection box to find the USB/1394 host controller, and record its IRQ from the Setting column.
    8. Compare the number you recorded for your PCI DAQ device to the number you recorded for the USB/1394 controller.

    If the setting number of the PCI data acquisition device matches the USB/1394 host controller, you can improve interrupt processing performance by following the instructions below.

    Note:   The sharing of an IRQL between the USB/1394 host controller and the PCI data acquisition device affects only the speed of processing interrupt transactions. It does not affect DMA or other I/O. Also, the sharing of an IRQL between any number of PCI data acquisition devices or other PCI devices, such as a video or network adapter, should not affect the interrupt processing speed.

    Easy Methods for Improving Interrupt Processing Speed

    If you are not using a USB/1394 device and do not plan to use one for some time, do the following:

    1. Right-click the My Computer icon, usually located in the top left corner of the screen.
    2. Select Properties from the pop-up menu to open the System Properties window.
    3. Click the Device Manager tab.

    ·        USB:

      1. Double-click Universal Serial Bus Controller.
      2. Double-click USB Host Controller.

    ·        1394:

      1. Double-click 1394 bus controller (this name may vary).
      2. Double-click the 1394 device.
    1. Click the General tab.
    2. Check Disable in this hardware profile box.
    3. Click OK to save settings and close the System Properties window.
    4. Reboot your system.

    If you are using or plan to use a USB/1394 device, the following instructions might work:

    1. Shut down and unplug your computer.
    2. Move the PCI DAQ device to another PCI slot.
    3. Start your system.
    4. Follow the instructions in the Determining the IRQL of Your PCI DAQ Device and USB/1394 Host Controller section to determine if the IRQ levels are still the same.

    Advanced Methods for Improving Interrupt Processing Speed

    If you are not using a USB/1394 device and do not plan to use one, you can do the following:

    1. Restart the computer and enter the BIOS settings screen (follow the instructions that came with your computer).
    2. If your BIOS controller allows you to disable the USB/1394 port, do so.
    3. If your BIOS controller allows you to enable/disable PCI IRQ levels, activate as many IRQ levels as possible to increase the chances of not sharing the same IRQL.
    4. Disable any unused devices, such as a built-in sound card, LPT2 port, or COM2 port, to free additional resources.
    5. Save your BIOS settings.
    6. Restart the system.

    Note:   Some devices cannot be disabled via the BIOS settings. In this case, try to disable the device(s) via the device manager within Windows.

    Last-Resort Method for Improving Interrupt Processing Speed

    If the previously described methods do not work, you can try following these instructions:

    Note:   This method should be used only as a last resort, since it requires you to manually change computer resources.

    1. Restart the computer and enter the BIOS settings screen (follow the instructions that came with your computer).
    2. Turn off or disable Plug and Play.
    3. Save the BIOS settings.
    4. Restart the system.
    5. Right-click the My Computer icon, usually located in the top left corner of the screen.
    6. Select Properties from the pop-up menu to open the System Properties window.
    7. Click the Device Manager tab.

    ·        USB:

      1. Double-click Universal Serial Bus Controller.
      2. Double-click USB Host Controller.

    ·        1394:

      1. Double-click 1394 bus controller (this name may vary).
      2. Double-click the 1394 device.
    1. Click the Resources tab.
    2. Click to remove the checkmark from Use Automatic settings.
    3. Double-click Interrupt Request and choose a setting level that differs from the PCI DAQ device.

    Back to Top

    USB and 1394 Support Requirements and Limitations

    Operating System Support for USB and 1394

    As of NI-DAQ 6.7 and later, software support for USB and 1394 is provided only for Windows 2000/XP/Me/98 single-processor systems. If you are running another version of Windows, you will need to upgrade your operating system to use USB or 1394 devices.

    National Instruments Software Support for USB and 1394

    Potential Problems

    It is best to connect your USB or 1394 DAQPad device to your PC and power it on before launching your DAQ application or MAX. If you connect or power on your DAQPad device after your DAQ application is loaded, reset the device in software before attempting to use it by running the Device Reset VI in LabVIEW or calling the Init_DA_Brds() in the NI-DAQ API.

    If you are using a DAQ application that does not support manual resets, like VirtualBench, you must connect and power on your USB or 1394 DAQPad device before running your application.

    On rare occasions, USB or 1394 devices will not appear in the MAX device tree if any Windows Explorer (including Internet Explorer) windows are open. If this problem occurs, close all Explorer windows and refresh the MAX window by pressing F5. If the problem still occurs, restart the system.

    USB and 1394 DAQPad devices do not support Windows 2000/XP/Me/98 suspend mode.

    Configuration and Power Management

    USB and 1394 devices support plug-and-play configuration and hot swapping, and Windows Me/98 provide some operating system support for power management. Although these features generally facilitate device configuration, please follow the guidelines in this section to avoid configuration problems.

    Under certain conditions, problems may occur when simultaneously disconnecting multiple 1394 devices during data acquisition. It is very important that you connect or disconnect devices before loading any data acquisition software.

    After disconnecting or powering off a device, you should wait 5-10 s (or until the hourglass icon goes away) before powering the device back on.

    On some computers, power management can interfere with active DAQ applications that are using USB or 1394 devices. If your DAQ application needs to run while the computer is unattended, disable the power management features in the operating system and the BIOS, as well as your screen saver.

    To disable power management in Windows XP/Me/98, do the following:

    1. Open the Control Panel by clicking Start»Settings»Control Panel.
    2. Double-click the Power Management icon (Power Options in Windows XP) to start the Power Management applet, then click the Power Schemes tab.
    3. In the Power Schemes list box, select Always On.
    4. In Settings for the Always On power scheme, set the parameters as follows:
      1. System standby: Never (In Windows XP, choose the Hibernate tab, and select Disable Hibernate)
      2. Turn off monitor: Any choice is acceptable
      3. Turn off hard disks: Never
    5. Click OK to save the settings and close the Power Management applet.
    6. Close the Control Panel.

    To find out if your system has power management built into the BIOS, and for instructions to disable BIOS power management features, refer to your system documentation.

    To disable your screen saver, do the following:

    1. Right-click anywhere on the Windows desktop, and choose Properties from the pop-up menu to open the Display Properties window.
    2. Click the Screen Saver tab.
    3. In the Screen Saver list box, select None.
    4. Click OK to save your settings and exit the Display Properties window.

    Performance

    USB/1394 performance depends highly on system-specific factors such as CPU speed, memory architecture, and system chipset characteristics. USB and 1394 operations are software-intensive, so running other applications during data acquisition operations may affect performance. Higher-speed USB and 1394 operations may also affect the performance of other applications.

    All the USB and 1394 devices connected to your PC share the same bandwidth. Using multiple USB and 1394 devices simultaneously may affect the performance of DAQ applications. Also, since the PC’s USB and 1394 host controllers reside on the PCI bus, using other bandwidth-intensive PCI devices may affect performance.

    Because data is transferred across the USB and 1394 buses in packets, the timing of operations involving the transfer of small or precise amounts of data is less deterministic than with plug-in DAQ devices. For example, the timing of messaging and interrupt-intensive operations is likely to vary more with USB and 1394 devices.

     

    Back to Top

    SCXI_Calibrate Note

    Performing a scan before running an internal calibration using SCXI_Calibrate could result in a –10636 error (you cannot start a continuous [double-buffered] operation with a synchronous function call). If developing in C, call the DAQ_DB_Config function with the device number of the DAQ device you are using to calibrate and Dbmode = 0. If you are using LabVIEW, run the Device Reset VI on the DAQ device. You can also exit your development environment and start your application again.

    Back to Top

    Remote SCXI Devices

    If you plan to use an SCXI-1104 or SCXI-1125 with a Remote SCXI configuration, you must update the firmware on your SCXI-2000 chassis or SCXI-2400 module. If you have Remote SCXI and do not plan to use an SCXI-1104 or SCXI-1125, no update is necessary.

    Follow these steps to update the firmware:

    1. Be sure that your Remote SCXI is functioning properly and is turned on.
    2. Double-click the Measurement & Automation icon to open MAX.
    3. Click Devices and Interfaces to view the device tree.
    4. Select the Properties. If you have an SCXI-2000 chassis, right-click its folder and select Properties. If you have an SCXI-2400 module, double-click the folder of the chassis that it is in, then right-click on the SCXI-2400 folder and select Properties.
    5. Click Reprogram.
    6. Enter the path to the updated Remote SCXI image file and click OK.

    The new firmware downloads to your Remote SCXI chassis or module. Do not unplug the cable or interrupt this operation.

    Back to Top

    Remote Device Access (RDA)

    If you want to use NI-DAQ 6.9 in an RDA application, be sure to run NI-DAQ 6.9 on both your client (local) and RDA server (remote) computers. This is required because of the new RDA security features added for this version.

    The security features allow you to specify a password for each device configured on the server, which restricts RDA to that device to clients who know the correct password. To set the password for a device, follow these instructions:

    1. On the server computer, open MAX (double-click the Measurement & Automation icon on your desktop).
    2. Double-click Devices and Interfaces to expand the device tree.
    3. Right-click the device to which you want to restrict access, and select Properties from the pop-up menu to open the device configuration window.
    4. Click the Remote Access tab.
    5. Click Set Password to open the password-setting dialog box, and enter a password.

    After you set a password for the device, RDA clients must specify the correct password to use the device through RDA. By default, the password is empty, indicating that the device is not password-protected. If a client is already using an RDA device when the password is changed, the client will get a –10340 error until the correct password is set. To set the correct password, follow these instructions:

    1. On the client computer, open MAX (double-click the Measurement & Automation icon on your desktop).
    2. Double-click Devices and Interfaces to expand the device tree.
    3. Right-click the device to which you want to restrict access, and select Properties from the pop-up menu to open the device configuration window.
    4. At the prompt for the password, enter the correct password for the device.

    In addition to each device-level password that can be set on the server, there is a root-level password that can be set to prevent unauthorized users from remotely configuring the RDA server. To set this password on the server computer, open MAX on the server and select Tools»NI-DAQ Configuration»Set Remote Configuration Password. After you set this password, clients attempting to remotely configure the server through MAX (by clicking Tools»NI-DAQ Configuration»Remote DAQ Configuration) must first enter the correct password. Clients that know the correct root-level password can change the root-level password of the server as well as each of the device-level passwords through Remote DAQ Configuration.

    For NI-DAQ 6.7 and later, RDA has the ability to time out. This is useful when your network connection is lost while your RDA client computer is waiting to receive a response from your RDA server computer. Without the timeout, your RDA client computer waits indefinitely, causing your LabVIEW program to appear to hang. With the timeout feature, your LabVIEW program returns the -10340 noConnectError instead.

    The default value for this timeout is 240,000 ms (4 min). To change this, you must add a value to an existing registry key. Follow these steps to do so:

    1. Run regedit.exe or regedt32.exe.
    2. Open HKEY_LOCAL_MACHINE»SOFTWARE»National Instruments»NI-DAQ»CurrentVersion»Configuration Manager.
    3. Select New»DWORD Valuefrom the Edit menu.
    4. Name the new value ReceiveTimeoutValue.
    5. Double-click ReceiveTimeoutValue to open a dialog box in which you enter the value data. Enter the timeout you want in milliseconds. Be sure the Base is set to Decimal. Specifying a timeout value of 0 indicates an infinite timeout, which exhibits the same behavior as NI-DAQ versions prior to 6.7.
    6. Exit regedit.exe or regedt32.exe.

    Be aware that NI-DAQ calls that read or write data can take a long time to return depending on your rates and the amount of data. Calling the AI Buffer Read VI and reading 100 scans when you are acquiring at 10 scans/s takes 10 s. If your ReceiveTimeoutValue is less then 10,000 ms, you receive the –10340 error even though your network connection is fine.

    Back to Top

    Modifying the DAQ Configuration Files in MAX

    For MAX version 2.0 through 2.2, the menu options under Tools»NI-DAQ Configuration allow you to manipulate your DAQ configuration files. The Set Active Configuration option lets you set any DAQ configuration file to be the active file. The Save Configuration As option lets you save the current configuration file to a new file. The Create New Configuration option creates a new configuration file with a name you choose.

    Back to Top

    NI-DAQ Documentation Changes

    DAQ Hardware Overview Guide

    The valid analog input range for the PCI-6110E and PCI-6111E is  ±42 V.

    Data Acquisition VI Help

    The help for the AI Config VI specifies that you can allocate more than one buffer with the PCI-5911 and the VXI-5912. This is incorrect. You should use NI-SCOPE to program your PCI-5911.

    The help for the AI Control VI defines the number of posttrigger scans in an acquisition as the number of scans allocated to the buffer minus the minimum number of pretrigger scans. This is incorrect. The number of posttrigger scans is equal to the total number of scans to acquire minus the minimum number of pretrigger scans.

    When using the AO Write, AO Waveform Gen, AO Continuous Gen, and AO Buffer VIs with a 61XX or 671X device, the number of samples in the scaled data or waveform data parameters must be even or a negative count error will be returned and no data will be written. For example, three channels with 101 points will fail, but three channels with 102 points or two channels with 101 points will work correctly.

    The help for the Route Signal VI lists the PLL reference clock as choice 21 of the signal source parameter. This is incorrect. Board clock is choice 21.

     

    The help does not document a parameter set by the AI Parameter VI. This parameter, FIFO Transfer Count, specifies how many points of data to transfer from the buffer upon each interrupt.

    NI-DAQ Function Reference Help

    The AI_Get_Overloaded_Channels function is supported for DSA devices only, except the NI 4454 for PCI.

    For the AO_Configure function, the chan parameter description should include the following:

    For the GPCTR_Read_Buffer function, the correct prototype is GPCTR_Read_Buffer (deviceNumber, gpctrNum, readMode, readOffset, numPtsToRead, timeOut, numPtsRead, buffer). The parameter discussion should include the following parameters:

    For the SCAN_Startfunction, valid values for the sampTimebase parameter include -3 and 2 for E Series devices.

    For the SCXI_Track_Hold_Setupfunction, the note stating that this function does not work with E Series devices is incorrect. If you have a track-and-hold module (SCXI-1530, SCXI-1531, SCXI-1140, SCXI-1520) connected to an E Series device, you can use this function to set up a channel-scanning operation in multiplexed mode.

    In the DIG_Block_PG_Config function, the valid range for reqInterval is 1 through 65,535. 

    The list of functions supported by the AT-AO-6/10, DAQ-AO-2DC, and NI 671X follows:

    AT-AO-6/10: AO_Calibrate, AO_Configure, AO_Update, AO_VScale, AO_VWrite, AO_Write, Config_DAQ_Event_Message, DIG_In_Line, DIG_In_Prt, DIG_Out_Line, DIG_Out_Prt, DIG_Prt_Config, Get_NI_DAQ_Version, Init_DA_Brds, RTSI_Clear, RTSI_Clock, RTSI_Conn, RTSI_DisConn, Timeout_Config, WFM_Chan_Control, WFM_Check, WFM_ClockRate, WFM_DB_Config, WFM_DB_HalfReady, WFM_DB_Transfer, WFM_from_Disk, WFM_Group_Control, WFM_Group_Setup, WFM_Load, WFM_Op, WFM_Rate, WFM_Scale

    DAQ-AO-2DC: AO_Change_Parameter, AO_Configure, AO_VWrite, DIG_In_Line, DIG_In_Prt, DIG_Out_Line, DIG_Out_Prt, DIG_Prt_Config, Get_DAQ_Device_Info, Get_NI_DAQ_Version, Init_DA_Brds

    NI 671X: AO_Change_Parameter, AO_Configure, AO_Update, AO_VScale, AO_VWrite, AO_Write, Calibrate_E_Series, Config_DAQ_Event_Message, DIG_In_Line, DIG_In_Prt, DIG_Line_Config, DIG_Out_Line, DIG_Out_Prt, DIG_Prt_Config, Get_DAQ_Device_Info, Get_NI_DAQ_Version, GPCTR_Change_Parameter, GPCTR_Config_Buffer, GPCTR_Control, GPCTR_Set_Application, GPCTR_Watch, Init_DA_Brds, Select_Signal, Set_DAQ_Device_Info, Timeout_Config, WFM_Check, WFM_ClockRate, WFM_DB_Config, WFM_DB_HalfReady, WFM_DB_Transfer, WFM_from_Disk, WFM_Group_Control, WFM_Group_Setup, WFM_Load, WFM_Op, WFM_Rate, WFM_Scale

    NI-DAQ Function Reference Manual

    National Instruments no longer prints a function reference manual for NI-DAQ. All of the NI-DAQ functions are now described only in the NI-DAQ Function Reference Help. To view the NI-DAQ Function Reference Help, click Start»Programs»National Instruments»NI-DAQ»NI-DAQ Help.

    NI-DAQ User Manual

    SCXI_Strain_Null information is missing. This function nulls the offset in the specified strain gauge on an SCXI-1520 strain gauge module by adjusting the internal potentiometers.

    Passing Unsigned 16-Bit and 32-Bit Integer Parameters in Visual Basic

    Unsigned 16-bit parameters: The Visual Basic INTEGER type is a signed value; any value that is greater than 32,767 is considered a negative number. The workaround for the problem is as follows:

    1. If the function is supposed to return an unsigned 16-bit integer, and you are reading back a negative number, add 65,536 to the negative number.

    For example:

    Dim myUnsignedCnt As Long       

    Dim retCnt As Integer                             

    ‘(retCnt is the value returned from the called function)

    ‘You can call a DAQ function that returns an unsigned 16-bit value and stores it in retCnt.

    if retCnt < 0 then

    myUnsignedCnt = CInt(retCnt) + 65536

    else

    myUnsignedCnt = retCnt

    end if

    1. To pass an unsigned 16-bit value to a function with an unsigned 16-bit type parameter, you must first compute the value that you want to pass to the function.

    For example:

    Dim myUnsignedCnt As Long

    Dim ToPassVal As Integer

    ‘You compute the value that you want to pass to the function and store it in myUnsignedCnt.

    if myUnsignedCnt > 32767 then

    ToPassVal = CInt(myUnsignedCnt - 65536)

    else

    ToPassVal = CInt(myUnsignedCnt)

    end if

    Unsigned 32-bit parameters: The Visual Basic LONG integer type is a signed 32-bit type; any value that is greater than 2,147,483,647 is considered a negative number. The workaround for the problem is as follows:

    1. If the function is supposed to return an unsigned 32-bit integer, and you are reading back a negative number, then add 4,294,967,296 to the negative number.

    For example:

    Dim myUnsignedCnt As Double

    Dim retCnt As Long       

    ‘(retCnt is the value returned from the called function)

    ‘You can call a DAQ function that returns an unsigned 16-bit value and stores it in retCnt.

    if retCnt < 0 then

    myUnsignedCnt = CInt(retCnt) + 4294967296

    else

    myUnsignedCnt = retCnt

    end if

    2.      To pass an unsigned 32-bit value to a function with an unsigned 32-bit type parameter, you must first compute the value that you want to pass to the function.

    For example:

    Dim myUnsignedCnt As Double

    Dim ToPassVal As Long

    ‘You compute the value that you want to pass to the function and store it in myUnsignedCnt.

    if myUnsignedCnt > 2147483647 then

    ToPassVal = CLng(myUnsignedCnt - 4294967296)

    else

    ToPassVal = CLng(myUnsignedCnt)

    end if

     

    Obsolete Standard

    DIN 43760 is an obsolete temperature-curve standard for RTDs. The current standard is
    DIN EN 60751.

     

    Back to Top