[Rigol #$%§ ... !!!]Bad day?
[Rigol #$%§ ... !!!]Bad day?So you've not studied Bud and MarkL's analysis of the 1054z then?
[Rigol #$%§ ... !!!]Bad day?So you've not studied Bud and MarkL's analysis of the 1054z then?
Link please ?
Some of the "nitty gritty" is here and the following page/s:
https://www.eevblog.com/forum/blog/eevblog-683-rigol-ds1000z-ds2000-oscilloscope-jitter-problems/msg563330/#msg563330
REMEMBER these guys uncovered the design flaws for us all to see.
Thanks for your report. Just to be completely clear.... you did try the following?
1. Display a signal on CH1 from the probe Calibrator, at 1V/div, trigger type Edge, trigger level 2.00 V, sweep mode Auto
2. Set Horizontal Scale to 1 us/div
3. Select "Auto" from Acquire>Mem Depth menu
4. Select "100 ms" from Display>Persis. Time menu
5. Enter Horizontal Zoom mode by pressing the Horizontal Scale knob
Thanks for your report. Just to be completely clear.... you did try the following?
1. Display a signal on CH1 from the probe Calibrator, at 1V/div, trigger type Edge, trigger level 2.00 V, sweep mode Auto
2. Set Horizontal Scale to 1 us/div
3. Select "Auto" from Acquire>Mem Depth menu
4. Select "100 ms" from Display>Persis. Time menu
5. Enter Horizontal Zoom mode by pressing the Horizontal Scale knob
Yeah, checked it again using that exact sequence and all I can notice is a slight hesitation on the screen update when going into H Zoom mode. I did it 5-6 times and the behaviour seems consistent.
Looking at your video, using that sequence, it seems all the controls goes unresponsive but the scope it self is continuing to operate and updating the display with the waveform. So is something triggering the KeyLock feature? and is the KeyLock feature otherwise working normally? just a thought...
-- and the scope freezes, stops responding to the Telnet connection, and requires a reboot. But it still shows a live waveform !!
-- and the scope freezes, stops responding to the Telnet connection, and requires a reboot. But it still shows a live waveform !!So more of a lockup than a freeze?
Just a guess: the processor encounters some critical exception, but FPGA keeps operating as usual. That might explain why the waveforms are still updating and the rest of the scope is unresponsive.
In regards to your hardware issue guess, it well may be the case. I have opened my 2072a to fix the ADC clock problem and what I found beside that problem was bunch of other hardware related problems all over the board, along and across. In one instance reviewing a circuit that occupied 1 square inch of space on the PCB I counted 10 design errors! Wrong component selection, wrong design, wrong circuit layout. 10 errors per sq inch,
...
So where is Rigol on this issue? Where's Dave? Based on our sample we can expect _half_ of all the DS1054 units out there to have this problem.
...
(Hello, Rigol.... are you out there? Dave? Earth to Dave, come in please...... over.......)
Are you aware of this problem? It seems to affect about half of the DS1054Z scopes that have tested for it (over 25 as I write this, with at least 13 affected). The problem occurs in scopes running firmware 04.03 and also in scopes running 04.02.
The scope "locks up" and does not respond to any user input (buttons, knobs, SCPI commands over LAN) and requires a power-cycle reboot. To reproduce the condition reliably, start with CH1 probe connected to Calibrator for a signal (although any signal or even no signal will also work). Set Horizontal timebase to 1 us/div or faster. Set Memory Depth to AUTO. Set Display Persistence Time to 100 ms, or any value other than "min". Enter Horizontal Zoom (Delayed) mode by pressing the Horizontal Scale knob or by using the menu item button. Scope locks up at this point. Or do the steps in different sequence, like have Mem Depth set at some value other than Auto, enter Horizontal Zoom then select "Auto" Mem Depth... scope locks up. The scope continues to show a live waveform but is completely unresponsive to any knobs or button presses. In this state, it also does not recognize attempts to connect over the LAN using Telnet. If the LAN connection is already established before the scope freezes, it stops responding to SCPI commands (connection is dropped).
The only way to restore function is to power-cycle the scope. Sometimes even power-cycling results in continued lockup and then the scope needs to be reset using the "5th Left Menu Button" reset technique which results in the scope coming up in Chinese (but operational.)
Please check the EEVBlog thread here:
https://www.eevblog.com/forum/testgear/rigol-ds1054z-freeze-up-bug/
And my videos demonstrating the bug:
Thank you for your attention to this matter. A perfectly legitimate combination of user settings should never cause an instrument to lock up completely requiring a hard reboot, and the fact that the "bug" appears in approximately half the units tested, using 04.02 and 04.03 firmwares equally, is very strange.