Set it up like that with a Math trace, put up some Measurements, and wait a while and see what happens...
Hi alsetalokin4017,
I watched your video and the others on your YouTube channel, and thought I'd try to duplicate the math hang. Please see attached image. I let it run for 8,332 counts (which is a lot more than I saw in your videos) and took a snapshot, it never stopped. Even as I'm posting this it's still running over 10k counts now.
When I put in the USB stick to save the image, I had forgot that the firmware update file was still there that I had used last time to update the machine, and I accidentally selected "OK" and it re-updated the firmware file as it was taking statistics, but even that didn't make it hang - interesting.
If you want me to try something different I'll see what I can do here.
Edit: Now over 11k counts ...
The bug seems to come along with the SP2 firmware. The measurements will freeze at random times when the conditions are met. Rarely for me will it go to 8k or 10k counts but it can indeed wait that long sometimes.
I've reported this to Rigol USA and they have reproduced the bug on their test scopes without difficulty. They have assigned "Case Number 9147" to the bug and are working on some kind of fix. Meanwhile the workaround that I'm using is to have the Math set up but turned OFF in the Math menu until I need to actually observe or record a reading, then turn the Math on for as short a time as possible, then turn it back off again. This will (I think) keep the Measurements running. But work quickly, because the Measurements can freeze after just a few hundred counts, sometimes less than a minute, with Math ON.
Here are some test results from two different scopes I've tested, the "Old Scope" is the one running Boot Version 0.0.1.2 that I've returned to Rigol, and the "New Scope" is the one with Boot Version 0.0.1.3 that they sent me as a replacement, which does not have the Freeze Bug problem. As you can see both will have the Measurements fail after random times, sometimes very quickly and sometimes not so fast. Both are running the latest SP2 firmware.
Old Scope:
stopped at 7k14
stopped at 8k326
(still running at over 19k with no input signals)
stopped at 5k171
stopped at 279
stopped at 4k51
New Scope:
(still running at over 23k with no input signals)
stopped at 715
stopped at 10k272
stopped at 1k37
stopped at 3k910 with no input signals!
(still running at 13k240 with no input signals)
So at 3 or 4 sample counts per second it could take an hour or more for the measurements to stop, or it could take as little as one minute or even less.
I've attached a simple Setup file (inside a zipfile for upload here) which you can use to try to reproduce the bug. Don't worry, it's nothing fancy, just normal Math using two channels and pretty much default settings everywhere else. Unzip it, copy to a USB stick and load it into your scope. Provide some signals for the Math to work on, and wait and watch.
As I said I think this bug affects the scopes with the latest firmware SP2. I discovered it only after I had already upgraded to SP2 so I haven't specifically tested for it on the earlier firmware. I did use SP1 for a long time though (months of daily use including Math) on the "Old Scope" and never noticed it.