Problems with traditional NI-Daq after upgrade

[tavis]

I recently upgraded to labview 8.6 from labview 7.1. I have a fairly complicated VI used to run a test rig that is no longer working. I've traced the problem to a conflict between NI-Daq and DAQmx. When I run the Vi I get the message:

Error -10461 occurred at AO Group Config

Possible reason(s):

NI-DAQ LV:  The specified resource is unavailable because it has already been reserved by another entity.

I believe the problem is that the PCI-6074 is being accessed by both theNI-daq and DAQmx drivers. I would like to update the vi to use DAQmx, but the tutorials have not helped me much. Since I inherited the test rig from someone who left, and I need to make sure it continues to run, I hesitate to just start experimenting with the vi as I don't have much labview experience. I hope someone can point me in the right direction. 

[KrisnaWisnu]

Hi Tavis,

I believe your problem caused by one device accessed by two driver (DAQmx and Traditional DAQ) at one time. To solve this problem, you need to make sure both DAQmx code and Traditional DAQ code run in sequence and RESET the device everytime you switch between the codes. 

Use the Device Reset VI at the end of the Traditional DAQ code sequence, annd DAQmx Reset Device VI at the end of the DAQmx code sequence. You still need to create a Traditional DAQ virtual channel and DAQmx Task for use with each driver respectively 

 Source:http://zone.ni.com/devzone/cda/tut/p/id/3021

 (bottom of the page)

I hope it helps!

Sincerely,

Krisna Wisnu

[tavis]

I've tried looking for other vis calling that same device, but I can only find the VI that I posted above. Is there some way to search to find other sub-vis that are calling the same device? Also, is the device I posted using a traditional or DAQmx driver? If it is using traditional, is there DAQmx replacement that doesn't use the express vi assistant?

[KrisnaWisnu]

Hi tavis,

Basically, before you upgrade to 8.6 the VI is already broken right? From my observation, before you proceed, you need to find the other subVIs. I tried to open it on my end, but it prompt me with missing Vis. Another thing, I could not find 6074 in DAQmx readme file, so I could not tell whether it belongs with DAQmx, Traditional DAQ or both.

It would be easier for you to know the functionality of the code and re-write the code with DAQmx (if your device supported this). Without more information, there is nothing I can do much.

Sincerely,

Krisna Wisnu

[tavis]

No, the VI worked perfectly before the upgrade. Once I upgraded the software, it stopped working. I would like to rewrite the VI, and possibly the entire library of 12 or so sub-VIs, but I just don't have that much time to devote to learning labview at this point.

[Dennis_Knutson]

Did you try going into MAX and resetting? That's assuming that when you did the upgrade, you installed the traditional DAQ driver as well. You need to have the device show up under the traditional driver.

[tavis]

I did reset, but as soon as I start the VI, i get the error message. I'm sure that Krisna is correct that there is a conflict between the current and legacy drivers, i'm just not sure where it is, and I'm not able to find it digging through the sub-VIs.

[Dennis_Knutson]

There is nothing in the VIs to look for. It is nothing but the functions in the traditional driver and the conflict is that DAQmx is the active driver. You should be able to reset the device in MAX and make the traditional driver active. Do you actually have traditional DAQ installed? Do you see it in MAX? Everything you need to do can be done in MAX. At the very worse, uninstall DAQmx completely since you don't want to take the time to convert.

[tavis]

I can't completely uninstall DAQmx, as I have another VI that needs the DAQmx drivers. That other VI is the reason I had to upgrade in the first place. I have already reset the DAQmx driver in MAX, but as soon as I start the upgraded VI, i get the error message. It would make sense that there is one sub-VI trying to access the legacy driver, and another sub-VI trying to access the DAQmx driver, I just can't find that conflict. Is there no way to search for every sub-VI in a library calling a specific device?

[Dennis_Knutson]

I've asked you a couple of times to verify that you have traditional DAQ installed and whether you can see your device listed there in MAX. Stop messing around with LabVIEW. You should be able to test the device in traditional DAQ. Then, do not run any DAQ code in parallel that uses different drivers. That does not work as has been already mentioned. The code you posted is missing some VIs but the stuff that is not missing, has no DAQmx. Search it if you want. That is what the Find and Replace option is for under the Edit menu.