Hello Jack,
Reviewed the code.
Remember The way labview executes code, Labview executes code by flow of information meaning that it is going to wait untill the neccesary items are ready before executing the next part of the code.
For example If we want to make a simple add function for "x" and "y" labview is going to wait untill both inputs are ready for operation before operating and outputing "z" as a result.
It does it the same way everytime. I took the time and rearranged the code so we can understand it better, The execution happens from left to right, from top to bottom.
If we refer to the image, the arrows show us the flow of information of the VI, The DAQ assitant, the filtering of the signal and the Triggering is done before you actually output data through device1 analog output.
The code is expected to work that way cause it waits untill done acquiring with the DAQ asistant to start generating an output.
I can think of different options,
-You can modify this VI so that the output takes place regardless of the input data
-Having two different vis where you can set the read and write at different rates, using a functional global variable.
-Using a producer/consumer architecture.
This is an example that I think might be useful.
Hope this was helpful,
Luis Martinez.
Applications Engineer.
National Instruments.
