Hmmm... this is pretty strange indeed. We have at least one other person who IS able to reproduce the freezeup, but several others who cannot.
Well, now that I know it can be avoided by using full memory depth, it's not really much of a problem for me, but it certainly is strange that some (at least two!) scopes have the bug and others don't.
(video linked up above)
What's the date of calibration for your scope? Mine's March 4, 2015, and I only took delivery of it yesterday. It's the closest thing I can think of to a "build date", something we could use to determine roughly when these were made.
My DS2000 was also freezing all the time when I first got it, it was really annoying I would get a lock up every 20 minutes on average, firmware upgrade to 3.0.3 solved the issue. The version that was buggy was 3.0.0. Since I upgraded to 3.0.3 I only had one lock up of the UI in 3 months.
Same on my brand new DS1054Z (4.02.SP4 as yet un-hacked). Mine will freeze after changing Persistence setting at anything faster than 20uS with Mem-Depth at Auto when put into Zoom mode. Changing from Auto to the maximum 24M (why is my unhacked 1054Z saying 24M? [edit: oh yeah - it's still on the Trial - doh!]) stops it freezing as reported above.
Oddly, it took me several tries before I was able to make it freeze, but it does it every time now.
I have also just made it freeze by changing the Persistence value while it was in Zoom mode @ 1us/div.
And again @ 20us - but this time I had to change the Persistence twice - it froze when I hit the button the second time to change it...
I think I'll let Rigol sort out the actual issue! Will just have to remember to keep it at 24M as suggested until Rigol sort it out (assuming it is firmware which I guess is most likely).
Is there no soft-reset for the scope - a combination of key-presses?
Cheers, Bob.
Hmmm... this is pretty strange indeed. We have at least one other person who IS able to reproduce the freezeup, but several others who cannot.
Well, now that I know it can be avoided by using full memory depth, it's not really much of a problem for me, but it certainly is strange that some (at least two!) scopes have the bug and others don't.
(video linked up above)
What's the date of calibration for your scope? Mine's March 4, 2015, and I only took delivery of it yesterday. It's the closest thing I can think of to a "build date", something we could use to determine roughly when these were made.
The cal cert says 16 Jan 2015.
I don't know if you've read about the "saga". We ordered the scope in early February, and due to backorder and longshoreman's strike, I didn't have a delivery until the first week of April. (I don't remember the exact dates offhand). This was "scope 1" which turned out to have a bad glitch on CH4. So after consulting with a Rigol tech and the folks at TEquipment I sent that one back and was shipped a "new" one from TEquipment. But... some alarms went off about the replacement "scope 2".
First, the packaging. There was only one box, it was not double-boxed like the first one and like the ones you see "unboxing" on YT videos. What happened to the outer box?
Second, the serial number. The "new" scope had an _earlier_ SN than the one I returned, by quite a bit of numbers. This didn't make sense to me, as all of TEquipment's stock at that time should have been from the container they received at the end of March.
Third, there were some minor differences in how the "feel" (control response timing) was compared to my memory of what the first scope felt like. Later I put that down to my imagination but now I'm not so sure any more.
And as we see now, the calibration date was in January, which fits with the early SN.
So I'm wondering what to make of all this. Is the scope I got as the "replacement" a lemon, not too bad to toss out like the first one but still not quite 100 percent "right"?
...
I think I'll let Rigol sort out the actual issue! Will just have to remember to keep it at 24M as suggested until Rigol sort it out (assuming it is firmware which I guess is most likely).
...
Thanks for that report, Bob! Now maybe Rigol will notice, especially if others can report the same bug.
...
My DS2000 was also freezing all the time when I first got it, it was really annoying I would get a lock up every 20 minutes on average, firmware upgrade to 3.0.3 solved the issue. The version that was buggy was 3.0.0. Since I upgraded to 3.0.3 I only had one lock up of the UI in 3 months.
Did other 2000 owners also have the same problem? I'm still waiting for more reports of this bug, most people don't seem to be reproducing it. If it's down to just mine, or a few from a short production run maybe, then I don't expect Rigol would fix it in a firmware update.
I'm also having trouble understanding how this could be a hardware fault, though. The first scope's glitching was obviously in hardware, but this one's a lot more difficult to call. Still, I've now reinstalled the 04.03 firmware again, and tested both with Options "installed" and "uninstalled". (I hate to use the "h" word.) Still the same problem happens.
Well, the closest thing to a "factory reset" is what comes up when one repeatedly presses the 5th dark grey left menu key during bootup, right? The scope comes up in Chinese. So I set English. The 1 us/div and Auto memory depth are set by default already. So I set Persistence to 100 ms, then enter Zoom mode... and it freezes.
I've tried everything suggested in this thread and still can't lock up my 1054z with firmware 4.02. And since we're sort of 50-50 for responders in this thread I'm going to guess that this is somehow due to a hardware variation -- however unlikely that seems.
I'll record this in the bug thread as "some users have reported scope lock ups when setting memory depth to AUTO, timebase to 1us, zooming in and changing the persistence from MIN something else."
Actually... by my count in this thread I am counting 5 who have reproduced the bug (including me) and 4 who have tried and can't reproduce it (including you). So instead of "some users" you could be saying "over half of the users who tried..."
Actually... by my count in this thread I am counting 5 who have reproduced the bug (including me) and 4 who have tried and can't reproduce it (including you). So instead of "some users" you could be saying "over half of the users who tried..."
Oh no, it sounds like we need another poll!
Actually... by my count in this thread I am counting 5 who have reproduced the bug (including me) and 4 who have tried and can't reproduce it (including you). So instead of "some users" you could be saying "over half of the users who tried..."
Oh no, it sounds like we need another poll!
Heh.. OK I put up a poll, and voted in it. Please everybody check it out and put your vote in!
Heh.. OK I put up a poll, and voted in it. Please everybody check it out and put your vote in!Plus another option: I haven't got a 1054Z but I want to see the results.
Heh.. OK I put up a poll, and voted in it. Please everybody check it out and put your vote in!Plus another option: I haven't got a 1054Z but I want to see the results.
The forum software has taken care of that; the "View Results" button is right below the actual poll. No need for a "fake" voting option ;-)