Tim,
you asked on Tue, 18 May 2004 10:24:03 -0700:
In LV6 the 'AI read.vi' hogs the CPU waiting for the number of samples requested to be available. someone (sorry for not remembering the name)The idea bvehind this 'cure' is in a 1st call to ask for 0 (zero) samples and to get the number of availabel samples from that call. Than in a 2nd call ask for that number only. If you need more, wait an apropriate time and repeat.
came up with a 'non-blocking AI read.vi' which i have been using happily.
i noticed the new DAQmx 'cont&graph.vi' is hogging the CPU also. is there a cure for it ( i think it makes DLL calls)?
another question: i've been using LV2 style globals to pass data between parallel loopsBoth ways will work. Speed will probably not vary much. But queues are in the end easier to handle and maintain and to separate into different VIs. For example, a listener VI can autostop when the queue gets destroyed by a (the) writer. You do not need any extra technique to stop that -otherwise independent- loop.
and am wondering if a queue is a better way to go?
AND queues are variant as inserted from the libs; YOU define their data type when creating a new queue. A LV2-style global has to be made variant to function that way. (My older templates used strings as data format for LV2 globals and casted any given data to/from strings).
HTH and Greetings from Germany! -- Uwe Frenz
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr. Uwe Frenz Entwicklung getemed Medizin- und Informationtechnik AG Oderstr. 59 D-14513 Teltow
Tel. +49 3328 39 42 0 Fax +49 3328 39 42 99 [EMAIL PROTECTED] WWW.Getemed.de
