I have to think this is a setup issue with my scope but lots of reading and experimenting later I cannot find and answer.
I have a 1054Z which for the most part I am very pleased with. However I have lately had some long-duration work. I am dealing with pulses that are generally around 0.5 to 2 seconds.
With my old tektronix I was able to set the horz to a second and just watch the trace move to the left end then IMMEDIATLY resume to the left-hand-side.
With the 1054z no matter what the horz setting (200ms thru 5s) I find the scope stays blank for several seconds (~10). Finally the pulse arrives and scans across the screen. Then it remains for another several seconds (about 10). Needless to say shifting between pulse lengths the instrument is not fast enough to show the results.
I am guessing I am encountering some type of "screen buffer" which stores several thousand samples including those on the screen and those off. For the usual rapid work I do (Khz and up) this is not noticed.
Does anyone have a similar experience--I am trying to find a command to narrow down the screen buffer to window size-or at least to fix the problem.
Thanks all
Fritz
I have a 1054Z which for the most part I am very pleased with. However I have lately had some long-duration work. I am dealing with pulses that are generally around 0.5 to 2 seconds.
With my old tektronix I was able to set the horz to a second and just watch the trace move to the left end then IMMEDIATLY resume to the left-hand-side.
With the 1054z no matter what the horz setting (200ms thru 5s) I find the scope stays blank for several seconds (~10). Finally the pulse arrives and scans across the screen. Then it remains for another several seconds (about 10). Needless to say shifting between pulse lengths the instrument is not fast enough to show the results.
I am guessing I am encountering some type of "screen buffer" which stores several thousand samples including those on the screen and those off. For the usual rapid work I do (Khz and up) this is not noticed.
Does anyone have a similar experience--I am trying to find a command to narrow down the screen buffer to window size-or at least to fix the problem.
Thanks all
Fritz