LabVIEW Imaqdx vi's Missing

Hi Guys,
I installed LV2011 with VDM 2011, installed imaqdx drivers too and installation was successful. But in functions palette the imaqdx vi's are missing.
Note: I reinstalled the driver twice the time and i also installed Latest driver downloaded from online (VAS_September_2011). Still seems to be not showing up. Please provide me any directions to resolve this issue. (Personnel: Is it a kind of BUG?)..
Waiting for replies.
Sasi.
Certified LabVIEW Associate Developer
If you can DREAM it, You can DO it - Walt Disney
Solved!
Go to Solution.

Hi Guys..
I found this article helped me http://digital.ni.com/public.nsf/allkb/A451D3CCBB740716862578FC004DB392. After activation, installed once again the latest driver.
Problem Solved !!!!!!!!!!!!
Sasi.
Certified LabVIEW Associate Developer
If you can DREAM it, You can DO it - Walt Disney

Similar Messages

The labview probe button is missing in the diagram view?

any ideas why the labview probe & is missing i the diagram view of one Vi?
Solved!
Go to Solution.
Attachments:
MissingButtons.JPG ‏17 KB

You have it switched off in the VI properities. Probably disabled debugging.

Windows 7 Compatability with Labview 8.0 and missing files while interfacing the FPGA with LV

I am trying to use an FPGA (PCI-7830R) with Labview 8.0. The computer has Windows 7 OS. I installed LV 8.0 in the proper order with the FPGA Module and labview is able to see the FPGA when I open a .lvproj (the FPGA is in the tree) however there is a warning symbol next to the FPGA selection and when I try to open a .vi file that is used on the other stations in my lab (it works on all the other stations), labview is unable to find a whole bunch of files. There are some pictures.
Missing File (there are a bunch more but this is the fist one).

According to this LabVIEW Compatibility LabVIEW 8.0 is NOT compatible with Windows 7
Visualize the Solution
CLA
LabVIEW, LabVIEW FPGA

Bug? LabVIEW-2009: Boolean wire missing some dots

I opened a VI from someone asking a question on this forum and noticed some missing dots on two boolean wires.
This was opened using LV 2009. It's an Evaluation installation (in case someone is wondering about specifics).
I minimized and maximized the block diagram and the dots were okay.
I don't know if this was already reported.
R
Message Edited by Ray.R on 10-08-2009 06:06 PM
Attachments:
missingLine.PNG ‏45 KB

Ray.R wrote:
LOL! Imagine all the people that would need help if we came up with wireless wires...
Of course we could also ask for underground wires that could be threaded below the diagram for some busy areas where they are not needed.
Message Edited by altenbach on 10-09-2009 02:07 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
WireTunnel.png ‏2 KB

New Hardware / DAQmx Install, LabView 7.1 Now Missing DAQmx VI's?

Hello -
I've been running Labview 7.1 and some applications we've built with it for some time now. Due to an old DAQ board failure, we had to upgrade. Upon receiving the new (PCI-6225M) DAQ board, we had to update DAQmx (to 8.9.5) in order for this new board to be supported.
In doing so, it appears that the DAQmx VI's I had for Labview 7.1 were actually removed from the system. When I try to load my 7.1 applications, I get errors saying that it can't find various DAQmx VI's (like the DAQmx Create Task and Read VI's). Since it allows me to browse for them, I browse to the directory structures that *do* have them now (intended for LV 8.2+, which we don't have). If I select these VI's they seem to be found okay, but then I get an error for each VI saying that it's only for a newer version of LabView, not v7.1.
So what gives? What can I do? Why on earth would a newer DAQmx installer actually go in and remove already existing files from my previous install that previously worked fine? I am not impressed. What should have been a simple board upgrade now appears to be setting us back some significant time.
Thanks,
Brett

Hi Dennis,
I also have common issue. I am using labview 7.1 with DAQmx version 8.8. Recently, I just bought the cDAQ-9178, which requires me to upgrade my DAQmx to version 9.4. After installation completed, I discovered all my DAQmx missing. My question is:
1. Do you have any patch to let me stay @ LV version 7.1 with the new DAQmx 9.5 without missing DAQmx vis? I need the new DAQmx to be able to connect with cDAQ-9178.
Thanks you for your time, Dylan

Labview 6 xmathtypes.dll missing

Hi,
I am trying to run Matlab script (Matlab version I think it is the latest one) from Labview 6.1. Initially it wasn't running. Then I came across this thread
http://digital.ni.com/public.nsf/websearch/CE309627064A3D5686256A9C005B0A5F?OpenDocument
and replaced the two script files (hiqscript.dll & matscript.dll) (in Labview6.1/resource/script) with three new files mentioned in that thread (matscript.dll, xmathscript.dll & XmathTypes.dll). Created a matscript with code given in Labview help
a=rand(50)
surf(a)
After running the code it shows me the plot. So everything works up to that point.
The problem is:
Whenever I right click on the matscipt (to add input/ouput) (even if I right click on a blank matscript), it gives me this error
" Labview.exe unable to locate component"
"This application has failed to start because XmathTypes.dll wasn't found. Re-installing the application may fix the problem."
Also somebody metioned in other thread to place a copy of that dll file (xmathtypes.dll) in system 32 folder. But not any help. I have already repaired the labview 6.1 using the labview cd. But the problem is still the same.
I have winows XP pro version installed on my desktop. I checked it on vista premium too. But the same error is popping up.
In our lab we have labview 8.5 and in that everything works fine.
But since all the drivers and code are written in labview 6.1. So I want this to be done in labview 6.1.
Thanks
Raj
Message Edited by Tablet on 02-12-2009 01:09 AM
Solved!
Go to Solution.

It finally worked.
Solution:
Placed all the three dll files in the system 32. After thateverything works fine

Labview 2013 daq assistant missing

I can't see the DAQ assistant in Labview 2013!
Labview 2013 + real-time + fpga
Max 5.5.1
Visa 5.4.0
Device driver august 2013
Why?
Thanks
Solved!
Go to Solution.

Did you install DAQmx AFTER installing LabVIEW? Can you see any of the DAQmx palette?
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Vision Acquisition Software installed, BUT why is the IMAQdx missing from the function palette?

I just installed to the labview 2011, and many other modules and softwares including this VASAugust2010. But the IMAQdx is missing from the function palette (vision and motion). However the NI-IMAQ 4.5, IN-IMAQ IO 2.4.0 and NI-IMAQdx 3.7 are all clearly listed as installed in the NI software (contorl panel -> program - NI). In MAX, my usb webcam is also listed as NI-IMAQdx Devices and works well under MAX. But my own program is broken because the LV can't find those functions. So why the IMAQdx funtion is missing and how to fix it?
Thanks,
Lei

hi tommy
check this may helps you http://digital.ni.com/public.nsf/allkb/A451D3CCBB740716862578FC004DB392
Sasi.
Certified LabVIEW Associate Developer
If you can DREAM it, You can DO it - Walt Disney

Use of APT objects in 64-bit LabVIEW

I have created an APT motion control VI to control a translation stage using 32-bit LabVIEW. However, I have since had to move to 64-bit LabVIEW. I am trying to create a similar VI that will run on the 64-bit version. The problem is when I create my ActiveX container and try to use MGMotor control to connect to the motor, MGMotor Control is not in my list of creatable objects.
Is this because it is not possible to access this particular motor in 64-bit LabVIEW or am I missing drivers that I can download to update the list of creatable objects?
P.S. I am relatively new to LabVIEW but any help at all would be great!

Hi,
What is the reason you have moved to 64bit LabVIEW? It could be that this driver is not supported on 64 bit LabVIEW but this would have to be confirmed by looking at the driver's requirements. 64 bit LabVIEW currently does not support every thing that 32 bit does but this is being worked on. Can you provide some more details of this motor driver.
If you have recently installed your new version of LabVIEW then you will need to reinstall the driver again. If you can provide some more details on the driver then perhaps we can find out if it is compatible with 64 bit LabVIEW
Best regards
Matt Surridge
National Instruments

Browse Projects button is missing

On the LabVIEW "Getting Started" window, in the "Open" section which shows recent projects and files, there is a Browse button at the bottom which broses all LabVIEW related files.
Missing is the "Browse Projects" button under the projects section. This is a little thing that will save many people a few seconds every time they open LabVIEW to look at their projects. I have a lot of projects and have to go back and forth to support the users of the software executables created by those projects.
Please add the "Browse Projects" button to the LabVIEW "Getting Started" window.
Thank You
Robert Thebert

I don't understand what you think is missing.
If you hit the Browse link on the Getting Started screen, you get a file dialog box. It includes all types of LabVIEW files include .lvproj project files.
Attachments:
untitled.PNG ‏157 KB

Vision 8.2.1 and standalone applications

I recently upgraded to Vision 8.2.1 (still running LabVIEW 8.2), and subsequently modified a vision acquisition VI to take advantage of some of the new IMAQdx calls. The modified VI works fine, and the executable built from it works fine. However, I have rebuilt a standalone installer for this application, and after installing the app, a co-worker is unable to run it. The machine we're attempting to run it on does not have Labview installed, but we have purchased the license for standalone Vision applications for this machine, and it activates successfully during installation. Also, I have built the installer using the the 8.2.1 Vision RTE, so I know that's up-to-date. We were previously able to run the earlier version of the application built using Vision 8.2 on this machine with no problems. On the first attempt to run the new app, we received an error message indicating that niimaqdx.dll couldn't be found. So I located that dll on my machine and copied it over. Now, when we try to run the installed executable, a dialog box reports that several IMAQdx subVIs are missing. The exact message is:
"Missing subVI IMAQdx Discover Ethernet Cameras.vi in (my VI name here).vi
Missing subVI IMAQdx Enumerate Cameras.vi in (my VI name here).vi
Missing subVI IMAQdx Open Camera.vi in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI (one of my subVIs) in (my VI name here).vi
Missing subVI IMAQdx Get Image.vi in (my VI name here).vi
Missing subVI IMAQdx Unconfigure Acquisition.vi in (my VI name here).vi
Missing subVI IMAQdx Close Camera.vi in (my VI name here).vi"
Also reported missing are a couple of subVIs that I developed myself --- but only ones that have been added to the top-level VI since updating to Vision 8.2.1!
The project is composed of several layers of subVIs, and I can't post the project here. So, as a test, I made a simple dummy VI and project, which simply has a call to Discover Ethernet Cameras and a call to Enumerate Cameras. I then built an executable. I then built an installer. After installing to a PC without Labview, the resulting application has the same error. I've double-checked all my project settings, and they all seem ok. In fact, the settings haven't changed since my working version, with the exception of the "Additional Installers". The only changes there are the selection of "NI Vision Run-Time Engine 8.2.1" instead of 8.2.
Attached are the test VI and images of the error dialogs. I believe anyone can recreate this error by simply starting a new project, adding the attached VI (or any VI using IMAQdx calls), building an installer, then installing the application on a machine without Labview (you will need a licensed Vision run-time).
Any clues? I desperately need to resolve this issue, because the application in question is an important tool used by my co-worker. Hopefully, it's something simple that I'm overlooking.
Attachments:
test imaq.vi ‏8 KB
errors.JPG ‏38 KB

Ceger--
    The question is really what type of acquisition system you have. What type of camera and how is it connected to your computer. Since you didn't mention having a 1394, or firewire, camera or license, I am going to assume that you are using a plug-in frambrabber. The reason that I ask is that if you are using our hardware (i.e. a frambrabber) the cost of the license is included in the purchase. So you do not need to purchase a lincense for the IMAQ software, it's free, since you need a framegrabber to use it.
      On the other hand, if you have a Firewire or GigE camera that can plug directly into the computer then you have to purchase a license for this driver software, named IMAQdx.
   I can think of two possible reasons why you are getting the error, the first being that you have a framegrabber and so do not have a license for IMAQdx for the deployment computer. If you have a framegrabber you shouldn't need to use IMAQdx for any reason. The next being, since it is saying that so many of those files are missing, that you have not included IMAQdx into the installer. IMAQdx is separate from IMAQ and if you need to use IMAQdx then you need to include this into the installer.
      Please, let me know if any of this sounds like it could be what is going on and please post back with any questions so that we can get this figured out and get you back up and running!
Regards,
John H
Applications Engineer
National Instruments

Open/close keyboard error

Hi, I was wondering if anybody had any experience with an error like this. I have a Labview made Application that is experiencing some conflicts after installation on a Windows 2000 machine. Bare in mind that it has been successfully installed on 2000 machines in the past. The problem is that when the application is run, the user receives a message that reads,"Select sub.vi to open keyboard". I don't believe this refers to a sub vi called "sub.vi" but a sub vi in general. Could there be a conflict with the keyboard drivers? I unfortunately am not a first hand witness, so this is all the info I have. Could a USB keyboard cause errors like this or something?
Glen D

Evan,
Thank you for all your suggestions. The exact error messages our customer is receiving are 'Select sub.vi to open keyboard' and 'Select sub.vi to close keyboard'. These errors occur when the exe is tried to run. By no coincidence, two of the vi's in this exe are called "open keyboard.vi" and "close keyboard.vi". This sounds strange to me because I would think the error message would read something more like, " Vi not found. Select 'Open Keyboard.vi'" The actual message implies that LabView knows what the missing vi's do, unless it is some other kind of error.
It also does not make sense to me that these two vi's would go missing on 1 out of who knows how many installations. Is there any possible explaination for that?
Lastly, an
d somewhat unrelated, at the heart of these vi's is a CIN. How do I review the code of the CIN?
Thanks again
Glen D

Cant figure out what error in my car wash tunnels

I made a vi to practice the car wash CLD sample question. And labview says there is missing assignment in every one of my 10 tunnels. But I checked, there is an enum array going into every one of 10 the tunnels. Where did the error come from?
I cant figure it out! My tunnels look exactly like the one in the CLD sample answer attached.
Solved!
Go to Solution.
Attachments:
Car Wash LV86.zip ‏73 KB
sunflower car wash 100.zip ‏44 KB

Hi,
Just move that Enum tunnel upward which you are indicating in RED arrow. You can find a unwired tunnel.Just delete that. Since it has been overlapped you are not able to see.
Thats it.All your error will vanish.

SeqEdit Crash - Access violation (0xC0000005)

I have a very nasty problem: when I open TestStand and click on any step that uses LabVIEW adapter, TS crashes with this message:
It happens ONLY when I click on the step with LabVIEW Adapter. Everything else works fine.
... Help!
Solved!
Go to Solution.

Ok, crash report indicated some problem with LabVIEW Run-Time Engine (missing ""tdtable.tdr" file to be exact). Reinstalling RTE helped. Interestingly, the missing file belonged to 2014 RTE, and it caused crash even when 2013 RTE (or LV 2013 Dev System) was set in LabVIEW Adapter options.
(Also: thanks to Daniel-E for helping with this issue )

Application Builder is it faster?

Hello all.
I just finished doing the example "Building an Application" from the
Release Notes "LabVIEW Application Builder Version 5.1". After doing
the build procedure the application ran noticeably slower that when I
ran the demo program in labview. Did I miss doing something to the
app or a setting in the builder, I was hoping the app would run at
least as fast when run from LabView but not slower. The machine I am
running on is a Pentium 300 running NT.
Thanks in advance.
Regards,
Steve Drake

The Application Builder creates an executable program which is at least as
fast as the same program run in the programming environment, with a gain
speed ranging from 2% to 10% due to the removed debug code.
However, this is true if you use the same options (especially the ones below
the "Performance" tag) you used in the programming environment. To force
your program to use these options, you have to make a copy of your current
LabVIEW.ini file (from the LV installation directory), rename it like your
executable file (i.e. assuming your exe file is myprog.exe, rename the copy
as myprog.ini). Finally edit the file, that has the same structure as a
standard Windows INI file, and rename the section named [LabVIEW] as your
program (in our example [myprog]). Distr
ibute this file in the same
installation directory of the executable file. This will force your progam
to use the same settings you used when developing it.
Apart from this, the executable file is also a bit smaller in memory, since
it does not load the editor and the debugger. In low memory conditions, this
can provide an additional speed gain.
Regards,
Nicola Chiari
"Steve Drake" wrote in message
news:[email protected]..
> Hello all.
>
> I just finished doing the example "Building an Application" from the
> Release Notes "LabVIEW Application Builder Version 5.1". After doing
> the build procedure the application ran noticeably slower that when I
> ran the demo program in labview. Did I miss doing something to the
> app or a setting in the builder, I was hoping the app would run at
> least as fast when run from LabView but not slower. The machine I am
> running on is a Pentium 300 running NT.
>
> Thanks in advance.
>
> Regar
ds,
>
> Steve Drake

LabVIEW Imaqdx vi's Missing

Similar Messages

Maybe you are looking for