Traditional DAQ support in LabVIEW 2010?

Hello,
Been researching this a while and I must admit, I am quite confused. I am trying to run a program written in LV 7.1 using traditional DAQ vi's in LV 2010. I think what I need are traditional DAQ drivers, but I cannot find the correct drivers. Plus I'm unsure if I will run into compatability issues. If someone could point me in the right direction I would very much appreciate it!
Old machine:
PCI 6040E
LV 7.1
Win XP
New Machine:
PXI 6251
LV 2010
Win 7
Thanks
Solved!
Go to Solution.

Dirk H. wrote:
... Finally, due to errors, I was forced to LabVIEW 2010.
What errors?
Finally, due to errors, I was forced to LabVIEW 2010. Now I'm looking for the traditional DAQ(to minimize my work) for the old software.
LabVIEW 2010 would require Traditional DAQ 7.4.4. http://digital.ni.com/public.nsf/allkb/F4E76EC05118F72D8625773000672298
Dirk H. wrote:
I have a PCI-6503 and a PCI-MIO-16E-4(along with a PCI-GPIB board). ... Am I forced to upgrade any or both of the DAQ cards? All of the cards appear to be installed successfully by viewing them in Measurement and Automation.
This page lists the required DAQ software for each device: http://zone.ni.com/devzone/cda/tut/p/id/6910. That page indicates both of your devices are supported by Traditional DAQ 7.4.4.

Similar Messages

DAQmx support for LabVIEW 2010

FYI to those downloading LabVIEW 2010 from NI web site:
After Installing LabVIEW 2010 (download from web site), I noticed that there is no support for DAQmx (i.e.. VI libraries) in NI_DeviceDrivers-February2010 DVD (my latest copy). Your have to download and install DAQmx 9.2 drivers (the first to include LabVIEW 2010 support).
Additionally, If you were using Traditional NI-DAQ (Legacy) 7.4.4 VIs in a prior version of LabVIEW, you must do one of the following:
      1. Uninstall current Traditional NI-DAQ (Legacy) 7.4.4 installation and re-install after completing LabVIEW 2010 installation.
          Reason: Traditional NI-DAQ (Legacy) installs support only for the latest version of LabVIEW found on the system.
Or
      2. Copy the the "<previous LabVIEW>\vi.lib\Daq" directory and all it contents to a new "<LabVIEW 2010\vi.lib\Daq directory. This way you can use Traditional NI-DAQ in both versions of LabVIEW.

I didn't have DVDs, I had to download.
Yes it was a mess. The device driver download took forever (NI can't help that). The installation took beyond forever (what else can be done?).
I was disappointed that I had to do all of this backing up of legacy folders and restoring them after installing the device drivers. Why does NI always have device drivers and toolkits install to the latest version of Labview only? Why couldn't they leave the legacy stuff alone?? I still use LV2009 and wanted to try LV2010. This involved a whole lot of trouble and time.
NI needs to provide a much easier way to upgrade, while still allowing previous versions to work without modification. Most people who upgrade will not completely abandon the older versions.
- tbob
Inventor of the WORM Global

PCI-6024E Traditional DAQ Control

I made the attached VI "Digital IO Testing" using the DAQ assistant. I want the traditional DAQ equivalent to turn these specific digital output channels to high/low.
How can this be accomplished. I have no idea what a port/group/line/etc is. The help menus for traditional daq is confusing me....
HELP
Attachments:
Digital IO Testing.vi ‏152 KB

Good Afternoon,
I have attached a knowledge base article that directs you to the Traditional DAQ examples within LabVIEW. These will help get you started. Hope this helps!
Traditional DAQ Examples
http://digital.ni.com/public.nsf/allkb/46D0C7360A10D25F862571B5007B4411?OpenDocument
-Cody C

Is there any incompatibility between Labview 8.5 and Traditional DAQ?

Hi, I`m using a DAQPad 6020E and the Labview 8.5 Daq assistant don`t detecte my DAQ when a try to create a new task (to create a new virtual chanel). But MAX detect the DaqPad. So, is ther any incompatibility between Labview 8.5 and traditional Daq? Do you know how can I resolve this?
Thanks.

First, you posted to the wrong board. Measure is an old add-on for Excel.
Second, there is no incompatibility between LabVIEW 8.5 and tradtional DAQ. There is an incompatibility between traditional DAQ and DAQmx which is what the DAQ Assistant uses. Make sure that you install DAQmx if your device is supported by it. Otherwise, you will not be able to use the DAQ Assistant.

I do not have the daq assistant vi on my labview 2010 and have found no drivers for it what should i do

I do not have the daq assistant vi on my labview 2010 and have found no drivers for it. I downloaded the service pack but that did not have it either what should i do.

Hi Youzhang He,
Did you install LabVIEW first on your PXIe 8102 before the drivers? Most likely, you're missing LabVIEW support for your DAQmx drivers. Fortunately, this is an easy fix. What you should do is open Add/Remove Programs, select National Instruments Software, select Uninstall/Repair. In the window that pops up listing NI software, select NI-DAQmx 9.x and select Modify. In the window that appears, expand Application Development Support and select to install LabVIEW support. From here complete the install process and restart your system. LabVIEW support should be installed and DAQ Assistant should appear in your palette.
Allie

Can I install an older version of traditional DAQ that support legacy DAQ with DAQmx for support of a new card?

I have a LabPC+ that works fine, but is not supported in the latest versions of NI DAQ. I also have a 6024E that I would like to use. I know that the version of DAQ that supports the LabPC+ also supports that 6024E, but I would prefer to use the latest DAQmx with this. Is this possible?

Hi Brain:
Doesn't look like it, the PC+ will only go up to 6.9.3 tradition DAQ
http://www.ni.com/support/daq/versions_legacy.htm
while the 6024E will go up to 7.4.1 traditional or 7.5mx or 8.0mx, dependiong on OS.
http://www.ni.com/support/daq/versions_pci_pxi.htm
I assumed these cards were PCI based.
I am not a DAQ expert, so hopefully someone can verify this.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Will the ELVIS board work with LabVIEW 2010 Student Edition?

I recently acquired a traditional ELVIS board (with the PCI DAQ board). So far I've only installed the evaluation for LabVIEW 2010 (x64), and when I attempt to install the ELVIS Traditional 3.0.5 software I get the following message: "This installer requires LabVIEW 8.5 Full Development system or later to be present on this computer. LabVIEW Base Development System in any version of LabVIEW is not supported. Please install LabVIEW and then run the NI ELVIS installer again."
I am eligible to purchase a student license for LabVIEW 2010 and would like to know if the ELVIS Traditional 3.0.5 software will install after I've acquired a student license.
I am running windows 7 (x64) with an evaluation version of LabVIEW 2010 (x64).
Solved!
Go to Solution.

Perhaps I spoke too soon. I purchased a student license for LabVIEW 2010 and am still receiving the same error. I've provided screenshots of my license and the message from the ELVIS Traditional 3.0.5 installer.

VIs worked in LabVIEW 2009 but do not work in LabVIEW 2010

The VIs were originally written in LV 7.1 but then compiled in LV 2009 and saved. These VIs worked fine on Windows XP machine.
Unfortunately, the XP machine was crashed and I am trying to run these VIs in LV 2010, with windows 7, 32 bit.
I have installed traditional DAQ drivers (latest version, 7.5) alongwith DAQmx (version 9.8).
We use these VI to control the vacuum valves, using PCI 6503.
To initiate we first use a VI that reset the valves and the PCI card. The name of the first vi is: portconfig.vi This vi uses port config and port write VIs. I see the error 10401 from port config vi, when I run step by step (i.e., sequence 1). However, the VI runs but not doing any actual work.
The second VI that depends on first VI, and therefore the second VI is also not working. on this VI we have buttons (representing valve) and when we click on them, the valves should shut off or open, but nothing happens in LV2010. the same VIs worked in LV2009!
PCI 6503 card is defined under devices and interfaces in MAX. It is not defined under legacy DAQ devices. When I test PCI 6503, it works.
I am attaching both the VIs (there are in QuadMain.llb). I dont know how to get the actual VI from the harddisk...
first open portconfig.vi
then open Control Panel.vi
there are global variables used in Control Panel.vi, there are listed in Valve Global.VI, which is in globals.LLB (second attachement).
I really appreciate if someone can convert these VIs for LV 2010.

Jpdas06 wrote:
Yes, I am doing that. But this is holding up the experiments. So I thought an easy fix for now and then once the work load goes down i can concentrate on changing the port config.vi using DAQmx.
I would really appreciate if you or someone can provide me steps for listing PCI 6503 as both types in MAX.
Thanks again.
You should be able to see the DAQ card in both driver interfaces DAQmx and Traditional DAQ. I just checked on one of out test fixtures. We have MAX 5.6, DAQmx 9.8 and Traditional DAQ 7.5 on Windows 7 32-bit. We use LabVIEW 2013 executables on this PC, but this really doesn't matter.
I believe the only exception, when you don't see cards in both drivers, is when the card is supported in DAQmx only. But in your case this card (PCI 6503) is supported by DAQmx and TDAQ.
I had some issues before renaming devices in Traditional DAQ. If you have more than one card, the device names not always match in both drivers. You could have one card for example as Device 2 in TDAQ and then as Dev 4 in DAQmx.
I would uninstall and install again the Traditional DAQ driver. I never added cards manually to the drivers. This should happen automatically.

Using LabVIEW 7.1 and LabVIEW 2010 on the same PC (Windows XP)

I have LabVIEW 7.1 on a Windows XP 32-bit PC and we plan to upgrade to LabVIEW 2010 soon. A lot of our software is using Traditional DAQ, DAQmx and DeviceNet. We need to use both versions of LabVIEW for some time on the same PC. Is this possible at all?
I installed an evaluation 2010 version and now I don't have DAQ and DeviceNet in LabVIEW 7.1. Any suggestions will be very helpful.
Thanks, Nick
Solved!
Go to Solution.

For what it is worth, I tried having multiple versions of LabVIEW on the same PC. If you are (very) careful, it is possible to do so, as long as you are only doing development work, i.e. you don't try and install LabVIEW drivers. However, as I've discovered to my great sorrow (which involved installing and removing various versions of LabVIEW on the same machine probably 5-8 times, eventually leading to wiping the machine and installing WinXP all over again, then only one version of LabVIEW), if you want to actually run your code, particularly if it does anything with hardware, you need to stick to one version!
There's another "gotcha" for those of us working with "older" versions (namely before 2009, though one can "trick" 8.6 if you're careful) -- Windows 7 doesn't "play well" with the older software!
So my development machine runs Windows 7. I have a VM of Windows XP in which I installed LabVIEW 7, which I use for my "legacy" work -- I use the Win 7 machine for LabVIEW 8.6, 2009, and 2010 development (and only development, see above).
The machine that got "rebuilt", where I wanted to run LabVIEW code for various hardware and potentially various LabVIEW versions, I did a really nutty thing -- I created a quadruple-boot PC! (It really is a triple-booter, as the Windows 7 system, which is the key step, is "hidden"). To make this work properly, I needed three hard drives in the machine (one for each OS -- I might have figured out how to put two XPs on a single drive, but since I already had the disks, one-OS-per-disk seemed easier). I'm using Windows 7's Boot Loader to give me the startup choice of which system to use (the message says something like "System for Hardware A", "System for Hardware B", "Test System"). True, you need to do a Restart, but since you're going to be collecting data, it's not such a bad idea to start with a "fresh machine".
[I did think about doing this with Virtual Machines, which would have been much simpler, but I didn't have "virtual drivers" for the hardware! One piece was actually a USB device, but the other was a proprietary device that plugged into my PC ...]

Can't use Daq Assistant in Labview 7.1

hi! I have Labview 7.1 installed and an AT-MIO-16E-10 NI board. I can see the board in MAX\devices&Interfaces\traditional NI-DAQ but i can't run any tests(Test panels). I don't know if this is normal for this NI-DAQ model. anyway my main conceirn is that i can not use DAQ Assistant in LabView(when i double click on it or right click->Properties nothing happends). So i can't use my board in LabView. please help! thanks a lot

You can use your board in LabVIEW but you can't use it with DAQmx. In the DAQ Quick Start Guide, the supported devices are listed and the AT E series is only supported with traditional DAQ.

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

How to simutaneously use 2 PCI cards, one with traditional DAQ, the other with DAQmx?

Hi,
I am currently trying to debug a system that used to work.. but sadly isnt anymore
A single computer contains 2 PCI cards (6110 & 6036E). The 6110 card is controlled by a fairly old software, programmed in labview, and hence, using Traditional NI-DAQ. The 6036e card is controlled by a more recent soft, programmed in LV as well but using DAQmx.
the AI/AO of the 6110 card is only momentarily used (20 sec consecutively, every minute) while the 6036E card is continuously receiving and sending data on its AI/AO.
Now the problem: the program that control the 6036E card freezes every time that the old prog access the 6110 card.. and then it works again perfectly until the next time that the 6110 card is used.
So my question: how can I make those 2 cards work simultaneously?
I dont think that it is because of the software nor because of the computer lack of memory/CPU if it used to work in the past. It might be about a wrong configuration of cards in the MAX but I couldnt find anything wrong there (no problem when accessing AI/AO of both cards through "test panel")
Thank you very much for you help.

That's what bugs me. The only thing that those 2 cards share is an AO of the 6110 connected to an AI of the 6036.
For the rest, nothing is common. The 1st program only deal with device1, while the 2nd prog only access dev2. There shouldnt be any problem and everything is working fine separately. Hence, why I was wondering if the traditional daq and daqmx might conflict on a same computer.
I just cant find out why the 2nd program controling the daqmx card just freeze everytime the 1st program access the traditional card. It actually doesnt freeze completly but becomes soooo slow, with about only 2 iterations of the main while loop during those 15-20 sec (instead of the normal 3-4000 iterations during such a period).
The computer specs are a 2.2ghz proc for 1G of ram and running XP, so it should be ok.. even though the computer does slow a bit down when the 1st prog access the traditional card.

3D graphs cause LabVIEW 2010 to hang

I've been using LabVIEW 2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work. Right-clicking on the window does not show a context menu. The main menu doesn't work. The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit. I have to kill the process in Task Manager.) It is the same story with just a plaing 3D picture indicator. Also, the solarsystem.vi example does not work either. The problems start as soon as I open the solarsystem.vi. After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7. I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion. The Mac drivers are all updated. Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
After searching the forums, I've tried all the other potential solutions I could find: 1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero.
Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.
Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed. The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
Solved!
Go to Solution.

Yep, it's the same virtual machine. I set it up almost 2 years ago and it has been extremely stable. Both LabVIEW 8.5 and 2010 have been perfectly happy on it. It's a great way to do LabVIEW on Win7. I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion. I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard. The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
I happen to have an XP virtual machine too, but I haven't installed LabVIEW there. Let me know if that would be a worthwhile test.
You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
The video card is the original stock:
NVIDIA GeForce GT 120:
Chipset Model: NVIDIA GeForce GT 120
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0640
Revision ID: 0x00a1
ROM Revision: 3386
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Display Connector:
Status: No Display Connected

Traditional DAQ and SCXI 1530 model name

Hi all,
I am using Labview 6.1 and Traditional DAQ 7.1. I am working on one system with one DAQ card (PCI 6052E) and several SCXI cards(1520, 1530). All the SCXI cards are installed correctly because MAX can detect them all.
I want to make a program with Traditional DAQ which can detect all the SCXI cards and show their model names on the front panel.
I found in Tradtional DAQ, there is one VI called "Get SCXI Information" which returns the model types of SCXI cards, something like, 50, 51....
I found in the help file of "Get SCXI Information" VI there is some kind of the configuration file saying 51 stands for SCXI 1520. What does 50 stand for? Where can I find the complete configuration file or somehow can I change it? Like make 51 stands for something else...
Any ideas are highly appreciated.... Thank you all!
Solved!
Go to Solution.

This is a duplicate of the last post in this thread: http://forums.ni.com/ni/board/message?board.id=250&thread.id=53087
Brad Keryan
NI R&D

Tradition DAQ installed but unavailable

Hello,
I have a system that had LabVIEW v6.0.2 executables running with NI-DAQ 6.9.3f3 with a PCI-6052E. I have now installed LabVIEW 2009 with both Traditional NI-DAQ 7.4.4 and NI-DAQmx 8.9.5 on this system. My 6052E shows up in MAX under both NI-DAQmx Devices and Traditional NI-DAQ (Legacy), but under Legacy, the 'Test Panels...' button is grayed-out and if I get the properties of this device, the subsequent dialog's 'System' tab has the resources box grayed out as well as the 'Test Resources' and 'Run Test Panels' buttons grayed-out. I've tried resetting the device under DAQmx, but it doesn't help. I have run a self test of the 6052E by right-clicking the device under DAQmx and it passes.
Another problem I've noticed is when I try to run any traditional LabVIEW DAQ example, I get the following error repeatedly: "Error loading "C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\Daq\lvdaq.dll". A dynamic link library (DLL) initialization failed." This occurs for every traditional DAQ VI that tries to load.
LabVIEW DAQmx examples load and run fine.
This sounds like a corrupt NI-DAQ (Legacy) installation. My goal is to get my code running under the latest NI-DAQ (Legacy), and then transition to DAQmx. What is the best way to proceed getting this new NI-DAQ (Legacy) to run?
Thanks,
Greg
Solved!
Go to Solution.

Got the problem solved by repairing the NI-DAQ 7.4.4 (Legacy) install via Windows 'Add or Remove Programs'.
Greg

Traditional DAQ support in LabVIEW 2010?

Similar Messages

Maybe you are looking for