Products > Test Equipment
Siglent SDS800 Zoom out question (problem?)
2N3055:
--- Quote from: electr_peter on October 05, 2024, 03:10:57 pm ---
--- End quote ---
I am not trying to disprove anything. I claim that YOU failed to prove that it is useful, sophisticated and indispensable.
It is not. It is a trick and gives you absolutely the same result as "change timebase-stop" on all other scopes.
"Zoom out" specifically means to be able to show data before and after the actual event on the screen.
Keysight implementation does not do that. It haven't got "zoom out". Period. It is misleading, QED. There are thousands of people out that that wrongly think it does "zoom out" in definition from previous sentence. And that lie is being used by proponents of Keysight as "another proof of sophistication and advanced capabilities". While it is nothing more than snake oil.
If signal is very repetitive it doesn't matter. But then also you are not limited to anything. You simply stay in RUN mode and change timebase at will.
It is all the same.
If signal is some changing pattern, then it is also all the same to do these steps:
20ns/div -> change timebase -> STOP
gives result equivalent to
20ns/div -> STOP -> change timebase.
With both you will end up with some random part of sequence in the memory of the scope.. They both have same number of steps. Except that first one will let you extend to more time than 400µs worth of data.
At this moment I can see that you understand how it works but despite being shown the details, you refuse to accept there is more to it than you think.
Since it is not my intention to "convert" you or make you change your mind. You do you. If you are happy so am I.
My concern is only that all people involved into discussion understand exactly what actually is going on,
I think all was explained in sufficient detail, so I have nothing more to add.
electr_peter:
--- Quote from: 2N3055 on October 05, 2024, 03:39:32 pm ---I am not trying to disprove anything. I claim that YOU failed to prove that it is useful, sophisticated and indispensable.
--- End quote ---
It was showed multiple times to be useful (in some circumstances) and more sophisticated. It is not my problem that nuances are not recognized (on purpose?) by some. To every factual claim you get misdirection, misquoting, willful ignorance, mental gymnastics, term redefinitions which somehow proves zoom out is wrong. Oh, well
--- Quote ---At this moment I can see that you understand how it works but despite being shown the details, you refuse to accept there is more to it than you think.
Since it is not my intention to "convert" you or make you change your mind. You do you. If you are happy so am I.
My concern is only that all people involved into discussion understand exactly what actually is going on,
I think all was explained in sufficient detail, so I have nothing more to add.
--- End quote ---
I can concur to every statement above in other direction >:D Some are just willfully blind.
Fungus:
Nobody's saying it can't be done the Siglent way, but it's not a natural workflow.
Nobody works zoomed out because you can't see anything, we all work zoomed in to see maximum detail of whatever we're looking at.
Siglent forces you to stop, zoom out, recapture, then go back in again to see if you managed to get what you wanted. Every. Single. Time.
There's no way that's generally better than just pressing "STOP" then zooming out.
Talk of "the 'scope is slower that way" is also greatly exaggerated.
newbrain:
--- Quote from: me ---until facts are correctly explained
--- End quote ---
--- Quote from: Fungus on October 05, 2024, 04:24:29 pm ---Siglent forces you to stop, zoom out, recapture, then go back in again to see if you managed to get what you wanted. Every. Single. Time.
--- End quote ---
First, I prefer to clearly say "increase/decrease timebase" rather than zoom out/in.
No, it does not (and if you think about it, it does not make sense).
If you know you have to recapture (and you have to, with Siglent/LeCroy), there's no point in stopping, just increase the timebase and stop later.
But that's not the way I do it.
You can set from the beginning a suitably long timebase and a zoom on the trigger area for details (or wherever you like).
You can stop when you like the composition and no one has their eyes closed, then you can zoom in and out (to the full capture extent) as much as you like.
Would I do differently on a "classical" scope? Probably not if I had the choice, yes if that was the only choice (as, in fact, it was for me).
The only real advantage of the "increase timebase after stop" is if I notice something (in the limited viewport of the screen) and my reflexes are fast enough to stop the capture before the next retrigger - otherwise it's just a shot in the dark (and BTW, with the Keysight trick one is SOL by design in this case).
nctnico:
--- Quote from: newbrain on October 05, 2024, 04:54:41 pm ---
--- Quote from: me ---until facts are correctly explained
--- End quote ---
--- Quote from: Fungus on October 05, 2024, 04:24:29 pm ---Siglent forces you to stop, zoom out, recapture, then go back in again to see if you managed to get what you wanted. Every. Single. Time.
--- End quote ---
First, I prefer to clearly say "increase/decrease timebase" rather than zoom out/in.
No, it does not (and if you think about it, it does not make sense).
If you know you have to recapture (and you have to, with Siglent/LeCroy), there's no point in stopping, just increase the timebase and stop later.
--- End quote ---
The thing is that if you need to go back & forth a lot between horizontal positions and timebase, being able to zoom in/out horizontally / scroll left/right after making an acquisition is just easier for people as it saves a lot of fiddling with buttons and thinking about what settings are needed exactly. When dealing with a complicated problem / circuit, the last thing you need is test equipment being more complicated to operate than necessary. You have to be carefull not to confuse your personal preference with what other people like to do. Also keep in mind that your projects / workflow may be entirely different so capturing beyond the screen is not useful for you. But that doesn't mean capturing beyond the screen is useless for everyone!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version