Considerable time passes between pressing the STOP button and the start of
drawing traces with sample data. While no UI response can be perceived in
this period of time. The run/stop illumination remains green, the main area
The effect is most probably seen with huge amounts of sample data and the
use of non-streaming acquisition devices, where retrieval of sample data only
occurs after acquisition has completed. It gets worse with reduced throughput
for sample data retrieval (slow physics, or less than perfect implementation).
It was specifically observed with asix-sigma, several hundred meg samples,
and the current driver implementation which might download, uncompress, or
submit to the session bus in ways that could use improvement. Reporter is
Michael Kaplan via the ML, I've seen this during development of the fix
that he tested as well.
It's to get determined whether hitting the STOP button could result in some
earlier UI feedback. Though driver architecture might prevent the UI from
telling "stopping" from "stopped, and data available". Could hitting the
STOP button (or pressing SPACE) "dim" the green run/stop illuminator perhaps,
before it goes completely dark after the acquisition has terminated?
For the record: The issue was noticed with and reported against Asix Sigma
specifically, but might reproduce with e.g. serial attached scopes or similar.
It's the combination of non-streaming, deep memory, and slow comm channel
which makes the issue noticable.