Editing data acquisition VI made with LV4.1 with LV7.0

[danbanana]

A question from a relative newbie to LabVIEW:

My lab has an old data acquisition program that was programmed out of house with LabVIEW 4.1. We would like to upgrade the whole DAQ system, preferrably by just editing the old VI with LV 7.0 to work with the new DAQ equipment (an MCC PCI-DAS1000 internal DAQ card). Unfortunately, MCC boards need to use their own Universal Library AI VIs for LabVIEW to properly recognize them. I believe I've successfully replaced all the necessary LV Analog Input VIs with MCC's. However, the application is still looking for an SCXI chassis (our old DAQ system) that doesn't exist on the machine. I believe the issue has to do with the old DAQDRV file used in old (pre-6.0) versions of LV
that has been replaced by LVDAQ.DLL. It seems that said DAQDRV is still being pointed to as the DAQ driver by the program.

Unfortunately, I have not been able to get a hold of the developer of our program.

So after much convaluted explanation, my question is: can I point the old VI program (made with LV4.1) to look at another driver file? If so, how? And if not, would anyone have any other suggestions concerning this problem?

[Dennis_Knutson]

I think that you've missed a LabVIEW daq VI. The DAQDRV file is only necessary when one of these is present and without one, DAQDRV is neither needed nor called. From your main VI, you should be able to look at the hierarchy. Besides AI VI's look for configuration VI's. One thing you can try is temporarily renaming LVDAQ.DLL to soemthing else and then open the main program. If something is calling LVDAQ, then that VI will be broken and you should be to find it from the error list.

[Process_Systems]

From your question, it sounds like the MCC drivers are not recognizing the MCC hardware. Have you installed MCC's Instacal software, and used it to configure your daq card in your computer??
I know this is basic, but you made no mention of this very necessary step.

Good luck.

Dave