DAQmx not displaying in Measurement I/O palette

[ry78]

Hi, I installed Labview 2018 SP1 f4 (32 bit) on to a newer computer of mine. The computer is running Windows 10 Pro (64 bit). The installation of Labview seemed to go well. I then decided to upgrade my NI-DAQmx drives to 21.8, per the software version compatibility chart. All things seemed well, until I wanted to test the upgrade. I quickly noticed in the measurement I/O palette DAQmx was not displayed. Also noticed a few other missing icons in other palettes.

I installed Labview first, then the NI-DAQmx driver. In measurement & automation explorer I show NI-DAQmx ADE Support, Device Driver and MAX Configuration of 21.8. The chassis I tried connecting to was a cDAQ-9178.

My older versions of Labview and NI-DAQmx drivers work fine on my older computer. They also connect to the cDAQ-9178 chassis with no issue.

Curious to know if there is something blatantly wrong with something I did with version compatibility or with the installation method.

Thanks

Ryan

[Bob_Schor]

It doesn't make sense to install one version of LabVIEW (for example, Version 2018 SP1 f4, 32-bit) and newer versions (for example, 21.8) of the Drivers and Additional Components which might want to reference calls to features not (yet) present in the earlier LabVIEW installation.

I recommend that you (safely) remove all National Instruments software from your "newer" computer, decide which version you want to re-install, then reinstall all the components using a single version of LabVIEW.  You should expect that this will give you a a working DAQmx.

Bob Schor

[ry78]

Hi Bob, thanks for the response. I'm not sure if I'm following you 100% here.

My "newer" computer only has one version of Labview installed on it. (2018 SP1 f4, 32-bit) I agree with that logic. Next would be selecting DAQmx drivers. My theory was to install the highest version of DAQmx drivers. Of course, which are compatible with the Labview version. I thought this would "future proof" my installation. Sounds like this isn't the most appropriate approach towards this.

How would I know which version of DAQmx drivers to install? Is this based on hardware requirements, software, etc? According to the compatibility chart I could install 18.0 - 21.8. I read the list as having thought all those versions would have worked. Am I incorrect in this understanding?

Thanks

Ryan

[ZYOng · Accepted solution]

In NI Package Manager, make sure you have the NI-DAQmx Support for LabVIEW installed. If it is not showing up under the INSTALLED tab, install it from the PACKAGES tab.

[Bob_Schor]

This is perhaps oversimplifying a bit, but think of LabVIEW as essentially many products -- LabVIEW 2018 (32-bit), LabVIEW 2018 (64-bit), LabVIEW 2019 (32-bit), LabVIEW 2019 (64-bit), ... LabVIEW 2025 (32-bit), LabVIEW 2025 (64-bit).

Each product comes in several "flavors", such as "Base", "Full", "Professional", and there is a Download/Install "Package" for each.  Do not Mix and Match.  If you are installing a LabVIEW 2019, 32-bit version, install LabVIEW, supporting "top-level" parts (such as Real-Time, Image Processing), Drivers (including NI-DAQmx, and VISA), and any Additional Products that you need (I recommend not "installing everything", but only those pieces that match and complement the components you have already selected).  You can assume that Drivers of the same "vintage" as your LabVIEW base install will work, whereas earlier versions might be missing a "feature" you need, and much later versions might have "unusuable Future Features" that will mess up the code you are trying to develop.

Bob Schor

[ry78]

Ok that's good to know.

Thanks

[ry78]

That was the problem! The packages tab was not visible at first. Finally found how to display that. Found the NI-DAQmx Support for Labview check box. One check box, that was it. lol I checked the functionality of various vi's/tasks, all look good. The only one that crashed was the DAQ Assistant. I can place the vi on the block diagram, it tries loading then nothing. I'll further investigate that, but what I really wanted, is now fixed.

Thanks, spent a few days trying to figure this one out.

Ryan