LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR WHEN STARTING VI

I have an error that pops up about every first and second time I start my vi after I turn on my computer.  After that it never shows the error again until I shutdown the computer, and restart windows.  Anyone have any ideas?  I have the 8.0.1 update.  Thanks for any help
0 Kudos
Message 1 of 6
(3,276 Views)

Hi TMDATA,

This looks error looks like it may have to do with an error in a DLL in the DAQ driver.  Have you tried uninstalling and reinstalling your DAQ driver to see if this might make a difference?  It's possible that a DLL has become corrupted--in fact, you may want to just reinstall all of LabVIEW if you're reinstalling, just in case.

 The tricky thing is that your VI works after you receive this error a few times and that's quite puzzling.  What sort of hardware are you working with?  Can you pare down your VI to just a few VIs which cause this error (it looks like it may originate in the DAQmx Start Task).  Perhaps you could post your VI here and a few of us could see if we can replicate it.

I hope this helps!  Good luck,
Megan B.
Applications Engineer
National Instruments

 

0 Kudos
Message 2 of 6
(3,247 Views)
So far today, I cant even get it to run.  It worked fine last night, and I have not changed anything.  I have attached the vi.  The card that is on this computer is a PCI-6014.  Thanks for the help
0 Kudos
Message 3 of 6
(3,246 Views)
If I open it in 8.0.1, I see a class conflict in the uppermost output tunnel. If I replace that "DaqMX clar task" with a new copy, the error clears.
 

Message Edited by altenbach on 03-30-200609:54 AM

0 Kudos
Message 4 of 6
(3,236 Views)
I replaced the uppermost DAQmx clear task, and I still get the error.  It gives me an error on everyone of the DAQmx functions on the top of the window.  DAQmx start task, DAQmx read, and so on.  If I replace them I still get the same error.  I ran into a similar problem with a different vi that crashed Labview everytime I ran it.  I ended up having to recreate the whole vi, and then it worked fine.
0 Kudos
Message 5 of 6
(3,207 Views)

Hi TMDATA,

It certainly sounds like the VI has become corrupted somehow.  Strangely, I haven't had any trouble opening or running the VI in 8.0.1.  Have you had trouble with any other VIs?  As far as this particular VI.  One thing you could try is copying and pasting the code into a brand new VI one piece at a time.  Be sure to run the VI in the intermediate steps to determine if any of the code you moved over is corrupting the new VI.  Copying the block diagram will often help these strange errors.

Hope this helps!
Megan B.
Applications Engineering
National Instruments

0 Kudos
Message 6 of 6
(3,182 Views)