Setting up a Vi to take data from ~ 25 inputs

[Dan]

I am using a PCI-6033E DAQ under labview 7.1 on a PC running W 2000 and
plan to take data on ~ 25 inputs , and average them for a short period
of time. The objective is to get operational dfata on a large air dryer
system and need pressure, temperature, humidity and air flow data
in the incoming air stream. adn in other parts of the system. The
apparatus would be modified with the airfow sensor being slightly
moved farther a small distance into the airstream and this data taking
process repeated.

I would appreciate being pointed to a reference on setting up this
large a number of inputs in one vi ( or more if necessaery) , and
averaging the results - for each run and present the results in a
graph- or an impo
rt to an Excel file to then plot the results. and be
able to compare results between two runs with different insertion
distances of the airflow sensor into the air stream
That objective for this airflow sensor movement is to obtain the air
flow profile in a ~ 10" ID pipe. and other parts of the air dryer
system

Thanks in advance .
Dan

[AggieBrett]

Dan,

There are two things to consider right now. The first is the programming architecture and the second is the DAQ programming.

DAQ Programming:
For the DAQ programming there are a couple of ways to set this up. Both methods are equally valid and differ only by what you are more familiar with.

The first is to programmatically setup your tasks to run different types of measurement. The following link will point you to a knowledge base on this. http://digital.ni.com/public.nsf/websearch/89B7218072F1CAF686256DC500722B6E?OpenDocument

The other way is to create a global channel for each input and group them all together on the block diagram using the DAQmx CHAN constant with I/O filtering set to �allow multiple channels�.

Program Architecture:
F
or the architecture I suggest some form of producer/consumer loop. There are templates for this setup that come with LabVIEW. This setup will allow for your acquisition and processing to run in parallel loops, which should reduce the chances of one interfering with the other.(note that there is always a limit to what you can do based on your hardware)

I think this should get you started in the right direction. Hope it helps.
Brett