DAQ - tasks?

[Viller]

Hi

I have designed a simple VI where I can write data out to a "current Out module" --- I´m a little confused about creating tasks and when and where to use them? I have attached a screen shot of my design. - In the "create channel" block there is a "task in" - if I create a task with let say DAQ assistant and connect it to this terminal, can I then disconnect the "min" and "max" terminals as these are specified in the "task"? - Furthermore the function of the "write block" isnt this specified in the task as well?? - I´m just a little confused about the whole idea with a task, as in my design I dont seem to need it???

ps. my design is "stolen" from an example

[Dennis_Knutson]

If you create a task in MAX, then you do not need to also define the range, terminal configuration (i.e. RSE, Diff, etc),  units, scaling, etc. with the Create Physical Channel. A task also has timing information. You still need a DAQmx Write in order to define the actual ouptut voltage. Tasks are convenient and can save some coding.

I haven't used tasks in my DAQ programs yet. One reason is that I prefer to have complete control in the LabVIEW program which cannot be edited when deployed. I don't want an overly curious user going into MAX and messing anything up.

Message Edited by Dennis Knutson on 02-19-2007 07:49 AM

[Viller]

Thanks......that makes sense.. I'll try it out