![]() This error can occur if two tasks sharing an acquisition loop have different sample rates. However, if the error is occurring because data is not being readout of the DAQmx buffer fast enough (Case 1 above), increasing the buffer size will only delay the occurrence of the error, and will not eliminate it completely.Ĭase 3: Reading two tasks running at different rates, using one acquisition loop Occasionally, this error can be resolved by simply increasing the size of the host side data buffer manually. Note: Do not use Highlight Execution with code that contains a DAQmx Read, since it will slow down the execution and cause a buffer overflow.Ĭase 2: PC Buffer Is Too Small to Hold Task DataĪnother reason for this error is that the DAQmx PC Buffer is too small to hold the amount of data required by the DAQmx task, causing an overwrite in the DAQmx PC Buffer before data has been acquired at all. If increasing the while loop performance is not an option, you may need to lower the sample rate for your application instead. If the while loop is performing more slowly than expected, you may need to implement a Producer/Consumer architecture to move other processes, such as logging, post-processing, analysis, and user interface functionality outside of the acquisition loop. Note: DAQmx Read will automatically wait until the requested number of samples are available, so it is usually only necessary to control one of these factors in a particular application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |