I'm using a Picoscope 6402B (FW 184.108.40.206 / 220.127.116.11, HW 1 1, Driver 18.104.22.168) w/ the (most recent) SDK on Win7 to aquire many (relatively) long captures at one of the higher sample rates (1.25 GSPS). The scope is triggered from channel C, acquires channels A & B.
After a (somewhat random) number of acquisitions (hundreds to thousands, depending on the exact parameters) , the scope is not triggered (although the signal is fine and there should be at least an auto-trigger in any case) and it is also impossible to stop and re-arm it (any subsequent RunBlock fails). I checked all my code as I suspected the problem there initially, however, at some point I swapped the unit against a second, identical scope (even bought in the same order).
With the second scope, everything is working as expected, no problems... Does this indicate a HW problem or is there a newer firmware that solve the issue? Is this a known problem?