How to add inbuilt DLL to a project explorer

[mc5000]

---

@billko wrote:

Project --> Show Item Paths

---

Thanks for the heads-up but it still does not display a path. The image below shows two different DLL files in the project viewer, and the DAQ970 one just doesn't display a path:

Do you have any idea what that means?

[rolfk]

Have you checked in C:\Windows\System32 (or C:\Windows\SysWOW64 if you use LabVIEW 32-bit on a windows 64-bit system)?

[mc5000]

---

@rolfk wrote:

Have you checked in C:\Windows\System32 (or C:\Windows\SysWOW64 if you use LabVIEW 32-bit on a windows 64-bit system)?

---

Yes I have looked around manually and searched through the entire C:\Windows with windows explorer and freecommander. I can find some generic NI DAQ dll's but not that specific one.

[Krokanwood]

Hi. I have the same issue. I am writing drivers for some Keysight/Agilent instruments and seems I am using a "dll wrapper" IVI driver like the OP. I did find the KtDAQ970.dll file. Its in C:\Program Files (x86)\IVI Foundation\IVI\Bin.

Exe's cannot find this DLL, and there is no way to include it into the "Always included" box:

So is the solution to rewrite everything to use SCPI commands instead? Why Can't I just add the DLL and stuff works? (Tried copying the dll... The exe created a tiny black hole and divided by zero. Didn't go well....)

[mc5000]

---

@Krokanwood wrote:

Hi. I have the same issue. I am writing drivers for some Keysight/Agilent instruments and seems I am using a "dll wrapper" IVI driver like the OP. I did find the KtDAQ970.dll file. Its in C:\Program Files (x86)\IVI Foundation\IVI\Bin.

Exe's cannot find this DLL, and there is no way to include it into the "Always included" box:

So is the solution to rewrite everything to use SCPI commands instead? Why Can't I just add the DLL and stuff works? (Tried copying the dll... The exe created a tiny black hole and divided by zero. Didn't go well....)

---

I never found a working solution for including the DLL. What does work for me is to install the IVI shared components and the Keysight drivers (KtDAQ970-IviC-x64_1.0.0.0.msi in my case) on the machine which will run the executable.

I placed the necessary driver install files in a sub-folder of the LabView project and then added them as source files in the settings for the installer. This way the drivers are copied in a sub folder next to the executable but must still be installed manually. I believe I read somewhere that it is possible to make the installer run the driver files during installation, but it did not seem straight forward when multiple external installers are necessary so I did not spend the time trying to make it work.

[Krokanwood]

Thanks for the update. Good to know I can bundle it together like that, its a great idea.

For my project I downloaded a different driver set from page 1 in the discussion here and I'm going to replace all the code with SCPI based commands. Anything requiring a dll should be avoided like a viral infection when it comes to Labview I guess...

[@ironman]

Hi the problem can be solved by installing IVI C driver in the destination laptop. https://download.keysight.com/GM/KtDAQ970-IviC-x86_1.0.0.0.msi?dl=1&authparam=1643102215_e854a7d00a9...

which fixed the problem for me. for that you might also need to download ivi sharedcomponent driver too.

https://ivifoundation.org/downloads/Shared%20Components/IviSharedComponents_300.exe