Hi Azazel,
From what I understand in your post, you'd rather have the Multi-Fetch I16 VI return only two rows: one with all of the records for channel 0 and one with all of the records for channel 1.
At any rate, there isn't another way to request waveform data from the driver when doing multi-record fetches. During a multi-record fetch, the digitizer is doing single fetches and adds them to the on-board memory in temporal order. The card has been programmed to use the advance trigger to start the next record fetch, and so this is how software interaction is removed from a multi-fetch process. Since the records are stored in the order they were taken, they are returned that way as well.
National Instruments welcomes feedback on products and drivers to improve our customers' experiences. That feedback page is called the
Product Suggestion Center. Please add your comments
🙂If you're worried about software performance during the decimation and signal processing steps in your program, you may want to consider using queues and parallel while loops to distribute the processing load. If you're not familiar with queues, take a look at the Producer/Consumer template under
File » New... and then
VI » From Template » Frameworks » Design Patterns » Producer/Consumer Design Pattern (Data). There is also a Developer Zone tutorial explaining in more detail how queues help streamline data processing applications:
Optimizing Automated Test Applications for Multicore Processors with NI LabVIEW, section "Optimizing Hardware-in-the-Loop Applications"
http://zone.ni.com/devzone/cda/tut/p/id/5899#toc3Please let me know if you'd like further clarification.
Joe FriedchickenNI Configuration Based Software |
---|
Get with your fellow OS users [ Linux ] [ macOS ] | Principal Software Engineer :: Configuration Based Software Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018) Software Engineer :: Measurements RLP Group (until Mar 2014) Applications Engineer :: High Speed Product Group (until Sep 2008) |