LV Runtime and missing DAQmx SubVIs

[OnlyOne]

Hello,

i created on computer-1 with a full lV version a VI that uses DAQmx subVIs.

On computer-2 is only Labview runtime installed and also DAQmx.

This brings now the problem that all VIs which are installed in <vilib>:\DAQmx\ on computer-1 are not available on computer-2.

What do i have to do now?

Thanks

[RavensFan]

When you install only the run-time for DAQmx, you don't get subVI's.  You don't need them since you aren't developing any VI's on that.  On your development PC with LabVIEW and your full DAQmx, that is where you will build an application into an executable.  That executable will run on the 2nd PC because the run-time engines provide the needed run-time libraries that don't get built into the EXE.

[OnlyOne]

I installed on both computers the full NI DAQmx.

I dont want to create an executable as i only need the VI that will be called in NI TestStand.

Is there a way that NI DAQmx also installs the VIs?

Thanks

[RavensFan]

How are you running a LabVIEW VI on a PC that only has a LabVIEW run-time?

[crossrulz]

---

@RavensFan wrote:

How are you running a LabVIEW VI on a PC that only has a LabVIEW run-time?

---

If the OP builds the VI(s) into a Packed Project Library, then it works just fine.  That is what I do for my plugin architecture, which is also used with TestStand.

[OnlyOne]

Hi,

@RavensFan, the computer without labview has an installation of NI Teststand together with "NI Labview Runtime (free)" If you only want to execuite VIs the free laview runtime can be used in NI Testand.

It worked after creating a library with manually selecting "include vi.lib" & "include instr.lib" subvis in the prjekt settings.

Then all needed VIs are in the projectfolder and using the folder on the computer without labview extecutes the VI in NI Teststand.

But it is not understandable why the installation of NI DAQmx does not always copy the DAQ-vis to the computer no matter if there is a labview installation or not. (Best woould be if there wold be a selection while installing).

Now in this case if there is an upgrade or bugfix to NI DAQmx the user has to recreate/rebuild all procjects containing nidaq-subvis instead of simply installing a newer version of nidaq.