I'm using the ps3000 API to get some measurements from a 3204. But I have a problem when using the streaming mode and stopping it again. It then just freeze in the ps300_stop function, and ill have to plug the cable for it to continue. PicoScope 6 and Picolog works fine. It seems like I cant interrupt the streaming.
The smallest code i get it with. (C#)
short[] bufferA = new short[60000];
short[] bufferB = new short[60000];
I've tried it and it does the same with the streaming mode. So it fail with both PS3000con.c and the C#.
When it fails I have to unplug the USB and remove the power cable from the pico and then put the power cable in again and then put the USB cable in again for it to work.
I've tried the 6.2.3 version, and looked if there was some new DLL in it. It was the same, so no win in that version either.
I've also tried it on a clean Windows XP, installed the drivers with the PicoScope 6.2.2 installation, plugging it in, and running the PS3000con. Then it freezes also when ps3000_stop is called.
I'm trying to re-create the problem using the console example. When you run it and select 'S', what happens? Does it hang on the first call to ps3000_stop?
It retrieves the measurements fine. Only when closing or stopping it fails.
I have tried it on three different computers: Two of them Windows XP (Lenovo Thinkpad T60 and a unknown) and one Windows 7 (Lenovo Thinkpad T60).
In Windows XP it is possible to call the ps3000_stop function after streaming and it returns to the menu. But.. when pushing X to exit and leave the memu loop, it freezes at ps3000_close_unit() instead.
In Windows 7 it already freezes at the ps3000_stop. So it get a little further on XP, but it will not allow the unit to be closed properly in any of them.
If I close the console and start it again, the pico is not correctly shut down and I have to reconnect the power and USB cable.
The 3.6.4.7 behaves different than 3.6.4.6 in the ps3000_stop command.
The behaevior in 3.6.4.6 was when it was called, it kept using cpu cycles in the setAdvTriggerDelay function for 10 seconds and then the threads shut down. In the 3.6.4.7 version it stops imediately when ps3000_stop is called. But both don't return control to the program and shuts the picoscope properly down.
I hope it is ok to enter this old thread. I am just trying to run the PS3000con.c example on Linux. I am using the driver release 3.6.2.0 Linux provided on the homepage. I do observe the described behavior, that the ps3000_stop() does not return to the console program. The device does not get stopped and I do have to plug USB off and on to get access to it again.