LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

nilvaiu.dll? Why was it not included in the build?

I am building a standalone application in LV 8.5
 
When I install and run the appllication on the target machine it keeps looking for nilvaiu.dll.
 
What is this dll and why is it not automatically included in the build if it is needed to run?
 
I have created an installer that includes the LV8.5 runtime and this is still not included?
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 1 of 15
(11,552 Views)

Now, I just spent an hour on the phone with NI tech support and neither I nor the NI guy could figure out why it was not automatically included since it dies show up as a dependency in the project explorer or how to include the dll's in the build.

Ok so I found the dll in the WINNT/System32 directory on my development computer and manually copied it to the target computer.

Low and behold yet another needed .dll is missing! This time it's nimdbgu.dll.

I can not believe that even after building an EXE and an installer I am still going to have to manually copy required dll's to the target computer.

What am I missing here?



Message Edited by RTSLVU on 11-28-2007 05:15 PM
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 2 of 15
(11,544 Views)
What hardware are you using in your program (i.e. GPIB, DAQ, etc.) and did you include any of the additional installers when you created the LabVIEW installation?
0 Kudos
Message 3 of 15
(11,536 Views)
I am using an NI-USB-6009 DAQ. I should have known this was going to be a problem.
 
As using any NI hardware requires a tangled web of drivers and updates to be installed to make even the simplest program run.
 
So this morning I have downloaded and am in the preocess of installing 1.5 GIGABYTES of various NI drivers in an attempt to get my 327K application to run.
 
As for building aditional installers. I tried building an installer for NI-DAQ 8.6 but LV8.5 is aksing for LV 8.2.1 disks to build it?
 
LabVIEW cannot locate the source installer for a component necessary to build this installer.
 
Distribution name: NI LabVIEW 8.2.1
Please locate the source installer for NI LabVIEW 8.2.1 and build your installer again.
 
Now I don't know why 8.5 needs 8.2.1 files when as far as I know 8.2.1 was never on this machine. If we do have 8.2.1 in the company the disks are locked up in some corperate I.S. department vault and it will take a director or VP level approval to get my hands on them.
 
Sorry for the rant here but this is such a trivial little program and the hoops I have to jump through to make it run on the target machine keep getting higher and about to be lit on fire.
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 4 of 15
(11,529 Views)

Not sure why it would be asking for 8.2.1 files unless you installed an older version of DAQmx instead of the one that came with 8.5. As far as the large download,  when you create the installer, you have the option of installing various types of DAQmx installations. They range from the full version with MAX, etc. to a minimal version without MAX.

 

0 Kudos
Message 5 of 15
(11,520 Views)

I downloaded and installed DAQmx on to the target computer this seems to be what was missing...

The LV app is a simple analog input and output program. (this is still just proof of concept)

The app runs with out errors but there is no analog output when controls are changed and the indacators do not display the analog input voltage.

I do not even know how to troubleshoot this since I can move the DAQ back to the develpoment computer and it runs fine.



Message Edited by RTSLVU on 11-29-2007 02:56 PM

Message Edited by RTSLVU on 11-29-2007 02:57 PM

Message Edited by RTSLVU on 11-29-2007 03:00 PM
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 6 of 15
(11,504 Views)
There is a lot that goes on with the DAQ Assistant. One of which is that it creates tasks in MAX that are used. You can export the settings fromm the pc where it works and then import them on the other pc. This is another option when building the installer. I never use the DAQ Assistant and don't create tasks in MAX. I create everything in the lower level DAQmx Create Channel.
0 Kudos
Message 7 of 15
(11,490 Views)
I have two scales and a DAQ Assistant in the project explorer on the development computer.
 
I don't see either of them in MAX.
 
Shouldn't the scales and DAQ assistant automatically be included in the build?
 


Message Edited by RTSLVU on 11-29-2007 04:54 PM
========================
=== Engineer Ambiguously ===
========================
Download All
0 Kudos
Message 8 of 15
(11,486 Views)
I had the same problem as well. First I downloaded and installed the 8.5.1 runtime, and the application wouldn't run, asking for the various dll's. So then I installed LabView drivers from the CD that came with the USB DAQ board. THe application would run no problem after that. Not really a good answer for you, just confirming your concern/question. Thanks, jp
0 Kudos
Message 9 of 15
(11,478 Views)
Hi RTSLU,
 

Shouldn't the scales and DAQ assistant automatically be included in the build?
 
From the LabVIEW Help:

Using Application Builder with NI-DAQmx

When using the Application Builder to create either a stand-alone application or an installer, you can choose to include or exclude project-defined tasks, channels, and scales.

To create an application, complete the following steps:

  1. Create a task, channel, or scale.
  2. Add the task, channel, or scale to a VI by dragging and dropping the object onto the front panel or block diagram.
  3. Right-click Build Specifications. Select New»Application (EXE).
  4. The Application Builder window opens. Refer to Building a Stand-Alone Application for more information on setting up an application build.
  5. Select Source Files from the Category list. Move the desired VI to the Startup VIs list box.
  6. Select Advanced from the Category list. The option Include hardware configuration files is selected by default. If you build with the option checked, daqmx.ini is created in the support directory path. The .ini file contains task, channel, and scale configuration data in plain text format. When you run the application, the application references the .ini file to set up tasks, channels, and scales in the VI.

To create an installer, complete the following steps:

  1. Right-click Build Specifications. Select New»Installer.
  2. Refer to Building an Installer for more information on setting up an installer build.
  3. Select Advanced from the Category list. Click Include hardware configuration from MAX. The MAX hardware configuration includes device information, in addition to NI-DAQmx task, channel, and scale configurations.
  4. Click Configure. The Configuration Export Wizard opens. For more information on exporting a hardware configuration, refer to Measurement & Automation Explorer Help for NI-DAQmx. When you run the installer, the installer references the .nce file to set up devices, tasks, channels, and scales in MAX.

I have two scales and a DAQ Assistant in the project explorer on the development computer.
I don't see either of them in MAX.

To see them in MAX please refer to the "Exporting NI-DAQmx Tasks, Channels, and Scales in a Project" in the LabVIEW Help.


I do not even know how to troubleshoot this since I can move the DAQ back to the develpoment computer and it runs fine.

When it runs fine, are you running the built executable or the VI on the development computer? Try including the hardware configuration from MAX in the installer as stated above.

0 Kudos
Message 10 of 15
(11,471 Views)