NI-DAQmx 8.8 does not work properly after upgrade to LabVIEW 8.6

[plp122]

Hi,

I just upgraded to LabView 8.6 from version 7.1 and found out that the NI-DAQmx 8.8 drivers do not install correctly, since there is not Measurement I/O tab in the Functions palette (see attached document). The curious thing is that I can see all my NI-DAQmx devices in the MAX, and they all test correctly, i.e., they are working correctly. The sales representative for my area recommended me to uninstall , and reinstall LV8.6 and then reinstall the NI-DAQmx 8.8 drivers, but it did not work. I still do not see the Measurement I/O functions and my application says that it "cannot compile" the NI-DAQmx vi's. Thanks in advance for your help.

Peter

PS. Someone reported a similar problem back in 2003, but the final solution was not posted. Thanks again.

[Christian Mergl]

Hey Peter,

Can you have a look at the Functions Palette in the Blockdiagramm under Measurement I/O. Is there an entry of DAQmx?

Christian

[plp122]

Hi Christian,

Thank you very much for your reply. The DAQmx menu is actually there (see attachment), however, the vi's are still not responsive for some reason. I'll keep doing some additional troubleshooting. Thanks again for your help. 

[mallorim]

Hello plp122,

So as I understand the issue, you have uninstalled and reinstalled LabVIEW 8.6, and then you reinstalled DAQmx 8.8, to no effect.

1. Before you reinstalled DAQmx 8.8, did you uninstall it? If not, then I  believe that the installer would see the driver already present and not actually make any changes.

2. When you say that the VIs are not responsive, could you describe this a bit better? Perhaps post one of the error messages about compiling that you mentioned in your first post?

3. If you open the NI Example Finder (Help»Find Examples) and the expand Hardware Input and Output»DAQmx»Analog Measurements»Voltage, are you able to run one of the example programs and see the correct values that you see in the Measurement and Automation Explorer Test Panels?

I look forward to your answers.

Regards,

Mallori M.

[plp122]

Dear Mallori,

Thanks for your help. You are right, I uninstalled and reinstalled LabVIEW 8.6 (update from LabVIEW 7.1) and reinstalled DAQmx 8.8. I still continue to have some problem that seem (to me) beyond compatibility issues. Here are the answers to your questions:

1.  Before you reinstalled DAQmx 8.8, did you uninstall it? If not, then I  believe that the installer would see the driver already present and not actually make any changes.

REPLY: No, I did not uninstall DAQmx 8.8. What do you recommend? Should I uninstall BOTH LabVIEW 8.6 and DAQmx 8.8 and then reinstall everything again? 

2.  When you say that the VIs are not responsive, could you describe this a bit better? Perhaps post one of the error messages about compiling that you mentioned in your first post?

REPLY: I am having a lots of "This SubVI is not executable" error messages in many of the library VI's not even mine. See the attached file.

3.  If you open the NI Example Finder (Help»Find Examples) and the expand Hardware Input and Output»DAQmx»Analog Measurements»Voltage, are you able to run one of the example programs and see the correct values that you see in the Measurement and Automation Explorer Test Panels?

REPLY:  I tried to runa couple of the examples for continuous voltage acquisition (internal clock) and both open with errors (see attachement).

Thanks again for your help. I am looking forward to your recommendation.

Regards,

Peter

[mallorim]

This issue was resolved offline. The broken run arrows the user saw when opening his VIs in LabVIEW 8.6 were the result of his Simple Error Handler functions being corrupted. The Error functions had been changed and saved, so that every instance of the error handler in LabVIEW 8.6 caused the error message "subVI is not executable."

The solution involved relpacing his corrupted error.llb in the LabVIEW's Program files (found in the Utility folder) with an uncorrupted version. Now, when he opens his 7.1 VIs, they update without error.

Regards,

Mallori M.