Professional Question

[wehlers@ambersi.com]

We bought the pro version so I can develop on my office computer then create an exe and use it on the lab computers. The lab computers have the Visa runtimes installed on them. When I do the EXE and run it on the lab computers I get a whole list of DLL's missing .LIB missing and other things. The Vi's I used to make the Keysight DAQ970 programs give an error when running the exe that they are not installed on the lab computer and cannot run. It is to the point that why did I buy a 4K pro version when I could have just bought the yearly $400 dollar license for each lab computer. The question I have is if I am making a EXE file than why do I need to set up all this other stuff on the lab computer or am I just missing a switch or button when the build is made that installs all of this in the build/EXE file?

[santo_13]

Probably, you are not including all the dependencies of the exe in the computer that runs it.

For example, you create an exe, you expect only your code to be built into an exe and all other dependencies exist already. you can't expect MS office to also install you Windows OS.

[GerdW]

Hi wehlers,

---

wehlers@ambersi.com wrote:

We bought the pro version so I can develop on my office computer then create an exe and use it on the lab computers. The lab computers have the Visa runtimes installed on them. When I do the EXE and run it on the lab computers I get a whole list of DLL's missing .LIB missing and other things.

---

The usual recommendation goes like this:

1. So you create a BuildSpec to build your EXE.
2. And then you create another BuildSpec to create an installer for your EXE.
3. And then you run that installer on your lab computers…

You are now complaining that these 3 steps result in non-executable EXEs on your lab computers?

[Yndigegn]

Hi

When you create an exe installer for your LabVIEW program then you must ensure that all dependencies are known to the installer.

Read these linked entries :

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N8tSAE

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kK4USAU

Regards

[rolfk]

Well not sure where the missing .lib should be from but the DLLs are likely from the Keysight device. Keysight in their infinite wisdom decided that maintaining a separate LabVIEW driver  is to much effort so they develop a bunch of dlls for their instruments that each environment can use.

The LabVIEW VI wrappers they provide only know about the device specific top level DLL but not the other support DLLs. You need to install all modern Keysight drivers separately through their own device specific driver installer or install the entire Keysight IO driver suite in order to use them from any programming environment, not just LabbVIEW.

Incidentally the DAQ970 is really for the most part fully compatible with older similar HP devices and for those exists a native LabVIEW driver. If you don’t really need any of the new features you could go with that driver from NI and forget about all the DLL shenigan for your device.

---

[RTSLVU]

As rolfk was saying you need to install the Keysight software and drivers on the target machines. 

The DAQ97x series is fully SCPI compatible with the HP/Agilent/Keysight 3497xA series that it replaced. So again unless you need some of the new functions you can use the Agilent Technologies / Keysight Technologies 34970A plug and play drivers

There are SCPI commands that you can use to access the new features on the DAQ97x series without using or installing the Keysight drivers. But you will have to RTFM and write your own LabVIEW for the new functions.

[wehlers@ambersi.com]

My thanks to all the responses. Sometimes you go off the deep end end it takes wiser folks to pull you back to reality. I have what I need and avoiding the manufacturer drivers and think from a development angle instead of being lazy is the key. Again my thanks