Polling with isReady after RunBlock

Post general discussions on using our drivers to write your own software here
Post Reply
Posts: 0
Joined: Wed Jan 29, 2014 1:31 pm

Polling with isReady after RunBlock

Post by slayes » Wed Jan 29, 2014 1:50 pm


We're using ps6402/ps6403 devices with a sofware written on our own, distributed by our company to many customers. It has been working for the last 3 years without major problems.

we have implemented a solution that uses the isReady() function to poll continuously the scope after a runBlock call (trigger is armed). This looked to work fine so far. We recently noticed that this sequence may fail (isReady never returns "ready") especially when these API calls are performed just after system power-up. A second call to this API sequence without any restart of the scope will work.

So here are my questions :
- does the behavior of the DLL can be different just after its loading into the memory ?
- Shall we introduce a tempo between the isReady calls / use a callback model ?

Here are my versions : driver / win7 pro 64bits

Thanks for your help.

Posts: 2855
Joined: Tue May 31, 2011 3:43 pm
Location: St. Neots, Cambridgeshire

Re: Polling with isReady after RunBlock

Post by Hitesh » Mon Feb 03, 2014 11:23 am

Hi slayes,

What sequence of calls are you making prior to ps6000RunBlock?

When you refer to 'system power-up', is the PicoScope's power supply being powered on?


Software Dev. Engineer

Post Reply