Driver Development Kit (DDK)

cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure a continuous pulse generation that doesn't end after the VI exits with DAQmx?

Hi,

I'm just learning the DAQmx and I have run into a problem.

With the legacy DAQ API I could configure a counter to create continuous pulses and
when I needed change the freq or duty cycle, I would just call the the configuration function
again. The pulses were generated even after I closed LV, so it was all in the hardware.

Now, with DAQmx api, it seems that this is not possible. I read a forum post saying that
LV will end the pulse generation after the VI exits. Is there a workaround for this?
I could ofcourse create a LV thread for this, but I liked the old one better Smiley Happy
It was simpler and I didn't need to worry about threads so much.

All LV operations are going to be inside a DLL that is called from outside of LV, so I can't
use LV threads in a simple way, e.g. putting things inside a while loop. Just that you'll
know why I wan't to avoid using the threads.

Thanks.
0 Kudos
Message 1 of 2
(6,324 Views)
Sorry, wrong forum.

I created a new topic in the correct forum. If someone is interested, it can be found from here.
0 Kudos
Message 2 of 2
(6,321 Views)