DAQ vis not in vi.llb

I just installed 7.1, and the DAQ vis no longer appear in the vi.llb. Did I miss checking an option?

If you did a custom installation and selected only LabVIEW, or canceled when it asked you to insert the DriverCD, no drivers were installed.
You can install individual drivers from the DriverCD that shipped with the LabVIEW 7.1 CD, or can download the latest NI-DAQ from our web site:
NI-DAQ Version 7.2 for Windows 2000/NT/XP
Zvezdana S.
National Instruments

Similar Messages

DAQ vis don't appear in LabVIEW

Hello,
I have a simple DAQ card and installed NI-DAQ onto the computer. Afterwards I installed LV 6.1. Why do the DAQ vis not appear in the function tool box?
Thanks for helping.
Regards,
Jerome.

You did things in the wrong order. You need to install NI-DAQ after you install LabVIEW. If the NI-DAq installer doesn't find LabVIEW, it won't install the functions.

How can I make DAQ VIs visible when using NI-DAQ 4.9 with LabVIEW 6.0?

My operational system is Windows 98, I am using a AT-DSP2200 card and is configured. I have installed a NI-DAQ 4.9 (the last for this card) and I use Labview 6.0, but I can not find the DAQ VIs on the functions palette. How can I solve this?

Hello;
That version of the driver is too old to work with Labview 6i. The oldest version of NI-DAQ that one can combine with Labview 6i is version 6.1.
You will need either to use another version of Labview, or to investigate a replacement hardware that you can use with newer versions of NI-DAQ.
Regards
Filipe A.
Applications Engineer
National Instruments

Daq do not appear at measurement i/o

I've just instaled My DAQ6009 and my labview, and the DAQ do not appear at measurement I/O on labview functions palet. It was working before when was instaled at my old computer.
The daq6009 is appearing at MAX tree.
Does anyone knows what can be happening?
thank you
Solved!
Go to Solution.

What version of LV are you using?
You must install NI DAQmx driver so you can use your device.
The link below has this driver so you can download and install it.
http://joule.ni.com/nidu/cds/view/p/id/2337/lang/en
Thanks.
Best Regards
Luciano Borges
R&D Engineer
Pirelli Brazil

NI DAQ card not find PXI-4070/PXI-6602

In the course of daily use, I found the acquisition card is often missing, does this problem how to solve?

The Version of your NI-DAQmx Driver?
--> 9.1.5
Whichever Operation System are you using?
--> It wasn't working on Windows XP. I now installed Windows 7 (32 bit) and it is still not working.
Do you try to set the PXI-6122 in another slot of your Chassis? What happend then?
--> The problem is not related to the PXI-6122 card, but rather to PXI cards (and maybe HP computers) in general, as I found out in the meantime:
http://forums.ni.com/t5/Multifunction-DAQ/DAQ-cards-not-selectable-although-listed-in-MAX/td-p/12426...
When I put the card into another slot (there were only two free slots), the PC didn't boot anymore.

The program can't start because nidaq32.dll is missing from your computer. Try reinstalling the program to fix this problem. Notes: DAQ is not installed.

Notes: DAQ is not installed. M&A Explorer has been Refreshing for the last half hour.

Thanks for your responses. I thought this error had something to do with the fact that I hadn't installed the I/O card yet.
This computer controls a piece of test equipment. The application software is supplied by the equip. mfg. who specifically stated to install NI driver, then their application software and finally the card. I would of thought the card would of been installed first then the driver. I've not worked much with I/O cards and their drivers before.
The error code went away and I was able to run the application software.

Visa not working after compile?

Im using visa in my application. Iim doing reading and writing.
My .VI works when its not compiled. And after i have Compiled it it no longer works ive tried looking for any infor on setting up visa.
So now i am here.
Anyone ever have the same problem.
-Kurt
Solved!
Go to Solution.

The most common problem with exe vs debug applications is file paths. If you are doing file io and using paths relative to a vi then you will have some trouble. If you are using the same PC then there shouldnt be a problem with visa not being installed. Do you get any error messages to clue you in on the source of the error? Do you have any error handling (passing error clusters and handleing them) in the application?
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

DAQ Solutions not available on NI8176

DAQ Solutions not available on LAbview 6.1,DAQ Solutions button not highlighted cant be selected on opening Window. Hardware listed below.
- Installed on Embedded Controller NI8176/W2K.
- in PXI-1011 Chasis, NI 4472 in PXI slot, using a 6052E DAQ Card, SCXI Modules - 1540, 1520, 1102

Hello;
If you had another version of NI-DAQ installed before upgrading Labview to version 6.1, the best way to go about that is to uninstall NI-DAQ completely, and install the 6.9.2 version of the driver that goes with the Labview CD. To do that, just run the Labview installer and select the NI-DAQ driver from the list (choose custom install).
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

I'm working on DC Motor control using DAQ. There is sufficient voltage output from DAQ but not current. What should i do so as to drive the motor

I'm working on DC Motor control using DAQ. There is sufficient voltage output from DAQ but not current. What should i do so as to drive the motor. Could you suggest me appropriate driver IC using which this problem can be solved.
Saravanan.T

You really should use a DC motor controller to control a DC motor, look at the 754410 IC for a good example. You should be able to interface these to most DAQ devices.
Alan

Rename all Vis in a library(llb)

Hi,
How can I automatically rename all Vis in a Vi library in LabVieW 5.0.1?
My application must change all the names of the Vis in the Library and update all the callers to use the new names so that it won't request me to find the new Vi when I run the application.
Any help would be most appreciated.

I'm not sure if LabVIEW 5 has everything you need, but I think it does. Still, it's a good idea to upgrade if you can. To answer your question, here's what I would do. First, make a backup of your LLB just in case.
1) Load up the top-level VIs. A top-level VI contains all the other VIs in the library as subVIs in its hierarchy unless you have multiple top-level VIs. Just make sure all top-levels are open so that they are in memory.
2) Now create the program to do this renaming. The program should first use the List function to list out the names of all the VIs in the Library. You'll want to feed the List function the full path to the library as an input.
3) Now that you have the file names of all your VIs, you can rename them with VI server
funtions. The list of VI names is an array. Feed that array (indexed) to a FOR loop so that each iteration peels off one VI name. Feed that VI name to an Open VI Reference function. Wire the resulting reference to an invoke node. Select the "Save Instrument" method. There will be an input for a new file path. Build the new path (Build Path function) using the existing path to the library and the new name of the VI. I'm guessing that the new name can be derived from the old one somehow. Maybe there a prefix or something? After the invoke node, close that VI reference. After the close, use a Delete function to remove the old VI.
That should do it since the top-levels were in memory the whole time. When the VIs get saved with their new names, the VIs in memory are automatically updated as long as you save them too.
If what I've described sounds too advanced for you, consider hiring an Alliance Member to help you out. We do this stuff every day.
Daniel L. Press
Prime
Test Corp.
www.primetest.com

Using Open VI Reference to run a VI, on an RT target, with sub-VIs not loaded

I've been using Open VI Reference and Call By Reference Node to remotely run VIs on my RT controller. I
usually wire string data to the vi path input, but this
requires the VI to be in memory. I understand (from LabVIEW help) that I can wire a path to this terminal and specify a VI that is
not in memory, but is on the disk. NI has an example that
confirms my understanding. I get errors when I attempt to do the same
with VIs that have sub-VIs; I suspect that the problem is that
the sub-VIs aren't in memory and that the top-level vi doesn't know where to
look for them (because the paths aren't specified). All of the sub-VIs are on the RT system (in the same directory), they're just not in memory.
Is there a way to get LabVIEW to look for sub-VIs on the disk? I don't want to rely on using a startup application and rebooting to get my VIs into memory.
Thank you,
Jim Carmody
Software Engineer
G2 Technologies
www.g2tek.com
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

Hi Jim,
It sounds like you are going about calling VIs remotely the correct way. It would be very helpful if you could post the errors you are receiving. I also wanted to know if you saw the note at the bottom of the article that says your VI library must contain everything your top level VI calls.
Eric A.
National Instruments
Distributed I/O Product Support Engineer

Characters from VISA not in ascii

I am using ARM Cortex Microcontroller. I am sending the numbers into lab view through usb port.
In such case, the strings obtained from VISA Read are not ascii but i can convert them into unsigned int with the help of string to uint premitive.
The numbers to be sent are continuous and they consist of u8, u16 and also float values.
So the problem here is the conversion. only those value which are defined as u8 are displayed correctly.
How do i convert into appropriate values.
E.g. if the value is integer but greater than 255 i should be able to read and display.
If the value is float i should be able to display the proper float number.
I also tried with scan string premitive, also string to number premitive. They can only read ascii and convert, but the characters i am converting are not ascii.
The characters i am receiving look like boxes and for a value of 0 they are empty space.
To convert a number into ASCII in my microcontroller could also be possible but the requirement here is with lab view. Microcontroller currently has huge load of programs.
I would be happy if someone whould help me in this.
Thanks in advance.
Solved!
Go to Solution.

Sorry for the mistake to write it is string to byte.
The necessary clippings are as below. The second clipping 'read buffer' is from a series of transformation where, first data is 300, second is 1 and third is 1.23. The output for these as seen in the third picture is 44, 1 and 1. Yes, 300-256 = 44, previously i wrote 45.
According to you, do you mean that the first two byte should correspond to 300 ? and also similar for the float (not only one byte value but with several values in consecutive elements of the array)?
I would be happy if similar clips would be avialable.

DAQ browser not working in compiled exe

I have built an executable of my code. It installs on a non-LabVIEW PC fine, but throws the error in the attached image. Previous releases of this software worked fine. I added functionality of being able to select a DAQ device/port/line shown in control line.jpg. That control is for a sub-vi in my code.
When I did a search for the attached error:
"Cannot load the Browse dialog. Some necessary components are missing. To correct the problem, reinstall the drive software that is associated with this control"
. . . I found the same error in reference to a Fieldpoint IO Point causing this problem in an exe with steps to solve the issue, but could not find anything related to DAQ IO.
Any thoughts and/or suggestions would be much appreciated. I would like to allow my user to select which DAQ port he wants to control.
-Aaron M. Baumer
Aaron M. Baumer
Attachments:
Browse error.JPG ‏145 KB
control line.JPG ‏12 KB
Toggle Line.vi ‏20 KB

Hooovahh wrote:
You say you have an installer for this, in the installer did you choose to include the DAQmx components? You say it worked fine before which makes me believe that the DAQmx components were installed before. If they were not then you will need to include them in the installer. Expect the installer to go from 200MB for EXE and run-time to probably 800MB to 1.2GB with the DAQmx components being included.
I did a manual install of DAQmx on the pc in question before, but this time I included DAQmx in the installer anyway (and, yes, it is now a 1.4Gb file!). Anyway, I'm having my guy onsite install that version to see if it helps, but I have a feeling it will not. It's the same error as here (also here). so I think it may require a similar workaround.
Almost forgot, I'm running LabVIEW 2012.0f3, MAX 5.3.1f0
Aaron M. Baumer

Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

PCI-6703 on MAX traditional daq but not on daqmx

Im using MAX 3.1.1 (with NI DAQmx 7.3.1f0) and its listing my device 6703 on the traditional daq list but not on the DAQmx. I'm trying to utilize the Express VI to use this card but since it does not apear on the list I can use it. I already tried F5 several times.
Thanks fot the help.
--Aaron

PCI-6703/6704 are supported by traditional nidaq, and nidaqmx 7.4 and higher.
They are not suppoeted by NidaqMx 7.3.
if you want to use Nidaqmx, upgrade to the latest NIdaq driver.

DAQ vis not in vi.llb

Similar Messages

Maybe you are looking for