Thank you for providing a complete gudance how to reproduce the issue. I've used 100 Hz to 1 MHz sweep and enabled advanced measurements on top of that, just to prove that the scope was running for at least 10 minutes with 3 ms trigger holdoff:
I haven't figured out a good solution because don't know if the user wants to choose the cursor or select an area. If want to distinguish between single and double clicks, I don't know if it's technically feasible.
Do you want to keep the persistance until you clear it?
Please test again with other holdoff values and the exakt procedure as ebastler explained
Thank you for providing a complete gudance how to reproduce the issue. I've used 100 Hz to 1 MHz sweep and enabled advanced measurements on top of that, just to prove that the scope was running for at least 10 minutes with 3 ms trigger holdoff:Please test again with other holdoff values and the exakt procedure as ebastler explained (with 3ms holdoff). This bug is like a mosquito: You only know if its has been killed, if you dont have any itchy place on your skin the next morning.
It was a fun one to figure out together with ebastler though ;-)
Are you testing 1.1.3.5 like we are ?
Cough.
Are you testing 1.1.3.5 like we are ?
Edit: I did not find that specific holdoff time to be critical. A minimum holdoff time is required to produce the freeze -- it varies with the chosen time base, and apparently must be a bit larger than the sweep time. Any holdoff times larger than that will produce the issue with the current firmware.
Are you testing 1.1.3.5 like we are ?
How could i? But if i would, i would have really made sure that i "slept well, and would not have a itchy bite in the morning".
Improvement suggestion:
Placing the zoom window with a double tap on the upper window does not work, if there is a cursor at the same spot.
Edit:
Improvement suggestion 2:
After having captured a few traces on persistance, moving the traces to measure with cursors is not possible, since all traces except one dissappear.
What you can do is to use history mode, enable persistence...
I use persistance not only for visual aid, since you can really do measurements with it! You can measure min and max of a pulse and roughly the average of it.
I use persistance not only for visual aid, since you can really do measurements with it! You can measure min and max of a pulse and roughly the average of it.
That may work, but 2N3055's point was that the scope has better ways to do it. If you set up a measurement for pulse height (or duration, depending on what you are after), in advanced measurement mode and with statistics enabled, you will get precise max, min and average values. Plus a histogram of the distribution if you care about that!
What you can do is to use history mode, enable persistence...LoL this works in quite a funny way.
If i would have came upon this, i guess i would have called it a bug.
I use persistance not only for visual aid, since you can really do measurements with it! You can measure min and max of a pulse and roughly the average of it.
Thanks to performa01 and electronics hobbyist for checking the trigger behaviour with both, the current and the upcoming firmware. This seems to confirm that, while the symptoms are different from the previously reported holdoff malfunction, the underlying cause is a common one and has now been fixed. Great!
... the scope has better ways to do it.
But when it comes to quantifying things, cursors are better than eye-balling, and automated measurements are better than cursors!
Tap on histogram for large version.
Gates are like cursors that allow you to instruct scope "Here you measure, right here!!"
Also I can confirm, fixed. (if 20 minute run with 10kHz-1MHz sweep (using ebastler's setup) is enough)
Also I can confirm, fixed. (if 20 minute run with 10kHz-1MHz sweep (using ebastler's setup) is enough)
This sweep goes over 100ms?
Tap on histogram for large version.Damn i never thought about that. I thought "neat but without scales kinda useless". Never thought about clicking that. But i gues its in the manual. But i do not go into that now. But you sure made me hungry ;-)Gates are like cursors that allow you to instruct scope "Here you measure, right here!!"Please dont overwhelm me.
... the scope has better ways to do it.It actually was not a simple pulse. i measured over 3 channels.
And in measurements you also have CH Delay page... For inter-channel measurements.
Depending on what exactly you need to measure, you may be able to define a Math function which provides the required combination of the raw traces, then take automated measurements on that.
Depending on what exactly you need to measure, you may be able to define a Math function which provides the required combination of the raw traces, then take automated measurements on that.That sounds very good. I guess i can use CHdelay on two math channels?