PicoScope 7 Software
Available on Windows, Mac and Linux
The high CPU usage of the PS2000 driver seems to be the real reason why it is so hard to acquire data continuously with a PS2000 scope.maximus-ms wrote: When PicosCope run it takes until 50% of CPU time.
Having done much testing with a PS2005, I use a delay of 1 millisecond between calls to the driver (not 32 as you do). This seems to be important. This way I can acquire data continuously with a sample rate of 5 MHz.maximus-ms wrote: In result about some 10's of thousands samples is less then -32767 (losted samples) for 10 seconds.
How to fix the problem?
Of course. Firstly I used 1-10 ms delay, but later I saw size of bufer which I get from DLL is 32512 samples, so it are some empty calls before buffer reach 32512 size. So I desided use 32-33ms delay.Have you tried reducing the sleep time?
I tried. The function doesn't work correct or I cann't use it.Try calling the ps2000_overview_buffer_status() function after every call to ps2000_get_streaming_last_values() and see if it returns a non-zero value - this will indicate a buffer overrun.
Code: Select all
short previous_buffer_overrun = 0;
ps2000_overview_buffer_status ( handle_ps, &previous_buffer_overrun);
DLL version 2.0.8.105What version of the ps2000.dll are you using?
The PicoScope6 (software) uses 35-40% of CPU time... hm...maximus-ms wrote:
When PicosCope run it takes until 50% of CPU time.
The high CPU usage of the PS2000 driver seems to be the real reason why it is so hard to acquire data continuously with a PS2000 scope.
The device supplied with a blue USB cable. What does it mean?Hitesh wrote: Was your device supplied with a blue or white USB cable?
So... it is no reason!! I have same results.Hitesh wrote: Please download SDK R10.4.3.1 from our website (http://www.picotech.com/software.html) and try the dll that is in there.