Products > Test Equipment

Oscilloscope Zoom Out Quirk

<< < (63/113) > >>

2N3055:

--- Quote from: nctnico on June 11, 2020, 02:19:15 pm ---You are free to find a workflow easier. But it still means you go through way more steps to achieve that result than I do (which is also fine by me). ...
--- End quote ---

It's same amount of steps. You Zoom Out,  I Zoom In.

And on Picoscope with big screen and mouse scroll wheel it is so intuitive I don't even think about it.
That is for debug work similar to what you explained in your original post.

For interactive work ( what I call "scoping around") I use Keysight and twiddle knobs all the time. I will twiddle timebase in and out, and will be in Auto mode. Working similar to how you would with analog scope. Then I will stumble upon a signal that has frequency of occurring slower than what auto mode is auto triggering and  I want it to stay on screen between triggers so triggering is stable. It might be something interesting so I press Single for it to capture it to Stop so I can take a look at what it is. This is the point where I can :

1 Change timebase to be longer to make sure to capture all of it (twiddle knob)
2. Arm for single and wait for trigger (press button)
3. Change timebase and horizontal position to look at signal in detail (like a full screen zoom in/out)

Or I can do this:

1. Go into scope setting and set acquisition memory for this (enter number of keystrokes and twiddles for your scope)
2. Arm for single and wait for trigger (press button)
3. Change timebase and horizontal position to look at signal in detail (like a full screen zoom in/out)
4. Once you move form this point go into scope setting and set acquisition memory for general work.

There is no even need for zoom mode. Zoom mode will add one more step to first procedure, and it will use some screen. OTOH it will allow you to have overview over where in the buffer are you, which can be confusing when you have zoom factors of 10000x. So with zoom mode it is same number of steps..

Martin72:

--- Quote from: EEVblog on June 11, 2020, 03:51:48 am ---Yes, on the Siglent you literally change the memory depth on the menu and the memory depth shown in the bottom sample window doesn't change. It's insane.

--- End quote ---

That´s not completely correct…

In the menu, you could change the memdepth to 10k, 100k, 100M and 200M, so far so good.
But it will ony change in real (bottom sample window) when the timebase is in "the range".
I had created a little table:



So, when you are in a timebase that "allows" 200Mpts memory, you could choose want yout want and it will be used (and displayed).
For example, when you are in a timebase where only 40Mpts are "possible", you could choose 100K or 10K, but you got no effect when choosing 100Mpts or 200Mpts.
So in my opinion, the selectable memory size is "semi-manual"....
When it´s not a big deal to change it in the firmware, siglent could let the user decide to have always the full memory control or change to auto mode.
And all will be happy... ;)



maginnovision:
I think we already established it's a very limited(4 or 5 options?) memory LIMIT. Not a depth selection.

2N3055:

--- Quote from: Martin72 on June 11, 2020, 07:45:25 pm ---
--- Quote from: EEVblog on June 11, 2020, 03:51:48 am ---Yes, on the Siglent you literally change the memory depth on the menu and the memory depth shown in the bottom sample window doesn't change. It's insane.

--- End quote ---

That´s not completely correct…

In the menu, you could change the memdepth to 10k, 100k, 100M and 200M, so far so good.
But it will ony change in real (bottom sample window) when the timebase is in "the range".
I had created a little table:

(Attachment Link)

So, when you are in a timebase that "allows" 200Mpts memory, you could choose want yout want and it will be used (and displayed).
For example, when you are in a timebase where only 40Mpts are "possible", you could choose 100K or 10K, but you got no effect when choosing 100Mpts or 200Mpts.
So in my opinion, the selectable memory size is "semi-manual"....
When it´s not a big deal to change it in the firmware, siglent could let the user decide to have always the full memory control or change to auto mode.
And all will be happy... ;)

--- End quote ---
Thanks for this Martin.
That confirms my statement the setting is "auto mode max memory setting", meaning it will autorange memory, trying to keep sample rate highest possible until timebase becomes slow enough that it will limit memory and start slowing down sampling. That is exactly how Pico handles memory.
I also agree that if possible Siglent should enable user sacrifice history mode, and use full length sampling if user for some reason wants that . Making existing History mode they did was more complicated than just making it simply stupidly sample fixed amount.

Martin72:

--- Quote from: maginnovision on June 11, 2020, 07:53:50 pm ---I think we already established it's a very limited(4 or 5 options?) memory LIMIT. Not a depth selection.

--- End quote ---

Sounds logically to me...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod