PicoScope 7 Software
Available on Windows, Mac and Linux
ps3000_run_streaming_ns returns 0
-
charliePico
- Newbie
- Posts: 0
- Joined: Thu Jul 16, 2020 1:59 pm
ps3000_run_streaming_ns returns 0
Hi,
I'm using ps3000 model 3424. The sdk command ps3000_run_streaming_ns always returns 0.
The code used to work before on a previous version of the firmware. We made some changes to the firmware. But none of the operating parameters / limits were changed. So there is no impact on the parameters being sent to ps3000_run_streaming_ns().
However when I run the code on the new firmware, the command always returns 0. Any suggestions?
Thanks,
Charlie
I'm using ps3000 model 3424. The sdk command ps3000_run_streaming_ns always returns 0.
The code used to work before on a previous version of the firmware. We made some changes to the firmware. But none of the operating parameters / limits were changed. So there is no impact on the parameters being sent to ps3000_run_streaming_ns().
However when I run the code on the new firmware, the command always returns 0. Any suggestions?
Thanks,
Charlie
Re: ps3000_run_streaming_ns returns 0
Can you give more details on which programming language you are using?
Also what OS you are using; Windows/linux etc and if its a 32-bit or 64-bit OS
Which version of the SDK packag are you using or dll driver version?
Could you email these details and your code if possible to support@picotech.com
Also what OS you are using; Windows/linux etc and if its a 32-bit or 64-bit OS
Which version of the SDK packag are you using or dll driver version?
Could you email these details and your code if possible to support@picotech.com
Regards Andrew
Technical Specialist
Technical Specialist
-
charliePico
- Newbie
- Posts: 0
- Joined: Thu Jul 16, 2020 1:59 pm
Re: ps3000_run_streaming_ns returns 0
Hi Andrew,
Below are the details:
Driver Version: 4.0.17.1457
USB Version: 2.0
Hardware Version: 6
Variant Info: 3424
Serial: VNR43/054
programming language: C
platform: Windows 10 64-bit
The voltage values are scaled between 0-5V.
It seems the previous trigger threshold value (3672) used on Channel-A does not work anymore. Since auto_trigger_ms was set to '0' the oscilloscope waited indefinitely for the trigger. This worked with the previous firmware version.
I tried setting a value for auto_trigger_ms to force the oscilloscope to start collecting samples after a delay of 425ms. I also changed the trigger threshold value to '0'. This seems to work for some signals but not all.
ps3000_set_trigger(unitOpened.handle, A, 0, PS3000_Raising, 0, 425)
So now I can get some signals completely, while the others get cut because of the hard-coded delay value. It would help if I could get the code to respond to the new firmware as before - i.e. the oscilloscope starts collecting data when the trigger threshold value is reached.
Below are the details:
Driver Version: 4.0.17.1457
USB Version: 2.0
Hardware Version: 6
Variant Info: 3424
Serial: VNR43/054
programming language: C
platform: Windows 10 64-bit
The voltage values are scaled between 0-5V.
It seems the previous trigger threshold value (3672) used on Channel-A does not work anymore. Since auto_trigger_ms was set to '0' the oscilloscope waited indefinitely for the trigger. This worked with the previous firmware version.
I tried setting a value for auto_trigger_ms to force the oscilloscope to start collecting samples after a delay of 425ms. I also changed the trigger threshold value to '0'. This seems to work for some signals but not all.
ps3000_set_trigger(unitOpened.handle, A, 0, PS3000_Raising, 0, 425)
So now I can get some signals completely, while the others get cut because of the hard-coded delay value. It would help if I could get the code to respond to the new firmware as before - i.e. the oscilloscope starts collecting data when the trigger threshold value is reached.