04-29-2008 01:34 AM
04-29-2008 08:35 AM
Hi,
The NI-USB devices have a totaly different approach for buffering write and read operations, then our Plug In boards. because it is USB , the driver buffers all the frames for Write operations in Host memory. For Read operations there is a small memory at the device but the driver transfers as fast as possible and buffers the frames in Host memory as well.
Thus you do not need to configure queues with the config function at all. I have not seen a overflow error so far, even with Full Speed USB.
Hope that helps.
DirkW
01-06-2010 08:28 PM
This is odd because if I wait too long to call ncWaitForState then ncReadMult I start getting messed up data.
Looks like a ping-pong buffer gone astray.
(I have a Sleep() with a user defineable number of milliseconds in the loop that calls ncWaitForState/ncReadMult.)
Don White
Concord, CA.