Search the Community
Showing results for tags 'task'.
Hello all, My question is: what is your preferred non-volatile way of storing daqmx task configurations? Backstory: For a long time I've used ini files to maintain task configurations between executions of a program. This has worked for primarily static DAQmx configurations but I'm looking at creating a test executive with some degree of flexibility, which means daqmx task configurations start to get more complicated. If you use MAX for storing your tasks: Do you run into problems accessing and maintaining these tasks even though you don't have direct access to the file? Or i
I have a problem I was hoping you might be able to help me figure out. I need to be able to create 6 analog output channels that will have separate data files loaded into them. These channels will be started individually in a timed sequence. I am having trouble getting the analog DAQ tasks created. LabVIEW is complaining when I try to set them up as individual tasks in the same routine. I used a for loop on an array of data files and an array of channel names. The error code is suggesting that I set the channels up under one task. But the problem with that is that I donâ€™t know how
When trying out a new program most error messages that LabVIEW gives me are not very helpful because they refer to "unnamed task" such and such. And so I would like to give names to my tasks. It ought to be simple but still it illudes me. So now I ask... How do I give a name to a task so that error messages then will be helpful?