3405d Time delay

Post any questions you may have about our current range of oscilloscopes
Post Reply
dyoon
Newbie
Posts: 0
Joined: Thu Dec 31, 2020 7:42 am

3405d Time delay

Post by dyoon »

Hello,
I am a user of 3405d pico oscilloscope, and I sampled data using Normal Runblock' mode not 'Rapid Block' in sdk code(python).
The problem is that time intervals among each waveform take much time.
I talk you specific conditions of my measurement in below.

Timebase : 4 (16 ns)
NoSamples : 650,000 (0.01s)
By using loop function in python, I was supposed to obtain successive data with 100 waveforms (i.e. the measurement time is 1s). At the same time, I calculate the measured time for each waveform, and the results are in below.
t0: 2.0936561s
t1: 3.1305201s
t2: 4.1658108s
t3: 5.2053143s
t4: 6.2442822s
t5: 7.2855299s
(I measured these times when the function of 'ps.ps3000aRunBlock' is activated in each loop)

In the manual of PicoScope 3000, it is illustrated that the gap among each waveform is tens of milliseconds with normal runblock mode. Thus, I thought that the tens of milliseconds delay can be neglected in my experiment.
However, the time delay shows roughly 1s not tens of milliseconds.
I tried to find reasons for this problem, and it was confirmed that data collection to finish the capture takes much time and roughly 1s. The capture code is written :

####################
ready = ctypes.c_int32(0)
check = ctypes.c_int32(0)

ready_rev = ps.ps3000aIsReady
ready_comp = ctypes.byref

while ready.value == check.value:
status["isReady"] = ready_rev(chandle, ready_comp(ready)) # This loop takes 1s
####################

To reduce the time interval among each waveform, what shall I do?

Post Reply