Hi Hitesh, after a long time I finally respond... As I wrote in my last reply, the update of the driver caused no effect. Now we finished the implementation phase and there are no errors anymore. Maybe that's because we only run our sequence once and during implementation we had problems e.g. after ...

Hi Hitesh,

thx for your ideas!

We updated the driver to 10.6.10.22 without success.

As next step we remove the closing of the unit each time so that we'll only call the close function once at the end of our process.

Regards

Hi Hitesh, Which version of the ps5000a.dll are you using? we're using the dll from the delivered CD R10.5.2.1. When you refer to the 27th run presumably you are running a loop to collect the data and not opening and closing the unit each time? Exactly, we're calling "PicoScope_5242A_init_config" in...

Hi Hitesh, thank you for your response! We tried it with calling ps5000aStop after the is ready indication but after 26 successful runs the 27th ps5000aRunBlock call was again answered with a 0x07. :cry: What could happen that PicoScope is not answering any commands comming from PC? Is it a driver i...

Hi, we try to run a simple data recording out of LabWindows CVI (C-code) of two channels using block mode. The first time we call the function ps5000aRunBlock and download the recorded data works well. But if we repeat this, we get PICO_STATUS = 0x07 (PICO_NOT_RESPONDING) as response when calling ps...