|
Unfortunately, at the first message here I made a mistake. I wrote that the problem occurs when the 2M memory depth and two channels are used. Probably it should be clear that I meant that the problem occurs when the oscilloscope uses all available memory of 2M. Simply, after reading my message, I saw that it can not be understood correctly, namely that when using two channels at once, I managed to allocate a memory depth of 2M for each channel, and this is not possible. Therefore, just in case, I will clarify that this is a situation when both channels are switched on and in use in the oscilloscope, and the memory depth is set to 1M, which in total gives a memory depth of 2M, since each channel uses 1M of memory. Today I tried again to reproduce the problem described here in the hope that there might be a bad day then, and maybe some natural phenomena influenced the work of the oscilloscope. Within five minutes, I again managed to achieve an automatic oscilloscope reset and reset the settings to their default values. This time it happened when I tried to switch off the second channel in the specified oscilloscope operation mode. The first time I pressed the "CH2 MENU" button, I heard a confirmation tone that the button was actually pressed and the oscilloscope registered its pressing, but after that the channel did not shut down; I waited for a shutdown of about 15-20 seconds. After that, I pressed the button a few more times in an attempt to turn off the second channel after all and at one of the next presses the oscilloscope automatically rebooted. I'll add one more noticed oddity in the oscilloscope's work. If in a situation where the oscilloscope operates using only one channel (the second channel is turned off) and the memory depth is 2M, then the second channel is taken and turned on, the memory depth used will suddenly change by 512K, although the change to 1M looks much more logical.
|
|