06-22-2024 08:51 PM
Hello,
I have labview 2017 software and PCI 4474 hardware, and I was able to integrate PCI 4474 into labview 2017 through DAQmx driver previously.
Recently, I formated my computer and reinstalled labview 2017 then DAQmx driver.
I tried several versions of the DAQmx driver, such as 19.1, 19.5, 20.0, and 20.7, which are compatible with labview 2017.
On the NI MAX, I can see that the DAQmd driver is properly installed.
However, there is no daqmx function under measurement I/O palette of labview 2017.
The driver installation does not generate the DAQmx folder at LabVIEW 2017\ vi.lib. So, I think the DAQmx driver installation does not recognize my labview version. I see there have been several posts relating this issue, and often it was suggested to select tap for "NI-DAQmx Support for LabVIEW 2017" during the installation, but I do not see this option. Actually, the DAQmx driver installation is done by NI pakage manager, and I installed every items that are allowed during the installation.
Does anyone have a idea how to solve this problem?
06-23-2024 02:07 AM
Hi gyungmin,
@gyungmin wrote:
Actually, the DAQmx driver installation is done by NI pakage manager, and I installed every items that are allowed during the installation.
Does anyone have a idea how to solve this problem?
LV2017 is a version before NIPM became available. And NIPM often/mostly doesn't know about software that was released before NIPM…
Suggestion: Use your LV2017 installation media and install DAQmx from those media. Then both software packages "know each other"…
06-23-2024 02:54 PM
If you have your activation code (or License number) for LabVIEW 2017 (I assume 32-bit), you can download LabVIEW 2017 from NI. You might only be missing DAQmx and drivers for this version. If that doesn't work, I'd recommend doing the following on a test PC or on a VM --
Bob Schor
06-24-2024 05:16 AM
Hi GerdW,
I found that the original install kit has an option to install intruments divers, which includes DAQmx.
Installing both labview 2017 and DAQmx driver from the original intall kit solves my problem.
Many Thanks.
Gyungmin