LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

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.

 Now I used the DAQ Assistant in my LV program. The scales and tasks that were created using teh DAQ Assistant do not show up in MAX but they do show up in the Project Explorer.

I Assumed they would be automatically included in the build as the daqmx.ini file is being created and included in the data directory of the build.

Is this correct or do I also have to create the tasks and scales in MAX as the instructions here say?


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.

Both the EXE and the VI run fine on the development computer. I am even using the exact same USB-DAQ, moving it from computer to computer.

On the target computer the program runs without errors but the program just does not operate, the analog output stays at 0V and the analog input constantly displays 0V.

If you scroll back a few you will see I have included screen shots of my code, MAX, and the Project Explorer.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 11 of 15
(1,927 Views)

I Assumed they would be automatically included in the build as the daqmx.ini file is being created and included in the data directory of the build.

Is this correct or do I also have to create the tasks and scales in MAX as the instructions here say?


The instructions there do not say to create tasks and scales in MAX. Unless I'm heavily mistaken, it should be fine to create the tasks from the Project. They will not show up in MAX if you do it this way. In the LabVIEW help there are sections on importing to and from MAX for tasks defined in a Project.

From the information included about creating an Application, it did not explicitly state that device information was included with the DAQmx tasks. The creating an installer did state that device information will be saved when including device information.

This may not be a necessary step, but it is necessary to check that the device information in MAX on both computers are identical (this does not mean that the tasks are identical, only devices and interfaces). You only provided a screenshot of MAX for one computer. Do you have other devices in MAX on your development machine? Could you provide that screenshot as well? If you have a service request open on this issue, could you also provide it? Thanks

0 Kudos
Message 12 of 15
(1,904 Views)

 I have a service request open on this 1081553

The person I talked to today basically advised against using the DAQ Assistant and modifiing one of the Labview example VI's

This is the first device of this type I have had to use NI-DAQ with so I am at a total loss here.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 13 of 15
(1,895 Views)
I've attached a project with build specification of a simple example (Cont Acq&Graph Voltage-Int Clk.vi). Try creating an exe from this example and run it on your target machine. It will allow you to choose which physical device you are using from the front panel. Do you have other devices in MAX on your development machine? Could you provide that screenshot as well?
0 Kudos
Message 14 of 15
(1,872 Views)

Now it's working?

I do not know how or why as I have changed nothing on the target machine.

I built and transfered the program you attached and it worked, so I ran my program and it worked too.

I just hope it stays working...



Message Edited by RTSLVU on 12-03-2007 03:05 PM
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 15 of 15
(1,849 Views)