Yes, that's right, I'm multiplying each value in the wave with itself in order to exaggerate the differences. This is to see subtle changes more clearly rather than just looking at peak to peak differences. So yes, the two Picoscopes are quite similar, but one seems to be very slightly noisier than ...

Hi Gerry, Please see attached for screenshots of sample waveforms collected by the 2207B vs the 2208B (all collection parameters are the same). As you can see, the actual waves look pretty similar, but by zooming in (the second plot shows the "total amplitude" which is the dot product of the wave ju...

Hi Gerry, This is a late reply, but the issue below was resolved after digging into my Python scripting more carefully and removing any timing delays. I've able to grab a waveform every ~0.2 seconds using the Docker setup I have, which is sufficient for my application. Another question came up today...

Hi Gerry, Yes it does look like the specifications are much higher than what I'm getting. I think it might be the overall effect of multithreaded processing, etc. We are already using the Rapid Block Mode. The Picoscope is being used together with an ultrasonic pulser. The pulser sends out an impuls...

Hi Gerry, Thanks for the response. I am using the Picoscope 2206B. I am not using the Picoscope 6 software, but rather my own code in a docker container. I then use Python to tell the Picoscope when to collect a waveform and save it on the computer. The waveform is generally only 10 us long, includi...

Hi, So I'm using a Picoscope 2000 series to collect ultrasound wave data. I'm controlling it with custom code on a Linux computer. It generally works well, but I notice that it's not able to collect more than one waveform per second. If I set to collect every 5 sec, it's quite accurate. Every 1 sec,...