That answers my question perfectly. Thank you!

Can anyone enlighten me as to what the direction parameter is doing with the pulse width qualifier? I can't anywhere in the docs see much about it beyond "the direction of the signal required for the trigger to fire". I posit that it's the direction that resets the counter, but that's not written do...

Thanks Karunen.

Do you know which was the last release to not have this bug? I previously upgraded because I had the odd annoying crash. It's not a showstopper, but I'd be great to downgrade to a version that still has the bug fixes.

Cheers,

Henry

This is with PicoScope 6.8.8.16. Further investigation of the problem shows that the ext trigger is basically _always_ triggering (from my description previously, this is actually a different symptom, but I didn't investigate thoroughly last time). If ext is set to be the trigger, whatever the input...

With a Picoscope 4227, I'm trying to trigger on the EXT input. The signal will trigger reliably on channels A and B, but if I switch the triggering input to EXT, and set it as such in Picoscope (and change nothing else), it fails to trigger at all. It's a 2 us 3.3V pulse, so it's not a strange input...

Yeah, I'm sorry about that - it was because I noticed the new lib that I realised I'd forgotten all about mine. Each has features the other is lacking, so they might serve as a useful reference to each other. There is a problem in that I've used Cython and you (I recall) use ctypes.

Cheers,

Henry

I wrote a python library a little while ago for wrapping the libps3000a which I finally got around to posting online: https://github.com/hgomersall/PicoPy It's pretty capable, with (I think) all the trigger capabilities exposed through a neat interface as well as nice pythonic wrapper class (pico3k)...

Great, thanks!

I noticed that the 3207B is supported by the linux driver. Is this with USB3 enabled, or does it fall back to USB 2?

Cheers,
Henry

I'm encountering a situation where apparently the overflow flag is not being raised desipite clipping occurring. Is this a problem that I might be expected to encounter? My work around is to inspect the maximum absolute value of the returned array and change the voltage range if it's close to the li...

Thanks Martyn. I'd read it before, but managed to forget it in this context.

Right, so I've now read 2.1.6 with the following: Note: This feature is provided for backward-compatibility only. The same effect can be obtained more efficiently with the PicoScope 3000 Series using the hardware averaging feature (see Downsampling modes). I guess that answers my question. Cheers, H...

My scope is a 3000 series scope. Could someone explain any difference between setting the oversample argument and using PS3000A_RATIO_MODE_AVERAGE when copying the data from the device (indeed, being a long, it seems that the latter has more flexibility). I initially thought that the oversample used...

Thanks Ziko 1. You cannot create an impossible trigger because separate conditions are OR-ed together - see P78 of manual. In the example the scope would always trigger, rather than never trigger (it would be like trigger mode "none" in PicoScope, or writing a single condition with all rows set to "...

I have a few questions advanced triggering. 1) What happens if I create an impossible trigger condition? (say, 2 conditions in which channel A is set to True in one and False in the other). Does this just result in the trigger never happening? 2) Does the pulse width qualifier trigger entirely indep...