Here's a peculiar one:
Conditions:
- DHO1074 (200MHz and 100MSa options enabled), F/W 00.02.12
- Only channel 4 enabled
- 10MHz fast-rise square wave of 2.5Vp (ground-referenced) coupled to channel 4 (1V/div) and to EXT Trig input (correctly terminated)
- Trigger engine configured EXT, rising edge, 1.25V Threshold, "normal" mode
- Memory depth "Auto", but 1MSa "works" as well - others not tested
Findings:
The scope won't trigger if the time base is set faster than 50ns/div or zoom is enabled faster than that and becomes very sluggish to respond to user inputs. At 50ns/div or slower, everything works normally. This peculiar behaviour isn't present if another channel is used. Also, just enabling another, additional channel will return the scope to "normal" operation. Triggering on channel 4 works completely normal, just channel 4 and external trigger shows this behaviour. It appears that "playing around in menus" may resolve this problem eventually though I'm not sure what operation in particular causes this. After a fresh reboot, the described problem returns.
More findings:
In Trigger menu with "External" trigger source selected, the "50%" button should be made inactive since it only resets the trigger threshold to 0V. The trigger threshold setting appears not to be very accurate when the external trigger input is used - I find the scope to trigger well between approx. -500mV and +3.5V threshold setting when I apply my 2.5Vp signal. Maybe the ~100ps edges affect the external trigger circuitry.
Web Interface:
Did anybody notice that when using the web interface, the browser window size gets "automatically" reset every now and then and as a consequence, the scroll bars get enabled and obstruct some of the screen area (very annoying). I want my manually resized remote scope screen to stay that way... It even resets the screen size to "window" if "full screen" is selected! Machine is a Windows 10 PC with Firefox browser, but a test with Edge shows the same problem. I'm not too much a Windows expert to know if this may be solved by browser configuration, but a quick scan through the setup menus didn't show up anything that might help (at least to my understanding). Any hint appreciated
!