What we have seen is the normal behavior for normal trigger mode for all SDS-series scopes. Just because it is different to other brands, this doesn’t automatically make it a bug. Where is the problem?
10MHz sine wave, 50% amplitude modulated at 50Hz, run mode:
Sine_10MHz_AM_50%_50Hz_Run
The usual intensity graded display. Now hit the [Stop] button.
Sine_10MHz_AM_50%_50Hz_Stop
Scope now knows that the user wants to stop and it shows the last acquisition. All the previous ones can be found in the history if needed.
Same scenario again, scope is in run mode, but now instead of hitting the [Stop] button we turn the input signal off.
Sine_10MHz_AM_50%_50Hz_Off
Scope is “Ready” and waits for a new trigger. It does not clear the screen buffer, which contains some 3300 acquisition records, captured within about 40ms. The scope does not know that the user considers the session to be over. Other brands seem to implement a timeout, Siglent does not.
Big problem?
No. If we desperately need to see only the last record, we can always hit the [Stop] button anytime we want.
Sine_10MHz_AM_50%_50Hz_Off_Stop
Voila, there is the latest acquisition again. And all the others in the history, where we can play them back at any speed we want to watch the original signal again, even though it’s long gone.
@rf-loop
The user has the choice already. It’s the stop button. Do we really need an automatic timeout? I for one do not, for sure.