NI 9172 & Application Builder Problems

[Jeremy@Thermadyne]

I am working on an application which receives analog inputs and displays the data and records it to an excel spreadsheet.  I am using the following hardware:

NI cDAQ-9172 Chassis with NI9211, Two NI9201, NI9481, and NI cRIO-9215 modules.

I am using the DAQ assistant to pull the data into Labview, and then building an EXE file with the Application builder.

Everything works fine on the computer that has Labview installed, but when I run the Application on a seperature computer, all of the inputs are zero.  If I strip down the application to only receive data from 1 module then it works, but if I try to receive data from 2 different modules (same chassis) then it just shows the inputs as zero.

I have the newest version if DaqMX installed on both computers, as well as the Labview 8.5 runtime files.

Any suggestions would be appreciated.

Thank you.

Message Edited by Jeremy@Thermadyne on 03-20-2008 01:14 PM

[Jeremy@Thermadyne]

Okay ignore my question,  the issue wasn't with the modules at all.  I had a custom scaling on one of the inputs and that was causing the issue.  When I removed it, the problem went away.

Can a moderator please delete the thread.

Thanks

[aplonis]

Jeremy,

I have your exact same problem using LabVIEW 8.0 on a cDAQ with NI
9205 and NI 9485 installed. I get no errors, by the blinking lights on
the control panel it would appear that my digital outputs are
happening...but they aren't. And neither is it reading any voltages.

Did anybody solve your issue?

On Mar 20, 2:40 pm, Jeremy@Thermadyne <x...@no.email> wrote:
> I am working on an application which receives analog inputs and displays the data and records it to an excel spreadsheet.&nbsp; I am using the following hardware:
> &nbsp;
> NI cDAQ-9172 Chassis with NI9211, Two NI9201, NI9481, and NI cRIO-9215 modules.
> &nbsp;
> I am using the DAQ assistant to pull the data into Labview, and then building an EXE file with the Application builder.
> &nbsp;
> Everything works fine on the computer that has Labview installed, but when I run the Application on a seperature computer, all of the inputs are zero.&nbsp; If&nbsp;I&nbsp;strip down the application to only receive data from 1 module then it works, but if I try to receive data from 2 different modules (same chassis) then it just shows the inputs as zero.
> &nbsp;
> I have the newest version if DaqMX installed on both computers, as well as the Labview 8.5 runtime files.
> &nbsp;
> Any suggestions would be appreciated.
> Thank you.Message Edited by Jeremy@Thermadyne on 03-20-2008  01:14 PM

[aplonis]

If you used the ExpressVI "DAQ Assistant" in your program, I may have
the answer for you.

NATURE OR THE PROBLEM (as happened to me):

Jeremy, here is what worked for me. I had used the same Dell M90
Workstation to build two prior EXEs from LabVIEW. The first one does
not relate because the DAQ hardware was LabJack, National Instruments.
The second does relate in the hardware was an identical (but not self-
same) cDAQ hardware setup. I had bought two of those.

So when connected first time to the cDAQ it was tagged with the name
cDAQ1 (note the numeral "1") by DAQmx the first time I plugged it in.
That system worked fine. It transferred fine to another PC because the
same thing happened there. It's the default.

Now comes the third time, and I plug in a second cDAQ wherupon DAQmx
names it cDAQ2 (note the numeral "2"). This is on my Dell M90
Workstation where I build stuff but don't run tests upon. I use that
to build for other PCs to run later. Anyway, I built my entire VI and
it worked fine.

But it would not translate to another PC which had not similarly had
two cDAQs plugged into them. The VI is looking for cDAQ2 and that
other target PC is thinking it has cDAQ1 (because it's only seen one).

HOW TO FIX IT:

On my target PC where the test is to run via the *.EXE version of the
VI here's what I had to do. Call up Measurements and Automation
Explorer (NI's MAC) program. Browse through Divices and Instruments
with your cDAQ plugged in and rename every instance of "cDAQ1_foo_bar"
to "cDAQ2_foo_bar". Then start your *.EXE and it should work. Anyhow,
mine did.

Hope this helps,

Gan

On Mar 20, 2:40 pm, Jeremy@Thermadyne <x...@no.email> wrote:
> I am working on an application which receives analog inputs and displays the data and records it to an excel spreadsheet.&nbsp; I am using the following hardware:
> &nbsp;
> NI cDAQ-9172 Chassis with NI9211, Two NI9201, NI9481, and NI cRIO-9215 modules.
> &nbsp;
> I am using the DAQ assistant to pull the data into Labview, and then building an EXE file with the Application builder.
> &nbsp;
> Everything works fine on the computer that has Labview installed, but when I run the Application on a seperature computer, all of the inputs are zero.&nbsp; If&nbsp;I&nbsp;strip down the application to only receive data from 1 module then it works, but if I try to receive data from 2 different modules (same chassis) then it just shows the inputs as zero.
> &nbsp;
> I have the newest version if DaqMX installed on both computers, as well as the Labview 8.5 runtime files.
> &nbsp;
> Any suggestions would be appreciated.
> Thank you.Message Edited by Jeremy@Thermadyne on 03-20-2008  01:14 PM