09-10-2014 07:29 AM
ah ok thanks.
i changed the DAQ inputs to DAQMQ Read.
But now i have 2 different Tasks so my program is slower.
The outputs can stay in DAQ Assistant because thay dont produce dynamic data?
09-10-2014 07:41 AM
@nkritsch wrote:
i changed the DAQ inputs to DAQMQ Read.
But now i have 2 different Tasks so my program is slower.
Why? You can have multiple channels in the same task.
I would do the same for the Outputs. Put them all in a single task (this is with the assumption that everything is on just a single DAQ board).
09-10-2014 07:59 AM
Crossrulez has already said much of what I would say. One thing I'd like to add is that you can convert a DAQ Assistant Express VI to a normal VI by right clicking and choosing Open SubVI. This can then show you the code that would normally get ran by the Express VI.
DAQ Assistant, and Express VIs are limited in what they can do. Want to change timing mid test? Well you can't. Want to stop the task and add some more channels? Well you can't. Want to choose what channels to read programatically? Well you can't.
But if the DAQ Assistant meets your needs, and you never need to add requirements to how data is measured, then DAQ Assistant can be used. It was wrong of me to say you shouldn't use it. Just know when it is appropriate to use DAQ Assistant.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord