| Products > Test Equipment |
| Siglent SDS800 Zoom out question (problem?) |
| << < (7/20) > >> |
| frank2644:
Thanks, again for more good info. I did manage to successfully confirm the marker frequencies of my sweep generator. I had impose the 20mhz bandwidth limit and the frequency measurements became stable and correct. It was a slow process to measure each segment, but iI was able to do it. No doubt others here could have figured out a faster way. More importantly, I don't think a zoom out capability would have helped. nctnico and 203055's recording method sounds good. Thanks again, Frank |
| KungFuJosh:
--- Quote from: frank2644 on October 03, 2024, 11:37:17 pm ---20mhz bandwidth --- End quote --- To keep communication clear, please follow standard labeling. Hertz is Hz. Lowercase m is millihertz, uppercase M is Megahertz. That's a slightly large difference. 😉 |
| electr_peter:
--- Quote from: Someone on October 03, 2024, 11:27:53 pm --- --- Quote from: electr_peter on October 03, 2024, 10:52:49 pm ---With Siglent, you would have to set slower timebase, capture again and zoom in - more steps and effort (not much, but still). --- End quote --- How many times does this need to be repeated? --- End quote --- Full quote: --- Quote from: electr_peter on October 03, 2024, 10:52:49 pm ---Is zoom out useful? Definitely, it allows quicker understanding of signal behavior at fast time base (main focus) and at slower time base without re-capturing again. With Siglent scopes (models having no fixed memory setting), you would have to set slower timebase, capture again and zoom in - more steps and effort (not much, but still). --- End quote --- How many times context of posts will be selectively ignored to discredit zoom out capability? --- Quote ---You do not have to use that workflow, if you wish to navigate around a larger window then capture it in the first place using zoom (or whatever method you prefer). When stopped all the data is there and there is no need to recapture as you claim. --- End quote --- Yeah, no need to recapture because you ignored first capture which was deemed too short/fast for some reason (how did you arrive to such conclusion without capturing, anyway?) and then recaptured on purposely slower time base. Oh, wait :palm: Keysight can capture at fast timebase AND gets more memory (aka "zoom out") AND can do whatever analysis with this capture. OR it can capture at slower timebase and do whatever. Siglent scopes (models having no fixed memory setting) can capture at fast timebase AND gets less memory thus FORCING you to recapture again in slower timebase if fast timebase capture memory if insufficient for analysis. Only after recapturing at slower timebase (which now gives adequate memory) you are free to do whatever. Keysight memory management is more flexible at fast timebases (while having no downsides) compared to Siglent. On Siglent scopes (models having no fixed memory setting) you get less memory at fast timebases. On Siglent scopes (models having fixed memory setting) you get same or more memory at fast timebases, but at slower update rate. Keysight scope gives more capture memory at fast timebases or is faster in RUN mode, obvious advantage. This fact does not change if some users do not appreciate/choose to ignore it. Let's say you are in hypothetical T&M cafe drinking coffee. Waiter asks if you want anything else and you say: "Can I have a biscuit, please?" If T&M cafe is run by Siglent (considering no fixed memory setting scope like SDS800HD), waiter responds: "Biscuit is not available to customers who have ordered coffee already. However, we will make biscuit if you order it with an additional coffee." If T&M cafe is run by Keysight, waiter responds: "I will check if biscuit is available and get it for you. If not, we will make biscuit if you order it with an additional coffee." Which cafe provides better service? :D In this analogy exchange coffee to single capture and biscuit to memory beyond display limits and you will get the gist. EDIT: added clarification on Siglent models as they differ in memory management. |
| frank2644:
--- Quote from: KungFuJosh on October 04, 2024, 12:10:01 am --- --- Quote from: frank2644 on October 03, 2024, 11:37:17 pm ---20mhz bandwidth --- End quote --- To keep communication clear, please follow standard labeling. Hertz is Hz. Lowercase m is millihertz, uppercase M is Megahertz. That's a slightly large difference. 😉 --- End quote --- Thanks, I never knew that. It's gonna be a challenge to remember that, I'm lucky to avoid using cps. https://en.wikipedia.org/wiki/Cycle_per_second#References Frank (very old guy) |
| Fungus:
--- Quote from: Someone on October 03, 2024, 11:27:53 pm ---]How many times does this need to be repeated? You do not have to use that workflow --- End quote --- How many times does it need to be repeated that it's the most natural, logical, sensible workflow. There is NO POSSIBLE EXCUSE for just taking seven samples at maximum zoom and nothing on either side. Hence the quip about scissors. Given the wide availability of right-handed scissors, why would anybody force themselves to learn and use left-handed ones? |
| Navigation |
| Message Index |
| Next page |
| Previous page |