LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQ Assistant overhead

Hi,

I'm making a transition from legacy DAQ to DAQmx, and everething is new
and unfamiliar to me.

So, my question is, does DAQ Assistant add some overhead to the VI compared
to wiring the DAQmx VIs manually?

Even a small overhead might make a difference in my app, so I need to know when
I shouldn't use the DAQ Assistant.

I noticed that I can convert the DAQ Assistant to regulat subVI. Should I do this with
all the Assistants when I think they are finished? And is there something useless extra
stuff in the generated code that might slow things down?

Thanks.
0 Kudos
Message 1 of 3
(2,625 Views)
the DAQ assistant does introduce some overhead, but it is fairly small (it depends what you are trying to do). I have found an easy way to learn DAQmx is to use the assistant to configure everything so that your measurements are working as expected, then right click on the express VI and select Open Front Panel and convert it to a VI you can browse into.

Once you have done this, you can see where the overhead will occur, and you can tailor the VI to suit your needs. I normally extract the initialisation and configuration routines and place them in separate VIs that I call only once, and then the main loop of your VI you just need to call the read functions.  
Message 2 of 3
(2,609 Views)
Thanks nrp for the reply.

Your suggestion of making the VIs with the wizard and then manually removing unneeded parts
sounds good. I'll be doing things like that also, at least until I figure this DAQxm stuff completely
to start building them from the scratch.
0 Kudos
Message 3 of 3
(2,587 Views)