For someone who is no stranger to English, this is not a problem, but for non-speaking English users, a searchable pdf is a must. Just enter a keyword and see if there is a mention somewhere, if not, try another similar word, etc. I hope the manual will be fixed.
And I would immediately take the opportunity to ask about two range functions.
1. Is it possible to automatically stop the measurement on the screen when a certain phenomenon occurs? I was measuring switching pulses and needed to see the leading edge, but I had to choose a slower speed (roll mode). Then it was no longer as detailed as when I accidentally stopped and caught the impulse.
2. The second query is focused on when I monitor pulses in roll mode, whether it is possible to display the times when the pulse was detected in the time axis above the pulse.
Perhaps I have described everything clearly. If not, then write and complete.
1. You use Normal (not auto) triggering mode and setup trigger for pulse you want to catch... history buffers will hold previous events.
2. On single long capture you setup search function (with method similar to triggers) and it will find all pulses that conform to criteria
3. there is pulse number measurement, that will count pulses above threshold (or rising edges, or falling edges) on screen or within time gates you setup
Thanks so much for the reply. I'm actually just learning with the oscilloscope, but he's already helped me a lot.
1. I tried it and it works exactly according to my ideas. It is even possible to use single mod.
2. I don't quite understand that. Is it possible to make a screen of what it would look like and how to search? I had the roll mod set to high times, for example 200s per piece. I was measuring the signals from the electricity meters and I needed to compare it between the oscilloscope and the Home Assistant and assign times to the individual pulses. To know exactly how many pulses there were at what minute. Is it working?
Thank you for explaining better. For your use case, best is to use triggering (like you already said it works),and set timebase to one pulse width, or a bit longer, not the length of the whole 200sec . Set scope to sequence mode (take a look at manual). Every time you get trigger, it will take one screen and save into memory, and will keep saving them like that, like pages in Power point presentation. In between pulses it will not record anything, simply will wait for next trigger. You can then take a look at how many you got, and every single one will have proper timestamp. You can take a look at every single one too, on screen.
Make note that in Sequence mode scope won't display anything until you stop it. This mode is used when pulses are really close together. If pulses are not that close (more than few milliseconds apart), you can get away with only history mode on. That one functions the same except you don't do anything special. During normal scope sweeps, it will save previous screen into history buffers, same as Sequence mode..
You can also search over history segments...
You really need to read manual in detail. That scope is pretty sophisticated..