What exactly does timeIndisposedMs do?

[elak]

I'm working with a picoscope 4262 interfacing with it through ctypes in python. I've been playing around making some measurements and found some discrepancies I was confused about. I am setting timebase = 2, oversampling factor= 1, and collecting 400000 samples without a trigger. The getTimebase2 command returns the timeInterval as 300 nanoseconds. Running the RunBlock command, though, timeIndisposedMs is returned as 160 milliseconds. This seems about 40 milliseconds too high.
What's curious is, at timebase=1, and all other settings kept the same, the timeInterval is 200 nanoseconds with timeIndisposedMS being 80 milliseconds - which is consistent (since 400000*(200e-9) = 80e-3). Am I misunderstanding or misusing these variables?

[AndrewA]

Hi,
Instead of using a callback function to know if a block/rapid block capture has finished you can poll the device using psXXXXIsReady().
With programming languages that don't support our C style callbacks like MATLAB, LABVIEW you have to use the polling option.
timeIndisposedMs from the psXXXXRunBlock function returns estimated time that capture should take.
So you can then call a delay/thread delay before starting to poll with psXXXXIsReady().
So timeIndisposedMs should equal-
sample internal(s) x number of samples / 1000
I know there were some edge cases of settings that it was reporting bigger numbers than expected.
Sounds like you found some of these issues.
Do you have a list of all results all timeInterval and number of samples you have tested?
Or some test code that I add to a bug report?