Wiring errors on updates DAQmx drivers from the traditional DAQ.

[erle]

I retrieved some VIs written with the traditional DAQ from an old broken desktop and am in the process of converting this VIs into executables using the LabView 2013. With materials on ni.com; I have been able to replace the traditional DAQ drivers with the new ones for DAQmx (because the VIs are broken on the new DAQmx due to missing drivers). The issue is that after updating this drivers there are compatibility issues, like the sink is 64-bits while the source is 32-bits and so both drivers can not be wired.  I looked at the Context Help, it says to include all subVIs and that is already done but it does not resolve this connection issues. How can I resolve this?

[Dennis_Knutson]

You need to attach the VI or an image showing the connection issue. I don't understand your comment about both drivers. You would be using only one driver - DAQmx.

[erle]

Excuse me, I meant subVIs not drivers. Attached is an image from the program, the subVIs disabled here are the 'write to digital' vi written on LabView 7.8. I attempted to replace them with the DAQ Assistant (Analog Input) as shown, it worked for some but not all. I cann't tell what the properties for "write to digital.vi'" are. I already called NI  and they couldnt help with that information. Would appreciate it if anyone has information on "write to digital.vi" so that I can better understand the attributes to create on the new DAQ Assistant.

[erle]

Image attached.

[Dennis_Knutson]

There is no such thing as LabVIEW 7.8 and it seems silly to use an analog input DAQ Assistant for a Write to Digital function. Did you install the traditional DAQ driver so that you can view the functions and read the help for them?

p.s. The image is too small to see any broken wires.

[erle]

I meant LabView 7.0. For what am trying to do, which is to acquire values from the analog inputs on the PCI, DAQ Assistant does not "seem silly". Using it to replace the write to digital.vi might not be logical; which is why am trying to know the attritubes of  write to digital.vi to understand why the original programmer used it.

[erle]

 There is an earlier attachment in pdf. It's attached here again.

[Dennis_Knutson]

I don't see any analog in DAQ Assistant in the pdf. You should simply attach the VI if it's in the enabled state. 

Write to Digital would be a write to a digital line or port which is why an analog input DAQ Assistant is both silly and illogical. You really need to install the traditional DAQ driver on some pc so that you can review the old code and the help for the old functions. The traditional DAQ functions have been obsolete since LabVIEW 7.0 and I don't remember any of the old details and you won't find manywho still have the old driver installed.

[erle]

The analog input DAQ Assistant is in the file attached here.

I installed the traditional DAQ to a system and was able to retrieve some but not all of the subVIs. The missing subVIs left broken wires. I have fixed the broken wires by applying reverse engineering and replacing the old functions with new ones in the DAQmx on another system with LabView 2013.

Even though there is no error, this program only does some of what it needs to do. The issues arises from the places I used the DAQ Assistance (and yes I used it properly and have them connected to the right lines and ports). 

Thanks.

[Dennis_Knutson]

So now you've attrached an image from a completely different frame of an evil stacked sequence structure. Is the disabled code the missing write to digital? That still does not seem to have anything to do with any sort of analog signal. 

If the Write to Digital is not part of the traditional DAQ driver, I don't what else you can do except do another search for the custom VI.