Nov 06, 2012 - 10:17 AM
It has to do with the capturing method PicoScope uses to give you a "screen buffer" or a number of automatically saved screens. There is a time delay between one screen to the next, often referred to as the "Pico Gap".
If left unchecked, "Murphy's Law" dictates that whatever anomally you are attempting to capture with PicoScope WILL fall into that "gap".
There is not a current function or setting to change to eliminate the screen buffer and hence the gaps. One could use a Single or Repeat trigger, with it set up above where the signal can cross the threshold, and use a slow enough timebase (200ms/div or more) to cause Pico to enter a streaming mode. The signal(s) will then stream "live" up to the trigger point (preferrably set up to the far right of the screen) and continue to stream until trigger is met (which you are trying to avoid) or you freeze capturing manually (hitting the space bar or left clicking on the stop button).
HTH. Later, Matt.
Source: I will not take credit for this technique as a gentleman by the name of Aaron Koeppen is the first person I've seen use it or mention it as a potential work around.