Hello,
I might be able to shed some light on this issue. There is a bit of overhead when configuring your DAQ board. Therefore, the "config" VIs will take longer then expected. The actual acquisition portion, however, shouldn't take long at all. Typically, if you are running a time sensitive application, you will want to do all your configuring before you need to acquire data. Once you are ready, use the AI Control (Start) to arm the acquisition. Since your board can handle up to 200kS/s, you will be able to acquire data at this rate (5us and not 0.4s) however this is using the buffer transfer and you are not reconfiguring for each acquisition.
It seems you might be using a loop and reconfiguring your acquisition each time through the loop, thus giving y
ou a limited performance because of all the configuring. Unfortunately, there is no way to eliminate the performance overhead of the configuration VIs. You have to design your final application around this limitation.
There is however another option. LabVIEW 7.0 and the new NI-DAQ 7.0 driver (only works with LabVIEW 7) have optimized the single point acquisition process. NI-DAQmx (part of NI-DAQ 7.0) defines and enforces a state model, which eliminates unnecessary reconfiguration of input limits, timing, triggering, and accessories (all done behind the scenes) and thus provides higher performance. It is currently over 10 times faster than NI-DAQ 6.9.
You're best bet though, is to design for a buffered acquisition in which you don't have to reconfigure each time. Hope that helps. Have a good day.
Ron
Applications Engineer
National Instruments