Datasheet for the 5444B https://www.picotech.com/download/datasheets/picoscope-5000ab-series-oscilloscope-data-sheet.pdf Datasheet for the 5444D https://www.picotech.com/download/datasheets/picoscope-5000d-series-data-sheet.pdf The difference is that the D model is USB3 and the B model is USB2, but ...

The development team have looked and don't see any particular issues. They have suggested that you do a test with PicoScope 6 where you set the time across the screen to a much longer value, you would then see that the trace results are similar with PicoLog 6. Try with 10 Secs/div for starters and s...

I have asked for comment from the development team, I will post a reply once I have a response.

There are no custom probes within the Test and Measurement software to support the automotive accessories as we don't recommend the use of our T&M Scopes in the automotive environment. You may wish to look at the PicoScope 6 Automotive software https://www.picoauto.com/downloads and check the custom...

I would suggest that you go to Tools->Preferences->Sampling and change the Slow Sampling Transition time to a value that is slower than the time you wish to collect. You won't be able to see the data as it is collected, but as data isn't being streamed to the driver you should be able to stop collec...

In the example Channel A, and both of the Digital Ports are enabled, which means the fastest possible sampling rate is 125MS/s

Disable the second Digital Ports on line 352 and check to see if you can set 250MS/s

Apologies for the delay, I am working remotely and didn't have access to the correct scope. I have now confirmed the issue and it is a driver bug which I have raised with the development team.

As a first look the PicoLog traces are greatly zoomed on the vertical axis (120uVolt) when compared to the PicoScope traces (10mVolt) so the noise automatically looks bad. I would also suggest sampling at 1msec per channel in PicoLog and select "Latest Sample" and not "Average" to see what you get a...

I would change the math channel 60/((1/freq(A))*2) to 30*freq(A) which is the same. The reason you are getting the crash is that at the very start of the trace the frequency is unknown as there haven't been the crossing points to determine it, you will see no trace in the math channel plot. And if y...

I would be keeping an array of device handles that are assigned when you open the units and then use these values for the close unit calls.

Actually I can see the issue you have, the 20200708-0001.psdata file I had originally loaded for comparison was the earlier one you sent through not the second one. I will need to test this against a real scope tomorrow.

If I step through those files each buffer in turn is different from the previous one, and if you compare file to file the same numbered buffers are different, so I am still at a loss in seeing what you are. One point when you run again are you are allowing it to fully capture the 1000 buffers and st...

The waveforms in the file you sent look perfectly feasible for a rapid block capture with those trigger settings.

What makes you say they are from the previous run ? can you make a short video to highlight the issue.

If you use the waveform buffer tools highlighted you can step through the 1000 rapid blocks that you have captured

Can you post a psdata file for your rapid block capture where you only get the first waveform so we can take a look at your setup.