Playing with my DSOX1102G I just found out that both zoom and serial decode do not work in roll mode (even when stopped).
It is quite disappointing because I use those features a lot on my Tektronix at work.
Is it true also for 2000X and 3000X models, or only 1000X is crippled this way?
Roll mode is usually too slow for decodes to be useful.
Roll mode is usually too slow for decodes to be useful.
The way I often like to work is to go into roll mode and manually stop scope when I capture some events, then I zoom in into area of interest and examine waveforms and decodes.
BTW, I never understood why only Tektronix automatically switches to roll mode in slow time bases, now I guess it is because other scopes have limited capabilities in this mode.
BTW, I never understood why only Tektronix automatically switches to roll mode in slow time bases, now I guess it is because other scopes have limited capabilities in this mode.
FWIW, that spec is "per channel." Still, a memory increase is something that I'm pushing. If it happens, it'll probably be free.
For live debugging, it's less of an irritation, but for capturing & analyzing it could show up more.
Hi Daniel ,
Still pushing on this ?
This distorted waveforms are a consequence of memory shortage ?
Hi Daniel ,
Still pushing on this ?
This distorted waveforms are a consequence of memory shortage ?
I cannot tell what the video is trying to show because of the LOUD <EXPLETIVE DELETED> MUSIC!
Hi Daniel ,
Still pushing on this ?
This distorted waveforms are a consequence of memory shortage ?
I cannot tell what the video is trying to show because of the LOUD <EXPLETIVE DELETED> MUSIC!
Yes, this is a memory thing. Any scope will do this if you zoom out far enough, but the point at which it happens is a function of sample rate and memory depth.
I'll give you a hint too:
you were trying to sample a 50 MHz waveform at a 50 kHz sample rate with the keysight and at a 1 MHz Sample rate with the siglent.
if that doesn't tell you something...
the other interesting thing, which you can learn from, is that the siglent still was able to resolve a squarish wave, which is of course bogus because the frequency counter in the upper right of the screen is still displaying 50 MHz, the measurement instead would have told you the signal frequency was jumping. why? because the hardware counter/dvm are independent from the sampling system.
I'll give you a hint too:
you were trying to sample a 50 MHz waveform at a 50 kHz sample rate with the keysight and at a 1 MHz Sample rate with the siglent.
if that doesn't tell you something...
the other interesting thing, which you can learn from, is that the siglent still was able to resolve a squarish wave, which is of course bogus because the frequency counter in the upper right of the screen is still displaying 50 MHz, the measurement instead would have told you the signal frequency was jumping. why? because the hardware counter/dvm are independent from the sampling system.I can choose sample rate only by minimize time captured . I cannot choose manually . But how can I do when I have to capture 1s or 500 micros ?
Hi ,
I don't want to teach anyone .
Just show some facts .
IMHO I think that is good to show that , despite the biased opinions ...
Beside of your personal opinion about my experience maybe you put an explanation about what and why is happening .
Anyway thank you for your appreciations about me .
Best regards .
Hi ,
I don't want to teach anyone .
Just show some facts .
IMHO I think that is good to show that , despite the biased opinions ...
Beside of your personal opinion about my experience maybe you put an explanation about what and why is happening .
Anyway thank you for your appreciations about me .
Best regards .
Yes, this is a memory thing. Any scope will do this if you zoom out far enough, but the point at which it happens is a function of sample rate and memory depth.Thanks !
I was not sure , because on Siglent I reduced the memory to 14K (7 times smaller than 100k on EDUX) and waveforms seems still recognizable . But maybe at deeper zoom levels it doesn't take account about my settings , something like Keysight do with automatic memory allocation .
About 1Mpts. of memory ? Not even as paid option ?
Facts about what? Tell me what are facts. Fact is that you show wrong use of these both scopes without understanding what you are showing. (aliasing (do you know what it is), BOTH scopes)
Then this FFT.
I have added three images to my previous msg.
I hope you understand what you see there. After soon you can realize that least these two last images are something what you can not at all see with this Keysight model, not even if it is best model in this product serie. Do you know why. There is one real fact.
Then look again this your video where you show facts. Facts are of course that these are screens what you see. All we can see. This is perhaps only fact. But what you want show with this? I can not find anything. If you think you measure something or even look any meaningful things on the screens or for compare these oscilloscopes performance or features differencies, this is totally wrong way. In some thing Siglent is better than this Keysight and vice versa. Only what can say thayour "show" about it is total bullshit. Facts are just that you have two oscilloscopes and one video camera. Now we know this fact. Also we know now that you have no idea how to measure anything with these equipments.
Can you explain why you have selected these settings for looking this signal wioth FFT. Some idea?
Showing some "facts".
Just label these with "Bullshit" label and then they are ok.
Both scopes are good scopes but even good scope can not do anything useful in bad hands.
A key difference between Keysight and Siglent scopes is that Keysight always uses the maximum amount of memory available and Siglent (by default) only uses enough memory to fill the screen. On the Keysight you can zoom out and see more of the signal when using short time/div settings. On the Siglent OTOH you'd need to recapture the signal and then zoom in which is kinda clunky.
I'll give you a hint too:
you were trying to sample a 50 MHz waveform at a 50 kHz sample rate with the keysight and at a 1 MHz Sample rate with the siglent.
if that doesn't tell you something...
the other interesting thing, which you can learn from, is that the siglent still was able to resolve a squarish wave, which is of course bogus because the frequency counter in the upper right of the screen is still displaying 50 MHz, the measurement instead would have told you the signal frequency was jumping. why? because the hardware counter/dvm are independent from the sampling system.I can choose sample rate only by minimize time captured . I cannot choose manually . But how can I do when I have to capture 1s or 500 micros ?