Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
TinkeringSteve:
Oh starting does work, the firmware apparently doesn't get to store that setting, it's back to "trace" when I start again.
--- Quote from: frozenfrogz on November 04, 2017, 07:40:27 pm ---No problems using FFT in memory mode.
Does your scope freeze every time / is it reproducible?
If it is persistent: Please try re-uploading the firmware as you already mentioned and if the error still remains, please share the extended system info for reference.
--- End quote ---
As to "does it always" - no - apparently not on CH1, but with at least CH2, when it's the only active channel, and I'm feeding in a sine @ 20 Hz, 3V with offset so that it's DC. And then set Mode to Memory.
frozenfrogz:
My scope does not freeze - regardless of which channels are activated etc. I fiddled around with the active channels selection, input selection of FFT function, window mode, trace/memory both in auto and record/stop mode and single shot triggering. My scope does not lock up.
TinkeringSteve:
--- Quote from: frozenfrogz on November 04, 2017, 08:30:21 pm ---My scope does not freeze - regardless of which channels are activated etc. I fiddled around with the active channels selection, input selection of FFT function, window mode, trace/memory both in auto and record/stop mode and single shot triggering. My scope does not lock up.
--- End quote ---
Funny. I can't reproduce it anymore either. I did a couple times before, only using Ch2 and restariting and going straight to "math" and changing the setting.
Now that I fiddled around a bit more, even restarting with only Ch2 active, going to math/fft and oing the memory setting, nah.
Weird.
frozenfrogz:
Good news everyone!
I recently bought another DS1054Z (and a DP832) and since the re-seller asked me to give some feedback I wrote a lengthy email regarding my user experience and also pointed towards this thread for more detailed information.
The re-seller forwarded my mail to the European Rigol service (had one or two phone calls with them in the past) and they again forwarded it to Rigol R&D, also stating they will have a closer look at our bug-list.
If and how this might affect the next firmware releases I can not tell, but after all it is another chance for communication.
This is just a heads up and while Rigol might be reading this: Thanks for taking us seriously and you are very welcome to chime in and get a part of this forum!
Lots of Rigol users to get in contact with around here!
bitseeker:
Excellent. Thanks for doing that. Hopefully, one day Rigol will pay attention to what goes on here. So far, they seem not to notice.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version