08-24-2005 11:49 AM
Hi Benson,
What do you mean when you say, "But the problem is higher frequency (>100KHz) I measure less accuracy result I read"?
Are you trying to write to your digital line at 100 kHz? Keep in mind that digital output for the USB-6008 is software timed. You cannot run your while loop at 100 kHz. The smallest time increment you can wait in the while loop is 1 ms. In fact, it takes about 10 ms for each iteration of this while loop to run on my computer. This corresponds to a digital update rate of 100 Hz.
Regards,
Sean C.
08-24-2005 09:28 PM
Hi Sean,
The function of my vi is to use DIO to select the different frequency from Function Generator and output frequency to the counter. Then counter compute the frequency and display on the indicator.
During vi is running, DIO is able to select manually and let counter to computer whatever frequency coming from F.G.(Maximum input frequency to the counter is 5 MHz as I check the specification).
I put DIO selector in the while loop(counter loop). The problem I have is when counter is trying to compute higher frequency i.e 100KHz the actually result will be 96KHz(Mabye DIO will share the hardware resource with counter). Without DIO in the counter loop is result can be good but then DIO can be called only once per run.
I hope you can understand what I post, sorry about my English
Thanks
Benson
08-25-2005 03:48 PM
Hi Benson,
I think I understand what you are doing now. I just ran your code with slight modifications (I created the tasks dynamically and linked the error clusters of the two tasks) and was able to read 100 kHz from a function generator.
08-29-2005 07:48 AM
08-30-2005 09:36 AM
Hello,
Your table question has been addressed in this thread.
-Alan A.