LabVIEW 7.1.1 with DAQmx 8.6 crashing before running LabVIEW code

[Truman]

I am in the process of writing some code for a project, and I just upgraded the DAQmx software to the version 8.6 to support some USB devices.  Now whenever I start up LabVIEW and look at my code, LabVIEW crashes.  It crashes even before I run the main VI.  One interesting thing is I have a tab control on the front panel, and LabVIEW seems to only crash when I have the first tab up.  I can have the other tabs up for however long, but it only seems to crash when I bring up the first tab.  And keep in mind this is without the main VI even running.  Any advice on how to prevent this would be great.

[Brian_R]

What objects are on the first tab of the tab control? 

To test if DAQmx is the culprit, I would suggest opening a few of the example VIs in the Example Finder.  Go to Help >> Find Examples... and navigate to some of the DAQ example to test if the DAQ VIs are the problem.  You can also try removing different nodes in the VI until you can identify what is causing the problem.

[Truman]

Sorry for the late response.  For a while the problem wasn't so bad.  Sometimes it would crash, and sometimes it wouldn't.  However, now it is a serious problem.  For some reason, I cannot open this VI at all anymore.  In addition, I cannot open older versions of this VI that have been backed up.  I tried to mass compile the library file to no avail.  I also tried repairing the LabVIEW installation to no avail.  I'm really in a bind now with weeks of work on the line.  There is one old version I was able to open and run, but I had the same intermittent crash problem with that version in the past.

[Truman]

I uninstalled LabVIEW and NIDAQmx.  I then installed LabVIEW 7.1, then upgraded to 7.1.1, then installed NIDAQmx 8.6.  I performed a mass recompile of the LabVIEW directory as is recommended when upgrading to 7.1.1.  For a while, I was able to open my files and get some work done.  However, when I closed the file and tried to open it back up, it is now constantly crashing (even backups as before).  I have attached the log of the mass compile.  It says there are many "bad" vi's.  Is there a way to fix these?  I am using four DAQ cards:  PCI-6024E, USB-6215, USB-9421, USB-9472.

[chasan]

Hi,

Currently i am using a PID controller vi with analog input for pressure acquisition (Dev1/ai0) and PWM counter output for the feed back pulse generation (Dev1/Ctr0)

and in another vi for the activation of a valve i generate pulse for the relay coil (Dev1/ai1) to activate and getting back the coil current thro another analog input(Dev1/ai1)

When i run the individual vi it works fine but i want to integrate both vi as a single vi and run for my purpose. I have to use the vi in such a way that when my PID controller is stabilized it has to activate the relay coil. I would like to use only one device to do all but it will happen only when the first (PID) releases the resource for the second (Relay coil)

My question is: Is there any other way to do the above function using DAQmx so that when the first vi (PID)is active only i have to start the second(Relay coil) to generate pulse

Over all i need a method to use more than one channel of a same device in a single vi( is there any way to synchronize the sample clock)

Thanks in advance

Chandru

[Truman]

Ok, another update, I'm on another computer with LabVIEW 8.0 and NIDAQmx 8.0.  I open the same VI's and LabVIEW does not crash.  At least I know I haven't lost my work.

[JamesR]

Hi chasan,

Would you mind posting your question to a new discussion forum thread?  It's useful to keep threads broken up by topic so people don't get confused.

Truman,

On your original computer, you might try uninstalling DAQmx and then trying to open your VI.  Of course your VI won't run, but this will help us determine whether the problem is related to the driver, or LabVIEW itself.  Before doing that, you could also try opening up some of the DAQ examples to see if LabVIEW crashes.

[Truman]

Thanks for the advice.  Using version 8 seems to be working perfectly now, and there's no need for me to stick with version 7.  So I think my problem is solved, even if I don't know exactly why...