02-15-2008 11:40 AM
02-15-2008 12:13 PM
I do not think that copying a task and setting all the parameters and things like that is going to be any faster. In fact I would say that it is going to be slower. Maybe you could show us the VI. What is it that is taking so long, Is it the setting up of the parameters or is the actual acquisition, the setting up of the parameters is always rather fast for me.
How are you setting the parameters. You should do it like this:
I have always had some trouble with the copy task. You need to make sure that the task that you are copying is not running, (ie stop it before you copy it).
Show us your code and maybe I can help more.
02-20-2008 04:58 AM
Hi Joe, thanks for replying.
I'll tell you what im ultimatley trying to do. I've got a clock signal and im using triggering to cause 2 tasks to run, one takes some measurements and after that the other one sets a voltage.
I had previously tried to get the task definition for the measurement outside the loop but when i run the loop the triggering wasnt working properly so to cheat i ended up defining a new task every time, only problem with that was its really slow but was suitable for the system at the time.
Now though im trying to get the system to run as fast as possible, ultimatley trying to get the loop to itterate about every 30us which is the time it takes my electronic load to settle. Ive stopped copying the task now but this is my code..
02-20-2008 05:41 AM
Sorry theres a couple of little mistakes in that one..
This one is working and triggers fine when my clock signal is about 100Hz.. if i try a kHz it cant keep up.
02-29-2008 11:03 AM