All acquisitions wait for digital trigger, why?

[digger]

On one computer I have 2 eseries 6023 daq boards installed. One for a digital triggered acquisition, and the other for a continuous (chart recorder type) acq. When running the two seperate VI's, why does the the cont. acq. VI wait for the trigger on the other VI? Appreciate any help.

[Greg_McKaskle2]

> On one computer I have 2 eseries 6023 daq boards installed. One for a
> digital triggered acquisition, and the other for a continuous (chart
> recorder type) acq. When running the two seperate VI's, why does the
> the cont. acq. VI wait for the trigger on the other VI? Appreciate
> any help.

This is because both tasks go through the same driver, and even if they
didn't, they are both loaded into the same OS and could easily affect
one another unless everything is done asynchronously.

Greg McKaskle

[waldemar.hersacher]

Hi digger,

AI Read.vi waits until the samples are in the buffer.
Do following: Call AI Read.vi with 0 scans to read. Look in scan backlog output if any samples are available. If there are samples waiting call AI Read.vi with this output contected to the input scans to read otherwise do nothing.
This prevents AI Read.vi from waiting until samples are in the buffer.

Waldemar