daq acquisition steps in teststand?

[david_jenkinson]

Hi,

I have a general "preferred architecture" question.  I'm going to use teststand to sequence a test in which labview acquires a waveform.  Psuedo code for teststand sequence, which will call labview modules, will be:

Setup and Start DAQ task

More steps

Stop DAQ task

Analyze acquired DAQ waveform

I'm mulling over the best way to pass the daq task cluster and waveform data between steps.  The simplest and most straightforward seems to be just to pass the task and waveform data directly out into a teststand variable by creating the proper data types in teststand, and reading them in where needed.  But I was wondering if it would be better to have all the vi's in a project, which would allow all the vi's to access the daq task and waveform data via shared variables.  It seems a bit cleaner, maybe.  Thoughts?

Thanks for any insight

David J.

[RaviShrigiri]

One of the approaches that we used :

We had to control multiple DAQ I/o and we preferred that the handles and data to be stored in TS only.
Each DAQ task (handle) was stored in a known TS variable name and it helped during programming.

Also your called functions are modular that way and can be easily used for multithread applications.

Ofcourse the approach that you suggested may save time as varialbes are not passes between TS and LV.But may get complicated with multi channels and multithread.