Test and Measurement Forum

ps3000_stop

Post general discussions on using our drivers to write your own software here

ps3000_stop

Postby Guest » Wed Sep 10, 2008 10:26 am

Hi,
I am runing the PS3026 in block mode and collecting data in a loop. When looking at e.g. ps3000con.c example code, the API functions are called in this order:

run_block
ready
stop
get_times_and_values

In the manual ch 4242 Using block mode, it is said that you need to call
run_block
ready
get_times_and_values

but no stop here.

So my question is, what is the difference of calling/not calling stop after ps3000_ready, can it be omitted when doing calls in a loop? Obviously the code should be a little bit faster without the additional lib-call, but can it cause some error situations etc?

BR,
JMa
Guest
 

Postby bmckenney » Fri Sep 12, 2008 1:59 pm

(I hope I'm not speaking out of turn:)

With the PS2205, I found I had to call ps2000_stop() after the acquisition
(ps2000_ready() said "done"). I don't recall the symptom, but I'm pretty
sure it occurred on the next ps2000_run_block() call.

The PS3000 series might be different, but this seems like the kind of
thing that would be common across product lines.
bmckenney
Active User
Active User
 
Posts: 11
Joined: Fri Jul 25, 2008 4:21 pm

Postby Guest » Mon Sep 15, 2008 6:40 am

Ok,
The reason why I asked is because I have not noted any difference when calling ps3000_stop and when not calling it in the implementation. But it might be wise to call it in either case.
Guest
 


Return to General Software Discussions

Who is online

Users browsing this forum: No registered users and 1 guest