Products > Test Equipment
Most (Digital-)Scopes are freezing while vertical adjustement...
nctnico:
--- Quote from: JPortici on November 15, 2022, 07:03:08 am ---As i wrote in another thread
"like the "zoom out quirk"
it's really incredible what people fixate on. It's just another non issue.
--- End quote ---
I don't think you fully understand what is going on. What the Rigol seems to be doing is wait until the DSO thinks the user is done adjusting the vertical position for so long that it is perceived as lag. The magic number for humans to experience something without delay is somewhere between 100ms and 200ms. Wait longer, and it is perceived as laggy. So for a fluent user experience (which isn't a non issue!) it is better for a DSO to just try to put traces on the screen while the vertical position is adjusted. This helps both giving visual feedback to the user and prevent perceived lag.
Actually, this makes me wonder whether there is a similar lag / delay on the Rigol when you change the trigger level.
alm:
--- Quote from: JPortici on November 15, 2022, 07:51:12 am ---Anyway i believe the fuss is over the fact that until the recent past most people had seen TDS2000 and simillar scopes, with 2.5kS acquisitions. Indeed it looked istantaneous, because the scope was refreshing faster than their movement. With deep acquisitions, not so much.
--- End quote ---
Actually the old Tek digital scopes with CCDs had pretty low refresh rates compared to modern scopes. I see no reason why a scope sampling say 10 * 1 ms/div in 2.5 kS, which should take 10 ms to fill, would refresh any faster than a scope sampling 10 * 1 ms/div in 10 MS, which should also take 10 ms. It just has to sample faster and move more data, but any scope with such deep memory should be able to handle that, since that's the whole reason for buying a deeper memory scope.
Based on ntcnico's description it sounds more like a UI choice rather than anything dictated by the hardware.
JPortici:
I completely understand where the issue is. I used to have a rigol after all, or i wouldn't be so critical of the brand at all times.
Judging by the first impression video the vertical movement behaves exactly as it does with many other scopes I own, owned or used. Acquisition is stopped and current data is moved around so the user can see where it will be placed after the move.
Fine with me.
Maybe the lag after moving stuff around can be improved, maybe not.
What is not fine is what other OLDER rigol scopes used to so which was stop EVERYTHING and not even update the screen so you are guessing where it's going to be. That is not fine at all, that is a bug/poor design choice, and that is not what i saw in the first impression video.
joeqsmith:
--- Quote from: Martin72 on November 14, 2022, 10:15:55 pm ---..
So what do you think, when scope“s freezes while adjusting vertical line, is it a bug most scopes then got ?
Keysight are mentioned not to do this, also GWInstek - Not all models.
..
--- End quote ---
I have no idea what you are saying. I went back and looked at the thread and still wasn't sure. Sounded like Dave had made some video but I skipped to the top post and nothing.
So set any scope to say 1 second per division and then adjust the offset then change the gain. Both adjustments will cause the scope to stop plotting. So, assuming the scope isn't some Siglent POS with poor encoders, if you continue to adjust say offset, the scope "freezes" the entire time. Minutes, hours, days.... Once you stop making adjustments, the scope will start plotting where it left off or maybe it resets to T0 but in both cases it is not smooth.
bdunham7:
--- Quote from: nctnico on November 15, 2022, 11:50:30 am ---What the Rigol seems to be doing is wait until the DSO thinks the user is done adjusting the vertical position for so long that it is perceived as lag.
--- End quote ---
I don't know if this comes into play, but the fact that its acquisition is more than the one screenful (to support the zoom-out...) probably slows down its retrigger quite a bit.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version