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. Is this some problem/limitation with the hardware?
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, it triggers seemingly as fast as it can. If it is used as one of the logic triggers, it is always true.
This could conceivably be a software issue - I only noticed it since upgrading to the new version, but equally this could have existed prior to the upgrade (which was from a version from mid 2013).
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.